Inter-system and event-triggered mobility load balancing

Methods, systems, and devices for wireless communications are described. Some wireless communications system may utilize an inter-system information report message (e.g., a self-organizing network (SON) information report message) to support inter-system mobility load balancing (MLB). For example, a first node, operating in accordance with a first radio access technology (RAT), may receive an information report message from a second node operating in accordance with a second RAT. The information report message may include a periodic load reporting request information element (IE) or an event-triggered load reporting request IE. In response, the first node may determine a traffic load based on the load reporting request and transmit, to the second node, an information report message which includes one or more IEs for reporting the determined traffic load. The exchange of the load information via the IEs may enable for MLB between nodes of different RAT.

FIELD OF TECHNOLOGY

The following relates generally to wireless communications and more specifically to inter-system and event-triggered mobility load balancing (MLB).

BACKGROUND

Some wireless communications systems may implement mobility load balancing (MLB) to ensure a uniformly-distributed traffic load among cells or areas of cells. For example, using MLB, a traffic load may be offloaded from a congested cell of a base station to relatively less congested cells of other base stations. However, inter-system load balancing may not be supported by some systems.

SUMMARY

The described techniques relate to improved methods, systems, devices, and apparatuses that support inter-system and event-triggered mobility load balancing (MLB). Generally, the described techniques provide for a node of a first radio access technology (RAT) (e.g., evolved universal terrestrial radio access (E-UTRA)) to exchange load information with a node of a second RAT (e.g., New Radio (NR)). To support load information exchange between different RAT systems, inter-system information reporting may be enhanced. For example, a self-organizing network (SON) information report exchanged over NG and S1 interfaces may include information elements (IEs) that facilitate both periodic and event-triggered load reporting by the nodes, thereby enabling inter-system MLB. The SON information report message may include one or more load reporting request IEs which may specify which cells, beams, or slices, or any combination thereof, for which a node may report load information. Upon receipt of the load reporting request IE(s), a reporting node may determine a traffic load and report the information using one or more load reporting response IEs of the SON information report message. In some cases, the event-triggered load reporting request IE may indicate a number of measurement reporting levels and the reporting node may divide a load scale into the indicated number of measurement reporting levels.

A method for wireless communication at a first node is described. The method may include determining a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmitting, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

An apparatus for wireless communication at a first node is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

Another apparatus for wireless communication at a first node is described. The apparatus may include means for determining a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and means for transmitting, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

A non-transitory computer-readable medium storing code for wireless communication at a first node is described. The code may include instructions executable by a processor to determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, determining the traffic load may include operations, features, means, or instructions for determining load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more IEs of the first information report message including a report of the determined load information.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the load information includes one or more load metrics including a composite available capacity (CAC) value, a radio resource status indicator, a hardware load (HWL) indicator, a transport network load (TNL) indicator, an uplink/downlink bit rate indicator, a physical resource block (PRB) usage indicator, or any combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving, from the second node, a second information report message including one or more IEs including the load reporting request, where the one or more IEs of the second information report message include a periodic load reporting request IE, an event-triggered load reporting request IE, or any combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within the periodic load reporting request IE, a request for load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, where determining the traffic load may include operations, features, means, or instructions for determining the load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, where a periodic load reporting response IE of the first information report message includes the determined load information.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within the periodic load reporting request IE, a cell global identifier (CGI) for each cell of the set of one or more cells, where the load information for the set of one or more cells may be based on the identified CGI.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within the periodic load reporting request IE, a synchronization signal block (SSB) index for each directional beam of the set of one or more directional beams, where the load information for the set of one or more directional beams may be based on the identified SSB index.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, may be associated with the first RAT or the second RAT.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within the event-triggered load reporting request IE, a measurement reporting level IE including a set of two or more measurement reporting levels and determining that the traffic load may have changed from a first measurement reporting level to a second measurement reporting level different from the first measurement reporting level based on the set of two or more measurement reporting levels, where transmitting the first information report message includes transmitting the first information report message to the second node based at least in part on the determination that the traffic load has changed, where an event-triggered load reporting response IE of the first information report message includes the determined load information.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the first information report message may include operations, features, means, or instructions for identifying that the determined traffic load triggers an overload state of the first node and transmitting the first information report message to the second node based on the determined traffic load triggering the overload state, where an event-triggered load reporting response IE of the first information report message includes the determined load information.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the first information report message may include operations, features, means, or instructions for identifying that the determined traffic load satisfies a threshold traffic level of the first node and transmitting the first information report message to the second node based on the determined traffic load satisfying the threshold traffic level, where an event-triggered load reporting response IE of the first information report message includes the determined load information.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first information report message includes an inter-system SON information report message and may be transmitted via an NG interface for a network operating in accordance with the NR RAT or an S1 interface for a network operating in accordance with the E-UTRA RAT.

A method for wireless communication at a first node is described. The method may include receiving, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, determining, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmitting, to the second node, a second message reporting the determined load information.

An apparatus for wireless communication at a first node is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmit, to the second node, a second message reporting the determined load information.

Another apparatus for wireless communication at a first node is described. The apparatus may include means for receiving, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, means for determining, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and means for transmitting, to the second node, a second message reporting the determined load information.

A non-transitory computer-readable medium storing code for wireless communication at a first node is described. The code may include instructions executable by a processor to receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmit, to the second node, a second message reporting the determined load information.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within an IE, the indication of the number of measurement reporting levels, the number of measurement reporting levels including a set of two or more measurement reporting levels and computing a load scale that corresponds to the set of two or more measurement reporting levels based on the indication, where the determined load information may be reported based on the set of two or more measurement reporting levels.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for identifying, within an IE, the indication of the measurement objects to be reported, the measurement objects to be reported including requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, where the determined load information may be reported based on the requested load metrics.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, determining the load information may include operations, features, means, or instructions for determining the load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the first node or the second node includes a centralized unit (CU) of a base station, a distributed unit (DU) of the base station, a node associated with a user plane, a node associated with a control plane, a first base station, or a second base station.

A method for wireless communication at a first node is described. The method may include transmitting, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receiving, from the second node, a second information report message, the second information report message including one or more IEs reporting a traffic load of the second node, and determining to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

An apparatus for wireless communication at a first node is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receive, from the second node, a second information report message, the second information report message including one or more Ws reporting a traffic load of the second node, and determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

Another apparatus for wireless communication at a first node is described. The apparatus may include means for transmitting, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more Ws including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, means for receiving, from the second node, a second information report message, the second information report message including one or more IEs reporting a traffic load of the second node, and means for determining to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

A non-transitory computer-readable medium storing code for wireless communication at a first node is described. The code may include instructions executable by a processor to transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more IEs including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receive, from the second node, a second information report message, the second information report message including one or more IEs reporting a traffic load of the second node, and determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, transmitting the first information report message may include operations, features, means, or instructions for transmitting, within the first information report message, a load information request for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more IEs of the first information report message including a periodic load reporting request IE, an event-triggered load reporting request IE, or any combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the traffic load of the second node includes one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, a periodic load reporting response IE of the second information report message includes load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, within the periodic load reporting request IE, a CGI for each cell of the set of one or more cells, where the load information for the set of one or more cells may be based on the CGI.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, within the periodic load reporting request IE, an SSB index for each directional beam of the set of one or more directional beams, where the load information for the set of one or more directional beams may be based on the SSB index.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, within the event-triggered load reporting request IE, a measurement reporting level IE including a set of two or more measurement reporting levels, where an event-triggered load reporting response IE of the second information report message includes load information based on the set of two or more measurement reporting levels.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the second information report message may be based on the traffic load triggering an overload state of the second node for a time duration.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for receiving the second information report message may be based on the traffic load satisfying a threshold traffic level of the second node.

A method for wireless communication at a first node is described. The method may include transmitting, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receiving, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determining to perform the MLB between the first node and the second node based on the load information of the second node.

An apparatus for wireless communication at a first node is described. The apparatus may include a processor, memory coupled with the processor, and instructions stored in the memory. The instructions may be executable by the processor to cause the apparatus to transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determine to perform the MLB between the first node and the second node based on the load information of the second node.

Another apparatus for wireless communication at a first node is described. The apparatus may include means for transmitting, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, means for receiving, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and means for determining to perform the MLB between the first node and the second node based on the load information of the second node.

A non-transitory computer-readable medium storing code for wireless communication at a first node is described. The code may include instructions executable by a processor to transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determine to perform the MLB between the first node and the second node based on the load information of the second node.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, within an IE, the indication of the number of measurement reporting levels, the number of measurement reporting levels including a set of two or more measurement reporting levels, where the load information may be based on the set of two or more measurement reporting levels.

Some examples of the method, apparatuses, and non-transitory computer-readable medium described herein may further include operations, features, means, or instructions for transmitting, within an IE, the indication of the measurement objects to be reported, the measurement objects to be reported including requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, where the load information may be reported based on the requested load metrics.

In some examples of the method, apparatuses, and non-transitory computer-readable medium described herein, the load information includes load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof.

DETAILED DESCRIPTION

Some wireless communications systems may support mobility load balancing (MLB). The objective of MLB may be to distribute a traffic load evenly among cells and among areas of cell by transferring traffic from congested cells to less congested cells. A function of MLB may include load reporting by exchanging information over respective interfaces between nodes (e.g., Xn, X2, F1, or E1 interfaces). As an example of inter-system MLB, a first base station operating in accordance with a first radio access technology (RAT) may exchange load information with a second base station operating in accordance with the first RAT over the X2 or Xn interfaces. In some examples, wireless communications systems may support mixed deployments of base stations, including base stations of a first RAT and base stations of a second RAT that may communicate with one another and further support communications for various UEs. In such examples, it may be beneficial to exchange load information between different RAT systems (e.g., inter-system load balancing) to provide network energy savings and enhanced communications performance. Specifically, inter-system load balancing for systems operating using different RATs (e.g., between a Long-Term Evolution (LTE) system and a New Radio (NR) system, or between systems using other RATs, such as those operating in accordance with future communications standards) may be desirable.

As described herein, a wireless communications system may support inter-system information reporting for inter-system MLB. For example, a self-organizing network (SON) information report message may include a load reporting request information element (IE) and a load reporting response IE for periodic and event-triggered load reporting. The load reporting request IE may indicate the cells, beams, or slices, or any combination thereof, for which a node is to report load information. Additionally, the load reporting request IE pertaining to event-triggered load reporting may also indicate a number of measurement reporting levels, and a reporting node may divide a load scale into the indicated number of measurement levels (e.g., 2, 3, or 5 levels). Upon receipt of the load reporting request IEs, a reporting node may respond with a SON information report including load reporting response IEs. The load reporting response IEs may include the load information (e.g., a composite available capacity (CAC) value, a radio resource status indicator, or a hardware load (HWL) indicator, and the like) for the requested cells, beams, or slices, or any combination thereof. As described above, the load reporting may be periodic or event-triggered. In the case of event-triggered reporting, the reporting node may exchange load information once an event is satisfied. In one example, if a value associated with load information changes (e.g., increases or decreases) from one measurement reporting level to another measurement reporting level in the load scale (e.g., determined by the reporting node and the indicated number of measurement reporting levels), then the reporting node may provide its traffic load information. In other examples, the reporting node may transmit an indication of its traffic load when a value associated with the load information exceeds a threshold value or when the load is in an overload state.

Additionally, for event-triggered MLB, a node may transmit a resource status request including IEs indicating report characteristics, which may include measurement objects (e.g., indicated by a bitmap) and the frequency at which the objects may be reported (e.g., based on various event triggers, such as physical resource block (PRB) events, transport network load (TNL) capacity events, CAC events, or the like). The resource status request may also include an IE indicating a number of measurement reporting levels. The target (e.g., reporting) node may divide a load scale by the indicated number of measurement levels and report load information if the values associated with the load information changes from one measurement reporting level to another measurement reporting level in the load scale or if the values associated with the load information exceed an overload threshold value. In response, the reporting node may transmit a resource status response (e.g., event-triggered) including the load information requested.

Aspects of the disclosure are initially described in the context of wireless communications systems. Additional aspects are described in the context of process flows. Aspects of the disclosure are further illustrated by and described with reference to apparatus diagrams, system diagrams, and flowcharts that relate to inter-system and event-triggered MLB.

Wireless communications system100may utilize MLB to ensure a uniformly-distributed traffic load among cells or areas of cells. For example, a base station105operating in accordance with a first RAT (e.g., E-UTRA) may experience increased traffic loads, which may overload the resources at the base station. Using MLB, the traffic load may be offloaded from the congested cell of the base station105to less congested cells of nearby base stations105also operating in accordance with a first RAT. In some examples, wireless communications system100may support mixed deployment of base stations105(e.g., E-UTRA and NR base stations105). In such example, it may be beneficial to exchange load information between a base station105operating in accordance with a first RAT and a base station105operating in accordance with a second RAT for network energy savings and user performance.

In some cases, wireless communications system100may support a node of a first RAT (e.g., E-UTRA) exchanging load information with a node of a second RAT (e.g., NR). To support load information exchange between different RATs, inter-system information reporting may be enhanced. For example, a SON information report exchanged over NG and S1 interfaces may include IEs that facilitate both periodic and event-triggered load reporting by the nodes, thereby enabling inter-system MLB. The SON information report message may include one or more load reporting request IEs which may specify which cells, beams, or slices, or any combination thereof, for which a node may report load information. Upon receipt of the load reporting request IE(s), a reporting node may determine a traffic load and report the information using one or more load reporting response IEs of the SON information report message. In some cases, the event-triggered load reporting request IE may indicate a number of measurement reporting levels and the reporting node may divide a load scale into the indicated number of measurement reporting levels. As such, wireless communications system100may support techniques for inter-system MLB (e.g., periodic and event-triggered) for nodes that operate using different RATs. For instance, using the described techniques, MLB may be performed between E-UTRA and NR. However, the described techniques may not be limited to inter-system MLB for E-UTRA and NR, and may be applicable to inter-system MLB for other RATs not explicitly described herein (such as additional RATs that operate in accordance with future wireless standards).

FIG.2illustrates an example of a wireless communications system200that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. In some examples, wireless communications system200may implement aspects of wireless communications system100. Wireless communications system200may include core network130-aand core network130-b, which may be examples of a core network130described with reference toFIG.1. Wireless communications system also includes base station105-a, base station105-b, base station105-c, and base station105-d, which may be examples of a base station105, as described with reference toFIG.1.

Core networks130may communicate with base stations105and base stations105may communication with one another via various interfaces. For example, core network130-amay communicate with base station105-ausing backhaul link210-aand base station105-busing backhaul link210-b. Backhaul link210-aand backhaul link210-bmay be examples of S1 interfaces (e.g., an interface between a node and a core network, such as in non-standalone operations). Additionally, base station105-amay communicate with base station105-bvia backhaul link215-a. Backhaul link215-amay be an example of an X2 interface (e.g., an interface allowing nodes to interconnect with each other, such as in non-standalone operations). Additionally, core network130-bmay communicate with base station105-cusing backhaul link210-cand base station105-dusing backhaul link210-d. Backhaul link210-cand backhaul link210-dmay be examples of NG interfaces (e.g., an interface between a node and a core network, such as in standalone operations). Additionally, base station105-cmay communicate with base station105-dvia backhaul link215-b. Backhaul link215-bmay be an example of an Xn interface (e.g., an interface allowing NG-RAN nodes to interconnect with each other). Moreover, core network130-amay exchange information with core network130-bover backhaul link220(e.g., an N26 interface). Interfaces may also exist within base stations105. For example, an F1 interface may allow a central unit (CU) (e.g., a logical node the performs functions of a base station, such as user data transfer, mobility control, session management, radio access network sharing, and the like) and a distributed unit (DU) (e.g., a logical node controlled by the CU and performs a subset of base station functions, for example, based on a functional split between the CU and the DU) of base stations105to exchange information. Additionally, E1 interfaces may exist between the control unit user plane (CU-UP) and control unit control plane (CU-CP) of base stations105.

In some examples, wireless communications system200may support SON, where SON may be described as a method to automate the configuration and optimization of wireless networks. Examples of functions of an SON may include self-configuration, self-optimization, and self-healing. A part of the self-optimization function of an SON may include MLB. The objective of MLB may be to evenly distribute load among cells (e.g., coverage area of a node or base stations105) and areas of cells (e.g., different sectors of a cell). Additionally, MLB may aid in the transfer of traffic from congested cells or areas of cells to less congested cells or areas of cells. Moreover, MLB may offload users from one cell, cell area, carrier, or RAT to achieve network energy saving. One aspect of MLB may include load reporting by exchanging load information over the Xn, X2, F1, and E1 interfaces. Another aspect of MLB may include performing load balancing actions (e.g., handover) based on the exchanged load information.

Wireless communications system200may support intra-system MLB. That is, load reporting may occur within system205-aor system205-b. For example, base station105-amay utilize backhaul link215-a(e.g., X2 interface) to exchange load reporting information with base station105-b. Base station105-amay transmit a resource status request message to base station105-b. The resource status request message may indicate to base station105-bhow and what load information is to be reported. In some examples, resource status request message may include multiple IEs. For example, the resource status request message may include IEs associated with report characteristics, cells to report, beams to report, etc. The report characteristics IE may include a bitmap, where each position of the bitmap indicates a measurement object base station105-bis requested to report and the frequency it is to be reported. The measurement objects may include a PRB event trigger, a TNL capacity event trigger, and CAC event trigger, which may correspond to a first bit, a second bit, and a third bit, respectively. Additionally, the report characteristic IE may indicate periodic reporting of the measurement objects. The range for periodicity reporting may be 1 to 10 seconds. The resource status request may also include IEs that indicate the cells, beams, or slices for which load reporting is requested. Cell global identifiers (CGI) may be used to identify cells and synchronization signal block (SSB) indices may be used to identify beams. In response to the resource status request, base station105-bmay periodically transmit a resource status response message which includes load information for each of the requested cells, beams, or slices. That is, base station105-amay exchange load information with base station105-band base stations105-bmay perform an action (e.g., handover) based on the exchanged load information. However, wireless communications system200may not support inter-system load balancing. As described herein, base station105-amay operate according to a first RAT (e.g., E-UTRA) and base station105-cmay operate according to a second RAT (e.g., NR). In some examples, mixed deployment of base stations105may be implemented. In such case, it may be important for base station105-ato exchange load information with base station105-cto provide network energy savings and better user performance.

Wireless communications system200may support inter-system load balancing. For example, wireless communications system200may utilize an inter-system SON information report message225to exchange load information between system205-aand system205-b. An example format of SON information report message225may be shown by Table 1. The SON information report message225may contain one or more IEs for a load reporting request. For example, SON information report message225may include periodic load reporting request IE230or event-triggered load reporting request IE240. Additionally, SON information report message225may include one or more IEs for a load reporting response. For example, SON information report message225may include periodic load reporting response IE235and event-triggered load reporting response IE245. Base station105-a, operating in accordance with E-UTRAN, may transmit SON information report message225including periodic load reporting request IE230or event-triggered load reporting request IE240to base station105-c, operating in accordance with NR, and in response, base station105-cmay transmit SON information report message225including periodic load reporting response IE235or event-triggered load reporting response IE245to base station105-c.

An example format of periodic reporting request IE230is shown by Tables 2 and 3. The periodic load reporting request IE230may include IEs pertaining to cells, beams, or slices (e.g., network slices) for which the load reports are requested. For example, the cells, beams, and slices associated with base station105-c. The cells may be indicated using CGI and the beams may be indicated using SSB indices. In some examples, cell list IEs may be octet string type IEs and the beam list IEs may be integer type IEs (e.g., 1, 2, . . . , 64).

An example format of periodic reporting response IE235is shown by Tables 4, 5, and 6. The periodic report response IE245may include load information for each of the requested cells, beams, and slices. Load information may include a CAC value, a radio resource status indicator, an HWL indictor, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, and the like.

An example format of event-triggered reporting request IE240is shown by Table 7. Event-triggered reporting response IE240may include an IE associated with a number (or quantity) of reporting levels. Base station105-a(e.g., reporting node) may determine a load-level threshold (e.g., overload value for the TNL load capacity or the HWL capacity) for each cell, beam, slice, or a combination thereof. The load-level threshold may be divided into a number of reporting levels (e.g., 2, 3, or 5 levels) indicated by event triggered reporting request IE240. The reporting levels may be evenly distributed on a linear scale below the load-level threshold (e.g., the overload value).

TABLE 7Event-Triggered Load Reporting RequestIE/Group NamePresenceNumber of Measurement Reporting LevelsM

An example format of event-triggered reporting response IE245is shown by Table 8. Base station105-cmay report load information when the value associated with TNL capacity or HWL capacity for each beam, cell, slice, or combination thereof increases from one reporting level to another reporting level (e.g., from level 2 to level 3), enters or exits the load-level threshold, or increases beyond an absolute threshold.

Additionally, the event-triggered reporting may be applied to intra-system MLB. As stated above, wireless communications system200may support periodic intra-system MLB reporting. For example, base station105-amay send a resource status request to base station105-arequesting measurement information associated with specified cells, beams, or slices and in response, base station105-bmay periodically transmit a resource status response indicating the measurement information. However, periodic load balancing reporting may result in unnecessary signaling and as such, a resource status message may support event-triggered reporting. For example, report characteristics IE of the resource status request may include additional measurement objects. For example, resource status report may include additional bits associated with event-triggered measurement objects. The resources status request may include a PRB usage indicator, a TNL indicator, and a CAC indicator corresponding to a sixth bit, seventh bit, and eighth bit respectively for event-triggered reporting. Additionally, resource status request may include an information element associated with a number of reporting levels. Base station105-b(e.g., target node) may determine a load-level threshold (e.g., for the TNL capacity or the HWL capacity) for each cell, beam, slice, or a combination thereof and divide values below the load-level threshold into the number of reporting levels (e.g., 2, 3, or 5 levels) indicated. The reporting levels may be evenly distributed on a linear scale below the load-level threshold. If the load value changes from one level to the next, exceeds the load-level threshold, or exceed any other preconfigured threshold, base station105-bmay transmit the resource status report indicating the measurement information to base station105-a.

FIG.3illustrates an example of a process flow300in a system that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. In some examples, process flow300may implement aspects of wireless communications system100and wireless communications system200. For example, the process flow300may include node305-aand node305-b, which may be examples of base stations105as described with reference toFIGS.1and2. Additionally, a node305may be an example of a CU, DU, CU-UP, CU-CP, or other node. In some examples, a wireless communication system may support event-triggered MLB. For example, node305-amay request load information from node305-band in response, node305-bmay report traffic load information to node305-abased on whether one or more events are triggered. Node305-aand node305-bmay implement one or more techniques described herein. Alternative examples of the following may be implemented, where steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

At310, node305-bmay transmit a resource status request message to node305-a. In some examples, the resource status request message may be referred to as or be a first message (e.g., a message before a second message), where the first message may request load information from the node305-afor event-triggered MLB between the node305-aand the node305-b. The resources status request message may include a report characteristics IE. The report characteristics IE may contain a bitmap where each position in the bitmap indicates a measurement object to be reported and the frequency at which load information is to be reported. For example, and as shown in Table9, the bitmap may include a first bit, a second bit, and a third bit corresponding to the periodic reporting of PRB usage, TNL capacity, and CAC. Further, for event-triggered traffic reporting, the bitmap may also include a sixth bit, a seventh bit, and an eighth bit corresponding to the event-triggered reporting of PRB, TNL capacity, and CAC, respectively.

The resource status request message may also include an IE indicating a number of reporting levels (e.g., 2, 3, 5, or other number of levels), as illustrated in Table 10. The resource status request may also include information elements indicating the particular beam, cell, or slice, or any combination thereof, for which load information is requested. The cell may be indicated using CGI and the beam may be indicated using SSB indices.

At315, node305-amay determine a traffic load. The load information include in the traffic load may be a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or a combination thereof for each beam, cell, or slice indicated in the resource status request. The traffic load may be based on the report characteristics IE of the resource status request. Additionally or alternatively, node305-amay determine a threshold reporting level (e.g., an overload value for TNL capacity or hardware capacity) and divide the values below the threshold reporting level into the indicated number of reporting levels. That is, node305-amay compute a load scale, which may be based on the number (e.g., quantity or amount) of measurement reporting levels IE.

At320, node305-amay transmit a resource status response message to node305-b. In some examples, the resource status response message may be referred to as or be a second message (e.g., a message after the first message or resource status request message), where the second message may report the determined traffic load. In some examples, the resource status response message may be transmitted periodically as indicated in the report characteristics IE of the resource status report message. Additionally or alternatively, the resource status response message may be transmitted once an event has occurred. For example, the load information may move from reporting level to the next reporting level or the traffic load may exceed the threshold reporting level.

FIG.4illustrates an example of a process flow400in a system that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. In some examples, process flow400may implement aspects of wireless communications system100, wireless communications system200, and process flow300. For example, the process flow400may include base station105-eand base station105-f, which may be examples of base stations105and nodes305as described with reference toFIGS.1through3. In some examples, a wireless communication system may support inter-system MLB. For example, base station105-emay operate in accordance with a first RAT and base station105-fmay operate in accordance with a second RAT. Base station105-emay exchange load information with base station105-f. Base station105-eand base station105-emay implement one or more techniques described herein. Alternative examples of the following may be implemented, where steps are performed in a different order than described or are not performed at all. In some cases, steps may include additional features not mentioned below, or further steps may be added.

At405, base station105-fmay transmit a SON information report message to base station105-e. The SON information report message may include one or more IEs corresponding to a load reporting request. For example, the SON information report message may include a periodic load reporting request IE and event-triggered load reporting request IE. The periodic load reporting request IE may contain IEs indicating cells, beam, and slices for which load information is requested. The event-triggered load reporting request may include an IE indicating a number of measurement reporting level. As described with more detail inFIGS.1and2, base station may determine a threshold reporting level and compute a load scale based on the indicated number of measurement reporting levels.

At410, base station105-emay determine the traffic load. Determining the traffic load may include determining load information for each of the requested beams, cells, or slices. Load information may include a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

At415, base station105-emay transmit a SON information report message to base station105-f. The SON information report message may indicate the requested load information. In some examples, the SON information report message may be transmitted periodically. Additionally or alternatively, the SON information report message may be transmitted once an event has occurred. For example, the load information may move from one reporting level to the next reporting level or the load information may exceed the threshold reporting level.

FIG.5shows a block diagram500of a device505that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The device505may be an example of aspects of a wireless node (e.g., a base station105, a node305, a CU-UP, a CU-CP, a DU, or a CU) as described herein. The device505may include a receiver510, a communications manager515, and a transmitter520. The device505may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Receiver510may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to inter-system and event-triggered MLB). Information may be passed on to other components of the device505. The receiver510may be an example of aspects of the transceiver820or920as described with reference toFIGS.8and9. The receiver510may utilize a single antenna or a set of antennas.

The communications manager515may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager515may also receive, from a second node, a first message for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmit, to the second node, a second message reporting the determined load information.

The communications manager515may also transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node, and determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager515may also transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receive, from the second node, a second message reporting a load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determine to perform the MLB between the first node and the second node based on the load information of the second node. The communications manager515may be an example of aspects of the communications manager810or910as described herein.

The actions performed by the communications manager515as described herein may be implements to realize one or more potential advantages. For example, the inclusion of IEs pertaining to periodic and even-triggered load reporting within an inter-system information report may allow the device505(e.g., a base station105or a node) to exchange load information with other devices505of different RAT technologies. In the event that device505is experiencing high traffic load, upon receiving load information, device505may offload users to other cells of devices505. This may free resources at device505and increase overall network efficiency.

Additionally, by introducing event-triggered reporting into inter-system and intra-system load reporting, a processor of device505(e.g., a processor controlling the receiver510, the communications manager515, the transmitter520, or a combination thereof) may reduce processing of load information used for MLB. For example, in some instance, load information may be sent upon satisfaction of an event (e.g., change in measurement reporting levels, or reaching a threshold) instead of periodically. This may significantly reduce the number of times device505may report load information. Not only may this decrease the processing needed to interpret the load information, but the processing used to construct the load report may also be decreased.

Transmitter520may transmit signals generated by other components of the device505. In some examples, the transmitter520may be collocated with a receiver510in a transceiver module. For example, the transmitter520may be an example of aspects of the transceiver820or920as described with reference toFIGS.8and9. The transmitter520may utilize a single antenna or a set of antennas.

FIG.6shows a block diagram600of a device605that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The device605may be an example of aspects of a device505, a base station105, or a node305as described herein. The device605may include a receiver610, a communications manager615, and a transmitter640. The device605may also include a processor. Each of these components may be in communication with one another (e.g., via one or more buses).

Receiver610may receive information such as packets, user data, or control information associated with various information channels (e.g., control channels, data channels, and information related to inter-system and event-triggered MLB). Information may be passed on to other components of the device605. The receiver610may be an example of aspects of the transceiver820or920as described with reference toFIGS.8and9. The receiver610may utilize a single antenna or a set of antennas.

The communications manager615may be an example of aspects of the communications manager515as described herein. The communications manager615may include a traffic load manager620, a resource status request manager625, a resource status response manager630, and a MLB manager635. The communications manager615may be an example of aspects of the communications manager810or910as described herein.

The traffic load manager620may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT. In some examples, the traffic load manager620may transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The resource status request manager625may receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported.

The traffic load manager620may determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported.

The resource status response manager630may transmit, to the second node, a second message reporting the determined load information.

The traffic load manager620may transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT. In some examples, the traffic load manager620may receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node.

The MLB manager635may determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The resource status request manager625may transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported.

The resource status response manager630may receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported.

The MLB manager635may determine to perform the MLB between the first node and the second node based on the load information of the second node.

Transmitter640may transmit signals generated by other components of the device605. In some examples, the transmitter640may be collocated with a receiver610in a transceiver module. For example, the transmitter640may be an example of aspects of the transceiver820or920as described with reference toFIGS.8and9. The transmitter640may utilize a single antenna or a set of antennas.

FIG.7shows a block diagram700of a communications manager705that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The communications manager705may be an example of aspects of a communications manager515, a communications manager615, or a communications manager810described herein. The communications manager705may include a traffic load manager710, a measurement object identifier component715, a cell identifier component720, a beam identifier component725, a measurement reporting level manager730, a threshold component735, a resource status request manager740, a resource status response manager745, a report characteristics manager750, and a MLB manager755. Each of these modules may communicate, directly or indirectly, with one another (e.g., via one or more buses).

The traffic load manager710may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT. In some examples, transmitting, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

In some examples, the traffic load manager710may determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported. In some examples, the traffic load manager710may transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT.

In some examples, the traffic load manager710may receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node. In some examples, the traffic load manager710may determine load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more information elements of the first information report message including a report of the determined load information.

In some examples, the traffic load manager710may receive, from the second node, a second information report message including one or more information elements including the load reporting request, where the one or more information elements of the second information report message include a periodic load reporting request information element, an event-triggered load reporting request information element, or any combination thereof. In some examples, transmitting the first information report message to the second node based on the determined traffic load triggering the overload state, where an event-triggered load reporting response information element of the first information report message includes the determined load information. In some examples, transmitting the first information report message to the second node based on the determined traffic load satisfying the threshold traffic level, where an event-triggered load reporting response information element of the first information report message includes the determined load information.

In some examples, the traffic load manager710may determine load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof. In some examples, the traffic load manager710may transmit, within the first information report message, a load information request for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more information elements of the first information report message including a periodic load reporting request information element, an event-triggered load reporting request information element, or any combination thereof.

In some examples, the traffic load manager710may receive the second information report message is based on the traffic load triggering an overload state of the second node for a time duration. In some examples, the traffic load manager710may receive the second information report message is based on the traffic load satisfying a threshold traffic level of the second node. In some cases, the load information includes one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

In some cases, the first information report message includes an inter-system SON information report message and is transmitted via an NG interface for a network operating in accordance with the NR RAT or an S1 interface for a network operating in accordance with the E-UTRA RAT.

In some cases, the first node includes a first base station providing a first cell and the second node includes a second base station providing a second cell. In some cases, the load information includes one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof. In some cases, the traffic load of the second node includes one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

In some cases, a periodic load reporting response information element of the second information report message includes load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof. In some cases, the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, are associated with the first RAT or the second RAT.

The resource status request manager740may receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported.

In some examples, the resource status request manager740may transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported. In some cases, the first node or the second node includes a CU of a base station, a DU of a base station, a node associated with a user plane, a node associated with a control plane, a first base station, or a second base station.

The resource status response manager745may transmit, to the second node, a second message reporting the determined load information. In some examples, the resource status response manager745may receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicted number of measurement reporting levels and the indicated measurement objects to be reported.

In some cases, the traffic load includes load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof. In some cases, the load information includes one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

The MLB manager755may determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT. In some examples, the MLB manager755may determine to perform the MLB between the first node and the second node based on the load information of the second node.

The measurement object identifier component715may identify, within the periodic load reporting request information element, a request for load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof. In some cases, determining the traffic load includes determining the load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, where a periodic load reporting response information element of the first information report message includes the determined load information.

The cell identifier component720may identify, within the periodic load reporting request information element, a CGI for each cell of the set of one or more cells, where the load information for the set of one or more cells is based on the identified CGI. In some examples, the cell identifier component720may transmit, within the periodic load reporting request information element, a CGI for each cell of the set of one or more cells, where the load information for the set of one or more cells is based on the CGI.

The beam identifier component725may identify, within the periodic load reporting request information element, an SSB index for each directional beam of the set of one or more directional beams, where the load information for the set of one or more directional beams is based on the identified SSB index. In some examples, the beam identifier component725may transmit, within the periodic load reporting request information element, an SSB index for each directional beam of the set of one or more directional beams, where the load information for the set of one or more directional beams is based on the SSB index. In some cases, the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, are associated with the first RAT or the second RAT.

The measurement reporting level manager730may identify, within the event-triggered load reporting request information element, a measurement reporting level information element including a set of two or more measurement reporting levels. In some examples, the measurement reporting level manager730may identify, within an information element, the indication of the number of measurement reporting levels, the number of measurement reporting levels including a set of two or more measurement reporting levels.

In some examples, transmitting, within the event-triggered load reporting request information element, a measurement reporting level information element including a set of two or more measurement reporting levels, where an event-triggered load reporting response information element of the second information report message includes load information based on the set of two or more measurement reporting levels. In some examples, the measurement reporting level manager730may transmit, within an information element, the indication of the number of measurement reporting level, the number of measurement reporting levels including a set of two or more measurement reporting levels, where the load information is based on the set of two or more measurement reporting levels.

In some cases, the set of two or more measurement reporting levels include a set of uniformly distributed reporting levels, each reporting level of the set of uniformly distributed reporting levels being less than a threshold reporting level of the first node.

The threshold component735may determine that the traffic load has changed from a first measurement reporting level to a second measurement reporting level different from the first measurement reporting level based on the set of two or more measurement reporting levels, where transmitting the first information report message includes transmitting the first information report message to the second node based at least in part on the determination that the traffic load has changed, where an event-triggered load reporting response information element of the first information report message includes the determined load information.

In some examples, the threshold component735may identify that the determined traffic load triggers an overload state of the first node. In some examples, the threshold component735may identify that the determined traffic load satisfies a threshold traffic level of the first node. In some examples, the threshold component735may compute a load scale that corresponds to the set of two or more measurement reporting levels based on the indication, where the determined traffic load is reported based on the set of two or more measurement reporting levels.

The report characteristics manager750may identify, within an information element, the indication of measurement objects to be reported, the measurement objects to be reporting including requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, where the determined traffic load is reported based on requested load metrics.

In some examples, the report characteristics manager750may transmit, within an information element, the indication of measurement objects to be reported, the measurement objects to be reported including requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, where the traffic load is reported based on requested load metrics. In some cases, the indication of the requested load metrics includes one or more entries of a bitmap.

FIG.8shows a diagram of a system800including a device805that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The device805may be an example of or include the components of device505, device605, a node, or a base station105described herein. The device805may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager810, a transceiver820, an antenna825, memory830, a processor840, and an I/O controller850. These components may be in electronic communication via one or more buses (e.g., bus855).

The communications manager810may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager810may also receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting level and an indication of measurement objects to be reported, determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmit, to the second node, a second message reporting the determined load information.

The communications manager810may also transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node, and determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager810may also transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determine to perform the MLB between the first node and the second node based on the load information of the second node.

The memory830may include RAM, ROM, or a combination thereof. The memory830may store computer-readable code835including instructions that, when executed by a processor (e.g., the processor840) cause the device to perform various functions described herein. In some cases, the memory830may contain, among other things, a basic input/output system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.

The I/O controller850may manage input and output signals for the device805. The I/O controller850may also manage peripherals not integrated into the device805. In some cases, the I/O controller850may represent a physical connection or port to an external peripheral. In some cases, the I/O controller850may utilize an operating system such as iOS®, ANDROID®, MS-DOS®, MS-WINDOWS®, OS/2®, UNIX®, LINUX®, or another known operating system. In other cases, the I/O controller850may represent or interact with a modem, a keyboard, a mouse, a touchscreen, or a similar device. In some cases, the I/O controller850may be implemented as part of a processor. In some cases, a user may interact with the device805via the I/O controller850or via hardware components controlled by the I/O controller850.

FIG.9shows a diagram of a system900including a device905that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The device905may be an example of or include the components of device505, device605, a node, or a base station105as described herein. The device905may include components for bi-directional voice and data communications including components for transmitting and receiving communications, including a communications manager910, a network communications manager915, a transceiver920, an antenna925, memory930, a processor940, and an inter-station communications manager945. These components may be in electronic communication via one or more buses (e.g., bus955).

The communications manager910may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT and transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager910may also receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and transmit, to the second node, a second message reporting the determined load information.

The communications manager910may also transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT, receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node, and determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT.

The communications manager910may also transmit, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported, receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported, and determine to perform the MLB between the first node and the second node based on the load information of the second node.

Network communications manager915may manage communications with the core network (e.g., via one or more wired backhaul links). For example, the network communications manager915may manage the transfer of data communications for client devices, such as one or more UEs115.

The memory930may include RAM, ROM, or a combination thereof. The memory930may store computer-readable code935including instructions that, when executed by a processor (e.g., the processor940) cause the device to perform various functions described herein. In some cases, the memory930may contain, among other things, a BIOS which may control basic hardware or software operation such as the interaction with peripheral components or devices.

FIG.10shows a flowchart illustrating a method1000that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The operations of method1000may be implemented by first node or its components as described herein. For example, the operations of method1000may be performed by a communications manager as described with reference toFIGS.5through9. In some examples, a node may execute a set of instructions to control the functional elements of the node to perform the functions described herein. Additionally or alternatively, a node may perform aspects of the functions described herein using special-purpose hardware.

At1005, the first node may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT. The operations of1005may be performed according to the methods described herein. In some examples, aspects of the operations of1005may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1010, the first node may transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT. The operations of1010may be performed according to the methods described herein. In some examples, aspects of the operations of1010may be performed by a traffic load manager as described with reference toFIGS.5through9.

FIG.11shows a flowchart illustrating a method1100that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The operations of method1100may be implemented by a first node or its components as described herein. For example, the operations of method1100may be performed by a communications manager as described with reference toFIGS.5through9. In some examples, a node may execute a set of instructions to control the functional elements of the node to perform the functions described herein. Additionally or alternatively, a node may perform aspects of the functions described herein using special-purpose hardware.

At1105, the first node may determine a traffic load at the first node based on a load reporting request, the first node operating in accordance with a first RAT. The operations of1105may be performed according to the methods described herein. In some examples, aspects of the operations of1105may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1110, the first node may transmit, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements for reporting the determined traffic load, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT. The operations of1110may be performed according to the methods described herein. In some examples, aspects of the operations of1110may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1115, the first node may receive, from the second node, a second information report message including one or more information elements including the load reporting request, where the one or more information elements of the second information report message include a periodic load reporting request information element, an event-triggered load reporting request information element, or any combination thereof. The operations of1115may be performed according to the methods described herein. In some examples, aspects of the operations of1115may be performed by a traffic load manager as described with reference toFIGS.5through9.

FIG.12shows a flowchart illustrating a method1200that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The operations of method1200may be implemented by a first node or its components as described herein. For example, the operations of method1200may be performed by a communications manager as described with reference toFIGS.5through9. In some examples, a node may execute a set of instructions to control the functional elements of the node to perform the functions described herein. Additionally or alternatively, the node may perform aspects of the functions described herein using special-purpose hardware.

At1205, a first node may receive, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported. The operations of1205may be performed according to the methods described herein. In some examples, aspects of the operations of1205may be performed by a resource status request manager as described with reference toFIGS.5through9.

At1210, the first node may determine, at the first node, the load information based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported. The operations of1210may be performed according to the methods described herein. In some examples, aspects of the operations of1210may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1215, the first node may transmit, to the second node, a second message reporting the determined load information. The operations of1215may be performed according to the methods described herein. In some examples, aspects of the operations of1215may be performed by a resource status response manager as described with reference toFIGS.5through9.

FIG.13shows a flowchart illustrating a method1300that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The operations of method1300may be implemented by a first node or its components as described herein. For example, the operations of method1300may be performed by a communications manager as described with reference toFIGS.5through9. In some examples, a node may execute a set of instructions to control the functional elements of the node to perform the functions described herein. Additionally or alternatively, a node may perform aspects of the functions described herein using special-purpose hardware.

At1305, the first node may transmit, to a second node, a first information report message for MLB between the first node and the second node, the first information report message including one or more information elements including a load reporting request, where the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT. The operations of1305may be performed according to the methods described herein. In some examples, aspects of the operations of1305may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1310, the first node may receive, from the second node, a second information report message, the second information report message including one or more information elements reporting a traffic load of the second node. The operations of1310may be performed according to the methods described herein. In some examples, aspects of the operations of1310may be performed by a traffic load manager as described with reference toFIGS.5through9.

At1315, the first node may determine to perform the MLB between the first node and the second node based on the traffic load of the second node, where the first RAT or the second RAT includes an NR RAT or an E-UTRA RAT. The operations of1315may be performed according to the methods described herein. In some examples, aspects of the operations of1315may be performed by a MLB manager as described with reference toFIGS.5through9.

FIG.14shows a flowchart illustrating a method1400that supports inter-system and event-triggered MLB in accordance with aspects of the present disclosure. The operations of method1400may be implemented by a first node, or its components as described herein. For example, the operations of method1400may be performed by a communications manager as described with reference toFIGS.5through9. In some examples, a node may execute a set of instructions to control the functional elements of a node to perform the functions described herein. Additionally or alternatively, a node may perform aspects of the functions described herein using special-purpose hardware.

At1405, the first node may, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message including at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported. The operations of1405may be performed according to the methods described herein. In some examples, aspects of the operations of1405may be performed by a resource status request manager as described with reference toFIGS.5through9.

At1410, the first node may receive, from the second node, a second message reporting the load information of the second node, the load information being based on the indicated number of measurement reporting levels and the indicated measurement objects to be reported. The operations of1410may be performed according to the methods described herein. In some examples, aspects of the operations of1410may be performed by a resource status response manager as described with reference toFIGS.5through9.

At1415, the first node may determine to perform the MLB between the first node and the second node based on the load information of the second node. The operations of1415may be performed according to the methods described herein. In some examples, aspects of the operations of1415may be performed by a MLB manager as described with reference toFIGS.5through9.

Aspect 1: A method for wireless communication at a first node, comprising: determining a traffic load at the first node based at least in part on a load reporting request, the first node operating in accordance with a first RAT; and transmitting, to a second node operating in accordance with a second RAT different from the first RAT, a first information report message for MLB between the first node and the second node, the first information report message comprising one or more IEs for reporting the determined traffic load, wherein the first RAT or the second RAT comprises an NR RAT or an E-UTRA RAT.

Aspect 2: The method of aspect 1, wherein determining the traffic load comprises: determining load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more IEs of the first information report message comprising a report of the determined load information.

Aspect 3: The method of aspect 2, wherein the load information comprises one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

Aspect 4: The method of any of aspects 1 through 3, further comprising: receiving, from the second node, a second information report message comprising one or more IEs comprising the load reporting request, wherein the one or more IEs of the second information report message include a periodic load reporting request IE, an event-triggered load reporting request IE, or any combination thereof.

Aspect 5: The method of aspect 4, further comprising: identifying, within the periodic load reporting request IE, a request for load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, wherein determining the traffic load comprises: determining the load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, wherein a periodic load reporting response IE of the first information report message comprises the determined load information.

Aspect 6: The method of aspect 5, further comprising: identifying, within the periodic load reporting request IE, a CGI for each cell of the set of one or more cells, wherein the load information for the set of one or more cells is based at least in part on the identified CGI.

Aspect 7: The method of any of aspects 5 through 6, further comprising: identifying, within the periodic load reporting request IE, an SSB index for each directional beam of the set of one or more directional beams, wherein the load information for the set of one or more directional beams is based at least in part on the identified SSB index.

Aspect 8: The method of any of aspects 5 through 7, wherein the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof, are associated with the first RAT or the second RAT.

Aspect 9: The method of any of aspects 4 through 8, further comprising: identifying, within the event-triggered load reporting request IE, a measurement reporting level IE comprising a set of two or more measurement reporting levels; and determining that the traffic load has changed from a first measurement reporting level to a second measurement reporting level different from the first measurement reporting level based at least in part on the set of two or more measurement reporting levels, wherein transmitting the first information report message comprises: transmitting the first information report message to the second node based at least in part on the determination that the traffic load has changed, wherein an event-triggered load reporting response IE of the first information report message comprises the determined load information.

Aspect 10: The method of any of aspects 4 through 9, wherein transmitting the first information report message comprises: identifying that the determined traffic load triggers an overload state of the first node; and transmitting the first information report message to the second node based at least in part on the determined traffic load triggering the overload state, wherein an event-triggered load reporting response IE of the first information report message comprises the determined load information.

Aspect 11: The method of any of aspects 4 through 10, wherein transmitting the first information report message comprises: identifying that the determined traffic load satisfies a threshold traffic level of the first node; and transmitting the first information report message to the second node based at least in part on the determined traffic load satisfying the threshold traffic level, wherein an event-triggered load reporting response IE of the first information report message comprises the determined load information.

Aspect 12: The method of any of aspects 1 through 11, wherein the first information report message comprises an inter-system SON information report message and is transmitted via an NG interface for a network operating in accordance with the NR RAT or an S1 interface for a network operating in accordance with the E-UTRA RAT.

Aspect 13: A method for wireless communication at a first node, comprising: receiving, from a second node, a first message requesting load information from the first node for event-triggered MLB between the first node and the second node, the first message comprising at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported; determining, at the first node, the load information based at least in part on the indicated number of measurement reporting levels and the indicated measurement objects to be reported; and transmitting, to the second node, a second message reporting the determined load information.

Aspect 14: The method of aspect 13, further comprising: identifying, within an IE, the indication of the number of measurement reporting levels, the number of measurement reporting levels comprising a set of two or more measurement reporting levels; and computing a load scale that corresponds to the set of two or more measurement reporting levels based at least in part on the indication, wherein the determined load information is reported based at least in part on the set of two or more measurement reporting levels.

Aspect 15: The method of any of aspects 13 through 14, further comprising: identifying, within an IE, the indication of the measurement objects to be reported, the measurement objects to be reported comprising requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, wherein the determined load information is reported based at least in part on the requested load metrics.

Aspect 16: The method of any of aspects 13 through 15, wherein determining the load information comprises: determining the load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof.

Aspect 17: The method of any of aspects 13 through 16, wherein the first node or the second node comprises a CU of a base station, a DU of the base station, a node associated with a user plane, a node associated with a control plane, a first base station, or a second base station.

Aspect 18: A method for wireless communication at a first node, comprising: transmitting, to a second node, a first information report message for MLB between the first node and the second node, the first information report message comprising one or more IEs including a load reporting request, wherein the first node operates in accordance with a first RAT and the second node operates in accordance with a second RAT different from the first RAT; receiving, from the second node, a second information report message, the second information report message comprising one or more IEs reporting a traffic load of the second node; and determining to perform the MLB between the first node and the second node based at least in part on the traffic load of the second node, wherein the first RAT or the second RAT comprises an NR RAT or an E-UTRA RAT.

Aspect 19: The method of aspect 18, wherein transmitting the first information report message comprises: transmitting, within the first information report message, a load information request for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof, the one or more IEs of the first information report message comprising a periodic load reporting request IE, an event-triggered load reporting request IE, or any combination thereof.

Aspect 20: The method of aspect 19, wherein the traffic load of the second node comprises one or more load metrics including a CAC value, a radio resource status indicator, an HWL indicator, a TNL indicator, an uplink/downlink bit rate indicator, a PRB usage indicator, or any combination thereof.

Aspect 21: The method of any of aspects 19 through 20, wherein a periodic load reporting response IE of the second information report message comprises load information for the set of one or more cells, the set of one or more directional beams, the set of one or more network slices, or any combination thereof.

Aspect 22: The method of aspect 21, further comprising: transmitting, within the periodic load reporting request IE, a CGI for each cell of the set of one or more cells, wherein the load information for the set of one or more cells is based at least in part on the CGI.

Aspect 23: The method of any of aspects 21 through 22, further comprising: transmitting, within the periodic load reporting request IE, an SSB index for each directional beam of the set of one or more directional beams, wherein the load information for the set of one or more directional beams is based at least in part on the SSB index.

Aspect 24: The method of any of aspects 19 through 23, further comprising: transmitting, within the event-triggered load reporting request IE, a measurement reporting level IE comprising a set of two or more measurement reporting levels, wherein an event-triggered load reporting response IE of the second information report message comprises load information based at least in part on the set of two or more measurement reporting levels.

Aspect 25: The method of any of aspects 19 through 24, wherein receiving the second information report message is based at least in part on the traffic load triggering an overload state of the second node for a time duration.

Aspect 26: The method of any of aspects 19 through 25, wherein receiving the second information report message is based at least in part on the traffic load satisfying a threshold traffic level of the second node.

Aspect 27: A method for wireless communication at a first node, comprising: transmitting, to a second node, a first message requesting load information from the second node for event-triggered MLB between the first node and the second node, the first message comprising at least an indication of a number of measurement reporting levels and an indication of measurement objects to be reported; receiving, from the second node, a second message reporting the load information of the second node, the load information being based at least in part on the indicated number of measurement reporting levels and the indicated measurement objects to be reported; and determining to perform the MLB between the first node and the second node based at least in part on the load information of the second node.

Aspect 28: The method of aspect 27, further comprising: transmitting, within an IE, the indication of the number of measurement reporting levels, the number of measurement reporting levels comprising a set of two or more measurement reporting levels, wherein the load information is based at least in part on the set of two or more measurement reporting levels.

Aspect 29: The method of any of aspects 27 through 28, further comprising: transmitting, within an IE, the indication of the measurement objects to be reported, the measurement objects to be reported comprising requested load metrics for PRB event triggered load reporting, TNL capacity event triggered load reporting, CAC event triggered load reporting, or any combination thereof, wherein the load information is reported based at least in part on the requested load metrics.

Aspect 30: The method of any of aspects 27 through 29, wherein the load information comprises load information for a set of one or more cells, a set of one or more directional beams, a set of one or more network slices, or any combination thereof.

Aspect 31: An apparatus for wireless communication at a first node, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 1 through 12.

Aspect 32: An apparatus for wireless communication at a first node, comprising at least one means for performing a method of any of aspects 1 through 12.

Aspect 33: A non-transitory computer-readable medium storing code for wireless communication at a first node, the code comprising instructions executable by a processor to perform a method of any of aspects 1 through 12.

Aspect 35: An apparatus for wireless communication at a first node, comprising at least one means for performing a method of any of aspects 13 through 17.

Aspect 36: A non-transitory computer-readable medium storing code for wireless communication at a first node, the code comprising instructions executable by a processor to perform a method of any of aspects 13 through 17.

Aspect 37: An apparatus for wireless communication at a first node, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 18 through 26.

Aspect 38: An apparatus for wireless communication at a first node, comprising at least one means for performing a method of any of aspects 18 through 26.

Aspect 39: A non-transitory computer-readable medium storing code for wireless communication at a first node, the code comprising instructions executable by a processor to perform a method of any of aspects 18 through 26.

Aspect 40: An apparatus for wireless communication at a first node, comprising a processor; memory coupled with the processor; and instructions stored in the memory and executable by the processor to cause the apparatus to perform a method of any of aspects 27 through 30.

Aspect 41: An apparatus for wireless communication at a first node, comprising at least one means for performing a method of any of aspects 27 through 30.

Aspect 42: A non-transitory computer-readable medium storing code for wireless communication at a first node, the code comprising instructions executable by a processor to perform a method of any of aspects 27 through 30.