Patent Description:
Service providers can use fiber optic cable, for example, to connect many cell sites to the core network for cellular backhaul. Wired backhauls that utilize fiber and/or copper cabling, however, are expensive and time-consuming to deploy. In many cases, such as for some rural applications, certain small cell deployments, and/or temporarily extending network capacity, it is not cost effective to deploy a wired backhaul.

<CIT> describes the establishment of integrated links comprising integrated wireless backhaul communications links and access communications links by transmitting multiplexed sync signals to enable synchronization between the relay transmission point devices, and using a random access channel procedure to complete the establishment. Backhaul communications between relay transmission points, rTPs, and access communications between user equipment (UE) and rTPs, can be integrated. For example, these communications can be multiplexed in the scheduler of an rTP, wherein the scheduler can be operable to determine resource assignments for transmissions between UEs and rTPs, and between rTPs. Typically, schedulers will assign resources based upon numerous criteria (e.g., base station throughput, user latency, fairness, etc.).

<NPL>, describes integrated access and backhaul, IAB, for New Radio, NR. Objectives of the study item include dynamic resource allocation between the backhaul and access links (RAN1, RAN2], e.g. mechanisms to efficiently multiplex access and backhaul links (for both downlink and uplink) in time, frequency or space under a per-link half-duplex constraint across one or multiple backhaul link hops for both TDD and FDD operation.

There is provided a system, a method, and a computer program according to the claims.

Accordingly there is provided a system as detailed in claim <NUM> and a method as detailed in claim <NUM>. Advantageous features are provided in the dependent claims.

Described herein are techniques and systems for providing wireless backhaul using relay nodes in a cellular network, such as a <NUM> network. The need for cellular backhaul has increased dramatically as the number of mobile devices and the use of cellular data services has increased. In many cases, cell towers may include a wired connection to provide backhaul links. For example, a cell tower may be connected to the core network using fiber optic, coaxial, or other wired connections. Deploying fiber, copper or microwave point-to-point for backhaul, however, can be expensive and time consuming.

Using techniques described herein, the higher frequency bands available in cellular networks, such as <NUM> networks, are utilized to provide both wireless backhaul links and access links. According to some configurations, a mesh of wireless nodes, such as Integrated Access and Backhaul (IAB) nodes (which may be referred to herein as "relay nodes"), are utilized to provide wireless backhaul links and access links in a <NUM> network. One or more relay nodes may be wirelessly coupled to a base station node (which may also be referred to herein as a "wired node"), such as gNodeB, that includes a wired connection to the core network. The wireless backhaul extends coverage to user equipment (UE) that are not directly connected to a gNodeB base station. The relay nodes are configured to provide wireless access to any UE that is connected. For example, a relay node may provide wireless access to each of the UEs connected to it, along with providing wireless backhaul received from one or more other relay nodes.

The relay nodes providing the wireless backhaul and access can be configured as a mesh network. In some examples, the relay nodes can be deployed in a chain configuration to provide extended coverage along a straight (or relatively straight) corridor, such as along a rural highway. In other examples, the relay nodes may be arranged to provide additional coverage within an area, such as within a city. In some cases, the relay nodes may be temporarily placed for an event, or some other occurrence.

According to some configurations, the allocation and scheduling of bandwidth may be determined by the relay nodes (i.e., IABs) and/or the wired nodes (i.e., gNodeBs). For instance, a wired node can determine how to allocate and schedule bandwidth to the connected relay nodes, whereas the relay nodes may determine how to allocate bandwidth to user equipment (UE) that is connected to the relay node. Providing both a wireless backhaul and access to UEs utilizing relay nodes, can enable operators to deploy cell sites with high capacity but without the added cost of deploying fiber, copper or conventional microwave point-to-point for backhaul. Example implementations are provided below with reference to the following figures.

<FIG> is a block diagram showing an illustrative environment <NUM> for providing wireless backhaul in a cellular network. The environment <NUM> may include a core network <NUM> and an access network <NUM> that is associated with a wireless service provider. The environment <NUM> is illustrated in simplified form and may include many more components.

The environment <NUM> may include nodes, such as relay nodes 102A, 102B and one or more wired nodes, such as wired node 104A. The environment <NUM> may also include one or more access points <NUM>, one or more gateways <NUM>, and one or more service nodes <NUM>. A relay node <NUM> and/or a wired node <NUM> may handle traffic and signals between electronic devices, such as the user equipment 110A and 110B, and a core network <NUM>. For example, a node <NUM>, <NUM> may perform the transcoding of speech channels, allocation of radio channels to electronic devices, paging, transmission and reception of voice and data, as well as other functions. A node <NUM>, <NUM> may include several base transceiver stations (BTS), each BTS may include a transceiver, antenna, and additional network switch and control equipment that provide a network cell for facilitating wireless communication between UE computing devices and the core network <NUM>. In some examples, the nodes <NUM>, <NUM> include a gNodeB and/or an eNodeB.

The core network <NUM> may be responsible for routing voice communication to other networks, as well as routing data communication to external packet switched networks, such as the Internet <NUM>. For example, the one or more service nodes <NUM> may be a Gateway GPRS Support Node (GGSN) or another equivalent node. According to some configurations, the one or more service nodes also include a Policy and Charging Rules Function (PCRF) node that utilized to enforce policy rules of the network. The PCRF node can be configured to automatically make policy decisions for each subscriber (e.g., each user equipment (UE)) active on the network. For example, the PCRF may be utilized to allocate bandwidth of the network as well as provide different levels of service to different computing devices on the network. Additionally, some data can be prioritized within the network.

The user equipment 110A and 110B are computing devices that may be a smart phone, a personal digital assistant, a netbook, a laptop computer, and/or another electronic that is capable of sending and/or receiving voice or data using a cellular access network <NUM>, and/or over a Wi-Fi network, or some other type of network. In some instances, the computing devices 110A and 110B can be configured to send and receive data using any wired or wireless protocols.

In some configurations, one or more of the service nodes <NUM> may be configured as one or more application servers that provide support for one more applications, such as application <NUM>. Some example applications include, but are not limited to browser applications, messaging applications, voice applications (e.g., Voice over Internet Protocol "VoIP" applications), video applications, and the like. While the service nodes <NUM> are illustrated within the core network <NUM>, one or more other computing devices may be located outside of the core network <NUM>. For example, an application server, or some other server or device, may be connected to the core network <NUM> via one or more external packet switched networks, such as the Internet.

According to some configurations, a telephony client application, such as application <NUM>, on the UE 110A may establish data communication with the network <NUM> through a data connection to the relay node 102B. The relay node 102B may be a node that routes a communication wirelessly from the UE 110A through the access network <NUM> to the wired node 104A for communication to the core network <NUM>.

When a communication request arrives at the network <NUM>, one or more of the service nodes <NUM> may determine the identity of the originating computing device for the communication (e.g., using a telephone number, IMEI, IMSI, IP address) as well as the identity of the computing devices to send the communication. According to some configurations, a UE 110B may connect to the service nodes <NUM>, or some other component such as an application server, via the Internet <NUM>. In such instances, the UE 110B may connect to the Internet <NUM> via Wi-Fi access point <NUM>. Accordingly, data traffic from the UE 110B may be routed to the service nodes <NUM> by the gateway <NUM> of the network <NUM>.

In some configurations, a wireless service provider may utilize alternative access vendor (AAV) networks, for example, which utilize Ethernet networks to provide a wired connection, such as wired connection <NUM>, to provide at least a portion of backhaul for broadband cellular services, such as <NUM> networks. In other examples, the wireless service provider may deploy its own wired connections.

In general, a node, such as relay nodes <NUM> and wired nodes <NUM> can be implemented as a variety of technologies to provide wired and/or wireless access to the network, as discussed herein. In some instances, the nodes <NUM>, <NUM> can include a 3GPP RAN, such a GSM/EDGE RAN (GERAN), a Universal Terrestrial RAN (UTRAN), an evolved UTRAN (E-UTRAN), or a New Radio (<NUM>) RAN, or alternatively, a "non-3GPP" RAN, such as a Wi-Fi RAN, or another type of wireless local area network (WLAN) that is based on the IEEE <NUM> standards. Further, the nodes <NUM>, <NUM> can include any number and type of transceivers and/or base stations representing any number and type of macrocells, microcells, picocells, or femtocells, for example, with any type or amount of overlapping coverage or mutually exclusive coverage. The nodes <NUM>, <NUM> can be associated with access network <NUM>.

In some instances, the environment <NUM> can further include one or more servers, including service nodes <NUM>, to facilitate communications by and between the various devices in the environment <NUM>. That is, environment <NUM> can include any computing devices implementing various aspects of one or more of second, third, fourth generation, and fifth generation (<NUM>, <NUM>, <NUM>, and <NUM>) cellular-wireless access technologies, which may be cross-compatible and may operate collectively to provide data communication services. Global Systems for Mobile (GSM) is an example of <NUM> telecommunications technologies; Universal Mobile Telecommunications System (UMTS) is an example of <NUM> telecommunications technologies; and Long Term Evolution (LTE), including LTE Advanced, Evolved High-Speed Packet Access (HSPA+) are examples of <NUM>, and <NUM> NR is an example of <NUM> telecommunications technologies. Thus, the environment <NUM> may implement GSM, UMTS, LTE/LTE Advanced, and/or <NUM> NR telecommunications technologies.

The environment <NUM> may include, but is not limited to, a combination of: base transceiver stations BTSs (e.g., NodeBs, Enhanced-NodeBs, gNodeBs), Radio Network Controllers (RNCs), serving GPRS support nodes (SGSNs), gateway GPRS support nodes (GGSNs), proxies, a mobile switching center (MSC), a mobility management entity (MME), a serving gateway (SGW), a packet data network (PDN) gateway (PGW), an evolved packet data gateway (e-PDG), an Internet Protocol (IP) Multimedia Subsystem (IMS), or any other data traffic control entity configured to communicate and/or route data packets between the user equipment <NUM>, the nodes <NUM>, <NUM>, and one or more endpoints of the network (e.g., service nodes <NUM>, websites, etc.). While <FIG> illustrates an example environment <NUM>, it is understood in the context of this document, that the techniques discussed herein may also be implemented in other networking technologies.

The access network <NUM> can be any sort of access network, such as a GSM or UMTS network. The access network <NUM> can include any aspects of one or more of second, third, fourth generation, and fifth generation (<NUM>, <NUM>, <NUM>, and <NUM>) cellular-wireless access technologies. The access network <NUM> can also be referred to as a universal terrestrial radio network (UTRAN) or a GSM EDGE radio access network (GERAN) and can include one or base stations, as well as a radio network controller (RNC).

Examples of the user equipment (UE) <NUM> can include, but are not limited to, smart phones, mobile phones, cell phones, tablet computers, portable computers, laptop computers, personal digital assistants (PDAs), electronic book devices, or any other portable electronic devices that can generate, request, receive, transmit, or exchange voice, video, and/or digital data over a network. Additional examples of the UE <NUM> include, but are not limited to, smart devices such as televisions, music players, or any other electronic appliances that can generate, request, receive, transmit, or exchange voice, video, and/or digital data over a network.

The UE <NUM> can further be configured to establish or receive a communication session, such as a VoLTE, VoNR, VoWifi, or other voice call, a video call, or another sort of communication. Establishment of such sessions can involve communication clients and Session Initiation Protocol (SIP) clients to communicate with the telecommunications network.

As shown in <FIG>, some base stations, such as relay nodes 102A and 102B, have no physical (i.e., "wired") data connection to network. In other words, relay nodes <NUM> are not connected to the core network <NUM> using fiber cabling, copper cabling, and/or some other type of wired connection.

As illustrated, the relay nodes 102A and 102B are connected to one or more wired nodes <NUM>, such as node <NUM>, that does have a wired connection to the core network <NUM>. A wired node utilizes fiber, or other wired data connections, to connect to the core network <NUM>. As shown, wired node 104A connects to the core network via an Ethernet connection <NUM> via a fiber optic, coaxial, or other high speed wired data connection. A wired node <NUM> could also be connected by a coaxial, T1, T3, or other suitable high-speed connection to the core network <NUM>.

Regardless of the connection type, however, changing a relay node <NUM> to a wired node may involve installing a new cable, fiber, satellite dish, microwave transceiver, or other equipment, and can involve considerable cost and time. The cost of installation of a wired backhaul connection can vary widely based on the distance from the relay node <NUM> to the network <NUM>, for example, where longer distances may require the installation of longer cables or more powerful transceivers, for example. Installation costs may also vary due to the terrain at the relay node <NUM>. Installation in mountainous locations, for example, may be much more expensive than an installation on flat ground or in a city.

In some configurations, mesh networking technology can be used to connect different nodes within the access network <NUM>. Geographic Information Services (GIS) and other terrain and location information systems can be used to determine nodes to provide a connection between one or more non-connected sites <NUM> and a network <NUM>. As discussed in more detail below, different techniques can be utilized to determine backhaul paths and access paths between the nodes <NUM> and <NUM>.

As illustrated in <FIG>, the higher frequency bands available in <NUM> networks are utilized to provide both wireless backhaul links <NUM> between relay nodes <NUM> and wired nodes <NUM> and access links to connected UEs. According to some configurations, the nodes <NUM>, and <NUM> form a mesh of wireless nodes that include Integrated Access and Backhaul (IAB) nodes ("relay nodes"), and gNodeB nodes <NUM> ("wired nodes") that includes a wired connection <NUM> to the core network <NUM>. The relay nodes <NUM> extend coverage to user equipment (UE) <NUM> that are not directly connected to a wired node <NUM>. Sharing the wireless channel of a relay node <NUM> to provide wireless access to connected UEs, and a wireless backhaul can enable cellular service provider to deploy cell sites with high capacity but without the added cost of deploying fiber, copper or conventional microwave point-to-point for backhaul
According to some configurations, the allocation and scheduling of bandwidth between the different nodes <NUM>, <NUM> may be determined using one or more of the relay nodes <NUM> and/or the wired nodes <NUM>. For instance, a wired node <NUM> can be configured to determine how to allocate and schedule bandwidth to the connected relay nodes <NUM>, whereas the relay nodes <NUM> may determine how to allocate bandwidth to user equipment (UE) that is connected to the relay node. In other examples, the wired node may determine the allocation and scheduling for each of the relay nodes <NUM>. In yet other examples, the distribution of allocating and/or scheduling the available bandwidth can be split differently among the nodes. The allocation of bandwidth and/or routing the data through the nodes <NUM>, <NUM> can be determined using different techniques.

Some techniques include but are not limited to a Minimum Spanning Tree (MST) technique, an Adaptive Graph Minimum Spanning Tree Algorithm (AG-MST) technique, and the like. Generally, MST or AG-MST can be utilized by one or more of the nodes <NUM>, <NUM> to select the nodes to utilize for wireless access links <NUM> and wireless backhaul links <NUM> between the UE 110A and the wire node 104A.

The nodes of the graph utilized in MST and/or AG-MST can be represented by the different nodes <NUM>, <NUM> within environment <NUM>. Some of the paths between the nodes <NUM>, <NUM> be considered more expensive, because they are longer, do not have as much available bandwidth, and the like. These paths may be represented by edges with larger weights.

A spanning tree for the graph which includes the vertices of the graph, with the minimum possible number of edges. In general, a graph may have several spanning trees. A minimum spanning tree is the route between the nodes with the lowest total cost. This information can be used to identify and select the different relay nodes <NUM> that can act as relays to the wired connection <NUM>.

In some configurations, the wired node <NUM> identifies the relay nodes <NUM> that are coupled to the wired node and the UEs <NUM> that are coupled to the relay nodes. According to some examples, a relay node <NUM> may determine and provide the number of UEs <NUM> that are connected to it to the wired node <NUM>. For instance, relay node 102B may transmit to wired node 104A that one UE 110A is connected. This data may be utilized to assist in determining how much available bandwidth is available to provide wireless backhaul links <NUM> and access links by a particular relay node. More details are provided below with regard to <FIG>.

<FIG> is a diagram showing an illustrative environment of relay nodes providing wireless backhaul in a cellular network. As illustrated, environment <NUM> includes wired nodes 104A, and 104B, relay nodes 102A - 102E, and UEs 110A - <NUM>. As discussed above, the scheduling an allocation of bandwidth between a UE <NUM> and a wired node <NUM> can be determined by a single node, such as one or more wired nodes <NUM>, one more relay nodes <NUM>, and/or some other component or device or by some combination of nodes. In some configurations, a wired node <NUM> that is coupled to a UE may be used to perform the scheduling an allocation of bandwidth.

As an example, wired node 104A may be configured to determine the scheduling an allocation of bandwidth between UE 110A and wired node 104A. In the current example, wired node 104A may determine the relay nodes <NUM> to utilize for providing the wireless backhaul links <NUM> and the access links <NUM>. As discussed above, the wired node 104A may use one or more techniques (e.g., MST) to select the relay nodes <NUM> to utilize.

The different techniques to determine the path through the mesh can be selected based on available bandwidth of a link, forecasted usage of the link, and the like. In the current example, the wired node 104A selected relay nodes 102B and 102C to provide wireless backhaul <NUM> for UE 110D. The selection of the relay nodes utilized may change over time depending on network conditions, and other factors. For example, if more UEs <NUM> connected to relay node 102B, and/or 102C, a different path using one or more different relay nodes <NUM> may be selected. In some configurations, in addition to determining a path through the mesh, one or more nodes, such as the wired node 104A, determines how to allocate the available bandwidth between the wireless backhaul links <NUM> and the wireless access links <NUM>. For instance, the determination can be based on past usage of the wireless channel, current usage of the wireless channel, and/or future usage of the wireless channel.

<FIG> is a diagram showing illustrative arrangements of relay nodes for providing wireless backhaul in a cellular network. As illustrated, <FIG> shows a first configuration <NUM> of relay nodes 102A, 102B, 102C coupled to a wired node 104A, and a second configuration <NUM> of relay nodes 102D, and 102E coupled to wired node 104B.

The signals of the microwave and millimeter bands associated with <NUM> networks travel along sight lines, but also spread as they propagate. As a result, both the linear, or visual, line-of-sight (LoS), and the area covered by the signal are of significance. The area that the signal covers as it spreads out is referred to as the Fresnel zone, which is generally required to be clear and free of obstructions to be considered true LoS.

When positioning relay nodes <NUM>, pathways between the nodes <NUM>, <NUM> may be selected to minimize obstructions. The obstructions can be, for example, trees, mountains, buildings, or other large objects that substantially block the propagation of a signal. A relay node <NUM> may be positioned such that LoS locations have both an unobstructed linear pathway between nodes and an unobstructed Fresnel zone. In other examples, it may not be possible to position relay nodes <NUM> to avoid at least some of the obstructions. For example, some relay nodes <NUM> may have an unobstructed linear pathway, but a Fresnel zone that is at least partially obstructed.

One or more relay nodes <NUM> can be located on third-party infrastructure, such as, for example, third-party buildings, towers, and trees. The relay nodes may be positioned to improve the LoS. In some examples, more than one relay node <NUM>, can be installed at a same location.

As shown in <FIG>, configuration <NUM> illustrates a mesh of relay nodes 102A, 102B and 102C at different locations relative to a hill <NUM> and wired node 104A. In this example, UE 110A may be coupled to wired node 104A using a combination of relay node 102C, 102A and/or 102B. In other words, more than one path through the relay nodes <NUM> may be utilized to provide access links <NUM> and/or wireless backhaul links <NUM>.

Configuration <NUM> illustrates relay nodes 102D, and 102E connected to wired node 104B and UE 110B. In configuration <NUM>, a single path using relay nodes 102D and 102E coupled UE 110B to the wired node 104B. As discussed herein, the relay nodes <NUM> providing the wireless backhaul links <NUM> and the access links <NUM> can be configured in a variety of configurations.

<FIG> is a block diagram illustrating a system <NUM> that includes an allocation and bandwidth allocation/scheduling module <NUM> for identifying relay nodes <NUM> and allocating/scheduling bandwidth for wireless access links <NUM> and wireless backhaul links <NUM> in a cellular network according to some examples. The system <NUM> includes a computing device <NUM>, which can represent relay nodes <NUM>, and/or wired nodes <NUM>, of <FIG>, <FIG>, <FIG> coupled to computing device <NUM>, via a network <NUM>. The computing device <NUM> can represent one or more of the service nodes <NUM>, a relay node <NUM> and/or a wired node <NUM>. The network <NUM> can represent, e.g., networks <NUM>, <NUM> or <NUM>.

The network <NUM> can include one or more core network(s) <NUM> connected to nodes <NUM>, <NUM> via one or more access network(s), such as access network <NUM>. Example access networks include <NUM> NR, LTE, WIFI, GSM Enhanced Data Rates for GSM Evolution (EDGE) Radio Access Network (GERAN), UTRAN, and other cellular access networks. Message transmission, reception, fallback, and deduplication as described herein can be performed, e.g., via <NUM>, <NUM>, <NUM>, WIFI, or other networks.

The cellular network <NUM> can provide wide-area wireless coverage using a technology such as GSM, Code Division Multiple Access (CDMA), UMTS, LTE, <NUM> NR, or the like. Example networks include Time Division Multiple Access (TDMA), Evolution-Data Optimized (EVDO), Advanced LTE (LTE+), Generic Access Network (GAN), Unlicensed Mobile Access (UMA), Orthogonal Frequency Division Multiple Access (OFDM), GPRS, EDGE, Advanced Mobile Phone System (AMPS), High Speed Packet Access (HSPA), evolved HSPA (HSPA+), VoIP, VoLTE, IEEE <NUM>. 1x protocols, wireless microwave access (WIMAX), WIFI, and/or any future IP-based network technology or evolution of an existing IP-based network technology.

The data network <NUM> can include various types of networks for transmitting and receiving data (e.g., data packets), including networks using technologies such as WIFI, IEEE <NUM>. <NUM> ("BLUETOOTH"), Asynchronous Transfer Mode (ATM), WIMAX, and other network technologies, e.g., configured to transport IP packets. In some examples, the computing device <NUM> includes or is communicatively connected with an IWF or other device bridging networks, e.g., <NUM>, LTE, <NUM>, and POTS networks. In some examples, the computing device <NUM> can bridge SS7 traffic from the PSTN into the network <NUM>, e.g., permitting PSTN customers to place calls to cellular customers and vice versa.

In some examples, the cellular network <NUM> and the data network <NUM> can carry voice or data. For example, the data network <NUM> can carry voice traffic using VoIP or other technologies as well as data traffic, or the cellular network <NUM> can carry data packets using HSPA, LTE, <NUM> NR, or other technologies as well as voice traffic. Some cellular networks <NUM> carry both data and voice in a packet-switch (PS) format. For example, many LTE networks carry voice traffic in data packets according to the VoLTE standard. Various examples herein provide origination and termination of, e.g., carrier-grade voice calls on, e.g., networks <NUM> using circuit-switching (CS) transports or mixed VoLTE/<NUM> transports, or on computing device <NUM> including OEM handsets and non-OEM handsets.

The computing device <NUM> can include one or more processors <NUM>, e.g., one or more processor devices such as microprocessors, microcontrollers, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), programmable logic devices (PLDs), programmable logic arrays (PLAs), programmable array logic devices (PALs), or digital signal processors (DSPs), and one or more computer readable media (CRM) <NUM>, such as memory (e.g., random access memory (RAM), solid state drives (SSDs), or the like), disk drives (e.g., platter-based hard drives), another type of computer-readable media, or any combination thereof. The CRM or other memory of computing device <NUM> can hold a datastore, e.g., an SQL or NoSQL database, a graph database, a BLOB, or another collection of data. The computing device <NUM> can further include a user interface (UI) <NUM>, e.g., including an electronic display device, a speaker, a vibration unit, a touchscreen, or other devices for presenting information to a user and receiving commands from a user. The computing device <NUM> can further include one or more network interface(s) <NUM> configured to selectively communicate (wired or wirelessly) via the network <NUM>, e.g., via an access network <NUM> or <NUM>, <NUM>.

The CRM <NUM> can be used to store data and to store instructions that are executable by the processors <NUM> to perform various functions as described herein. The CRM <NUM> can store various types of instructions and data, such as an operating system, device drivers, etc. The processor-executable instructions can be executed by the processors <NUM> to perform the various functions described herein.

The CRM <NUM> can be or include computer-readable storage media. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other tangible, non-transitory medium which can be used to store the desired information and which can be accessed by the processors <NUM>. Tangible computer-readable media can include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program components, or other data.

The CRM <NUM> can include processor-executable instructions of a bandwidth allocation/scheduling module 432B. The bandwidth allocation/scheduling module 432B, can be configured to perform functionality relating to providing wireless backhaul in a cellular network, such as a <NUM> network. The CRM <NUM> can also store other modules <NUM> configured to perform other functionality.

The computing device <NUM> can include one or more processors <NUM> and one or more CRM <NUM>. The CRM <NUM> can be used to store processor-executable instructions of a bandwidth allocation/scheduling module 432A, as well as one or more other components <NUM>. In some configurations, the computing device <NUM> can be configured as a service node <NUM>, some other service node, and the like. The processor-executable instructions can be executed by the one or more processors <NUM> to perform various functions described herein, e.g., with reference to <FIG>.

In some examples, computing device <NUM> can communicate with (e.g., is communicatively connectable with) computing device <NUM> or other devices via one or more communications interface(s) <NUM>, e.g., network transceivers for wired or wireless networks, or memory interfaces. Example communications interface(s) <NUM> can include ETHERNET or FIBRE CHANNEL transceivers, WIFI radios, or DDR memory-bus controllers (e.g., for DMA transfers to a network card installed in a physical server <NUM>).

In some examples, processor <NUM> and, if required, CRM <NUM>, are referred to for brevity herein as a "control unit. " For example, a control unit can include a CPU or DSP and instructions executable by that CPU or DSP to cause that CPU or DSP to perform functions described herein. Additionally, or alternatively, a control unit can include an ASIC, FPGA, or other logic device(s) wired (physically or via blown fuses or logic-cell configuration data) to perform functions described herein. Other examples of control units can include processor <NUM> and, if required, CRM <NUM>.

<FIG> illustrates an example user equipment (UE) <NUM> configured to connect to a relay node that provides wireless backhaul in a cellular network. In some embodiments, the UE <NUM> can correspond to the UE <NUM> of <FIG>. It is to be understood in the context of this disclosure that the UE <NUM> can be implemented as a single device or as a plurality of devices with components and data distributed among them.

As illustrated, the UE <NUM> comprises a memory <NUM> storing the communication component <NUM>, a session initiation protocol (SIP) component <NUM>, an application component <NUM>, an authentication component <NUM>, and other components <NUM>. Also, the UE <NUM> includes processor(s) <NUM>, a removable storage <NUM> and non-removable storage <NUM>, input device(s) <NUM>, output device(s) <NUM>, and transceiver(s) <NUM>.

In various embodiments, the memory <NUM> is volatile (such as RAM), non-volatile (such as ROM, flash memory, etc.) or some combination of the two. The communication component <NUM>, the SIP component <NUM>, the application component <NUM>, the authentication component <NUM>, and the other components <NUM> stored in the memory <NUM> can comprise methods, threads, processes, applications, or any other sort of executable instructions. The communication component <NUM>, the SIP component <NUM>, the application component <NUM>, the authentication component <NUM>, and the other components <NUM> can also include files and databases.

The communication component <NUM> may include functionality to send and receive communication (e.g., a voice call, an SMS, or an MMS) and/or perform other operations. In some examples, the communication component <NUM> may perform a number of functions, such as interfacing with the transceiver(s) <NUM>, preparing the user equipment <NUM> to receive or handover a call, tuning the transceiver(s) <NUM>, receiving and processing an invitation message such as a SIP Message received via the transceiver(s) <NUM>, transmitting other messages via the transceiver(s) <NUM>, detecting a failure condition, and the like.

The SIP component <NUM> may be an application that enables calls to be served via Voice over Internet Protocol (VoIP) using Session Initiation Protocol (SIP) signaling. The SIP component <NUM> may determine a current location of the user equipment <NUM> using a Global Positioning System (GPS).

The application component <NUM> may display various information associated with a communication session. The application component <NUM> may provide a portal for the user to sign up for services with a service provider. In various examples, the application component <NUM> may provide an interface for the user(s) to register new user accounts and download one or more applications associated with the service provider, such as the authentication component <NUM>. The application component <NUM> may communicate with servers of the service provider for the user equipment(s) <NUM> through the communication component <NUM> to receive or update user settings.

The authentication component <NUM> may perform various types of authentication. The authentication component <NUM> may interact with the database(s) to store, retrieve, and update the database(s) containing user subscription information, including items such as user identification and addressing (e.g., the IMSI (International Mobile Subscriber Identity) and MSISDN (Mobile Subscriber ISDN Number)), user profile information (e.g., subscription data). The authentication component <NUM> may also be configured to perform other operations.

The authentication component <NUM> may authenticate the UE <NUM> to send and receive communication using a user account. The other components <NUM> may perform other operations. In some embodiments, the processor(s) <NUM> is a central processing unit (CPU), a graphics processing unit (GPU), or both CPU and GPU, or other processing unit or component known in the art.

The UE <NUM> also includes additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in <FIG> by removable storage <NUM> and non-removable storage <NUM>. Tangible computer-readable media can include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data. The memory <NUM>, the removable storage <NUM> and the non-removable storage <NUM> are all examples of computer-readable storage media. Computer-readable storage media include, but are not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile discs (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information, and which can be accessed by the UE <NUM>. Any such tangible computer-readable media can be part of the UE <NUM>.

The UE <NUM> can include input device(s) <NUM>, such as a keypad, a cursor control, a touch-sensitive display, etc. Also, the UE <NUM> can include output device(s) <NUM>, such as a display, speakers, etc. These devices are well known in the art and need not be discussed at length here.

As illustrated in <FIG>, the UE <NUM> can include one or more wired or wireless transceiver(s) <NUM>. In some wireless embodiments, to increase throughput, the transceiver(s) <NUM> can utilize multiple-input/multiple-output (MIMO) technology. The transceiver(s) <NUM> can be any sort of wireless transceivers capable of engaging in wireless, radio frequency (RF) communication, as discussed herein. The transceiver(s) <NUM> can also include other wireless modems, such as a modem for engaging in Wi-Fi, WiMAX, Bluetooth, infrared communication, or the like.

<FIG> illustrates an example process <NUM> in accordance with embodiments of the disclosure. The process is illustrated as a logical flow graph, each operation of which represents a sequence of operations that can be implemented in hardware, software, or a combination thereof. In the context of software, the operations represent computer-executable instructions stored on one or more computer-readable storage media that, when executed by one or more processors, perform the recited operations. Generally, computer-executable instructions include routines, programs, objects, components, data structures, and the like that perform particular functions or implement particular abstract data types. The order in which the operations are described is not intended to be construed as a limitation, and any number of the described operations can be combined in any order and/or in parallel to implement the processes.

<FIG> illustrates an example process for using relay nodes to provide wireless backhaul in a cellular network. The example process <NUM> can be performed by one or more of the relay nodes <NUM>, the wired nodes <NUM>, the computing device <NUM>, computing device <NUM>, the service nodes <NUM>, or one or more other components, in connection with other components discussed herein. Some or all of the process <NUM> can be performed by one or more devices, equipment, or components illustrated in <FIG>, for example.

At <NUM>, relay nodes <NUM> and user equipment (UE) devices <NUM> coupled to the wired node <NUM> are determined. As discussed above, the relay nodes <NUM> may be IAB nodes and the wired nodes may be gNodeB nodes. In some examples, the nodes <NUM>, <NUM> operate in a <NUM> network that utilize one or more of a centimeter wave band or a millimeter wave bands. In some examples, the processors of the wired node <NUM> are configured to determine the coupled relay nodes and UE <NUM>. In other examples, processors of one or more of the relay nodes <NUM> can be utilized.

At <NUM>, after identifying the coupled relay nodes <NUM> and the UE devices <NUM>, the allocation of bandwidth between access links <NUM> and backhaul links <NUM> is determined. As discussed above, different techniques can be utilized to determine the allocation and scheduling. For examples, a MST can be utilized to determine a path using the available relay nodes <NUM>. Generally, the techniques are utilized to select the relay nodes <NUM> to couple a UE <NUM> to a wired node <NUM>.

At <NUM>, the one or more wireless access links between the wired node and one or more of the UE devices are established. As discussed above, different relay nodes <NUM> can be utilized to provide the backhaul links <NUM> between the UE <NUM> and a wired node <NUM>.

At <NUM>, the one or more wireless backhaul links between the wired node base station and one or more of the relay nodes is established. As discussed above, different relay nodes <NUM> can be utilized to provide the wireless backhaul links <NUM> between the UE <NUM> and a wired node <NUM>.

At <NUM>, the one or more wireless access links <NUM> and the one or more backhaul links <NUM> are utilized to communicate with a UE device <NUM>. As discussed above, the links may change over time depending on various network conditions and/or other criteria.

Claim 1:
A system (<NUM>) comprising:
one or more processors (<NUM>) of a fifth generation, <NUM>, base station that uses one or more of a centimeter wave band or a millimeter wave band for communication; and
programming instructions (<NUM>) configured to be executed by the one or more processors to perform operations comprising:
identifying relay nodes (<NUM>) and user equipment, UE, devices (<NUM>) wirelessly coupled to the <NUM> base station (<NUM>), wherein a first relay node (102A, 102D, 102E) of the relay nodes is connected to the <NUM> base station and a second relay node (102B, 102C) of the relay nodes is connected to the first relay node;
allocating, based at least in part on the identifying the relay nodes and the UE devices, a first portion of bandwidth for respective wireless access links between the <NUM> base station and the UE devices and a second portion of the bandwidth for respective wireless backhaul links between the <NUM> base station and the first relay node and between the first relay node and the second relay node;
establishing the respective wireless access links (<NUM>) between the <NUM> base station and one or more of the UE devices;
establishing the respective wireless backhaul links (<NUM>) between the <NUM> base station and the first relay node and between the first relay node and the second relay node; and
utilizing the respective wireless access links to communicate with the one or more of the UE devices, and the backhaul links to communicate with the first and second relay nodes;
wherein at least a portion of the relay nodes form a mesh network; and
wherein the identifying relay nodes comprises determining a path from the <NUM> base station through the mesh network of relay nodes and the second portion of the bandwidth is allocated for the wireless backhaul links of the path.