Authorization for multipath relays

Abstract

According to certain embodiments, a method performed by a user equipment (UE) comprises receiving an indication from a network. The indication indicates whether the network supports multipath relays. The method further comprises determining, based at least in part on the indication from the network, whether to initiate communication with the network via a multipath relay. In response to determining to initiate communication with the network via the multipath relay, the method further comprises communicating via the multipath relay. The multipath relay comprises a path using a sidelink to a second UE.

Description

Authorization for Multipath RelaysRELATED APPLICATIONS

[0001] This application claims priority to U.S. Provisional Patent Application No. 63 / 527,425, filed on July 18, 2023, the disclosure and content of which is incorporated by reference herein in its entirety.TECHNICAL FIELD

[0002] Embodiments of the present disclosure are directed to wireless communications and more particularly to authorization for multipath relays.BACKGROUND

[0003] The Third Generation Partnership Project (3GPP) comprises standards organizations that develop technical specifications (TS) for mobile telecommunications, including technical specifications for Long Term Evolution (LTE), Fifth Generation (5G) New Radio (NR), and other mobile telecommunications technologies. The 3GPP organizes the technical specifications into releases identified by release number (e.g., Rel-12, Rel-13, and so on) . In general, a new release may include some functionality from a previous release and some new functionality. The 3GPP technical specifications describe many features. Examples of certain features relevant to the present disclosure include sidelink communication and relay communication, such as layer 2 (L2) user equipment (UE)-to-network (NW) relays (L2 UE-to- NW relays) and multiple path relays (referred to as “multipath” or “multi-path” relays). The following paragraphs provide an introduction of these features.Sidelink

[0004] 3GPP Rel-12 specifies LTE device-to-device (D2D) technology, also known as sidelink (SL) or the PC5 interface. This specification targets Proximity Services (ProSe) communication and discovery use cases. 3GPP Rel-13 and Rel-14 enhance support for such services and extensively redesign the LTE sidelink to support vehicular communications, such as vehicle-to-vehicle (V2V) communications and vehicle-to-everything (V2X). 3GPP Rel-15 provides further enhancements from the point-of-view of the lower radio layers. LTE SL uses broadcast communication where a transmission from a UE targets any receiver within range.

[0005] 3GPP Rel-16 introduces the sidelink for NR. This specification facilitates certain D2D use cases (such as certain V2V and V2X use cases) by including more stringentrequirements for the NR SL than those that typically could be served by LTE SL. To meet these stringent requirements, the NR SL can perform broadcast, groupcast, and unicast communications. Groupcast communication typically targets a subset of receivers (e.g., vehicles) near the transmitter as the intended receivers of a message. Unicast communication targets a single intended receiver.

[0006] Both the LTE SL and the NR SL can operate with and without network coverage and with varying degrees of interaction between the UEs and the NW, including support for standalone, network-less operation.

[0007] 3GPP Rel-17 adds enhancements to certain NR sidelink features specified in Rel- 16. Certain enhancements support public safety use cases. In some scenarios, public safety services need to operate out of network coverage or with partial network coverage (such as when one UE within cellular NW coverage facilitates communication between the cellular NW and another UE outside of the cellular NW coverage). The need to operate out of network coverage or with partial network coverage can occur when a public safety event causes network infrastructure to be destroyed, partially destroyed, or otherwise not available, such as during indoor firefighting, forest firefighting, earthquake rescue, sea rescue, etc. Thus, coverage extension is a crucial enabler for public safety, both for services communicated between a UE and a cellular network and for services communicated between UEs via sidelink.

[0008] In Rel-17, 3GPP introduced a work item description (WID) on NR sidelink relay, described in RP-212601, “New WID on NR Side link Relay,” TSG RAN#93e. The WID aims to further explore coverage extension for sidelink-based communication, including both UE- to-NW relay for cellular coverage extension and UE-to-UE relay for sidelink coverage extension. Now the work has proceeded to the normative phase. Another WID only considers a UE-to-NW relay, see RP-213585, “New WID on NR Sidelink Relay Enhancements,” TSG RAN#94-e. In addition to public safety use cases, 3GPP has designed an NR sidelink relay work item to support other commercial use cases that would also benefit from the coverage extension. 3GPP specifies two solutions for UE-to-NW relaying, namely L2 UE-to-NW relaying and L3 (layer 3) UE-to-NW relaying.

[0009] A 3GPP RAN plenary session (described in RP-213585) began RAN#94 discussions to identify detailed motivations and work areas for evolving NR SL and NR SL relays in Rel-18. For NR SL relays, support for a multipath operation with relays was agreed for its potential to improve the reliability / robustness as well as throughput.

[0010] Figure 1A and Figure IB each illustrates an example of a communication system comprising a network node 2, a first UE 4A, and a second UE 4B. Examples of the networknode 2 include a radio network node, such as a base station (e.g., gNB). Examples of the UEs 4 A and 4B include UEs that support D2D communication. The communication system may include other network nodes, such as one or more core network (CN) nodes (not shown).

[0011] The network node 2 communicates with the first UE 4A via a first direct path 6A. The network node 2 communicates with the second UE 4B via a second direct path 6B. Further, in the communication system shown in Figure IB, the first UE 4A communicates with the second UE 4B via a sidelink path 8.

[0012] The sidelink path 8 shown in Figure IB facilitates a multipath scenario for the first UE 4A. The first UE 4A uses a multipath operation with a relay to connect to the network node 2 via both the first direct path 6A and an indirect path 10. The indirect path 10 between the first UE 4A and the network node 2 includes the sidelink path 8 (which provides a UE-to-Relay UE path from the first UE 4A to the second UE 4B) and the second direct path 6B (where the second UE 4B provides a Relay UE-to-Network path to the network node 2). In the arrangement shown in Figure IB, the first UE 4A may be referred to interchangeably as a multipath UE or as a remote UE, and the second UE 4B may be referred to as a relay UE.

[0013] In one example configuration of Figure IB, the first direct path 6A corresponds to a first Uu interface, the second direct path 6B corresponds to a second Uu interface, and the sidelink path 8 corresponds to a PC5 interface. In this example, in the first direct path 6A, the first UE 4A communicates with the network node 2 (e.g., gNB) over the first Uu interface. In the indirect path 10, the first UE 4A communicates with the second UE 4B (relay UE) over the PC5 interface corresponding to the sidelink path 8, and the second UE 4B (relay UE) relays the communication to / from the network node 2 (e.g., gNB) over the second Uu interface corresponding to the second direct path 6B. That is, in the indirect path 10, the first UE 4A communicates with the network node 2 (e.g., gNB) indirectly via the sidelink path 8 / PC5 interface and the second direct path 6B / second Uu interface over a single hop. The multipath operation offers the first UE 4A a choice to perform a transmission (a) over either the first direct path 6A or over the indirect path 10, or (b) over both the first direct path 6A and the indirect path 10, thereby allowing flexibility for the transmission.

[0014] Although the paragraph above describes an example where the sidelink 8 is based on a PC5 interface, 3GPP has also agreed to study the scenario where the sidelink 8 between the multipath UE / remote UE (e.g., UE 4A) and the relay UE (e.g., UE 4B) is based on some form of an ideal link (instead of PC5). An ideal link generally refers to a device-to-device link specified outside the scope of 3GPP. The ideal link can be formed using any non-3GPP based access. For example, the ideal link may use a proprietary format, or the ideal link may bespecified by a standard other than a 3GPP standard (non-limiting examples of other standards may include a Wi-Fi standard, a Bluetooth standard, a Zigbee standard, or other standard specifying device-to-device communication). Although a 3GPP standard does not specify the details of the ideal link, 3GPP may still refer to the ideal link at least conceptually, for example, to describe relaying communication between a remote UE and a 3GPP network using both an ideal link (for communication between the remote UE and a relay UE) and a 3GPP link (for communication between the relay UE and the 3GPP network). 3GPP may use any suitable terminology for the ideal link, such as a non-3GPP link, an N3C link, etc. See, e.g., S2- 2307707, “Reply LS to SA2 on authorization for multi-path Scenario 2,” TSG-WG SA2 Meeting #157 for an example of 3GPP discussing a non-3GPP link.

[0015] Turning to Figures 2-4, examples of user plane and control plane protocol stacks that may be supported by the network node 2 (e.g., gNB) and the UEs 4 are provided.Layer 2 UE-to-Network relay

[0016] 3GPP TS 23.304, “Proximity based Services (ProSe) in the 5G System (5GS),” describes the L2 UE-to-NW relay, also known as the L2 U2N relay. See, e.g., TS 23.304 V18.0.0 (2022-12) at section 6.I.2.3.2.

[0017] Figure 2 illustrates the protocol stack for the user plane transport, related to a protocol data unit (PDU) session, including a Layer 2 UE-to-Network Relay UE. The PDU layer corresponds to the PDU carried between the Remote UE and the Data Network (DN) over the PDU session. It is important to note that the two endpoints of the Packet Data Convergence Protocol (PDCP) link are the Remote UE and the gNB. The relay function is performed below PDCP. This ensures data security between the Remote UE and the gNB without exposing raw data at the UE-to-Network Relay UE.

[0018] The adaptation layer within the UE-to-Network Relay UE can differentiate between signaling radio bearers (SRBs) and data radio bearers (DRBs) for a particular Remote UE. The adaption relay layer is also responsible for mapping PC5 traffic to one or more DRBs of the Uu.

[0019] Figure 3 illustrates a control plane for a L2 UE-to-Network Relay UE, including the protocol stack of the non-access stratum (NAS) connection for the Remote UE to the NAS- MM (mobility management) and NAS-SM (session management) components. The NAS messages are transparently transferred between the Remote UE and 5G access network (5G- AN) over the Layer 2 UE-to-Network Relay UE. The UE-to-Network Relay UE relays the PDUs from the signaling radio bearer without any modifications.Multipath Relays based on Ideal link

[0020] Figure 4 illustrates a protocol stack for multipath relays with an ideal link (such as the ideal link described above with respect to Figures 1A-1B). The example in Figure 4 includes the protocol stack for the control-plane and user-plane. The protocol stack is based on progress from a previous 3GPP meeting of the radio access network 2 (RAN2) working group.SUMMARY

[0021] There currently exist certain challenge(s). Previous RAN2 meetings discussed the issue of authorization and provisioning for multipath relays based on an ideal link. Further, a liaison statement (LS) was sent to System Architecture Working Group 2 (SA2) to ask them whether this scenario requires such an authorization and subscription function. In reply, SA2 provided document S2-2307707, which states:Based on the WID on NR SL relay enh and RAN2 agreements related to Scenario 2, SA2's understanding is that in Scenario 2, non-3GPP link (hut not PC 5 link) is used between a relay UE and a remote UE. SA2 has neither studied nor investigated this Scenario.Therefore, SA2 would like to provide the following answer to the question from RAN2:■ Multi-path transmission authorization and subscription function for Scenario 2 in all cases is out of SA2 scope.

[0022] From SA2’s reply, there is no authorization / subscription function defined as SA2 has not studied the ideal link (i.e., non-3GPP link). This could result in cases where no authorization function will be applied for a multipath relay with an ideal link. By not applying an authorization function in such cases, any pair of UEs with individual (Uu) authorizations to access the network can also access the network using the multipath relay with an ideal link. However, from the network's point of view, this could result in uncontrollable pairing of UEs in the network (without a subscription) and requesting for configurations, even if the network does not support this feature. Further, a lack of authorization functions could lead to overutilization of network resources and increased system interference. Furthermore, the network may not be able to control the increased system interference given that it cannot control the pairing of the UEs for multipath relays with an ideal link.

[0023] In addition, the current authorization / provisioning framework specified for 5G ProSe by SA2 in 3GPP TS 23.304 V18.0.0 (2022-12) for the case of multipath relays over the PC5 interface cannot be reused because non-3GPP link between UEs is not in the scope of 5G ProSe work performed by SA2.

[0024] In addition, SA2 is discussing potential Rel-19 work items for ProSe. The candidates include Layer-2 UE-to-Network relaying using a non-3GPP access between the remote UE and relay UE. In which case, SA2 may start working on the authorization / provisioning framework in Rel-19.

[0025] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. As an example, on a cell-level, certain embodiments introduce a flag to enable / disable the multipath relay with ideal link functionality. As another example, on a UE-level, certain embodiments add new subscription data for multipath via direct Uu path and via non-3GPP link. This information can be exchanged between the Unified Data Management (UDM) / Access & Mobility Management Function (AMF) and the RAN. Certain embodiments provide network-based authorization of the multipath relays with ideal link functionality on a cell-level (by introducing a flag in the broadcast message), on a UE-level (by introducing new subscription data for this feature), or both.

[0026] According to certain embodiments, a method performed by a UE comprises receiving an indication from a network. The indication indicates whether the network supports multipath relays. The method further comprises determining, based at least in part on the indication from the network, whether to initiate communication with the network via a multipath relay. In response to determining to initiate communication with the network via the multipath relay, the method further comprises communicating via the multipath relay. The multipath relay comprises a path using a sidelink to a second UE.

[0027] According to certain embodiments, a user equipment comprises processing circuitry and power supply circuitry. The processing circuitry is configured to receive an indication from a network. The indication indicates whether the network supports multipath relays. The processing circuitry is further configured to determine, based at least in part on the indication from the network, whether to initiate communication with the network via a multipath relay. In response to determining to initiate communication with the network via the multipath relay, the processing circuitry is further configured to communicate via the multipath relay. The multipath relay comprises a path using a sidelink to a second UE. The power supply circuitry is configured to supply power to the processing circuitry.

[0028] According to certain embodiments, a method performed by a network node comprises obtaining information indicating whether the network node supports multipath relays. The method further comprises communicating, to one or more UEs, an indication whether the network node supports multipath relays, the indication based on the obtained information.

[0029] According to certain embodiments, a network node comprises processing circuitry and power supply circuitry. The processing circuitry is configured to obtain information indicating whether the network node supports multipath relays. The processing circuitry is further configured to communicate, to one or more UEs, an indication whether the network node supports multipath relays, the indication based on the obtained information. The power supply circuitry is configured to supply power to the processing circuitry.

[0030] Certain embodiments may provide one or more of the following technical advantage(s). In certain embodiments, the network has control over the pairing of UEs using a sidelink, such as an ideal link. As a result, the network has control over interference that can be caused by such pairing. Certain embodiments can prevent rogue UEs from accessing the network by pairing up with another UE. Certain embodiments can enable and disable this feature when necessary. Other advantages may be readily apparent to one having skill in the art. Certain embodiments may have none, some, or all of the recited advantages.BRIEF DESCRIPTION OF THE DRAWINGS

[0031] For a more complete understanding of the disclosed embodiments and their features and advantages, reference is now made to the drawings, in which:

[0032] Figure 1A illustrates an example of interfaces between a network node and two UEs.

[0033] Figure IB illustrates an example of a multipath scenario.

[0034] Figure 2 illustrates an example of a user plane stack for a Layer 2 (L2) UE-to- Network Relay UE.

[0035] Figure 3 illustrates an example of a control plane for an L2 UE-to-Network Relay UE.

[0036] Figure 4 illustrates an example of a control plane (CP) and user plane (UP) protocol stack for multipath relays with an ideal link.

[0037] Figure 5 illustrates an example of UE-level control based on subscription information in accordance with some embodiments.

[0038] Figure 6 illustrates an example of UE-level control based on subscription information in accordance with some embodiments.

[0039] Figure 7 shows an example of a communication system in accordance with some embodiments.

[0040] Figure 8 shows an example of a user equipment (UE) in accordance with some embodiments.

[0041] Figure 9 shows an example of a network node in accordance with some embodiments.

[0042] Figure 10 shows an example of a virtualization environment in accordance with some embodiments.

[0043] Figure 11 illustrates an example of a method performed by a wireless device in accordance with some embodiments.

[0044] Figure 12 illustrates an example of a method performed by a network node in accordance with some embodiments.

[0045] Figure 13 illustrates an example of a method performed by a wireless device in accordance with some embodiments.

[0046] Figure 14 illustrates an example of a method performed by a network node in accordance with some embodiments.

[0047] Figure 15 illustrates an example of a method performed by a core network node in accordance with some embodiments.DETAILED DESCRIPTION

[0048] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.Overview

[0049] Certain embodiments are described in the context of NR with two or more SL UEs deployed in a same or different NR cell. However, the same principles may be applied to LTE or any other technology that enables the direct connection of two (or more) nearby devices. The embodiments are also applicable to relay scenarios including UE-to-network relaying and / or UE-to-UE relaying where the remote UE and the relay UE may be based on LTE sidelink or NR sidelink. The Uu connection between the relay UE and the base station may be LTE Uu or NR Uu. Certain embodiments are applicable to L2 based U2N relaying scenarios.

[0050] Certain embodiments are described in the context of a multipath relay using an ideal link between a first UE and a second UE. However, the same principles may be applied to a multipath relay using another type of link between the first UE and the second UE, such as a multipath relay using a PC5-link or other sidelink technology.

[0051] The terms multipath operation / connection with relays and multipath operation / connection are often used inter-changeably. Certain embodiments are described from the perspective of a multipath UE / remote UE. Certain embodiments are described from the perspective of a relay UE. Certain embodiments are described from the perspective of a gNB.

[0052] The embodiments below are not restricted by any term defined in the above texts. Any other similar term is inter-changeable where applicable without any loss of the meaning.Cell-level control:

[0053] In a first embodiment, a UE capable of performing a multipath operation using an ideal link receives an indication from the network. The indication indicates whether the network supports multipath relays using an ideal link. The UE that receives the indication may be a remote UE or a relay UE. The indication may be received from a base station (e.g., gNB) in the network. The indication may be received in the downlink (DL) in a broadcast message or in a dedicated message. As an example, the network may broadcast the indication to the UE in a system information block (SIB), such as SIB 12. As another example, the network may provide the indication to the UE in a dedicated message via DL radio resource control (RRC). Based on the indication, the UE can initiate a request for a multipath operation.

[0054] The following is an example of the SIB 12 with the indication of the multipath relays using an ideal link.

[0055] In a second embodiment, the UE (remote UE or relay UE) in RRC IDLE / INACTIVE mode and capable of performing a multipath operation using an ideal link based on the indication from the network / gNB can prioritize cells supporting the multipath operation using an ideal link during the cell selection / reselection procedures.

[0056] In a third embodiment, the UE (remote UE or relay UE) in RRC CONNECTED mode and capable of performing a multipath operation using an ideal link based on the indication from the network / gNB can prioritize cells supporting the multipath operation using an ideal link in the measurement report to the gNB.

[0057] In a fourth embodiment, a UE (remote UE or relay UE) can indicate to the network that the UE can perform a multipath operation using an ideal link. For example, the UE may indicate its capabilities to the network, and the capabilities may include an indication that the UE can perform a multipath operation using an ideal link. In certain embodiments, the UE indicates its capabilities to the network as part of a capability enquiry procedure. The capability enquiry procedure takes place after establishing access stratum (AS) security, i.e., after the UE has been authorized to access the network using the Uu interface. In certain embodiments, the UE communicates the indication / capabilities to the network using an uplink (UL) RRC message.

[0058] In another aspect, the UE (remote UE or relay UE) can send the network a request indicating the UE’s need to setup a multipath operation using an ideal link. In certain embodiments, the UE may send the request to the network using an UL RRC message. As an example, the request may be included as a part of UEAssistancelnformation.

[0059] In a fifth embodiment, a network node (e.g., gNB) receives an indication from a UE (remote UE or relay UE). The indication indicates a multipath operation using an ideal link. As an example, the network node (e.g., gNB) may receive capabilities indicating that the UE can perform a multipath operation using an ideal link. As another example, the network node (e.g., gNB) may receive a request indicating to setup a multipath operation using an ideal link. In response to receiving the indication indicating a multipath operation using an ideal link fromthe UE, the network node (e.g., gNB) can pass this information on to the core network (CN). The CN can either allow or deny the UE (remote UE or relay UE) from setting up the multipath connection using an ideal link. For example, the AMF of the CN can then check the subscription information from the UDM and can either allow or deny the UE (remote UE or relay UE) from setting up the multipath connection using an ideal link. Figure 5 illustrates an example of UE-level control based on subscription information checked by the AMF.

[0060] In a sixth embodiment, during registration of the UE, the CN (e.g., AMF) provides information to the network (e.g., gNB) indicating whether UE aggregation with non-3GPP is authorized. The network / gNB may later receive an indication from the UE indicating to set up multipath operation using an ideal link to aggregate the data. In response, the network / gNB checks the authorized information received from the CN, and the network / gNB determines whether to allow or deny setting up the multipath connection using an ideal link based on the authorized information. The network may allow setting up the multipath connection using an ideal link if the authorized information indicates that the UE is authorized. The network may deny setting up the multipath connection using an ideal link if the authorized information indicates that the UE is not authorized. Figure 6 illustrates an example of UE-level control based on subscription information checked by the gNB (the gNB checks whether UE Aggregation with non-3GPP is authorized based on information previously received from the CN / AMF).

[0061] In a seventh embodiment, new subscription information is introduced for UE aggregation using 3GPP and non-3GPP access. For example, new subscription information (such as a new field, parameter, information element, or other information not already specified by 3GPP) may be used to indicate whether / when the UE is authorized to communicate via a multipath relay using an ideal link. The corresponding authorization information can be sent to the gNB / AMF as explained in the fifth and sixth embodiments.

[0062] In another aspect, the existing ProSe subscription information can be expanded to include the authorization for non-3GPP based UE-to-Network relaying (i.e., only one path via the relay UE to the gNB). For example, the first link between the remote UE and relay UE can be a Wireless Local Area Network (WLAN) link, in which case the subscription information can include “WLAN based UE-to-Network relays.” For other technologies, the subscription information can include “non-3GPP based UE-to-Network relays.” A combination of the subscription information of the direct path, i.e., over Uu and the subscription information over the indirect path, i.e., non-3GPP access can also be used by the network to authorize the UE (remote UE or relay UE) to setup a multipath using an ideal link.

[0063] Note that a “UE aggregation with non-3GPP authorized” indication may also be provided to the network / gNB in other procedures, such as handover procedures or service request procedures. Examples of procedures that may be used to provide the indication include N2-based handover (from AMF to Next Generation-Radio Access Network (NG-RAN)), Xn- based handover (from source RAN to target RAN), and / or Service Request (from AMF to NG- RAN).

[0064] Figure 7 shows an example of a communication system 100 in accordance with some embodiments.

[0065] In the example, the communication system 100 includes a telecommunication network 102 that includes an access network 104, such as a radio access network (RAN), and a core network 106, which includes one or more core network nodes 108. The access network 104 includes one or more access network nodes, such as network nodes 110a and 110b (one or more of which may be generally referred to as network nodes 110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network 102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network 102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network 102, including one or more network nodes 110 and / or core network nodes 108.

[0066] Examples of an ORAN network node include an open radio unit (O-RU), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O- CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an Al, Fl, Wl, El, E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may beimplemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the 0-RAN Alliance or comparable technologies. The network nodes 110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 112a, 112b, 112c, and 112d (one or more of which may be generally referred to as UEs 112) to the core network 106 over one or more wireless connections. As depicted, UEs 112A and 112B may communicate over a SL connection to provide for multipath connectivity as described herein.

[0067] Example wireless communications over a wireless connection include transmitting and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for conveying information without the use of wires, cables, or other material conductors. Moreover, in different embodiments, the communication system 100 may include any number of wired or wireless networks, network nodes, UEs, and / or any other components or systems that may facilitate or participate in the communication of data and / or signals whether via wired or wireless connections. The communication system 100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0068] The UEs 112 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and / or operable to communicate wirelessly with the network nodes 110 and other communication devices. Similarly, the network nodes 110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs 112 and / or with other network nodes or equipment in the telecommunication network 102 to enable and / or provide network access, such as wireless network access, and / or to perform other functions, such as administration in the telecommunication network 102.

[0069] In the depicted example, the core network 106 connects the network nodes 110 to one or more hosts, such as host 116. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 106 includes one more core network nodes (e.g., core network node 108) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and / or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 108. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity(MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and / or a User Plane Function (UPF).

[0070] The host 116 may be under the ownership or control of a service provider other than an operator or provider of the access network 104 and / or the telecommunication network 102, and it may be operated by the service provider or on behalf of the service provider. The host 116 may host a variety of applications to provide one or more service. Examples of such applications include live and pre-recorded audio / video content, data collection services such as retrieving and compiling data on various ambient conditions detected by a plurality of UEs, analytics functionality, social media, functions for controlling or otherwise interacting with remote devices, functions for an alarm and surveillance center, or any other such function performed by a server.

[0071] As a whole, the communication system 100 of Figure 7 enables connectivity between the UEs, network nodes, and hosts. In that sense, the communication system may be configured to operate according to predefined rules or procedures, such as specific standards that include, but are not limited to: Global System for Mobile Communications (GSM); Universal Mobile Telecommunications System (UMTS); Long Term Evolution (LTE), and / or other suitable 2G, 3G, 4G, 5G standards, or any applicable future generation standard (e.g., 6G); wireless local area network (WLAN) standards, such as the Institute of Electrical and Electronics Engineers (IEEE) 802.11 standards (Wi-Fi); and / or any other appropriate wireless communication standard, such as the Worldwide Interoperability for Microwave Access (WiMax), Bluetooth, Z-Wave, Near Field Communication (NFC) ZigBee, LiFi, and / or any low-power wide-area network (LPWAN) standards such as LoRa and Sigfox.

[0072] In some examples, the telecommunication network 102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 102. For example, the telecommunications network 102 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and / or Massive Machine Type Communication (mMTC)ZMassive loT services to yet further UEs.

[0073] In some examples, the UEs 112 are configured to transmit and / or receive information without direct human interaction. For instance, a UE may be designed to transmitinformation to the access network 104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 104. Additionally, a UE may be configured for operating in single- or multi -RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e., being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved-UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN- DC).

[0074] In the example, the hub 114 communicates with the access network 104 to facilitate indirect communication between one or more UEs (e.g., UE 112c and / or 112d) and network nodes (e.g., network node 110b). In some examples, the hub 114 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 114 may be a broadband router enabling access to the core network 106 for the UEs. As another example, the hub 114 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 110, or by executable code, script, process, or other instructions in the hub 114. As another example, the hub 114 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub 114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0075] The hub 114 may have a constant / persistent or intermittent connection to the network node 110b. The hub 114 may also allow for a different communication scheme and / or schedule between the hub 114 and UEs (e.g., UE 112c and / or 112d), and between the hub 114 and the core network 106. In other examples, the hub 114 is connected to the core network 106 and / or one or more UEs via a wired connection. Moreover, the hub 114 may be configured to connect to an M2M service provider over the access network 104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 110 while still connected via the hub 114 via a wired or wireless connection. In some embodiments, the hub 114 may be a dedicated hub - that is, a hub whose primary function is to route communications to / from the UEs from / to the network node 110b. In otherembodiments, the hub 114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0076] Figure 8 shows a UE 200 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and / or operable to communicate wirelessly with network nodes and / or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle, vehicle-mounted or vehicle embedded / integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0077] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), orvehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and / or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0078] The UE 200 includes processing circuitry 202 that is operatively coupled via a bus 204 to an input / output interface 206, a power source 208, a memory 210, a communication interface 212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 8. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0079] The processing circuitry 202 is configured to process instructions and data and may be configured to implement any sequential state machine operative to execute instructions stored as machine-readable computer programs in the memory 210. The processing circuitry 202 may be implemented as one or more hardware-implemented state machines (e.g., in discrete logic, field-programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), etc.); programmable logic together with appropriate firmware; one or more stored computer programs, general-purpose processors, such as a microprocessor or digital signal processor (DSP), together with appropriate software; or any combination of the above. For example, the processing circuitry 202 may include multiple central processing units (CPUs).

[0080] In the example, the input / output interface 206 may be configured to provide an interface or interfaces to an input device, output device, or one or more input and / or output devices. Examples of an output device include a speaker, a sound card, a video card, a display, a monitor, a printer, an actuator, an emitter, a smartcard, another output device, or any combination thereof. An input device may allow a user to capture information into the UE 200. Examples of an input device include a touch-sensitive or presence-sensitive display, a camera (e.g., a digital camera, a digital video camera, a web camera, etc.), a microphone, a sensor, a mouse, a trackball, a directional pad, a trackpad, a scroll wheel, a smartcard, and the like. The presence-sensitive display may include a capacitive or resistive touch sensor to sense input from a user. A sensor may be, for instance, an accelerometer, a gyroscope, a tilt sensor, a force sensor, a magnetometer, an optical sensor, a proximity sensor, a biometric sensor, etc., or any combination thereof. An output device may use the same type of interface port as an input device. For example, a Universal Serial Bus (USB) port may be used to provide an input device and an output device.

[0081] In some embodiments, the power source 208 is structured as a battery or battery pack. Other types of power sources, such as an external power source (e.g., an electricity outlet), photovoltaic device, or power cell, may be used. The power source 208 may further include power circuitry for delivering power from the power source 208 itself, and / or an external power source, to the various parts of the UE 200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 208 to make the power suitable for the respective components of the UE 200 to which power is supplied.

[0082] The memory 210 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory(PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 210 includes one or more application programs 214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 216. The memory 210 may store, for use by the UE 200, any of a variety of various operating systems or combinations of operating systems.

[0083] The memory 210 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD- DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and / or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory 210 may allow the UE 200 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 210, which may be or comprise a device-readable storage medium.

[0084] The processing circuitry 202 may be configured to communicate with an access network or other network using the communication interface 212. The communication interface 212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 222. The communication interface 212 may include one or more transceivers used to communicate, such as by communicating with one or more remote transceivers of another device capable of wireless communication (e.g., another UE or a network node in an access network). Each transceiver may include a transmitter 218 and / or a receiver 220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 218 and receiver 220 may be coupled to one or more antennas (e.g., antenna 222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0085] In the illustrated embodiment, communication functions of the communication interface 212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol / intemet protocol (TCP / IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth.

[0086] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 212, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

[0087] As another example, a UE comprises an actuator, a motor, or a switch, related to a communication interface configured to receive wireless input from a network node via a wireless connection. In response to the received wireless input the states of the actuator, the motor, or the switch may change. For example, the UE may comprise a motor that adjusts the control surfaces or rotors of a drone in flight according to the received input or to a robotic arm performing a medical procedure according to the received input.

[0088] A UE, when in the form of an Internet of Things (loT) device, may be a device for use in one or more application domains, these domains comprising, but not limited to, city wearable technology, extended industrial application and healthcare. Non-limiting examples of such an loT device are a device which is or which is embedded in: a connected refrigerator or freezer, a TV, a connected lighting device, an electricity meter, a robot vacuum cleaner, a voice controlled smart speaker, a home security camera, a motion detector, a thermostat, a smoke detector, a door / window sensor, a flood / moisture sensor, an electrical door lock, a connected doorbell, an air conditioning system like a heat pump, an autonomous vehicle, asurveillance system, a weather monitoring device, a vehicle parking monitoring device, an electric vehicle charging station, a smart watch, a fitness tracker, a head-mounted display for Augmented Reality (AR) or Virtual Reality (VR), a wearable for tactile augmentation or sensory enhancement, a water sprinkler, an animal- or item-tracking device, a sensor for monitoring a plant or animal, an industrial robot, an Unmanned Aerial Vehicle (UAV), and any kind of medical device, like a heart rate monitor or a remote controlled surgical robot. A UE in the form of an loT device comprises circuitry and / or software in dependence of the intended application of the loT device in addition to other components as described in relation to the UE 200 shown in Figure 8.

[0089] As yet another specific example, in an loT scenario, a UE may represent a machine or other device that performs monitoring and / or measurements, and transmits the results of such monitoring and / or measurements to another UE and / or a network node. The UE may in this case be an M2M device, which may in a 3GPP context be referred to as an MTC device. As one particular example, the UE may implement the 3 GPP NB-IoT standard. In other scenarios, a UE may represent a vehicle, such as a car, a bus, a truck, a ship and an airplane, or other equipment that is capable of monitoring and / or reporting on its operational status or other functions associated with its operation.

[0090] In practice, any number of UEs may be used together with respect to a single use case. For example, a first UE might be or be integrated in a drone and provide the drone’s speed information (obtained through a speed sensor) to a second UE that is a remote controller operating the drone. When the user makes changes from the remote controller, the first UE may adjust the throttle on the drone (e.g., by controlling an actuator) to increase or decrease the drone’s speed. The first and / or the second UE can also include more than one of the functionalities described above. For example, a UE might comprise the sensor and the actuator, and handle communication of data for both the speed sensor and the actuators.

[0091] Figure 9 shows a network node 300 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and / or operable to communicate directly or indirectly with a UE and / or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)), 0-RAN nodes or components of an 0-RAN node (e.g., O-RU, O-DU, O-CU).

[0092] Base stations may be categorized based on the amount of coverage they provide (or, stated differently, their transmit power level) and so, depending on the provided amount ofcoverage, may be referred to as femto base stations, pico base stations, micro base stations, or macro base stations. A base station may be a relay node or a relay donor node controlling a relay. A network node may also include one or more (or all) parts of a distributed radio base station such as centralized digital units, distributed units (e.g., in an O-RAN access node) and / or remote radio units (RRUs), sometimes referred to as Remote Radio Heads (RRHs). Such remote radio units may or may not be integrated with an antenna as an antenna integrated radio. Parts of a distributed radio base station may also be referred to as nodes in a distributed antenna system (DAS).

[0093] Other examples of network nodes include multiple transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment such as MSR BSs, network controllers such as radio network controllers (RNCs) or base station controllers (BSCs), base transceiver stations (BTSs), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCEs), Operation and Maintenance (O&M) nodes, Operations Support System (OSS) nodes, Self-Organizing Network (SON) nodes, positioning nodes (e.g., Evolved Serving Mobile Location Centers (E-SMLCs)), and / or Minimization of Drive Tests (MDTs).

[0094] The network node 300 includes a processing circuitry 302, a memory 304, a communication interface 306, and a power source 308. The network node 300 may be composed of multiple physically separate components (e.g., a NodeB component and a RNC component, or a BTS component and a BSC component, etc.), which may each have their own respective components. In certain scenarios in which the network node 300 comprises multiple separate components (e.g., BTS and BSC components), one or more of the separate components may be shared among several network nodes. For example, a single RNC may control multiple NodeBs. In such a scenario, each unique NodeB and RNC pair, may in some instances be considered a single separate network node. In some embodiments, the network node 300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 304 for different RATs) and some components may be reused (e.g., a same antenna 310 may be shared by different RATs). The network node 300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 300, for example GSM, WCDMA, LTE, NR, WiFi, Zigbee, Z-wave, LoRaWAN, Radio Frequency Identification (RFID) or Bluetooth wireless technologies. These wireless technologies may be integrated into the same or different chip or set of chips and other components within network node 300.

[0095] The processing circuitry 302 may comprise a combination of one or more of a microprocessor, controller, microcontroller, central processing unit, digital signal processor, application-specific integrated circuit, field programmable gate array, or any other suitable computing device, resource, or combination of hardware, software and / or encoded logic operable to provide, either alone or in conjunction with other network node 300 components, such as the memory 304, to provide network node 300 functionality.

[0096] In some embodiments, the processing circuitry 302 includes a system on a chip (SOC). In some embodiments, the processing circuitry 302 includes one or more of radio frequency (RF) transceiver circuitry 312 and baseband processing circuitry 314. In some embodiments, the radio frequency (RF) transceiver circuitry 312 and the baseband processing circuitry 314 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 312 and baseband processing circuitry 314 may be on the same chip or set of chips, boards, or units.

[0097] The memory 304 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and / or any other volatile or non-volatile, non-transitory device-readable and / or computerexecutable memory devices that store information, data, and / or instructions that may be used by the processing circuitry 302. The memory 304 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and / or other instructions capable of being executed by the processing circuitry 302 and utilized by the network node 300. The memory 304 may be used to store any calculations made by the processing circuitry 302 and / or any data received via the communication interface 306. In some embodiments, the processing circuitry 302 and memory 304 is integrated.

[0098] The communication interface 306 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE. As illustrated, the communication interface 306 comprises port(s) / terminal(s) 316 to send and receive data, for example to and from a network over a wired connection. The communication interface 306 also includes radio front-end circuitry 318 that may be coupled to, or in certain embodiments a part of, the antenna 310. Radio front-end circuitry 318 comprises filters 320 and amplifiers 322. The radio front-end circuitry 318 may be connected to an antenna 310 and processingcircuitry 302. The radio front-end circuitry may be configured to condition signals communicated between antenna 310 and processing circuitry 302. The radio front-end circuitry 318 may receive digital data that is to be sent out to other network nodes or UEs via a wireless connection. The radio front-end circuitry 318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 320 and / or amplifiers 322. The radio signal may then be transmitted via the antenna 310. Similarly, when receiving data, the antenna 310 may collect radio signals which are then converted into digital data by the radio front-end circuitry 318. The digital data may be passed to the processing circuitry 302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0099] In certain alternative embodiments, the network node 300 does not include separate radio front-end circuitry 318, instead, the processing circuitry 302 includes radio front-end circuitry and is connected to the antenna 310. Similarly, in some embodiments, all or some of the RF transceiver circuitry 312 is part of the communication interface 306. In still other embodiments, the communication interface 306 includes one or more ports or terminals 316, the radio front-end circuitry 318, and the RF transceiver circuitry 312, as part of a radio unit (not shown), and the communication interface 306 communicates with the baseband processing circuitry 314, which is part of a digital unit (not shown).

[0100] The antenna 310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna 310 may be coupled to the radio front-end circuitry 318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna 310 is separate from the network node 300 and connectable to the network node 300 through an interface or port.

[0101] The antenna 310, communication interface 306, and / or the processing circuitry 302 may be configured to perform any receiving operations and / or certain obtaining operations described herein as being performed by the network node. Any information, data and / or signals may be received from a UE, another network node and / or any other network equipment. Similarly, the antenna 310, the communication interface 306, and / or the processing circuitry 302 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and / or signals may be transmitted to a UE, another network node and / or any other network equipment.

[0102] The power source 308 provides power to the various components of network node 300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 308 may further comprise, or be coupledto, power management circuitry to supply the components of the network node 300 with power for performing the functionality described herein. For example, the network node 300 may be connectable to an external power source (e.g., the power grid, an electricity outlet) via an input circuitry or interface such as an electrical cable, whereby the external power source supplies power to power circuitry of the power source 308. As a further example, the power source 308 may comprise a source of power in the form of a battery or battery pack which is connected to, or integrated in, power circuitry. The battery may provide backup power should the external power source fail.

[0103] Embodiments of the network node 300 may include additional components beyond those shown in Figure 9 for providing certain aspects of the network node’s functionality, including any of the functionality described herein and / or any functionality necessary to support the subject matter described herein. For example, the network node 300 may include user interface equipment to allow input of information into the network node 300 and to allow output of information from the network node 300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 300.

[0104] Figure 10 is a block diagram illustrating a virtualization environment 400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized. In some embodiments, the virtualization environment 400 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an O-2 interface.

[0105] Applications 402 (which may alternatively be called software instances, virtual appliances, network functions, virtual nodes, virtual network functions, etc.) are run in the virtualization environment Q400 to implement some of the features, functions, and / or benefits of some of the embodiments disclosed herein.

[0106] Hardware 404 includes processing circuitry, memory that stores software and / or instructions executable by hardware processing circuitry, and / or other hardware devices as described herein, such as a network interface, input / output interface, and so forth. Software may be executed by the processing circuitry to instantiate one or more virtualization layers 406 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 408a and 408b (one or more of which may be generally referred to as VMs 408), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer 406 may present a virtual operating platform that appears like networking hardware to the VMs 408.

[0107] The VMs 408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 406. Different embodiments of the instance of a virtual appliance 402 may be implemented on one or more of VMs 408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment.

[0108] In the context of NFV, a VM 408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non- virtualized machine. Each of the VMs 408, and that part of hardware 404 that executes that VM, be it hardware dedicated to that VM and / or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 408 on top of the hardware 404 and corresponds to the application 402.

[0109] Hardware 404 may be implemented in a standalone network node with generic or specific components. Hardware 404 may implement some functions via virtualization. Alternatively, hardware 404 may be part of a larger cluster of hardware (e.g., such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 410, which, among others, oversees lifecycle management of applications 402. In some embodiments, hardware 404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. Insome embodiments, some signaling can be provided with the use of a control system 412 which may alternatively be used for communication between hardware nodes and radio units.

[0110] Figure 11 illustrates an example of a method 1100 that may be performed by a wireless device, such as a UE described with respect to any of Figures 1A-6 (e.g., remote UE or relay UE), UE 112 of Figure 7, or UE 200 of Figure 8. As an example, in certain embodiments, the wireless device comprises at least one processor (such as processing circuitry 202) configured to perform one or more operations of the method 1100. In certain embodiments, the wireless device comprises a computer-readable medium (such as memory 210) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the operations of the method 1100.[oni] Method 1100 begins at operation 1102 with a UE (e.g., a first UE) receiving an indication from a network. The indication indicates whether the network supports multipath relays. In certain embodiments, a multipath relay includes at least one path that uses a sidelink between the first UE and a second UE for relaying communication to the network. The first UE may be capable of acting as a relay UE (e.g., to relay communication between the network and the second UE) and / or as a remote UE (e.g., to communicate with the network via the second UE, the second UE acting as a relay UE).

[0112] The indication from the network in operation 1102 may be received via any suitable network node, such as a gNB. The indication may indicate support at any suitable level of granularity, such as per network node, per cell, or other suitable granularity. Certain embodiments receive the indication in a broadcast message, such as a SIB. Certain embodiments receive the indication in a dedicated message, such as a DL RRC message.

[0113] The method proceeds to operation 1104 with determining whether to initiate communication with the network via a multipath relay. The multipath relay may use a sidelink to a second UE. The sidelink may be an ideal link, a PC5-link, or other sidelink. The determining is based at least in part on the indication from the network received in operation 1102. For example, if the indication indicates that the network supports multipath relays, method 1100 may determine at operation 1104 to send the network a request to communicate via the multipath relay.

[0114] In certain embodiments, the method proceeds to operation 1106 with communicating with the network via the multipath relay. In certain embodiments, the UE performing method 1100 is configured as / communicates as a remote UE with the second UE communicating as a relay UE. In other embodiments, the UE performing method 1100 isconfigured as / communicates as a relay UE with the second UE communicating as a remote UE.

[0115] In certain embodiments, method 1100 further comprises performing a cell selection / reselection procedure using the indication from the network to select a cell that supports the multipath relays. For example, the UE may give higher priority to a cell that supports the multipath relays and lower priority to a cell that does not support the multipath relays. Cell selection / reselection may be performed when the UE is in an idle or inactive RRC state.

[0116] In certain embodiments, method 1100 further comprises preparing a measurement report using the indication from the network to prioritize a measurement associated with a cell that supports the multipath relays. For example, the UE may give higher priority to a measurement associated with a cell that supports the multipath relays and lower priority to a measurement associated with a cell that does not support the multipath relays. Measurement reporting may be performed when the UE is in a connected RRC state.

[0117] Optionally, method 1100 may include any other suitable operations or details, such as those described above with respect to the heading “Cell-level control” (see, e.g., the first, second, and / or third embodiments).

[0118] The multipath relay of method 1100 may use any suitable type of sidelink, such as a PC5-link, an ideal link, or other type of sidelink. As described above, a PC5-link refers to a link specified by 3GPP. In general, the PC5-link facilitates communication between UEs in a manner specified by 3GPP. Further details of the PC5-link may depend on the 3GPP standard or release number being implemented. An ideal link refers to a link that facilitates communication between UEs and is outside the scope of 3GPP (such as an alternative to 3GPP’s PC5-link). The ideal link can use any proprietary or other non-3GPP based access to form a link between UEs. An example of an “other” type of sidelink may include a sidelink that may be specified by 3GPP in the future, such as a non-PC5 sidelink that may be within the scope of 3 GPP.

[0119] As an example of an embodiment of method 1100 that uses an ideal link, method 1100 comprises receiving an indication from a network, the indication indicating whether the network supports multipath relays using an ideal link (operation 1102); and determining whether to initiate communication with the network via a multipath relay using an ideal link to a second UE, the determining based at least in part on the indication from the network (operation 1104). In certain embodiments, in response to determining to initiate communication with the network via the multipath relay using the ideal link to the second UE,method 1100 may further comprise initiating the communication and / or communicating via the multipath relay using the ideal link to the second UE (operation 1106).

[0120] Certain embodiments may apply to multipath relays in general (without distinguishing among different types of sidelinks). Other embodiments may distinguish among different types of sidelinks. As an example, the indication in operation 1102 may simply indicate whether the network supports multipath relays (in general, e.g., regardless of type), or the indication in operation 1102 may more specifically indicate (implicitly or explicitly) whether the network supports multipath relays using one or more types of sidelinks, such as an ideal link, a PC5-link, and / or another type of sidelink. An indication may implicitly indicate that it is for multipath relays using a particular type of sidelink (such as the ideal link or PC5- link), for example, if a specification defines the indication only for that type of sidelink. An indication may explicitly indicate that it is for multipath relays using a particular type of sidelink, for example, if the indication includes a field, parameter, information element, or other information indicating the sidelink type(s) to which it does (or does not) apply. Optionally, other features, such as cell selection / reselection to a cell that supports multipath relays, measurement reporting that prioritizes cells that support multipath relays, etc., may be performed for the case of multipath relays (in general) or for the case of multipath relays using a particular type of sidelink (such as the ideal link or PC5-link).

[0121] Figure 12 illustrates an example of a method 1200 that may be performed by a network node, such as network node 2 of Figure 1A or IB, network node 110 of Figure 7, or network node 300 of Figure 9. As an example, in certain embodiments, the network node comprises at least one processor (such as processing circuitry 302) configured to perform one or more operations of the method 1200. In certain embodiments, the network node comprises a computer-readable medium (such as memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the operations of the method 1200.

[0122] In certain embodiments, method 1200 begins at operation 1202 with obtaining information indicating whether the network node supports multipath relays. The information may be obtained in any suitable manner. As an example, a network node may obtain the information by checking its configuration, provisioning, status, and / or other attributes to determine whether it supports the multipath relays. As another example, the network node may obtain the information from memory. As another example, the network node may obtain the information from another node, such as a core network node, or from operator-controlled Operations, Administration and Maintenance (0AM). Based on the information obtained inoperation 1202, certain embodiments prepare an indication to communicate to one or more UEs. The indication indicates whether the network node supports multipath relays. In certain embodiments, the information obtained in operation 1202 may comprise the indication itself. As an example, certain embodiments may obtain the indication itself from memory. In other embodiments, the information obtained in operation 1202 may be used as an input to generate the indication. The method proceeds to operation 1204 with communicating the indication to one or more UEs. The indication may be communicated in a broadcast message capable of being read by multiple UEs (such as a SIB broadcast) and / or the indication may be communicated to a particular UE via a dedicated message (such as via a DL RRC message). The indication may be communicated at any suitable time or at multiple times (such as for a recurring broadcast).

[0123] In certain embodiments, method 1200 may further comprise receiving, from a first UE of the one or more UEs, a request to communicate with the network via a multipath relay. The method may then determine whether to grant the request. The determination may be based at least in part on whether the network node supports the multipath relays. For example, the method may deny the request if the network node does not support the multipath relays. In certain embodiments, the determination may also be based on one or more other factors, such as whether the first UE is authorized to communicate with the network via the multipath relay (e.g., based on subscription information associated with the first UE).

[0124] In certain embodiments, method 1200 further comprises communicating with a first of the one or more UEs via the multipath relay using a sidelink to the second UE. The first UE may communicate as either a relay UE (e.g., to relay communication between the network and the second UE) or as a remote UE (e.g., to communicate with the network via the second UE, the second UE communicating as a relay UE).

[0125] Optionally, method 1200 may include any other suitable operations or details, such as those described above with respect to the heading “Cell-level control” (see, e.g., the first, second, and / or third embodiments).

[0126] The multipath relay of method 1200 may use any suitable type of sidelink, such as a PC5-link, an ideal link, or other type of sidelink. As an example of an embodiment where the multipath relay uses an ideal link, method 1200 comprises obtaining information indicating whether the network node supports multipath relays using an ideal link (operation 1202); and communicating an indication to one or more UEs (operation 1204). The indication indicates, based on the information obtained in operation 1202, whether the network node supports multipath relays using an ideal link. In some embodiments, method 1200 further comprisescommunicating with a first of the one or more UEs via the multipath relay using the ideal link to a second UE.

[0127] Optionally, certain embodiments may distinguish among different types of sidelinks. As an example, in certain embodiments, the indication in operation 1202 may indicate (implicitly or explicitly) whether the network supports multipath relays using an ideal link, a PC5-link, and / or one or more other types of sidelinks. In other embodiments, the indication in operation 1202 may simply indicate whether the network supports multipath relays in general (without distinguishing among different types of sidelinks).

[0128] Figure 13 illustrates an example of a method 1300 that may be performed by a wireless device, such as a UE described with respect to any of Figures 1A-6 (e.g., remote UE or relay UE), UE 112 of Figure 7, or UE 200 of Figure 8. As an example, in certain embodiments, the wireless device comprises at least one processor (such as processing circuitry 202) configured to perform one or more operations of the method 1300. In certain embodiments, the wireless device comprises a computer-readable medium (such as memory 210) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the operations of the method 1300.

[0129] In certain embodiments, method 1300 begins at operation 1302 with communicating an indication to a network. The indication indicates that the UE supports a multipath relay. As an example, communicating the indication to the network in operation 1302 may comprise sending, to the network, a request to setup the multipath operation. As another example, communicating the indication to the network in operation 1302 may comprise sending, to the network, information indicating capabilities of the UE. The information indicating capabilities of the UE comprises the indication that the UE supports the multipath relay. Certain embodiments send the information indicating capabilities of the UE to the network during a capability enquiry procedure that occurs after the network has authorized the UE to access the network.

[0130] In certain embodiments, method 1300 may proceed to operation 1304 with receiving information from the network. The information indicates whether the network authorizes the UE to communicate via the multipath relay. As an example, the network may accept the UE’s request to support or setup the multipath operation if the UE is authorized. The network may deny the UE’s request to support or setup the multipath operation if the UE is not authorized.

[0131] Optionally, method 1300 may include any other suitable operations or details, such as those described above with respect to the heading “Cell-level control” (see, e.g., the fourth, fifth, sixth, and / or seventh embodiments).

[0132] Depending on the embodiment, the multipath relay of method 1300 may use an ideal link, a PC5-link, or other suitable sidelink technology. As an example of an embodiment where the multipath relay uses an ideal link, method 1300 comprises communicating, to a network, an indication that the UE supports a multipath relay using an ideal link (operation 1302); and receiving, from the network, information indicating whether the network authorizes the UE to communicate via the multipath relay using the ideal link (operation 1304). Optionally, certain embodiments may (implicitly or explicitly) distinguish among different types of sidelinks. Other embodiments may simply be described in the context of multipath relays in general (without distinguishing among different types of sidelinks).

[0133] Figure 14 illustrates an example of a method 1400 that may be performed by a network node, such as network node 2 of Figure 1A or IB, network node 110 of Figure 7, or network node 300 of Figure 9. As an example, in certain embodiments, the network node comprises at least one processor (such as processing circuitry 302) configured to perform one or more operations of the method 1400. In certain embodiments, the network node comprises a computer-readable medium (such as memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the operations of the method 1400.

[0134] In certain embodiments, method 1400 may be performed by a radio access network node, such as a gNB. Method 1400 begins at operation 1402 with receiving an indication from a UE. The indication indicates that the UE supports a multipath relay. As an example, the indication that the UE supports the multipath relay may be received as a request to setup the multipath relay. As another example, the indication that the UE supports the multipath relay may be received / included in information indicating capabilities of the UE. In certain embodiments, the information indicating capabilities of the UE is received from the UE during a capability enquiry procedure. The capability enquiry procedure occurs after the network has authorized the UE to access the network.

[0135] Method 1400 proceeds to operation 1404 with communicating information to the UE indicating whether the network authorizes the UE to communicate via the multipath relay. For example, certain embodiments may indicate whether the UE is authorized by either allowing or denying setup of the multipath relay. In method 1400, the network node (e.g., gNB) may receive an indication whether the UE is authorized to use the multipath relay from the corenetwork. The indication whether the UE is authorized to use the multipath relay may be based on subscription information associated with the UE. Subscription information is further described below with respect to Figure 15. The indication whether the UE is authorized to use the multipath relay may be received from the core network at any suitable time, such as during registration of the UE or in response to the network node indicating to the core network that the UE has requested to setup the multipath relay.

[0136] Optionally, method 1400 may include any other suitable operations or details, such as those described above with respect to the heading “Cell-level control” (see, e.g., the fourth, fifth, sixth, and / or seventh embodiments).

[0137] Depending on the embodiment, the multipath relay of method 1400 may use an ideal link, a PC5-link, or other suitable sidelink technology. As an example of an embodiment where the multipath relay uses an ideal link, method 1400 comprises receiving, from a UE, an indication that the UE supports a multipath relay using an ideal link (operation 1402); and communicating, to the UE, information indicating whether the network authorizes the UE to communicate via the multipath relay using the ideal link (operation 1404). Optionally, certain embodiments may (implicitly or explicitly) distinguish among different types of sidelinks. Other embodiments may simply be described in the context of multipath relays in general (without distinguishing among different types of sidelinks).

[0138] Figure 15 illustrates an example of a method 1500 that may be performed by a core network node, such as an AMF (see, e.g., Figure 5 or Figure 6) or core network node 108 of Figure 7. As an example, in certain embodiments, the core network node comprises at least one processor (generally analogous to processing circuitry 302) configured to perform one or more operations of the method 1500. In certain embodiments, the core network node comprises a computer-readable medium (generally analogous to memory 304) comprising instructions that, when executed by the at least one processor, cause the at least one processor to perform any of the operations of the method 1500.

[0139] Figure 15 begins at operation 1502 with determining whether a UE is authorized to use a multipath relay. The determining may be based on subscription information associated with the UE. For example, prior to operation 1502, method 1500 may comprise setting up the subscription information associated with the UE. A network operator may opt to add, modify, or remove subscription information at any suitable time, such as when the owner of the UE subscribes to a subscription plan or when a subscription option becomes available / unavailable in the network. As an example, the subscription information may be set up as part of a provisioning procedure when the UE is new. The subscription information may be stored at thecore network node or at a location in the network accessible to the core network node (e.g., such that the core network node may obtain the subscription information by communicating with another network node).

[0140] As described above with respect to the seventh embodiment, the subscription information described in this disclosure is new in that it has not been previously conceived of or specified by 3GPP. The present disclosure recommends introducing / specifying the subscription information by 3GPP. For example, a new field, parameter, information element, or other information not already specified by 3GPP may be introduced to indicate whether / when the UE is authorized to communicate via a multipath relay. The present disclosure describes certain subscription information by the working name “UE aggregation with non-3GPP authorized” (e.g., for an embodiment where the multipath relay uses an ideal / non-3GPP link), however, another name could be used.

[0141] Method 1500 continues to operation 1504 with communicating, to a radio access network node, an indication whether the UE is authorized to use the multipath relay. Certain embodiments communicate the indication during registration of the UE (Figure 6 illustrates an example). Certain embodiments communicate the indication in response to the radio access network node indicating to the core network node that the UE requested to setup the multipath relay (Figure 5 illustrates an example).

[0142] Depending on the embodiment, the multipath relay of method 1500 may use an ideal link, a PC5-link, or other suitable sidelink technology. As an example of an embodiment where the multipath relay uses an ideal link, method 1500 comprises determining whether a UE is authorized to use a multipath relay using an ideal link (operation 1502); and communicating, to a radio access network node, an indication whether the UE is authorized to use the multipath relay using the ideal link (operation 1504). Optionally, certain embodiments may (implicitly or explicitly) distinguish among different types of sidelinks. Other embodiments may simply be described in the context of multipath relays in general (without distinguishing among different types of sidelinks).Group A Embodiments

[0143] In an embodiment Al, a method performed by a user equipment (UE) (112) comprises receiving (1102) an indication from a network, the indication indicating whether the network supports multipath relays; and determining (1104) whether to initiate communication with the network via a multipath relay, the determining based at least in part on the indication from the network.

[0144] In an embodiment A2, the method of embodiment Al further comprises communicating (1106) via the multipath relay, wherein the multipath relay comprises a path using a sidelink to a second UE.

[0145] In an embodiment A3, the method of embodiment A2, wherein the UE communicates as a remote UE and the second UE communicates as a relay UE.

[0146] In an embodiment A4, the method of embodiment A2, wherein the UE communicates as a relay UE and the second UE communicates as a remote UE.

[0147] In an embodiment A5, the method of any of embodiments A1-A4, wherein the indication from the network is received in a broadcast message.

[0148] In an embodiment A6, the method of any of embodiments A1-A4, wherein the indication from the network is received in a dedicated message.

[0149] In an embodiment A7, the method of any of embodiments A 1-A6 further comprises performing a cell selection / reselection procedure using the indication from the network to select a cell that supports the multipath relays.

[0150] In an embodiment A8, the method of any of embodiments A1-A7 further comprises preparing a measurement report using the indication from the network to prioritize a measurement associated with a cell that supports the multipath relays; and communicating the measurement report to the network.

[0151] In an embodiment A9, a method performed by a user equipment (UE) (112) comprises communicating (1302), to a network, an indication that the UE supports a multipath relay; and receiving (1304), from the network, information indicating whether the network authorizes the UE to communicate via the multipath relay.

[0152] In an embodiment A 10, the method of embodiment A9, wherein communicating the indication to the network comprises sending, to the network, information indicating capabilities of the UE, the information indicating capabilities of the UE comprising the indication that the UE supports the multipath relay.

[0153] In an embodiment Al l, the method of embodiment A 10, wherein the information indicating capabilities of the UE is sent to the network during a capability enquiry procedure, the capability enquiry procedure occurring after the network has authorized the UE to access the network.

[0154] In an embodiment A 12, the method of embodiment A9, wherein communicating the indication to the network comprises sending, to the network, a request to setup the multipath operation.

[0155] In an embodiment A 13, the method of any of embodiments Al -A 12, wherein the multipath relay uses an ideal link between the UE and a second UE.

[0156] In an embodiment A 14, the method of any of embodiments Al -A 12, wherein the multipath relay uses a PC5-link between the UE and a second UE.Group B Embodiments

[0157] In an embodiment Bl, a method performed by a network node (110) comprises obtaining (1202) information indicating whether the network node supports multipath relays; and communicating (1204), to one or more user equipment (UEs), an indication whether the network node supports multipath relays, the indication based on the obtained information.

[0158] In an embodiment B2, the method of embodiment B 1 further comprises receiving, from a first UE of the one or more UEs, a request to communicate with the network via a multipath relay using a sidelink to a second UE; and determining whether to grant the request based at least in part on whether the network node supports the multipath relays.

[0159] In an embodiment B3, the method of any of embodiments B1-B2 further comprises communicating with a first of the one or more UEs via the multipath relay using the sidelink to the second UE.

[0160] In an embodiment B4, the method of any of embodiments B1-B3, wherein the indication is communicated to the one or more UEs in a broadcast message.

[0161] In an embodiment B5, the method of any of embodiments B1-B3, wherein the indication is communicated to a first UE of the one or more UEs in a dedicated message.

[0162] In an embodiment B6, a method performed by a network node (110) comprises receiving (1402), from a user equipment (UE), an indication that the UE supports a multipath relay; and communicating (1404), to the UE, information indicating whether the network authorizes the UE to communicate via the multipath relay.

[0163] In an embodiment B7, the method of embodiment B6, wherein the indication that the UE supports the multipath relay is included in information indicating capabilities of the UE.

[0164] In an embodiment B8, the method of embodiment B7, wherein the information indicating capabilities of the UE is received from the UE during a capability enquiry procedure, the capability enquiry procedure occurring after the network has authorized the UE to access the network.

[0165] In an embodiment B9, the method of embodiment B6, wherein the indication that the UE supports the multipath relay is received as a request to setup the multipath relay.

[0166] In an embodiment BIO, the method of any of embodiments B6-B9 further comprises receiving, from the core network, an indication whether the UE is authorized to use the multipath relay; and allowing or denying setup of the multipath relay based at least in part on whether the UE is authorized.

[0167] In an embodiment Bl l, the method of embodiment BIO, wherein the indication whether the UE is authorized to use the multipath relay is based on subscription information associated with the UE.

[0168] In an embodiment B12, the method of any of embodiments B10-B11, wherein the indication whether the UE is authorized to use the multipath relay is received from the core network during registration of the UE.

[0169] In an embodiment B13, the method of any of embodiments B10-B11, wherein the indication whether the UE is authorized to use the multipath relay is received from the core network in response to the network node indicating to the core network that the UE has requested to setup the multipath relay.

[0170] In an embodiment B14, a method in a core network node comprises determining (1502) whether a user equipment (UE) is authorized to use a multipath relay; and communicating (1504), to a radio access network node, an indication whether the UE is authorized to use the multipath relay.

[0171] In an embodiment B15, the method of embodiment B14, wherein the determining is based on subscription information associated with the UE.

[0172] In an embodiment Bl 6, the method of any of embodiments B14-B15, wherein the indication is communicated during registration of the UE.

[0173] In an embodiment Bl 7, the method of any of embodiments B14-B15, wherein the indication is communicated in response to the radio access network node indicating to the core network node that the UE requested to setup the multipath relay.

[0174] In an embodiment B18, the method of any of embodiments B14-B17 further comprises setting up subscription information associated with the UE.

[0175] In an embodiment Bl 9, the method of any of embodiments Bl -Bl 7, wherein the multipath relay uses an ideal link. [Or, wherein the multipath relays use ideal links]. [Or, wherein the multipath relay uses an ideal link as the sidelink to the second UE] .

[0176] In an embodiment B20, the method of any of embodiments Bl -Bl 7, wherein the multipath relay uses a PC5-link. [Or, wherein the multipath relays use PC5-links]. [Or, wherein the multipath relay uses a PC5-link as the sidelink to the second UE],Group C Embodiments

[0177] In an embodiment Cl, a user equipment comprises processing circuitry configured to perform any of the operations of any of the Group A embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0178] In an embodiment C2, a network node comprises processing circuitry configured to perform any of the operations of any of the Group B embodiments; and power supply circuitry configured to supply power to the processing circuitry.

[0179] In an embodiment C3, a user equipment (UE) comprises an antenna configured to send and receive wireless signals; radio front-end circuitry connected to the antenna and to processing circuitry, and configured to condition signals communicated between the antenna and the processing circuitry; the processing circuitry being configured to perform any of the operations of any of the Group A embodiments; an input interface connected to the processing circuitry and configured to allow input of information into the UE to be processed by the processing circuitry; an output interface connected to the processing circuitry and configured to output information from the UE that has been processed by the processing circuitry; and a battery connected to the processing circuitry and configured to supply power to the UE.

[0180] In certain embodiments, a wireless device (e.g., UE) and a network node (e.g., gNB) may perform reciprocal operations. For example, a message sent from a wireless device to a network node may be received by the network node from the wireless device, and vice versa. Similarly, a network node (e.g., gNB or other radio access network node) and a core network node may perform reciprocal operations. For example, a message sent from a gNB to a CN node may be received by the CN node from the gNB, and vice versa. The disclosure encompasses embodiments from the perspective of each node.

[0181] Although the computing devices described herein (e.g., UEs, network nodes, hosts) may include the illustrated combination of hardware components, other embodiments may comprise computing devices with different combinations of components. It is to be understood that these computing devices may comprise any suitable combination of hardware and / or software needed to perform the tasks, features, functions and methods disclosed herein. Determining, calculating, obtaining or similar operations described herein may be performed by processing circuitry, which may process information by, for example, converting the obtained information into other information, comparing the obtained information or converted information to information stored in the network node, and / or performing one or more operations based on the obtained information or converted information, and as a result of saidprocessing making a determination. Moreover, while components are depicted as single boxes located within a larger box, or nested within multiple boxes, in practice, computing devices may comprise multiple different physical components that make up a single illustrated component, and functionality may be partitioned between separate components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of the components may be partitioned between the processing circuitry and the communication interface. In another example, non-computationally intensive functions of any of such components may be implemented in software or firmware and computationally intensive functions may be implemented in hardware.

[0182] In certain embodiments, some or all of the functionality described herein may be provided by processing circuitry executing instructions stored on in memory, which in certain embodiments may be a computer program product in the form of a non-transitory computer- readable storage medium. In alternative embodiments, some or all of the functionality may be provided by the processing circuitry without executing instructions stored on a separate or discrete device-readable storage medium, such as in a hard-wired manner. In any of those particular embodiments, whether executing instructions stored on a non-transitory computer- readable storage medium or not, the processing circuitry can be configured to perform the described functionality. The benefits provided by such functionality are not limited to the processing circuitry alone or to other components of the computing device, but are enjoyed by the computing device as a whole, and / or by end users and a wireless network generally.

[0183] Modifications, additions, or omissions may be made to the methods described herein without departing from the scope of the disclosure. The methods may include more, fewer, or other operations. Additionally, operations may be performed in any suitable order.

[0184] Although this disclosure has been described in terms of certain embodiments, alterations and permutations of the embodiments will be apparent to those skilled in the art. Accordingly, the description of the embodiments does not constrain this disclosure. Other changes, substitutions, and alterations are possible.

Claims

CLAIMS1. A method performed by a user equipment (UE) (112, 200), the method comprising: receiving (1102) an indication from a network, the indication indicating whether the network supports multipath relays; determining (1104) whether to initiate communication with the network via a multipath relay, the determining based at least in part on the indication from the network; and communicating (1106) via the multipath relay, wherein the multipath relay comprises a path using a sidelink to a second UE.

2. The method of claim 1, wherein the sidelink is an ideal link.

3. The method of any of claims 1-2, wherein the UE communicates as a remote UE and the second UE communicates as a relay UE.

4. The method of any of claims 1-2, wherein the UE communicates as a relay UE and the second UE communicates as a remote UE.

5. The method of any of claims 1-4, wherein the indication from the network is received in a broadcast message.

6. The method of any of claims 1-5, wherein the indication from the network is received in a system information block (SIB).

7. The method of any of claims 1-6, further comprising: performing a cell selection / reselection procedure using the indication from the network to select a cell that supports the multipath relays.

8. The method of any of claims 1-7, further comprising: preparing a measurement report using the indication from the network to prioritize a measurement associated with a cell that supports the multipath relays; and communicating the measurement report to the network.

9. A method performed by a network node (110, 300), the method comprising: obtaining (1202) information indicating whether the network node supports multipathrelays; and communicating (1204), to one or more user equipment (UEs), an indication whether the network node supports multipath relays, the indication based on the obtained information.

10. The method of claim 9, further comprising: receiving, from a first UE of the one or more UEs, a request to communicate with the network via a multipath relay using a sidelink to a second UE; and determining whether to grant the request based at least in part on whether the network node supports the multipath relays.

11. The method of any of claims 9-10, further comprising: communicating with a first of the one or more UEs via the multipath relay using the sidelink to the second UE.

12. The method claims 9-11, wherein the sidelink is an ideal link.

13. The method of any of claims 9-12, wherein the indication is communicated to the one or more UEs in a broadcast message.

14. The method of any of claims 9-13, wherein the indication is communicated to the one or more UEs in a system information block (SIB).

15. A user equipment (112, 200), comprising: processing circuitry (202) configured to perform the operations of any of claims 1-8; and power supply circuitry (208) configured to supply power to the processing circuitry.

16. A network node (110, 300), the network node comprising: processing circuitry (302) configured to perform the operations of any of claims 9-14; power supply circuitry (308) configured to supply power to the processing circuitry.

Images