WO2023113678A1

WO2023113678A1 - Reporting performance impacts associated to load

Info

Publication number: WO2023113678A1
Application number: PCT/SE2022/051156
Authority: WO
Inventors: Luca LUNARDI; Angelo Centonza; Pablo SOLDATI; Julien Muller
Original assignee: Telefonaktiebolaget Lm Ericsson (Publ)
Priority date: 2021-12-16
Filing date: 2022-12-08
Publication date: 2023-06-22

Abstract

A first network node, in a communications network that includes a second network node,can transmit (810) a first message to the second network node requesting one or more performance impact indications associated with resource status information of the second network node. The first network node can receive (830) a second message from the second network node comprising the one or more performance impact indications.

Description

REPORTING PERFORMANCE IMPACTS ASSOCIATED TO LOAD

TECHNICAL FIELD

[0001] The present disclosure is related to wireless communication systems and more particularly to reporting performance impacts associated to load.

BACKGROUND

[0002] FIG. 1 illustrates an example of current 5^th generation radio access network (“NG- RAN”) architecture. The NG-RAN architecture can be further described as follows. The NG- RAN includes a set of 5^th generation (“5G”) base stations (referred to herein as gNBs) connected to the 5^th generation core network (“5GC”) through the next generation (“NG”) network. A gNB can support frequency division duplex (“FDD”) mode, time division duplex (“TDD”) mode or dual mode operation. gNBs can be interconnected through the Xn interface. A gNB can include a gNB-central unit (“CU”) and gNB -distributed units (“DUs”). A gNB-CU and a gNB- DU are connected via a Fl logical interface. One gNB-DU is connected to only one gNB-CU. For resiliency, a gNB-DU may be connected to multiple gNB-CU by appropriate implementation. NG, Xn, and Fl are logical interfaces. The NG-RAN is layered into a Radio Network Layer (“RNL”) and a Transport Network Layer (“TNL”). The NG-RAN architecture (e.g., the NG-RAN logical nodes and interfaces between them) is defined as part of the RNL. For each NG-RAN interface (e.g., NG, Xn, and Fl) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport.

[0003] For NG-RAN, the NG and Xn-C interfaces for a gNB consisting of a gNB-CU and gNB-DUs, terminate in the gNB-CU. For EN-DC, the Sl-U and X2-C interfaces for a gNB including a gNB-CU and gNB-DUs, terminate in the gNB-CU. The gNB-CU and connected gNB-DUs are only visible to other gNBs and the 5GC as a gNB.

[0004] A gNB may also be connected to a long term evolution (“LTE”) base station (referred to herein as an eNB) via an X2 interface. Another architectural option is that where an LTE eNB connected to the Evolved Packet Core network is connected over the X2 interface with a so called nr-gNB. The latter is a gNB not connected directly to a core network (“CN”) and connected via X2 to an eNB for the sole purpose of performing dual connectivity.

[0005] The architecture in FIG. 1 can be expanded by spitting the gNB-CU into two entities. One gNB-CU-user plane (“UP”), which serves the user plane and hosts the packet data convergence protocol (“PDCP”) and one gNB-CU-control plane (“CP”), which serves the control plane and hosts the PDCP and radio resource control (“RRC”) protocol. A gNB-DU hosts the radio link control (“RLC”)/media access control (“MAC”)/physical layer (“PHY”) protocols.

[0006] Other standardization groups, such as the open radio access network (“ORAN”), have further extended the architecture above and have for example split the gNB-DU into two further nodes connected by a fronthaul interface. The lower node of the split gNB-DU can include the PHY protocol and the radio frequency (“RF”) parts, the upper node of the split gNB- DU can host the RLC and MAC. In ORAN the upper node is called O-DU, while the lower node is called O-RU.

[0007] An NG-RAN can also include a set of ng-eNBs, an ng-eNB can include an ng-eNB- CU and one or more ng-eNB-DU(s). An ng-eNB-CU and an ng-eNB-DU can be connected via a W1 interface. While this disclosure may refer generally to gNBs, the general principles may apply to other radio access technologies, for example, the principles may apply to a ng-eNB and W1 interface.

SUMMARY

[0008] There currently exist certain challenges. According to current Mobility Load Balancing signaling solutions, a first network node receiving resource status update from a second network node has very limited knowledge with regard to the fact that, in case mobility load balancing actions are triggered to move some load towards the second network node, the performance at the second network node will be degraded or improved, and to what extent. [0009] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Various embodiments herein define new load related information indicating the performance of the network node sending resource status information for a given load. In some embodiments, such performance impact indications may indicate a number of performance levels experienced by the RAN node at the time of signaling the Resource Status. In some examples, such performance impact indications may be provided on a per node, per cell, per coverage area (e.g., SSB beam coverage area), per transmission point, per PLMN, per service type.

[0010] According to some embodiments, a method of operating a first network node in a communications network that includes a second network node is provided. The method includes transmitting a first message to the second network node requesting one or more performance impact indications associated with resource status information of the second network node. The method further includes receiving a second message from the second network node including the one or more performance impact indications. [0011] According to other embodiments, a method of operating a second network node in a communications network that includes a first network node is provided. The method includes receiving a first message from the first network node requesting one or more performance impact indications associated with resource status information of the second network node. The method further includes transmitting a second message to the first network node including the one or more performance impact indications.

[0012] According to other embodiments, a network node, computer program, computer program product, non-transitory readable-medium, or host is provided to perform one of the methods above.

[0013] In some embodiments, the load balancing process can be enhanced with information concerning the performance level of a RAN node at a given resource utilization status. With this information it is possible to distribute load in an effective way, which can allow optimal RAN performance.

BRIEF DESCRIPTION OF THE DRAWINGS

[0014] The accompanying drawings, which are included to provide a further understanding of the disclosure and are incorporated in and constitute a part of this application, illustrate certain non-limiting embodiments of inventive concepts. In the drawings:

[0015] FIG. 1 is a block diagram illustrating an example of a NG-RAN architecture;

[0016] FIG. 2 is a block diagram illustrating an example of a gNB architecture with separation of gNB-CU-CP and gNB-CU-UP;

[0017] FIG. 3 is a signal flow diagram illustrating an example of a resource status reporting procedure for E-UTRAN and NG-RAN;

[0018] FIG. 4 is a signal flow diagram illustrating an example of operations for reporting performance impacts associated to a load between two network nodes in accordance with some embodiments;

[0019] FIG. 5 is a signal flow diagram illustrating an example of operations for reporting performance impacts associated to a load between two NG-RAN nodes in accordance with some embodiments;

[0020] FIG. 6 is a signal flow diagram illustrating an example of operations for reporting performance impacts associated to a load between a gNB-CU-CP and a gNB-DU in accordance with some embodiments;

[0021] FIG. 7 is a signal flow diagram illustrating an example of operations for reporting performance impacts associated to a load between a gNB-CU-CP and a gNB-CU-UP in accordance with some embodiments; [0022] FIG. 8 is a flow chart illustrating an example of operations of a first network node according to some embodiments of inventive concepts;

[0023] FIG. 9 is a flow chart illustrating an example of operations of a first network node according to some embodiments of inventive concepts;

[0024] FIG. 10 is a block diagram of a communication system in accordance with some embodiments;

[0025] FIG. 11 is a block diagram of a user equipment in accordance with some embodiments

[0026] FIG. 12 is a block diagram of a network node in accordance with some embodiments;

[0027] FIG. 13 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments;

[0028] FIG. 14 is a block diagram of a virtualization environment in accordance with some embodiments; and

[0029] FIG. 15 is a block diagram of a host computer communicating via a base station with a user equipment over a partially wireless connection in accordance with some embodiments in accordance with some embodiments.

DETAILED DESCRIPTION

[0030] Some of the embodiments contemplated herein will now be described more fully with reference to the accompanying drawings. Embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art. Inventive concepts may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of present inventive concepts to those skilled in the art. It should also be noted that these embodiments are not mutually exclusive. Components from one embodiment may be tacitly assumed to be present/used in another embodiment.

[0031] FIG. 2 illustrates an example of an architecture for separation of gNB-CU-CP and gNB-CU-UP. A gNB may consist of a gNB-CU-CP, multiple gNB-CU-UPs and multiple gNB- DUs. The gNB-CU-CP is connected to the gNB-DU through the Fl-C interface. The gNB-CU- UP is connected to the gNB-DU through the Fl-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the El interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. One gNB-DU can be connected to multiple gNB-CU-UPs under the control of the same gNB-CU-CP. One gNB-CU-UP can be connected to multiple DUs under the control of the same gNB-CU-CP.

[0032] For different radio access networks, such as evolved universal mobile telecommunications service terrestrial radio access network (“EUTRAN”), NG-RAN, including Multi-Radio Dual Connectivity options, standard procedures exist to assist a network node to determine load balancing actions.

[0033] For example, the following procedures are defined in 3GPP TS 36.423 vl6.7.0: Resource Status Reporting Initiation (clause 8.3.6); Resource Status Reporting (clause 8.3.7); EN-DC Resource Status Reporting Initiation (clause 8.7.21); and EN-DC Resource Status Reporting (clause 8.7.22). In other examples, the following procedures are defined in 3GPP TS 38.423 vl6.7.0: Resource Status Reporting Initiation (clause 8.4.10); and Resource Status Reporting (clause 8.4.11).

[0034] FIG. 3 illustrates a common pattern used across all the procedures listed above and used for requesting and reporting load related metrics. A first network node requests a second network node to start or stop sending load metrics. The request can indicate if the second network node should send to the first network node load metrics as one-time reporting or according to a reporting period. The second network node responds to the first network node by acknowledging the request or indicating a failure In case the second network node acknowledges the request, the second network node sends to the first network node load metrics as one-time reporting or periodically according to the received indications

[0035] The message used to report load metric can be generically identified as “Resource Status Update” and it assumes slightly different names in the different specifications. In some examples, the message comprising load metric(s) sent from one eNB to another eNB is the X2AP RESOURCE STATUS UPDATE message. In additional or alternative examples, the message comprising load metric(s) sent from one NG-RAN node to another NG-RAN node is the XnAP RESOURCE STATUS UPDATE message. In additional or alternative examples, the message comprising load metric(s) sent between one en-gNB and one eNB is the X2AP EN-DC RESOURCE STATUS UPDATE message.

[0036] According to current Mobility Load Balancing signaling solutions, a first network node receiving resource status update from a second network node has very limited knowledge with regard to the fact that, in case mobility load balancing actions are triggered to move some load towards the second network node, the performance at the second network node will be degraded or improved, and to what extent.

[0037] In some examples, if the resource status reported indicates a Composite Available Capacity of 100% it is expected that mobility towards the reporting node should be avoided. And if the resource status reported indicates a Composite Available Capacity of 0%, the potential target of mobility load balancing actions can be considered as free. Without any more information a load balancing process would be induced to balance load equally between all cells in a neighborhood. Alternatively, the load balancing algorithm may purely react to overload and therefore offload traffic when excessive load is experienced. Hence, any decision in a load balancing process based on current standard is taken from the point of view of monitored load and not from the point of view of the overall performance level changes in the different RAN nodes involved.

[0038] In additional or alternative examples, a first RAN node may experience no performance degradation when serving UEs at loads between 50% and 70% (where load could be represented as e.g., PRB utilization). On the contrary, a neighbor second RAN node may start experiencing performance degradations when load moves above 50%. In such scenario, it would be counterproductive for the first node to offload traffic towards the second RAN node. It might result that the best network status is to keep the second RAN node at loads equal or below 50%, while keeping the first RAN node at loads below 70%.

[0039] The above effect is due to the fact that, at present, the first network node (receiver of resource status updates) has no idea of the effects on performance due to a load transfer towards the second network node.

[0040] Various embodiments herein define new load related information indicating the performance of the network node sending resource status information for a given load. In some embodiments, such performance impact indications may indicate a number of performance levels experienced by the RAN node at the time of signaling the Resource Status. In some examples, such performance impact indications may be provided on a per node, per cell, per coverage area (e.g., SSB beam coverage area), per transmission point, per PLMN, per service type.

[0041] In some examples, the performance level may indicate how well the RAN node is fulfilling QoS requirements for the bearers served for each connected UE.

[0042] In additional or alternative examples, the performance level may indicate the status of utilization of internal node resources such as processing power and memory occupancy. [0043] In additional or alternative examples, the performance level may indicate on a per QoS class basis (e.g. on a per 5QI basis), what is the percentage of UEs served according to requirements and what is the percentage served below requirements.

[0044] In additional or alternative examples, the performance level may state the Energy Consumption of the RAN node or of the parts of the RAN node serving a specific cell. [0045] In additional or alternative embodiments, the receiving RAN node is able to judge whether the load balancing actions taken have produced an increase or a decrease in performance based on the one or more performance impact indicators. The advantage is that load balancing actions are not only taken to balance load, but also to optimize performance. Indeed, in some examples, load balancing actions may totally become dependent on performance changes (e.g., load balancing may be triggered only if performance is maximized, rather than if load is imbalanced).

[0046] In additional or alternative embodiments, a first network node is provided with one or more performance impact indications associated to reported load status measured or predicted in a second network node. In some examples, the first network node transmits a signal to the second network node requesting one or more performance impact indications associated to load status.

[0047] Certain embodiments may provide one or more of the following technical advantages. In some embodiments, the load balancing process can be enhanced with information concerning the performance level of a RAN node at a given resource utilization status. With this information it is possible to distribute load in an effective way, which can allow optimal RAN performance.

[0048] In the present disclosure, a network node can include a RAN node, a gNB, eNB, en- gNB, ng-eNB, gNB-CU, gNB-CU-CP, gNB-CU-UP, gNB-DU, eNB-CU, eNB-CU-CP, eNB- CU-UP, eNB-DU, lAB-node, lAB-donor- DU, lAB-donor-CU, lAB-donor-CU-CP, lAB-donor- CU-UP, IAB-MT, O-CU, O-CU-CP, O-CU-UP, O-DU, O-RU, or O-eNB.

[0049] In some embodiments, a first network node requests a second network node to report to the first network node one or more performances impact indications of the second network node, indicating performances or impact on performances of the second network at the time when measured or predicted resource status information is sent from the second network node to the first network node.

[0050] In additional or alternative embodiments, the second network node sends to the first network node one or more performances impact indications of the second network node, indicating performances of the second network node or impact on performances of the second network node associated to measured or predicted resource status information sent from the second network node to the first network node.

[0051] In additional or alternative embodiments, the first network node receives one or more performances impact indications of the second network node, indicating performances of the second network node or impact on performances of the second network node associated to measured or predicted resource status information sent from the second network node to the first network node.

[0052] In additional or alternative embodiments, the first network node uses the received above information to derive decisions or proposals for radio network optimization, such as load balancing decisions.

[0053] FIGS. 4-7 illustrate examples of operations for reporting performance impacts associated to load. FIG. 4 illustrates an example of communications between two network nodes. FIG. 5 illustrates an example of communications between two NG-RAN nodes. FIG. 6 illustrates an example of communications between a gNB-CU-UP and a gNB-DU. FIG. 7 illustrates an example of communications between a gNB-CU-CP and a gNB-CU-UP.

[0054] In some embodiments, the first network node and/or the second network node can be different RAN nodes (e.g. two gNBs, or two eNBs, or two en-gNBs, or two ng-eNBs).

[0055] In additional or alternative embodiments, the first network node and/or the second network node can be different nodes/functions of a same RAN node (e.g. a gNB-DU and a gNB- CU-CP, or a gNB-CU-CP and a gNB-CU-UP).

[0056] In additional or alternative embodiments, the first network node and/or the second network node can pertain to the same Radio Access Technology (e.g. NR) or to different Radio Access Technologies (e.g., one to NR and the other to LTE).

[0057] In additional or alternative embodiments, the first network node and/or the second network node can pertain to the same RAN system (e.g. NG-RAN) or to different RAN systems (e.g. one to NG-RAN and the other to E-UTRAN).

[0058] In additional or alternative embodiments, the first network node and the second network node may be connected via a direct signaling connection (e.g., two gNB via XnAP), or an indirect signaling connection (e.g., an e-NB and a gNB via S1AP, NGAP and one or more Core Network nodes, for example, an MME and an AMF)

[0059] Operations performed by the first network node are described below.

[0060] In some embodiments, the first network node receives from the second network node one or more SECOND MESSAGE in response to the FIRST MESSAGE and comprising one or more of performances impact indications of the second network node associated to measured and/or predicted resource status information of the second network node.

[0061] A performance impact indication is derived at the point in time when measured and/or predicted resource status information is collected by the RAN node. These parameters are signalled together (e.g. in the same message, or via the same signaling procedure as) or by means of a separate signaling procedure. In an alternative case, the requested performance impact indications may be signaled by the second network node to the first network node together with (e.g. in the same message, or via the same signaling procedure as) the associated measured/predicted resource status information.

[0062] Prior to receiving the SECOND MESSAGE, the first network node can receive from the second network node a THIRD MESSAGE in response to the FIRST MESSAGE to acknowledge at least part of the requests comprised in the FIRST MESSAGE or to fail the requests comprised in the FIRST MESSAGE.

[0063] The THIRD MESSAGE may optionally comprise performances impact indications of the second network node associated to measured and/or predicted resource status information of the second network node as requested in the corresponding FIRST MESSAGE.

[0064] In non-limiting examples a performance impact indication can be represented as an absolute value (e.g. as an integer) or as a percentage (e.g., in a range from 0 to 100) or as a deviation/delta from a reference value, which could be known at the first network node, signaled with the SECOND or THIRD MESSSAGE, or in another alternative provided by the first network node to the second network node with the FIRST MESSAGE.

[0065] Performances impact indications (e.g., performance costs, performance impacts, performance gains, performance indexes, performance statuses, or performance scores or similar terminology) can be associated to one or more of the parameters: a RAN node (e.g., a gNB or an eNB); a network node (e.g., a gNB-DU, or gNB-CU-UP); one or more values or ranges of values of measured or predicted radio resource status information; one or more values or ranges of values of measured or predicted Composite Available Capacity information; one or more values or ranges of values of measured or predicted Transport network layer capacity information; one or more cell(s), SSB area(s), network slice(s), group of cells, group of SSB areas, group of network slices; a Tracking Area, a Tracking Area List, a PLMN; an Area Scope (e.g., used for MDT data collection or for QoE data collection); Guaranteed Bit Rate (“GBR”) services, Non-Guaranteed Bit Rate (“Non-GBR”) services, or both;

GBR, Non-GBR) or both; downlink direction, uplink direction, both downlink and uplink; supplementary uplink or supplementary downlink;

- NR Unlicensed; a carrier frequency;

QoS parameters, (e.g., to guaranteed bit rate in uplink and/or downlink, guaranteed flow bit rate in uplink and/or uplink, maximum bit rate in uplink and/or downlink, maximum packet error rate in downlink or uplink, minimum or maximum delay);

- Energy Saving information or energy saving recommendations/decisions (per network node, per carrier frequency, per coverage area, per cell, per SSB area, per UE, per service type, per network slice, for uplink, downlink or both uplink and downlink); Quality of Experience (“QoE”) information for one or more service types or service subtypes, such as to RAN visible QoE metrics or RAN visible QoE values, e.g. buffer level and Playout delay for media startup for streaming services; and/or a combination of one or more of the above criteria obtained applying logical expression(s) or formula(s) to the combined criteria, for example, a performance impact indication can be associated to a value or range of values for GBR in Uplink for an SSB Area.

[0066] In additional or alternative embodiments, a performance impact indication can refer to: 1) measured levels of performances of the second network node; and/or 2) predicted levels of performances of the second network node

[0067] In additional or alternative embodiments, a performance impact indication can refer to: 1) acceptable levels of performances of the second network node; 2) average levels of performances of the second network node; 3) minimum levels of performances of the second network node; 4) maximum levels of performances of the second network node; 5) residual levels of performances of the second network node; and/or 6) guaranteed levels of performances of the second network node

[0068] In additional or alternative embodiments, levels of performance can refer to one or more: 1) QoS parameters (e.g. bit rate or throughput in downlink/uplink, packet delay, packet loss uplink/downlink, latency, packet delay budget, inter arrival time, burst size); 2) QoE related information, such as RAN visible QoE measurements and/or RAN visible QoE values; 3) Energy saving / energy efficiency / energy consumption information / energy score(s); 4) Hardware resources usage (e.g. memory, processing); 5) Transport network resources usage, for example, this can be relevant in a cloud environment, where a network node may share physical resources with other nodes. The less resources are used, the better; and/or 5) Radio resources usage (e.g., bands, BWP)

[0069] In additional or alternative embodiments, how a performance impact indication (e.g. a performance cost or performance index or a performance impact or performance status) can be associated (e.g. sent together with) to measured and/or predicted resource status information are indicated herein: a performance cost/index/impact/status of value X is associated to a measured or to a predicted Composite Available Capacity Downlink of value Y a performance cost/index/impact/status of value X is associated to a measured or to a predicted Composite Available Capacity Downlink comprised in a range of values between R1 and R2 a performance cost/index/impact/status of value X is associated to a measured or to a predicted Composite Available Capacity Downlink of value Y AND to a measured or to a predicted Composite Available Capacity Uplink of value Z a performance cost/index/impact/status of value X is associated to a measured or to a predicted Composite Available Capacity Downlink of values comprised in a range between R1 and R2 AND to a measured or to a predicted Composite Available Capacity Uplink of values comprised in a range between R3 and R4 a performance cost/index/impact/status of value X is associated to a measured or to a predicted Slice Available Capacity of value Y a performance cost/index/impact/status of value X is associated to a measured or to a predicted Composite Available Capacity Uplink for Normal Uplink of value Y 1 OR to a measured or to a predicted Composite Available Capacity Uplink for Supplementary Uplink of value Y2 a performance cost/index/impact/status of value X is associated to a minimum/maximum/average of measured/predicted Slice Available Capacity Value Downlink and measured/predicted Slice Available Capacity Value Uplink a performance cost/index/impact/status of value X is associated to the range of Resource Status values contained in a message carrying resource status update information, for example the Xn: Resource Status Update message.

[0070] In some embodiments, a FIRST MESSAGE can be realized as an existing message, e g. an XnAP RESOURCE STATUS REQUEST, an X2AP RESOURCE STATUS REQUEST, an X2AP EN-DC RESOURCE STATUS REQUEST, an F1AP RESOURCE STATUS REQUEST.

[0071] In additional or alternative embodiments, a SECOND MESSAGE can be realized as an existing message, e g. an XnAP RESOURCE STATUS UPDATE, an X2AP RESOURCE STATUS UPDATE, an X2AP EN-DC RESOURCE STATUS UPDATE, an F1AP RESOURCE STATUS UPDATE. [0072] In additional or alternative embodiments, in case of acknowledgement (or acknowledgement of at least part of the requests comprised in the FIRST MESSAGE), a THIRD MESSAGE can be realized as an existing message, e.g. an XnAP RESOURCE STATUS RESPONSE, an X2AP RESOURCE STATUS RESPONSE, an X2AP EN-DC RESOURCE STATUS RESPONSE, an F1AP RESOURCE STATUS RESPONSE.

[0073] In additional or alternative embodiments, in case of failure of the second network node to comply to the requests of the first network node comprised in the FIRST MESSAGE, a THIRD MESSAGE can be realized as an existing message, e.g. an XnAP RESOURCE STATUS FAILURE, an X2AP RESOURCE STATUS FAILURE, an X2AP EN-DC RESOURCE STATUS FAILURE, an F1AP RESOURCE STATUS FAILURE.

[0074] Operations performed by the second network node are described below.

[0075] In some embodiments, a second network node receives from a first network node a FIRST MESSAGE comprising a request to send to the first network node one or more of performances impact indications of the second node associated to measured and/or predicted resource status information of the second network node.

[0076] In additional or alternative embodiments, the second network node sends to the first network node one or more SECOND MESSAGE corresponding to the FIRST MESSAGE and comprising one or more of performances impact indications of the second network node associated to measured and/or predicted resource status information of the second network node. [0077] In additional or alternative embodiments, prior to sending the SECOND MESSAGE, the second network node can send to the first network node a THIRD MESSAGE corresponding to the FIRST MESSAGE to acknowledge at least part of the requests comprised in the FIRST MESSAGE or to fail the requests comprised in the FIRST MESSAGE.

[0078] In additional or alternative embodiments, the THIRD MESSAGE may optionally comprise one or more performances impact indications of the second network node associated to measured and/or predicted resource status information of the second network node as requested in the corresponding FIRST MESSAGE.

[0079] In some examples, the term “Performance Cost” is used. This can be equivalent to Performance Index, Performance Impact, Performance Gain, Performance Status, Performance Score, and similar terminology. Such parameter points at the performance level of the node signaling it, where such performance may be measured against different criteria, such as QoS levels with which some or all UEs are served, Energy performance, RAN node resources handling (e.g. low performance may mean that high amounts of memory and processing power is used). [0080] In the description that follows, while the network nodes may be any of the network node 1010A, 1010B, 1200, 1506, hardware 1404, or virtual machine 1408A, 1408B, the network node 1200 shall be used to describe the functionality of the operations of the network nodes. Operations of the network node 1200 (implemented using the structure of FIG. 12) will now be discussed with reference to the flow charts of FIGS. 8-9 according to some embodiments of inventive concepts. For example, modules may be stored in memory 1204 of FIG. 12, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 1202, processing circuitry 1202 performs respective operations of the flow charts.

[0081] FIG. 8 illustrates an example of operations performed by a first network node in a communications network that includes a second network node. At block 810, processing circuitry 1202 transmits, via communication interface 1206, a first message requesting a performance impact indication to the second network node. At block 820, processing circuitry 1202 receives, via communication interface 1206, an acknowledgment message. At block 830, processing circuitry 1202 receives, via communication interface 1206, a second message including the one or more performance impact indications. At block 840, processing circuitry 1202 performs a load balancing procedure based on the one or more performance impact indications.

[0082] FIG. 9 illustrates an example of operations performed by the second network node in the communications network that includes the first network node. At block 910, processing circuitry 1202 receives, via communication interface 1206, a first message requesting one or more performance impact indications. At block 920, processing circuitry 1202 transmits, via communication interface 1206, an acknowledgment message. At block 930, processing circuitry 1202 transmits, via communication interface 1206, a second message including the one or more performance impact indications.

[0083] In some embodiments, the one or more performance impact indications include at least one of: an absolute value; a percentage; and a delta from a reference value.

[0084] In additional or alternative embodiments, the one or more performance impact indications include at least one of: performance costs; performance gains; performance indices; performance impacts; performance statuses; and performance scores.

[0085] In additional or alternative embodiments, the one or more performance impact indications comprise a performance impact indications associated with one or more cells or with one or more reference signals of the second network node.

[0086] In additional or alternative embodiments, the one or more performance impact indications comprise performance impact indications associated with at least one of: radio resource status information; composite available capacity information; transport network layer capacity information; a tracking area; a tracking area list; a public land mobile network; a synchronization signal block, SSB, area; a network slice; a group of cells; a group of SSB areas; a group of network slices; an area scope; a guaranteed bit rate, GBR, service; a non-GBR service; a GBR; a non-GBR; downlink traffic; uplink traffic; new radio unlicensed traffic; a specific frequency of traffic; quality of service parameters; energy saving information; energy efficiency information; energy score information; quality of experience information; hardware resource usage; transport network resource usage; and radio resource usage.

[0087] In additional or alternative embodiments, the one or more performance impact indications include a measured level of performance associated with the resource status information; or a predicted level of performance associated with the resource status information. [0088] In additional or alternative embodiments, the one or more performance impact indications include at least one of: an acceptable level of performance of the second network node; an average level of performance of the second network node; a minimum level of performance of the second network node; a maximum level of performance of the second network node; a residual level of performance of the second network node; and a guaranteed level of performance of the second network node.

[0089] In additional or alternative embodiments, the first includes comprises one of: an XnAP RESOURCE STATUS REQUEST; an X2AP RESOURCE STATUS REQUEST; an X2AP EN-DC RESOURCE STATUS REQUEST; or an F1AP RESOURCE STATUS REQUEST.

[0090] In additional or alternative embodiments, the second message further includes the resource status information. In some examples, the second message includes one of: an XnAP RESOURCE STATUS UPDATE; an X2AP RESOURCE STATUS UPDATE; an X2AP EN- DC RESOURCE STATUS UPDATE; or an Fl AP RESOURCE STATUS UPDATE.

[0091] In additional or alternative embodiments, the second message is separate from a third message including the resource status information.

[0092] In additional or alternative embodiments, the acknowledgement comprises one of: an XnAP RESOURCE STATUS RESPONSE; an X2AP RESOURCE STATUS RESPONSE; an X2AP EN-DC RESOURCE STATUS RESPONSE; or an F1AP RESOURCE STATUS RESPONSE.

[0093] In additional or alternative embodiments, the first network node includes at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node. In additional or alternative embodiments, the second network node includes at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node. In some examples, the first network node and the second network node are portions of a common next generation radio access network (“NG-RAN”) node deployed with distributed architecture.

[0094] Various operations from the flow charts of FIGS. 8-9 may be optional with respect to some embodiments of a network node and related methods. Regarding methods of example embodiment 1 (set forth below), for example, operations of block 820 may be optional.

Regarding methods of example embodiment 20 (set forth below), for example, operations of block 920 may be optional.

[0095] FIG. 10 shows an example of a communication system 1000 in accordance with some embodiments.

[0096] In the example, the communication system 1000 includes a telecommunication network 1002 that includes an access network 1004, such as a radio access network (RAN), and a core network 1006, which includes one or more core network nodes 1008. The access network 1004 includes one or more access network nodes, such as network nodes 1010a and 1010b (one or more of which may be generally referred to as network nodes 1010), or any other similar 3^rd Generation Partnership Project (3 GPP) access node or non-3GPP access point. The network nodes 1010 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1012a, 1012b, 1012c, and 1012d (one or more of which may be generally referred to as UEs 1012) to the core network 1006 over one or more wireless connections.

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

[0098] The UEs 1012 may be any of a wide variety of communication devices, including wireless devices arranged, configured, and/or operable to communicate wirelessly with the network nodes 1010 and other communication devices. Similarly, the network nodes 1010 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1012 and/or with other network nodes or equipment in the telecommunication network 1002 to enable and/or provide network access, such as wireless network access, and/or to perform other functions, such as administration in the telecommunication network 1002. [0099] In the depicted example, the core network 1006 connects the network nodes 1010 to one or more hosts, such as host 1016. These connections may be direct or indirect via one or more intermediary networks or devices. In other examples, network nodes may be directly coupled to hosts. The core network 1006 includes one more core network nodes (e.g., core network node 1008) that are structured with hardware and software components. Features of these components may be substantially similar to those described with respect to the UEs, network nodes, and/or hosts, such that the descriptions thereof are generally applicable to the corresponding components of the core network node 1008. Example core network nodes include functions of one or more of a Mobile Switching Center (MSC), Mobility Management Entity (MME), Home Subscriber Server (HSS), Access and Mobility Management Function (AMF), Session Management Function (SMF), Authentication Server Function (AUSF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), and/or a User Plane Function (UPF).

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

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

[0102] In some examples, the telecommunication network 1002 is a cellular network that implements 3 GPP standardized features. Accordingly, the telecommunications network 1002 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1002. For example, the telecommunications network 1002 may provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs, while providing Enhanced Mobile Broadband (eMBB) services to other UEs, and/or Massive Machine Type Communication (mMTC)/Massive loT services to yet further UEs. [0103] In some examples, the UEs 1012 are configured to transmit and/or receive information without direct human interaction. For instance, a UE may be designed to transmit information to the access network 1004 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1004. Additionally, a UE may be configured for operating in single- or multi-RAT or multi-standard mode. For example, a UE may operate with any one or combination of Wi-Fi, NR (New Radio) and LTE, i.e. being configured for multi-radio dual connectivity (MR-DC), such as E-UTRAN (Evolved- UMTS Terrestrial Radio Access Network) New Radio - Dual Connectivity (EN-DC).

[0104] In the example, the hub 1014 communicates with the access network 1004 to facilitate indirect communication between one or more UEs (e.g., UE 1012c and/or 1012d) and network nodes (e.g., network node 1010b). In some examples, the hub 1014 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1014 may be a broadband router enabling access to the core network 1006 for the UEs. As another example, the hub 1014 may be a controller that sends commands or instructions to one or more actuators in the UEs. Commands or instructions may be received from the UEs, network nodes 1010, or by executable code, script, process, or other instructions in the hub 1014. As another example, the hub 1014 may be a data collector that acts as temporary storage for UE data and, in some embodiments, may perform analysis or other processing of the data. As another example, the hub 1014 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1014 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1014 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1014 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy loT devices. [0105] The hub 1014 may have a constant/persistent or intermittent connection to the network node 1010b. The hub 1014 may also allow for a different communication scheme and/or schedule between the hub 1014 and UEs (e.g., UE 1012c and/or 1012d), and between the hub 1014 and the core network 1006. In other examples, the hub 1014 is connected to the core network 1006 and/or one or more UEs via a wired connection. Moreover, the hub 1014 may be configured to connect to an M2M service provider over the access network 1004 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1010 while still connected via the hub 1014 via a wired or wireless connection. In some embodiments, the hub 1014 may be a dedicated hub - that is, a hub whose primary function is to route communications to/from the UEs from/to the network node 1010b. In other embodiments, the hub 1014 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node 1010b, but which is additionally capable of operating as a communication start and/or end point for certain data channels.

[0106] FIG. 11 shows a UE 1100 in accordance with some embodiments. As used herein, a UE refers to a device capable, configured, arranged and/or operable to communicate wirelessly with network nodes and/or other UEs. Examples of a UE include, but are not limited to, a smart phone, mobile phone, cell phone, voice over IP (VoIP) phone, wireless local loop phone, desktop computer, personal digital assistant (PDA), wireless cameras, gaming console or device, music storage device, playback appliance, wearable terminal device, wireless endpoint, mobile station, tablet, laptop, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), smart device, wireless customer-premise equipment (CPE), vehicle-mounted or vehicle embedded/integrated wireless device, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3 GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0107] A UE may support device-to-device (D2D) communication, for example by implementing a 3 GPP standard for sidelink communication, Dedicated Short-Range Communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle- to-everything (V2X). In other examples, a UE may not necessarily have a user in the sense of a human user who owns and/or operates the relevant device. Instead, a UE may represent a device that is intended for sale to, or operation by, a human user but which may not, or which may not initially, be associated with a specific human user (e.g., a smart sprinkler controller). Alternatively, a UE may represent a device that is not intended for sale to, or operation by, an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter). [0108] The UE 1100 includes processing circuitry 1102 that is operatively coupled via a bus 1104 to an input/output interface 1106, a power source 1108, a memory 1110, a communication interface 1112, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG. 11. The level of integration between the components may vary from one UE to another UE. Further, certain UEs may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

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

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

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

[0112] The memory 1110 may be or be configured to include memory such as random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable readonly memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1110 includes one or more application programs 1114, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1116. The memory 1110 may store, for use by the UE 1100, any of a variety of various operating systems or combinations of operating systems. [0113] The memory 1110 may be configured to include a number of physical drive units, such as redundant array of independent disks (RAID), flash memory, USB flash drive, external hard disk drive, thumb drive, pen drive, key drive, high-density digital versatile disc (HD-DVD) optical disc drive, internal hard disk drive, Blu-Ray optical disc drive, holographic digital data storage (HDDS) optical disc drive, external mini-dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro-DIMM SDRAM, smartcard memory such as tamper resistant module in the form of a universal integrated circuit card (UICC) including one or more subscriber identity modules (SIMs), such as a USIM and/or ISIM, other memory, or any combination thereof. The UICC may for example be an embedded UICC (eUICC), integrated UICC (iUICC) or a removable UICC commonly known as ‘ SIM card.’ The memory 1110 may allow the UE 1100 to access instructions, application programs and the like, stored on transitory or non-transitory memory media, to off-load data, or to upload data. An article of manufacture, such as one utilizing a communication system may be tangibly embodied as or in the memory 1110, which may be or comprise a device-readable storage medium.

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

[0115] In the illustrated embodiment, communication functions of the communication interface 1112 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short- range communications such as Bluetooth, near-field communication, location-based communication such as the use of the global positioning system (GPS) to determine a location, another like communication function, or any combination thereof. Communications may be implemented in according to one or more communication protocols and/or standards, such as IEEE 802.11, Code Division Multiplexing Access (CDMA), Wideband Code Division Multiple Access (WCDMA), GSM, LTE, New Radio (NR), UMTS, WiMax, Ethernet, transmission control protocol/intemet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0116] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1112, via a wireless connection to a network node. Data captured by sensors of a UE can be communicated through a wireless connection to a network node via another UE. The output may be periodic (e.g., once every 15 minutes if it reports the sensed temperature), random (e.g., to even out the load from reporting from several sensors), in response to a triggering event (e.g., when moisture is detected an alert is sent), in response to a request (e.g., a user initiated request), or a continuous stream (e.g., a live video feed of a patient).

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

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

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

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

[0121] FIG. 12 shows a network node 1200 in accordance with some embodiments. As used herein, network node refers to equipment capable, configured, arranged and/or operable to communicate directly or indirectly with a UE and/or with other network nodes or equipment, in a telecommunication network. Examples of network nodes include, but are not limited to, access points (APs) (e.g., radio access points), base stations (BSs) (e.g., radio base stations, Node Bs, evolved Node Bs (eNBs) and NRNodeBs (gNBs)).

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

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

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

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

[0126] In some embodiments, the processing circuitry 1202 includes a system on a chip (SOC). In some embodiments, the processing circuitry 1202 includes one or more of radio frequency (RF) transceiver circuitry 1212 and baseband processing circuitry 1214. In some embodiments, the radio frequency (RF) transceiver circuitry 1212 and the baseband processing circuitry 1214 may be on separate chips (or sets of chips), boards, or units, such as radio units and digital units. In alternative embodiments, part or all of RF transceiver circuitry 1212 and baseband processing circuitry 1214 may be on the same chip or set of chips, boards, or units. [0127] The memory 1204 may comprise any form of volatile or non-volatile computer- readable memory including, without limitation, persistent storage, solid-state memory, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (for example, a hard disk), removable storage media (for example, a flash drive, a Compact Disk (CD) or a Digital Video Disk (DVD)), and/or any other volatile or non-volatile, non-transitory device-readable and/or computer-executable memory devices that store information, data, and/or instructions that may be used by the processing circuitry 1202. The memory 1204 may store any suitable instructions, data, or information, including a computer program, software, an application including one or more of logic, rules, code, tables, and/or other instructions capable of being executed by the processing circuitry 1202 and utilized by the network node 1200. The memory 1204 may be used to store any calculations made by the processing circuitry 1202 and/or any data received via the communication interface 1206. In some embodiments, the processing circuitry 1202 and memory 1204 is integrated.

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

[0129] In certain alternative embodiments, the network node 1200 does not include separate radio front-end circuitry 1218, instead, the processing circuitry 1202 includes radio front-end circuitry and is connected to the antenna 1210. Similarly, in some embodiments, all or some of the RF transceiver circuitry 1212 is part of the communication interface 1206. In still other embodiments, the communication interface 1206 includes one or more ports or terminals 1216, the radio front-end circuitry 1218, and the RF transceiver circuitry 1212, as part of a radio unit (not shown), and the communication interface 1206 communicates with the baseband processing circuitry 1214, which is part of a digital unit (not shown).

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

[0131] The antenna 1210, communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any receiving operations and/or certain obtaining operations described herein as being performed by the network node. Any information, data and/or signals may be received from a UE, another network node and/or any other network equipment.

Similarly, the antenna 1210, the communication interface 1206, and/or the processing circuitry 1202 may be configured to perform any transmitting operations described herein as being performed by the network node. Any information, data and/or signals may be transmitted to a UE, another network node and/or any other network equipment.

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

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

[0134] FIG. 13 is a block diagram of a host 1300, which may be an embodiment of the host 1016 of FIG. 10, in accordance with various aspects described herein. As used herein, the host 1300 may be or comprise various combinations hardware and/or software, including a standalone server, a blade server, a cloud-implemented server, a distributed server, a virtual machine, container, or processing resources in a server farm. The host 1300 may provide one or more services to one or more UEs.

[0135] The host 1300 includes processing circuitry 1302 that is operatively coupled via a bus 1304 to an input/output interface 1306, a network interface 1308, a power source 1310, and a memory 1312. Other components may be included in other embodiments. Features of these components may be substantially similar to those described with respect to the devices of previous figures, such as Figures 11 and 12, such that the descriptions thereof are generally applicable to the corresponding components of host 1300.

[0136] The memory 1312 may include one or more computer programs including one or more host application programs 1314 and data 1316, which may include user data, e.g., data generated by a UE for the host 1300 or data generated by the host 1300 for a UE. Embodiments of the host 1300 may utilize only a subset or all of the components shown. The host application programs 1314 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Versatile Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of UEs (e.g., handsets, desktop computers, wearable display systems, heads-up display systems). The host application programs 1314 may also provide for user authentication and licensing checks and may periodically report health, routes, and content availability to a central node, such as a device in or on the edge of a core network. Accordingly, the host 1300 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 1314 may support various protocols, such as the HTTP Live Streaming (HLS) protocol, Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), Dynamic Adaptive Streaming over HTTP (MPEG-DASH), etc.

[0137] FIG. 14 is a block diagram illustrating a virtualization environment 1400 in which functions implemented by some embodiments may be virtualized. In the present context, virtualizing means creating virtual versions of apparatuses or devices which may include virtualizing hardware platforms, storage devices and networking resources. As used herein, virtualization can be applied to any device described herein, or components thereof, and relates to an implementation in which at least a portion of the functionality is implemented as one or more virtual components. Some or all of the functions described herein may be implemented as virtual components executed by one or more virtual machines (VMs) implemented in one or more virtual environments 1400 hosted by one or more of hardware nodes, such as a hardware computing device that operates as a network node, UE, core network node, or host. Further, in embodiments in which the virtual node does not require radio connectivity (e.g., a core network node or host), then the node may be entirely virtualized.

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

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

[0140] The VMs 1408 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 1406. Different embodiments of the instance of a virtual appliance 1402 may be implemented on one or more of VMs 1408, and the implementations may be made in different ways. Virtualization of the hardware is in some contexts referred to as network function virtualization (NFV). NFV may be used to consolidate many network equipment types onto industry standard high volume server hardware, physical switches, and physical storage, which can be located in data centers, and customer premise equipment. [0141] In the context of NFV, a VM 1408 may be a software implementation of a physical machine that runs programs as if they were executing on a physical, non-virtualized machine. Each of the VMs 1408, and that part of hardware 1404 that executes that VM, be it hardware dedicated to that VM and/or hardware shared by that VM with others of the VMs, forms separate virtual network elements. Still in the context of NFV, a virtual network function is responsible for handling specific network functions that run in one or more VMs 1408 on top of the hardware 1404 and corresponds to the application 1402.

[0142] Hardware 1404 may be implemented in a standalone network node with generic or specific components. Hardware 1404 may implement some functions via virtualization.

Alternatively, hardware 1404 may be part of a larger cluster of hardware (e.g. such as in a data center or CPE) where many hardware nodes work together and are managed via management and orchestration 1410, which, among others, oversees lifecycle management of applications 1402. In some embodiments, hardware 1404 is coupled to one or more radio units that each include one or more transmitters and one or more receivers that may be coupled to one or more antennas. Radio units may communicate directly with other hardware nodes via one or more appropriate network interfaces and may be used in combination with the virtual components to provide a virtual node with radio capabilities, such as a radio access node or a base station. In some embodiments, some signaling can be provided with the use of a control system 1412 which may alternatively be used for communication between hardware nodes and radio units. [0143] FIG. 15 shows a communication diagram of a host 1502 communicating via a network node 1504 with a UE 1506 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1012a of FIG. 10 and/or UE 1100 of FIG. 11), network node (such as network node 1010a of FIG. 10 and/or network node 1200 of FIG. 12), and host (such as host 1016 of FIG. 10 and/or host 1300 of FIG. 13) discussed in the preceding paragraphs will now be described with reference to FIG. 15.

[0144] Like host 1300, embodiments of host 1502 include hardware, such as a communication interface, processing circuitry, and memory. The host 1502 also includes software, which is stored in or accessible by the host 1502 and executable by the processing circuitry. The software includes a host application that may be operable to provide a service to a remote user, such as the UE 1506 connecting via an over-the-top (OTT) connection 1550 extending between the UE 1506 and host 1502. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 1550. [0145] The network node 1504 includes hardware enabling it to communicate with the host 1502 and UE 1506. The connection 1560 may be direct or pass through a core network (like core network 1006 of FIG. 10) and/or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network may be a backbone network or the Internet.

[0146] The UE 1506 includes hardware and software, which is stored in or accessible by UE 1506 and executable by the UE’s processing circuitry. The software includes a client application, such as a web browser or operator-specific “app” that may be operable to provide a service to a human or non-human user via UE 1506 with the support of the host 1502. In the host 1502, an executing host application may communicate with the executing client application via the OTT connection 1550 terminating at the UE 1506 and host 1502. In providing the service to the user, the UE's client application may receive request data from the host's host application and provide user data in response to the request data. The OTT connection 1550 may transfer both the request data and the user data. The UE's client application may interact with the user to generate the user data that it provides to the host application through the OTT connection 1550. [0147] The OTT connection 1550 may extend via a connection 1560 between the host 1502 and the network node 1504 and via a wireless connection 1570 between the network node 1504 and the UE 1506 to provide the connection between the host 1502 and the UE 1506. The connection 1560 and wireless connection 1570, over which the OTT connection 1550 may be provided, have been drawn abstractly to illustrate the communication between the host 1502 and the UE 1506 via the network node 1504, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0148] As an example of transmitting data via the OTT connection 1550, in step 1508, the host 1502 provides user data, which may be performed by executing a host application. In some embodiments, the user data is associated with a particular human user interacting with the UE 1506. In other embodiments, the user data is associated with a UE 1506 that shares data with the host 1502 without explicit human interaction. In step 1510, the host 1502 initiates a transmission carrying the user data towards the UE 1506. The host 1502 may initiate the transmission responsive to a request transmitted by the UE 1506. The request may be caused by human interaction with the UE 1506 or by operation of the client application executing on the UE 1506. The transmission may pass via the network node 1504, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 1512, the network node 1504 transmits to the UE 1506 the user data that was carried in the transmission that the host 1502 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 1514, the UE 1506 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 1506 associated with the host application executed by the host 1502. [0149] In some examples, the UE 1506 executes a client application which provides user data to the host 1502. The user data may be provided in reaction or response to the data received from the host 1502. Accordingly, in step 1516, the UE 1506 may provide user data, which may be performed by executing the client application. In providing the user data, the client application may further consider user input received from the user via an input/output interface of the UE 1506. Regardless of the specific manner in which the user data was provided, the UE 1506 initiates, in step 1518, transmission of the user data towards the host 1502 via the network node 1504. In step 1520, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 1504 receives user data from the UE 1506 and initiates transmission of the received user data towards the host 1502. In step 1522, the host 1502 receives the user data carried in the transmission initiated by the UE 1506.

[0150] One or more of the various embodiments improve the performance of OTT services provided to the UE 1506 using the OTT connection 1550, in which the wireless connection 1570 forms the last segment. More precisely, the teachings of these embodiments may enhance the load balancing process with information concerning the performance level of a RAN node at a given resource utilization status. With this information it is possible to distribute load in an effective way, which can allow optimal RAN performance.

[0151] In an example scenario, factory status information may be collected and analyzed by the host 1502. As another example, the host 1502 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 1502 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 1502 may store surveillance video uploaded by a UE. As another example, the host 1502 may store or control access to media content such as video, audio, VR or AR which it can broadcast, multicast or unicast to UEs. As other examples, the host 1502 may be used for energy pricing, remote control of non-time critical electrical load to balance power generation needs, location services, presentation services (such as compiling diagrams etc. from data collected from remote devices), or any other function of collecting, retrieving, storing, analyzing and/or transmitting data.

[0152] In some examples, a measurement procedure may be provided for the purpose of monitoring data rate, latency and other factors on which the one or more embodiments improve. There may further be an optional network functionality for reconfiguring the OTT connection 1550 between the host 1502 and UE 1506, in response to variations in the measurement results. The measurement procedure and/or the network functionality for reconfiguring the OTT connection may be implemented in software and hardware of the host 1502 and/or UE 1506. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 1550 passes; the sensors may participate in the measurement procedure by supplying values of the monitored quantities exemplified above, or supplying values of other physical quantities from which software may compute or estimate the monitored quantities. The reconfiguring of the OTT connection 1550 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 1504. Such procedures and functionalities may be known and practiced in the art. In certain embodiments, measurements may involve proprietary UE signaling that facilitates measurements of throughput, propagation times, latency and the like, by the host 1502. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 1550 while monitoring propagation times, errors, etc.

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

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

Claims

CLAIMS What is claimed is:

1. A method of operating a first network node (1200) in a communications network that includes a second network node, the method comprising: transmitting (810) a first message to the second network node requesting one or more performance impact indications associated with resource status information of the second network node; receiving (830) a second message from the second network node comprising the one or more performance impact indications.

2. The method of Claim 1, wherein the one or more performance impact indications comprise at least one of: an absolute value; a percentage; and a delta from a reference value.

3. The method of any of Claims 1-2, wherein the one or more performance impact indications comprise at least one of: performance costs; performance impacts; performance gains; performance indices; performance statuses; and performance scores.

4. The method of any of Claims 1-3, wherein the one or more performance impact indications comprise one or more performance impact indications associated with one or more cells or with one or more reference signals of the second network node.

5. The method of any of Claims 1-4, wherein the one or more performance impact indications comprise at least one of: a measured level of performance associated with the resource status information; and a predicted level of performance associated with the resource status information.

6. The method of any of Claims 1-5, wherein the one or more performance impact indications comprise one or more performance impact indications associated with at least one of: radio resource status information; composite available capacity information; and transport network layer capacity information.

7. The method of any of Claims 1-6, wherein the one or more performance impact

33 indications comprise performance impact indications associated with at least one of: a tracking area; a tracking area list; a public land mobile network; a synchronization signal block, SSB, area; a network slice a group of cells; a group of SSB areas; a group of network slices; and an area scope.

8. The method of any of Claims 1-7, wherein the one or more performance impact indications comprise performance impact indications associated with at least one of: a guaranteed bit rate, GBR, service; a non-GBR service; a GBR; and a non-GBR.

9. The method of any of Claims 1-8, wherein the one or more performance impact indications comprise performance impact indications associated with at least one of: downlink traffic; uplink traffic; unlicensed traffic; and a specific frequency of traffic.

10. The method of any of Claims 1-9, wherein the one or more performance impact indications comprise performance impact indications associated with at least one of: quality of service parameters; energy saving information; energy efficiency information; energy score information; quality of experience information; hardware resource usage; transport network resource usage; and radio resource usage.

34

11. The method of any of Claims 1-10, wherein the one or more performance impact indications comprise a measured level of performance associated with the resource status information.

12. The method of any of Claims 1-11, wherein the one or more performance impact indications comprise a predicted level of performance associated with the resource status information.

13. The method of any of Claims 1-12, wherein the one or more performance impact indications comprise at least one of: an acceptable level of performance of the second network node; an average level of performance of the second network node; a minimum level of performance of the second network node; a maximum level of performance of the second network node; a residual level of performance of the second network node; and a guaranteed level of performance of the second network node.

14. The method of any of Claims 1-13, wherein the first message comprises one of: an XnAP RESOURCE STATUS REQUEST; an X2AP RESOURCE STATUS REQUEST; an X2AP EN- DC RESOURCE STATUS REQUEST; or an F1AP RESOURCE STATUS REQUEST.

15. The method of any of Claims 1-14, wherein the second message further comprises the resource status information.

16. The method of Claim 15, wherein the second message further comprises one of: an XnAP RESOURCE STATUS UPDATE; an X2AP RESOURCE STATUS UPDATE; an X2AP EN- DC RESOURCE STATUS UPDATE; or an F1AP RESOURCE STATUS UPDATE.

17. The method of any of Claims 1-14, wherein the second message is separate from a third message comprising the resource status information.

18. The method of any of Claims 1-17, further comprising: responsive to transmitting the first message, receiving (820) an acknowledgment of the first message from the second network node.

19. The method of Claim 18, wherein the acknowledgement comprises one of: an XnAP RESOURCE STATUS RESPONSE; an X2AP RESOURCE STATUS RESPONSE; an X2AP EN-DC RESOURCE STATUS RESPONSE; or an Fl AP RESOURCE STATUS RESPONSE.

20. The method of any of Claims 1-19, further comprising: performing (840) a load balancing procedure based on the one or more performance impact indications.

21. The method of any of Claims 1-20, wherein the first network node comprises at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node, and wherein the second network node comprises at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node.

22. A method of operating a second network node (1200) in a communications network that includes a first network node, the method comprising: receiving (910) a first message from the first network node requesting one or more performance impact indications associated with resource status information of the second network node; and transmitting (930) a second message to the first network node comprising the one or more performance impact indications.

23. The method of Claim 22, wherein the one or more performance impact indications comprise at least one of: an absolute value; a percentage; and a delta from a reference value, and wherein the one or more performance impact indications further comprises at least one of: performance costs; performance impacts; performance gains; performance indices; performance statuses; and performance scores.

24. The method of any of Claims 22-23, wherein the one or more performance impact indications comprise a performance impact indication associated with one or more cells or with one or more reference signals of the second network node.

25. The method of any of Claims 22-24, wherein the one or more performance impact indications comprise performance impact indications associated with at least one of: radio resource status information; composite available capacity information; transport network layer capacity information; a tracking area; a tracking area list; a public land mobile network; a synchronization signal block, SSB, area; a network slice; a group of cells; a group of SSB areas; a group of network slices; an area scope; a guaranteed bit rate, GBR, service; a non-GBR service; a GBR; a non-GBR; downlink traffic; uplink traffic; unlicensed traffic; a specific frequency of traffic; quality of service parameters; energy saving information; energy efficiency information; energy score information; quality of experience information; hardware resource usage; transport network resource usage; and radio resource usage.

26. The method of any of Claims 22-25, wherein the one or more performance impact indications comprise: a measured level of performance associated with the resource status information; or a predicted level of performance associated with the resource status information.

27. The method of any of Claims 22-26, wherein the one or more performance impact indications comprise at least one of: an acceptable level of performance of the second network

37 node; an average level of performance of the second network node; a minimum level of performance of the second network node; a maximum level of performance of the second network node; a residual level of performance of the second network node; and a guaranteed level of performance of the second network node.

28. The method of any of Claims 22-27, wherein the first message comprises one of: an XnAP RESOURCE STATUS REQUEST; an X2AP RESOURCE STATUS REQUEST; an X2AP EN- DC RESOURCE STATUS REQUEST; or an F1AP RESOURCE STATUS REQUEST.

29. The method of any of Claims 22-28, wherein the second message further comprises the resource status information, and wherein the second message further comprises one of: an XnAP RESOURCE STATUS UPDATE; an X2AP RESOURCE STATUS UPDATE; an X2AP EN-DC RESOURCE STATUS UPDATE; or an F1AP RESOURCE STATUS UPDATE.

30. The method of any of Claims 22-28, wherein the second message is separate from a third message comprising the resource status information.

31. The method of any of Claims 22-30, further comprising: responsive to receiving the first message, transmitting (920) an acknowledgment of the first message to the first network node, wherein the acknowledgement comprises one of: an XnAP RESOURCE STATUS RESPONSE; an X2AP RESOURCE STATUS RESPONSE; an X2AP EN-DC RESOURCE STATUS RESPONSE; or an F1AP RESOURCE STATUS RESPONSE.

32. The method of any of Claims 22-31, wherein the first network node comprises at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node, and wherein the second network node comprises at least one of a: a radio access network, RAN, node; a central unit control plane, CU-CP, node; a central unit user plane, CU-UP, node; and a distributed unit, DU, node.

33. A first network node (1200) in a communications network that includes a second network node (1200) comprising: processing circuitry (1202); and

38 memory (1204) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first network node to perform operations according to any of Claims 1-21.

34. A first network node (1200) in a communications network that includes a second network node (1200) and is adapted to perform according to any of Claims 1-21.

35. A computer program comprising program code to be executed by processing circuitry (1202) of a first network node (1200) in a communications network that includes a second network node (1200), whereby execution of the program code causes the first network node to perform operations according to any of Claims 1-21.

36. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1202) of a first network node (1200) in a communications network that includes a second network node (1200), whereby execution of the program code causes the first network node to perform operations according to any of Claims 1- 21.

37. A second network node (1200) in a communications network that includes a first network node (1200) comprising: processing circuitry (1202); and memory (1204) coupled with the processing circuitry, wherein the memory includes instructions that when executed by the processing circuitry causes the first network node to perform operations according to any of Claims 22-32.

38. A second network node (1200) in a communications network that includes a first network node (1200) and is adapted to perform according to any of Claims 22-32.

39. A computer program comprising program code to be executed by processing circuitry (1202) of a second network node (1200) in a communications network that includes a first network node (1200), whereby execution of the program code causes the second network node to perform operations according to any of Claims 22-32.

40. A computer program product comprising a non-transitory storage medium including program code to be executed by processing circuitry (1202) of a second network node (1200) in

39 a communications network that includes a first network node (1200), whereby execution of the program code causes the second network node to perform operations according to any of Claims 22-32.

40