METHOD AND SYSTEM FOR INTEGRATED ACCESS BACKHAUL SHARING AMONG CO-LOCATED RADIO SITES

A method, a network device, and a non-transitory computer-readable storage medium are described in relation to an IAB backhaul sharing among co-located radio sites service. The IAB backhaul sharing among co-located radio sites service may include a traffic balancing service that performs access link bandwidth management and allocation to integrated access and backhaul (IAB) nodes based on bandwidth assessment of IAB backhaul links and bandwidth demands of IAB nodes. The service may further include a scheduling service that includes localized scheduling and load balancing at each IAB node of user traffic based on an allocated bandwidth provided by the traffic balancing service. The scheduling service may include an integrated schedule between co-located radio sites associated with the IAB node.

BACKGROUND

Development and design of networks present certain challenges from a network-side perspective and an end device perspective. For example, Next Generation (NG) wireless networks, such as Fifth Generation New Radio (5G NR) networks are being deployed and are under development. An implementation for a radio access network (RAN) deployment, transport between distributed units (DUs) and radio units (RUS), as well as centralized units (CUs) at transport access points (TAPs) and/or service access points (SAPs) include optical connections.

DETAILED DESCRIPTION

IAB provides a backhaul solution for radio sites where wireline backhaul may not be reachable or may be cost prohibitive. An IAB deployment may operate in millimeter wave (mmWave) bands that provide greater bandwidth in comparison to Fourth Generation (4G) or 5G frequency division duplex (FDD) low band and mid band. Current IAB solutions may enable sharing of the backhaul with geographically co-located low band and mid band radio sites. For example, a sub-6 gigahertz (GHz) next generation Node B (gNB) may be co-located with a mmWave IAB node, which backhauls both mmWave and C-band traffic to an IAB donor node with fiber point-of-presence (POP). A point-to-multipoint mmWave deployment may also enable multiple sub-6 GHz sites to be backhauled with a single mmWave IAB donor node, for example. An IAB device, as used herein, may refer to an IAB node, an IAB donor node, IAB donor DU node, IAB donor DU/RU node, or the like.

Despite the notable advantages associated with an IAB deployment, there are problems regarding how to manage end user traffic pertaining to different frequency bands or cells in a manner that optimizes the backhaul usage of a site when at least some users may have wireless service via multiple frequency bands or cells. Typical load balancing algorithms, which try to equalize the load on each frequency, cannot be employed as such algorithms assume that all radios have independent and unlimited optical fiber backhaul. For example, a first frequency (e.g., mmWave) cell of an IAB device may be allocated to only the backhaul, and all user traffic may be supported by a second frequency (e.g., sub-6 GHz) cell of a gNB. According to another example, the first frequency cell may support all the user traffic it can without limitation, and only left over capacity is used for backhauling user traffic of the second frequency cell. In either case, these backhaul sharing arrangements yield sub-optimal results.

Additionally, there are other problems regarding backhaul usage and IAB deployments. For example, with shared backhaul links, there are challenges as to how backhaul links are shared by the IAB devices along an IAB network route, path, or relay chain. Any viable solution to this problem should maximize the backhaul links utilization while supporting the bandwidth and service demands from the users at each radio site.

According to exemplary embodiments, an IAB backhaul sharing among co-located radio sites service is described. According to an exemplary embodiment, the IAB backhaul sharing among co-located radio sites service provides access link bandwidth management and allocation for a set of co-located radio sites based on a bandwidth assessment of IAB backhaul links, bandwidth demands provided by each co-located radio sites, and a maximum access bandwidth allotted to each co-located radio sites. According to an exemplary embodiment, the IAB backhaul sharing among co-located radio sites service may perform scheduling and load balancing pertaining to each radio site associated with the co-located radio sites and the IAB backhaul link based on the allotted maximum access bandwidth.

According to an exemplary embodiment, the co-located radio sites may include a wireless station (e.g., a DU and an RU) or a different set of split radio access components as described herein) and an IAB device (e.g., an RU, an IAB Mobile Termination (MT) antenna, and/or another set of radio access components, as described herein). According to an exemplary embodiment, each co-located radio sites may support two or more frequency bands, carriers, cells, or the like, as described herein.

According to an exemplary embodiment, the IAB backhaul sharing among co-located radio sites service may perform access link bandwidth management and allocation according to a centralized architecture. For example, a traffic balancer may include logic of a traffic balancing service included in the IAB backhaul sharing among co-located radio sites service. According to various exemplary embodiments, the traffic balancer may be implemented in a radio intelligent controller (RIC) device, an IAB donor DU node, an IAB donor node, or similar functioning RAN device, as described herein.

According to an exemplary embodiment, the IAB backhaul sharing among co-located radio sites service may perform scheduling and load balancing between the co-located radios. For example, each co-located radio sites or IAB device may include a scheduler. The scheduler may include logic of a scheduling service included in the IAB backhaul sharing among co-located radio sites service. For example, the scheduler may perform scheduling and load balancing regarding access to and use of the IAB backhaul based on an assigned or permitted maximum access link bandwidth provided by the traffic balancer.

According to an exemplary embodiment, the scheduler may assess backhaul bandwidth associated with an IAB link and the co-located radio sites. The scheduler may also assess capacity demands associated with the co-located radio sites. According to an exemplary embodiment, the scheduler may consider various factors pertaining to access capacity demands, such as number of users, the connections associated with the frequency bands, radio frequency conditions, spectral efficiency, and the like. Each scheduler may provide the traffic balancer with backhaul bandwidth and capacity demands. Based on the bandwidth and access demand assessment values, the traffic balancer may calculate and allocate the maximum access bandwidth for each co-located radio site. According to an exemplary embodiment, the traffic balancer may consider various factors, such as network topology, radio site efficiency, radio site cluster efficiency, bandwidth history, day and/or time, and/or other types of context information, as described herein, when calculating the maximum access bandwidth.

According to an exemplary embodiment, the scheduler may perform cross-frequency band, cross-user scheduling and load balancing based on the maximum access bandwidth allocated by the traffic balancer, as described herein. According to an exemplary embodiment, the scheduler may determine whether a total bandwidth demand exceeds the allotted maximum access bandwidth. According to an exemplary embodiment, the scheduler may determine whether traffic of users associated with a first frequency band may be reconfigured for scheduling with traffic of users associated with a second frequency band based on service level agreement (SLA) requirements, as described herein. According to an exemplary embodiment, the scheduler may suspend scheduling of traffic of lower priority users when the total bandwidth demand exceeds the allocated maximum access bandwidth.

In view of the foregoing, the IAB backhaul sharing among co-located radio sites service may improve backhaul link utilization, scheduling, and load balancing among co-located radio sites. The IAB backhaul sharing among co-located radio sites service may manage access and use of a shared backhaul for co-located radio sites.

FIG.1is a diagram illustrating an exemplary environment100in which an exemplary embodiment of an IAB backhaul sharing among co-located radio sites service may be implemented. As illustrated, environment100includes an access network105, backhaul network110, an external network115, and a core network120. Access network105includes access devices107(also referred to individually or generally as access device107). Backhaul network110includes transport devices112(also referred to individually or generally as transport device112). External network115includes external devices117(also referred to individually or generally as external device117). Core network120includes core devices122(also referred to individually or generally as core device122). Environment100further includes end devices130(also referred to individually or generally as end device130).

The number, type, and arrangement of networks illustrated in environment100are exemplary. For example, according to other exemplary embodiments, environment100may include fewer networks, additional networks, and/or different networks. For example, according to other exemplary embodiments, other networks (e.g., fronthaul, mid-haul, etc.) not illustrated inFIG.1may be included that may support a wireless service and/or an application service, as described herein.

A network device, a network element, or a network function (referred to herein simply as a network device) may be implemented according to one or multiple network architectures, such as a client device, a server device, a peer device, a proxy device, a cloud device, and/or a virtualized network device. Additionally, a network device may be implemented according to various computing architectures, such as centralized, distributed, cloud (e.g., elastic, public, private, etc.), edge, fog, and/or another type of computing architecture, and may be incorporated into distinct types of network architectures (e.g., Software Defined Networking (SDN), client/server, peer-to-peer, etc.) and/or implemented with various networking approaches (e.g., logical, virtualization, network slicing, etc.). The number, the type, and the arrangement of network devices are exemplary.

Environment100includes communication links between the networks and between the network devices. Environment100may be implemented to include wired, optical, and/or wireless communication links. A communicative connection via a communication link may be direct or indirect. For example, an indirect communicative connection may involve an intermediary device and/or an intermediary network not illustrated inFIG.1. A direct communicative connection may not involve an intermediary device and/or an intermediary network. The number, type, and arrangement of communication links illustrated in environment100are exemplary.

Environment100may include various planes of communication including, for example, a control plane, a user plane, a service plane, and/or a network management plane. Environment100may include other types of planes of communication. A message communicated in support of the IAB backhaul sharing among co-located radio sites service may use at least one of these planes of communication.

Access network105may include one or multiple networks of one or multiple types and technologies. For example, access network105may be implemented to include a 5G RAN, a future generation RAN (e.g., a Sixth Generation (6G) RAN, a Seventh Generation (7G) RAN, or a subsequent generation RAN), a centralized-RAN (C-RAN), an Open-RAN (O-RAN), a cloud RAN, a virtualized RAN (vRAN), a self-organizing network (SON), an IAB network, and/or another type of access network. Access network105may include a legacy RAN (e.g., a Third Generation (3G) RAN, a 4G or 4.5 RAN, etc.). Access network105may communicate with and/or include other types of access networks, such as, for example, a Wi-Fi network, a Worldwide Interoperability for Microwave Access (WiMAX) network, a local area network (LAN), a Citizens Broadband Radio System (CBRS) network, a wired network (e.g., optical, cable, etc.), or another type of network that provides access to or can be used as an on-ramp to access network105.

Access network105may include different and multiple functional splitting, such as options 1, 2, 3, 4, 5, 6, 7, or 8 that relate to combinations of access network105and core network120including an Evolved Packet Core (EPC) network and/or an NG core (NGC) network, or the splitting of the various layers (e.g., physical layer, media access control (MAC) layer, radio link control (RLC) layer, and packet data convergence protocol (PDCP) layer, etc.), plane splitting (e.g., user plane, control plane, etc.), interface splitting (e.g., F1-U, F1-C, E1, Xn-C, Xn-U, X2-C, Common Public Radio Interface (CPRI), enhanced CPRI (eCPRI), etc.) as well as other types of network services, such as dual connectivity (DC) or higher (e.g., a secondary cell group (SCG) split bearer service, a master cell group (MCG) split bearer, an SCG bearer service, non-standalone (NSA), standalone (SA), etc.), carrier aggregation (CA) (e.g., intra-band, inter-band, contiguous, non-contiguous, etc.), edge and core network slicing, coordinated multipoint (COMP), various duplex schemes (e.g., frequency division duplex (FDD), time division duplex (TDD), half-duplex FDD (H-FDD), etc.), and/or another type of connectivity service (e.g., NSA NR, SA NR, future generation deployment/connectivity service, etc.).

According to some exemplary embodiments, access network105may be implemented to include various architectures of wireless service, such as, for example, macrocell, microcell, femtocell, picocell, metrocell, NR cell, Long Term Evolution (LTE) cell, non-cell, 5G cell, or another type of wireless architecture. Additionally, according to various exemplary embodiments, access network105may be implemented according to various wireless technologies (e.g., RATs, etc.), and various wireless standards, frequencies, bands, and segments of radio spectrum (e.g., centimeter (cm) wave, mmWave, below 6 GHz, above 6 GHz, higher than mmWave, C-band, licensed radio spectrum, unlicensed radio spectrum, etc.), and/or other attributes or technologies used for radio communication. Additionally, or alternatively, according to some exemplary embodiments, access network105may be implemented to include various wired and/or optical architectures for wired and/or optical access services.

Depending on the implementation, access network105may include one or multiple types of network devices, such as access devices107. For example, access device107may include a gNB, an eLTE evolved Node B (eNB), an eNB, a radio network controller (RNC), a RIC device, an IAB device (e.g., IAB node, IAB donor node (e.g., CU, DU, RU), IAB donor DU node, IAB donor DU/RU node, etc.), a base station controller (BSC), a remote radio head (RRH), a baseband unit (BBU), an RU, a remote radio unit (RRU), a CU, a CU-control plane (CP), a CU-user plane (UP), a DU, a small cell node (e.g., a picocell device, a femtocell device, a microcell device, a home eNB, a home gNB, etc.), an open network device (e.g., O-RAN CU (O-CU), O-RAN DU (O-DU), O-RAN RU (O-RU), O-RAN next generation Node B (O-gNB), O-RAN evolved Node B (O-eNB)), a 5G ultra-wide band (UWB) node, a future generation wireless access device (e.g., a 6G wireless station, a 7G wireless station, or another generation of wireless station), or another type of wireless node (e.g., a WiFi device, a WiMax device, a hotspot device, a fixed wireless access CPE (FWA CPE), etc.) that provides a wireless access service. Additionally, access devices107may include a wired and/or an optical device (e.g., modem, wired access point, optical access point, Ethernet device, multiplexer, etc.) that provides network access and/or transport service.

According to some exemplary implementations, access device107may include a combined functionality of multiple radio access technologies (RATs) (e.g., 4G and 5G functionality, 5G and 5.5G functionality, etc.) via soft and hard bonding based on demands and needs. According to some exemplary implementations, access device107may include a split access device (e.g., a CU-control plane (CP), a CU-user plane (UP), or another type of split access device), an integrated functionality, such as a CU-CP and a CU-UP, or other integrations or splits of RAN nodes. Access device107may be an indoor device or an outdoor device.

According to an exemplary embodiment, at least some of access devices107may include logic of an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service. For example, a RIC device, an RNC device, a BSC device, or similar type of RAN device that may manage, control, and/or configure wireless stations of access network107(referred to herein simply as a RIC device) may provide a traffic balancing service of the IAB backhaul sharing among co-located radio sites service. According to another example, an IAB donor DU node may provide the traffic balancing service, as described herein. For example, an IAB donor node may be implemented to include the IAB donor DU node with a separate or an integrated CU. According to another example, an IAB donor node may include an IAB donor O-DU with a separate or an integrated O-CU. According to yet another example, the traffic balancing service may be collaboratively performed by the IAB donor DU node and the CU, for example. According to still another example, an IAB donor O-DU node may provide the traffic balancing service.

According to an exemplary embodiment, at least some access devices107may include logic of a scheduling service included in the IAB backhaul sharing among co-located radio sites service. For example, the IAB donor DU node, the IAB donor O-DU node, a gNB, an eNB, an eLTE eNB, a DU, an O-DU, or another type of cellular wireless station of access network105(referred to simply as wireless station) may provide or support the scheduling service. As described herein, the scheduling service may calculate schedules for access and use of the IAB backhaul in relation to co-located radio sites that include the wireless station. For example, the scheduling service may integrate schedules for two or more frequency bands, cells, or the like associated with user traffic of end devices130for access and use of the IAB backhaul. According to another example, separate schedulers may collaboratively integrate the schedule for two or more frequency bands, cells, etc. for access and use of the IAB backhaul.

Backhaul network110may include one or multiple networks of one or multiple types and technologies that may connect access network105to core network120and/or a backbone network (not illustrated). For example, backhaul network110may include a transport network (e.g., optical network, wireless network, etc.), a signaling network, and/or another type of intermediary network. Backhaul network110may include one or multiple types of transport devices112, such as routing devices, relay devices, switches, platforms, aggregation devices, and/or the like.

External network115may include one or multiple networks of one or multiple types and technologies that provide an application service. For example, external network115may be implemented using one or multiple technologies including, for example, network function virtualization (NFV), software defined networking (SDN), cloud computing, Infrastructure-as-a-Service (IaaS), Platform-as-a-Service (PaaS), Software-as-a-Service (SaaS), or another type of network technology. External network115may be implemented to include a cloud network, a private network, a public network, a MEC network, a fog network, the Internet, a packet data network (PDN), a service provider network, the World Wide Web (WWW), an Internet Protocol Multimedia Subsystem (IMS) network, a Rich Communication Service (RCS) network, a software-defined (SD) network, a virtual network, a packet-switched network, a data center, a data network, or other type of application service layer network that may provide access to and may host an end device application service.

Depending on the implementation, external network115may include various network devices such as external devices117. For example, external devices117may include virtual network devices (e.g., virtualized network functions (VNFs), servers, host devices, application functions (AFs), application servers (ASs), server capability servers (SCSs), containers, hypervisors, virtual machines (VMs), pods, network function virtualization infrastructure (NFVI), and/or other types of virtualization elements, layers, hardware resources, operating systems, engines, etc.) that may be associated with application services for use by end devices130. Although not illustrated, external network115may include one or multiple types of core devices122, as described herein.

External devices117may host one or multiple types of application services. For example, the application services may pertain to broadband services, broadband access everywhere, enhanced mobile broadband (eMBB), higher user mobility, Internet of Things, extreme real-time communications (e.g., tactile Internet, augmented reality (AR), virtual reality (VR), etc.), lifeline communications, ultra-reliable communications (e.g., automated traffic control and driving, collaborative robots, health-related services, broadcast-like services, communication services (e.g., email, text (e.g., Short Messaging Service (SMS), Multimedia Messaging Service (MMS), etc.), massive machine-type communications (mMTC), voice, video calling, video conferencing, instant messaging), video streaming, navigation services, and/or other types of wireless and/or wired application services. External devices117may include non-virtual, logical, and/or physical network devices.

Core network120may include one or multiple networks of one or multiple network types and technologies. Core network120may include a complementary network of access network105. For example, core network120may be implemented to include a 5G core network, an evolved packet core (EPC) of an LTE network, an LTE-Advanced (LTE-A) network, and/or an LTE-A Pro network, a future generation core network (e.g., a 5.5G, a 6G, a 7G, or another generation of core network), and/or another type of core network.

Depending on the implementation of core network120, core network120may include diverse types of network devices that are illustrated inFIG.1as core devices122. For example, core devices122may include a user plane function (UPF), a Non-3GPP Interworking Function (N3IWF), an access and mobility management function (AMF), a session management function (SMF), a unified data management (UDM) device, a unified data repository (UDR), an authentication server function (AUSF), a security anchor function (SEAF), a network slice selection function (NSSF), a network repository function (NRF), a policy control function (PCF), a network data analytics function (NWDAF), a network exposure function (NEF), a service capability exposure function (SCEF), a lifecycle management (LCM) device, a mobility management entity (MME), a packet data network gateway (PGW), an enhanced packet data gateway (ePDG), a serving gateway (SGW), a home agent (HA), a General Packet Radio Service (GPRS) support node (GGSN), a home subscriber server (HSS), an authentication, authorization, and accounting (AAA) server, a policy and charging rules function (PCRF), a policy and charging enforcement function (PCEF), and/or a charging system (CS).

According to other exemplary implementations, core devices122may include additional, different, and/or fewer network devices than those described. For example, core devices122may include a non-standard or a proprietary network device, and/or another type of network device that may be well-known but not particularly mentioned herein. Core devices122may also include a network device that provides a multi-RAT functionality (e.g., 4G and 5G, 5G and 5.5G, 5G and 6G, etc.), such as an SMF with PGW control plane functionality (e.g., SMF+PGW-C), a UPF with PGW user plane functionality (e.g., UPF+PGW-U), and/or other combined nodes (e.g., an HSS with a UDM and/or UDR, an MME with an AMF, etc.). Also, core devices122may include a split core device122. For example, core devices122may include a session management (SM) PCF, an access management (AM) PCF, a user equipment (UE) PCF, and/or another type of split architecture associated with another core device122, as described herein.

End device130may include a device that may have communication capabilities (e.g., wireless, wired, optical, etc.). End device130may or may not have computational capabilities. End device130may be implemented as a mobile device, a portable device, a stationary device (e.g., a non-mobile device and/or a non-portable device), a device operated by a user, or a device not operated by a user. For example, end device130may be implemented as a smartphone, a mobile phone, a personal digital assistant, a tablet, a netbook, a wearable device (e.g., a watch, glasses, headgear, a band, etc.), a computer, a gaming device, a television, a set top box, a music device, an IoT device, a drone, a smart device, a fixed wireless device, a router, a sensor, an automated guided vehicle (AGV), an industrial robot, or other type of wireless device (e.g., other type of user equipment (UE)). End device130may be configured to execute various types of software (e.g., applications, programs, etc.). The number and the types of software may vary among end devices130. End device130may include “edge-aware” and/or “edge-unaware” application service clients. For purposes of description, end device130is not considered a network device. End device130may be implemented as a virtualized device in whole or in part.

FIG.2is a diagram illustrating another exemplary environment200in which an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service may be implemented. As illustrated, exemplary environment200may include DUs202-1through202-3(also referred to collectively as DUs202and individually or generally as DU202) and RUs210-1through210-6(also referred to collectively as RUs210and individually or generally as RU210). As further illustrated, DU202-1may include a traffic balancer204. Environment200may further include schedulers206-1through206-3(also referred to collectively as schedulers206and individually or generally as scheduler206), in which each DU202may include scheduler206.

According to an exemplary embodiment, environment200provides the IAB backhaul sharing among co-located radio sites in which the radio sites (e.g., an IAB device (e.g., IAB node, IAB donor DU, IAB donor node) and a wireless station (e.g., RU210, DU202, etc.)) are co-located and the scheduling is integrated (versus not integrated as described herein) among multiple frequencies, such as Frequency (Freq) A and Frequency (Freq) B. IAB link 1 and IAB link 2 are also shown as wireless links (e.g., IAB backhaul access links) that communicatively couple the co-located radio sites with one another.

DU202may include a type of access device107that may provide baseband processing and radio frequency (RF) functions, for example. DU202may support the lower layers of a protocol stack, such as a physical layer, a media access control (MAC), and a radio link control (RLC) layer. DU202may provide a function and/or a service associated with a split architecture that may be defined or specified by a standards body, such as Third Generation Partnership Project (3GPP), 3GPP2, International Telecommunication Union (ITU), European Telecommunications Standards Institute (ETSI), Global System Mobile Association (GSMA), and the like. DU202may provide other functions and/or services, as described herein. For example, DU202may provide a traffic balancing service, a scheduling service, or both, as described herein.

Traffic balancer204may include logic that provides a traffic balancing service of the IAB backhaul sharing among co-located radio sites service, as described herein. According to an exemplary embodiment, traffic balancer204may calculate a maximum access bandwidth for each IAB device or co-located radio sites relating to use of the IAB backhaul links, as described herein. For example, traffic balancer204may calculate the maximum access bandwidth based on an access capacity demand associated with each IAB device or co-located radio sites and an IAB link bandwidth associated with each IAB device or co-located radio sites.

Scheduler206may include logic that provides a scheduling service of the IAB backhaul sharing among co-located radio sites service, as described herein. Scheduler206may calculate local scheduling for access and use of the IAB backhaul by an IAB device or co-located radio sites. According to an exemplary embodiment, scheduler206may calculate a joint schedule (e.g., involving two or more frequencies bands or cells associated with RUs210at or of the IAB device or co-located radio sites) versus an independent scheduler for each frequency band or radio at or of the IAB device or the co-located radio sites. Scheduler206may calculate the joint schedule based on a total bandwidth demand and an allotted maximum access bandwidth provided by the traffic balancing service. The scheduler may further reconfigure a first allocation of bandwidth pertaining to the IAB backhaul associated with users of a first frequency band or cell to a second allocation of bandwidth pertaining to the IAB backhaul associated with users of a second frequency band or cell based on the relative values between the total bandwidth demand and the allotted maximum access bandwidth, as described herein.

RU210may include a type of access device107that converts radio signals to and from an antenna into a digital signal. RU210may provide digital front end (DFE) functions, support a lower physical layer, as well as other radio techniques, such as beamforming, etc. As illustrated, according to exemplary environment200, at each DU202, RU210may support a Freq A or a Freq B. According to an exemplary embodiment, Freq A and Freq B are different. Freq A may be implemented as a low, mid, high, or another portion of the radio spectrum. Freq B may be implemented in the mmWave, above mmWave, or another portion of the radio spectrum. As illustrated, RU210-1,210-4, and210-5may each be associated with an IAB device, as described herein. In contrast, RU210-2, RU210-3, and RU210-6may be associated with a non-IAB device (e.g., gNB, etc.), for example. As illustrated, RU210-1and RU210-2may be co-located radio sites. DU202may also be co-located with RUs210.

AlthoughFIG.2illustrates environment200with exemplary network devices and communication links, according to other exemplary embodiments, the number and arrangement of network devices and communication links may be different. According to an exemplary embodiment, DU202-1may be implemented as a part of an IAB donor DU device or the like. Although not illustrated, the IAB donor DU device may be integrated with or split from a CU to form an IAB donor device, which may connect to backhaul network110. Additionally, according to other exemplary embodiments, the number of frequencies at each co-located radio site may be greater than two.

FIG.3is a diagram illustrating yet another exemplary environment300in which an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service may be implemented. As illustrated, exemplary environment300may include O-DUs302-1through302-3(also referred to collectively as O-DUs302and individually or generally as O-DU302) and O-RUs304-1through O-RU304-6(also referred to collectively as O-RUs304and individually or generally as O-RU304). As further illustrated, each O-DU302may include scheduler206. Environment300may further include an O-CU308and a RIC device310. RIC device310may include traffic balancer204. In view of the O-RAN standard, O-DU302and O-RU304may perform similar functions and/or provide similar services as DU202and RU210, as previously described. IAB link 1 and IAB link 2 are also shown as wireless links (e.g., IAB backhaul links) that communicatively couple the co-located radio sites with one another.

O-CU308may include a type of access device107that provides partial layer2functionality (e.g., Packet Data Convergence Protocol (PDCP) and Service Data Adaptation Protocol (SDAP)), and layer3functionality (e.g., Radio Resource Control (RRC)). O-CU308may include an O-CU-CP and an O-CU-UP (not illustrated) that provide control plane and user plane services.

RIC device310may provide intelligent radio resource management, QoS management, connectivity management, and handover management in a RAN. For example, RIC device310may control and optimize various radio resources, such as the selection of radio access devices (e.g., eNB, CU, gNB), etc.) associated with a 4G, 5G, or future RAN. RIC device310may support (near)-real-time intelligent radio resource management. For example, RIC device310may control and optimize various radio resources of radio access devices (e.g., eNB, RU, RRH, gNB, DU, etc.) associated with a 4G, 5G, or future RAN, radio resource scheduling for uplink and downlink communication with end device130, and radio signal characteristics (e.g., modulation, beam management, etc.). RIC device310may support non-real-time intelligent radio resource management, higher layer procedure optimization, and policy optimization in a RAN.

According to an exemplary embodiment, RIC device310may include logic of an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service, as described herein. For example, as mentioned above, RIC device310may include traffic balancer204, which contrasts with environment200, wherein traffic balancer204is situated in DU202-1. Traffic balancer204may provide traffic balancing services, as described herein.

AlthoughFIG.3illustrates environment300with exemplary network devices and communication links, according to other exemplary embodiments, the number and arrangement of network devices and communication links may be different. According to an exemplary embodiment, O-DU302-1may be implemented as a part of an IAB donor device or the like. Additionally, according to other exemplary embodiments, the number of frequencies at each co-located radio site may be greater than two.

FIG.4is a diagram illustrating still another exemplary environment400in which an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service may be implemented. As illustrated, exemplary environment400may include DUs402-1through402-3(also referred to collectively as DUs402and individually or generally as DU402) and RUs406-1through RU406-6(also referred to collectively as RUs406and individually or generally as RU406). Additionally, as illustrated, DUs402may be connected to each other via links408-1,408-2, and408-3(referred to collectively as link408, and individually or generally as link408). IAB link 1 and IAB link 2 are also shown as wireless links (e.g., IAB backhaul links) that communicatively couple the co-located radio sites with one another.

DU402and RU406may operate similarly to DU202and RU210. However, in contrast to environments200and300, schedulers404-1through404-6(referred to collectively as schedulers404and individually or generally as scheduler404) may not be integrated but separate or not integrated relative to each frequency band or cell, for example. For example, as further illustrated, each DU402may include scheduler404and be associated with RU406(e.g., a radio site). Environment400may include RIC device310and traffic balancer204, as previously described, and a CU410. While not an O-RAN device, for purposes of description, CU410may perform similar functions and/or services as those described in relation to O-CU308.

Scheduler404may provide the scheduling service in a manner similar to that of scheduler206except that each scheduler404of a co-located radio site may calculate a schedule for its respective radio site. For example, scheduler404-1may calculate a schedule pertaining to users of RU406-1and scheduler404-2may calculate a scheduler pertaining to users of RU406-2. Additionally, scheduler404-1or scheduler404-2may communicate their respective schedule via link408-1to the other scheduler404(e.g., scheduler404-1or scheduler404-2). According to exemplary embodiment, scheduler404-1or scheduler404-2may calculate a joint or integrated schedule based on receipt of the scheduler from the other scheduler404and their own calculated schedule.

FIG.5is a diagram illustrating exemplary components of a device500that may be included in one or more of the devices described herein. For example, device500may correspond to access device107, external device117, core device122, end device130, DU202, RU210, O-DU302, O-RU304, O-CU308, RIC device310, CU410, and/or other types of devices, as described herein. As illustrated inFIG.5, device500includes a bus505, a processor510, a memory/storage515that stores software520, a communication interface525, an input530, and an output535. According to other embodiments, device500may include fewer components, additional components, different components, and/or a different arrangement of components than those illustrated inFIG.5and described herein.

Bus505includes a path that permits communication among the components of device500. For example, bus505may include a system bus, an address bus, a data bus, and/or a control bus. Bus505may also include bus drivers, bus arbiters, bus interfaces, clocks, and so forth.

Processor510may control the overall operation, or a portion of operation(s) performed by device500. Processor510may perform one or multiple operations based on an operating system and/or various applications or computer programs (e.g., software520). Processor510may access instructions from memory/storage515, from other components of device500, and/or from a source external to device500(e.g., a network, another device, etc.). Processor510may perform an operation and/or a process based on various techniques including, for example, multithreading, parallel processing, pipelining, interleaving, learning, model-based, etc.

Memory/storage515includes one or multiple memories and/or one or multiple other types of storage mediums. For example, memory/storage515may include one or multiple types of memories, such as, a random access memory (RAM), a dynamic RAM (DRAM), a static RAM (SRAM), a cache, a read only memory (ROM), a programmable ROM (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a single in-line memory module (SIMM), a dual in-line memory module (DIMM), a flash memory (e.g., 2D, 3D, NOR, NAND, etc.), a solid state memory, and/or some other type of memory. Memory/storage515may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, a solid-state component, etc.), a Micro-Electromechanical System (MEMS)-based storage medium, and/or a nanotechnology-based storage medium.

Memory/storage515may be external to and/or removable from device500, such as, for example, a Universal Serial Bus (USB) memory stick, a dongle, a hard disk, mass storage, off-line storage, or some other type of storing medium. Memory/storage515may store data, software, and/or instructions related to the operation of device500.

Software520includes an application or a program that provides a function and/or a process. As an example, with reference to access device107, software520may include an application that, when executed by processor510, provides a function and/or a process of the IAB backhaul sharing among co-located radio sites service, as described herein. Software520may also include firmware, middleware, microcode, hardware description language (HDL), and/or another form of instruction. Software520may also be virtualized. Software520may further include an operating system (OS) (e.g., Windows, Linux, Android, proprietary, etc.).

Communication interface525permits device500to communicate with other devices, networks, systems, and/or the like. Communication interface525includes one or multiple wireless interfaces, optical interfaces, and/or wired interfaces. For example, communication interface525may include one or multiple transmitters and receivers, or transceivers. Communication interface525may operate according to a protocol stack and a communication standard. Communication interface525may support one or multiple MIMO, beamforming, and/or transmission/reception configurations.

Input530permits an input into device500. For example, input530may include a keyboard, a mouse, a display, a touchscreen, a touchless screen, a button, a switch, an input port, speech recognition logic, and/or some other type of visual, auditory, tactile, affective, olfactory, etc., input component. Output535permits an output from device500. For example, output535may include a speaker, a display, a touchscreen, a touchless screen, a light, an output port, and/or some other type of visual, auditory, tactile, etc., output component.

As previously described, a network device may be implemented according to various computing architectures (e.g., in a cloud, etc.) and according to various network architectures (e.g., a virtualized function, PaaS, etc.). Device500may be implemented in the same manner. For example, device500may be instantiated, created, deleted, or some other operational state during its life-cycle (e.g., refreshed, paused, suspended, rebooted, or another type of state or status), using well-known virtualization technologies. For example, access device107, core device122, external device117, and/or another type of network device or end device130, as described herein, may be a virtualized device.

Device500may be configured to perform a process and/or a function, as described herein, in response to processor510executing software520stored by memory/storage515. By way of example, instructions may be read into memory/storage515from another memory/storage515(not shown) or read from another device (not shown) via communication interface525. The instructions stored by memory/storage515, when executed, may cause or configure processor510to perform a function or a process, as described herein. Alternatively, for example, according to other implementations, device500may be configured to perform a function or a process described herein based on the execution of hardware (processor510, etc.).

FIG.6is a diagram illustrating still another exemplary environment600in which an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service may be implemented. As illustrated, environment600includes co-located access devices607-1through607-3(also referred to collectively as co-located access devices607and individually or generally as co-located access device607). Co-located access device607may include multiple radio sites. For example, as illustrated, co-located access device607may include a radio site 1 that supports a frequency 1 (FR1) and a radio site 2 that supports a frequency 2 (FR2). The number of co-located access devices607and radio sites at each co-located access device607are exemplary. As described herein, the number of frequencies, frequency bands, carriers, or the like at each co-located access device607may be more than two. Additionally, as described for access device107, co-located access device607may support various radio spectrum (e.g., low band, mid band, high band, mmWave, above mmWave, cm wave, etc.) for connectivity to end device130(not illustrated), for IAB links, and so forth. The topology of co-located access devices607is also exemplary. According to other exemplary embodiments, the topology may include two or more IAB links connected to one or multiple co-located access devices607.

As further illustrated, co-located access devices607may be communicatively coupled via an IAB link 1 and an IAB link 2. For example, radio site 2 at each co-located access device607may be associated with an IAB device. By way of further example, co-located access device607-1may be an IAB donor DU/RU device and co-located access devices607-2and607-3may each be an IAB DU/RU device or child (e.g., Child 1 and Child 2). IAB link 1 and IAB link 2 and co-located access devices607may be considered an (IAB) network path to and from backhaul network110. Although not illustrated, each co-located access device607may include a scheduler device (e.g., scheduler206). Additionally, although not illustrated, environment600may include a traffic balancing device. According to some exemplary embodiments, co-located access device607-1may include a traffic balancing device (e.g., traffic balancer204) or the traffic balancing device (e.g., traffic balancer204) may be included in RIC device310or the like, for example.

The allocation of a maximum bandwidth for an IAB link is constrained by the bandwidth capacity of the IAB link. For example, assume the bandwidth for IAB link 1 is BW1. IAB link 1 may support the user traffic for all IAB devices, such as Child 1 and Child 2. Also assume that the access link bandwidth for Child 1 and Child 2 are BW Child 1 and BW Child 2. For the sake of simplicity, assume that overhead is ignored, the access link bandwidth allocation should satisfy the following exemplary condition or expression:

FIG.7is a flow diagram illustrating an exemplary process700of an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service. According to an exemplary embodiment, access device107may perform process700. For example, access device107may be implemented as a RIC device, such as RIC device310or similar RAN controller device, or an IAB donor DU device or an IAB donor device that may provide the traffic balancing services of the IAB backhaul sharing among co-located radio sites service, as described herein. According to an exemplary implementation, processor510executes software520to perform a step (in whole or in part) of process500, as described herein. Alternatively, a step (in whole or in part) may be performed by the execution of only hardware.

For purposes of description in relation to process700, the RIC device, the IAB donor DU device, and/or the like is/are referred to as traffic balancing device. Additionally, for the purposes of description, reference is made toFIGS.2,3, and6.

Referring toFIG.7, in block705, the traffic balancing device may receive available bandwidth of IAB link from each co-located radio sites. For example, the traffic balancing device (e.g., traffic balancer204) may receive an available IAB link bandwidth value regarding an IAB link from the scheduling device (e.g., scheduler206, scheduler404, schedulers of co-located access devices607). According to an exemplary embodiment, the scheduling device may provide a scheduling service (in an integrated manner) in relation to two or more radio frequencies, frequency bands, carriers, cells, etc., of the co-located radio sites, as described herein. According to another exemplary embodiment, the scheduling device may provide a scheduling service (in a non-integrated manner, such as scheduler404). The available IAB link bandwidth value may indicate a total bandwidth or a capacity value. The available IAB link bandwidth value may include a current value and/or a prospective value.

In block710, the traffic balancing device may receive a bandwidth demand from each co-located radio sites. For example, the traffic balancing device may receive a bandwidth demand value from the scheduling device of co-located access devices607(e.g., IAB donor DU, Child 1, Child 2), DU202and RU210, O-DU302and O-RU304, DU402and RU406, and so forth.

In block715, the traffic balancing device may calculate and allocate the maximum access bandwidth for each co-located radio sites. For example, the traffic balancing device may calculate and allocate a maximum access bandwidth value based on the available IAB link bandwidth value and the bandwidth demand value for each co-located radio sites, as well as expression (1), as described herein. The traffic balancing device may calculate the allotted maximum access bandwidth value for each co-located radio sites based on other types of criteria, such as node efficiency, cluster efficiency, co-located radio sites bandwidth history, IAB topology, and/or other factors (e.g., network policies relating to user traffic priority, access fairness, etc.). Referring toFIG.6, the allotted maximum access bandwidth value associated with each co-located radio sites (e.g., co-located radio sites607-1,607-2, and607-3) may be a portion of the IAB backhaul (e.g., IAB link 1 and IAB link 2 or child 2 to donor) that is shared by multiple co-located radio sites of a network path (e.g., child 2 to donor) to backhaul network110in the upstream direction or a network path (e.g., donor to child 2) from backhaul network110in the downstream direction, for example.

In block720, the traffic balancing device may transmit the maximum access bandwidth allocated to each scheduling device. For example, the traffic balancing device may transmit an allotted maximum access bandwidth value, which may be different between different co-located radio sites, to the scheduling device of each co-located radio sites.

FIG.7illustrates an exemplary process700of the IAB backhaul sharing among co-located radio sites service, however, according to other exemplary embodiments, the IAB backhaul sharing among co-located radio sites service may perform additional operations, fewer operations, and/or different operations than those illustrated and described in relation toFIG.7. For example, the traffic balancing device may perform additional and/or different operations or steps as described elsewhere in this description.

FIG.8is a flow diagram illustrating an exemplary process800of an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service. According to an exemplary embodiment, access device107may perform process800. For example, access device107may be implemented as a wireless station, such as an eNB, an eLTE eNB, a gNB, a DU device, a DU and RU device, an IAB device, or the like, which includes a scheduler that provides the scheduling service, as described herein. According to an exemplary implementation, processor510executes software520to perform a step (in whole or in part) of process800, as described herein. Alternatively, a step (in whole or in part) may be performed by the execution of only hardware. For purposes of description, process800is described as being performed by a scheduling device.

Referring toFIG.8, in block805, the scheduling device may calculate a traffic schedule for user traffic associated with multiple frequency bands or cell of a co-located radio site. The scheduling device may evaluate respective users buffer size, SLA or QoS, and queueing history associated with each radio site and set of users.

In block810, the scheduling device may determine whether the total bandwidth demand is greater than the allocated bandwidth. For example, the scheduling device may compare the total access bandwidth demand to the allotted maximum access bandwidth provided by the traffic balancer.

When the total bandwidth demand is not greater than the allocated bandwidth (block810-NO), the scheduling device may determine whether to reconfigure any user (block815). For example, when there is excess IAB backhaul bandwidth, the scheduling device may increase an allotment of the maximum access bandwidth to a set of users or a user. By way of example, referring toFIG.6, if an FR1 user (e.g., a sub-6 GHz user) is situated in an FR2 cell (e.g., a mmWave cell) (as well as the FR1 cell), the scheduling device may increase or upgrade the allotment of IAB backhaul bandwidth to such FR1 user. Thus, as illustrated inFIG.8, in block820, the scheduling device may reconfigure the user. Depending on whether there is any remaining excess bandwidth, process800may proceed from block820to block825, or proceed from block820to block825.

When the scheduling device determines that there are no users that may be reconfigured (block815-NO), the scheduling device may update the bandwidth demand (block825). For example, the scheduling device may inform the traffic balancer with an updated access capacity demand. In this way, the traffic balancer may assign any excess bandwidth to another co-located radio sites or IAB device. As further illustrated, from blocks820and825, the scheduling device may calculate an access bandwidth demand and other parameters, in block830. The other parameters may include SLA requirement of a user, buffer size, queueing history, and other parameters, as described herein.

Referring back to block810, when the total bandwidth demand is greater than the allocated maximum access bandwidth (block810-YES), the scheduling device may determine whether any user may be reconfigured (block835). For example, when there is insufficient IAB backhaul bandwidth, the scheduling device may decrease or downgrade an allotment of the maximum access bandwidth to a set of users or a user. By way of example, referring toFIG.6, if an FR2 user (e.g., a mmWave user) is situated in an FR1 cell (e.g., a sub-6 GHz cell), the scheduling device may decrease the allotment of IAB backhaul bandwidth to such FR2 user. Thus, as illustrated inFIG.8, in block840, the scheduling device may reconfigure the user. When the scheduling device determines that the user may not be reconfigured (block835-NO), the scheduling device may suspend lower priority users to meet the allocated access bandwidth (block845). For example, the scheduling device may determine or identify gradations of priority among users based on SLA requirements, queueing history (e.g., a user has been scheduled more often than another user, or a user has been scheduled less often than another user), subscription information pertaining to the user/end device130, and/or other configurable factors.

As further illustrated, at blocks840and845, process800may continue to block850in which the scheduling device may calculate the access bandwidth demand and other parameters. The other parameters may include SLA requirement of a user, buffer size, queueing history, and other parameters, as described herein. Process800may continue to block805.

FIG.8illustrates an exemplary process of the IAB backhaul sharing among co-located radio sites service, however, according to other exemplary embodiments, the IAB backhaul sharing among co-located radio sites service may perform additional operations, fewer operations, and/or different operations than those illustrated and described in relation toFIG.8. For example, the scheduling device may perform additional and/or different operations as described elsewhere in this description.

FIG.9is a flow diagram illustrating an exemplary process900of an exemplary embodiment of the IAB backhaul sharing among co-located radio sites service. According to an exemplary embodiment, access device107may perform process900. For example, access device107may be implemented as a wireless station, such as an eNB, an eLTE eNB, a gNB, a DU device, a DU and RU device, or the like. According to an exemplary implementation, processor510executes software520to perform a step (in whole or in part) of process800, as described herein. Alternatively, a step (in whole or in part) may be performed by the execution of only hardware. For purposes of description in relation to process900, the wireless station is referred to as a scheduling device.

In block905, the scheduling device may calculate an available bandwidth and report to a traffic balancing device. For example, the scheduling device (e.g., scheduler206, scheduler404, etc.) may calculate a current and/or prospective available IAB link bandwidth value. The available IAB link bandwidth value may be a dynamic value over time based on varying RF conditions and/or other known factors. The scheduling device may transmit the current and/or prospective available IAB link bandwidth value to traffic balancer204.

In block910, the scheduling device may calculate access capacity demand and report to the traffic balancing device. For example, the scheduling device (e.g., scheduler206, scheduler404, etc.) may calculate a current and/or prospective access demand value, and transmit the access demand value to traffic balancer204. The scheduling device may calculate the current and/or prospective access demand value based on various criteria, such as the number of users being serviced, the number of connections served by the co-located radio sites (e.g., FR1 connections, FR2 connections, etc.), current RF conditions, spectral efficiency, and/or other types of criteria (e.g., end device130mobility, user priority, user traffic characteristics (e.g., bursty, periodic, aperiodic, continuous, amount of data, length of time pertaining to a transmission or a reception of data, etc.).

In block915, the scheduling device may receive an allotted maximum access bandwidth. For example, responsive to a transmission of the available and/or prospective IAB link bandwidth value and the current and/or prospective access demand value, the scheduling device (e.g., scheduler206, scheduler404, etc.) may receive from traffic balancer204an allotted maximum access bandwidth value.

In block920, the scheduling device may provide a scheduling service based on the allotted maximum access bandwidth. For example, as illustrated and described in relation toFIG.8, the scheduling device (e.g., scheduler206, scheduler404, etc.) may perform the scheduling service. The scheduling device may also provide the scheduling service based on other criteria, such as users buffer size, load balancing between different frequency bands, and/or other types of metrics (e.g., user traffic priority, etc.).

FIG.9illustrates an exemplary process of the IAB backhaul sharing among co-located radio sites service, however, according to other exemplary embodiments, the IAB backhaul sharing among co-located radio sites service may perform additional operations, fewer operations, and/or different operations than those illustrated and described in relation toFIG.9. For example, the scheduling device may perform additional and/or different operations as described elsewhere in this description.

Additionally, embodiments described herein may be implemented as a non-transitory computer-readable storage medium that stores data and/or information, such as instructions, program code, a data structure, a program module, an application, a script, or other known or conventional form suitable for use in a computing environment. The program code, instructions, application, etc., is readable and executable by a processor (e.g., processor510) of a device. A non-transitory storage medium includes one or more of the storage mediums described in relation to memory/storage515. The non-transitory computer-readable storage medium may be implemented in a centralized, distributed, or logical division that may include a single physical memory device or multiple physical memory devices spread across one or multiple network devices.

No element, act, or instruction set forth in this description should be construed as critical or essential to the embodiments described herein unless explicitly indicated as such.

All structural and functional equivalents to the elements of the various aspects set forth in this disclosure that are known or later come to be known are expressly incorporated herein by reference and are intended to be encompassed by the claims.