Relay node with multi-connectivity cellular backhaul

Abstract

A method of wireless communication at a relay node is described. The method can include transmitting, using a first mobile terminal functionality of the relay node, a measurement report to a network management functionality via a first backhaul link to a first parent node, where the measurement report includes measurements transmitted by a second parent node. The method can also include receiving, using the first mobile terminal functionality of the relay node via the first backhaul link, a backhaul link configuration for a second mobile terminal functionality based on the transmitted measurement report, and establishing a second backhaul link between the second mobile terminal functionality of the relay node and the second parent node based on the received backhaul link configuration.

Description

[0001] This application is a divisional application of the invention patent filed on September 17, 2019, with application number "201980060264.7" and invention title "Relay Node with Multi-Connection Cellular Backhaul".

[0002] Cross-reference to related applications

[0003] This patent application claims priority to U.S. Patent Application No. 16 / 572,219, filed September 16, 2019, entitled “RELAY NODES WITH MULTI-CONNECTED CELLULAR BACKHAUL,” and U.S. Provisional Patent Application No. 62 / 734,947, filed September 21, 2018, entitled “RELAY NODES WITH MULTI-CONNECTED CELLULAR BACKHAUL,” which is assigned to the assignee. Technical Field

[0004] The following generally pertains to wireless communication, and more specifically to the management of relay nodes with multi-backhaul connections. Background Technology

[0005] Wireless communication systems are widely deployed to provide various types of communication content, such as audio, video, packet data, messaging, and broadcasting. These systems are capable of supporting communication with multiple users by sharing available system resources (e.g., time, frequency, and power). Examples of such multi-access systems include fourth-generation (4G) systems, such as Long Term Evolution (LTE), LTE-A, or LTE-A Pro systems; and fifth-generation (5G) systems, which may be referred to as New Radio (NR) systems. These systems can employ technologies such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), or Discrete Fourier Transform-Distributed-OFDM (DFT-S-OFDM). A wireless multi-access communication system can comprise several base stations or network access nodes, each simultaneously supporting communication from multiple communication devices, which may be called User Equipment (UE).

[0006] In some wireless communication systems (e.g., 5G NR systems), NR access infrastructure and spectrum resources can additionally support wireless backhaul link capabilities as a supplement to cable backhaul connections to provide an Integrated Access and Backhaul (IAB) network architecture. One or more base stations may contain centralized units (CUs) and distributed units (DUs) and may be referred to as donor base stations. One or more DUs associated with a donor base station may be partially controlled by the CU associated with the donor base station. One or more donor base stations (e.g., IAB donors) may communicate with one or more additional base stations (e.g., IAB nodes or relay nodes) via supported access and backhaul links. IAB nodes may support mobile terminal (MT) functionality, which is controlled and / or scheduled by the DUs of the coupled IAB donor or parent IAB node, and by DUs associated with additional entities (e.g., child IAB nodes, UEs, etc.) within the configuration of the relay link or access network.

[0007] In some cases, upstream connections in an IAB network (e.g., the connection between the MT functionality of a relay node and the DU of a parent node) can be degraded due to factors such as uplink synchronization loss, poor channel conditions, and communication interference. This can lead to reduced throughput, radio link failure (RLF) processes, increased latency, and other issues that may impair system performance. Summary of the Invention

[0008] The described techniques relate to improved methods, systems, apparatuses, or devices according to various aspects of this disclosure. Generally, the described techniques support the configuration of relay nodes with multi-MT functionality that provides cellular backhaul with multiple connections. For example, network management functions (e.g., in an IAB network architecture) can configure multiple (e.g., redundant) backhaul routes for relay nodes with multi-MT functionality, where each MT function can support a wireless backhaul link (e.g., via different parent nodes in the IAB network).

[0009] In some examples, the network management function may have explicit awareness and control over multi-MT operation. For instance, a relay node (e.g., supporting multi-MT functionality) may establish a first backhaul link between a first MT and a first parent node (e.g., a first parent node under the control of the network management function). The relay node may transmit a capability report to the network management function via the first backhaul link using the first MT functionality. The capability report may include the relay node's capabilities with respect to MT functionality (e.g., the number of supported MT functions, identifiers of the supported MTs, isolation between different MT functions, etc.) and the capabilities of individual MT functions (e.g., radio access technology (RAT) supported by a second MT function, frequency bands supported by the second MT function, azimuth and elevation modes supported by the second MT function, etc.). The network management function may receive the capability report from the relay node's first MT (e.g., via the first backhaul link) and may identify the relay node's measurement configuration (e.g., based on the capabilities indicated by the relay node). The measurement configuration may include identifiers of the MT function to be measured, identifiers of the parent node to be measured, and identifiers of the measurements to be performed (e.g., Received Signal Strength Indicator (RSSI) measurement, Reference Signal Received Power (RSRP) measurement, etc.). The network management function can then transmit the measurement configuration to the relay node via the first backhaul link.

[0010] The relay node can receive measurement configurations and perform measurements on the second parent node based on these configurations (e.g., using the second MT function). The relay node can transmit a measurement report containing measurement information to the network management function via a first backhaul link to the first parent node. The network management function can then identify the backhaul link configuration for the second MT function based on the received measurement report. In some cases, the backhaul link configuration may include information about the establishment and operation of the second backhaul link (e.g., the identifier of the second parent node to connect to, routing utilization information, link utilization information, resource allocation information, etc.). The network function can transmit the backhaul link configuration to the relay node via the first backhaul link. The relay node can establish a second backhaul link between the second MT and the second parent node based on the backhaul link configuration. Additionally, the second MT can use the backhaul link according to its configuration. For example, in some cases, the first and second backhaul links can be used simultaneously (e.g., in parallel). In other cases, the second backhaul link can be used as a backup backhaul link.

[0011] In other examples, the relay node's MT function can autonomously connect to the parent node, and the network management function can coordinate the backhaul configuration when multiple MT functions associated with the same relay node autonomously (e.g., independently) connect to the network management function on two or more backhaul links. For example, a relay node can establish a first backhaul link between a first MT and a first parent node (e.g., based on some performed measurement and parent selection policy), and can also establish a second backhaul link between a second MT and a second parent node (e.g., based on some performed measurement and parent selection policy). The relay node can use the first MT to exchange its identifier with the first network management function (e.g., the first network management function can generate a relay identifier for the relay node and transmit the relay identifier to the first MT, or the relay node can identify the relay identifier and transmit the relay identifier to the network management function). The relay node can then use the second MT to transmit the relay identifier to the second network management function via a second backhaul link to the second parent node (e.g., where the second network management function can be the same as or different from the first network management function, as determined in the following discussion).

[0012] When a relay node autonomously connects to two parent nodes under the control of the same network management function (e.g., when the first and second network management functions are the same), the network management function can receive relay identifiers on both links (e.g., from the first and second parent nodes) and can identify a relay node's dual connection to the network management function. In such a case, the network management function can coordinate the use of the first and second backhaul links based on the identification of the relay node's dual connection to the network management function (e.g., the network management function can transmit a backhaul link configuration to the second MT on the second link, or it can transmit a backhaul link configuration of the second MT to the first MT on the first link, where the backhaul link configuration includes the identifier of the second MT). When a relay node autonomously connects to parent nodes under the control of different network management functions, the relay node can connect to two different network management functions.

[0013] A method for wireless communication at a relay node is described. The method may include transmitting a measurement report to a network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, wherein the measurement report includes measurements transmitted by a second parent node. The method may further include receiving a backhaul link configuration for a second mobile terminal function via the first backhaul link based on the transmitted measurement report, and establishing a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0014] An apparatus for wireless communication at a relay node is described. The apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executed by the processor to cause the apparatus to transmit a measurement report to a network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, wherein the measurement report contains measurements transmitted by a second parent node. The instructions may also be executed by the processor to further cause the apparatus to receive a backhaul link configuration for a second mobile terminal function via the first backhaul link based on the transmitted measurement report, and to establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0015] Another device for wireless communication at a relay node is described. The device may include components for transmitting a measurement report to a network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, wherein the measurement report contains measurements transmitted by a second parent node. The device may also include components for receiving a backhaul link configuration of a second mobile terminal function via the first backhaul link based on the transmitted measurement report, and for establishing a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0016] A non-transitory computer-readable medium is described, storing code for wireless communication at a relay node. The code may contain processor-executable instructions to transmit a measurement report to a network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, wherein the measurement report contains measurements transmitted by a second parent node. The code may also contain instructions, further processor-executable, to receive a backhaul link configuration for a second mobile terminal function via the first backhaul link based on the transmitted measurement report, and to establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0017] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving routing configurations for a first backhaul link and a second backhaul link, wherein the routing configurations include routing utilization information, link utilization information, resource allocation information, or combinations thereof.

[0018] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a capability report to a network management function via a first backhaul link using a first mobile terminal function, receiving a measurement configuration of a second mobile terminal function of a relay node via the first backhaul link based on the transmitted capability report, and performing measurements transmitted by a second parent node using the second mobile terminal function of the relay node based on the measurement configuration, wherein the transmitted measurement report contains measurements.

[0019] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability report includes an identifier of a second mobile terminal function, one or more RATs supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, radio frequency (RF) capabilities of the second mobile terminal function, isolation between the first and second mobile terminal functions, an identifier of a relay node, a list of supported mobile terminal functions, or some combination thereof.

[0020] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the measurement configuration includes an identifier for the second mobile terminal function, an identifier for the second parent node, or combinations thereof. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration for the second mobile terminal function includes an identifier for the second mobile terminal function of the relay node, an identifier for the second parent node, routing configuration parameters, or combinations thereof.

[0021] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second mobile terminal function can be received within a container of a Radio Resource Control (RRC) message received by the first mobile terminal function. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second mobile terminal function can be received in an F1 Application Protocol (F1-AP) signaling notification. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first parent node and the second parent node can be associated with network management functions supported by the CU.

[0022] In some examples of the methods, devices, and non-transitory computer-readable media described herein, network management functions include next-generation Node B (gNB), gNB-Central Unit (gNB-CU), gNB-CU-Control Plane (gNB-CU-CP), evolved Node B (eNB), eNB-Central Unit (eNB-CU), eNB-CU-Control Plane (eNB-CU-CP), centralized controller, topology functions, routing functions, resource functions, or combinations thereof.

[0023] A method for wireless communication is described. The method may include receiving, via a first backhaul link, a measurement report from a relay node for a first mobile terminal function, wherein the measurement report includes measurements transmitted by a second parent node. The method may further include identifying a backhaul link configuration for a second mobile terminal function based on the received measurement report, and transmitting the identified backhaul link configuration for the second mobile terminal function to the first mobile terminal function at the relay node via the first backhaul link.

[0024] A device for wireless communication is described. The device may include a processor, memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be processor-executable to cause the device to receive, via a first backhaul link, a measurement report from a first mobile terminal function of a relay node, wherein the measurement report contains measurements transmitted by a second parent node. The instructions may also be processor-executable to further cause the device to identify a backhaul link configuration for the second mobile terminal function based on the received measurement report, and for the network management function to transmit the identified backhaul link configuration for the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link.

[0025] Another device for wireless communication is described. The device may include components for receiving, via a first backhaul link, a measurement report from a relay node for a first mobile terminal function, wherein the measurement report contains measurements transmitted by a second parent node. The device may also include components for identifying a backhaul link configuration of the second mobile terminal function based on the received measurement report, and for transmitting the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link by the network management function.

[0026] A non-transitory computer-readable medium storing code for wireless communication is described. The code may contain processor-executable instructions to receive, via a first backhaul link, a measurement report from a first mobile terminal function at a relay node, wherein the measurement report contains measurements transmitted by a second parent node. The code may also contain instructions further processor-executable to identify a backhaul link configuration for the second mobile terminal function based on the received measurement report, and to transmit the identified backhaul link configuration for the second mobile terminal function to the first mobile terminal function at the relay node via the first backhaul link.

[0027] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for routing configuration of a second backhaul link between a second mobile terminal function of a relay node and a first parent node, and a first backhaul link between a first MT of a relay node and the first parent node, wherein the routing configuration includes routing utilization information, link utilization information, resource allocation information, or some combination thereof.

[0028] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a capability report from a first mobile terminal function of a relay node via a first backhaul link by a network management function, wherein the capability report contains capability information of a second mobile terminal function of the relay node, identifying a measurement configuration of the second mobile terminal function of the relay node based on the received capability report, and transmitting the identified measurement configuration to the first mobile terminal function via the first backhaul link by the network management function, wherein a measurement report may be received based on the transmitted measurement configuration.

[0029] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the capability report includes an identifier of a second mobile terminal function, one or more RATs supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, RF capabilities of the second mobile terminal function, isolation between the first and second mobile terminal functions, an identifier of a relay node, a list of supported mobile terminal functions, or some combination thereof.

[0030] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the measurement configuration includes an identifier for the second mobile terminal function, an identifier for the second parent node, or combinations thereof. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration for the second mobile terminal function includes an identifier for the second mobile terminal function of the relay node, an identifier for the second parent node, routing configuration parameters, or combinations thereof.

[0031] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second mobile terminal function can be transmitted to the first mobile terminal function within a container of an RRC message. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second mobile terminal function can be transmitted in an F1-AP signaling notification. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the first backhaul link between the first mobile terminal function of the relay node and the first parent node, and the second backhaul link between the second mobile terminal function of the relay node and the first parent node, can be associated with a cellular RAT.

[0032] A method for wireless communication at a relay node is described. The method may include exchanging a relay node identifier with a first network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, and transmitting the relay node identifier to a second network management function via a second backhaul link to a second parent node using a second mobile terminal function of the relay node. The method may further include receiving a backhaul link configuration for the second mobile terminal function based on transmitting the relay node identifier to the first network management function via the first backhaul link and transmitting the relay node identifier to the second network management function via the second backhaul link.

[0033] An apparatus for wireless communication at a relay node is described. The apparatus may include a processor, memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be processor-executable to cause the apparatus to exchange a relay node identifier with a first network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, and to transmit the relay node identifier to a second network management function via a second backhaul link to a second parent node using a second mobile terminal function of the relay node. The instructions may also be processor-executable to further cause the apparatus to receive a backhaul link configuration of a second mobile terminal function based on transmitting the relay node identifier to the first network management function via the first backhaul link and transmitting the relay node identifier to the second network management function via the second backhaul link.

[0034] Another device for wireless communication at a relay node is described. The device may include components for exchanging a relay node identifier with a first network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node, and for transmitting the relay node identifier to a second network management function via a second backhaul link to a second parent node using a second mobile terminal function of the relay node. The device may also include components for receiving a backhaul link configuration of the second mobile terminal function based on transmitting the relay node identifier to the first network management function via the first backhaul link and transmitting the relay node identifier to the second network management function via the second backhaul link.

[0035] A non-transitory computer-readable medium is described, storing code for wireless communication at a relay node. The code may contain instructions executable by a processor to exchange a relay node identifier with a first network management function via a first backhaul link to a first parent node using a first mobile terminal function of the relay node; to transmit the relay node identifier to a second network management function via a second backhaul link to a second parent node using a second mobile terminal function of the relay node; and to receive the second mobile terminal function based on a backhaul link configuration that transmits the relay node identifier to the first network management function via the first backhaul link and to the second network management function via the second backhaul link.

[0036] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for exchanging backhaul information with a first mobile terminal function and a first network management function via a first backhaul link to a first parent node, or exchanging backhaul information with a second mobile terminal function and a second network management function via a second backhaul link to a second parent node, or both, based on a received backhaul link configuration.

[0037] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for establishing a first backhaul link between a first mobile terminal function of a relay node and a first parent node, wherein an identifier of the relay node may be transmitted to a first network management function via the established first backhaul link, and for establishing a second backhaul link between a second mobile terminal function of a relay node and a second parent node, wherein an identifier of the relay node may be transmitted to a second network management function via the established second backhaul link.

[0038] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving an identifier of a first network management function associated with a first backhaul link and receiving an identifier of a second network management function associated with a second backhaul link. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the identifier of the first management function associated with the first backhaul link may be different from the identifier of the second management function associated with the second backhaul link, and that a backhaul link configuration identifying a second mobile terminal function may be associated with the second management function of the second backhaul link.

[0039] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for determining that the identifier of a first management function associated with a first backhaul link may be the same as the identifier of a second management function associated with a second backhaul link, and for identifying that the backhaul link configuration of a second mobile terminal function may be associated with the same management function of the first and second backhaul links.

[0040] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, establishing a second backhaul link between a second mobile terminal function of a relay node and a second parent node may also include operations, features, components, or instructions for using the second mobile terminal function to perform one or more signal strength measurements of one or more parent nodes, and for identifying the second parent node based on one or more signal strength measurements, wherein the second backhaul link may be established based on the identified second parent node.

[0041] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving a measurement configuration of a second mobile terminal function using a first mobile terminal function of a relay node, wherein one or more signal strength measurements may be performed based on the received measurement configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for exchanging backhaul information using a first backhaul link, a second backhaul link, or both, based on a received backhaul link configuration.

[0042] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a capability report to a second parent node using a second mobile terminal function, wherein the capability report includes an identifier of the second mobile terminal function, one or more RATs supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, RF capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

[0043] In some examples of the methods, apparatuses, and non-transitory computer-readable media described herein, the first network management function and the second network management function each include a gNB, gNB-CU, gNB-CU-CP, eNB, eNB-CU, eNB-CU-CP, a central controller, a topology function, a routing function, a resource function, or some combination thereof.

[0044] A method for wireless communication in a CU is described. The method may include: identifying a relay node connected to a first parent node via a first mobile terminal function of the relay node, identifying a relay node connected to a second parent node via a second mobile terminal function of the relay node, and transmitting a backhaul link configuration of the second mobile terminal function based on the identified relay node connection.

[0045] A device for wireless communication in a CU is described. The device may include a processor, memory in electronic communication with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the device to identify a relay node connected to a first parent node via a first mobile terminal function of the relay node, identify a relay node connected to a second parent node via a second mobile terminal function of the relay node, and transmit a backhaul link configuration for the second mobile terminal function based on the identified relay node connection.

[0046] Another device for wireless communication in a CU is described. The device may include components for identifying a relay node connected to a first parent node via a first mobile terminal function of the relay node, identifying a relay node connected to a second parent node via a second mobile terminal function of the relay node, and transmitting a backhaul link configuration of the second mobile terminal function based on the identified relay node connection.

[0047] A non-transitory computer-readable medium is described, storing code for wireless communication in a CU. The code may contain instructions executable by a processor to identify a relay node connected to a first parent node via a first mobile terminal function of the relay node, to identify a relay node connected to a second parent node via a second mobile terminal function of the relay node, and to transmit a backhaul link configuration of the second mobile terminal function based on the identified relay node connection.

[0048] Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for receiving backhaul information from a first mobile terminal function of a relay node via a first parent node, and receiving backhaul information from a second mobile terminal function of a relay node via a second parent node, or both, based on the transmitted backhaul link configuration. Some examples of the methods, apparatuses, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a network management function identifier to a relay node via a first parent node, and transmitting a management function identifier to a relay node via a second parent node.

[0049] In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, identifying that a relay node can be connected to a second parent node via a second mobile terminal function of the relay node may include operations, features, components, or instructions for receiving an identifier of the relay node from a first parent node and receiving an identifier of the relay node from a second parent node, wherein identifying that a relay node can be connected to a second parent node via a second mobile terminal function of the relay node may be based on the fact that the identifier of the relay node from the second parent node is the same as the identifier of the relay node from the first parent node.

[0050] Some examples of the methods, apparatus, and non-transitory computer-readable media described herein may also include operations, features, components, or instructions for transmitting a measurement configuration of a second mobile terminal function to a relay node, wherein the measurement configuration includes an identifier of a second parent node, relay node selection policy information of the second parent node, or some combination thereof. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second mobile terminal function may be transmitted to the first mobile terminal function within a container of an RRC message. In some examples of the methods, apparatus, and non-transitory computer-readable media described herein, the backhaul link configuration of the second MT may be transmitted in an F1-AP signaling notification. Attached Figure Description

[0051] Figure 1 An example of a wireless communication system supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is illustrated.

[0052] Figure 2 and Figure 3 An exemplary wireless communication system supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is illustrated.

[0053] Figure 4 An example flowchart illustrating a relay node supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is shown.

[0054] Figure 5 An example of a processing flow for a relay node supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is illustrated.

[0055] Figure 6 An example flowchart illustrating a relay node supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is shown.

[0056] Figure 7 An example of a processing flow for a relay node supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is illustrated.

[0057] Figure 8 and Figure 9 A block diagram of an apparatus for supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0058] Figure 10 A block diagram of a communication manager supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0059] Figure 11 A diagram of a system comprising an apparatus for supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0060] Figure 12 and Figure 13 A block diagram of an apparatus for supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0061] Figure 14 A block diagram of a communication manager supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0062] Figure 15 A diagram of a system comprising an apparatus for supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown.

[0063] Figures 16 to 20A flowchart illustrating a method for supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown. Detailed Implementation

[0064] In some wireless communication systems (e.g., 5G NR systems), the infrastructure and spectrum resources for NR access can additionally support wireless backhaul link capabilities as a supplement to cable backhaul connections to provide an IAB network architecture. One or more base stations may contain CUs and DUs and may be referred to as donor base stations (e.g., IAB donors). One or more DUs associated with a donor base station may be partially controlled by the CU associated with the donor base station. The base station CU may be a component of a database, data center, core network, or network cloud. Network nodes associated with a RAT can communicate with the donor base station CU via a backhaul link (e.g., cable backhaul or wireless backhaul). One or more donor base stations (e.g., IAB donors) can communicate with one or more additional base stations (e.g., IAB nodes or relay nodes) and the UE. IAB nodes can support MT functionality controlled and scheduled by the IAB donor and / or parent IAB nodes relative to the MT-supported IAB nodes. IAB nodes can additionally support DU operability relative to additional entities (e.g., child IAB nodes, UEs, etc.) within the configuration of the relay chain or access network (e.g., relative to entities downstream of the IAB node). For example, the IAB network architecture can include chains of radio devices (e.g., starting at a donor base station and ending at a UE, with any number of IAB relay nodes in between) connected via link resources that support NR access and backhaul capabilities (e.g., cable backhaul or wireless backhaul).

[0065] A relay node can be an intermediate node in a relay chain (e.g., an IAB relay chain). For example, a relay node can relay communication between a parent node (e.g., an IAB donor, or an IAB node upstream or higher in the relay chain) and a child node (e.g., an IAB node downstream or lower in the relay chain). In some cases, a relay node can be an IAB node's DU or Access Node Function (AN-F). A child node can be an IAB-node (e.g., an IAB-node's MT) or a UE that is a child of another IAB-node (e.g., such as a relay node). A parent node communicating with a relay node can be an upstream IAB-node or an IAB-donor (e.g., an IAB-node or IAB-donor's DU / AN-F). In some cases, a parent node can be referred to as a control node (e.g., a control node can be an IAB node, or a parent node's DU that communicates with a relay node or another intermediate IAB node's MT).

[0066] The techniques presented herein can enhance the efficiency of certain wireless communication systems, including those that use wireless connections between nodes (e.g., base stations) for backhaul communication. In wireless communication systems that use cable links for backhaul communication, wireless nodes can enjoy robust cable links to a network entity that coordinates aspects of backhaul communication for adjacent nodes (e.g., the network entity provides timing information, cell identity, etc.) to coordinate backhaul transmission. However, in some systems, deploying cable links to wireless nodes can result in significant costs and resource expenditures. For example, wireless nodes operating in the millimeter-wave (mmW) frequency range may be associated with reduced coverage areas (e.g., smaller geographic footprint, directional transmission, etc.), which may necessitate deploying a large number of access nodes (e.g., wireless nodes or IAB nodes) to provide acceptable coverage to users. Therefore, the number of wireless nodes within a wireless communication system may not be coupled to cable backhaul links, and wireless backhaul links can be used alternatively for backhaul communication on wireless backhaul networks (e.g., such as IAB networks).

[0067] The described technique provides maintenance of wireless backhaul connections by using multiple wireless backhaul links. For example, in some cases, a relay node can support multiple MT functionalities (e.g., a relay node can contain multiple MT entities) and can connect to different parent IAB nodes using different MT functionalities. This allows the relay node to establish multiple paths (e.g., redundant paths) for multiple wireless backhaul links. That is, the relay node can establish multiple wireless backhaul links via multiple MT links leading to different parent nodes connected to the same CU or network management function through different paths in the relay chain. In some cases, all established wireless backhaul links (e.g., wireless backhaul links established by each MT of the relay node) can be used in parallel (e.g., simultaneously) for backhaul communication. In other cases, a subset of wireless backhaul links can be used for backhaul communication, and the remaining wireless backhaul links can be used for backup purposes (e.g., when a subset of backhaul links is degraded due to uplink synchronization loss, poor channel conditions, communication interference, etc.).

[0068] The described technology also provides mechanisms for coordinating network management functions (e.g., network or CU) and the configuration of multiple such wireless backhaul links. In some cases, where a relay node supports multiple (e.g., more than one) MT functionalities, the network management function can be notified of the relay node's capabilities regarding the MT functionalities. For example, a relay node can use a first MT functional to establish a first backhaul link to the network management function (e.g., to a first parent node). The relay node can use the first backhaul link to transmit capability reports (e.g., a list or identifier of additional supported MT functionalities, RATs supported by the additional MT functionalities, frequency bands supported by the additional MT functionalities, RF capabilities of the additional MT functionalities, etc.) to the network management function (e.g., via the first backhaul link to the first parent node). The network management function can then identify some or all of the measurement configurations of the relay node's additional MT functionalities based on the capability reports (e.g., based on the capabilities of the additional MT functionalities supported by the relay node). The network management function can then transmit the measurement configurations to the relay node via the first backhaul link. The relay node can perform measurements on the parent node using one or all of the additional MT functions, depending on the measurement configuration (e.g., the measurement configuration may include identifiers of the additional MT functions to be measured, identifiers of the parent node to be measured, etc.). The relay node can then transmit the measurement report to the network management function via the first backhaul link using the relay node's first MT function.

[0069] The network management function can thus coordinate and configure additional backhaul links for relay nodes based on received measurement reports. For example, the network management function can transmit the backhaul link configuration of the second MT function to the relay node via the first backhaul link, and the relay node can establish a second wireless backhaul link to the second parent node (e.g., where the second MT function and the second parent node can be indicated by the backhaul link configuration).

[0070] In other examples, the multi-MT functionality of a relay node can autonomously connect to different parent nodes (e.g., it may or may not be associated with the same network management function). For example, in some cases, the relay node's MT functionality can autonomously search for parent nodes (e.g., perform parent node transmit measurements). In such an example, the relay node can exchange (e.g., using the relay node's first MT functionality) its identifier with a first network management function via a first backhaul link to a first parent node. The relay node can also transmit (e.g., using the relay node's second MT functionality) its identifier to a second network management function via a second backhaul link to a second parent node. Thus, when both parent nodes (e.g., or backhaul links) are associated with the same network management function, the management function can receive the relay node identifier via both backhaul links and can identify that the relay node supports multiple backhaul links. In such a scenario, network management functions can transmit backhaul link configurations (e.g., for a first MT function, a second MT function, or both) to the relay node (e.g., via a first backhaul link, a second backhaul link, or both) based on the identifier that the relay node supports multiple backhaul link connections.

[0071] Advantageously, techniques such as those described herein that support relay nodes with multiple backhaul links (e.g., multi-hop backhaul links) can improve backhaul communication robustness (e.g., by using additional wireless backhaul links to reduce service interruptions, signaling notification delays, etc., associated with degraded wireless backhaul links). Network management functions can identify that a relay node supports multiple backhaul connections and can coordinate and configure multiple backhaul connections using the techniques described herein. For example, network management functions can thus configure the use of parallel wireless backhaul links (e.g., this can increase backhaul throughput, add wireless link redundancy for more reliable backhaul communication, etc.). In other examples, network management functions can configure backup wireless backhaul links (e.g., this can be used when the first or primary wireless backhaul link degrades, when measurement reports indicate that a second wireless backhaul link can be more reliable, etc.).

[0072] Aspects of this disclosure are initially described in the context of a wireless communication system. Exemplary wireless communication systems, flowcharts, and processing flows implementing the discussed techniques are then described. Aspects of this disclosure are further illustrated and described with reference to device diagrams, system diagrams, and flowcharts relating to relay nodes with multi-connectivity cellular backhaul.

[0073] Figure 1An example of a wireless communication system 100 supporting relay nodes with multi-connection cellular backhaul according to one or more aspects of this disclosure is illustrated. The wireless communication system 100 includes network device 105, UE 115, and core network 130. In some examples, the wireless communication system 100 may be an LTE network, an LTE-A network, an LTE-A Pro network, or an NR network. In some cases, the wireless communication system 100 may support enhanced broadband communication, ultra-reliable (e.g., mission-critical) communication, low-latency communication, or communication using low-cost and low-complexity devices. The wireless communication system 100 may support signaling notification between network devices 105 to establish multi-backhaul connections for relay nodes (e.g., network device 105) supporting multiple MT functionality.

[0074] Core network 130 can provide user authentication, access authorization, tracking, Internet Protocol (IP) connectivity, and other access, routing, or mobility functions. Core network 130 may be an evolved packet core (EPC), which may include at least one Mobility Management Entity (MME), at least one Serving Gateway (S-GW), and at least one Packet Data Network (PDN) Gateway (P-GW). The MME can manage non-access stratum (e.g., control plane) functions, such as mobility, authentication, and bearer management of UE 115 served by network apparatus 105 associated with the EPC. User IP packets can be transmitted through the S-GW, which itself can be connected to the P-GW. The P-GW can provide IP address allocation and other functions. The P-GW can be connected to network operator IP services. Operator IP services may include access to the Internet, intranet(s), IP Multimedia Subsystem (IMS), or packet-switched (PS) streaming services.

[0075] At least some of the network devices 105 (e.g., network device 105-a, which may be an example of a base station (e.g., an eNB, a network access device, a gNB), or network device 105-b, which may be an example of an access node controller (ANC)) can be connected to the core network 130 via backhaul links 132 (e.g., S1, S2) and can perform radio configuration and scheduling of communications with UE 115. In various examples, network devices 105-b can communicate with each other directly or indirectly (e.g., via the core network 130) on backhaul links 134 (e.g., X1, X2), which can be wired or wireless communication links.

[0076] Each network device 105-b may also additionally or alternatively communicate with several other network devices 105-c via several other network devices 105-c, wherein network device 105-c may be an example of a smart radio header (or via several smart radio headers). In alternative configurations, the various functions of each network device 105 may be distributed across various network devices 105 (e.g., radio headers and access network controllers) or combined into a single network device 105 (e.g., a base station).

[0077] Network device 105 can wirelessly communicate with UE 115 via one or more base station antennas. Network device 105 described herein may include, or be referred to by those skilled in the art as, a base station transceiver, radio base station, access point, radio transceiver, NodeB, eNB, next-generation Node B or gigabit nodeB (any of which may be referred to as gNB), home NodeB, home eNodeB, or some other suitable terminology. Wireless communication system 100 may include different types of network devices 105 (e.g., macro or small cell base stations). UE 115 described herein is capable of communicating with various types of network devices 105 and network equipment, including macro eNBs, small cell eNBs, gNBs, relay base stations, etc.

[0078] Each network device 105 can be associated with a specific geographic coverage area 110, supporting communication with various UEs 115 within that geographic coverage area 110. Each network device 105 can provide communication coverage for the corresponding geographic coverage area 110 via a communication link 125, and the communication link 125 between the network device 105 and the UE 115 can utilize one or more carriers. The communication link 125 shown in the wireless communication system 100 can include an uplink transmission from the UE 115 to the network device 105, or a downlink transmission from the network device 105 to the UE 115. The downlink transmission can also be referred to as a forward link transmission, and the uplink transmission can also be referred to as a reverse link transmission.

[0079] The geographic coverage area 110 of network device 105 can be divided into sectors, each sector constituting only a portion of the geographic coverage area 110, and each sector can be associated with a cell. For example, each network device 105 can provide communication coverage for macro cells, small cells, hotspots, or other types of cells, or various combinations thereof. In some examples, network device 105 can be mobile, and thus provide communication coverage for mobile geographic coverage areas 110. In some examples, different geographic coverage areas 110 associated with different technologies can overlap, and overlapping geographic coverage areas 110 associated with different technologies can be supported by the same network device 105 or by different network devices 105. Wireless communication system 100 can include, for example, heterogeneous LTE / LTE-A / LTE-A Pro or NR networks, where different types of network devices 105 provide coverage for various geographic coverage areas 110.

[0080] The term "cell" refers to a logical communication entity used to communicate with network device 105 (e.g., on a carrier) and may be associated with an identifier (e.g., Physical Cell Identifier (PCID), Virtual Cell Identifier (VCID)) used to distinguish adjacent cells operating via the same or different carriers. In some examples, a carrier may support multiple cells and may be configured with different cells based on different protocol types that can provide access for different types of devices (e.g., Machine-Type Communication (MTC), Narrowband Internet of Things (NB-IoT), Enhanced Mobile Broadband (eMBB), or others). In some cases, the term "cell" may refer to a portion of the geographical coverage area 110 (e.g., a sector) on which the logical entity operates.

[0081] UE 115 can be distributed throughout the wireless communication system 100, and each UE 115 can be stationary or mobile. UE 115 can also be referred to as a mobile device, wireless device, remote device, handheld device, or subscriber device, or some other suitable term, wherein "device" can also be referred to as a unit, station, terminal, or client. UE 115 can also be a personal electronic device, such as a cellular phone, personal digital assistant (PDA), tablet computer, laptop computer, or personal computer. In some examples, UE 115 can also involve a wireless local loop (WLL) station, Internet of Things (IoT) device, Internet of Everything (IoE) device, or MTC device, which can be implemented as various objects, such as home appliances, vehicles, meters, etc. UE 115 can communicate with the core network 130 via communication link 135.

[0082] Some UE 115 devices (such as MTC or IoT devices) can be low-cost or low-complexity devices and can provide automated communication between machines (e.g., via machine-to-machine (M2M) communication). M2M communication or MTC can involve data communication technologies that allow devices to communicate with each other or with network device 105 without human intervention. In some examples, M2M communication or MTC can include communication from a device that integrates sensors or meters to measure or capture information and relay that information to a central server capable of utilizing the information, or to present the information to humans interacting with programs or applications. Some UE 115 devices can be designed to collect information or enable automated behavior of machines. Examples of applications for MTC devices include smart meters, inventory monitoring, water level monitoring, equipment monitoring, health monitoring, wildlife monitoring, climate and geological event monitoring, fleet management and tracking, remote security sensing, physical access control, and transaction-based business charging.

[0083] Some UEs 115 can be configured to operate in power-saving modes, such as half-duplex communication (e.g., a mode that supports unidirectional communication via transmission or reception but not simultaneous transmission and reception). In some examples, half-duplex communication can be performed at a reduced peak rate. Other power-saving techniques for UEs 115 include entering a power-efficient “deep sleep” mode when not engaged in active communication, or operating on limited bandwidth (e.g., according to narrowband communication). In some cases, UEs 115 can be designed to support critical functions (e.g., mission-critical functions), and the wireless communication system 100 can be configured to provide ultra-reliable communication for these functions.

[0084] In some cases, UE 115 may also be able to communicate directly with other UE 115s (e.g., using point-to-point (P2P) or device-to-device (D2D) protocols). One or more UE 115s in a group utilizing D2D communication may be within the geographic coverage area 110 of network device 105. Other UE 115s in such a group may be outside the geographic coverage area 110 of network device 105 or may be unable to receive transmissions from network device 105 for other reasons. In some cases, a group of UE 115s communicating via D2D may utilize a one-to-many (1:M) system, where each UE 115 transmits to every other UE 115 in the group. In some cases, network device 105 facilitates the scheduling of resources for D2D communication. In other cases, D2D communication between UE 115s occurs without the involvement of network device 105.

[0085] Network devices 105 can communicate with and with the core network 130. For example, network devices 105 can be connected to the core network 130 via backhaul link 132 (e.g., via S1, N2, N3, or other interfaces). Network devices 105 can communicate with each other directly (e.g., directly between network devices 105) or indirectly (e.g., via the core network 130) on backhaul link 134 (e.g., via X2, Xn, or other interfaces).

[0086] Network device 105 may support functionality for operation within an IAB network. For example, network device 105 may be partitioned into supporting entities (e.g., functionalities) to cooperate with NR communication access to facilitate radio backhaul density. In some cases, one or more network devices 105 may be partitioned into associated base station CU and DU entities, where one or more DUs may be partially controlled by the associated CU. The CU entities of one or more network devices 105 may facilitate connectivity between the core network 130 and the access network (e.g., via cable or wireless connection to the core network). The DUs of one or more network devices 105 may control and / or schedule the functionality of additional devices (e.g., one or more alternative network devices 105, UE 115) based on configured access and backhaul link control. Based on the entities supported at one or more network devices 105, one or more network devices 105 may be referred to as donor network devices (e.g., or IAB donor, donor base station, etc.).

[0087] Furthermore, in some cases, one or more network devices 105 may be divided into associated MT and base station DU entities, wherein the MT functionality of one or more network devices 105 may be controlled and / or scheduled by the DU entities of one or more donor network devices (e.g., via the Uu interface). The DU associated with one or more network devices may be controlled by the MT functionality. Additionally, the DU of one or more network devices 105 may be partially controlled by signaling notification messages from CU entities associated with donor network devices on configured access and backhaul links connected to the network (e.g., via F1-AP). The DU of one or more network devices 105 may support one of multiple serving cell coverage areas 110 of the network coverage area. The DU of one or more network devices 105 may control and / or schedule the functionality of additional devices (e.g., one or more other network devices 105, UE 115) according to configured access and backhaul links. Based on the entities supported at one or more network devices 105, the base station may be referred to as an intermediate network device (e.g., or IAB node, intermediate base station, etc.).

[0088] At least some of the network devices (such as network device 105) may include sub-components such as access network entities, which may be examples of ANC. Each access network entity may communicate with UE 115 through several other access network transmitting entities, which may be referred to as radio headers, smart radio headers, or transmit / receive points (TRPs). In some configurations, the various functions of each access network entity or network device 105 may be distributed across various network devices (e.g., radio headers and access network controllers) or combined into a single network device (e.g., network device 105).

[0089] Wireless communication system 100 can operate using one or more frequency bands, typically in the range of 300 MHz to 300 GHz. Generally, the 300 MHz to 3 GHz range is known as the Ultra High Frequency (UHF) band or decimeter band because wavelengths range in length from approximately one decimeter to one meter. UHF waves may be blocked or redirected by buildings and environmental features. However, the wave can penetrate structures sufficiently to provide service to UE 115 located indoors for macrocells. Compared to transmissions in the high frequency (HF) or very high frequency (VHF) portion of the spectrum below 300 MHz, which use lower frequencies and longer wavelengths, UHF wave transmissions can be associated with smaller antennas and shorter ranges (e.g., less than 100 km).

[0090] The wireless communication system 100 can also operate in the ultra-high frequency (SHF) region using frequency bands from 3 GHz to 30 GHz, also known as the centimeter wave band. The SHF region includes frequency bands such as the 5 GHz industrial, scientific, and medical (ISM) band, which can be used as needed by devices capable of tolerating interference from other users.

[0091] The wireless communication system 100 can also operate in the extremely high frequency (EHF) region of the spectrum (e.g., from 30 GHz to 300 GHz), also known as the millimeter wave band. In some examples, the wireless communication system 100 can support mmW communication between the UE 115 and the network device 105, and the EHF antennas of the corresponding devices can even be smaller and more closely spaced than UHF antennas. In some cases, this can facilitate the use of antenna arrays within the UE 115. However, the propagation of EHF transmissions may suffer from even greater atmospheric attenuation and has a shorter range than SHF or UHF transmissions. The techniques disclosed herein can be used for transmissions using one or more different frequency bands, and the designated use of frequency bands in these frequency bands can vary by country or regulatory body.

[0092] In some cases, wireless communication system 100 may utilize licensed and unlicensed radio spectrum bands. For example, wireless communication system 100 may employ Licensed Assisted Access (LAA), LTE-Unlicensed (LTE-U) radio access technologies, or NR technologies in unlicensed bands such as the 5 GHz ISM band. When operating in unlicensed radio spectrum bands, wireless devices such as network device 105 and UE 115 may employ a Listen-After-Talk (LBT) procedure to ensure that the frequency channel is idle before transmission. In some cases, operation in unlicensed bands may be based on CA configuration, combined with CC operation in licensed bands (e.g., LAA). Operation in unlicensed spectrum may include downlink transmission, uplink transmission, point-to-point transmission, or a combination thereof. Duplexing in unlicensed spectrum may be based on Frequency Division Duplex (FDD), Time Division Duplex (TDD), or a combination of both.

[0093] In some examples, network device 105 or UE 115 may be equipped with multiple antennas, which can be used to employ techniques such as transmit diversity, receive diversity, multiple-input multiple-output (MIMO) communication, or beamforming. For example, wireless communication system 100 may use a transmission scheme between a transmitting device (e.g., network device 105) and a receiving device (e.g., UE 115), wherein the transmitting device is equipped with multiple antennas and the receiving device is equipped with one or more antennas. MIMO communication can employ multipath signal propagation to improve spectral efficiency by transmitting or receiving multiple signals via different spatial layers, which can be referred to as spatial multiplexing. Multiple signals can be transmitted, for example, by the transmitting device via different antennas or different combinations of antennas. Similarly, multiple signals can be received by the receiving device via different antennas or different combinations of antennas. Each of the multiple signals can be referred to as a separate spatial stream and can carry bits associated with the same data stream (e.g., the same codeword) or different data streams. Different spatial layers can be associated with different antenna ports used for channel measurement and reporting. MIMO technology includes single-user MIMO (SU-MIMO) and multi-user MIMO (MU-MIMO). In single-user MIMO (SU-MIMO), multiple spatial layers are transmitted to the same receiving device, while in multi-user MIMO (MU-MIMO), multiple spatial layers are transmitted to multiple devices.

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

[0095] In one example, network device 105 may use multiple antennas or antenna arrays to perform beamforming operations for directional communication with UE 115. For example, some signals (e.g., synchronization signals, reference signals, beam selection signals, or other control signals) may be transmitted multiple times by network device 105 in different directions, which may include transmitting signals according to different beamforming weight sets associated with the different directions of transmission. Transmissions in different beam directions may be used to identify (e.g., by network device 105 or receiving device, such as UE 115) the beam directions subsequently transmitted and / or received by network device 105. Some signals (such as data signals associated with a particular receiving device) may be transmitted by network device 105 in a single beam direction (e.g., the direction associated with a receiving device such as UE 115). In some examples, the beam direction associated with transmissions along a single beam direction may be determined at least in part based on signals transmitted in different beam directions. For example, UE 115 may receive one or more signals transmitted by network device 105 in different directions, and UE 115 may report to network device 105 an indication of the signal it received with the highest signal quality or other acceptable signal quality. While these techniques are described with reference to signals transmitted by network device 105 in one or more directions, UE 115 may employ similar techniques to transmit signals multiple times in different directions (e.g., to identify the beam direction for subsequent transmissions or receptions by UE 115), or to transmit signals in a single direction (e.g., to transmit data to a receiving device).

[0096] When receiving various signals (such as synchronization signals, reference signals, beam selection signals, or other control signals) from network device 105, the receiving device (e.g., UE 115, which may be an example of an mmW receiving device) may attempt multiple receiving beams. For example, the receiving device may attempt multiple receiving directions by: receiving via different antenna subarrays; processing the received signal according to different antenna subarrays; receiving according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements in the antenna array; or processing the received signal according to different sets of receiving beamforming weights applied to signals received at multiple antenna elements in the antenna array, any of which may be referred to as "listening" according to different receiving beams or receiving directions. In some examples, the receiving device may use a single receiving beam to receive along a single beam direction (e.g., when receiving data signals). The single receiving beam may be aligned in beam directions that are determined at least partially based on listening according to different receiving beam directions (e.g., determined at least partially based on listening according to multiple beam directions as the beam direction with the highest signal strength, highest signal-to-noise ratio, or other acceptable signal quality).

[0097] In some cases, the antennas of network device 105 or UE 115 may be located within one or more antenna arrays, which may support MIMO operation or transmit / receive beamforming. For example, one or more base station antennas or antenna arrays may co-located within an antenna assembly, such as an antenna tower. In some cases, the antennas or antenna arrays associated with network device 105 may be located in different geographical locations. Network device 105 may have an antenna array with several rows and columns of antenna ports, which network device 105 can use to support beamforming for communication with UE 115. Similarly, UE 115 may have one or more antenna arrays capable of supporting various MIMO or beamforming operations.

[0098] In some cases, the wireless communication system 100 can be a packet-based network operating according to a layered protocol stack. In the user plane, communication at the bearer or Packet Data Convergence Protocol (PDCP) layer can be IP-based. The Radio Link Control (RLC) layer can, in some cases, perform packet segmentation and reassembly for communication on logical channels. The Medium Access Control (MAC) layer can perform prioritization and multiplex logical channels into transport channels. The MAC layer can also use Hybrid Automatic Repeat Request (HARQ) to provide retransmission at the MAC layer, thereby improving link efficiency. In the control plane, the RRC protocol layer can provide the establishment, configuration, and maintenance of RRC connections between UE 115 and network device 105 or core network 130, which supports radio bearers for user plane data. In the physical (PHY) layer, transport channels can be mapped to physical channels.

[0099] In some cases, UE 115 and network device 105 can support data retransmission to increase the likelihood of successful data reception. HARQ feedback is a technique to increase the correct reception of data on communication link 125. HARQ can include a combination of error detection (e.g., using Cyclic Redundancy Check (CRC)), forward error correction (FEC), and retransmission (e.g., Automatic Repeat Request (ARQ)). HARQ can improve throughput at the MAC layer under poor radio conditions (e.g., signal-to-noise conditions). In some cases, the radio device can support same-slot HARQ feedback, where the device can provide HARQ feedback for data received in a previous symbol within a specific time slot. In other cases, the device can provide HARQ feedback in subsequent time slots or according to some other time interval.

[0100] The time interval in LTE or NR can be expressed as multiple basic time units, which can, for example, involve T. s = 1 / 30,720,000 seconds of sampling period. The time interval of communication resources can be organized according to radio frames, each with a duration of 10 milliseconds (ms), where the frame period can be expressed as T. f =307,200T s Radio frames can be identified by a System Frame Number (SFN), ranging from 0 to 1023. Each frame can contain 10 subframes numbered from 0 to 9, and each subframe can have a duration of 1 ms. A subframe can be further divided into two time slots, each with a duration of 0.5 ms, and each time slot can contain 6 or 7 modulation symbol periods (e.g., depending on the length of the cyclic prefix preceding each symbol period). In addition to the cyclic prefix, each symbol period can contain 2048 sampling periods. In some cases, a subframe can be the minimum scheduling unit of the wireless communication system 100 and can be referred to as the Transmit Time Interval (TTI). In other cases, the minimum scheduling unit of the wireless communication system 100 can be shorter than a subframe or can be dynamically selected (e.g., in a burst with a shortened TTI (sTTI), or in a selected component carrier using an sTTI).

[0101] In some wireless communication systems, time slots can also be divided into multiple micro-time slots, each containing one or more symbols. In some instances, a symbol or micro-time slot can be the smallest unit of scheduling. The duration of each symbol can vary, for example, depending on the subcarrier spacing or the operating frequency band. Additionally, some wireless communication systems can implement time slot aggregation, where multiple time slots or micro-time slots are aggregated together and used for communication between UE 115 and network device 105.

[0102] The term "carrier" refers to a set of radio spectrum resources having a defined physical layer structure to support communication over communication link 125. For example, a carrier of communication link 125 may comprise a portion of a radio spectrum band operating according to physical layer channels for a given radio access technology. Each physical layer channel may carry user data, control information, or other signaling notifications. Carriers may be associated with predetermined frequency channels (e.g., E-UTRA Absolute Radio Channel Number (EARFCN)) and can be located according to a channel raster for discovery by UE 115. Carriers may be downlink or uplink (e.g., in FDD mode), or configured to carry both downlink and uplink communication (e.g., in TDD mode). In some examples, the signal waveform transmitted on a carrier may consist of multiple subcarriers (e.g., using multi-carrier modulation (MCM) techniques such as OFDM or DFT-s-OFDM).

[0103] The organization of a carrier can vary depending on the radio access technology (e.g., LTE, LTE-A, LTE-A Pro, NR, etc.). For example, communication on a carrier can be organized according to a TTI or time slot, each of which can contain user data as well as control information or signaling notifications to support the decoding of user data. A carrier can also contain dedicated acquisition signaling notifications (e.g., synchronization signals or system information) and control signaling notifications coordinating the operation of the carrier. In some examples (e.g., in a carrier aggregation configuration), a carrier may also have acquisition signaling notifications or control signaling notifications coordinating the operation of other carriers.

[0104] Physical channels can be multiplexed on carriers using various techniques. Physical control channels and physical data channels can be multiplexed on downlink carriers, for example, using time division multiplexing (TDM), frequency division multiplexing (FDM), or hybrid TDM-FDM techniques. In some examples, control information transmitted in the physical control channel can be distributed in a cascaded manner between different control areas (e.g., between a common control area or common search space and one or more UE-specific control areas or UE-specific search spaces).

[0105] A carrier can be associated with a specific bandwidth of radio spectrum, and in some examples, the carrier bandwidth can be referred to as the “system bandwidth” of the carrier or wireless communication system 100. For example, the carrier bandwidth can be one of several predetermined bandwidths (e.g., 1.4, 3, 5, 10, 15, 20, 40, or 80 MHz) of a carrier for a particular radio access technology. In some examples, each served UE 115 can be configured to operate on a portion or all of the carrier bandwidth. In other examples, some UEs 115 can be configured to operate using a narrowband protocol type associated with a predetermined portion or range within the carrier (e.g., a set of subcarriers or RBs) (e.g., “in-band” deployment of a narrowband protocol type).

[0106] In a system employing MCM technology, a resource element can consist of a symbol period (e.g., the duration of a modulation symbol) and a subcarrier, where the symbol period and subcarrier spacing are inversely related. The number of bits carried by each resource element can depend on the modulation scheme (e.g., the order of the modulation scheme). Thus, the more resource elements UE 115 receives and the higher the order of the modulation scheme, the higher the data rate can be for UE 115. In a MIMO system, wireless communication resources can involve a combination of radio spectrum resources, temporal resources, and spatial resources (e.g., spatial layers), and using multiple spatial layers can further increase the data rate of communication with UE 115.

[0107] The apparatus of the wireless communication system 100 (e.g., network apparatus 105 or UE 115) may have a hardware configuration that supports communication on a specific carrier bandwidth, or may be configurable to support communication on one of a set of carrier bandwidths. In some examples, the wireless communication system 100 may include network apparatus 105 and / or UE 115, which may support simultaneous communication via carriers associated with more than one different carrier bandwidth.

[0108] The wireless communication system 100 can support communication with the UE 115 on multiple cells or carriers; this feature can be referred to as carrier aggregation (CA) or multi-carrier operation. The UE 115 can be configured with multiple downlink CCs and one or more uplink CCs depending on the carrier aggregation configuration. Carrier aggregation can be used in conjunction with both FDD and TDD component carriers.

[0109] In some cases, the wireless communication system 100 may utilize enhanced component carrier (eCC). The eCC may be characterized by one or more features, including a wider carrier or frequency channel bandwidth, a shorter symbol duration, a shorter TTI duration, or a modified control channel configuration. In some cases, the eCC may be associated with carrier aggregation configurations or dual connectivity configurations (e.g., when multiple serving cells have suboptimal or non-ideal backhaul links). The eCC may also be configured for unlicensed spectrum or shared spectrum (e.g., where more than one operator is permitted to use the spectrum). The wide-carrier-bandwidth eCC may comprise one or more segments that can be utilized by a UE 115 that cannot monitor the entire carrier bandwidth or is otherwise configured to use a limited carrier bandwidth (e.g., for energy conservation).

[0110] In some cases, eCC can utilize a different symbol duration than other CCs, which may involve using a shorter symbol duration compared to other CCs. The shorter symbol duration can be associated with an increased spacing between adjacent subcarriers. Devices such as UE 115 or network device 105 utilizing eCC can transmit wideband signals (e.g., according to frequency channels or carrier bandwidths of 20, 40, 60, 80 MHz, etc.) with a shortened symbol duration (e.g., 16.67 microseconds). The TTI in eCC can consist of one or more symbol periods. In some cases, the TTI duration (i.e., the number of symbol periods in the TTI) can be variable.

[0111] Wireless communication systems such as NR systems can utilize licensed, shared, and unlicensed frequency bands, as well as any other combination thereof. The flexibility in eCC symbol duration and subcarrier spacing allows for the use of eCC across multiple spectrums. In some examples, shared spectrum in NR systems can improve spectrum utilization and efficiency, particularly through dynamic vertical (e.g., across frequency domains) and horizontal (e.g., across time domains) sharing of resources.

[0112] In some wireless communication systems 100, one or more network devices 105 (e.g., donor network device 105, donor IAB node, donor base station, etc.) may include CUs and DUs, wherein one or more DUs associated with a donor network device may be partially controlled by a CU associated with the donor network device. The network device CU may be a component of a network management function, database, data center, or core network 130 (e.g., a 5G NR core network (5GC)). In some cases, the network device CU may communicate with a network management function (e.g., in some cases, the network management function may involve a separate entity communicating with the network device CU). In some cases, the network management function may be referred to as a management function. The network device CU may communicate with the donor network device 105 via a backhaul link 132 (e.g., cable backhaul or wireless backhaul). As another example, in an IAB network, the network device CU (e.g., donor network device 105) may communicate with the core network 130 (e.g., NGC) via a backhaul link 132 (e.g., cable backhaul or wireless backhaul). The donor network device 105 may be referred to as an IAB donor, for example, in an IAB network, and may communicate with one or more IAB nodes (e.g., other network devices 105) that operate as network devices DU relative to the IAB donor and one or more UEs.

[0113] For example, an IAB network may comprise a chain of radio devices (e.g., starting at donor network device 105 (terminating at a radio access network (RAN) node connected to the core network) and ending at UE 115, with any number of IAB nodes or relay network devices in between). IAB nodes (e.g., relay network devices, relay nodes, relay base stations, etc.) may support MT functionality (which may also be referred to as UE functionality (UEF)) controlled and scheduled by the IAB donor or another parent IAB node. IAB nodes (e.g., relay base stations, relay nodes, etc.) may also support DU functionality (which may also be referred to as Active Access Network Functionality (ANF)) relative to additional entities (e.g., IAB nodes, UEs, etc.) within the relay chain or configuration (e.g., downstream) of the access network. In some cases, MT functionality may involve implementations that support at least some aspects of the MT or UE (e.g., as defined in 3GPP TS23.101 Release 8.0.0). These relay mechanisms can forward traffic to additional entities, extend the range of radio access for one or more base stations, and increase the density of backhaul capabilities within the serving cell, among other things.

[0114] Wireless communication system 100 may employ one or more wired and wireless backhaul links (e.g., backhaul link 132 or backhaul link 134) to establish connectivity between a core network (e.g., core network 130) and one or more wireless nodes within wireless communication system 100. For example, wireless communication system 100 may include multiple network devices 105 (e.g., base stations, remote radio telegraph heads, etc.), with at least one network device 105 coupled to a cable backhaul link, such as a fiber optic cable. Additional network devices 105 may be directly coupled to core network 130 or another network device 105 without a wired backhaul link and may use a wireless backhaul link to communicate backhaul traffic. In such a case, network device 105 can wirelessly communicate backhaul access traffic to a high-capacity fiber optic point (e.g., a location where a wireless node is coupled to a cable link leading to core network 130). Each of backhaul links 132 and 134 may carry packets from one or more established PDN gateways via an SGi interface and subsequently route the packets through the core network and onto the coupled wireless node via an S1 interface.

[0115] While mobile access can sometimes be associated with a single-hop communication link between source and destination (e.g., an asymmetric link), wireless backhaul communication can support multi-hop transmission and provide robustness through topological redundancy (e.g., alternative paths for data exchange within a wireless communication network). Accordingly, the underlying links using wireless backhaul communication can be symmetric in nature and utilize large-scale resource coordination between wireless communication links.

[0116] The relay node multi-connection backhaul manager 101 can transmit measurement reports to the network management function via a first backhaul link to the first parent node using the relay node's first mobile terminal function. These measurement reports include measurements transmitted by the second parent node (e.g., a parent node reference signal transmission). Additionally, the relay node multi-connection backhaul manager 101 can receive a backhaul link configuration for a second mobile terminal function via the first backhaul link based on the transmitted measurement reports, and establish a second backhaul link between the relay node's second mobile terminal function and the second parent node based on the received backhaul link configuration. Generally, the relay node multi-connection backhaul manager 101 can be a component, function, or logic device of network device 105 (e.g., network device 105-a, network device 105-b, network device 105-c, etc.).

[0117] The Management Functions Multi-Connection Backhaul Manager 102 can receive measurement reports from a first mobile terminal function at a relay node via a first backhaul link, where the measurement reports include measurements transmitted by a second parent node, and identify the backhaul link configuration of the second mobile terminal function based on the received measurement reports. Additionally, the Management Functions Multi-Connection Backhaul Manager 102 can transmit the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function at the relay node via the first backhaul link. Overall, the Management Functions Multi-Connection Backhaul Manager 102 can be a component, function, or logical device of the core network 130.

[0118] The relay node multi-connection backhaul manager 101 can also use the relay node's first mobile terminal function to exchange the relay node's identifier with the first network management function via a first backhaul link to the first parent node, and use the relay node's second mobile terminal function to transmit the relay node's identifier to the second network management function via a second backhaul link to the second parent node. Furthermore, the relay node multi-connection backhaul manager 101 can receive the backhaul link configuration of the second mobile terminal function based on transmitting the relay node's identifier to the first network management function via the first backhaul link and transmitting the relay node's identifier to the second network management function via the second backhaul link.

[0119] The management function multi-connection backhaul manager 102 can also identify relay nodes connected to a first parent node via the relay node's first mobile terminal function, identify relay nodes connected to a second parent node via the relay node's second mobile terminal function, and transmit backhaul link configurations for the second mobile terminal function based on the identified relay node connections.

[0120] Figure 2 An example of a wireless communication system 200 supporting aspects of a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is illustrated. In some examples, the wireless communication system 200 may implement aspects of the wireless communication system 100. The wireless communication system 200 may support one or more base stations 105 (e.g., which may be as follows). Figure 1 (Example of network device 105 described herein), base station 105 supports network access to one or more UEs 115 within the cell coverage area 110 (e.g., it may be as follows). Figure 1 Examples of UE 115 and coverage area 110 described herein. In some cases, one or more cell coverage areas 110 may be non-co-located. The NR access infrastructure and spectrum resources within the wireless communication system 200 may additionally support the wireless backhaul link 215 capability as a supplement to the cable backhaul connection 210 to provide an IAB network architecture.

[0121] In some cases, base station 105-a can be divided into associated base station CU and DU entities, where one or more DUs can be partially controlled by the associated CU. The CU entity of base station 105-a can facilitate connectivity between core network 205 and access network (e.g., via cable backhaul link 210 or wireless connection to the core network). The DU of base station 105-a can control and / or schedule the functionality of additional devices (e.g., relay base stations, such as relay base station 105-b) based on configured wireless backhaul link 215 and access link 220. Based on the entities supported by base station 105-a, base station 105-a can be referred to as an IAB donor. Relay base station 105-b can support link connectivity with the IAB donor (e.g., base station 105-a) as part of a relay chain within the IAB network architecture. For example, base station 105-b can be divided into associated MT and DU entities, wherein the MT functionality of base station 105-b can be controlled and / or scheduled by the DU entity of base station 105-a (e.g., an IAB donor). The DU associated with base station 105-b can be controlled by the MT functionality. Furthermore, in some cases, the DU of base station 105-b can be partially controlled by signaling notification messages from CU entities associated with the network-connected IAB donor node (e.g., via F1-AP). The DU of base station 105-b can support a serving cell coverage area of ​​110 for the IAB network coverage area. Based on the entities supported by base station 105-b, base station 105-b can be referred to as a relay base station, IAB node, relay node, etc.

[0122] Furthermore, the wireless communication system 100 may employ one or more radio access links 220 to establish mobile access to one or more coupled UEs 115. Each of the base station 105 and UE 115 may be configured to support a cellular RAT (such as a mmW-based RAT) to access traffic between the UE 115 and the base station 105. Additionally, each of the base stations 105 may share the resources of its configured RAT to access traffic on the network with backhaul traffic (e.g., as in the case of IAB). Due to the enhanced radio link capacity, IAB network solutions can become increasingly advantageous as cellular technologies evolve. Specifically, IAB network solutions can provide solutions for the densification of network cells (i.e., cost reduction in small cell deployment) and increase data traffic as a means of maximizing spectral efficiency by jointly optimizing and integrating access and backhaul resources within the network. Due to the large bandwidth per channel and the need to mitigate short-term signal blockage, IAB network solutions can be particularly suitable for mmW RATs.

[0123] Access links using mmW-based RATs can be designed as asymmetric single-hop links, which can be used to allocate control and scheduling tasks to base station 105 while providing instructions to one or more UEs 115 to schedule communication. In such a case, base station 105 can coordinate radio resources among multiple UEs 115, with each UE 115 being assigned to one base station 105 at a time. In some cases, inter-node links can be inherently symmetric and can form a mesh topology to enhance robustness, where radio transmissions can occur along multiple hops.

[0124] Communication on the IAB network based on a specific RAT (e.g., mmW RAT) can enable one or more functionalities at base station 105 in the network. For example, each base station 105 can be configured for both ANF and UEF to allow each base station 105 to act as a scheduling entity and a receiving (e.g., scheduled) entity. Each of these functionalities can operate via each of one or more backhaul links 215. The ANF can enable the corresponding base station 105 to operate as a scheduling entity on one or more access links 220 and communicate with one or more UEs 115 located within the IAB network. The ANF can also enable the corresponding base station 105 to operate as a scheduling entity on one or more coupled backhaul links 215 to facilitate communication between one or more other base stations 105 in the IAB network (i.e., via a mesh topology). The UEF functionality can enable the corresponding base station 105 to operate as a scheduled entity and communicate with one or more other base stations 105 to receive data. The combination of UEF and ANF capabilities at each base station 105 in the IAB network allows each of the base stations 105 to utilize switching operations on the radio spectrum associated with the RAT to transmit access traffic to / from the UE 115 and backhaul traffic to / from the core network 130, providing coupled access to one or more PDNs. Furthermore, each of the base stations 105 may contain a routing table to examine received data packets and forward them along the optimal path within the IAB network toward the designated IP address of the packet's destination.

[0125] Wireless communication system 200 can illustrate examples of compact small cell systems with integrated access and backhaul links (e.g., allowing self-backhaul for access traffic). Integrated access and backhaul links (e.g., integrated wireless backhaul link 215) can allow such compact small cell systems without requiring each cell (e.g., each base station 105) to be connected to a fiber optic point or cable backhaul connection 210. Wireless communication system 200 can thus illustrate multi-hop wireless backhaul networks (e.g., with self-backhaul). Such compact small cell systems can provide sub-6 frequencies, which can, for example, provide massive MIMO techniques to improve spectral efficiency. In some cases, each relay base station 105 can be associated with a single MT function, and thus backhaul relay as shown can be employed. In some cases, relay base station 105 can support multiple MT functions, in which case relay base station 105 can be able to connect multiple cellular backhauls (e.g., as exemplified herein). Figure 3 (As described).

[0126] Figure 3 An example of a wireless communication system 300 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is illustrated. In some examples, the wireless communication system 300 may implement aspects of wireless communication system 100 and wireless communication system 200, as referenced... Figure 1 and Figure 2 As described. For example, Figure 3 The illustration depicts a wireless communication system 300 (e.g., an NR system) that supports shared infrastructure and spectrum resources for NR access with wireless backhaul link capabilities, complementing cable backhaul connections, to provide an IAB network architecture. The wireless communication system 300 may include a core network 305 (e.g., an NGC), and base stations or supporting devices divided into one or more supporting entities (e.g., functionalities) to cooperate with NR communication access to facilitate wireless backhaul density. The supporting functional aspects of the base stations may be referred to as IAB nodes.

[0127] The wireless communication system 300 may include an IAB donor node divided into associated base station CU 310 and DU 315 entities, wherein the DU 315 associated with the IAB donor node may be partially controlled by the associated CU 310. The CU 310 of the IAB donor node may host Layer 3 (L3) functionalities and signaling notifications (e.g., RRC, Serving Data Adaptation Protocol (SDAP), PDCP, etc.). Other CU 310s of the IAB donor node may communicate with the core network 305 on, for example, an NG interface (which may be part of a backhaul link). The DU 315 may host lower layers, such as Layer 1 (L1) and Layer 2 (L2) functionalities and signaling notifications (e.g., RLC, MAC, PHY, etc.). The DU 315 entity of the IAB donor node may support one of multiple serving cells covered by the network, depending on the connection associated with the backhaul and the access link of the IAB network. The IAB donor node DU 315 can control both the access link and the backhaul link within the corresponding network coverage area, and can provide control and scheduling of descendant (e.g., child) relay IAB nodes 320 and / or UE 115.

[0128] The relay IAB node 320 can be divided into associated MT and DU entities. The MT functionality (e.g., UEF) of the relay IAB node 320 can be controlled and / or scheduled by a connected predecessor IAB node (e.g., by an IAB donor node or another IAB node acting as its parent node) established via access and backhaul links across the coverage area. The DU associated with the relay IAB node 320 can be controlled by the node's MT functionality. Furthermore, the DU of the IAB node 320 can be partially controlled by signaling notification messages from the CU 310 entity of the associated IAB donor node in the network connection (e.g., via F1-AP). The DU of the IAB node 320 can support one of multiple serving cells within the network coverage area. The DU functionality (e.g., ANF) can schedule child IAB nodes and UEs and can control both access and backhaul links under its coverage.

[0129] Each relay node may contain at least one MT function and one DU. The relay can connect to a parent relay node or donor node via each MT function, and can also support connections to UE 115 and child relay nodes via DUs. In some cases, all DUs on the relay node and donor node may connect to a centralized donor CU (e.g., CU 310) that maintains network management functions, or connect to the network management functions. The network management functions can support link management, routing management, topology management, resource management, etc., of the wireless communication system 300 (e.g., IAB network). Connections between DUs on the wireless backhaul link can use a modified form of the F1 protocol (e.g., F1*). Each relay node MT function may include an RRC connection to CU 310. Additionally, each relay node DU may include an F1* control plane connection to CU 310. In this way, the network management functions can support link configuration, routing configuration, and resource configuration tasks for the wireless backhaul topology.

[0130] The wireless communication system 300 can employ relay links for communication within the IAB network architecture. For example, an IAB donor can support a primary backhaul link to relay IAB node 320 and one or more secondary (e.g., parallel or backup) backhaul links. The IAB donor can also support one or more access links to additional devices (e.g., UE 115) or entities in the network. Furthermore, the MT functionality of each of one or more relay IAB nodes 320 and UE 115 can be configured to support network connectivity to multiple parent nodes via access and backhaul links associated with the coverage area of ​​the IAB network.

[0131] To enable relay IAB nodes to support multiple paths to CU 310, the relay IAB nodes can maintain multiple MT functions (e.g., multiple MTs). For example, relay IAB node 320-a can support a single MT function (e.g., and can have a single path or backhaul link to CU 310), relay IAB node 320-b can support two MT functions (e.g., and can have two paths or two backhaul links to CU 310), and relay IAB node 320-d can support three MT functions (e.g., and can have three paths or three backhaul links to CU 310). When relay IAB node 320 supports multiple MT functions, each MT function can support connectivity to different parent nodes. For example, for IAB relay node 320-b, a first MT function can establish a first backhaul link through a first parent node (e.g., DU 315-a), and a second MT function can establish a second backhaul link through a second parent node (e.g., DU 315-b). As another example, for IAB relay node 320-d, the first MT function can establish a first backhaul link through the first parent node (e.g., IAB node 320-a), the second MT function can establish a second backhaul link through the second parent node (e.g., DU 315-a), and the third MT function can establish a third backhaul link through the third parent node (e.g., IAB node 320-c, and ultimately through DU 315-a or DU 315-b after being relayed by IAB node 320-c).

[0132] In this way, IAB nodes supporting multi-MT functionality can support topological redundancy paths in the wireless communication system 300. In some cases (e.g., associated with CU 310), network management functions can be configured (e.g., for relay IAB nodes 320-b) to use multiple paths (e.g., multiple backhaul links) in parallel or simultaneously. As discussed herein, the use of parallel or simultaneous backhaul links can involve the operation of backhaul links combined with each other (e.g., whether to use each link for redundant communication of backhaul information, use each link for load balancing of backhaul information, etc.). Thus, parallel backhaul link operation can involve backhaul links being active and available for backhaul, and may not necessarily imply that two backhaul links must convey the same information at the same time. In other cases (e.g., associated with CU 310), network management functions can be configured to use alternative paths (e.g., alternative backhaul links) in the event of degradation of an established backhaul link or in the event of an improved backhaul link identified by the IAB relay node or network management functions. For example, relay IAB node 320-c can communicate via backhaul through DU315-b, but can be configured (e.g., by network management functions) with a backup backhaul link via DU 315-a. For example, network management functions can configure the relay node's multi-MT capability to connect to different parent nodes, thereby simultaneously using all links (e.g., backhaul links) that the relay node has with its multiple parents, or network management functions can configure the relay node to use only a subset of links and maintain other links for backup purposes (e.g., shown as dashed lines).

[0133] Multipath connectivity via such multi-backhaul links provides robustness against radio link failures on backhaul links (e.g., on degraded backhaul links). Additionally, capacity optimization through load balancing across multiple backhaul paths is possible (e.g., increasing backhaul throughput, reducing latency associated with backhauls on individual backhaul links, etc.). For network management functions to coordinate and configure multi-backhaul links (e.g., to support relay nodes with multi-MT functionality), the management functions can first become aware that the relay node supports such multi-MT functionality (e.g., and therefore enables multi-connection cellular backhauls).

[0134] Multiple MT functions residing on a single relay node can have different characteristics (e.g., different MT functions on the relay node can cover different angular sectors, support different frequency bands, have different power levels, etc.). Furthermore, MT functions and DU functions residing on the same relay node can have relationships with each other (e.g., MTs and DUs can share the same antenna panel). Additionally, multiple MTs with different antenna panels can have limited antenna isolation, which may affect resource allocation for simultaneous (e.g., parallel) operation. To fully utilize the advantages of a large number of MTs co-located on a relay (e.g., to maximize backhaul efficiency in the wireless communication system 300), network management functions can be aware of these aspects and can have means to configure the use of multiple MTs accordingly.

[0135] The first MT function of a relay IAB node (e.g., relay IAB node 320-d) can establish a backhaul link with a first parent (e.g., IAB node 320-a) and transmit a list of MT-identifiers of supported MTs (e.g., identifiers of the supported MT(multiple)) to a network management function (e.g., via the first backhaul link to IAB node 320-a). In this way, each MT function can be addressed individually by the network management function. In some cases, relay IAB node 320-d can provide further details about the capabilities of each MT, relationships between MTs, etc. In some examples, for a second MT function of IAB node 320-d, the network management function can transmit a measurement configuration to the first MT of IAB node 320-d via the first backhaul link. For example, the measurement configuration may include an identifier of the second MT function, one or more parent nodes to be measured by the second MT function, the measurements to be received (e.g., RSSI, RSRP, etc.), etc. The second MT function of IAB node 320-d can perform measurements (e.g., measurements of the indicated parent(s) or all detected parent(s)), and IAB node 320-d can transmit measurement reports (e.g., containing measurements received by the second MT function of IAB node 320-d) to the network management function (e.g., via the first backhaul link to IAB node 320-a). That is, the MT functions of the IAB nodes can communicate with each other (e.g., the first MT function of IAB node 320-d can pass measurement configurations to the second MT function of IAB node 320-d, and the second MT function of IAB node 320-d can transmit measurement results or measurement reports back to the first MT function of IAB node 320-d (e.g., for the first MT function to transmit to the network management function).

[0136] The network management function can then select a second parent node (e.g., for a second backhaul link with the second MT functionality of IAB node 320-d) based on the received measurement reports. The network management function can then transmit the configuration of the second link to the second MT of IAB node 320-d on the first backhaul link (e.g., via the first MT of IAB node 320-d). The second MT of IAB node 320-d can then establish a second backhaul link (e.g., via IAB node 320-c to the network management function) based on the received backhaul link configuration.

[0137] In other examples, the MT function of an IAB node can autonomously establish links with parent nodes (e.g., based on IAB node settings, without requiring configuration from the parent node or network management functions). In such a case, the first MT function of a relay IAB node (e.g., relay IAB node 320-d) can establish a first backhaul link with a first parent (e.g., IAB node 320-a) and can (e.g., via the first backhaul link) establish a relay identifier (e.g., the identifier of relay IAB node 320-d) with the network management function. The second MT function of relay IAB node 320-d can perform signal strength measurements of other parent nodes (e.g., DU 315-a, IAB node 320-b, IAB node 320-c, etc.) and select a second parent node (e.g., IAB node 320-c) based on a parent selection strategy (e.g., the criteria for parent selection of IAB node 320-a, such as the strongest detected parent node, a parent node with signal strength above a threshold, etc.). IAB node 320-d can then connect to the second parent node, IAB node 320-c, and transmit the relay identifier to the network management function via the second backhaul link to IAB node 320-c. Here, the network management function can associate the second MT function with the same relay node as the first MT function (e.g., by comparing the relay identifiers received on each backhaul link, identifying two relay identifiers associated with a single relay node, etc.). The network management function can then transmit the configuration of the second link from the second MT function (e.g., via the first backhaul link to the first MT function) to the second parent (IAB node 320-c). The second MT function can establish the second link and use it for backhaul (e.g., according to the backhaul link configuration).

[0138] The following section discusses additional details regarding the options for handling the awareness and coordination configuration of the aforementioned multi-MT relay nodes. For example, in one scenario, management functions could have explicit awareness and control over multi-MT operations (e.g., as referenced below). Figure 4 and Figure 5(More detailed description). In another scenario, relay nodes can autonomously establish multi-MT connectivity based on a pre-configured parent selection strategy (as referenced below). Figure 6 and Figure 7 (For a more detailed description). In either case, network management functions can configure backhaul routes (e.g., backhaul links) and resource configurations on redundant topologies.

[0139] In either scenario (e.g., whether the management function has explicit awareness and control over multi-MT operation, or the relay node autonomously establishes multi-MT connectivity), signaling notification messages between the relay node's MT function and the network management function (e.g., MT capability reports transmitted by the relay node, measurement configurations transmitted by the network management function, measurement reports transmitted by the relay node, backhaul link configurations transmitted by the network management function, etc.) may use RRC signaling notification in some cases. In some cases, signaling notification messages between the relay node's MT function and the network management function may use the F1 protocol or a Non-Access Stratum (NAS) protocol. In some examples, the link may use a cellular RAT (e.g., such as NR or LTE). In some examples, the relay node may also maintain a complete base station (e.g., a complete gNB) rather than just a DU (e.g., a gNB-DU). The relay node may also maintain an eNB or an eNB's DU, which may be connected to the eNB's CU via multi-hop radio backhaul. In some cases, the radio link between the relay node and the parent node may include an RLC channel. RLC channels can include an adaptation layer, which can be used for purposes such as routing.

[0140] In some examples, arbitrary communication between the network management function and the second MT of the relay node via the first MT of the relay node can occur via a container (e.g., a field) inserted into a message between the network management function and the first MT. In some cases, communication between the network management function and the second MT of the relay node via the first MT (e.g., a container) can include an identifier of the second MT. In some cases, routing configuration, routing usage, link usage, and resource allocation among multiple upstream links supported by the relay node can be determined and configured by the network management function. The network management function can be part of a gNB, gNB-CU, eNB, eNB-CU, or core network (e.g., such as EPC or NGC). In some cases, the network management function can coexist with these nodes or functions. In some cases, the network management function can have an interface to these nodes or functions. In some cases, the interface to these nodes or functions can be transparent to the MT communicating with the network management function.

[0141] Figure 4An example flowchart 400 supporting a relay node with multi-connectivity cellular backhaul according to one or more aspects of this disclosure is illustrated. In some examples, flowchart 400 may implement aspects of wireless communication system 100, wireless communication system 200, and / or wireless communication system 300. For example, flowchart 400 may illustrate network management functions and the operation of relay nodes (e.g., intermediate IAB nodes), as referenced... Figures 1 to 3 As described. Specifically, flowchart 400 can illustrate network management functions with explicit awareness and control over multiple MT operations. As discussed, the mechanisms for performing one or more processes of the described techniques can be performed by the network management functions and the first MT function or first MT entity (e.g., UEF) and second MT function or second MT entity of the relay node. However, the described techniques can be extended by analogy to additional MT functions supported by the relay node without departing from the scope of this disclosure.

[0142] In section 405, a relay node can use the first MT function to select a first parent node (e.g., parent relay node, donor node's DU, etc.) based on a parent selection policy. For example, the parent selection policy can be identified in the system information or pre-configured on the relay node. In some cases, a relay node can connect to the network once to retrieve the parent selection policy from Operation, Administration, and Maintenance (OAM) functions or other sources.

[0143] In 410, the first MT function of the relay node can establish the first link to the selected parent node (e.g., the first return link).

[0144] In section 415, the first MT function can send signaling notification messages to the network management function. The message may contain a relay identifier (e.g., an identifier of the relay node) and a list of MT-identifiers (e.g., identifiers of one or more supported MT functions) of the MTs supported by the relay node. In this way, each MT can be addressed individually by the management function. Alternatively, the first MT may send the relay identifier and the number of supported MTs. In this case, the relay identifier along with the MT index allows the network management function to still uniquely identify the MT (e.g., using a combination of the relay identifier and the MT index). In some cases, the relay identifier may be assigned by the network (e.g., by the network management function), and the MT may specify the number of supported MTs.

[0145] The first MT can provide details about the capabilities of each MT (e.g., RAT, frequency band, power level, angular coverage in the azimuth and elevation directions, number of supported antenna panels, etc.). For example, the first MT can transmit a capability report (e.g., containing the capabilities of each supported MT) to the network management function via the first backhaul link. This allows the network management function to process and understand the limitations of the relay node for multi-MT operation. In some cases, the first MT can also provide limitations about the relationships between MTs (e.g., antenna isolation between MTs, overlapping azimuth or elevation ranges, etc.). In some cases, the first MT can also provide information about the number of DUs supported by the relay, and can provide relationships between MTs and DUs (e.g., if MTs and DUs share antenna panels), etc. The first MT can provide some or all of this information, for example, via the RRC to the network management function.

[0146] In 420, the relay node can use the first radio link for backhaul access or backhaul traffic of the co-located DU.

[0147] In section 425, the network management function can decide to activate additional MT functions (e.g., a second MT function) of the relay node and can select the parent of the second MT function. The network management function can communicate this to the relay node by transmitting a measurement configuration message to the first MT, which can define the measurement events to be reported by the second MT (e.g., via the first MT of the relay node to the network management function). The measurement configuration message can explicitly specify the measurement configuration for a particular MT (e.g., by including an MT identifier or MT index in the configuration). Alternatively, the configuration can be implicitly applied to all or a subset of the MTs supported by the relay node. In some cases, a subset of MTs can also be specified in the configuration message.

[0148] At 430, the second MT can perform measurements based on a measurement configuration and upon event triggering. The first MT can report the measurements (e.g., performed by the second MT) to a management function (e.g., to the gNB-CU) while indicating that the second MT has performed the measurement. In some cases, the measurement configuration can be transmitted via RRC.

[0149] In section 435, the network management function can (e.g., based on measurement reports) decide to activate the second MT and can select a second parent relay for the second MT under the control of the network management function. The network management function can use the configuration of the second MT to transmit signaling notification messages (e.g., backhaul link configuration messages) to the first MT. The configuration of the second MT may include the identifier of the second MT, as well as other link and routing configuration information for the second MT. In some cases, the configuration can use RRC (e.g., backhaul link configuration can be transmitted in an RRC reconfiguration message).

[0150] At 440, the second MT can establish a link as specified in the backhaul link configuration message. In some cases, the second MT can authenticate at the network as part of the link establishment. The second MT can also report its capabilities in the same or similar manner as the first MT reports its capabilities.

[0151] In 445, based on the backhaul link configuration, the relay node can then use a second radio link for access to or backhaul traffic of the co-located DU, or it can also use both radio links simultaneously for access to or backhaul traffic of the co-located DU. The backhaul link configuration can also specify that the relay node uses the first link for a subset of the co-located DUs and the other link for another subset of the co-located DUs.

[0152] Figure 5 An example 500 of a processing flow supporting a relay node with multi-connectivity cellular backhaul according to one or more aspects of this disclosure is illustrated. In some examples, processing flow 500 may implement aspects of wireless communication system 100, wireless communication system 200, and / or wireless communication system 300. For example, processing flow 500 may include relay node 505, parent node 510-a, parent node 510-b, and CU 310-a, which may be a corresponding functional example of an IAB network architecture (e.g., such as network device 105 or base station 105, relay node 320, DU 315, CU 310), as referenced. Figures 1 to 4 As described above. Processing flow 500 may illustrate network management functions that become aware of multi-MT support for relay nodes (e.g., relay node 505) and control of multi-MT operations (e.g., operations of MT 515-a and MT 515-d) by the network management functions. In the following description of processing flow 500, operations between relay node 505, parent node 510, and network management functions (e.g., CU 310-a, or some network management functions or network management function entities communicating with CU 310-a) may be transmitted in a different order than the exemplary order shown, or operations performed by relay node 505, parent node 510-a, parent node 510-b, and network management functions may be performed in a different order or at different times. In some cases, certain operations may also be excluded from processing flow 500, or other operations may be added to processing flow 500.

[0153] Processing flow 500 may illustrate a relay node 505 communicating with a network management function via a first wireless backhaul link between a first MT function (e.g., MT 515-a) and a first parent or control node (e.g., parent node 510-a). Processing flow 500 also illustrates a network management function configuration (e.g., using the multi-MT functionality of relay node 505) between a second MT function (e.g., MT 515-d) and a second parent or control node (e.g., parent node 510-b) and a second wireless backhaul link. That is, parent node 510-a and parent node 510-b may each involve a parent relay node (e.g., which may contain both MT functionality and DU 520) or a donor node (e.g., which may contain DU 520 and may be directly connected to CU 310-a, or in some cases may contain CU 310-a). In cases where parent node 510-a and / or parent node 510-b involve a parent relay node, the parent relay node may include MT functionality, which may also relay to or act as an intermediate point in the link to the donor node. That is, parent node 510-a and parent node 510-b may each involve a parent node of relay node 505, and may involve a parent relay node or a donor node, as described herein, and may each provide a link from relay node 505 to network management functions (e.g., CU 310-a).

[0154] The DU 520-a associated with relay node 505 may be partially controlled and / or scheduled by MT 515-a and / or MT 515-d. DU 520-a may host lower layers such as L1 and L2 (e.g., RLC, MAC, PHY, etc.), functionality, and signaling notifications. Relay node 505 may be a descendant (e.g., child) node relative to parent nodes 510-a and 510-b along two different paths within the relay chain. Additionally, relay node 505 may include MT 515-a, which may be controlled and / or scheduled by DU 520-b of parent node 510-a via access and backhaul links of the IAB network, and may also include MT 515-d, which may be controlled and / or scheduled by DU 520-c of parent node 510-b via access and backhaul links of the IAB network. Furthermore, in some cases (e.g., when both parent nodes 510-a and 510-b are parent relay nodes), DU 520-b and DU 520-c may be partially controlled and / or scheduled by CU 310-a signaling notification messages from the IAB donor (e.g., via F1-AP). Parent node 510-a may support one or more radio backhaul and / or access links within the relay chain, providing network services to one or more descendant devices (e.g., such as relay node 505) distributed throughout the network. Parent node 510-b may support one or more radio backhaul and / or access links within the relay chain, providing network services to one or more descendant devices (e.g., such as relay node 505) distributed throughout the network.

[0155] At 505, relay node 505 can establish a first backhaul link (BL) between a first MT function (e.g., MT 515-a) and a first parent node (e.g., parent node 510-a). In some cases, the first backhaul link can be established based on relay node 505, which uses MT 515-a to measure one or more parent nodes and selects parent node 510-a based on a parent selection policy. The first backhaul link can connect relay node 505 (e.g., specifically, MT 515-a) to a network management function (e.g., CU 310-a) via parent node 510-a. As described above, in some cases, parent node 510-a can be a parent relay node or a DU associated with a donor node. That is, parent node 510-a can generally relate to the first node or CU 310-a, which communicates with relay node 505 under the control of the management control function.

[0156] At 510, relay node 505 can transmit a capability report to the network management function via the first backhaul link using MT 515-a. The capability report may include the relay node's capabilities in terms of MT functionality (e.g., the number of supported MT functions, identifiers of the supported MTs, isolation between different MT functions, etc.) and the capabilities of individual MT functions (e.g., RATs supported by the second MT function, frequency bands supported by the second MT function, azimuth and elevation modes supported by the second MT function, etc.). For example, the capability report may include the identifier of MT 515-d, one or more RATs supported by MT 515-d, one or more frequency bands supported by MT 515-d, azimuth and elevation modes supported by MT 515-d, RF capabilities of MT 515-d, isolation between MT 515-a and MT 515-d, the relay node's identifier 505, a list of supported MT functions (e.g., identifiers of MT 515-a, MT 515-d, and any other MTs supported by relay node 505), etc.

[0157] In section 515, the network management function can identify the measurement configuration of MT 515-d based on the received capability report. For example, the network management function can consider the capabilities of relay node 505 (e.g., and MT 515-d) and can identify the parent node (e.g., parent node 510-b) that MT 515-d will measure. Generally, the measurement configuration can include identifiers of the MT functions to be measured, identifiers of the parent nodes to be measured, and identifiers of the measurements to be performed (e.g., RSSI measurement, RSRP measurement, etc.). For example, if relay node 505 indicates several MT functions (e.g., more than two MT functions) in the capability report, the measurement configuration can identify the parent nodes to be measured and the measurements to be received by more than one MT. The measurement configuration can indicate (e.g., via MT identifiers, which may already be included in the capability report) which MT functions will be measured, which measurements will be performed, and which parent nodes each MT function should measure, etc.

[0158] In the 520, network management functions can transmit the identified measurement configuration to the MT 515-a via the first backhaul link.

[0159] At 525, the relay node can use MT 515-d to perform one or more measurements of parent node 510-b based on the measurement report received at 520. For example, MT 515-a can receive the measurement configuration and can pass the measurement configuration to MT515-d (e.g., because MT 515-a and MT 515-d can be connected and communicate within relay node 505). Relay node 505 can thus use MT 515-d to perform measurements of parent node 510-b based at least in part on the measurement configuration.

[0160] At 530, the relay node can transmit a measurement report containing measurement information received by MT 515-d to the network management function via a first return link to parent node 510-a. For example, MT 515-d can perform measurements and pass measurement report information to MT 515-a (e.g., because MT 515-d and MT 515-a can be connected and communicate within relay node 505), and MT 515-a can transmit the measurement report to parent node 510-a.

[0161] At 535, the network management function can identify the backhaul link configuration (e.g., via MT 515-d for relay node 505) at least in part based on the measurement report received at 530. For example, the network management function can identify which parent node(s) the additional MT of the relay node should be connected to, whether the additional backhaul link will operate in parallel with the first backhaul link or as a backup for the first backhaul link, etc. In some cases, the network management function can determine second backhaul link routing utilization information, second backhaul link utilization information, second backhaul link resource allocation information, etc., based on the received measurement report.

[0162] At 540, network management functions can transmit the backhaul link configuration of the identified MT 515-d to MT 515-a via the first backhaul link (e.g., via parent node 510-a). In some cases, the backhaul link configuration may include information about the establishment and operation of the second backhaul link (e.g., the identifier of the second parent node to which to connect, routing utilization information, link utilization information, resource allocation information, etc.).

[0163] At 545, the network management function may optionally transmit routing configurations that indicate how the first and second backhaul links should be used (e.g., in parallel, as primary and backup backhaul links, etc.). In some cases, routing configuration information may be included in the backhaul link configuration transmitted at 540 (e.g., in some cases, information from 545 may be included in 540 and not transmitted as separate messages).

[0164] At 550, MT 515-d can establish a second backhaul link between the second MT function (e.g., MT 515-d) and the second parent node (e.g., parent node 510-b). The second backhaul link can connect the relay node 505 (e.g., specifically MT 515-d) to the network management function (e.g., CU 310-a) via the parent node 510-b. As described above, in some cases, the parent node 510-b can be a parent relay node or a DU associated with a donor node. That is, the parent node 510-b can generally relate to the first node or CU 310-a, which communicates with the relay node 505 under the control of the management control function.

[0165] In this way, relay node 505 can operate in a multi-connection cellular backhaul state (e.g., using multi-backhaul connections to network management functions). Network management functions can coordinate the multi-backhaul links associated with relay node 505. For example, the routing configuration (e.g., 545) can update or reconfigure the first and / or second backhaul links, so that the use of one or both of the first and second backhaul links can be dynamically adjusted by the network management functions (e.g., based on conditions for backhaul link changes, backhaul traffic volume, or priority changes, etc.).

[0166] Figure 6 An example flowchart 600 supporting a relay node with multi-connectivity cellular backhaul according to one or more aspects of this disclosure is illustrated. In some examples, flowchart 600 may implement aspects of wireless communication system 100, wireless communication system 200, and / or wireless communication system 300. For example, flowchart 600 may illustrate network management functions and the operation of relay nodes (e.g., intermediate IAB nodes), as referenced... Figures 1 to 3 As described. Specifically, flowchart 600 may illustrate the autonomous establishment of multi-MT connectivity based on a pre-configured parent selection strategy, and the backhaul configuration coordinated by network management functions (e.g., in cases where multi-MT functions associated with the same relay node autonomously connect to the same network management function on two or more backhaul links). As described, the mechanisms for performing one or more processes of the described techniques may be performed by the network management function and the first MT function or first MT entity (e.g., UEF) and second MT function or second MT entity of the relay node. However, the described techniques can be extended by analogy to additional MT functions supported by the relay node without departing from the scope of this disclosure.

[0167] In section 605, a relay node can use the first MT function to select a first parent node (e.g., parent relay node, donor node's DU, etc.) based on a parent selection policy. For example, the relay node can identify the parent selection policy in the system information. In other cases, the parent selection policy can be pre-configured. In some cases, the relay node can connect to the network once to retrieve the parent selection policy from the OAM function or other sources.

[0168] In 610, the first MT function of the relay node can establish the first link to the selected parent (e.g., the first return link).

[0169] In section 615, the first MT function of a relay node can send a relay identifier (e.g., the relay node's identifier) ​​to the network management function during the link establishment process. In some cases, the relay identifier can be provided by the network (e.g., the network management function can establish the relay identifier and notify the relay node of its relay identifier during the link establishment process). In some examples, the first MT can also transmit the capabilities of additional MTs of the relay node (e.g., in a capability report containing several supported MTs, the capabilities of the MTs, etc., as described herein) to the network management function. In some cases, relay identifiers and / or capability reports can be transmitted using RRC messages. In some cases, the first MT function can receive policies or requests to activate other MTs from the network management function.

[0170] In 620, the relay node can use the established first radio link to access the backhaul traffic of the co-located DU.

[0171] In 625, using the second MT function, the relay node can measure and select a second parent relay node (e.g., based on a parent selection strategy). The relay node can then establish a second backhaul link with the selected parent node. In some cases, the measurement (e.g., measurement and selection) can be based on signal strength (e.g., measurements associated with different parent nodes). In some cases, the parent selection strategy used by the second MT function can be different from the parent selection strategy used by the first MT.

[0172] In 630, the second MT function of the relay node can establish a second return link to the selected parent node.

[0173] In section 635, during the link establishment process, the second MT function can send the relay identifier to network management functions (e.g., resource management functions). In some cases, the second MT function can use RRC signaling notification to transmit the relay identifier.

[0174] If the same network management function supports two parent nodes, the network management function can derive or identify that the first MT and the second MT reside on the same relay node, and can also identify that the relay node is therefore dual-connected. For example, the network management function can receive a relay identifier from the first MT function on the first backhaul link, and can also receive a relay identifier from the second MT function on the second backhaul link. In this way, the network management function can determine that the two received relay identifiers are associated with the same relay node, and that the relay node is therefore dual-connected on the two backhaul links to the network management function via the MT functions of the two relay nodes.

[0175] Network management functions can therefore perform additional configuration operations for each MT function of the relay node. For example, network management functions can configure which MT function of the relay node carries traffic, whether two backhaul links should be used in parallel, and whether one backhaul link should be reserved as a backup backhaul link. In some cases, each MT function can send its corresponding MT identifier during link establishment (e.g., at 610 and 630). In such cases, network management functions can include the identifier of the MT function being configured in the configuration sent to the MT. Thus, for example, network management functions can transmit the configuration of a second MT on the first link (e.g., by including the second MT function identifier in the backhaul link configuration message), and the relay node can identify that the backhaul link configuration is for the second MT function.

[0176] When different network management functions support two parent nodes (e.g., different management functions support a relay node autonomously connecting to a first and second parent node), each of the network management functions can treat the relay node as a single-connection node. In this way, each of the network management functions can perform additional configuration operations for one of the two MT functions. To avoid conflicting configurations (such as the same resource allocation for two links), the MT functions can provide different capabilities on each link (e.g., different supported frequency bands). In some cases, the MT can also use one link only as a backup link. Additionally, the relay node can identify or distinguish whether the MT functions are connected to the same or different network management functions (e.g., whether the two parent nodes to which the relay node's two MT functions are connected are supported by the same or different network management functions). For this purpose, the topology and resource management functions can provide their own identifiers (e.g., network management function identifiers or network identifiers) to each corresponding MT function of the relay node. The relay node can then compare the network management function identifiers received on each of its MT functions and identify or determine whether the relay node is dual-connected to a single network management function (e.g., if the network identifiers indicate the same network management function) or single-connected to two network management functions (e.g., if the network identifiers indicate different network management functions).

[0177] At 640, based on the configuration received at 635, the relay node can then use the second radio link for the access traffic or backhaul traffic of the co-located DU, or the relay node can use two radio links simultaneously (e.g., in parallel) for the access or backhaul traffic of the co-located DU. In some cases, the configuration can also specify whether the relay node wants to use the first link for a subset of the co-located DUs and the other link for another subset of the co-located DUs (e.g., in some cases, the configuration can partition the backhaul on the two backhaul links by assigning the backhaul of some co-located DUs to each link).

[0178] Figure 7 An example 700 of a processing flow supporting a relay node with multi-connectivity cellular backhaul according to one or more aspects of this disclosure is illustrated. In some examples, processing flow 700 may implement aspects of wireless communication system 100, wireless communication system 200, and / or wireless communication system 300. For example, processing flow 700 may include relay node 705, parent node 710-a, parent node 710-b, and CU 310-b, which may be corresponding functional examples of an IAB network architecture (e.g., such as network device 105 or base station 105, relay node 320, DU 315, CU 310), as referenced. Figures 1 to 4 As described, process flow 700 can illustrate how network management functions become aware of relay node support for multiple MTs and how network management functions control multiple MT operations. In the following description of process flow 700, operations between relay node 705, parent node 710, and network management functions (e.g., CU 310-a, or some network management function or network management function entity communicating with CU 310-a) may be transmitted in a different order than the exemplary order shown, or operations performed by relay node 705, parent node 710-a, parent node 710-b, and network management functions may be performed in a different order or at different times. In some cases, certain operations may also be excluded from process flow 700, or other operations may be added to process flow 700.

[0179] At 705, relay node 705 can (e.g., autonomously) establish a first backhaul link between a first MT function (e.g., MT 715-a) and a first parent node (e.g., parent node 710-a). In some cases, the first backhaul link can be established based on relay node 705, which uses MT 715-a to measure one or more parent nodes and selects parent node 710-a based on a parent selection policy. The first backhaul link can connect relay node 705 (e.g., specifically MT 715-a) to a network management function (e.g., CU 310-b) via parent node 710-a. As described above, in some cases, parent node 710-a can be a parent relay node or a DU associated with a donor node. That is, parent node 710-a can generally relate to the first node or CU 310-b, which communicates with relay node 705 under the control of a network management function (e.g., a management control function).

[0180] At 710, relay node 705 can (e.g., autonomously) establish a second backhaul link between a second MT function (e.g., MT 715-d) and a second parent node (e.g., parent node 710-b). In some cases, the second backhaul link can be established based on relay node 705, which uses MT 715-d to measure one or more parent nodes and selects parent node 710-b based on a parent selection strategy (e.g., which may be the same parent selection strategy used by MT 715-a or a different parent selection strategy). The second backhaul link can connect relay node 705 (e.g., specifically MT 715-d) to a network management function (e.g., CU 310-b) via parent node 710-b. As mentioned above, in some cases, parent node 710-b can be a parent relay node or a DU associated with a donor node. That is, the parent node 710-b can generally involve the second node or CU 310-b, and the second node communicates with the relay node 705 under the control of the management and control functions.

[0181] At 715, relay node 705 can exchange relay node identifiers with the network management function using MT 715-a. In some cases, the network management function can generate a relay identifier for relay node 705 (e.g., at 705, during link establishment) and can transmit the relay identifier to MT 715-a. In other cases, relay node 705 can identify the relay identifier (e.g., based on a node identification number) and transmit the relay identifier to the network management function (e.g., via the first return link to parent node 710-a).

[0182] At 720, relay node 705 can then use MT715-d to transmit (e.g., identified or received at 715) the relay identifier to the network management function via a second backhaul link to parent node 710-b.

[0183] At 725, the network management function can receive relay identifiers on two links (e.g., from parent node 710-a and parent node 710-b) and can identify that relay node 705 is dual-connected to the network management function (e.g., the network management function can identify that two relay identifiers received on two links are associated with the same relay node 705 and can infer that relay node 705 is dual-connected to the network management function).

[0184] At 730, the network management function can coordinate the use of the first and second backhaul links based on identifying the dual connection of relay node 705 to the network management function. For example, the network management function can identify the backhaul link configuration of the second connection's MT (e.g., MT715-d).

[0185] In 735, the network management function can transmit the backhaul link configuration to MT 715-d on the second link, or it can transmit the backhaul link configuration of MT 715-d to MT 715-a on the first link, wherein the backhaul link configuration includes an identifier of MT 715-d (e.g., enabling MT 715-a to know that the backhaul link configuration applies to MT 715-d and forward the backhaul link configuration to MT 715-d). In some cases, the first backhaul link can be configured additionally or alternatively in 730 and 735. Overall, once the dual connection of relay node 705 is determined to be to the network management function, the network management function can coordinate the configuration of the first and second backhaul links.

[0186] Figure 8 A block diagram 800 of an apparatus 805 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown. Apparatus 805 may be an example of an aspect of a relay node as described herein (e.g., such as relay network apparatus 105 or relay base station 105, relay IAB node 320, relay node 505, relay node 705). Apparatus 805 may include a receiver 810, a communications manager 815, and a transmitter 820. Apparatus 805 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0187] Receiver 810 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information about relay nodes with multi-connectivity cellular backhaul). The information can be passed to other components of device 805. Receiver 810 can serve as a reference. Figure 11 Examples of aspects of the transceiver 1120 described herein. The receiver 810 may utilize a single antenna or a set of antennas.

[0188] The communication manager 815 can transmit a measurement report to the network management function via a first backhaul link to the first parent node using the first mobile terminal function of the relay node, wherein the measurement report contains measurements transmitted by the second parent node. The communication manager 815 can receive the backhaul link configuration of the second mobile terminal function via the first backhaul link using the first mobile terminal function of the relay node based on the transmitted measurement report. The communication manager 815 can establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0189] The communication manager 815 can also use the first mobile terminal function of the relay node to exchange the relay node's identifier with the first network management function via a first backhaul link to the first parent node. The communication manager 815 can use the second mobile terminal function of the relay node to transmit the relay node's identifier to the second network management function via a second backhaul link to the second parent node. The communication manager 815 can receive the backhaul link configuration of the second mobile terminal function based on transmitting the relay node's identifier to the first network management function via the first backhaul link and transmitting the relay node's identifier to the second network management function via the second backhaul link. The communication manager 815 can be an example of an aspect of the communication manager 1110 described herein.

[0190] The communication manager 815 (or its sub-components) may be implemented as hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented as processor-executable code, the functionality of the communication manager 815 or its sub-components may be performed by a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0191] The communication manager 815 (or its sub-components) may be physically located in various locations, including portions distributed such that functionalities are implemented by one or more physical components at different physical locations. In some examples, the communication manager 815 (or its sub-components) may be separate and distinct components according to various aspects of this disclosure. In some examples, the communication manager 815 (or its sub-components) may be combined with one or more other hardware components, including, but not limited to, input / output (I / O) components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof according to various aspects of this disclosure.

[0192] Transmitter 820 can transmit signals generated by other components of device 805. In some examples, transmitter 820 can co-occur with receiver 810 in transceiver module. For example, transmitter 820 can be a reference. Figure 11 Examples of aspects of the described transceiver 1120. The transmitter 820 may utilize a single antenna or a set of antennas.

[0193] Figure 9 A block diagram 900 is shown of an apparatus 905 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure. Apparatus 905 may be an example of an apparatus 805 as described herein or an aspect of a relay node (e.g., such as relay network apparatus 105 or relay base station 105, relay IAB node 320, relay node 505, relay node 705). Apparatus 905 may include a receiver 910, a communications manager 915, and a transmitter 940. Apparatus 905 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0194] Receiver 910 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information about relay nodes with multi-connectivity cellular backhaul). This information can be transmitted to other components of device 905. Receiver 910 can serve as a reference. Figure 11 Examples of aspects of the described transceiver 1120. The receiver 910 may utilize a single antenna or a set of antennas.

[0195] Communication manager 915 may be an example of an aspect of communication manager 815 as described herein. Communication manager 915 may include measurement report manager 920, backhaul link configuration manager 925, backhaul link manager 930, and relay node ID manager 935. Communication manager 915 may be an example of an aspect of communication manager 1110 as described herein.

[0196] The Measurement Report Manager 920 can transmit measurement reports to the network management function via the first backhaul link to the first parent node using the first mobile terminal function of the relay node, wherein the measurement reports contain measurements transmitted by the second parent node.

[0197] The backhaul link configuration manager 925 can receive the backhaul link configuration of the second mobile terminal function via the first mobile terminal function of the relay node using the first mobile terminal function of the relay node based on the transmitted measurement report.

[0198] The backhaul link manager 930 can establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration.

[0199] The relay node ID manager 935 can use the first mobile terminal function of the relay node to exchange the identifier of the relay node with the first network management function via the first backhaul link to the first parent node, and use the second mobile terminal function of the relay node to transmit the identifier of the relay node to the second network management function via the second backhaul link to the second parent node.

[0200] The backhaul link configuration manager 925 can receive the backhaul link configuration of the second mobile terminal function based on the identifier of the relay node transmitted via the first backhaul link to the first network management function and the identifier of the relay node transmitted via the second backhaul link to the second network management function.

[0201] Transmitter 940 can transmit signals generated by other components of device 905. In some examples, transmitter 940 can co-occur with receiver 910 in transceiver module. For example, transmitter 940 can be a reference. Figure 11 Examples of aspects of the transceiver 1120 described. The transmitter 940 may utilize a single antenna or a set of antennas.

[0202] Figure 10 A block diagram 1000 of a communication manager 1005 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure, is shown. The communication manager 1005 may be an example of an aspect of the communication manager 815, communication manager 915, or communication manager 1110 described herein. The communication manager 1005 may include a measurement report manager 1010, a backhaul link configuration manager 1015, a backhaul link manager 1020, an MT capability manager 1025, a measurement configuration manager 1030, a parent node measurement manager 1035, a relay node ID manager 1040, and a management function ID manager 1045. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0203] The measurement report manager 1010 can transmit measurement reports to the network management function via the first backhaul link to the first parent node using the first mobile terminal function of the relay node, wherein the measurement report contains measurements transmitted by the second parent node.

[0204] The backhaul link configuration manager 1015 can receive the backhaul link configuration of the second mobile terminal function via the first backhaul link using the first mobile terminal function of the relay node, based on the transmitted measurement report. In some examples, the backhaul link configuration manager 1015 can receive the backhaul link configuration of the second mobile terminal function based on transmitting the relay node's identifier to the first network management function via the first backhaul link and transmitting the relay node's identifier to the second network management function via the second backhaul link.

[0205] In some examples, routing configurations for the first and second backhaul links are received, where the routing configurations include routing utilization information, link utilization information, resource allocation information, or combinations thereof. In some cases, the backhaul link configuration of the second mobile terminal function includes the identifier of the second mobile terminal function of the relay node, the identifier of the second parent node, routing configuration parameters, or combinations thereof. In some cases, the backhaul link configuration of the second mobile terminal function is received within a container of an RRC message received by the first mobile terminal function. In some cases, the backhaul link configuration of the second mobile terminal function is received in an F1-AP signaling notification. In some cases, the first and second network management functions each include a gNB, gNB-CU, gNB-CU-CP, eNB, eNB-CU, eNB-CU-CP, a central controller, topology functions, routing functions, resource functions, or combinations thereof.

[0206] The backhaul link manager 1020 can establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration. In some examples, the backhaul link manager 1020 can exchange backhaul information using the first mobile terminal function and the first network management function via the first backhaul link to the first parent node, and exchange backhaul information using the second mobile terminal function and the second network management function via the second backhaul link to the second parent node, or both, based on the received backhaul link configuration.

[0207] In some examples, the backhaul link manager 1020 can establish a first backhaul link between a first mobile terminal function of a relay node and a first parent node, wherein the relay node's identifier is transmitted to a first network management function via the established first backhaul link. In some examples, the backhaul link manager 1020 can establish a second backhaul link between a second mobile terminal function of a relay node and a second parent node, wherein the relay node's identifier is transmitted to a second network management function via the established second backhaul link. In some examples, the backhaul link manager 1020 can exchange backhaul information using the first backhaul link, the second backhaul link, or both, based on the received backhaul link configuration.

[0208] In some cases, the first and second parent nodes are associated with network management functions supported by the CU. In some cases, network management functions include gNB, gNB-CU, gNB-CU-CP, eNB, eNB-CU, eNB-CU-CP, central controller, topology functions, routing functions, resource functions, or some combination thereof.

[0209] The relay node ID manager 1040 can use the relay node's first mobile terminal function to exchange the relay node's identifier with the first network management function via a first backhaul link to the first parent node. In some examples, the relay node ID manager 1040 can use the relay node's second mobile terminal function to transmit the relay node's identifier to the second network management function via a second backhaul link to the second parent node.

[0210] The MT Capability Manager 1025 can transmit capability reports to network management functions via a first backhaul link using a first mobile terminal function. In some examples, the MT Capability Manager 1025 can transmit capability reports to a second parent node using a second mobile terminal function, wherein the capability report includes an identifier of the second mobile terminal function, one or more RATs supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, RF capabilities of the second mobile terminal function, isolation between the first and second mobile terminal functions, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

[0211] In some cases, the capability report includes the identifier of the second mobile terminal function, one or more RATs supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, RF capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, the identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

[0212] Measurement configuration manager 1030 can receive measurement configurations of a relay node's second mobile terminal function via a first backhaul link using the relay node's first mobile terminal function, based on the transmitted capability report. In some examples, measurement configuration manager 1030 can receive measurement configurations of a second mobile terminal function using the relay node's first mobile terminal function, wherein one or more signal strength measurements are performed based on the received measurement configuration. In some cases, the measurement configuration includes an identifier for the second mobile terminal function, an identifier for the second parent node, or some combination thereof.

[0213] The parent node measurement manager 1035 can perform measurements of a second parent node's transmissions using the second mobile terminal function of the relay node based on a measurement configuration, wherein the transmitted measurement report contains the measurements. In some examples, the parent node measurement manager 1035 can use the second mobile terminal function to perform one or more signal strength measurements on one or more parent nodes. In some examples, the parent node measurement manager 1035 can identify a second parent node based on one or more signal strength measurements, wherein a second backhaul link is established based on the identified second parent node.

[0214] The Management Function ID Manager 1045 can receive an identifier for a first network management function associated with a first backhaul link. In some examples, the Management Function ID Manager 1045 can receive an identifier for a second network management function associated with a second backhaul link. In some examples, the Management Function ID Manager 1045 can determine that the identifier for the first management function associated with the first backhaul link is different from the identifier for the second management function associated with the second backhaul link. In some examples, the Management Function ID Manager 1045 can identify that the backhaul link configuration of a second mobile terminal function is associated with the second management function of the second backhaul link. In some examples, the Management Function ID Manager 1045 can determine that the identifier for the first management function associated with the first backhaul link is the same as the identifier for the second management function associated with the second backhaul link. In some examples, the Management Function ID Manager 1045 can identify that the backhaul link configuration of a second mobile terminal function is associated with the same management function of both the first and second backhaul links.

[0215] Figure 11 A system 1100 comprising an apparatus 1105 supporting a cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is illustrated. Apparatus 1105 may be an example of or include components of an apparatus 805, apparatus 905, or a relay node (e.g., such as relay base station 105, relay IAB node 320, relay node 505, relay node 705) as described herein. Apparatus 1105 may include components for bidirectional audio and data communication, components for transmitting and receiving communication, including a communication manager 1110, an I / O controller 1115, a transceiver 1120, an antenna 1125, a memory 1130, and a processor 1140. These components may communicate electronically via one or more buses (e.g., bus 1145).

[0216] The communication manager 1110 can transmit a measurement report (containing measurements transmitted by the second parent node) to a network management function via a first backhaul link to the first parent node using the first mobile terminal function of the relay node; receive a backhaul link configuration for the second mobile terminal function via the first backhaul link based on the transmitted measurement report; and establish a second backhaul link between the second mobile terminal function of the relay node and the second parent node based on the received backhaul link configuration. The communication manager 1110 can also exchange the relay node's identifier with the first network management function via the first backhaul link to the first parent node using the first mobile terminal function of the relay node; transmit the relay node's identifier to the second network management function via the second backhaul link to the second parent node using the second mobile terminal function of the relay node; and receive a backhaul link configuration for the second mobile terminal function based on transmitting the relay node's identifier to the first network management function via the first backhaul link and transmitting the relay node's identifier to the second network management function via the second backhaul link.

[0217] I / O controller 1115 can manage the input and output signals of device 1105. I / O controller 1115 can also manage peripherals not integrated into device 1105. In some cases, I / O controller 1115 can represent a physical connection or port to an external peripheral. In some cases, I / O controller 1115 can utilize an operating system, such as... Or another known operating system. In other cases, I / O controller 1115 may represent or interact with a modem, keyboard, mouse, touchscreen, or similar device. In some cases, I / O controller 1115 may be implemented as part of a processor. In some cases, a user may interact with device 110 via I / O controller 1115 or via hardware components controlled by I / O controller 1115.

[0218] Transceiver 1120 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1120 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1120 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0219] In some cases, the wireless device may contain a single antenna 1125. However, in other cases, the device may have more than one antenna 1125, which is capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0220] Memory 1130 may include RAM and ROM. Memory 1130 may store computer-readable, computer-executable code or software 1135, which contains instructions that, when executed, cause the processor to perform the various functions described herein. In some cases, among others, memory 1130 may contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0221] Processor 1140 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1140 may be configured to operate a memory array using a memory controller. In other cases, the memory controller may be integrated into processor 1140. Processor 1140 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1130) to cause device 1105 to perform various functions (e.g., functions or tasks supporting relay nodes with multi-connectivity cellular backhaul).

[0222] Software 1135 may contain instructions to implement aspects of this disclosure, including instructions supporting wireless communication. Software 1135 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, software 1135 may not be directly executable by processor 1140, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0223] Figure 12 A block diagram 1200 is shown of an apparatus 1205 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure. Apparatus 1205 may be an example of a base station 105, a parent node, or an aspect of network management functionality as described herein. Apparatus 1205 may include a receiver 1210, a communications manager 1215, and a transmitter 1220. Apparatus 1205 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0224] Receiver 1210 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information about relay nodes with multi-connectivity cellular backhaul). The information can be transmitted to other components of device 1205. Receiver 1210 can serve as a reference. Figure 15 Examples of aspects of the transceiver 1520 described. The receiver 1210 may utilize a single antenna or a set of antennas.

[0225] The communication manager 1215 can receive measurement reports from a first mobile terminal function of a relay node via a first backhaul link using network management functions. These measurement reports contain measurements transmitted by a second parent node. The communication manager 1215 can identify the backhaul link configuration of the second mobile terminal function based on the received measurement reports. The communication manager 1215 can then transmit the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link.

[0226] Communication manager 1215 can also identify relay nodes connected to a first parent node via a first mobile terminal function of the relay node, identify relay nodes connected to a second parent node via a second mobile terminal function of the relay node, and transmit backhaul link configurations for the second mobile terminal function based on the identified relay node connections. Communication manager 1215 may be an example of an aspect of communication manager 1510 described herein.

[0227] The communication manager 1215 (or its sub-components) may be implemented as hardware, processor-executable code (e.g., software or firmware), or any combination thereof. If implemented as processor-executable code, the functionality of the communication manager 1215 or its sub-components may be performed by a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described in this disclosure.

[0228] The communication manager 1215 (or its sub-components) may be physically located in various locations, including distributions such that functional parts are implemented by one or more physical components in different physical locations. In some examples, the communication manager 1215 (or its sub-components) may be separate and distinct components according to various aspects of this disclosure. In some examples, the communication manager 1215 (or its sub-components) may be combined with one or more other hardware components, including, but not limited to, I / O components, transceivers, network servers, other computing devices, one or more other components described in this disclosure, or combinations thereof according to various aspects of this disclosure.

[0229] Transmitter 1220 can transmit signals generated by other components of device 1205. In some examples, transmitter 1220 can co-occur with receiver 1210 in transceiver module. For example, transmitter 1220 can be a reference. Figure 15 Examples of aspects of the described transceiver 1520. The transmitter 1220 may utilize a single antenna or a set of antennas.

[0230] Figure 13A block diagram 1300 is shown of an apparatus 1305 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure. Apparatus 1305 may be an aspect of apparatus 1205 as described herein, or an example of a base station 105, a parent node, or a network management function. Apparatus 1305 may include a receiver 1310, a communications manager 1315, and a transmitter 1335. Apparatus 1305 may also include a processor. Each of these components may communicate with each other (e.g., via one or more buses).

[0231] Receiver 1310 can receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information associated with relay nodes having multiple connections in a cellular backhaul). The information can be passed to other components of device 1305. Receiver 1310 can serve as a reference. Figure 15 Examples of aspects of the transceiver 1520 described. The receiver 1310 may utilize a single antenna or a set of antennas.

[0232] Communication manager 1315 may be an example of an aspect of communication manager 1215 as described herein. Communication manager 1315 may include measurement report manager 1320, backhaul link configuration manager 1325, and backhaul link manager 1330. Communication manager 1315 may be an example of an aspect of communication manager 1510 as described herein.

[0233] The measurement report manager 1320 can receive measurement reports from the first mobile terminal function of the relay node via the first backhaul link through the network management function, wherein the measurement report contains measurements transmitted by the second parent node.

[0234] The backhaul link configuration manager 1325 can identify the backhaul link configuration of the second mobile terminal function based on the received measurement report, and transmit the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link.

[0235] The backhaul link manager 1330 can identify whether a relay node is connected to a first parent node via the relay node's first mobile terminal function and whether the relay node is connected to a second parent node via the relay node's second mobile terminal function.

[0236] The backhaul link configuration manager 1325 can transmit backhaul link configurations for second mobile terminal functionality based on the identified relay node connection.

[0237] Transmitter 1335 can transmit signals generated by other components of device 1305. In some examples, transmitter 1335 can co-occur with receiver 1310 in a transceiver module. For example, transmitter 1335 can be a reference. Figure 15 Examples of aspects of the described transceiver 1520. The transmitter 1335 may utilize a single antenna or a set of antennas.

[0238] Figure 14 A block diagram 1400 is shown of a communication manager 1405 supporting a relay node with multiple connections for cellular backhaul, according to one or more aspects of this disclosure. The communication manager 1405 may be an example of an aspect of the communication manager 1215, communication manager 1315, or communication manager 1510 described herein. The communication manager 1405 may include a measurement report manager 1410, a backhaul link configuration manager 1415, an MT capability manager 1420, a measurement configuration manager 1425, a backhaul link manager 1430, a management function ID manager 1435, and a relay node ID manager 1440. Each of these modules may communicate directly or indirectly with each other (e.g., via one or more buses).

[0239] The measurement report manager 1410 can receive measurement reports from the first mobile terminal function of the relay node via the first backhaul link through the network management function, wherein the measurement report contains measurements transmitted by the second parent node.

[0240] The backhaul link configuration manager 1415 can identify the backhaul link configuration of the second mobile terminal function based on the received measurement report. In some examples, the backhaul link configuration manager 1415 can transmit the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link. In some examples, the backhaul link configuration manager 1415 can transmit the backhaul link configuration of the second mobile terminal function based on the identified relay node connection.

[0241] In some examples, routing configuration for a second backhaul link is transmitted between the second mobile terminal function of the relay node and the first parent node, and routing configuration for a first backhaul link is transmitted between the first MT of the relay node and the first parent node, wherein the routing configuration includes routing utilization information, link utilization information, resource allocation information, or some combination thereof.

[0242] In some cases, the backhaul link configuration of the second mobile terminal function includes the identifier of the second mobile terminal function of the relay node, the identifier of the second parent node, routing configuration parameters, or some combination thereof. In some cases, the backhaul link configuration of the second mobile terminal function is transmitted to the first mobile terminal function in a container of an RRC message. In some cases, the backhaul link configuration of the second mobile terminal function is transmitted in an F1-AP signaling notification.

[0243] Backhaul link manager 1430 can identify a relay node connected to a first parent node via a first mobile terminal function of the relay node. In some examples, backhaul link manager 1430 can identify a relay node connected to a second parent node via a second mobile terminal function of the relay node. In some examples, backhaul link manager 1430 can receive backhaul information from the first mobile terminal function of the relay node via the first parent node, and from the second mobile terminal function of the relay node via the second parent node, or both, based on the transmitted backhaul link configuration. In some cases, a first backhaul link between the first mobile terminal function of the relay node and the first parent node and a second backhaul link between the second mobile terminal function of the relay node and the first parent node are associated with a cellular RAT.

[0244] The MT Capability Manager 1420 can receive a capability report from a first mobile terminal function (RTF) of a relay node via a first backhaul link. This capability report contains capability information for a second RTF of the relay node. In some cases, the capability report includes an identifier for the second RTF, one or more RATs supported by the second RTF, one or more frequency bands supported by the second RTF, azimuth and elevation modes supported by the second RTF, RF capabilities of the second RTF, isolation between the first and second RTFs, an identifier for the relay node, a list of supported RTFs, or combinations thereof.

[0245] Measurement configuration manager 1425 can identify the measurement configuration of the second mobile terminal function of the relay node based on the received capability report. In some examples, measurement configuration manager 1425 can transmit the identified measurement configuration to the first mobile terminal function via a first backhaul link, wherein a measurement report is received based on the transmitted measurement configuration. In some examples, the measurement configuration of the second mobile terminal function is transmitted to the relay node, wherein the measurement configuration includes an identifier of the second parent node, relay node selection policy information of the second parent node, or some combination thereof. In some cases, the measurement configuration includes an identifier of the second mobile terminal function, an identifier of the second parent node, or some combination thereof.

[0246] The Management Function ID Manager 1435 can transmit the network management function identifier to the relay node via the first parent node. In some examples, the Management Function ID Manager 1435 can transmit the management function identifier to the relay node via the second parent node. The Relay Node ID Manager 1440 can receive the relay node identifier from the first parent node. In some examples, the Relay Node ID Manager 1440 can receive the relay node identifier from the second parent node, wherein the identifier that the relay node is connected to the second parent node via the relay node's second mobile terminal function is based on the fact that the relay node identifier from the second parent node is the same as the relay node identifier from the first parent node.

[0247] Figure 15 A system 1500 comprising a relay node supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is illustrated. The device 1505 may be an aspect of device 1205, device 1305, or base station 105 as described herein, an example of a parent node or network management function, or include components thereof. The device 1505 may include components for bidirectional audio and data communication, components for transmitting and receiving communication, including a communication manager 1510, a network communication manager 1515, a transceiver 1520, an antenna 1525, a memory 1530, a processor 1540, and an inter-site communication manager 1545. These components may communicate electronically via one or more buses (e.g., bus 1550).

[0248] The communication manager 1510 can receive measurement reports from a first mobile terminal function of a relay node via a first backhaul link through a network management function. These measurement reports contain measurements transmitted by a second parent node. Based on the received measurement reports, the communication manager identifies the backhaul link configuration of the second mobile terminal function and transmits the identified backhaul link configuration of the second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link. The communication manager 1510 can also identify whether a relay node is connected to a first parent node via its first mobile terminal function, identify whether a relay node is connected to a second parent node via its second mobile terminal function, and transmit the backhaul link configuration of the second mobile terminal function based on the identified relay node connection.

[0249] The network communication manager 1515 can manage communication with the core network (e.g., via one or more wired backhaul links). For example, the network communication manager 1515 can manage the transmission of data communication by client devices such as one or more UE 115.

[0250] Transceiver 1520 can communicate bidirectionally via one or more antennas, wired or wireless links as described above. For example, transceiver 1520 can represent a wireless transceiver and can communicate bidirectionally with another wireless transceiver. Transceiver 1520 may also include a modem to modulate packets and provide the modulated packets to the antenna for transmission, and demodulate packets received from the antenna.

[0251] In some cases, the wireless device may contain a single antenna 1525. However, in other cases, the device may have more than one antenna 1525, which is capable of transmitting or receiving multiple wireless transmissions simultaneously.

[0252] Memory 1530 may include RAM, ROM, or a combination thereof. Memory 1530 may store computer-readable code or software 1535 containing instructions that, when executed by a processor (e.g., processor 1540), cause the device to perform the various functions described herein. In some cases, among others, memory 1530 may contain a BIOS that controls basic hardware or software operations, such as interaction with peripheral components or devices.

[0253] Processor 1540 may include intelligent hardware devices (e.g., general-purpose processors, DSPs, CPUs, microcontrollers, ASICs, FPGAs, programmable logic devices, discrete gate or transistor logic components, discrete hardware components, or any combination thereof). In some cases, processor 1540 may be configured to operate a memory array using a memory controller. In some cases, the memory controller may be integrated into processor 1540. Processor 1540 may be configured to execute computer-readable instructions stored in memory (e.g., memory 1530) to cause device 1505 to perform various functions (e.g., functions or tasks supporting relay nodes with multi-connectivity cellular backhaul).

[0254] Inter-site communication manager 1545 can manage communication with other base stations 105 and may include a controller or scheduler to cooperate with other base stations 105 to control communication with UE 115. For example, inter-site communication manager 1545 can coordinate the scheduling of transmissions to UE 115 for various interference mitigation techniques such as beamforming or joint transmission. In some examples, inter-site communication manager 1545 may provide an X2 interface within LTE / LTE-A wireless communication network technology to facilitate communication between base stations 105.

[0255] Software 1535 may contain instructions to implement aspects of this disclosure, including instructions supporting wireless communication. Software 1535 may be stored in a non-transitory computer-readable medium, such as system memory or other types of memory. In some cases, software 1535 may not be directly executable by processor 1540, but may enable a computer (e.g., when compiled and executed) to perform the functions described herein.

[0256] Figure 16 A flowchart illustrating method 1600 for supporting cellular backhaul with multiple connections is shown, according to one or more aspects of this disclosure. Operation of method 1600 can be implemented by a relay node or its components as described herein. For example, operation of method 1600 can be achieved by, as referenced... Figures 8 to 11 The communication manager described herein performs the functions. In some examples, the relay node can execute a set of instructions to control the functional elements of the relay node to perform the functions described below. Alternatively or additionally, the relay node may use dedicated purpose hardware to perform aspects of the functions described below.

[0257] In 1605, the relay node can use its first mobile terminal function to transmit a measurement report to the network management function via the first backhaul link to the first parent node, where the measurement report contains measurements from the second parent node. The operation of 1605 can be performed according to the methods described herein. In some examples, aspects of the operation of 1605 can be described by reference to [reference needed]. Figures 8 to 11 The described measurement report manager is used.

[0258] In 1610, the relay node can establish a second backhaul link between the relay node's second mobile terminal function and the second parent node based on the received backhaul link configuration. The operation of 1610 can be performed according to the methods described herein. In some examples, aspects of the operation of 1610 can be derived from, as referenced... Figures 8 to 11 The backhaul link manager described is used.

[0259] In step 1615, the relay node can receive a backhaul link configuration for a second mobile terminal function via a first backhaul link using the relay node's first mobile terminal function, based on the transmitted measurement report. Operation of step 1615 can be performed according to the methods described herein. In some examples, aspects of operation of step 1615 can be derived from, as referenced... Figures 8 to 11 The backhaul link configuration manager is described.

[0260] Figure 17A flowchart illustrating method 1700 for supporting cellular backhaul with multiple connections according to one or more aspects of this disclosure is shown. Operation of method 1700 can be implemented by a relay node or its components as described herein. For example, operation of method 1700 can be implemented by, as referenced... Figures 8 to 11 The communication manager described herein performs the functions. In some examples, the relay node can execute a set of instructions to control the functional elements of the relay node to perform the functions described below. Alternatively or additionally, the relay node may use dedicated purpose hardware to perform aspects of the functions described below.

[0261] In 1705, the relay node can transmit a capability report to the network management function via the first backhaul link using the first mobile terminal function. The operation of 1705 can be performed according to the methods described herein. In some examples, aspects of the operation of 1705 can be described as follows: Figures 8 to 11 The MT Capability Manager is described.

[0262] In 1710, a relay node can receive a measurement configuration of its second mobile terminal function via a first backhaul link using its first mobile terminal function, based on the transmitted capability report. Operation of 1710 can be performed according to the methods described herein. In some examples, aspects of operation of 1710 can be derived from references... Figures 8 to 11 The described measurement configuration manager is used.

[0263] In 1715, the relay node can use its second mobile terminal functionality, based on a measurement configuration, to perform measurements transmitted by the second parent node, wherein the transmitted measurement report contains the measurements. The operation of 1715 can be performed according to the methods described herein. In some examples, aspects of the operation of 1715 can be derived from, as referenced... Figures 8 to 11 The parent node measurement manager is described.

[0264] In 1720, the relay node can use its first mobile terminal function to transmit measurement reports to the network management function via the first backhaul link to the first parent node, where the measurement reports contain measurements transmitted by the second parent node. The operation of 1720 can be performed according to the methods described herein. In some examples, aspects of the operation of 1720 can be derived from references... Figures 8 to 11 The described measurement report manager is used.

[0265] At 1725, the relay node can establish a second backhaul link between the relay node's second mobile terminal function and the second parent node based on the received backhaul link configuration. The operation of 1725 can be performed according to the methods described herein. In some examples, aspects of the operation of 1725 can be derived from, as referenced... Figures 8 to 11The backhaul link manager described is used.

[0266] At 1730, the relay node can receive a backhaul link configuration for a second mobile terminal function via a first backhaul link using the relay node's first mobile terminal function, based on the transmitted measurement report. Operation of 1730 can be performed according to the methods described herein. In some examples, aspects of operation of 1730 can be derived from, as referenced... Figures 8 to 11 The backhaul link configuration manager is described.

[0267] At 1735, the relay node can receive routing configurations for the first and second backhaul links, whereby the routing configurations include routing utilization information, link utilization information, resource allocation information, or combinations thereof. Operation of 1735 can be performed according to the methods described herein. In some examples, aspects of 1735 operation can be derived from, as referenced... Figures 8 to 11 The backhaul link configuration manager is described.

[0268] Figure 18 A flowchart illustrating method 1800 for supporting a relay node with multiple connections for cellular backhaul according to one or more aspects of this disclosure is shown. Operation of method 1800 may be implemented by management functions (e.g., a CU or base station) or components thereof as described herein. For example, operation of method 1800 may be implemented by, as referenced... Figures 12 to 15 The communication manager described herein performs the functions described. In some examples, the management function (e.g., or CU or base station) may execute a set of instructions to control the functional elements of the management function (e.g., or CU or base station) to perform the functions described below. Alternatively or additionally, the management function (e.g., or CU or base station) may use dedicated purpose hardware to perform aspects of the functions described below.

[0269] At 1805, the management function (e.g., CU or base station) can receive a measurement report from a first mobile terminal function via a first backhaul link from a relay node, wherein the measurement report contains measurements transmitted by a second parent node. Operation of 1805 can be performed according to the methods described herein. In some examples, aspects of operation of 1805 can be described as referenced... Figures 12 to 15 The described measurement report manager is used.

[0270] In 1810, management functions (e.g., CU or base station) can identify the backhaul link configuration of the second mobile terminal function based on the received measurement reports. Operation of 1810 can be performed according to the methods described herein. In some examples, aspects of operation of 1810 can be determined by reference to... Figures 12 to 15 The backhaul link configuration manager is described.

[0271] In step 1815, a management function (e.g., a CU or base station) can transmit the backhaul link configuration of the identified second mobile terminal function to the first mobile terminal function of the relay node via the first backhaul link. Operation of step 1815 can be performed according to the methods described herein. In some examples, aspects of the operation of step 1815 can be determined by reference to... Figures 12 to 15 The backhaul link configuration manager is described.

[0272] Figure 19 A flowchart illustrating method 1900 for supporting cellular backhaul with multiple connections, according to one or more aspects of this disclosure, is shown. Operation of method 1900 can be implemented by a relay node or its components as described herein. For example, operation of method 1900 can be achieved by, as referenced... Figures 8 to 11 The communication manager described herein performs the functions. In some examples, the relay node can execute a set of instructions to control the functional elements of the relay node to perform the functions described below. Alternatively or additionally, the relay node may use dedicated purpose hardware to perform aspects of the functions described below.

[0273] In 1905, the relay node can use its first mobile terminal function to exchange its identifier with the first network management function via the first backhaul link to the first parent node. Operation of 1905 can be performed according to the methods described herein. In some examples, aspects of operation of 1905 can be described as follows: Figures 8 to 11 The relay node ID manager is described.

[0274] In 1910, the relay node can use its second mobile terminal function to transmit its identifier to the second network management function via a second backhaul link to the second parent node. Operation of 1910 can be performed according to the methods described herein. In some examples, aspects of 1910 operation can be derived from, as referenced... Figures 8 to 11 The relay node ID manager is described.

[0275] In 1915, the relay node can receive the backhaul link configuration of the second mobile terminal function based on transmitting the relay node's identifier to the first network management function via the first backhaul link and transmitting the relay node's identifier to the second network management function via the second backhaul link. The operation of 1915 can be performed according to the methods described herein. In some examples, aspects of the operation of 1915 can be derived from, as referenced... Figures 8 to 11 The backhaul link configuration manager is described.

[0276] Figure 20A flowchart illustrating a method 2000 for supporting a relay node with multiple connections for cellular backhaul according to one or more aspects of this disclosure is shown. Operation of method 2000 can be implemented by management functions (e.g., a CU or base station) or components thereof as described herein. For example, operation of method 2000 can be implemented by, as referenced... Figures 12 to 15 The communication manager described herein performs the functions described. In some examples, the management function (e.g., or CU or base station) may execute a set of instructions to control the functional elements of the management function (e.g., or CU or base station) to perform the functions described below. Alternatively or additionally, the management function (e.g., or CU or base station) may use dedicated purpose hardware to perform aspects of the functions described below.

[0277] In 2005, management functions (e.g., CU or base station) can identify that a relay node is connected to a first parent node via a first mobile terminal function of the relay node. Operation of 2005 can be performed according to the methods described herein. In some examples, aspects of operation of 2005 can be determined by reference to [reference needed]. Figures 12 to 15 The backhaul link manager described is used.

[0278] In 2010, management functions (e.g., CU or base station) can identify a relay node connected to a second parent node via a second mobile terminal function of the relay node. Operation of 2010 can be performed according to the methods described herein. In some examples, aspects of operation of 2010 can be determined by reference to [reference needed]. Figures 12 to 15 The backhaul link manager described is used.

[0279] In 2015, management functions (e.g., CU or base station) transmit backhaul link configurations for second mobile terminal functions based on identified relay node connections. Operation in 2015 can be performed according to the methods described herein. In some examples, aspects of operation in 2015 can be determined by reference to [reference needed]. Figures 12 to 15 The backhaul link configuration manager is described.

[0280] It should be noted that the methods described in this paper describe possible implementations, and the operations and steps can be rearranged or otherwise modified, and other implementations are possible. Furthermore, aspects from two or more methods can be combined.

[0281] The technologies described in this article can be used in various wireless communication systems, such as CDMA, TDMA, FDMA, OFDMA, Single Carrier Frequency Division Multiple Access (SC-FDMA), and others. CDMA systems can implement radio technologies such as CDMA2000 and Universal Terrestrial Radio Access (UTRA). CDMA2000 covers the IS-2000, IS-95, and IS-856 standards. IS-2000 releases may generally be referred to as CDMA2000 1X, 1X, etc. IS-856 (TIA-856) is generally referred to as CDMA2000 1xEV-DO, High Rate Packet Data (HRPD), etc. UTRA includes Wideband CDMA (WCDMA) and other variants of CDMA. TDMA systems can implement radio technologies such as Global System for Mobile Communications (GSM).

[0282] OFDMA systems can implement radio technologies such as Ultra Mobile Broadband (UMB), Evolved UTRA (E-UTRA), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and Flash OFDM. UTRA and E-UTRA are part of the Universal Mobile Telecommunications System (UMTS). LTE, LTE-A, and LTE-A Pro are releases of UMTS using E-UTRA. UTRA, E-UTRA, UMTS, LTE, LTE-A, LTE-APro, NR, and GSM are described in documents from an organization called the 3rd Generation Partnership Project (3GPP). CDMA2000 and UMB are described in documents from an organization called 3rd Generation Partnership Project 2 (3GPP2). The technologies described herein can be used in the systems and radio technologies mentioned herein, as well as in other systems and radio technologies. While aspects of LTE, LTE-A, LTE-A Pro, or NR systems may be described for illustrative purposes, and the terms LTE, LTE-A, LTE-A Pro, or NR systems may be used in multiple places in the specification, the techniques described herein are applicable to applications other than LTE, LTE-A, LTE-A Pro, or NR.

[0283] Macro cells generally cover a relatively large geographic area (e.g., a radius of several kilometers) and can allow unrestricted access for UE 115 with a service subscription to a network provider. In contrast, small cells can be associated with a lower-power base station 105 and can operate in the same or different (e.g., licensed, unlicensed, etc.) frequency bands as macro cells. Depending on various examples, small cells can include picocells, femtocells, and microcells. A picocell can, for example, cover a small geographic area and can allow unrestricted access for UE 115 with a service subscription to a network provider. A femtocell can also cover a small geographic area (e.g., a home) and can provide restricted access for UE 115 associated with a femtocell (e.g., UE 115 in a Closed Subscription Group (CSG), UE 115 of a user in a home, etc.). The eNB of a macro cell can be referred to as a macro eNB. The eNB of a small cell can be referred to as a small cell eNB, pico eNB, femtocell eNB, or home eNB. eNB can support one or more (e.g., two, three, four, etc.) cells, and can also support communication using one or more component carriers.

[0284] The wireless communication system 100, or the system described herein, can support synchronous or asynchronous operation. For synchronous operation, base stations 105 can have similar frame timing, and transmissions from different base stations 105 can be approximately time-aligned. For asynchronous operation, base stations 105 can have different frame timing, and transmissions from different base stations 105 can be time-misaligned. The techniques described herein can be used for both synchronous and asynchronous operation.

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

[0286] The various illustrative blocks and modules described herein can be implemented or performed using a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device (PLD), discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor may be a microprocessor, but alternatively, the processor may be any conventional processor, controller, microcontroller, or state machine. The processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, a combination of multiple microprocessors, a combination of one or more microprocessors incorporating a DSP core, or any other such configuration).

[0287] The functionality described herein can be implemented as hardware, software executed by a processor, firmware, or any combination thereof. If implemented as software executed by a processor, the functionality can be stored in or emitted as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of this disclosure and the appended claims. For example, due to the nature of software, the functionality described herein can be implemented using software executed by a processor, hardware, firmware, hardwiring, or any combination thereof. Features implementing the functionality can also be physically located, including distributions such that portions of the functionality are implemented in different physical locations.

[0288] Computer-readable media encompasses both non-transitory computer storage media and communication media, including any medium that facilitates the transfer of a computer program from one location to another. Non-transitory storage media can be any available medium accessible to a general-purpose or special-purpose computer. By way of example, and not limitation, non-transitory computer-readable media can include random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory, optical disc (CD) ROM or other optical disc storage, disk storage or other magnetic storage devices, or any other non-transitory medium that can be carried, or stores required program code in the form of instructions or data structures, accessible to a general-purpose or special-purpose computer or a general-purpose or special-purpose processor. Furthermore, any connection is appropriately referred to as computer-readable media. For example, the definition of media includes coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave if software is transferred from a website, server, or other remote source using coaxial cable, fiber optic cable, twisted pair, DSL, or wireless technologies such as infrared, radio, and microwave. The disks and optical discs used in this article include CDs, laser discs, optical discs, digital multifunction discs (DVDs), floppy disks, and Blu-ray discs. Disks typically copy data magnetically, while optical discs copy data optically using lasers. Combinations of these are also included within the scope of computer-readable media.

[0289] As used herein, the word "or" in a list of items (e.g., a list of items beginning with a phrase such as "at least one" or "one or more") included in the claims indicates an inclusive list, such as a list of at least one of A, B, or C indicating A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, as used herein, the phrase "based on" should not be construed as a reference to a closed set of conditions. For example, an exemplary step described as "based on condition A" may be based on both condition A and condition B without departing from the scope of this disclosure. In other words, as used herein, the phrase "based on" should be interpreted in the same manner as the phrase "at least partially based on".

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

[0291] The description presented herein, taken in conjunction with the accompanying drawings, illustrates exemplary configurations and does not represent all examples that can be implemented or that are within the scope of the claims. The term "exemplary" as used herein means "serving as an example, instance, or illustration," and not "preferred" or "superior to other examples." Specific details are included in the detailed description to provide an understanding of the described techniques. However, these techniques can be practiced without these specific details. In some instances, well-known structures and devices are shown in block diagram form to avoid obscuring the concepts of the described examples.

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

Claims

1. A method for wireless communication at a relay node, comprising: The relay node uses a first mobile terminal function to transmit a measurement report to the network management function via a first backhaul link to the first parent node, wherein the measurement report includes measurements transmitted by the second parent node; Based at least in part on the transmitted measurement reports, the relay node uses the first mobile terminal function to receive the backhaul link configuration of the second mobile terminal function via the first backhaul link; as well as A second backhaul link is established between the second mobile terminal function of the relay node and the second parent node, based at least in part on the received backhaul link configuration.

2. The method according to claim 1, further comprising: The system receives routing configurations for the first backhaul link and the second backhaul link, wherein the routing configurations include routing utilization information, link utilization information, resource allocation information, or some combination thereof.

3. The method according to claim 1, further comprising: The first mobile terminal function is used to transmit a capability report to the network management function via the first backhaul link; Based at least in part on the transmitted capability report, the measurement configuration of the relay node's second mobile terminal function is received via the first backhaul link using the relay node's first mobile terminal function. as well as Measurements transmitted by the second parent node are performed using the second mobile terminal function of the relay node, at least in part, based on the measurement configuration, wherein the transmitted measurement report includes the measurements.

4. The method of claim 3, wherein the capability report includes an identifier of the second mobile terminal function, one or more radio access technologies (RATs) supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, radio frequency (RF) capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

5. The method of claim 3, wherein the measurement configuration includes an identifier for the second mobile terminal function, an identifier for the second parent node, or some combination thereof.

6. The method according to claim 1, wherein the backhaul link configuration of the second mobile terminal function includes an identifier of the second mobile terminal function of the relay node, an identifier of the second parent node, routing configuration parameters, or some combination thereof.

7. The method of claim 1, wherein the backhaul link configuration of the second mobile terminal function is received in a container of a Radio Resource Control (RRC) message received by the first mobile terminal function or in an F1 Application Protocol (F1-AP) signaling notification.

8. The method of claim 1, wherein the first parent node and the second parent node are associated with network management functions supported by a central unit (CU), and the network management functions include a next-generation Node B (gNB), a gNB-Central Unit (gNB-CU), a gNB-CU-Control Plane (gNB-CU-CP), an evolved Node B (eNB), an eNB-Central Unit (eNB-CU), an eNB-CU-Control Plane (eNB-CU-CP), a centralized controller, topology functions, routing functions, resource functions, or combinations thereof.

9. A method for wireless communication, comprising: The network management function receives a measurement report from the first mobile terminal function of the relay node via the first backhaul link, wherein the measurement report includes measurements transmitted by the second parent node; The backhaul link configuration of the second mobile terminal function is identified at least in part based on the received measurement reports; as well as The network management function transmits the backhaul link configuration of the second mobile terminal function, identified by the second mobile terminal function, to the first mobile terminal function of the relay node via the first backhaul link.

10. The method of claim 9, further comprising: The network management function transmits a routing configuration for a second backhaul link between the second mobile terminal function of the relay node and the first parent node, and transmits a routing configuration for a first backhaul link between the first mobile terminal function of the relay node and the first parent node, wherein the routing configuration includes routing utilization information, link utilization information, resource allocation information, or some combination thereof.

11. The method of claim 9, further comprising: The network management function receives a capability report from the first mobile terminal function of the relay node via the first backhaul link, wherein the capability report includes capability information of the second mobile terminal function of the relay node; The measurement configuration of the second mobile terminal functionality of the relay node is identified at least in part based on the received capability reports; as well as The network management function transmits an identified measurement configuration to the first mobile terminal function via the first backhaul link, wherein the measurement report is received based at least in part on the transmitted measurement configuration.

12. The method of claim 11, wherein the capability report includes an identifier of the second mobile terminal function, one or more radio access technologies (RATs) supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, radio frequency (RF) capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

13. An apparatus at a relay node, comprising: processor; as well as A memory coupled to the processor, wherein the processor and the memory are configured as follows: Using the first mobile terminal function of the relay node, a measurement report is transmitted to the donor central unit via a first backhaul link to the first parent node, wherein the measurement report includes measurements transmitted by the second parent node; Based at least in part on the measurement report, the backhaul link configuration of the second mobile terminal function is received via the first backhaul link using the first mobile terminal function of the relay node; as well as A second backhaul link is established between the second mobile terminal function of the relay node and the second parent node, at least in part based on the backhaul link configuration.

14. The apparatus of claim 13, wherein the processor and memory are further configured to: The system receives routing configurations for the first backhaul link and the second backhaul link, wherein the routing configurations include routing utilization information, link utilization information, resource allocation information, or some combination thereof.

15. The apparatus of claim 13, wherein the processor and memory are further configured to: The first mobile terminal function is used to transmit a capability report to the donor central unit via the first backhaul link; Based at least in part on the capability report, the measurement configuration of the relay node's second mobile terminal function is received via the first backhaul link using the relay node's first mobile terminal function; and The measurement of the second parent node's transmissions is performed using the second mobile terminal function of the relay node, at least in part, based on the measurement configuration, wherein the measurement report includes the measurement.

16. The apparatus of claim 15, wherein the capability report includes an identifier of the second mobile terminal function, one or more radio access technologies (RATs) supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, radio frequency (RF) capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

17. The apparatus of claim 13, wherein the backhaul link configuration of the second mobile terminal function includes an identifier of the second mobile terminal function of the relay node, an identifier of the second parent node, routing configuration parameters, or some combination thereof.

18. The apparatus of claim 13, wherein the first parent node and the second parent node are associated with the donor central unit, and the donor central unit comprises a next-generation Node B (gNB)-Central Unit (gNB-CU), a gNB-CU-Control Plane (gNB-CU-CP), an evolved Node B (eNB)-Central Unit (eNB-CU), an eNB-CU-Control Plane (eNB-CU-CP), or some combination thereof.

19. A device at a donor central unit, comprising: processor; as well as A memory coupled to the processor, wherein the processor and the memory are configured as follows: A measurement report is received from the first mobile terminal function of the relay node via the first backhaul link, wherein the measurement report includes measurements transmitted by the second parent node; The backhaul link configuration of the second mobile terminal function of the relay node is identified at least in part based on the measurement report; as well as The backhaul link configuration of the second mobile terminal function is transmitted to the first mobile terminal function of the relay node via the first backhaul link.

20. The apparatus of claim 19, wherein the processor and memory are further configured to: The donor central unit transmits a routing configuration for a second backhaul link between the second mobile terminal function of the relay node and the first parent node, and transmits a routing configuration for a first backhaul link between the first mobile terminal function of the relay node and the first parent node, wherein the routing configuration includes routing utilization information, link utilization information, resource allocation information, or some combination thereof.

21. The apparatus of claim 19, wherein the processor and memory are further configured to: A capability report is received from the first mobile terminal function of the relay node via the first backhaul link, wherein the capability report includes capability information of the second mobile terminal function of the relay node; The measurement configuration of the second mobile terminal function of the relay node is identified at least in part based on the capability report; as well as The measurement configuration is transmitted to the first mobile terminal function via the first backhaul link, wherein the measurement report is received based at least in part on the measurement configuration.

22. The apparatus of claim 21, wherein the capability report includes an identifier of the second mobile terminal function, one or more radio access technologies (RATs) supported by the second mobile terminal function, one or more frequency bands supported by the second mobile terminal function, azimuth and elevation modes supported by the second mobile terminal function, radio frequency (RF) capabilities of the second mobile terminal function, isolation between the first mobile terminal function and the second mobile terminal function, an identifier of the relay node, a list of supported mobile terminal functions, or some combination thereof.

23. An apparatus at a relay node, comprising a component for performing the method of any one of claims 1-8.

24. An apparatus at a donor central unit, comprising components for performing the method of any one of claims 9-12.

25. A non-transitory computer-readable medium storing code for wireless communication at a relay node, wherein the code is executable by a processor to cause the processor to perform the method of any one of claims 1-8.

26. A non-transitory computer-readable medium storing code for wireless communication at a donor central unit, wherein the code is executable by a processor to cause the processor to perform the method of any one of claims 9-12.

Images