Recommended modems for business segmentation
By collaborating with relay UEs through XR devices, and utilizing L3 multipath relay and modem-recommended cross-layer APIs, the limited number of antennas for XR devices in the 5G band is resolved, improving performance and communication quality.
Patent Information
- Application Number
- CN202580025868.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2024-04-12
- Filing Date
- 2025-03-03
- Publication Date
- 2026-11-17
AI Technical Summary
Small-form-factor extended reality (XR) devices such as XR glasses and smartwatches suffer from performance disadvantages in certain 5G frequency bands due to the limited number of antennas, making them unable to compete with full-capability user equipment (UE). Existing technologies have difficulty effectively improving this problem.
By collaborating XR devices with relay UEs to form virtual UEs, and utilizing the relay UEs to provide data forwarding, combined with L3 multipath relay technology and modem recommendations, cross-layer APIs are used for service splitting and load balancing to improve the performance of XR devices.
Through collaborative operation, XR devices can function as if they have more Rx antennas, improving system performance, achieving better MIMO gain and path switching, and enhancing communication quality.
Smart Images

Figure CN123125945A_ABST
Abstract
Description
[0001] Cross-references
[0002] This patent application claims priority to U.S. Patent Application No. 18 / 634,081, filed April 12, 2024, entitled “MODEM RECOMMENDATIONS FORTRAFFIC SPLITTING,” which is assigned to the assignee of this application. The disclosure of the earlier application is considered part of this patent application and is incorporated herein by reference. Technical Field
[0003] This disclosure relates in general to wireless communications, and in particular to techniques, apparatus, and methods for recommending modems for service splitting. Background Technology
[0004] Wireless communication systems are widely deployed to provide a variety of services, including voice, text, messaging, video, data, and / or other services. Services may include unicast, multicast, and / or broadcast services, etc. Typical wireless communication systems employ multiple access radio access technologies (RATs) capable of supporting communication with multiple users by sharing available system resources (e.g., time-domain resources, frequency-domain resources, spatial-domain resources, and / or device transmit power, etc.). Examples of such multiple access RATs 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, and Time Division Synchronous Code Division Multiple Access (TD-SCDMA) systems.
[0005] The aforementioned Multiple Access RATs have been adopted in various telecommunications standards to provide a common protocol enabling different wireless communication devices to communicate at the city, national, regional, or global level. An example telecommunications standard is New Radio (NR). NR (also known as 5G) is part of the continuous evolution of mobile broadband announced by the 3rd Generation Partnership Project (3GPP). NR (and other mobile broadband evolutions beyond NR) can be designed to better support the Internet of Things (IoT) and reduced-capacity device deployments, industrial connectivity, millimeter-wave (mmWave) expansion, licensed and unlicensed spectrum access, non-terrestrial network (NTN) deployments, sidelinks and other device-to-device direct communication technologies (e.g., cellular vehicle-to-everything (CV2X) communications), massive MIMO, decomposed network architectures and network topology expansion, multi-subscriber implementations, high-precision positioning and / or radio frequency (RF) sensing, and more. As the demand for mobile broadband access continues to grow, further improvements to NR can be implemented, and other radio access technologies (such as 6G) can be introduced to further advance mobile broadband evolution. Summary of the Invention
[0006] In some specific implementations, an apparatus for wireless communication at a first user equipment (UE) includes: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to: identify a recommended service split between a first connection associated with the first UE and a second connection associated with a second UE by a modem of the first UE; and to provide auxiliary information indicating the recommended service split by the modem using a cross-layer application programming interface (API).
[0007] In some specific implementations, a method for wireless communication performed by a first UE includes: identifying a recommended service split between a first connection associated with the first UE and a second connection associated with a second UE by a modem of the first UE; and providing auxiliary information indicating the recommended service split by the modem using a cross-layer API.
[0008] In some implementations, a non-transitory computer-readable medium storing a set of instructions for wireless communication includes one or more instructions that, when executed by one or more processors of a first UE, cause the first UE to: identify a recommended service split between a first connection associated with the first UE and a second connection associated with a second UE by a modem of the first UE; and provide auxiliary information indicating the recommended service split by the modem using a cross-layer API.
[0009] In some specific implementations, a first device for wireless communication includes: components for identifying, by a modem of the first device, a recommended traffic split between a first connection associated with the first device and a second connection associated with a second device; and components for providing auxiliary information indicating the recommended traffic split by the modem using a cross-layer API.
[0010] Various aspects of this disclosure may be implemented or be implemented as described in whole by or embodied in the methods, apparatus, systems, computer program products, non-transitory computer-readable media, user equipment, base stations, network nodes, network entities, wireless communication devices and / or processing systems as fully described in the specification and drawings and illustrated in the specification and drawings.
[0011] The preceding paragraphs of this section have broadly summarized some aspects of this disclosure. These and additional aspects and their associated advantages will be described below. The disclosed aspects can serve as the basis for modifying or designing other aspects for performing the same or similar purposes of this disclosure. Such equivalent aspects do not depart from the scope of the appended claims. The characteristics of the aspects disclosed herein, their organization and operation, and their associated advantages will be better understood from the following description taken in conjunction with the accompanying drawings. Attached Figure Description
[0012] The accompanying drawings illustrate some aspects of this disclosure but do not limit its scope, as other aspects can be achieved by this description. Each drawing in the drawings is provided for illustrative and descriptive purposes and not as a definition of limitation of the claims. Identical or similar reference numerals in different drawings may identify identical or similar elements.
[0013] Figure 1 This is a diagram illustrating an example of a wireless network according to the present disclosure.
[0014] Figure 2 This is a diagram illustrating an example of communication between a network node and a user equipment (UE) in a wireless network according to the present disclosure.
[0015] Figure 3 This is a diagram illustrating an example decomposed base station architecture according to this disclosure.
[0016] Figure 4 This is a diagram illustrating examples of the accompanying UE and anchor UE according to this disclosure.
[0017] Figure 5 This is a diagram illustrating an example of a multipath relay system according to the present disclosure.
[0018] Figure 6 This is a diagram illustrating an example of a multipath relay system according to the present disclosure.
[0019] Figure 7 This is a diagram illustrating an example of a synchronization requirement for multimodal applications according to this disclosure.
[0020] Figures 8 to 10 This is a diagram illustrating an example of a modem recommendation associated with service segmentation according to this disclosure.
[0021] Figure 11 This is a diagram illustrating an example process associated with modem recommendations for service segmentation according to this disclosure.
[0022] Figure 12 This is a diagram of an example device for wireless communication according to the present disclosure. Detailed Implementation
[0023] Various aspects of this disclosure are described below with reference to the accompanying drawings. However, aspects of this disclosure may be embodied in many different forms and should not be construed as limited to any specific aspect illustrated or described with reference to the drawings or otherwise presented in this disclosure. Rather, these aspects are provided so that this disclosure will be comprehensive and complete, and will fully convey the scope of protection of this disclosure to those skilled in the art. Those skilled in the art will understand that the scope of this disclosure is intended to cover any aspect of this disclosure disclosed herein, whether implemented independently of or in combination with any other aspect of this disclosure. For example, various combinations or numbers of aspects set forth herein may be used to implement an apparatus or a practice. Furthermore, the scope of this disclosure is intended to cover apparatuses having structures and / or functionalities other than those available for practicing the various aspects of this disclosure set forth herein, or methods practiced using these other structures and / or functionalities. Any aspect of this disclosure disclosed herein may be embodied by one or more elements of the claims.
[0024] Various methods, operations, apparatuses, and techniques will now be presented with reference to them. These methods, operations, apparatuses, and techniques will be described in detail below and illustrated in the accompanying drawings by various boxes, modules, components, circuits, steps, processes, or algorithms (collectively, “elements”). These elements may be implemented using hardware, software, or a combination of hardware and software. Whether such elements are implemented as hardware or software depends on the specific application and the design constraints imposed on the system as a whole.
[0025] Compared to full-capable user equipment (UE) (e.g., smartphones), extended reality (XR) devices (such as XR glasses or other wearable devices (e.g., smartwatches)) can be associated with a relatively small form factor. This small form factor can result in a limited number of antennas for certain frequency bands compared to a full-capable UE. For example, the small form factor may prevent XR devices from having four receive (Rx) antennas in certain 5G bands, which is common in full-capable UEs. Conversely, XR glasses may be limited to two Rx antennas, and smartwatches to a single Rx antenna. XR devices with fewer Rx antennas compared to full-capable UEs may experience performance disadvantages associated with full-capable UEs.
[0026] To mitigate some of the performance disadvantages described above, in some scenarios, the XR device, which can be considered the anchor UE, can cooperate with a relay UE (or a companion UE), which can be used to improve the anchor UE's performance. For example, the anchor UE and the relay UE can be aggregated into a virtual UE to maximize multiple-input multiple-output (MIMO) gain or allow path switching / splitting. In this companion scenario, the relay UE can provide data forwarding to the anchor UE, and the anchor UE and the relay UE can communicate with each other via one or more types of links, such as ultra-wideband (UWB) links, PC5 NR sidelinks (licensed or unlicensed), WiFi links, Bluetooth links, Universal Serial Bus (USB) links, Frequency Range 2 (FR2) links, etc. As an example, the anchor UE can have one or two Rx antennas, and by cooperating with the relay UE, a virtual UE with four or more Rx antennas can be formed. Therefore, the XR device can operate as if it had more Rx antennas than physically configured for the XR device.
[0027] In some scenarios, the supporting UE can be a Layer 3 (L3) multipath relay UE. To support L3 multipath relay, various options for service handover or splitting may exist for uplink services. For example, in the first option, the Access Service Guided Handover Split (ATSSS) functionality in the anchor UE's application client can split the service into a first data stream and a second data stream, where the first data stream can be to or from the anchor UE, and the second data stream can be to or from the relay UE. In the first option, the ATSSS functionality can split or aggregate services at the User Plane Function (UPF) below the Internet Protocol (IP) layer in the application client. In the second option, the Multipath Fast User Datagram Protocol (UDP) Internet Connection (MPQUIC) layer (or Multipath Transmission / Control Protocol (MPTCP) layer) in the anchor UE's application client can split the service into a first data stream and a second data stream, or the MPQUIC layer (or MPTCP layer) can aggregate the first and second data streams.
[0028] When using the first option, the anchor UE can provide UE assistance information to the UPF, which allows the default uplink or downlink allocation to be changed (e.g., the anchor UE can use ATSSS and local conditions to determine the splitting of uplink traffic, and the UPF can use N4 rules and feedback from the anchor UE to split downlink traffic). However, when using the second option, this UE assistance information may not be supported by the anchor UE. In other words, when the MPQUIC layer is responsible for splitting traffic above the application client's IP layer, the anchor UE may not be configured to support UE assistance information. Therefore, when the MPQUIC layer is responsible for splitting traffic above the application client's IP layer, the anchor UE may not be able to change the default uplink allocation. For example, the anchor UE may not be able to change the allocation between the first and second data streams, which could negatively impact the overall performance of the anchor UE.
[0029] The overall picture involves modem recommendations for service splitting. For example, when transport layer splitting or aggregation resides above the IP layer in the anchor UE or application server, the modem of the anchor UE can provide auxiliary information to the anchor UE's MPQUIC-aware application, the anchor UE's application client, and / or the application server. The modem can provide auxiliary information using a cross-layer application programming interface (API), and this auxiliary information can recommend splitting or load balancing of uplink or downlink services between two connections, where the first connection may be associated with the anchor node and the second connection may be associated with a relay node. The modem can provide recommendations or auxiliary information for uplink service splitting via the cross-layer API for the MPQUIC-aware application. Alternatively, the modem can provide recommendations or auxiliary information for downlink service splitting via a cross-layer API for the application client, and the application client can forward the recommendations or auxiliary information to the application server. The application server can then determine whether to implement the recommended downlink service splitting.
[0030] Some aspects more specifically relate to modem recommendations for uplink or downlink traffic splitting. In some examples, the modem of a first UE (e.g., an anchor UE) may identify a recommended traffic split between a first connection associated with the first UE and a second connection associated with a second UE (e.g., a relay UE). The recommended traffic split can be used for downlink adaptive load balancing via an application server. Alternatively, the recommended traffic split can be used for uplink adaptive load balancing via the first UE. The modem of the first UE may use a cross-layer API to provide auxiliary information that indicates the recommended traffic split. The cross-layer API may be a dedicated API for an MPQUIC-aware application for the first UE, or the cross-layer API may be used by an application client of the first UE. The auxiliary information may include information about a first link condition associated with the first connection and a second link condition associated with the second connection. In some aspects, the UE's application client may forward the auxiliary information to the application server.
[0031] Specific aspects of the subject matter described in this disclosure can be implemented to achieve one or more of the following potential advantages. In some examples, by implementing auxiliary information indicating recommended service splitting, the described techniques can be used by a first UE to split uplink services based on the auxiliary information, or by an application server to split downlink services based on the auxiliary information. The auxiliary information (which can be implemented by a cross-layer API) can be applied when packet aggregation or splitting is performed above the IP layer of the first UE or the application server, rather than below the IP layer at the first UE or the UPF. The cross-layer API allows the modem of the first UE to relay the auxiliary information to the MPQUIC-aware application or the application server. Due to the auxiliary information, the modem of the first UE can control load balancing and / or service splitting based on the link conditions of the first UE and the second UE, thereby improving overall system performance.
[0032] Multiple access radio access technology (RAT) has been adopted in various telecommunications standards to provide a common protocol that enables wireless communication devices to communicate at the city, enterprise, national, regional, or global level. For example, 5G New Radio (NR) is part of the continuous mobile broadband evolution announced by the 3rd Generation Partnership Project (3GPP). 5G NR supports a variety of technologies and use cases, including enhanced mobile broadband (eMBB), ultra-reliable low-latency communication (URLLC), massive machine-type communication (mMTC), millimeter wave (mmWave) technology, beamforming, network slicing, edge computing, Internet of Things (IoT) connectivity and management, and network function virtualization (NFV).
[0033] With increasing demand for broadband access and the evolution of technologies supported by wireless communication networks, further technological improvements can be adopted in or implemented for 5G NR or future RATs (such as 6G) to further advance the evolution of wireless communication for a variety of existing and new use cases and applications. These technological improvements can be associated with new frequency band extensions, licensed and unlicensed spectrum access, overlapping spectrum use, small cell deployments, non-terrestrial network (NTN) deployments, decomposed network architectures and network topology extensions, device aggregation, advanced duplex communication, sidelinks and other device-to-device direct communication, IoT (including passive or ambient IoT) networks, reduced-capacity (RedCap) UE functionality, industrial connectivity, multi-subscriber implementations, high-precision positioning, radio frequency (RF) sensing and / or artificial intelligence or machine learning (AI / ML), and more. These technological improvements can support use cases such as wireless backhaul, wireless communication hubs, XR and metaverse applications, meta-services for supporting vehicle connectivity, holographic and mixed reality communications, autonomous and collaborative robots, vehicle platooning and collaborative maneuvering, sensor networks, posture monitoring, brain-computer interfaces, digital twin applications, asset management, and general coverage applications using off-ground and / or aerial platforms, among others. The methods, operations, apparatuses, and techniques described herein can implement one or more of the foregoing technologies and / or support one or more of the foregoing use cases.
[0034] Figure 1 This is a diagram illustrating an example of a wireless communication network 100 according to the present disclosure. The wireless communication network 100 may be a 5G (or NR) network or a 6G network, or may include elements of a 5G (or NR) network or elements of a 6G network, etc. The wireless communication network 100 may include a plurality of network nodes 110, shown as network node (NN) 110a, network node 110b, network node 110c, and network node 110d. Network nodes 110 may support communication with a plurality of UEs 120 (shown as UE120a, UE 120b, UE 120c, UE 120d, and UE 120e).
[0035] Network nodes 110 and UEs 120 of wireless communication network 100 can communicate using the electromagnetic spectrum, which can be subdivided into various categories, bands, carriers, and / or channels according to frequency or wavelength. For example, devices of wireless communication network 100 can communicate using one or more operating bands. In some aspects, multiple wireless networks 100 can be deployed in a given geographical area. Each wireless communication network 100 can support a specific RAT (which may also be referred to as an air interface) and can operate on one or more carrier frequencies in one or more frequency ranges. Examples of RATs include 4G RATs, 5G / NR RATs, and / or 6G RATs, etc. In some examples, when multiple RATs are deployed in a given geographical area, each RAT in that geographical area can operate on a different frequency to avoid interference with each other.
[0036] Various operating bands have been defined by frequency range designations: FR1 (410 MHz to 7.125 GHz), FR2 (24.25 GHz to 52.6 GHz), FR3 (7.125 GHz to 24.25 GHz), 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). Although a portion of FR1 is greater than 6 GHz, in some documents and articles, FR1 is often (interchangeably) referred to as the “sub-6 GHz” band. Similarly, in some documents and articles, FR2 is often (interchangeably) referred to as the “millimeter wave” band, but this is distinct from the Extremely High Frequency (EHF) band (30 GHz to 300 GHz) designated as the “millimeter wave” band by the International Telecommunication Union (ITU). The frequencies between FR1 and FR2 are generally referred to as the midband frequencies, including FR3. Frequency bands falling within FR3 can inherit FR1 or FR2 characteristics, thereby effectively extending the characteristics of FR1 or FR2 into the midband frequency range. Therefore, "below 6 GHz" (if used herein) can broadly refer to frequencies less than 6 GHz, within FR1, and / or included in the midband frequency range. Similarly, the term "millimeter wave" (if used herein) can broadly refer to frequencies included in the midband frequency range, within FR2, FR4, FR4-a, FR4-1, or FR5, and / or within the EHF band. Higher frequency bands can extend 5G NR operation, 6G operation, and / or other RATs above 52.6 GHz. For example, each of FR4a, FR4-1, FR4, and FR5 falls within the EHF band. In some examples, the wireless communication network 100 can implement dynamic spectrum sharing (DSS), where multiple RATs (e.g., 4G / LTE and 5G / NR) are implemented within a single frequency band using dynamic bandwidth allocation (e.g., based on user demand). It is conceivable that the frequencies included in these operating bands (e.g., FR1, FR2, FR3, FR4, FR4-a, FR4-1 and / or FR5) can be modified, and the techniques described herein are applicable to those modified frequency ranges.
[0037] Network node 110 may include one or more devices, components, or systems that enable communication between UE 120 and one or more devices, components, or systems of wireless communication network 100. Network node 110 may be, may include, or may also be referred to as an NR network node, 5G network node, 6G network node, node B, eNB, gNB, access point (AP), transmit / receive point (TRP), mobility element, core, network entity, network element, network equipment, and / or another type of device, component, or system included in a radio access network (RAN).
[0038] Network node 110 may be implemented as a single physical node (e.g., a single physical structure) or as two or more physical nodes (e.g., two or more different physical structures). For example, network node 110 may be a device or system implementing a portion of a radio protocol stack, a device or system implementing a complete radio protocol stack (such as a complete gNB protocol stack), or a collection of devices or systems collectively implementing a complete radio protocol stack. For example, and as shown, network node 110 may be an aggregated network node (with an aggregated architecture), meaning that network node 110 can implement a complete radio protocol stack physically and logically integrated within a single node (e.g., a single physical structure) in the wireless communication network 100. For example, aggregated network node 110 may consist of a single standalone base station or a single TRP that uses a complete radio protocol stack to implement or facilitate communication between UE 120 and the core network of wireless communication network 100.
[0039] Alternatively, and also as shown in the figure, network node 110 can be a decomposed network node (sometimes referred to as a decomposed base station), meaning that network node 110 can realize a radio protocol stack that is physically distributed and / or logically distributed among two or more nodes in the same or different geographic locations. For example, a decomposed network node may have a decomposed architecture. In some deployments, decomposed network node 110 may be used in integrated access and backhaul (IAB) networks, in open radio access networks (O-RAN) (such as network configurations compliant with the O-RAN Alliance), or in virtualized radio access networks (vRAN) (also referred to as cloud radio access networks (C-RAN)) to facilitate scaling by decomposing base station functionality into multiple units that can be deployed independently.
[0040] Network nodes 110 of the wireless communication network 100 may include one or more central units (CUs), one or more distributed units (DUs), and / or one or more radio units (RUs). CUs may host one or more higher-layer control functions, such as Radio Resource Control (RRC) functions, Packet Data Convergence Protocol (PDCP) functions, and / or Service Data Adaptation Protocol (SDAP) functions, etc. DUs may host one or more of the Radio Link Control (RLC) layer, Media Access Control (MAC) layer, and / or one or more higher physical (PHY) layers, at least in part, according to functional splits (such as functional splits defined by 3GPP). In some examples, DUs may also host one or more lower PHY layer functions, such as Fast Fourier Transform (FFT), Inverse FFT (iFFT), beamforming, Physical Random Access Channel (PRACH) extraction and filtering, and / or scheduling of resources for one or more UEs 120, etc. RUs may host RF processing functions or lower PHY layer functions, such as FFT, iFFT, beamforming, or PRACH extraction and filtering, etc., according to functional splits (such as lower-layer functional splits). In this type of architecture, each RU can be operated to handle over-the-air (OTA) communications with one or more UE 120s.
[0041] In some aspects, a single network node 110 may include a combination of one or more CUs, one or more DUs, and / or one or more RUs. Additionally or alternatively, network node 110 may include one or more near real-time (near RT) RAN Intelligent Controllers (RICs) and / or one or more non-real-time (non-RT) RICs. In some examples, CUs, DUs, and / or RUs may be implemented as virtual units, such as Virtual Central Units (VCUs), Virtual Distributed Units (VDUs), or Virtual Radio Units (VRUs), etc. Virtual units may be implemented as virtual network functions, such as those associated with cloud deployments.
[0042] Some network nodes 110 (e.g., base stations, RUs, or TRPs) can provide communication coverage for a specific geographic area. In 3GPP, the term "cell" can refer to the coverage area of network node 110 or to network node 110 itself, depending on the context in which the term is used. Network node 110 can support one or more (e.g., three) cells. In some examples, network node 110 can provide communication coverage for macro cells, pico cells, femto cells, or another type of cell. A macro cell can cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access by UE 120 with a service subscription. A pico cell can cover a relatively small geographic area and can allow unrestricted access by UE 120 with a service subscription. A femto cell can cover a relatively small geographic area (e.g., a residential area) and can allow restricted access by UE 120 associated with that femto cell (e.g., UE 120 in a Closed Subscriber Group (CSG)). The network node 110 used for a macro cell can be referred to as a macro network node. Network node 110 used for a picocell may be referred to as a pico network node. Network node 110 used for a femtocell may be referred to as a femto network node or a home network node. In some examples, the cell may not necessarily be stationary. For example, the geographical area of the cell may move depending on the location of the associated mobile network node 110 (e.g., a train, satellite base station, drone, or NTN network node).
[0043] The wireless communication network 100 can be a heterogeneous network, comprising different types of network nodes 110, such as macro network nodes, piconet nodes, femtonet nodes, relay network nodes, aggregation network nodes, and / or decomposition network nodes, etc. Figure 1 In the example shown, network node 110a can be a macro network node for macro cell 130a, network node 110b can be a pico network node for pico cell 130b, and network node 110c can be a femto network node for femto cell 130c. Compared to other types of network nodes 110, the various types of network nodes 110 typically transmit at different power levels, serve different coverage areas, and / or have different effects on interference in the wireless communication network 100. For example, macro network nodes may have high transmit power levels (e.g., 5 watts to 40 watts), while pico network nodes, femto network nodes, and relay network nodes may have lower transmit power levels (e.g., 0.1 watts to 2 watts).
[0044] In some examples, network node 110 may be, may include, or operate as a RU, TRP, or base station communicating with one or more UEs 120 via a radio access link (which may be referred to as a "Uu" link). The radio access link may include a downlink and an uplink. A "downlink" (or "DL") refers to the communication direction from network node 110 to UE 120, and an "uplink" (or "UL") refers to the communication direction from UE 120 to network node 110. Downlink channels may include one or more control channels and one or more data channels. Downlink control channels may be used to transmit downlink control information (DCI) (e.g., scheduling information, reference signals, and / or configuration information) from network node 110 to UE 120. Downlink data channels may be used to transmit downlink data (e.g., user data associated with UE 120) from network node 110 to UE 120. Downlink control channels may include one or more physical downlink control channels (PDCCH), and downlink data channels may include one or more physical downlink shared channels (PDSCH). The uplink channel may similarly include one or more control channels and one or more data channels. The uplink control channel can be used to transmit uplink control information (UCI) from UE 120 to network node 110 (e.g., transmitting corresponding reference signals and / or feedback with one or more downlinks). The uplink data channel can be used to transmit uplink data (e.g., user data associated with UE 120) from UE 120 to network node 110. The uplink control channel may include one or more physical uplink control channels (PUCCH), and the uplink data channel may include one or more physical uplink shared channels (PUSCH). The downlink and uplink may each include a set of resources on which network node 110 and UE 120 can communicate.
[0045] Downlink and uplink resources may include time-domain resources (frames, subframes, time slots, and / or symbols), frequency-domain resources (bands, component carriers, subcarriers, resource blocks, and / or resource elements), and / or spatial-domain resources (specific transmission directions and / or beam parameters). Frequency-domain resources in some bands may be subdivided into bandwidth portions (BWPs). A BWP may be a contiguous block of frequency-domain resources allocated to one or more UEs 120 (e.g., a contiguous block of resource blocks). UEs 120 may be configured using both uplink and downlink BWPs (where the uplink and downlink BWPs may be the same BWP or different BWPs). BWPs may be dynamically configured and / or reconfigured (e.g., by sending DCI configuration to one or more UEs 120 via network node 110), meaning that BWPs may be adjusted in real-time (or near real-time) based on changing network conditions in the wireless communication network 100 and / or based on the specific requirements of one or more UEs 120. This allows for more efficient use of available frequency domain resources in the wireless communication network 100, as fewer frequency domain resources can be allocated to the BWP for UE 120 (which reduces the number of frequency domain resources that UE 120 needs to monitor), thus allowing more frequency domain resources to be distributed across multiple UE 120s. Therefore, the BWP can also assist in the implementation of such UE 120s by facilitating the configuration of smaller bandwidths for communications performed by lower-capacity UE 120s.
[0046] As described above, in some aspects, the wireless communication network 100 may be an IAB network, may include an IAB network, or may be included in an IAB network. In an IAB network, at least one network node 110 is an anchor network node communicating with a core network. The anchor network node 110 may also be referred to as an IAB donor (or "IAB donor"). The anchor network node 110 may be connected to the core network via a wired backhaul link. For example, the Ng interface of the anchor network node 110 may terminate at the core network. Additionally or alternatively, the anchor network node 110 may be connected to one or more devices in the core network that provide core access and mobility management functions (AMF). An IAB network typically also includes multiple non-anchor network nodes 110, which may also be referred to as relay network nodes or simply IAB nodes (or "IAB-nodes"). Each non-anchor network node 110 can directly communicate with the anchor network node 110 via a wireless backhaul link to access the core network, or can indirectly communicate with the anchor network node 110 via one or more other non-anchor network nodes 110 and an associated wireless backhaul link forming a backhaul path to the core network. Some anchor network nodes 110 or other non-anchor network nodes 110 can also directly communicate with one or more UEs 120 via a wireless access link carrying access services. In some examples, network resources used for wireless communication (such as time resources, frequency resources, and / or spatial resources) can be shared between the access link and the backhaul link.
[0047] In some examples, any network node 110 relaying communication may be referred to as a relay network node, a relay station, or simply a repeater. A repeater may receive communications from an upstream station (e.g., another network node 110 or UE 120) and transmit communications to a downstream station (e.g., UE 120 or another network node 110). In this case, the wireless communication network 100 may include or be referred to as a "multi-hop network." Figure 1 In the example shown, network node 110d (e.g., a relay network node) can communicate with network node 110a (e.g., a macro network node) and UE 120d to facilitate communication between network node 110a and UE 120d. Additionally or alternatively, UE 120 can be a relay station capable of relaying transmissions to or from other UE 120s, or can operate as such a relay station. UE 120 relaying communication can be referred to as a UE repeater or relay UE, etc.
[0048] UE 120 may be physically distributed throughout the wireless communication network 100, and each UE 120 may be stationary or mobile. UE 120 may be, may include, an access terminal, another terminal, a mobile station, or a subscriber unit, or may be included in an access terminal, another terminal, a mobile station, or a subscriber unit. UE 120 may be, or may include, 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 computer, a camera, a gaming device, a netbook, a smartbook, an ultrabook, a medical device, a biometric device, a wearable device (e.g., a smartwatch, smart clothing, smart glasses, a smart wristband and / or smart jewelry (such as a smart ring or smart bracelet)), an entertainment device (e.g., a music device, a video device and / or a satellite radio), an XR device, a vehicle component or sensor, a smart meter or sensor, industrial manufacturing equipment, a Global Navigation Satellite System (GNSS) device (such as a Global Positioning System device or another type of positioning device), a UE function of a network node, and / or any other suitable device or function that can communicate via a wireless medium, or may be coupled to them.
[0049] UE 120 and / or network node 110 may include one or more chips, system-on-a-chip (SoC), chipsets, packages, or devices that individually or collectively constitute or include a processing system. The processing system includes processor (or “processing”) circuitry in the form of one or more processors, microprocessors, processing units (such as central processing units (CPUs), graphics processing units (GPUs), neural processing units (NPUs), and / or digital signal processors (DSPs)), processing blocks, application-specific integrated circuits (ASICs), programmable logic devices (PLDs) (such as field-programmable gate arrays (FPGAs)), or other discrete gate or transistor logic components or circuits (all of which are generally referred to herein individually as “processors” or collectively as “processors” or “processor circuitry”). One or more of these processors may be individually or collectively configured to perform the various functions or operations described herein. A processor group that can be configured or configured to perform a set of functions may include a first processor that can be configured or configured to perform a first function in the set, and a second processor that can be configured or configured to perform a second function in the set, or may include the entire processor group that is configured or configured to perform the set of functions.
[0050] The processing system may also include memory circuitry in the form of one or more memory devices, memory blocks, memory elements, or other discrete gate or transistor logic components or circuits, each of which may include tangible storage media such as random access memory (RAM) or read-only memory (ROM) or combinations thereof (all of which are generally referred to herein individually as "memory" or collectively as "memory" or "memory circuitry"). One or more of these memories may be coupled to one or more processors in the processor (e.g., operatively coupled, communicatively coupled, electronically coupled, or electrically coupled) and may store processor-executable code (such as software) individually or collectively, which, when executed by one or more processors in the processor, may configure one or more processors in the processor to perform the various functions or operations described herein. Additionally or alternatively, in some examples, one or more processors in the processor may be pre-configured to perform the various functions or operations described herein without being configured by software. The processing system may also include or be coupled to one or more modems (such as Wi-Fi (e.g., IEEE compliant) modems or cellular (e.g., 3GPP 4G LTE, 5G, or 6G compliant) modems). In some embodiments, one or more processors of the processing system include or implement one or more modems among the modems. The processing system may also include, or be coupled to, multiple radio components (collectively, “radio components”), multiple RF chains, or multiple transceivers, each of which may in turn be coupled to one or more antennas among multiple antennas. In some embodiments, one or more processors of the processing system include or implement one or more of the radio components, RF chains, or transceivers. UE 120 may be included or may be contained in a housing that houses components associated with UE 120, including the processing system.
[0051] Some UEs 120 may be considered Machine Type Communication (MTC) UEs, Evolved or Enhanced Machine Type Communication (eMTC) UEs, Further Enhanced eMTC (feMTC) UEs, or Enhanced feMTC (efeMTC) UEs, or further evolutions thereof, all of which may be referred to simply as "MTC UEs". MTC UEs may be, may include, or may be included in or coupled with the following: robots, unmanned aerial vehicles, remote devices, sensors, instruments, monitors, and / or location tags. Some UEs 120 may be considered IoT devices and / or may be implemented as NB-IoT (Narrowband IoT) devices. IoT UEs or NB-IoT devices may be, may include, or may be included in or coupled with the following: industrial machines, appliances, refrigerators, doorbell camera devices, home automation devices, and / or lighting fixtures, etc. Some UEs 120 may be considered customer premises equipment, which may include telecommunications equipment installed at a customer location (such as a home or office) to enable access to a service provider’s network (such as being included in or communicating with the wireless communication network 100).
[0052] Some UEs 120 can be categorized according to different categories associated with varying levels of complexity and / or capabilities. UEs 120 in the first category facilitate large-scale IoT within the wireless communication network 100 and offer lower complexity and / or lower cost compared to UEs 120 in the second category. UEs 120 in the second category may include mission-critical IoT devices capable of URLLC, enhanced mobile broadband (eMBB), and / or precise positioning within the wireless communication network 100, legacy UEs, baseline UEs, high-level UEs, advanced UEs, full-capability UEs, and / or premium UEs. UEs 120 in the third category may have intermediate-level complexity and / or capabilities (e.g., capabilities between those of UEs 120 in the first category and those of UEs 120 in the second category). UEs 120 in the third category may be referred to as reduced-capability UEs (“RedCap UEs”), intermediate-level UEs, NR lightweight UEs, and / or NR simplified UEs, etc. RedCap UEs bridge the gap in capabilities and complexity between NB-IoT devices and / or eMTC UEs and mission-critical IoT devices and / or premium UEs. RedCap UEs can include, for example, wearable devices, IoT devices, industrial sensors, and / or cameras associated with limited bandwidth, power capacity, and / or transmission range. RedCap UEs can support healthcare environments, building automation, power distribution, process automation, transportation and logistics, and / or smart city deployments, among others.
[0053] In some examples, two or more UEs 120 (e.g., shown as UE 120a and UE 120e) can communicate directly with each other using sidelink communication (e.g., without communication through a network node 110 acting as an intermediary). As an example, UE 120a can directly send data, control information, or other signaling to UE 120e as sidelink communication. This contrasts with, for example, UE 120a first sending data to network node 110 in UL communication, and then that network node sending data to UE 120e in DL communication. In various examples, UE 120 can use peer-to-peer (P2P) communication protocols, device-to-device (D2D) communication protocols, vehicle-to-everything (V2X) communication protocols (which may include vehicle-to-vehicle (V2V) protocols, vehicle-to-infrastructure (V2I) protocols, and / or vehicle-to-pedestrian (V2P) protocols), and / or mesh network communication protocols to send and receive sidelink communication. In some deployments and configurations, network node 110 may schedule and / or allocate resources for sidelink communication between UEs 120 in the wireless communication network 100. In some other deployments and configurations, UE 120 (instead of network node 110) may perform or cooperate with or negotiate with one or more other UEs to perform scheduling operations, resource selection operations, and / or other operations for sidelink communication.
[0054] In various examples, in addition to half-duplex operation, some network nodes and UEs in the wireless communication network 100, including network node 110 and UE 120, can also be configured for full-duplex operation. Network node 110 or UE 120 operating in half-duplex mode can perform only one of transmission or reception during a specific time resource period (such as a specific time slot, symbol, or other time period). Half-duplex operation may involve time division duplex (TDD), where the DL transmission of network node 110 and the UL transmission of UE 120 do not occur in the same time resource (i.e., the transmissions do not overlap in time). In contrast, network node 110 or UE 120 operating in full-duplex mode can transmit and receive communications concurrently (e.g., within the same time resource). By operating in full-duplex mode, network node 110 and / or UE 120 can generally increase the capacity of the network and radio access links. In some examples, full-duplex operation may involve frequency division duplex (FDD), in which network node 110 performs DL transmission in a first frequency band or on a first component carrier, and UE 120 performs transmission in a second frequency band or on a second component carrier, the second frequency band or the second component carrier being different from the first frequency band or the first component carrier, respectively. In some examples, full-duplex operation may be enabled for UE 120 but not for network node 110. For example, UE 120 may simultaneously transmit UL to the first network node 110 and receive DL transmissions from the second network node 110 in the same time resources. In some other examples, full-duplex operation may be enabled for network node 110 but not for UE 120. For example, network node 110 may simultaneously transmit DL to the first UE 120 and receive UL transmissions from the second UE 120 in the same time resources. In some other examples, full-duplex operation may be enabled for both network node 110 and UE 120.
[0055] In some examples, UE 120 and network node 110 can perform MIMO communication. "MIMO" generally refers to the simultaneous transmission or reception of multiple signals (such as multiple layers or multiple data streams) using the same time and frequency resources. MIMO techniques typically utilize multipath propagation. MIMO can be implemented using various spatial processing or spatial multiplexing operations. In some examples, MIMO can support simultaneous transmission to multiple receivers, which is called multi-user MIMO (MU-MIMO). Some RATs can employ advanced MIMO techniques such as mTRP operations (including redundant transmission or reception on multiple TRPs), reciprocity in the time or frequency domain, single-frequency network (SFN) transmission, or noncoherent joint transmission (NC-JT).
[0056] In some aspects, the first UE (e.g., UE 120a) may include a communication manager 140. As described in more detail elsewhere herein, the communication manager 140 may be identified by the modem of the first UE as a recommended service split between a first connection associated with the first UE and a second connection associated with the second UE (e.g., UE 120e); and may be provided by the modem using a cross-layer API to provide auxiliary information indicating the recommended service split. Additionally or alternatively, the communication manager 140 may perform one or more other operations described herein.
[0057] As indicated above, Figure 1 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 1 The examples described are different.
[0058] Figure 2 This is a diagram illustrating communication between an example network node 110 and an example UE 120 in a wireless network according to the present disclosure.
[0059] like Figure 2 As shown, network node 110 may include a data source 212, a transmit processor 214, a transmit (TX) MIMO processor 216, a set of modems 232 (shown as 232a to 232t, where t ≥ 1), a set of antennas 234 (shown as 234a to 234v, where v ≥ 1), a MIMO detector 236, a receive processor 238, a data sink 239, a controller / processor 240, a memory 242, a communication unit 244, and / or a scheduler 246, etc. In some configurations, one or a combination of antennas 234, modems 232, MIMO detectors 236, receive processors 238, transmit processors 214, and / or TX MIMO processors 216 may be included in the transceiver of network node 110. The transceiver may be under the control of and used by one or more processors (such as controller / processor 240), and in some respects, performs aspects of the methods, processes, and / or operations described herein in conjunction with processor-readable code stored in memory 242. In some respects, network node 110 may include one or more interfaces, communication components and / or other components that facilitate communication with UE 120 or another network node.
[0060] The terms “processor,” “controller,” or “controller / processor” can refer to one or more controllers and / or one or more processors. For example, references to “a / the processor,” “a / the controller / processor,” etc. (in the singular) should be understood as referring to a combination of… Figure 2The processor described refers to any one or more processors, such as a single processor or a combination of multiple different processors. The reference to "one or more processors" should be understood as a combination of references. Figure 2 Any one or more processors described herein. For example, one or more processors of network node 110 may include transmit processor 214, TX MIMO processor 216, MIMO detector 236, receive processor 238, and / or controller / processor 240. Similarly, one or more processors of UE 120 may include MIMO detector 256, receive processor 258, transmit processor 264, TX MIMO processor 266, and / or controller / processor 280.
[0061] In some aspects, a single processor can perform all operations described as being performed by one or more processors. In some aspects, a first set of one or more processors can perform a first operation described as being performed by that one or more processors, and a second set of one or more processors can perform a second operation described as being performed by that one or more processors. The processors in the first set and the processors in the second set can be from the same set of processors or can be from different sets of processors. The reference to "one or more memories" should be understood to refer to any one or more memories of the corresponding device, such as those in combination. Figure 2 The memory described. For example, an operation described as being performed by one or more memories can be performed by the same subset of the one or more memories or by different subsets of the one or more memories.
[0062] For downlink communication from network node 110 to UE 120, transmitting processor 214 may receive data (“downlink data”) intended for use by UE 120 (or a set of UEs including UE 120) from data source 212 (such as a data pipeline or data queue). In some examples, transmitting processor 214 may select one or more MCSs for UE 120 based on one or more Channel Quality Indicators (CQIs) received from UE 120. Network node 110 may process the data (e.g., including encoding the data) according to the MCS selected for UE 120 for transmission to UE 120 on the downlink, thereby generating data symbols. Transmitting processor 214 may process system information (e.g., semi-static resource partitioning information (SRPI)) and / or control information (e.g., CQI requests, grants, and / or upper-layer signaling) and provide overhead symbols and / or control symbols. The transmitting processor 214 can generate reference symbols for reference signals (e.g., cell-specific reference signals (CRS), demodulation reference signals (DMRS), or channel state information (CSI) reference signals (CSI-RS)) and / or synchronization signals (e.g., primary synchronization signal (PSS) or secondary synchronization signal (SSS)).
[0063] The TX MIMO processor 216 can perform space processing (e.g., pre-decoding) on data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., T A set of output symbol streams is provided to modem 232. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 232. Each modem 232 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for orthogonal frequency division multiplexing (OFDM)) to obtain an output sample stream. Each modem 232 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain a time-domain downlink signal. Modems 232a to 232t may transmit the set of downlink signals (e.g., via a set of corresponding antennas 234) together. T (One downlink signal).
[0064] Downlink signals may include DCI communication, MAC control element (MAC-CE) communication, RRC communication, downlink reference signals, or another type of downlink communication. Downlink signals may be transmitted on the PDCCH, PDSCH, and / or on another downlink channel. Downlink signals may carry one or more transport blocks (TBs) of data. A TB may be a data unit transmitted via the air interface in the wireless communication network 100. A data stream (e.g., from data source 212) may be encoded into multiple TBs for transmission via the air interface. The number of TBs used to carry data associated with a particular data stream may be associated with a TB size shared by multiple TBs. The TB size may be based on the radio channel conditions of the air interface, the MCS used to encode the data, downlink resources allocated for transmitting data, and / or other parameters, or otherwise associated with them. Generally, a larger TB size allows for a larger amount of data to be transmitted in a single transmission, reducing signaling overhead. However, a larger TB size may be more prone to transmission and / or reception errors than a smaller TB size, but such errors can be mitigated through more robust error correction techniques.
[0065] For uplink communication from UE 120 to network node 110, the uplink signal from UE 120 may be received by antenna 234, processed by modem 232 (e.g., demodulator component of modem 232, shown as DEMOD), detected where applicable by MIMO detector 236 (e.g., receive (Rx) MIMO processor), and / or further processed by receive processor 238 to obtain decoded data and / or control information. Receive processor 238 may provide the decoded data to data sink 239 (which may be a data pipeline, data queue, and / or another type of data sink) and provide the decoded control information to processors such as controller / processor 240.
[0066] Network node 110 may use scheduler 246 to schedule one or more UEs 120 for downlink or uplink communication. In some aspects, scheduler 246 may use DCI to dynamically schedule DL transmissions to and / or UL transmissions from UE 120. In some examples, scheduler 246 may allocate repetitive time-domain and / or frequency-domain resources that UE 120 may use to transmit and / or receive communication using RRC configuration (e.g., semi-static configuration), for example, to perform semi-persistent scheduling (SPS) or to configure configuration grant (CG) for UE 120.
[0067] One or more of the following may be included in the RF chain of network node 110: transmit processor 214, TX MIMO processor 216, modem 232, antenna 234, MIMO detector 236, receive processor 238, and / or controller / processor 240. The RF chain may include one or more filters, mixers, oscillators, amplifiers, analog-to-digital converters (ADCs), and / or other devices for converting analog signals (such as those used for transmission or reception via an air interface) to digital signals (such as those used for processing by one or more processors of network node 110). In some aspects, the RF chain may be a transceiver of network node 110, or may be included in such a transceiver.
[0068] In some examples, network node 110 may use communication unit 244 to communicate with the core network and / or other network nodes. Communication unit 244 may support wired and / or wireless communication protocols and / or connections, such as Ethernet, fiber optic, Common Public Radio Interface (CPRI), and / or wired or wireless backhaul, etc. Network node 110 may use communication unit 244 to send and / or receive data associated with UE 120, or to perform network control signaling, etc. Communication unit 244 may include transceivers and / or interfaces, such as network interfaces.
[0069] UE 120 may include a collection of antennas 252 (shown as antennas 252a to 252r, where r ≥ 1), a collection of modems 254 (shown as modems 254a to 254u, where u ≥ 1), a MIMO detector 256, a receive processor 258, a data sink 260, a data source 262, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, a memory 282, and / or a communication manager 140, etc. One or more components of UE 120 may be included in housing 284. In some aspects, one or a combination of antenna 252, modem 254, MIMO detector 256, receive processor 258, transmit processor 264, or TX MIMO processor 266 may be included in a transceiver included in UE 120. The transceiver may be under the control of and used by one or more processors (such as controller / processor 280), and in some respects, may perform aspects of the methods, procedures, or operations described herein in conjunction with processor-readable code stored in memory 282. In some respects, UE 120 may include another interface, another communication component, and / or another component that facilitates communication with network node 110 and / or another UE 120.
[0070] For downlink communication from network node 110 to UE 120, the set of antennas 252 can receive downlink communication or signals from network node 110, and can receive the set of downlink signals (e.g., R Each received signal is provided to a set of modems 254. For example, each received signal may be provided to a corresponding demodulator component (shown as DEMOD) of modem 254. Each modem 254 may use the corresponding demodulator component to condition (e.g., filter, amplify, down-convert, and / or digitize) the received signal to obtain an input sample. Each modem 254 may use the corresponding demodulator component to further demodulate or process the input sample (e.g., for OFDM) to obtain a received symbol. MIMO detector 256 may obtain the received symbols from the set of modems 254, perform MIMO detection on the received symbols where applicable, and provide the detected symbols. Receiver processor 258 may process (e.g., decode) the detected symbols, provide the decoded data for UE 120 to data sink 260 (which may include data pipelines, data queues, and / or applications executed on UE 120), and provide the decoded control information and system information to controller / processor 280.
[0071] For uplink communication from UE 120 to network node 110, the transmitting processor 264 may receive and process data (“uplink data”) from data source 262 (such as data pipelines, data queues, and / or applications running on UE 120) and control information from controller / processor 280. The control information may include one or more parameters, feedback, one or more signal measurements, and / or other types of control information. In some aspects, the receiving processor 258 and / or controller / processor 280 may determine one or more parameters related to the transmission of uplink communication for received signals (such as those received from network node 110 or another UE). One or more parameters may include a Reference Signal Received Power (RSRP) parameter, a Received Signal Strength Indicator (RSSI) parameter, a Reference Signal Received Quality (RSRQ) parameter, a CQI parameter, or a Transmit Power Control (TPC) parameter, etc. The control information may include indications of the RSRP parameter, RSSI parameter, RSRQ parameter, CQI parameter, TPC parameter, and / or another parameter. Control information can facilitate parameter selection and / or scheduling for UE 120 by network node 110.
[0072] Transmit processor 264 can generate reference symbols for one or more reference signals, such as uplink DMRS, uplink sounding reference signal (SRS), and / or another type of reference signal. Symbols from transmit processor 264 can be pre-decoded by TX MIMO processor 266 where applicable, and further processed by a set of modems 254 (e.g., for DFT-s-OFDM or CP-OFDM). TX MIMO processor 266 can perform spatial processing (e.g., pre-decoding) on data symbols, control symbols, overhead symbols, and / or reference symbols where applicable, and can output a set of symbol streams (e.g., ... U A set of output symbol streams is provided to modem 254. For example, each output symbol stream may be provided to a corresponding modulator component (shown as MOD) of modem 254. Each modem 254 may use the corresponding modulator component to process (e.g., modulate) the corresponding output symbol stream (e.g., for OFDM) to obtain an output sample stream. Each modem 254 may further use the corresponding modulator component to process (e.g., convert to analog, amplify, filter, and / or upconvert) the output sample stream to obtain an uplink signal.
[0073] Modems 254a to 254u can transmit uplink signal sets (e.g., via a set of corresponding antennas 252) R One uplink signal or U Uplink signals may include UCI communication, MAC-CE communication, RRC communication, or another type of uplink communication. Uplink signals may be transmitted on PUSCH, PUCCH, and / or another type of uplink channel. Uplink signals may carry one or more TBs of data. Sidelink data and control transmission (i.e., transmission directly between two or more UEs 120) may typically use techniques similar to those described for uplink data and control transmission, and may use sidelink-specific channels such as the Physical Sidelink Shared Channel (PSSCH), Physical Sidelink Control Channel (PSCCH), and / or Physical Sidelink Feedback Channel (PSFCH).
[0074] One or more antennas in the set of antennas 252 or the set of antennas 234 may include one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc., or may be included in one or more antenna panels, one or more antenna groups, one or more sets of antenna elements, or one or more antenna arrays, etc. Antenna panels, antenna groups, sets of antenna elements, or antenna arrays may include one or more antenna elements (within a single housing or multiple housings), a set of coplanar antenna elements, a set of non-coplanar antenna elements, or with one or more transmitting or receiving components (such as...) Figure 2 An antenna module is a combination of one or more antenna elements coupled to one or more components. As used herein, "antenna" can mean one or more antennas, one or more antenna panels, one or more antenna groups, one or more collections of antenna elements, or one or more antenna arrays. "Antenna panel" can mean a group of antennas (such as antenna elements) arranged in an array or panel that can facilitate beamforming by manipulating the parameters of that group of antennas. "Antenna module" can mean a circuit that includes one or more antennas, and may also include one or more other components (such as filters, amplifiers, or processors) associated with integrating the antenna module into a wireless communication device.
[0075] In some examples, each antenna element of antenna 234 or antenna 252 may include one or more sub-elements for radiating or receiving radio frequency signals. For example, a single antenna element may include a first sub-element cross-polarized with a second sub-element that can be used to independently transmit cross-polarized signals. Antenna elements may include patch antennas, dipole antennas, and / or other types of antennas arranged in a linear pattern, a two-dimensional pattern, or another pattern. The spacing between antenna elements can allow signals with a desired wavelength transmitted individually by the antenna elements to interact or interfere (e.g., to form a desired beam) in various directions. For example, given a desired wavelength or frequency range, the spacing may provide a quarter wavelength, half a wavelength, or another fraction of the wavelength between adjacent antenna elements to allow desired constructive and destructive interference modes of signals transmitted by individual antenna elements within that desired range.
[0076] The amplitude and / or phase of signals transmitted via antenna elements and / or sub-elements can be modulated and (e.g., by manipulating phase shifts, phase offsets, and / or amplitudes) shifted relative to each other to generate one or more beams; this is known as beamforming. The term "beam" can refer to the directional transmission of a wireless signal toward a receiving device or otherwise in a desired direction. "Beam" can also generally refer to the direction associated with such directional signal transmission, the set of directional resources associated with the signal transmission (e.g., angle of arrival, horizontal direction, and / or vertical direction), and / or a set of parameters indicating one or more aspects of the directional signal, the direction associated with the signal, and / or the set of directional resources associated with the signal. In some implementations, antenna elements can be individually selected or deselected for the directional transmission of a signal (or multiple signals) by controlling the amplitude of one or more corresponding amplifiers and / or the phase of the signal to form one or more beams. The shape of the beam (such as amplitude, width, and / or the presence of sidelobes) and / or the direction of the beam (such as the angle of the beam relative to the surface of the antenna array) can be dynamically controlled by modifying the phase shifts, phase offsets, and / or amplitudes of multiple signals relative to each other.
[0077] Different UEs 120 or network nodes 110 may include different numbers of antenna elements. For example, UE 120 may include a single antenna element, two antenna elements, four antenna elements, eight antenna elements, or different numbers of antenna elements. As another example, network node 110 may include eight antenna elements, 24 antenna elements, 64 antenna elements, 128 antenna elements, or different numbers of antenna elements. Generally speaking, a larger number of antenna elements provides increased control over the parameters used for beamforming compared to a smaller number of antenna elements, while a smaller number of antenna elements may be less complex to implement and can use less power. Multiple antenna elements can support multi-layer transmission, in which the same time and frequency resources are used to utilize spatial multiplexing to transmit a first layer of communication (which may include a first data stream) and a second layer of communication (which may include a second data stream).
[0078] Although Figure 2 The boxes in the diagram are illustrated as different components, but the functions described above with respect to these boxes may be implemented in a single hardware, software, or combined component, or in various combinations of components. For example, the functions described with respect to transmit processor 264, receive processor 258, and / or TX MIMO processor 266 may be performed by or under the control of controller / processor 280.
[0079] As indicated above, Figure 2 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 2 The examples described are different.
[0080] Figure 3 This is an illustration of an example decomposed base station architecture 300 according to the present disclosure. One or more components of the example decomposed base station architecture 300 may be, may include, or may be included in one or more network nodes (such as one or more network nodes 110). The decomposed base station architecture 300 may include a CU 310, which may communicate directly with the core network 320 via a backhaul link, or may communicate indirectly with the core network 320 via one or more decomposed control units (such as non-RT RIC 350 and / or near-RT RIC 370 associated with a Service Management and Orchestration (SMO) framework 360 (e.g., via an E2 link)). The CU 310 may communicate with one or more DU 330s via a corresponding midhaul link (such as via an F1 interface). Each DU 330 may communicate with one or more RU 340s via a corresponding fronthaul link. Each RU 340 may communicate with one or more UE 120s via a corresponding RF access link. In some deployments, a UE 120 may be served simultaneously by multiple RU 340s.
[0081] Each component in the decomposed base station architecture 300 (including CU 310, DU 330, RU 340, near-RT RIC 370, non-RT RIC 350, and SMO frame 360) may include one or more interfaces or be coupled to one or more interfaces for receiving or transmitting signals, such as data or information, via wired or wireless transmission media.
[0082] In some respects, the CU 310 can be logically divided into one or more CU user plane (CU-UP) units and one or more CU control plane (CU-CP) units. When implemented in an O-RAN configuration, the CU-UP units can communicate bidirectionally with the CU-CP units via an interface such as an E1 interface. The CU 310 can be deployed to communicate with one or more DU 330s for network control and signaling, as needed. Each DU 330 may correspond to a logical unit that includes one or more base station functions for controlling the operation of one or more RU 340s. For example, the DU 330 may host various layers, such as the RLC layer, MAC layer, or one or more PHY layers (such as one or more high PHY layers or one or more low PHY layers). Each layer (which may also be referred to as a module) can be implemented using an interface for signaling to other layers (and modules) hosted by the DU 330, or for signaling to control functions hosted by the CU 310. Each RU 340 may implement lower-layer functionality. In some respects, the real-time and non-real-time aspects of communication with the control plane and user plane of the RU 340 can be controlled by the corresponding DU 330.
[0083] The SMO framework 360 supports RAN deployment and provisioning for both non-virtualized and virtualized network elements. For non-virtualized network elements, the SMO framework 360 supports the deployment of dedicated physical resources for RAN coverage requirements, which can be managed via operation and maintenance interfaces such as the O1 interface. For virtualized network elements, the SMO framework 360 can interact with cloud computing platforms such as the Open Cloud (O-Cloud) platform 390 to perform network element lifecycle management (such as instantiating virtualized network elements) via cloud computing platform interfaces such as the O2 interface. Virtualized network elements may include, but are not limited to, CU 310, DU 330, RU 340, non-RT RIC 350, and / or near-RT RIC 370. In some aspects, the SMO framework 360 can communicate with hardware aspects of the 4G RAN, 5G NR RAN, and / or 6G RAN (such as the Open eNB (O-eNB) 380) via the O1 interface. Additionally or alternatively, the SMO framework 360 can communicate directly with each of one or more RUs 340 via the corresponding O1 interface. In some deployments, this configuration enables each DU 330 and CU 310 to be implemented in a cloud-based RAN architecture, such as a vRAN architecture.
[0084] The non-RT RIC 350 may include or implement logic functions that enable non-real-time control and optimization of RAN elements and resources, including AI / ML workflows for model training and updates, and / or policy-based guidance of applications and / or features in the near-RT RIC 370. The non-RT RIC 350 may be coupled to or communicate with the near-RT RIC 370, such as via an A1 interface. The near-RT RIC 370 may include or implement logic functions that enable near real-time control and optimization of RAN elements and resources via an interface, such as an E2 interface, through data collection and actions, connecting one or more CU 310s, one or more DU 330s, and / or O-eNBs to the near-RT RIC 370.
[0085] In some aspects, to generate AI / ML models to be deployed in the near-RT RIC 370, the non-RT RIC 350 may receive parameters or external enrichment information from an external server. This information can be utilized by the near-RT RIC 370 and can be received from non-network data sources or network functions at the SMO framework 360 or the non-RT RIC 350. In some examples, the non-RT RIC 350 or near-RT RIC 370 may modulate RAN behavior or performance. For example, the non-RT RIC 350 may monitor long-term trends and patterns in performance and may employ AI / ML models to perform corrective actions via the SMO framework 360 (such as reconfiguration via the O1 interface) or via the creation of RAN management policies (such as A1 interface policies).
[0086] Figure 1 , Figure 2 or Figure 3 Network node 110, its controller / processor 240, UE 120, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with modem recommendation for traffic splitting or perform one or more operations associated with modem recommendation for traffic splitting, as described in more detail elsewhere herein. For example, network node 110's controller / processor 240, UE 120's controller / processor 280, CU 310, DU 330, RU 340, or any other component may implement one or more technologies associated with modem recommendation for traffic splitting or perform one or more operations associated with modem recommendation for traffic splitting, as described in more detail elsewhere herein. Figure 2 Any other component, CU 310, DU 330, or RU 340 may (alone or in combination with one or more other processors) perform or direct, for example... Figure 11 The operation of process 1100 or other processes as described herein. Memory 242 may store data and program code for network node 110, CU 310, DU 330, or RU 340. Memory 282 may store data and program code for UE 120. In some examples, memory 242 or memory 282 may include a non-transitory computer-readable medium storing a set of instructions (e.g., code or program code) for wireless communication. Memory 242 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). Memory 282 may include one or more memories, such as a single memory or multiple different memories (of the same or different types). For example, the set of instructions may be executed by one or more processors of network node 110, UE 120, CU 310, DU 330, or RU 340 (e.g., directly, or after compilation, transformation, or interpretation). Figure 11The process 1100 or other processes as described herein. In some examples, the execution instructions may include run instructions, transformation instructions, compilation instructions, and / or interpretation instructions, etc.
[0087] In some aspects, the first UE (e.g., UE 120a) includes components for identifying, by the modem of the first UE, a recommended traffic split between a first connection associated with the first UE and a second connection associated with the second UE (e.g., UE 120e); and / or components for the modem to provide auxiliary information indicating the recommended traffic split using a cross-layer API. Components for the first UE to perform the operations described herein may include, for example, one or more of the following: a communication manager 140, an antenna 252, a modem 254, a MIMO detector 256, a receive processor 258, a transmit processor 264, a TX MIMO processor 266, a controller / processor 280, or a memory 282.
[0088] As indicated above, Figure 3 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 3 The examples described are different.
[0089] Compared to full-capable UEs (e.g., smartphones), XR devices (such as XR glasses or other wearable devices, such as smartwatches) can be associated with a relatively small form factor. This small form factor can result in a limited number of antennas for certain frequency bands compared to full-capable UEs. For example, an XR device may not be allowed to have four receive (Rx) antennas in certain 5G bands, which is common in full-capable UEs. Instead, an XR device may be limited to two Rx antennas, and a smartwatch may be limited to a single Rx antenna. In other words, a subset of XR devices may have two or fewer Rx antennas when operating in a 100MHz bandwidth. On the other hand, full-capable UEs may be required to have at least four Rx antennas. XR devices with fewer Rx antennas than full-capable UEs may have a performance disadvantage associated with full-capable UEs.
[0090] Figure 4 This is a diagram illustrating example 400 of a companion UE and an anchor UE according to this disclosure.
[0091] like Figure 4As shown, anchor UE 402 can communicate with gNB 406 via a first Uu link. For example, anchor UE 402 can be XR glasses or a smartwatch. Anchor UE 402 can use a cellular antenna to communicate with gNB 406. Accompanying UE 404 can communicate with gNB 406 via a second Uu link. For example, accompanying UE 404 can be a smartphone. Accompanying UE 404 can use a cellular antenna to communicate with gNB 406. Accompanying UE 404 can be a Layer 2 (L2) or Layer 3 (L3) multipath relay UE (or relay UE). Accompanying UE 404 can provide data forwarding to anchor UE 402 at L3 or higher. Anchor UE 402 and accompanying UE 404 can communicate with each other via a link. This link can support ultra-wideband (UWB) based data communication, PC5 NR sidelink communication (e.g., licensed or unlicensed communication), WiFi communication, Bluetooth communication, or FR2-based communication. The link can be a low-power, high-bandwidth, low-latency, and high-reliability cooperative link. For example, anchor UE 402 and companion UE 404 can each use a sidelink modem that allows communication between anchor UE 402 and companion UE 404. Anchor UE 402 and companion UE 404 can be aggregated into a virtual UE to maximize MIMO gain and allow path switching or splitting. As an example, anchor UE 402 (e.g., augmented reality (AR) glasses or wearable device) can have one or two Rx antennas, and by using cooperation with companion UE 404, a virtual UE with four or more Rx antennas can be formed.
[0092] As indicated above, Figure 4 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 4 The examples described are different.
[0093] Figure 5 This is a diagram illustrating an example 500 of a multipath relay system according to the present disclosure. Example 500 includes a anchor UE 502, a relay UE 504, a gNB 506, an application client 508, an application server 510, and a UPF 512. The application client 508 may run on the anchor UE 502.
[0094] like Figure 5As shown, the UDP layer of application client 508 can identify packets. For example, the packet may be associated with an XR service. The UDP layer can split the packet. The first part of the packet can be provided to the SDAP layer of anchor UE 502. The second part of the packet can be provided to the non-3GPP layer of anchor UE 502. The first part of the packet can be sent from anchor UE 502 to gNB 506 via relay UE 504. The first SDAP layer of gNB 506 can provide the first part of the packet to UPF 512. UPF 512 can be associated with ATSSS functionality. The second part of the packet can be sent from anchor UE 502 to gNB 506 via relay UE 504. The second SDAP layer of gNB 506 can provide the second part of the packet to UPF 512. UPF 512 can aggregate the first part and the second part of the packet to form an aggregated packet, and the aggregated packet can be provided to application server 510.
[0095] like Figure 5 As shown, relay UE 504 can be supported using ATSSS at both application client 508 and UPF 512, which allows packets to be split / aggregated between two paths. Splitting and aggregation, located at anchor UE 502 and UPF 512 respectively, can occur below the IP layer. In other words, using ATSSS, UPF 512 and anchor UE 502 can perform service bootstrapping, handover, and / or splitting below the IP layer. Traffic in a data flow can be split across multiple access networks. Certain traffic in a data flow can be delivered via one access network, and other traffic in the same data flow can be delivered via another access network. Anchor UE 502 can use ATSSS rules and location conditions to determine how to split uplink traffic. Similarly, UPF 512 can use rules and / or feedback from the UE to split downlink traffic. In the uplink, IP packet aggregation can be located at UPF 512.
[0096] Using the ATSSS solution, anchor UE 502 can provide UE assistance information to UPF 512. Anchor UE 502 can provide downlink service allocation to UPF 512 via the UE assistance information, which can then be applied by UPF 512 to downlink services. The UE assistance information can inform UPF 512 how to change the default uplink allocation method. In other words, the UE assistance information can be applied to either downlink or uplink services.
[0097] As indicated above, Figure 5 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 5 The examples described are different.
[0098] Figure 6This is a diagram illustrating example 600 of a multipath relay system according to the present disclosure. Example 600 includes anchor UE 602, relay UE 604, gNB 606, application client 608, application server 610, and UPF 612. Application client 608 may run on anchor UE 602.
[0099] like Figure 6 As shown, the application client 608 can identify packets. For example, the packet may be associated with an XR service. The application can provide the packet to an MPQUIC, which can split the packet. A first portion of the packet can be provided to a first UDP layer of the application client 608, and a second portion of the packet can be provided to a second UDP layer of the application client 608. The first portion of the packet can be transmitted from anchor UE 602 to gNB 606 via relay UE 604. The second portion of the packet can be transmitted from anchor UE 602 to gNB 606 via relay UE 604. The first portion of the packet can be received at the UDP layer of the application server 610. The second portion of the packet can be received at the UDP layer of the application server 610. The MPQUIC at the application server 610 can aggregate the first and second portions of the packet to form an aggregated packet, and the aggregated packet can be provided to the application running on the application server 610.
[0100] like Figure 6 As shown, relay UE 604 can be supported using over-the-top-above-IP aggregation. Aggregation and splitting, located at application server 610 and application client 608 respectively, can reside above the IP layer, which can be implemented using over-the-top MPQUIC or Multipath Transmission Control Protocol (MPTCP) proxies. Separate Packet Data Unit (PDU) sessions can be formed for anchor UE 602 and relay UE 604. In the uplink, aggregation of packets from different links can occur at application server 610, and packet splitting can occur at application client 608.
[0101] As indicated above, Figure 6 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 6 The examples described are different.
[0102] Figure 7 This is an illustration of example 700 of a synchronization requirement for multimodal use according to the present disclosure.
[0103] Synchronization requirements can be specified for multimodal scenarios. Audio, visual, and haptic streams can have different periodicities. Synchronization requirements can be specified between two streams (e.g., audio and haptic, or video and haptic). For an audio-haptic scenario, the synchronization threshold for audio delay can be approximately 50 ms, and the synchronization threshold for haptic delay can be approximately 25 ms. For a visual-haptic scenario, as shown by reference numeral 702, the synchronization threshold for visual delay can be approximately 15 ms, and as shown by reference numeral 704, the synchronization threshold for haptic delay can be approximately 50 ms. For each media component, "delay" can refer to the situation where that media component is delayed relative to another media component.
[0104] As indicated above, Figure 7 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 7 The examples described are different.
[0105] In various aspects of the technologies and apparatus described herein, when transport layer splitting or aggregation resides above the IP layer in the anchor UE or application server, the modem of the anchor UE can provide auxiliary information to the anchor UE's MPQUIC-aware application, the anchor UE's application client, and / or the application server. The modem can provide auxiliary information using cross-layer APIs for the MPQUIC-aware application and / or for the application client. The auxiliary information can recommend splitting or load balancing between two connections, where the first connection may be associated with the anchor node and the second connection may be associated with a relay node. The splitting or load balancing recommendation can be used for uplink or downlink traffic. The modem can provide suggestions or assistance regarding uplink traffic splitting via the cross-layer API for the MPQUIC-aware application. Alternatively, the modem can provide suggestions or assistance regarding downlink traffic splitting via the cross-layer API for the application client, and the application can forward the suggestions or assistance to the application server. The application can determine whether to implement the recommended downlink traffic splitting.
[0106] Figure 8 This is a diagram illustrating an example 800 associated with a modem recommendation for service splitting according to this disclosure. Example 800 includes an anchor UE 802, a relay UE 804, a gNB 806, an application client 808, an application server 810, and a UPF 812. The application client 808 may run on the anchor UE 802. The anchor UE 802 may include the application client 808, an MPQUIC or MPTCP aware application, a UDP layer, an IP layer, and one or more modems, such as a sidelink modem and a Uu modem. The application server 810 may include an application, an MPQUIC or MPTCP aware application, a UDP layer, and an IP layer. Although Figure 8An example of packet splitting located above the IP layer of application server 810 (e.g., at the MPQUIC layer) is shown, but Figure 8 The illustrated architecture can be used for the aggregation of packets located above the IP layer.
[0107] Figure 8 Examples of downlink adaptive load balancing based on some aspects described herein are illustrated. In downlink load balancing, anchor UE 802 may recommend the use of MPQUIC or MPTCP-aware applications to split packets of the same Service Data Flow (SDF) or different SDFs over two connections above the IP layer, as described in more detail below. In some aspects, as indicated by reference numeral 814, the modem of anchor UE 802 (e.g., a sidelink modem and / or a Uu modem) may use signaling to provide auxiliary information. For example, the modem may use cross-layer APIs for MPQUIC / MPTCP-aware application layers and / or cross-layer APIs for application client 808 to provide auxiliary information about link conditions for various connections to / from anchor UE 802. As indicated by reference numeral 816, application client 808 may signal the auxiliary information received from the modem of anchor UE 802 to application server 810. Application server 810 may perform downlink adaptive load balancing based on the auxiliary information.
[0108] As a specific example, link conditions may include a first link condition associated with anchor UE 802 and a second link condition associated with relay UE 804. The first link condition may be a condition of anchor UE 802. The second link condition may be a condition of relay UE 804. Connections to / from anchor UE 802 may include a first connection and a second connection. The first connection may be between anchor UE 802, relay UE 804, gNB 806, UPF 812, and application server 810. The second connection may be between anchor UE 802, gNB 806, UPF 812, and application server 810.
[0109] In some examples, cross-layer APIs for MPQUIC / MPTCP aware applications and / or for application client 808 can be used to provide recommendations or information about sidelinks. For instance, the modem at anchor UE 802 can provide recommendations or assistance regarding uplink traffic splitting via cross-layer APIs for MPQUIC / MPTCP aware applications and / or for application client 808. Application client 808 or the MPQUIC / MPTCP aware application can then correspondingly provide recommended downlink traffic splitting to application server 810 at 816.
[0110] In this manner, in downlink adaptive load balancing, the modem (or multiple modems of the anchor UE 802) can recommend splitting or load balancing between two connections by providing auxiliary information about the conditions of the two links. For example, the modem of the anchor UE 802 can provide recommendations for downlink splitting between two connections. The modem of the anchor UE 802 can transmit this auxiliary information to the application client 808 via a cross-layer API for MPQUIC / MPTCP aware applications and / or a cross-layer API for the application client 808. The application client 808 can forward the auxiliary information to the application server 810 (e.g., via in-band signaling). In this case, downlink adaptive load balancing can be implemented using signaling from the application client 808 to the application server 810.
[0111] Figure 8 The illustrated architecture can be additionally or alternatively used for uplink adaptive load balancing. For example, in uplink adaptive load balancing, the splitting or load balancing of packets with the same SDF or different SDFs can be based at least in part on a recommendation from anchor UE 802. The modem of anchor UE 802 (or multiple modems of anchor UE 802) can provide the recommendation for splitting or load balancing to application client 808. The modem of anchor UE 802 can provide this recommendation using a cross-layer API for MPQUIC / MPTCP aware applications (e.g., a dedicated API for MPQUIC / MPTCP aware applications). The modem of anchor UE 802 can consider its own radio link conditions, the radio link conditions of relay UE 804, and / or UE-to-UE link conditions. The radio link conditions of anchor UE 802 can correspond to a radio link and can indicate the associated throughput (e.g., bandwidth) and latency. The radio link conditions of relay UE 804 can correspond to a mating link and can indicate the associated throughput and latency. The UE-to-UE link conditions can correspond to the link between anchor UE 802 and relay UE 804, and can indicate the associated throughput and latency. In this example, the modem of anchor UE 802 can provide suggestions or assistance regarding uplink traffic splitting through a cross-layer API for MPQUIC / MPTCP aware applications, and the MPQUIC / MPTCP aware applications can split uplink traffic accordingly.
[0112] As described herein, application client 808 may reside at anchor UE 802. By using a cross-layer API for application client 808, the modem of anchor UE 802 can provide application client 808 with auxiliary information for load balancing across various connections (e.g., two connections). The auxiliary information provided by the modem of anchor UE 802 may include information about direct link conditions, indirect link conditions, and / or side link conditions. The cross-layer API for MPQUIC / MPTCP aware applications can implement the auxiliary information as is or with some modifications. The modem of anchor UE 802 can provide uplink traffic allocation to application client 808 or directly to the operating system, which can be applied by the application client through MPQUIC (via the API) to the uplink traffic applicable to the auxiliary information. In other words, by using the cross-layer API, the modem of anchor UE 802 can provide suggestions or assistance regarding uplink traffic splitting, and then application client 808 can split traffic between two connections via a dedicated MPQUIC / MPTCP aware application. The modem of anchor UE 802 can determine, at least in part, how to allocate uplink traffic matching SDF based on its own link conditions and the link conditions of the relay UE. Auxiliary information may be information associated with the link conditions of the two connections and / or the link conditions of the UE-to-UE connection, latency status reports, bandwidth, and / or throughput.
[0113] In some respects, and as described herein, the modem of anchor UE 802 can provide signaling to application client 808, and application client 808 can provide signaling to application server 810. For example, the modem of anchor UE 802 can provide UE assistance to application server 810, indicating downlink service allocation. Downlink service allocation can be delegated by the application server using MPQUIC / MPTCP for all downlink services applicable to UE assistance.
[0114] In some respects, when aggregation and / or splitting reside above the IP layer, rather than when aggregation and / or splitting occur in the downlink at UPF 812, and when aggregation and / or splitting at anchor UE 802 utilizes ATSSS below the IP layer, the modem of anchor UE 802 may be allowed to control load balancing and / or splitting. The modem of anchor UE 802 may be allowed to control load balancing and / or splitting at least in part based on anchor UE link conditions and trunk UE link conditions and / or sidelink conditions. Signaling to application client 808 and / or application server 810 can be transmitted via a cross-layer API. MPQUIC / MPTCP aware applications can then forward the recommendations to the operating system.
[0115] In some respects, multimodal synchronization requirements can be maintained. Multimodal can refer to two Quality of Service (QoS) streams, for which synchronization requirements must be maintained so that the end user experience does not experience asynchrony. For example, for audio and haptic QoS streams, the synchronization requirement between associated packets of the two separate streams cannot exceed 15ms. In the uplink, the anchor UE 802 implementing the application is aware of the experienced latency and can recommend splitting to the application client 808 based at least in part on the synchronization requirements and the link conditions at both the anchor UE 802 and the relay UE 804.
[0116] In some respects, signaling from the modem of anchor UE 802 to application client 808 can be achieved via a cross-layer API. Signaling from the modem of anchor UE 802 to application client 808, and then to application server 810, can be based at least in part on two options. In a first option, the signaling can be in-band signaling. In a second option, the signaling can be control plane signaling from anchor UE 802 to gNB 806, to AMF (not shown), to Session Management Function (SMF) (not shown), to Network Open Function (NEF) (not shown), and then to application server 810. Control plane signaling can include auxiliary information. Auxiliary information can indicate flow conditions, such as uplink or downlink. Auxiliary information can indicate link conditions, such as direct path and indirect path link conditions, sidelink conditions, latency and / or bandwidth. Auxiliary information can indicate suggested splits, such as suggested load balancing service descriptors. For example, control plane signaling may include auxiliary messages that include recommendations for splitting downlink traffic and / or uplink traffic, which may be used to determine policy and charging control (PCC) rules in the case of ATSSS-type aggregation at the UPF. Upon receiving the control signaling, application server 810 may respond to anchor UE 802 with an acknowledgment (e.g., acknowledging the recommended splitting).
[0117] In some respects, anchor UE 802 and trunk UE 804 can exchange information to support service splitting. This exchange can occur on the link between anchor UE 802 and trunk UE 804. In some respects, application client 808 can instruct anchor UE 802 to provide SDF (Software-Defined Function) supplementary information before the modem of anchor UE 802 provides a suggested load balancing split or guidance.
[0118] In some aspects, the modem of anchor UE 802 may provide signaling to application client 808 indicating the mapping of multimodal flows to two connections. For example, this signaling may include a suggestion that a first QoS flow travels along the first link and a second QoS flow travels along the second link. As another example, the signaling may indicate a splitting factor for the same SDF. This signaling may include a suggestion that 20% of the load travels along the first connection and the remaining 80% travels along the second connection. In the uplink direction, the signaling indication may terminate in application client 808 of anchor UE 802. In the downlink direction, application client 808 may forward the signaling indication (e.g., the suggested splitting) to application server 810. In some aspects, the modem of anchor UE 802 may be configured with triggering conditions to provide cross-layer API signaling. For example, the modem of anchor UE 802 may provide a new traffic splitting descriptor only when a specific link condition changes. The triggering conditions may include both anchor UE link triggering conditions and trunk UE link triggering conditions.
[0119] In some respects, the Application Function (AF) can explicitly influence the generation of PCC rules by the Policy and Control Function (PCF) based at least in part on signaling from the modem of the anchor UE 802, where the signaling may indicate proposed splits or other information. The AF can provide a service descriptor and preferred access, which can be used to determine ATSSS rules or any relevant service aggregation or splitting features in the UPF 812.
[0120] As indicated above, Figure 8 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 8 The examples described are different.
[0121] Figure 9 This is an illustration of example 900 associated with a modem recommendation for service splitting according to this disclosure. Example 900 includes anchor UE 902. Anchor UE 902 may include application client 904, modem 906, and MPQUIC / MPTCP aware application 908.
[0122] As shown by reference numeral 910, application client 904 may provide modem 906 with a list of uplink service flows that can be split or guided by modem assistance. As shown by reference numeral 912, modem 906 may determine a splitting factor for uplink signals. For example, modem 906 may determine that 80% of the multimodal QoS flows should be associated with a first link, and the remaining 20% of the multimodal QoS flows should be associated with a second link. As another example, modem 906 may determine that a first multimodal QoS flow should be associated with a first link, and a second multimodal QoS flow should be associated with a second link. As shown by reference numeral 914, modem 906 may transmit assistance information to MPQUIC / MPTCP aware application 908, wherein the assistance information may indicate the splitting factor. Modem 906 may transmit assistance information via a cross-layer API. In other words, in the uplink, modem 906 may suggest load balancing splits or guidance for at least one or more SDFs via a cross-layer API. As indicated by reference numeral 916 in the accompanying drawings, the MPQUIC / MPTCP aware application 908 may employ a suggested modem splitting factor as indicated in the auxiliary information. For example, the MPQUIC / MPTCP aware application 908 may adapt packet splitting across two connections based at least in part on load balancing suggested by the modem. Additionally or alternatively, the MPQUIC / MPTCP aware application 908 may provide feedback to the modem 906, wherein such feedback may be in response to the suggested modem splitting factor indicated in the auxiliary information.
[0123] As indicated above, Figure 9 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 9 The examples described are different.
[0124] Figure 10 This is an illustration of Example 1000 associated with a modem recommendation for service splitting according to this disclosure. Example 1000 includes anchor UE 1002, RAN 1008, and application server 1010. Anchor UE 1002 may include application client 1004 and modem 1006.
[0125] As shown by reference numeral 1012, modem 1006 can determine a split factor between two connections. The split factor may be associated with the downlink direction. As shown by reference numeral 1014, modem 1006 can transmit auxiliary information to application client 1004, wherein the auxiliary information may indicate a suggested split factor. Modem 1006 may transmit the auxiliary information via a cross-layer API. As shown by reference numeral 1016, application client 1004 may transmit auxiliary information to application server 1010 via RAN 1008. In other words, application client 1004 may forward auxiliary information (e.g., a suggested split factor) to application server 1010, wherein application server 1010 may or may not implement the suggested split factor in the downlink direction.
[0126] As indicated above, Figure 10 This is provided as an example. Other examples are available with reference to [the relevant information]. Figure 10 The examples described are different.
[0127] Figure 11 This is a diagram illustrating an example process 1100 performed, for example, at a first UE or a device of the first UE, according to this disclosure. Example process 1100 is an example in which a device or UE (e.g., UE 120) performs operations associated with a modem recommendation for service splitting.
[0128] like Figure 11 As shown, in some aspects, process 1100 may include: identifying a recommended service split between a first connection associated with a first UE and a second connection associated with a second UE by the UE's modem (box 1110). For example, the first UE (e.g., using...) Figure 12 The described communication manager 1206 can be identified by the UE's modem as a recommended service split between a first connection associated with the first UE and a second connection associated with the second UE, as described above, for example in... Figure 9 912 locations and in Figure 10 The description of location 1012.
[0129] like Figure 11 As further shown, in some aspects, process 1100 may include: the modem using a cross-layer API to provide auxiliary information indicating recommended service splitting (box 1120). For example, the first UE (e.g., using a cross-layer API) Figure 12 The described communication manager 1206 can be used by the modem via a cross-layer API to provide auxiliary information indicating recommended service splits, as described above, for example in... Figure 9 914 locations and in Figure 10 The description of location 1016.
[0130] Process 1100 may include additional aspects, such as any single aspect or any combination of aspects described below and / or in conjunction with one or more other processes described elsewhere in this document.
[0131] In the first aspect, the auxiliary information is provided to the application client of the first UE, and process 1100 includes forwarding the auxiliary information to the application server via the application client, wherein the cross-layer API is used by the application client.
[0132] In the second aspect, the auxiliary information is forwarded to the application server, either alone or in combination with the first aspect, at least in part based on in-band signaling or control plane signaling.
[0133] In a third aspect, either alone or in combination with one or more of the first and second aspects, the auxiliary information includes information about a first link condition associated with the first connection and a second link condition associated with the second connection, and the information indicates one or more of the throughput, bandwidth, latency, or sidelink conditions for each connection.
[0134] In the fourth aspect, either alone or in combination with one or more of the first to third aspects, the auxiliary information includes the flow associated with the recommended business segmentation, and the flow is either an uplink flow or a downlink flow.
[0135] In the fifth aspect, either alone or in combination with one or more of the first to fourth aspects, the recommended business split is used for downlink adaptive load balancing via the application server.
[0136] In the sixth aspect, either alone or in combination with one or more of the first to fifth aspects, the recommended service split is used for uplink adaptive load balancing via the first UE.
[0137] In the seventh aspect, either alone or in combination with one or more of the first to sixth aspects, the splitting of uplink packets of the service data stream occurs above the IP layer of the first UE using the MPQUIC or MPTCP aware application of the first UE.
[0138] In the eighth aspect, alone or in combination with one or more of the first to seventh aspects, the cross-layer API is a dedicated API for the MPQUIC or MPTCP-aware application.
[0139] In the ninth aspect, either alone or in combination with one or more of the first to eighth aspects, process 1100 includes: the MPQUIC or MPTCP aware application adopting the recommended service split, wherein the recommended service split is an uplink service split; or providing feedback to the modem indicating that the recommended service split has not been adopted.
[0140] In the tenth aspect, alone or in combination with one or more of the first to ninth aspects, process 1100 includes: controlling packet load balancing or splitting via the modem, at least in part, based on the auxiliary information, when the aggregation or splitting of packets is located above the IP layer of the application server or the IP layer of the first UE, respectively.
[0141] In the eleventh aspect, alone or in combination with one or more of the first to tenth aspects, the recommended service split is used to meet the multimodal synchronization requirements for two QoS streams, wherein the two QoS streams are associated with two or more of the following: a visual QoS stream, an audio QoS stream, or a haptic QoS stream.
[0142] In the twelfth aspect, either alone or in combination with one or more of the first to eleventh aspects, process 1100 includes: receiving from the second UE information for supporting service splitting between the first connection and the second connection.
[0143] In the thirteenth aspect, alone or in combination with one or more of the first to twelfth aspects, process 1100 includes: the modem receiving from the application client of the first UE an indication of a possible service data stream for which the modem can provide auxiliary information.
[0144] In the fourteenth aspect, alone or in combination with one or more of the first to thirteenth aspects, the auxiliary information includes a mapping of the multimodal flow to the first connection and the second connection.
[0145] In the fifteenth aspect, alone or in combination with one or more of the first to fourteenth aspects, the mapping indicates that a first percentage of traffic in a multimodal QoS flow is associated with the first connection and a second percentage of traffic in the multimodal QoS flow is associated with the second connection, or that a first multimodal QoS flow is associated with the first connection and a second multimodal QoS flow is associated with the second connection.
[0146] In the sixteenth aspect, alone or in combination with one or more of the first to fifteenth aspects, the auxiliary information is provided at least in part based on the fulfillment of the triggering condition.
[0147] In the seventeenth aspect, either alone or in combination with one or more of the first to sixteenth aspects, the PCF generates PCC rules based at least in part on signaling initiated by the modem from the modem.
[0148] although Figure 11 An example box of process 1100 is shown, but in some respects, process 1100 may include... Figure 11 The boxes depicted may be fewer, different, or arranged differently compared to additional boxes. Alternatively, two or more boxes in process 1100 may be executed in parallel.
[0149] Figure 12 This is a diagram of an example device 1200 for wireless communication according to the present disclosure. Device 1200 may be a first UE, or a first UE may include device 1200. In some aspects, device 1200 includes a receiving component 1202, a transmitting component 1204, and / or a communication manager 1206 that can communicate with each other (e.g., via one or more buses and / or one or more other components). In some aspects, communication manager 1206 is combined with... Figure 1 The described communication manager 140. As shown, the device 1200 can use the receiving component 1202 and the transmitting component 1204 to communicate with another device 1208, such as a UE or a network node (such as a CU, DU, RU or base station).
[0150] In some respects, device 1200 can be configured to perform the functions described herein. Figures 8 to 10 One or more operations as described herein. Additionally or alternatively, the apparatus 1200 may be configured to perform one or more processes described herein (such as...). Figure 11 Process 1100) or combinations thereof. In some aspects, device 1200 and / or Figure 12 One or more components shown may include combinations Figure 2 One or more components of the first UE as described. Additionally or alternatively, Figure 12 One or more components shown can be combined Figure 2 Implementation within one or more of the described components. Additionally or alternatively, one or more components in the set of components may be implemented at least partially as software stored in one or more memories. For example, a component (or a portion thereof) may be implemented as instructions or code stored in a non-transitory computer-readable medium and executable by one or more controllers or one or more processors to perform the function or operation of the component.
[0151] Receiver 1202 may receive communications from device 1208, such as reference signals, control information, data communications, or combinations thereof. Receiver 1202 may provide the received communications to one or more other components of device 1200. In some aspects, receiver 1202 may perform signal processing (such as filtering, amplification, demodulation, analog-to-digital conversion, demultiplexing, deinterleaving, demapping, equalization, interference cancellation, or decoding, etc.) on the received communications, and may provide the processed signals to the one or more other components of device 1200. In some aspects, receiver 1202 may include combinations of... Figure 2 The first UE described includes one or more antennas, one or more modems, one or more demodulators, one or more MIMO detectors, one or more receiver processors, one or more controllers / processors, one or more memories, or combinations thereof.
[0152] Transmitting component 1204 may transmit communications, such as reference signals, control information, data communications, or combinations thereof, to device 1208. In some aspects, one or more other components of device 1200 may generate communications and provide the generated communications to transmitting component 1204 for transmission to device 1208. In some aspects, transmitting component 1204 may perform signal processing (such as filtering, amplification, modulation, digital-to-analog conversion, multiplexing, interleaving, mapping, or encoding, etc.) on the generated communications and may transmit the processed signals to device 1208. In some aspects, transmitting component 1204 may include combinations of... Figure 2 The described first UE includes one or more antennas, one or more modems, one or more modulators, one or more transmit MIMO processors, one or more transmit processors, one or more controllers / processors, one or more memories, or combinations thereof. In some aspects, the transmit component 1204 may co-located with the receive component 1202 in one or more transceivers.
[0153] The communication manager 1206 may support the operation of the receiving component 1202 and / or the transmitting component 1204. For example, the communication manager 1206 may receive information associated with configuring the receiving component 1202 to receive communication and / or the transmitting component 1204 to transmit communication. Additionally or alternatively, the communication manager 1206 may generate control information and / or provide control information to the receiving component 1202 and / or the transmitting component 1204 to control the receiving and / or transmitting of communication.
[0154] The communication manager 1206 can identify a recommended service split between a first connection associated with the first UE and a second connection associated with the second UE via the modem of the first UE. The communication manager 1206 can also provide auxiliary information indicating the recommended service split via a cross-layer API using the modem.
[0155] The transmitting component 1204 can forward auxiliary information to the application server via the application client of the first UE, wherein the cross-layer API is used for the application client. The communication manager 1206 can adopt recommended service splitting by an MPQUIC or MPTCP-aware application, wherein the recommended service splitting is an uplink service splitting. The communication manager 1206 can provide feedback to the modem indicating that the recommended service splitting has not been adopted. The communication manager 1206 can control packet load balancing or splitting, at least partially based on the auxiliary information, via the modem when packet aggregation or splitting is located above the IP layer of the application server or the IP layer of the first UE, respectively. The receiving component 1202 can receive information from the second UE to support service splitting between the first and second connections. The communication manager 1206 can receive from the application client of the first UE, via the modem, an indication of possible service data streams for which the modem can provide auxiliary information.
[0156] Figure 12 The number and arrangement of components shown are provided as an example. In reality, with... Figure 12 Compared to the components shown, there may be additional components, fewer components, different components, or components arranged in a different manner. Furthermore, Figure 12 The two or more components shown can be implemented within a single component, or Figure 12 The single component shown can be implemented as multiple distributed components. Additionally or alternatively, Figure 12 The collection of (one or more) components shown is executable and described as being composed of Figure 12 Another set of components shown performs one or more functions.
[0157] The following provides an overview of some aspects of this disclosure: Aspect 1: A method for wireless communication performed by a first user equipment (UE), the method comprising: identifying a recommended traffic split between a first connection associated with the first UE and a second connection associated with a second UE by a modem of the first UE; and providing auxiliary information indicating the recommended traffic split by the modem using a cross-layer application programming interface (API).
[0158] Aspect 2: According to the method of aspect 1, wherein the auxiliary information is provided to the application client of the first UE, and the method further includes: forwarding the auxiliary information to the application server via the application client, wherein the cross-layer API is used by the application client.
[0159] Aspect 3: According to the method of aspect 2, the forwarding of the auxiliary information to the application server is at least partially based on in-band signaling or control plane signaling.
[0160] Aspect 4: The method according to any one of Aspects 1 to 3, wherein the auxiliary information includes information about a first link condition associated with the first connection and a second link condition associated with the second connection, and the information indicates one or more of throughput, bandwidth, latency or sidelink conditions for each connection.
[0161] Aspect 5: The method according to any one of Aspects 1 to 4, wherein the auxiliary information includes flow direction associated with the recommended service split, and the flow direction is uplink flow direction or downlink flow direction.
[0162] Aspect 6: The method according to any one of Aspects 1 to 5, wherein the recommended service split is used for downlink adaptive load balancing via the application server.
[0163] Aspect 7: The method according to any one of Aspects 1 to 6, wherein the recommended service split is used for uplink adaptive load balancing via the first UE.
[0164] Aspect 8: The method according to any one of Aspects 1 to 7, wherein the splitting of uplink packets of the service data stream occurs above the Internet Protocol (IP) layer of the first UE using a Multipath Fast User Datagram Protocol Internet Connection (MPQUIC) or Multipath Transmission Control Protocol (MPTCP) aware application of the first UE.
[0165] Aspect 9: According to the method described in aspect 8, the cross-layer API is a dedicated API for the MPQUIC or MPTCP aware application.
[0166] Aspect 10: The method according to aspect 9 further includes: the MPQUIC or MPTCP aware application adopting the recommended service split, wherein the recommended service split is an uplink service split; or providing feedback to the modem indicating that the recommended service split has not been adopted.
[0167] Aspect 11: The method according to any one of Aspects 1 to 10, the method further comprising: when the aggregation or splitting of packets is located above the Internet Protocol (IP) layer of the application server or the Internet Protocol (IP) layer of the first UE, respectively, controlling the load balancing or splitting of packets via the modem based at least in part on the auxiliary information.
[0168] Aspect 12: The method according to any one of Aspects 1 to 11, wherein the recommended service split is used to satisfy multimodal synchronization requirements for two Quality of Service (QoS) streams, wherein the two QoS streams are associated with two or more of the following: a visual QoS stream, an audio QoS stream, or a haptic QoS stream.
[0169] Aspect 13: The method according to any one of Aspects 1 to 12, the method further comprising: receiving from the second UE information for supporting service splitting between the first connection and the second connection.
[0170] Aspect 14: The method according to any one of Aspects 1 to 13, the method further comprising: receiving from the application client of the first UE an indication of a possible service data stream for which the modem can provide auxiliary information.
[0171] Aspect 15: The method according to any one of Aspects 1 to 14, wherein the auxiliary information includes a mapping of multimodal flows to the first connection and the second connection.
[0172] Aspect 16: According to the method of aspect 15, wherein the mapping indicates that a first percentage of a multimodal Quality of Service (QoS) flow is associated with the first connection and a second percentage of the multimodal QoS flow is associated with the second connection, or a first multimodal QoS flow is associated with the first connection and a second multimodal QoS flow is associated with the second connection.
[0173] Aspect 17: The method according to any one of Aspects 1 to 16, wherein the auxiliary information is provided at least in part based on the fulfillment of a triggering condition.
[0174] Aspect 18: The method according to any one of Aspects 1 to 17, wherein the generation of policy and control (PCF) policy and charging control (PCC) rules is based at least in part on signaling initiated by the modem from the modem.
[0175] Aspect 19: An apparatus for wireless communication at a device, the apparatus comprising: one or more processors; one or more memories coupled to the one or more processors; and instructions stored in the one or more memories and executable by the one or more processors to cause the apparatus to perform the method according to one or more of aspects 1 to 18.
[0176] Aspect 20: An apparatus for wireless communication at a device, the apparatus comprising: one or more memories; and one or more processors coupled to the one or more memories, the one or more processors being configured to cause the device to perform the method according to one or more of aspects 1 to 18.
[0177] Aspect 21: An apparatus for wireless communication, the apparatus comprising at least one component for performing the method according to one or more of aspects 1 to 18.
[0178] Aspect 22: A non-transitory computer-readable medium storing code for wireless communication, said code including instructions executable by one or more processors to perform the methods described in one or more of aspects 1 to 18.
[0179] Aspect 23: A non-transitory computer-readable medium storing a set of instructions for wireless communication, the set of instructions comprising one or more instructions that, when executed by one or more processors of a device, cause the device to perform the method according to one or more of aspects 1 to 18.
[0180] Aspect 24: A device for wireless communication, the device including a processing system comprising one or more processors and one or more memories coupled to the one or more processors, the processing system being configured to cause the device to perform the method according to one or more of aspects 1 to 18.
[0181] Aspect 25: An apparatus for wireless communication at a device, the apparatus comprising one or more memories and one or more processors coupled to the one or more memories, the one or more processors being individually or collectively configured to cause the device to perform the method according to one or more of aspects 1 to 18.
[0182] While the foregoing disclosure provides examples and descriptions, it is not intended to be exhaustive or to limit the aspects to the precise form disclosed. Modifications and variations may be made based on the foregoing disclosure, or from various forms of practice.
[0183] As used herein, the term "component" is intended to be broadly interpreted as hardware or a combination of hardware and at least one of software or firmware. "Software" should be broadly interpreted as instructions, instruction sets, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable programs, threads of execution, procedures, or functions, whether referred to as software, firmware, middleware, microcode, hardware description languages, or other terms. As used herein, a "processor" is implemented in hardware or a combination of hardware and software. It will be apparent that the systems or methods described herein may be implemented in various forms of hardware or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems or methods is not limited in any way. Therefore, the operation and behavior of these systems or methods are described herein without reference to specific software code, as those skilled in the art will understand that the software and hardware can be designed to implement these systems or methods, at least in part, based on the description herein. Unless otherwise stated, a component configured to perform a function means that the component has the capability to perform that function, but it is not necessary for the component to actually perform that function.
[0184] As used in this article, depending on the context, "meeting the threshold" can mean a value greater than the threshold, greater than or equal to the threshold, less than the threshold, less than or equal to the threshold, equal to the threshold, not equal to the threshold, etc.
[0185] As used in this article, the phrase “at least one of” in a list of items refers to any combination of these items, including a single member. As an example, “at least one of the following: a, b, or c” is intended to cover a, b, c, a+b, a+c, b+c, and a+b+c, as well as any combination with 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 ordering of a, b, and c).
[0186] No element, action, or instruction used herein should be construed as essential or necessary unless explicitly stated otherwise. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and are used interchangeably with “one or more.” Similarly, as used herein, the article “described” is intended to include one or more items mentioned in connection with the article “described” and is used interchangeably with “one or more.” Furthermore, as used herein, the terms “collection” and “group” are intended to include one or more items and are used interchangeably with “one or more.” If only one item is desired, the phrase “only one” or similar terminology will be used. Moreover, as used herein, the terms “having” and similar terms are intended as open-ended terms that do not limit the elements they modify (e.g., “having” A may also have B). Additionally, the phrase “based on” is intended to mean “based on or otherwise related to” unless otherwise explicitly stated. Furthermore, as used herein, the term “or” is intended to be inclusive when used consecutively and is interchangeable with “and / or” unless otherwise explicitly stated (e.g., if used in conjunction with “either of the two” or “only one of them”). It should be understood that “one or more” is equivalent to “at least one”.
[0187] Although specific combinations of features are set forth in the claims or disclosed in the description, these combinations are not intended to limit the disclosure of various aspects. Many of these features may be combined in ways not specifically stated in the claims or disclosed in the description. The disclosure of various aspects includes each dependent claim in combination with each other claim in the claim set.
Claims
1. An apparatus for performing wireless communication at a first user equipment (UE), the apparatus comprising: One or more memory units; and One or more processors, said one or more processors coupled to said one or more memories, said one or more processors individually or collectively configured to: The recommended service split between the first connection associated with the first UE and the second connection associated with the second UE, identified by the modem identifier of the first UE; and The modem uses a cross-layer application programming interface (API) to provide auxiliary information indicating the recommended service split.
2. The apparatus of claim 1, wherein the auxiliary information is provided to the application client of the first UE, and the one or more processors are individually or jointly configured to: The auxiliary information is forwarded to the application server via the application client, wherein the cross-layer API is used by the application client.
3. The apparatus of claim 2, wherein the one or more processors are individually or collectively configured to forward the auxiliary information to the application server at least in part based on in-band signaling or control plane signaling.
4. The apparatus of claim 1, wherein the auxiliary information includes information about a first link condition associated with the first connection and a second link condition associated with the second connection, and the information indicates one or more of throughput, bandwidth, latency, or sidelink conditions for each connection.
5. The apparatus of claim 1, wherein the auxiliary information includes flow direction associated with the recommended service split, and the flow direction is an uplink flow direction or a downlink flow direction.
6. The apparatus of claim 1, wherein the recommended service split is used for downlink adaptive load balancing via the application server.
7. The apparatus of claim 1, wherein the recommended service split is used for adaptive load balancing via the uplink of the first UE.
8. The apparatus of claim 1, wherein the splitting of uplink packets of the service data stream occurs above the Internet Protocol (IP) layer of the first UE using a Multipath Fast User Datagram Protocol Internet Connection (MPQUIC) or Multipath Transmission Control Protocol (MPTCP) aware application of the first UE.
9. The apparatus of claim 8, wherein the cross-layer API is a dedicated API for the MPQUIC or MPTCP aware application.
10. The apparatus of claim 9, wherein the one or more processors are configured individually or collectively to: The recommended service split is adopted by the MPQUIC or MPTCP awareness application, wherein the recommended service split is an uplink service split; or Provide feedback to the modem indicating that the recommended service split has not been adopted.
11. The apparatus of claim 1, wherein the one or more processors are configured individually or collectively to: When the aggregation or splitting of packets is located above the Internet Protocol (IP) layer of the application server or the Internet Protocol (IP) layer of the first UE, the load balancing or splitting of packets is controlled by the modem at least in part based on the auxiliary information.
12. The apparatus of claim 1, wherein the recommended service split is used to satisfy multimodal synchronization requirements for two Quality of Service (QoS) streams, wherein the two QoS streams are associated with two or more of the following: a visual QoS stream, an audio QoS stream, or a haptic QoS stream.
13. The apparatus of claim 1, wherein the one or more processors are configured individually or collectively to: The second UE receives information for supporting service splitting between the first connection and the second connection.
14. The apparatus of claim 1, wherein the one or more processors are configured individually or collectively to: The modem receives from the application client of the first UE an indication of possible service data streams for which the modem can provide auxiliary information.
15. The apparatus of claim 1, wherein the auxiliary information includes a mapping of multimodal flows to the first connection and the second connection.
16. The apparatus of claim 15, wherein the mapping indication: A first percentage of traffic in the multimodal Quality of Service (QoS) flow is associated with the first connection, and a second percentage of traffic in the multimodal QoS flow is associated with the second connection, or The first multimodal QoS flow is associated with the first connection, and the second multimodal QoS flow is associated with the second connection.
17. The apparatus of claim 1, wherein the auxiliary information is provided at least in part based on the fulfillment of a triggering condition.
18. The apparatus of claim 1, wherein the generation of policy and control (PCF) rules for policy and charging control (PCC) is based at least in part on signaling initiated by the modem from the modem.
19. A method for wireless communication performed by a first user equipment (UE), the method comprising: The recommended service split is identified by the modem identifier of the first UE between the first connection associated with the first UE and the second connection associated with the second UE; as well as The modem uses a cross-layer application programming interface (API) to provide auxiliary information indicating the recommended service split.
20. A non-transitory computer-readable medium storing an instruction set for wireless communication, the instruction set comprising: One or more instructions, which, when executed by one or more processors of a first user equipment (UE), cause the first UE to: The recommended service split between the first connection associated with the first UE and the second connection associated with the second UE, identified by the modem identifier of the first UE; and The modem uses a cross-layer application programming interface (API) to provide auxiliary information indicating the recommended service split.
