Network control for multipath sidelink operation

Abstract

Methods, systems, and devices for wireless communication are described. A first user equipment (UE) can establish an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link including a first path. The first UE can send, via the end-to-end link, an indication of a configuration for a second path between the first UE and the second UE, wherein the configuration for the second path is based on service information associated with the service. The first UE can communicate traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

Description

Technical Field

[0001] The following relates to wireless communications, including network control of multipath sidelink operations. Background Art

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

[0003] In some examples, a first user equipment (UE) may communicate with a second UE using a single path. For example, the first UE may communicate directly with the second UE, or may communicate with the second UE using a relay UE. Technologies that enable the first UE to communicate with the second UE via more than one path may improve the efficiency of wireless communications. However, supporting multiple paths for communication between UEs presents challenges in managing the paths used for communication. Summary of the invention

[0004] The described technology relates to improved methods, systems, devices and apparatuses for network control that supports multipath sidelink operations. For example, the described technology enables a first user equipment (UE) to establish multiple paths with a second UE according to a multipath rule. For example, a first UE can establish an end-to-end link with a second UE for communicating a service associated with a service, and the end-to-end link includes a first path. The first UE may send an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The first UE may communicate the service associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0005] A method for wireless communication at a first user equipment (UE) is described. The method may include: establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link comprising a first path; sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and communicating traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

[0006] A device for wireless communication at a first UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the device to: establish an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; send an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and based on sending the indication of the configuration for the second path, communicate the traffic associated with the service with the second UE via the first path or the second path.

[0007] Another apparatus for wireless communication at a first UE is described. The apparatus may include: a component for establishing an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; a component for sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and a component for communicating traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

[0008] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to perform the following operations: establish an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; send an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and based on sending the indication of the configuration for the second path, communicate the traffic associated with the service with the second UE via the first path or the second path.

[0009] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of a configuration for a second path may include operations, features, components, or instructions for sending an indication of whether the second path is associated with a separate bearer or an independent bearer via an end-to-end link, wherein communication of traffic associated with the service via the first path or the second path may be based on sending an indication of whether the second path is associated with a separate bearer or an independent bearer.

[0010] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of a configuration for a second path may include operations, features, components, or instructions for sending an indication of a number of paths via an end-to-end link, where communicating traffic associated with the service via the first path or the second path may be based on sending the indication of the number of paths.

[0011] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of a configuration for a second path may include operations, features, components, or instructions for sending an indication of an access type to the second path via an end-to-end link, where communicating traffic associated with the service via the first path or the second path can be based on sending the indication of the access type to the second path.

[0012] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of an access type includes an indication of an access type set, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for: sending an indication of service information via an end-to-end link; receiving an indication of a subset of the access type set from a second UE; and based on receiving the indication of the subset of the access type set, communicating traffic associated with the service via a first path or a second path.

[0013] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, sending an indication of a configuration for a second path may include operations, features, components, or instructions for sending an indication of whether the second path may be a direct path from a first UE to a second UE or may be a relay path via an end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0014] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: sending an indication of a bearer configuration to a second UE, wherein the bearer configuration may be based on service information; and receiving an indication from the second UE that the second UE accepts the bearer configuration, wherein communicating the service associated with the service via the first path or the second path may be based on receiving an indication that the second UE accepts the bearer configuration.

[0015] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: determining a configuration for a second path at a first layer of the first UE based on service information; providing a configuration for the second path and an indication of a quality of service (QoS) flow to a second layer of the first UE; and communicating traffic associated with the service via the first path or the second path based on providing the configuration for the second path and the indication of the QoS flow to the second layer of the first UE.

[0016] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first layer includes a proximity service layer and the second layer includes a radio resource control layer.

[0017] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: providing service information and a quality of service (QoS) flow by a first layer of a first UE to a second layer of the first UE; determining a configuration for a second path at the second layer based on the provided service information; and communicating traffic associated with the service via the first path or the second path based on the configuration determined for the second path at the second layer.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for providing, by a first layer of the first UE, an identifier of the first UE, an identifier of the second UE, or both, wherein determining a configuration for the second path may be based on the identifier of the first UE, the identifier of the second UE, or both.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first layer includes a proximity service layer and the second layer includes a radio resource control layer.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service information includes an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0021] A method for wireless communication at a first UE is described. The method may include: establishing an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and communicating traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

[0022] A device for wireless communication at a first UE is described. The device may include a processor, a memory coupled to the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the device to: establish an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; receive an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and based on sending the indication of the configuration for the second path, communicate the traffic associated with the service with the second UE via the first path or the second path.

[0023] Another apparatus for wireless communication at a first UE is described. The apparatus may include: a component for establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link including a first path; a component for receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and a component for communicating traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

[0024] A non-transitory computer-readable medium storing code for wireless communication at a first UE is described. The code may include instructions executable by a processor to perform the following operations: establish an end-to-end link for communicating traffic associated with a service with a second UE, the end-to-end link including a first path; receive an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service; and communicate traffic associated with the service with the second UE via the first path or the second path based on sending the indication of the configuration for the second path.

[0025] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication of a configuration for a second path may include operations, features, components, or instructions for receiving an indication of whether the second path is associated with a separate bearer or an independent bearer via an end-to-end link, wherein communicating traffic associated with the service via the first path or the second path may be based on sending an indication of whether the second path is associated with a separate bearer or an independent bearer.

[0026] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication of a configuration for a second path may include operations, features, components, or instructions for receiving an indication of a number of paths via an end-to-end link, where communicating traffic associated with the service via the first path or the second path may be based on sending the indication of the number of paths.

[0027] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication of a configuration for a second path may include operations, features, components, or instructions for receiving an indication of an access type for the second path via an end-to-end link, wherein communicating traffic associated with the service via the first path or the second path may be based on sending the indication of the access type for the second path.

[0028] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the indication of an access type includes an indication of an access type set, and the methods, apparatus, and non-transitory computer-readable media may also include operations, features, components, or instructions for: receiving an indication of service information via an end-to-end link; sending an indication of a subset of the access type set to a second UE; and based on receiving the indication of the subset of the access type set, communicating traffic associated with the service via a first path or a second path.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, receiving an indication of a configuration for a second path may include operations, features, components, or instructions for receiving an indication of whether the second path may be a direct path from a first UE to a second UE or may be a relay path via an end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0030] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for: receiving an indication of a bearer configuration from a second UE, wherein the bearer configuration may be based on service information; and sending an indication to the second UE that the first UE accepts the bearer configuration, wherein communicating the service associated with the service via the first path or the second path may be based on sending the indication that the first UE accepts the bearer configuration.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the service information includes an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1An example of a network-controlled wireless communication system supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated.

[0033] Figure 2 An example of a network-controlled wireless communication system supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated.

[0034] Figure 3 An example of a network-controlled path establishment process supporting multi-path side-link operation according to one or more aspects of the present disclosure is illustrated.

[0035] Figure 4 An example of a specific implementation of multipath rules for network control supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated.

[0036] Figure 5 An example of a process flow for network control supporting multipath sidelink operations according to one or more aspects of the present disclosure is illustrated.

[0037] Figure 6 and Figure 7 A block diagram of a device supporting network control of multipath sidelink operations according to one or more aspects of the present disclosure is shown.

[0038] Figure 8 A block diagram of a communication manager for network control supporting multipath sidelink operations according to one or more aspects of the present disclosure is shown.

[0039] Fig. 9 A diagram of a system including a device supporting network control of multipath sidelink operations according to one or more aspects of the present disclosure is shown.

[0040] Figures 10 to 13 A flow chart illustrating a method of network control supporting multipath sidelink operation according to one or more aspects of the present disclosure is shown. DETAILED DESCRIPTION

[0041] In some examples, a first user equipment (UE) may communicate with a second UE using multiple (e.g., two or more) paths. For example, the first UE may send a first transmission directly to the second UE along a first path, and may send a second transmission to the second UE along a second path using a third UE as a relay. In some examples, multiple paths may have one or more associated communication parameters. For example, each path may have an associated access type (e.g., licensed vs. unlicensed), a path type (e.g., direct or relay), a bearer type (e.g., a separate bearer or a separate bearer), or any combination thereof. In some examples, there may be certain constraints on the values ​​of one or more communication parameters. However, if the first UE and / or the second UE fails to determine these constraints for a particular service, the first UE and / or the second UE may mistakenly use values ​​of one or more communication parameters that do not comply with these constraints.

[0042] In order to enable the UE to determine the communication parameter value to be used for a particular service, the UE may be configured with a multipath rule indicating a mapping between service information and one or more communication parameters. For example, a first UE may establish an end-to-end link with a second UE for communicating a service associated with the service, the end-to-end link comprising a first path. The first UE may send an indication of a configuration for a second path (e.g., an indication of one or more communication parameters) via the end-to-end link, wherein the configuration for the second path is based on the service information associated with the service. The first UE may communicate the service associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0043] In some examples, the multipath rule may be implemented at a proximity service (ProSe) layer. For example, the first UE may determine one or more communication parameters at the ProSe layer based on the service information and using the multipath rule, and may provide the one or more communication parameters to the radio resource control (RRC) layer, wherein the RRC layer may establish a second path based on the one or more communication parameters provided. In other examples, the multipath rule may be implemented at the RRC layer. For example, the ProSe layer may provide service information to the RRC layer, and the first UE may determine one or more communication parameters from the service information based on the multipath rule at the RRC layer. The first UE may then establish a second path based on the determined one or more communication parameters. Additionally or alternatively, the first UE may send an indication of the service information and at least one of the one or more communication parameters (e.g., access type) to the second UE, wherein the second UE may indicate to the first UE whether the second UE supports or accepts at least one of the one or more communication parameters corresponding to the service information. The first UE may then establish a second path based on an indication that the second UE supports or accepts at least one of the one or more communication parameters.

[0044] Various aspects of the disclosure are first described in the context of a wireless communication system. Additional aspects of the disclosure are described in the context of a path establishment process, a multipath rule implementation, and a process flow. Various aspects of the disclosure are further illustrated and described by and with reference to device diagrams, system diagrams, and flow diagrams related to network control of multipath sidelink operations.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0061] In some examples, such as in a carrier aggregation configuration, a carrier may also have acquisition signaling or control signaling that coordinates the operation of other carriers. A carrier may be associated with a frequency channel (e.g., an Evolved Universal Mobile Telecommunications System Terrestrial Radio Access (E-UTRA) Absolute RF Channel Number (EARFCN)) and may be identified based on a channel raster for discovery by UE 115. A carrier may operate in a standalone mode, in which case initial acquisition and connection may be made by UE 115 via the carrier, or a carrier may operate in a non-standalone mode, in which case a different carrier (e.g., of the same or different radio access technology) is used to anchor the connection.

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

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

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

[0065] One or more parameter sets for a carrier may be supported, and the parameter sets may include subcarrier spacing (Δf) and cyclic prefixes. A carrier may be divided into one or more BWPs with the same or different parameter sets. In some examples, a UE 115 may be configured with multiple BWPs. In some examples, a single BWP for a carrier may be active at a given time, and communications of a UE 115 may be constrained to one or more active BWPs.

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

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

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

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

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

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

[0072] In some examples, a carrier may support multiple cells, and different cells may be configured according to different protocol types (e.g., MTC, narrowband IoT (NB-IoT), enhanced mobile broadband (eMBB)) that may provide access to different types of devices.

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

[0074] The wireless communication system 100 may support synchronous or asynchronous operation. For synchronous operation, the network entities 105 (e.g., base stations 140) may have similar frame timing, and transmissions from different network entities 105 may be approximately aligned in time. For asynchronous operation, the network entities 105 may have different frame timing, and in some examples, transmissions from different network entities 105 may not be aligned in time. The techniques described herein may be used for synchronous or asynchronous operation.

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

[0076] Some UEs 115 may be configured to employ an operating mode that reduces power consumption, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but does not transmit and receive concurrently). In some examples, half-duplex communication may be performed with a reduced peak rate. Other energy-saving techniques for UEs 115 include entering a power-saving deep sleep mode when not engaged in active communications, operating using limited bandwidth (e.g., according to narrowband communications), or a combination of these techniques. For example, some UEs 115 may be configured to operate using a narrowband protocol type that is associated with a defined portion or range (e.g., a subcarrier or resource block (RB) set) within a carrier, within a guard band of a carrier, or outside a carrier.

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

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

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

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

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

[0082] The wireless communication system 100 may also operate using a super high frequency (SHF) region, which may be in the range of 3 GHz to 30 GHz (also known as a centimeter band), or an extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz) (also known as a millimeter band). In some examples, the wireless communication system 100 may support millimeter wave (mmW) communications between a UE 115 and a network entity 105 (e.g., a base station 140, a RU 170), and the EHF antennas of the corresponding devices may be smaller and closer together than UHF antennas. In some examples, such techniques may facilitate the use of antenna arrays within the device. However, the propagation of EHF transmissions may be affected by even greater attenuation and shorter range than SHF or UHF transmissions. The techniques disclosed herein may be employed across transmissions using one or more different frequency regions, and the use of frequency bands specified across these frequency regions may vary by country or regulatory agency.

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

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

[0085] The network entity 105 or UE 115 may use MIMO communication to utilize multipath signal propagation and improve spectral efficiency by sending or receiving multiple signals via different spatial layers. Such a technology may be referred to as spatial multiplexing. The multiple signals may be sent, for example, by a transmitting device via different antennas or different combinations of antennas. Similarly, the multiple signals may be received by a receiving device via different antennas or different combinations of antennas. Each of the multiple signals may be referred to as a separate spatial stream and may carry information associated with the same data stream (e.g., the same codeword) or different data streams (e.g., different codewords). Different spatial layers may be associated with different antenna ports for channel measurement and reporting. MIMO technologies include: single-user MIMO (SU-MIMO), for which multiple spatial layers are sent to the same receiving device; and multi-user MIMO (MU-MIMO), for which multiple spatial layers are sent to multiple devices.

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

[0087] The network entity 105 or UE 115 may use beam scanning techniques as part of a beamforming operation. For example, the network entity 105 (e.g., base station 140, RU 170) may use multiple antennas or antenna arrays (e.g., antenna panels) to perform beamforming operations for directional communication with UE 115. Some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be sent multiple times by the network entity 105 along different directions. For example, the network entity 105 may send signals according to different sets of beamforming weights associated with different transmission directions. Transmissions along different beam directions may be used to identify (e.g., by a transmitting device (such as network entity 105), or by a receiving device (such as UE 115)) beam directions for later transmission or reception by the network entity 105.

[0088] Some signals, such as data signals associated with a particular receiving device, may be sent by a transmitting device (e.g., transmitting network entity 105, transmitting UE 115) along a single beam direction (e.g., a direction associated with a receiving device (such as receiving network entity 105 or receiving UE 115)). In some examples, the beam direction associated with the transmission along the single beam direction may be determined based on signals sent along one or more beam directions. For example, UE 115 may receive one or more of the signals sent by network entity 105 along different directions, and may report to network entity 105 an indication of the signal received by UE 115 with the highest signal quality or other acceptable signal quality.

[0089] In some examples, transmission by a device (e.g., by network entity 105 or UE 115) may be performed using multiple beam directions, and the device may use a combination of digital precoding or beamforming to generate a combined beam for transmission (e.g., from network entity 105 to UE 115). UE 115 may report feedback indicating precoding weights for one or more beam directions, and the feedback may correspond to a configured set of beams across a system bandwidth or one or more subbands. Network entity 105 may send a reference signal (e.g., a cell-specific reference signal (CRS), a channel state information reference signal (CSI-RS)), which may or may not be precoded. UE 115 may provide feedback for beam selection, which may be a precoding matrix indicator (PMI) or codebook-based feedback (e.g., a multi-panel codebook, a linear combination codebook, a port selection codebook). Although these techniques are described with reference to signals sent along one or more directions by a network entity 105 (e.g., base station 140, RU 170), UE 115 may use similar techniques to send signals multiple times along different directions (e.g., to identify a beam direction for subsequent transmission or reception by UE 115), or to send signals along a single direction (e.g., to send data to a receiving device).

[0090] A receiving device (e.g., UE 115) may perform receiving operations according to multiple receiving configurations (e.g., directional listening) when receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from a receiving device (e.g., network entity 105). For example, the receiving device may perform reception according to multiple receiving directions by: receiving via different antenna subarrays, processing the received signals according to different antenna subarrays, receiving according to different receiving beamforming weight sets (e.g., different directional listening weight sets) applied to signals received at multiple antenna elements of an antenna array, or processing the received signals according to different receiving beamforming weight sets applied to signals received at multiple antenna elements of an antenna array, any of which may be referred to as "listening" according to different receiving configurations or receiving directions. In some examples, the receiving device may use a single receiving configuration to receive along a single beam direction (e.g., when receiving a data signal). A single receive configuration may be aligned along a beam direction determined based on listening according to different receive configuration directions (e.g., a beam direction determined to have the highest signal strength, highest signal-to-noise ratio (SNR), or other acceptable signal quality based on listening according to multiple beam directions).

[0091] The wireless communication system 100 may be a packet-based network that operates according to a layered protocol stack. In the user plane, communications at the bearer or PDCP layer may be IP-based. The RLC layer may perform packet segmentation and reassembly to communicate via logical channels. The MAC layer may perform priority processing and multiplexing of logical channels into transport channels. The MAC layer may also implement error detection techniques, error correction techniques, or both to support retransmission to improve link efficiency. In the control plane, the RRC layer may provide the establishment, configuration, and maintenance of an RRC connection that supports a radio bearer for user plane data between the UE 115 and the network entity 105 or the core network 130. The PHY layer may map a transport channel to a physical channel.

[0092] UE 115 and network entity 105 may support retransmission of data to increase the likelihood of data being successfully received. Hybrid automatic repeat request (HARQ) feedback is a technique for increasing the likelihood of correctly receiving data via a communication link (e.g., communication link 125, D2D communication link 135). HARQ may include a combination of error detection (e.g., using a cyclic redundancy check (CRC)), forward error correction (FEC), and retransmission (e.g., automatic repeat request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., low signal-to-noise ratio conditions). In some examples, a device may support same-slot HARQ feedback, in which case the device may provide HARQ feedback in a specific time slot for data received via a previous symbol in the time slot. In some other examples, the device may provide HARQ feedback in a subsequent time slot or according to some other time interval.

[0093] In some examples, the first UE 115 may act as a relay for communication from the second UE 115 to the third UE 115. In such examples, a UE 115 (e.g., the first UE 115) that relays traffic between the second UE 115 and the third UE 115 may be referred to as a relay UE 115. The originator of the relayed traffic may be referred to as a source UE 115 (e.g., the second UE 115), and the target of the relayed traffic may be referred to as a target UE 115 (e.g., the third UE 115). If there is a single relay UE 115 between the source UE 115 and the target UE 115, there may be a single-hop relay. If there are multiple relay UEs between the source UE 115 and the target UE 115, there may be a multi-hop relay.

[0094] In some examples, the remote UE 115 may support dual path connections through two relays. For example, the remote UE 115 may use PC5 or non-3GPP radio access technology (RAT) access to connect to the two relays, where PC5 may be on a licensed band or an unlicensed band. Alternatively, the remote UE 115 may support dual path connections through one relay and one direct path. In either case, each path may be used for end-to-end traffic aggregation or replication, and at least one end-to-end signaling radio bearer (SRB) or data radio bearer (DRB) may be applied.

[0095] In some examples, different management or policies regarding bearer type or access type may be specified for different applications or constraints. However, during multipath connection establishment, if there are no rules or network controls in the remote UE for determining which path type, bearer type, or access type to use, the remote UE may not be able to determine these types for a particular service. The present disclosure describes how the network can control UE 115 to perform multipath operations.

[0096] Figure 2 An example of a network-controlled wireless communication system 200 supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated. In some examples, the wireless communication system 200 may be implemented by one or more aspects of the wireless communication system 100. For example, UEs 115-a, 115-b, and 115-c may be as described in reference Figure 1 Described are examples of UE 115. Additionally, UE 115-a may be an example of a source UE, UE 115-b may be an example of a relay UE, and UE 115-c may be an example of a target UE.

[0097] In some examples, UE 115-a may communicate with UE 115-c using multiple (e.g., two or more) paths. For example, UE 115-a may communicate with UE 115-c along a first path 205 using UE 115-b as a relay, and may communicate with UE 115-c along a second path 210, which may be a direct path between UE 115-a and UE 115-c, or may have one or more relay UEs 115 (e.g., UE 115-d) that may relay communications along the second path 210 between UE 115-a and UE 115-c.

[0098] In some examples, multiple paths may have one or more associated communication parameters. For example, each path may have an associated access type. For example, each of the first path 205 or the second path 210 may be associated with a licensed PC5 communication, an unlicensed PC5 communication, or a non-3GPP communication. Additionally or alternatively, each path may have an associated path type. For example, in this example, the first path 205 may be a relay path, and the second path 205 may be one of a relay path or a direct path. In some examples, the path type may also indicate the number of hops (e.g., n, where n may be the number of hops and / or the number of relay UEs between UE 115-a and UE 115-c). Additionally or alternatively, each path may have an associated bearer type. For example, the first path 205 and the second path 210 may be in a separate bearer configuration, or alternatively, the first path 205 and the second path 210 may each be associated with a separate bearer. In some examples, the bearer type may be represented as the number of paths. For example, a number of 1 may indicate that the path has a separate bearer, while a number greater than 1 (eg, 2) may indicate that the path is part of a split bearer configuration.

[0099] In some examples, there may be certain constraints on the values ​​of one or more communication parameters. However, if UE 115-a and UE 115-c fail to determine these constraints for a particular service, UE 115-a and / or UE 115-c may erroneously use values ​​for one or more communication parameters that do not comply with these constraints. Additionally or alternatively, a set of values ​​for a particular path may be associated with improved signaling characteristics (e.g., higher SNR, higher SINR, higher link efficiency) for a particular service compared to another set of values ​​for a particular service. However, without information indicating which of these communication parameter values ​​are associated with the improved signaling characteristics, the UE may be unable to determine these communication parameter values.

[0100] In order to enable UE 115-a and / or UE 115-c to determine communication parameter values ​​to be used for a particular service, UE 115-a and / or 115-c may be configured with a multipath rule indicating a mapping between service information and one or more communication parameters. For example, UE 115-a may establish an end-to-end link with UE 115-c for communicating traffic associated with a service, the end-to-end link including a first path 205. UE 115-a may send an indication of a configuration 215-a for a second path 210 (e.g., an indication of one or more communication parameters) via the end-to-end link, wherein the configuration 215-a for the second path is based on the service information associated with the service. Configuration 215-a may be received at UE 115-b and may be relayed to UE 115-c as configuration 215-b for the second path. UE 115-a may communicate traffic associated with the service with UE 115-c via first path 205 or second path 210 based on sending an indication of configuration 215-a for the second path. In some examples, the service information may include an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0101] In some examples (e.g., when applied to L2-based relays), multipath rules can be implemented at the ProSe layer. For example, UE 115-a can determine one or more communication parameters at the ProSe layer based on the service information and using the multipath rules, and can provide the one or more communication parameters to the RRC layer, where the RRC layer can establish the second path 210 based on the provided one or more communication parameters. In some such examples, the ProSe layer can determine the values ​​of one or more communication parameters for each PC5 QoS flow based on the multipath rules when generating a quality of service (QoS) flow or QoS flow rules. Additionally, the ProSe layer can provide the one or more communication parameters to the RRC layer together with the QoS flow, where the RRC layer can configure the bearer for the QoS flow based on the received one or more communication parameters.

[0102] As described herein, at least in some examples, multipath rules implemented at the ProSe layer may be used for L2-based UAV-to-UAV relaying. In some such examples, the multipath rules may be configured by the core network. Additionally, in such examples, when a QoS flow or QoS flow rule is generated, one or more communication parameters (e.g., bearer or path information, such as bearer type, path type, or access type) for each PC5 QoS flow may be determined based on the multipath rules. In some such examples, the multipath rules may be defined as a mapping between one or more communication parameters (e.g., bearer or path information, such as bearer type, path type, or access type) and service information (e.g., service type, constraint, packet filter, or packet filter set). For example, a bearer may be a separate bearer (e.g., dual path) or an independent bearer (e.g., single path). A separate bearer may include an end-to-end radio bearer having separate radio link control (RLC) bearers on different paths. An independent bearer may be an end-to-end bearer having an RLC bearer on one path. The path information may also include whether the path is a relay path or a direct path. In some examples, the access type may be an access technology, such as PC5 on a licensed band, PC5 on an unlicensed band, or a non-3GPP technology. In some examples, the mapping may be a list (e.g., an instance of service information may be mapped to a list of path information). In some examples, for each of the one or more bearers, there may be an access type to be determined.

[0103] In some examples, the ProSe layer may include path information and QoS rules in the QoS context. In some examples, the ProSe layer may provide the path information to the RRC layer together with the QoS flow. In some examples, the RRC layer may configure the corresponding bearer and access type for the QoS flow according to the path information. In some examples, when the ProSe layer provides the QoS flow to the RRC layer, the ProSe layer may provide the RRC layer with QoS flow information and bearer information.

[0104] The following is a table illustrating an example of multipath rules when configured in the ProSe layer:

[0105] Table 1: Multipath rules in the ProSe layer

[0106]

[0107] In some such examples, PQI may be defined as a PC5 QoS indicator (e.g., where a higher number may, for example, indicate a higher priority QoS), PDB may be defined as a packet delay budget, PER may be defined as a packet error rate, and PFI may be defined as a packet flow identifier.

[0108] In some examples (e.g., when applied to L2-based relays), the multipath rules may be implemented at the RRC layer. For example, the ProSe layer may provide service information to the RRC layer, and the UE 115-a may determine one or more communication parameters from the service information according to the multipath rules at the RRC layer. The UE 115-a may then establish the second path 210 according to the determined one or more communication parameters.

[0109] Below is a table illustrating an example of multipath rules when configured in the RRC layer:

[0110] Table 2: Multipath rules in the RRC layer

[0111]

[0112] In some examples, when the ProSe layer provides the QoS flow and QoS parameters to the RRC layer, the RRC layer may determine the path information based on the configured multipath rules. Figure 3 Additional details regarding applying multipath rules to the ProSe layer and the RRC layer are described.

[0113] In some examples (e.g., when applied to L3-based unmanned aerial vehicle (UAV) to UAV relay communications), UE 115-a may send an indication of service information and at least one of one or more communication parameters (e.g., access type) to UE 115-b or UE 115-c, where UE 115-b or UE 115-c may indicate to UE 115-a whether UE 115-b or UE 115-c supports or accepts at least one of the one or more communication parameters corresponding to the service information. UE 115-a may then establish a second path 210 based on the indication that UE 115-b or UE 115-c supports or accepts at least one of the one or more communication parameters.

[0114] In some examples where UE 115-c sends an indication of service information to UE 115-b or 115-c, UE 115-a, 115-b and / or 115-c may be configured or preconfigured with multipath rules in the ProSe layer. In some such examples, the multipath rules may be configured or preconfigured by the core network using a non-access stratum (NAS) message (e.g., a registration acceptance or UE configuration update message). In some examples, UE 115-a and / or 115-c may determine path information (e.g., path type, access type) for each service data flow (SDF). In some examples, the multipath rules may be defined as a mapping between path information (e.g., path type, access type) and service information (e.g., service type, application (APP) identifier (ID), packet filter, packet filter set). In some such examples, the access type may be an access technology, such as PC5 on a licensed band, PC5 on an unlicensed band, or a non-3GPP technology. In some examples, the mapping may be a list (e.g., an instance of service information may be mapped to a list of path information). In some examples, a source UE (e.g., UE 115-a) may utilize the service information to initiate a direct communication request (e.g., PC5-S) with a peer UE (e.g., UE 115-b in the case of a relay path, or UE 115-c in the case of a direct path). The peer UE (e.g., UE 115-b or UE 115-c) may feedback the accepted access type. If the peer UE (e.g., UE 115-b or UE 115-c) does not accept any access type based on the multipath rules, the peer UE (e.g., UE 115-b or UE 115-c) may deny service.

[0115] In some examples, applying the methods described herein may be associated with one or more advantages. For example, implementing multipath rules at UE 115-a, 115-b, or 115-c may enable UE 115-a, 115-b, or 115-c to use multiple paths while satisfying constraints specific to each instance of service information. Additionally or alternatively, a set of values ​​for a particular path may be associated with improved signaling characteristics (e.g., higher SNR, higher SINR, higher link efficiency) for a particular service compared to another set of values ​​for a particular service. If these values ​​are configured at UE 115-a, 115-b, and / or 115-c, UE 115-a, 115-b, and / or 115-c may be able to communicate based on the improved signaling characteristics for each instance of service information.

[0116] Figure 3An example of a network-controlled path establishment process 300 supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated. In some examples, the path establishment process 300 can be implemented by one or more aspects of the wireless communication system 100 and / or 200. For example, each of the UEs 115-e, 115-f, 115-g, and 115-h can be as described in reference Figure 1 Additionally or alternatively, UE 115-e may be an example of a UE 115 described herein. Figure 2 As described above, UE 115-a may be an example of a UE 115-f. Figure 2 As described above, the UE 115-b may be a UE 115-g. Figure 2 The example of UE 115-d described above, and UE 115-h may be as described in reference Figure 2 An example of a UE 115-c is described.

[0117] At 305-a, UE 115-e may be configured or preconfigured with multipath rules. Additionally, at 305-b, UE 115-h may be configured or preconfigured with multipath rules. In some examples, UE 115-e and 115-h may be configured with multipath rules at the ProSe layer. In such examples, when a new service is to be used, UE 115-e may determine one or more communication parameters (e.g., path or bearer information, such as path type, bearer type, or access type) according to the rules for each PC5QoS flow. In other examples, UE 115-e and 115-h may be configured with multipath rules at the RRC layer. In some such examples, multipath rules may be defined as a mapping between one or more communication parameters (e.g., bearer or path information, such as bearer type, path type, or access type) and service information. Additionally, multipath rules may include PC5QoS parameters and source and / or target link IDs. Additionally, rules may include service information (e.g., service type, application layer). In some such examples, UE 115-e may determine path information based on parameters received from upper layers (e.g., one or more communication parameters, PC5QoS parameters) and / or source or target link IDs.

[0118] At 310, UE 115-e may establish an end-to-end link with UE 115-h for communicating traffic associated with a service, the end-to-end link including a first path. In some such examples, the first path may include a relay UE (e.g., UE 115-f). In some such examples (e.g., when multipath rules are configured at the ProSe layer), UE 115-e may negotiate one or more communication parameters with UE 115-h (e.g., enhanced QoS negotiation may be performed). For example, UE 115-e may transmit values ​​of one or more communication parameters corresponding to specific service information and / or specific QoS parameters to UE 115-h (e.g., along the first path via UE 115-f). UE 115-h may determine whether to accept the values ​​of one or more communication parameters for each service and QoS parameter based on the configured or preconfigured multipath rules, and may respond to UE 115-e with the accepted values ​​of the service and communication parameters (e.g., along the first path via UE 115-f).

[0119] At 315, UE 115-e may discover UE 115-g and may select UE 115-g to serve as a relay UE.

[0120] At 320, UE 115-e may send an indication of a configuration for a second path between UE 115-e and UE 115-h via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service for which the end-to-end link is established. For example, UE 115-e may send one or more communication parameter values ​​for the second path to UE 115-h, wherein UE 115-h may determine whether to accept the second path addition. Additionally (e.g., if multipath rules are implemented at the RRC layer), UE 115-e may send one or more QoS parameters to UE 115-h, which UE 115-h may use to determine whether to accept the second path addition and the one or more communication parameter values ​​based on the multipath rules.

[0121] At 325-a, UE 115-e may perform PC5-S connection establishment with UE 115-g. Additionally, at 325-b, UE 115-h may perform PC5-S connection establishment with UE 115-g. After performing PC5-S connection establishment with UE 115-g, at 330, UE 115-e may send one or more end-to-end QoS profiles to UE 115-g. At 335-a, UE 115-e may perform PC5-RRC connection establishment with UE 115-g. Additionally, at 335-b, UE 115-h may perform PC5-RRC connection establishment with UE 115-g.

[0122] Figure 4 An example of a multipath rule implementation 400 for network control supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated. For example, the multipath rule implementation may include an intermediate layer 405 (e.g., an IP stack), a ProSe layer 410, and access type configurations 415 and 420. The access type configuration 420 may correspond to a PC-5 license, and the access type configuration 415 may correspond to PC5 license, PC5 unlicensed, and non-3GPP communications. In some examples, the ProSe layer 410 may include a multipath rule 425, wherein the multipath rule may map an aspect of the intermediate layer 405 (e.g., IP) to an access type configuration (e.g., one or both of the access type configurations 415 and 420).

[0123] Figure 5 An example of a process flow 500 for network control supporting multipath sidelink operation according to one or more aspects of the present disclosure is illustrated. In some examples, the process flow 500 can implement one or more aspects of the wireless communication system 100 and / or 200. For example, UE 115-i and / or UE 115-j can be as described in reference Figure 1 Additionally or alternatively, UE 115-i may be an example of a UE 115 as described above. Figure 2 The example of UE 115-a described above and UE 115-j may be as described in reference Figure 2 An example of a UE 115-c is described.

[0124] At 505, UE 115-i may establish an end-to-end link with UE 115-j for communicating traffic associated with a service, the end-to-end link including a first path.

[0125] At 510, UE 115-i may send an indication of a bearer configuration to UE 115-j, wherein the bearer configuration is based on service information associated with the service.

[0126] At 515, UE 115-j may send an indication to UE 115-i that UE 115-j accepts the bearer configuration.

[0127] At 520, UE 115-i may send an indication of a configuration for a second path between UE 115-i and UE 115-j to UE 115-j via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. In some examples, sending the indication of the configuration for the second path may include sending an indication of whether the second path is associated with a separate bearer or an independent bearer, an indication of a number of paths, an indication of an access type for the second path, or an indication of whether the second path is a direct path from UE 115-i to UE 115-j or a relay path, wherein the relay path includes at least one hop from UE 115-i to UE 115-j. In some examples, the service information may include an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0128] At 525, UE 115-i may communicate traffic associated with the service with UE 115-j via the first path or the second path based on sending an indication of the configuration for the second path. In some examples, communicating traffic associated with the service via the first path or the second path may be based on communicating an indication of whether the second path is associated with a separate bearer or an independent bearer, an indication of the number of paths, an indication of an access type for the second path, or an indication of whether the second path is a direct path or a relay path from UE 115-i to UE 115-j. In some examples, communicating traffic associated with the service via the first path or the second path is based on receiving an indication that UE 115-j accepts the bearer configuration.

[0129] In some examples, UE 115-i may send an indication of the service information via the end-to-end link. Additionally, UE 115-j may send an indication of a subset of the access type set to UE 115-i. In some such examples, communicating traffic associated with the service via the first path or the second path may be based on communicating the indication of the subset of the access type set.

[0130] In some examples, UE 115-i may determine a configuration for a second path at a first layer of UE 115-i based on the service information, and may provide a configuration for the second path and an indication of a QoS flow to a second layer of UE 115-i. In some such examples, communicating the traffic associated with the service via the first path or the second path is based on providing a configuration for the second path and an indication of a QoS flow to a second layer of UE 115-i. Additionally or alternatively, UE 115-i may provide service information and QoS flows to a second layer of UE 115-i by the first layer of UE 115-i. UE 115-i may determine a configuration for the second path at a second layer based on the provided service information. In some such examples, communicating the traffic associated with the service via the first path or the second path may be based on determining a configuration for the second path at a second layer. In some examples, UE 115-i may be provided by a first layer of UE 115-i with an identifier of UE 115-i, an identifier of UE 115-k, or both, wherein determining a configuration for a second path is based on the identifier of UE 115-i, the identifier of UE 115-j, or both. In some examples, the first layer may be a ProSe layer, and the second layer may be an RRC layer.

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

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

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

[0134] The communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or various components thereof may be examples of means for performing various aspects of network control of multipath sidelink operations as described herein. For example, the communication manager 620, the receiver 610, the transmitter 615, or various combinations thereof or components thereof may support methods for performing one or more of the functions described herein.

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

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

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

[0138] According to examples as disclosed herein, the communication manager 620 may support wireless communication at the first UE. For example, the communication manager 620 may be configured to or otherwise support a component for establishing an end-to-end link with a second UE for communicating a service associated with the service, the end-to-end link including a first path. The communication manager 620 may be configured to or otherwise support a component for sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The communication manager 620 may be configured to or otherwise support a component for communicating the service associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0139] Additionally or alternatively, according to examples as disclosed herein, the communication manager 620 may support wireless communication at the first UE. For example, the communication manager 620 may be configured to or otherwise support a component for establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link comprising a first path. The communication manager 620 may be configured to or otherwise support a component for receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The communication manager 620 may be configured to or otherwise support a component for communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0140] By including or configuring a communications manager 620 according to examples as described herein, a device 605 (e.g., a processor controlling or otherwise coupled to a receiver 610, a transmitter 615, a communications manager 620, or a combination thereof) may support techniques for the device 605 to satisfy constraints specific to each instance of service information and / or may enable the device to establish a multipath configuration having values ​​of communications parameters that exhibit improved signal characteristics as compared to other values ​​of the communications parameters.

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

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

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

[0144] Device 705 or its various components may be examples of components for performing various aspects of network control of multipath side link operations as described herein. For example, communication manager 720 may include link establishment component 725, path configuration transmitter 730, business communication component 735, path configuration receiver 740, or any combination thereof. Communication manager 720 may be an example of various aspects of communication manager 620 as described herein. In some examples, communication manager 720 or its various components may be configured to perform various operations (e.g., receive, obtain, monitor, output, send) using or otherwise in conjunction with receiver 710, transmitter 715, or both. For example, communication manager 720 may receive information from receiver 710, transmit information to transmitter 715, or integrate with receiver 710, transmitter 715, or both in combination to obtain information, output information, or perform various other operations as described herein.

[0145] According to examples as disclosed herein, the communication manager 720 may support wireless communication at the first UE. The link establishment component 725 may be configured to or otherwise support components for establishing an end-to-end link with the second UE for communicating traffic associated with the service, the end-to-end link comprising a first path. The path configuration transmitter 730 may be configured to or otherwise support components for sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The traffic communication component 735 may be configured to or otherwise support components for communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0146] Additionally or alternatively, according to examples as disclosed herein, the communication manager 720 may support wireless communication at the first UE. The link establishment component 725 may be configured to or otherwise support a component for establishing an end-to-end link with the second UE for communicating traffic associated with the service, the end-to-end link comprising a first path. The path configuration receiver 740 may be configured to or otherwise support a component for receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The traffic communication component 735 may be configured to or otherwise support a component for communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0147] Figure 8 A block diagram 800 of a communication manager 820 supporting network control of multipath side link operations according to one or more aspects of the present disclosure is shown. The communication manager 820 may be an example of aspects of the communication manager 620, the communication manager 720, or both as described herein. The communication manager 820 or its various components may be examples of components for performing various aspects of network control of multipath side link operations as described herein. For example, the communication manager 820 may include a link establishment component 825, a path configuration transmitter 830, a business communication component 835, a path configuration receiver 840, a bearer configuration indication receiver 845, a path configuration determination component 850, a bearer configuration indication transmitter 855, a service information indication component 860, an access type indication component 865, or any combination thereof. Each of these components may communicate directly or indirectly with each other (e.g., via one or more buses).

[0148] According to examples as disclosed herein, the communication manager 820 may support wireless communication at the first UE. The link establishment component 825 may be configured to or otherwise support components for establishing an end-to-end link with the second UE for communicating traffic associated with the service, the end-to-end link comprising a first path. The path configuration transmitter 830 may be configured to or otherwise support components for sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The traffic communication component 835 may be configured to or otherwise support components for communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0149] In some examples, to support sending an indication of a configuration for a second path, the path configuration transmitter 830 may be configured as or otherwise support components for sending an indication of whether the second path is associated with a separate bearer or an independent bearer via an end-to-end link, wherein traffic associated with the service is communicated via the first path or the second path based on sending an indication of whether the second path is associated with a separate bearer or an independent bearer.

[0150] In some examples, to support sending an indication of a configuration for a second path, the path configuration transmitter 830 may be configured as or otherwise support components for sending an indication of the number of paths via an end-to-end link, wherein communication of traffic associated with the service via the first path or the second path is based on sending the indication of the number of paths.

[0151] In some examples, to support sending an indication of a configuration for a second path, the path configuration transmitter 830 may be configured as or otherwise support components for sending an indication of an access type to the second path via an end-to-end link, wherein communication of traffic associated with the service via the first path or the second path is based on sending the indication of the access type to the second path.

[0152] In some examples, the indication of the access type includes an indication of a set of access types, and the service information indication component 860 may be configured to or otherwise support a component for sending an indication of service information via an end-to-end link. In some examples, the indication of the access type includes an indication of a set of access types, and the access type indication component 865 may be configured to or otherwise support a component for receiving an indication of a subset of the set of access types from a second UE. In some examples, the indication of the access type includes an indication of a set of access types, and the service communication component 835 may be configured to or otherwise support a component for communicating services associated with the service via a first path or a second path based on receiving an indication of a subset of the set of access types.

[0153] In some examples, to support sending an indication of a configuration for a second path, the path configuration transmitter 830 may be configured as or otherwise support components for sending an indication of whether the second path is a direct path or a relay path from the first UE to the second UE via an end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0154] In some examples, the path configuration transmitter 830 may be configured to or otherwise support a component for sending an indication of a bearer configuration to the second UE, wherein the bearer configuration is based on the service information. In some examples, the bearer configuration indication receiver 845 may be configured to or otherwise support a component for receiving an indication from the second UE that the second UE accepts the bearer configuration, wherein communicating the traffic associated with the service via the first path or the second path is based on receiving an indication that the second UE accepts the bearer configuration.

[0155] In some examples, the path configuration determination component 850 may be configured as or otherwise support components for determining a configuration for a second path at a first layer of the first UE based on the service information. In some examples, the path configuration determination component 850 may be configured as or otherwise support components for providing a configuration for the second path and an indication of a quality of service (QoS) flow to a second layer of the first UE. In some examples, the service communication component 835 may be configured as or otherwise support components for communicating services associated with the service via the first path or the second path based on providing a configuration for the second path and an indication of a QoS flow to a second layer of the first UE.

[0156] In some examples, the first layer includes a proximity services layer and the second layer includes a radio resource control layer.

[0157] In some examples, the path configuration determination component 850 may be configured as or otherwise support a component for providing service information and a quality of service (QoS) flow from the first layer of the first UE to the second layer of the first UE. In some examples, the path configuration determination component 850 may be configured as or otherwise support a component for determining a configuration for the second path at the second layer based on the provided service information. In some examples, the service communication component 835 may be configured as or otherwise support a component for communicating a service associated with the service via the first path or the second path based on the configuration determined for the second path at the second layer.

[0158] In some examples, the path configuration determination component 850 may be configured as or otherwise support a component for providing, by a first layer of the first UE, an identifier of the first UE, an identifier of the second UE, or both, wherein determining the configuration for the second path is based on the identifier of the first UE, the identifier of the second UE, or both.

[0159] In some examples, the first layer includes a proximity services layer and the second layer includes a radio resource control layer.

[0160] In some examples, the service information includes an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0161] Additionally or alternatively, according to examples as disclosed herein, the communication manager 820 may support wireless communications at the first UE. In some examples, the link establishment component 825 may be configured to or otherwise support components for establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link comprising a first path. The path configuration receiver 840 may be configured to or otherwise support components for receiving an indication of a configuration for a second path between the first UE and the second UE via an end-to-end link, wherein the configuration for the second path is based on service information associated with the service. In some examples, the traffic communication component 835 may be configured to or otherwise support components for communicating traffic associated with a service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0162] In some examples, to support receiving an indication of a configuration for a second path, the path configuration receiver 840 may be configured as or otherwise support a component for receiving an indication of whether the second path is associated with a separate bearer or an independent bearer via an end-to-end link, wherein traffic associated with the service is communicated via the first path or the second path based on sending an indication of whether the second path is associated with a separate bearer or an independent bearer.

[0163] In some examples, to support receiving an indication of a configuration for a second path, path configuration receiver 840 may be configured as or otherwise support components for receiving an indication of a number of paths via an end-to-end link, wherein communication of traffic associated with the service via the first path or the second path is based on sending the indication of the number of paths.

[0164] In some examples, to support receiving an indication of a configuration for a second path, path configuration receiver 840 may be configured as or otherwise support components for receiving an indication of an access type for the second path via an end-to-end link, wherein communication of traffic associated with the service via the first path or the second path is based on sending the indication of the access type for the second path.

[0165] In some examples, the indication of the access type includes an indication of a set of access types, and the service information indication component 860 may be configured to or otherwise support a component for receiving an indication of service information via an end-to-end link. In some examples, the indication of the access type includes an indication of a set of access types, and the access type indication component 865 may be configured to or otherwise support a component for sending an indication of a subset of the set of access types to the second UE. In some examples, the indication of the access type includes an indication of a set of access types, and the service communication component 835 may be configured to or otherwise support a component for communicating services associated with the service via a first path or a second path based on receiving an indication of a subset of the set of access types.

[0166] In some examples, to support receiving an indication of a configuration for a second path, the path configuration receiver 840 may be configured as or otherwise support components for receiving an indication of whether the second path is a direct path or a relay path from the first UE to the second UE via an end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0167] In some examples, the path configuration receiver 840 may be configured to or otherwise support a component for receiving an indication of a bearer configuration from a second UE, wherein the bearer configuration is based on the service information. In some examples, the bearer configuration indication transmitter 855 may be configured to or otherwise support a component for sending an indication of the first UE accepting the bearer configuration to the second UE, wherein communicating the traffic associated with the service via the first path or the second path is based on sending an indication of the first UE accepting the bearer configuration.

[0168] In some examples, the service information includes an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

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

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

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

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

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

[0174] According to examples as disclosed herein, the communication manager 920 may support wireless communication at the first UE. For example, the communication manager 920 may be configured to or otherwise support a component for establishing an end-to-end link with a second UE for communicating a service associated with the service, the end-to-end link comprising a first path. The communication manager 920 may be configured to or otherwise support a component for sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The communication manager 920 may be configured to or otherwise support a component for communicating the service associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0175] Additionally or alternatively, according to examples as disclosed herein, the communication manager 920 may support wireless communication at the first UE. For example, the communication manager 920 may be configured to or otherwise support a component for establishing an end-to-end link with a second UE for communicating a service associated with the service, the end-to-end link comprising a first path. The communication manager 920 may be configured to or otherwise support a component for receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The communication manager 920 may be configured to or otherwise support a component for communicating a service associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path.

[0176] By including or configuring a communications manager 920 according to examples as described herein, the device 905 may support techniques for the device 905 to satisfy constraints specific to each instance of service information and / or may enable the device to establish a multipath configuration having values ​​of communications parameters that exhibit improved signal characteristics compared to other values ​​of the communications parameters.

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

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

[0179] At 1005, the method may include establishing an end-to-end link with a second UE for communicating traffic associated with the service, the end-to-end link including a first path. The operations of 1005 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1005 may be performed as described in reference to Figure 8 The described link establishment component 825 is performed.

[0180] At 1010, the method may include sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The operations of 1010 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1010 may be performed as described in reference to Figure 8 The described path configures the transmitter 830 to execute.

[0181] At 1015, the method may include communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path. The operations of 1015 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1015 may be performed as described in reference to Figure 8 The described business communication component 835 is executed.

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

[0183] At 1105, the method may include establishing an end-to-end link with a second UE for communicating traffic associated with the service, the end-to-end link including a first path. The operations of 1105 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1105 may be performed as described in reference to Figure 8 The described link establishment component 825 is performed.

[0184] At 1110, the method may include sending an indication of whether the second path is associated with a separate bearer or an independent bearer via the end-to-end link, wherein whether the second path is associated with a separate bearer or an independent bearer is based at least in part on service information associated with the service. The operations of 1110 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1110 may be performed as described in reference to Figure 8 The described path configures the transmitter 830 to execute.

[0185] At 1115, the method may include communicating traffic associated with the service with the second UE via the first path or the second path based at least in part on sending an indication of whether the second path is associated with a separate bearer or an independent bearer. The operations of 1115 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1115 may be performed as described in reference to Figure 8 The described business communication component 835 is executed.

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

[0187] At 1205, the method may include establishing an end-to-end link with a second UE for communicating traffic associated with the service, the end-to-end link including a first path. The operations of 1205 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1205 may be performed as described in reference to Figure 8 The described link establishment component 825 is performed.

[0188] At 1210, the method may include receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based on service information associated with the service. The operations of 1210 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1210 may be performed as described in reference to Figure 8 The described path configures the receiver 840 to execute.

[0189] At 1215, the method may include communicating traffic associated with the service with the second UE via the first path or the second path based on sending an indication of the configuration for the second path. The operations of 1215 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1215 may be performed as described in reference to Figure 8 The described business communication component 835 is executed.

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

[0191] At 1305, the method may include establishing an end-to-end link with a second UE for communicating traffic associated with the service, the end-to-end link including a first path. The operations of 1305 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1305 may be performed as described in reference to Figure 8 The described link establishment component 825 is performed.

[0192] At 1310, the method may include receiving, via the end-to-end link, an indication of whether the second path is associated with a separate bearer or an independent bearer, wherein whether the second path is associated with a separate bearer or an independent bearer is based at least in part on service information associated with the service. The operations of 1310 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1310 may be performed as described in reference to Figure 8 The described path configures the receiver 840 to execute.

[0193] At 1315, the method may include communicating traffic associated with the service with the second UE via the first path or the second path based at least in part on sending an indication of whether the second path is associated with a separate bearer or an independent bearer. The operations of 1315 may be performed according to examples as disclosed herein. In some examples, aspects of the operations of 1315 may be performed as described in reference to Figure 8 The described business communication component 835 is executed.

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

[0195] Aspect 1: A method for performing wireless communications at a first UE, the method comprising: establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link comprising a first path; sending an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based at least in part on service information associated with the service; and communicating traffic associated with the service with the second UE via the first path or the second path based at least in part on sending the indication of the configuration for the second path.

[0196] Aspect 2: A method according to Aspect 1, wherein sending the indication of the configuration for the second path includes: sending an indication of whether the second path is associated with a separate bearer or an independent bearer via the end-to-end link, wherein the communication of the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of whether the second path is associated with the separate bearer or the independent bearer.

[0197] Aspect 3: A method according to any one of Aspects 1 to 2, wherein sending the indication of the configuration for the second path includes: sending an indication of the number of paths via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of the number of paths.

[0198] Aspect 4: A method according to any one of Aspects 1 to 3, wherein sending the indication of the configuration for the second path includes: sending an indication of an access type to the second path via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of the access type to the second path.

[0199] Aspect 5: A method according to Aspect 4, wherein the indication of the access type includes an indication of an access type set, and the method further includes: sending an indication of the service information via the end-to-end link; receiving an indication of a subset of the access type set from the second UE; and communicating the business associated with the service via the first path or the second path based at least in part on receiving the indication of the subset of the access type set.

[0200] Aspect 6: A method according to any one of Aspects 1 to 5, wherein sending the indication of the configuration for the second path includes: sending an indication of whether the second path is a direct path or a relay path from the first UE to the second UE via the end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0201] Aspect 7: According to the method described in any one of Aspects 1 to 6, the method further includes: sending an indication of a bearer configuration to the second UE, wherein the bearer configuration is at least partially based on the service information; and receiving an indication from the second UE that the second UE accepts the bearer configuration, wherein the communication of the service associated with the service via the first path or the second path is at least partially based on receiving the indication that the second UE accepts the bearer configuration.

[0202] Aspect 8: According to the method described in any one of Aspects 1 to 7, the method further includes: determining the configuration for the second path at the first layer of the first UE based at least in part on the service information; and providing the configuration for the second path and an indication of a quality of service (QoS) flow to the second layer of the first UE; and communicating the business associated with the service via the first path or the second path based at least in part on providing the configuration for the second path and the indication of the QoS flow to the second layer of the first UE.

[0203] Aspect 9: The method according to aspect 8, wherein the first layer comprises a proximity service layer, and the second layer comprises a radio resource control layer.

[0204] Aspect 10: According to the method described in any one of Aspects 1 to 9, the method further includes: providing the service information and quality of service (QoS) flow to the second layer of the first UE by the first layer of the first UE; determining the configuration for the second path at the second layer based at least in part on the provided service information; and communicating the business associated with the service via the first path or the second path based at least in part on the configuration for the second path determined at the second layer.

[0205] Aspect 11: According to the method according to Aspect 10, the method also includes: providing an identifier of the first UE, an identifier of the second UE, or both by the first layer of the first UE, wherein determining the configuration for the second path is at least partially based on the identifier of the first UE, the identifier of the second UE, or both.

[0206] Aspect 12: The method according to aspect 11, wherein the first layer comprises a proximity service layer, and the second layer comprises a radio resource control layer.

[0207] Aspect 13: The method according to any one of aspects 1 to 12, wherein the service information comprises an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0208] Aspect 14: A method for performing wireless communications at a first UE, the method comprising: establishing an end-to-end link with a second UE for communicating traffic associated with a service, the end-to-end link comprising a first path; receiving an indication of a configuration for a second path between the first UE and the second UE via the end-to-end link, wherein the configuration for the second path is based at least in part on service information associated with the service; and communicating traffic associated with the service with the second UE via the first path or the second path based at least in part on sending the indication of the configuration for the second path.

[0209] Aspect 15: A method according to Aspect 14, wherein receiving the indication of the configuration for the second path includes: receiving an indication of whether the second path is associated with a separate bearer or an independent bearer via the end-to-end link, wherein the communication of the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of whether the second path is associated with the separate bearer or the independent bearer.

[0210] Aspect 16: A method according to any one of Aspects 14 to 15, wherein receiving the indication of the configuration for the second path includes: receiving an indication of the number of paths via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of the number of paths.

[0211] Aspect 17: A method according to any one of Aspects 14 to 16, wherein receiving the indication of the configuration for the second path includes: receiving an indication of an access type to the second path via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is at least partially based on sending the indication of the access type to the second path.

[0212] Aspect 18: A method according to Aspect 17, wherein the indication of the access type includes an indication of an access type set, and the method further includes: receiving an indication of the service information via the end-to-end link; sending an indication of a subset of the access type set to the second UE; and communicating the traffic associated with the service via the first path or the second path based at least in part on receiving the indication of the subset of the access type set.

[0213] Aspect 19: A method according to any one of Aspects 14 to 18, wherein receiving the indication of the configuration for the second path includes: receiving an indication of whether the second path is a direct path or a relay path from the first UE to the second UE via the end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

[0214] Aspect 20: According to the method described in any one of Aspects 14 to 19, the method further includes: receiving an indication of a bearer configuration from the second UE, wherein the bearer configuration is at least partially based on the service information; and sending an indication to the second UE that the first UE accepts the bearer configuration, wherein the communication of the service associated with the service via the first path or the second path is at least partially based on sending the indication that the first UE accepts the bearer configuration.

[0215] Aspect 21: The method according to any one of aspects 14 to 20, wherein the service information comprises an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

[0216] Aspect 22: An apparatus for performing wireless communications at a first UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 1 to 13.

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

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

[0219] Aspect 25: An apparatus for performing wireless communications at a first UE, the apparatus comprising: a processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method according to any one of Aspects 14 to 21.

[0220] Aspect 26: An apparatus for wireless communication at a first UE, the apparatus comprising at least one component for performing a method according to any one of aspects 14 to 21.

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

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

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

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

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

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

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

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

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

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

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

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

Claims

1. A method for wireless communication at a first user equipment (UE), the method comprising: establishing, with a second UE, an end-to-end link for communicating traffic associated with the service, the end-to-end link comprising a first path; sending, via the end-to-end link, an indication of a configuration for a second path between the first UE and the second UE, wherein the configuration for the second path is based at least in part on service information associated with the service; as well as Based at least in part on sending the indication of the configuration for the second path, communicating traffic associated with the service with the second UE via the first path or the second path.

2. The method of claim 1 , wherein sending the indication of the configuration for the second path comprises: and sending, via the end-to-end link, an indication of whether the second path is associated with a separate bearer or an independent bearer, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of whether the second path is associated with the separate bearer or the independent bearer.

3. The method of claim 1 , wherein sending the indication of the configuration for the second path comprises: An indication of a number of paths is sent via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the number of paths.

4. The method of claim 1 , wherein sending the indication of the configuration for the second path comprises: An indication of an access type to the second path is sent via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the access type to the second path.

5. The method of claim 4, wherein the indication of the access type comprises an indication of an access type set, the method further comprising: sending an indication of the service information via the end-to-end link; receiving, from the second UE, an indication of a subset of the set of access types; as well as Based at least in part on receiving the indication of the subset of the set of access types, the traffic associated with the service is communicated via the first path or the second path.

6. The method of claim 1 , wherein sending the indication of the configuration for the second path comprises: An indication of whether the second path is a direct path or a relay path from the first UE to the second UE is sent via the end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

7. The method according to claim 1, further comprising: sending an indication of a bearer configuration to the second UE, wherein the bearer configuration is based at least in part on the service information; as well as An indication is received from the second UE that the second UE accepts the bearer configuration, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on receiving the indication that the second UE accepts the bearer configuration.

8. The method according to claim 1, further comprising: determining, at a first layer of the first UE, the configuration for the second path based at least in part on the service information; providing the configuration for the second path and an indication of a quality of service (QoS) flow to a second layer of the first UE; as well as The traffic associated with the service is communicated via the first path or the second path based at least in part on providing the configuration for the second path and the indication of the QoS flow to the second layer of the first UE.

9. The method of claim 8, wherein the first layer comprises a proximity service layer and the second layer comprises a radio resource control layer.

10. The method according to claim 1, further comprising: providing, by a first layer of the first UE, the service information and a quality of service (QoS) flow to a second layer of the first UE; determining, at the second layer, the configuration for the second path based at least in part on the provided service information; as well as The traffic associated with the service is communicated via the first path or the second path based at least in part on determining the configuration for the second path at the second layer.

11. The method according to claim 10, further comprising: An identifier of the first UE, an identifier of the second UE, or both is provided by the first layer of the first UE, wherein determining the configuration for the second path is based at least in part on the identifier of the first UE, the identifier of the second UE, or both.

12. The method of claim 11, wherein the first layer comprises a proximity service layer and the second layer comprises a radio resource control layer.

13. The method of claim 1, wherein the service information comprises an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

14. A method for wireless communication at a first user equipment (UE), the method comprising: establishing, with a second UE, an end-to-end link for communicating traffic associated with the service, the end-to-end link comprising a first path; receiving, via the end-to-end link, an indication of a configuration for a second path between the first UE and the second UE, wherein the configuration for the second path is based at least in part on service information associated with the service; as well as Based at least in part on sending the indication of the configuration for the second path, communicating traffic associated with the service with the second UE via the first path or the second path.

15. The method of claim 14, wherein receiving the indication of the configuration for the second path comprises: and receiving, via the end-to-end link, an indication of whether the second path is associated with a separate bearer or an independent bearer, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of whether the second path is associated with the separate bearer or the independent bearer.

16. The method of claim 14, wherein receiving the indication of the configuration for the second path comprises: An indication of a number of paths is received via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the number of paths.

17. The method of claim 14, wherein receiving the indication of the configuration for the second path comprises: An indication of an access type to the second path is received via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the access type to the second path.

18. The method of claim 17, wherein the indication of the access type comprises an indication of an access type set, the method further comprising: receiving, via the end-to-end link, an indication of the service information; sending an indication of a subset of the access type set to the second UE; as well as Based at least in part on receiving the indication of the subset of the set of access types, the traffic associated with the service is communicated via the first path or the second path.

19. The method of claim 14, wherein receiving the indication of the configuration for the second path comprises: An indication is received via the end-to-end link whether the second path is a direct path or a relay path from the first UE to the second UE, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

20. The method according to claim 14, further comprising: receiving an indication of a bearer configuration from the second UE, wherein the bearer configuration is based at least in part on the service information; as well as An indication is sent to the second UE that the first UE accepts the bearer configuration, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication that the first UE accepts the bearer configuration.

21. The method of claim 14, wherein the service information comprises an indication of a service type, an indication of an application layer, an indication of a packet filter set, or any combination thereof.

22. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establishing, with a second UE, an end-to-end link for communicating traffic associated with the service, the end-to-end link comprising a first path; sending, via the end-to-end link, an indication of a configuration for a second path between the first UE and the second UE, wherein the configuration for the second path is based at least in part on service information associated with the service; as well as Based at least in part on sending the indication of the configuration for the second path, communicating traffic associated with the service with the second UE via the first path or the second path.

23. The apparatus of claim 22, wherein the instructions for sending the indication of the configuration for the second path are executable by the processor to cause the apparatus to: and sending, via the end-to-end link, an indication of whether the second path is associated with a separate bearer or an independent bearer, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of whether the second path is associated with the separate bearer or the independent bearer.

24. The apparatus of claim 22, wherein the instructions for sending the indication of the configuration for the second path are executable by the processor to cause the apparatus to: An indication of a number of paths is sent via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the number of paths.

25. The apparatus of claim 22, wherein the instructions for sending the indication of the configuration for the second path are executable by the processor to cause the apparatus to: An indication of an access type to the second path is sent via the end-to-end link, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on sending the indication of the access type to the second path.

26. The apparatus of claim 25, wherein the indication of the access type comprises an indication of an access type set, and the instructions are further executable by the processor to cause the apparatus to: sending an indication of the service information via the end-to-end link; receiving, from the second UE, an indication of a subset of the set of access types; as well as Based at least in part on receiving the indication of the subset of the set of access types, the traffic associated with the service is communicated via the first path or the second path.

27. The apparatus of claim 22, wherein the instructions for sending the indication of the configuration for the second path are executable by the processor to cause the apparatus to: An indication of whether the second path is a direct path or a relay path from the first UE to the second UE is sent via the end-to-end link, wherein the relay path includes at least one hop from the first UE to the second UE via at least one relay UE.

28. The apparatus of claim 22, wherein the instructions are further executable by the processor to cause the apparatus to: sending an indication of a bearer configuration to the second UE, wherein the bearer configuration is based at least in part on the service information; and An indication is received from the second UE that the second UE accepts the bearer configuration, wherein communicating the traffic associated with the service via the first path or the second path is based at least in part on receiving the indication that the second UE accepts the bearer configuration.

29. The apparatus of claim 22, wherein the instructions are further executable by the processor to cause the apparatus to: determining, at a first layer of the first UE, the configuration for the second path based at least in part on the service information; providing the configuration for the second path and an indication of a quality of service (QoS) flow to a second layer of the first UE; as well as The traffic associated with the service is communicated via the first path or the second path based at least in part on providing the configuration for the second path and the indication of the QoS flow to the second layer of the first UE.

30. An apparatus for wireless communication at a first user equipment (UE), the apparatus comprising: processor; a memory coupled to the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to: establishing, with a second UE, an end-to-end link for communicating traffic associated with the service, the end-to-end link comprising a first path; receiving, via the end-to-end link, an indication of a configuration for a second path between the first UE and the second UE, wherein the configuration for the second path is based at least in part on service information associated with the service; as well as Based at least in part on sending the indication of the configuration for the second path, communicating traffic associated with the service with the second UE via the first path or the second path.

Images