CALCULATION OF PHYSICAL RESOURCE BLOCK UTILIZATION IN MULTI- TRANSMISSION POINTS TRANSMISSION TECHNICAL FIELD [0001] The present disclosure is related to wireless communication systems and more particularly to calculation of physical resource block (“PRB”) utilization in multi-transmission points transmission. BACKGROUND [0002] FIG.1 illustrates an example of current 5th generation radio access network (“NG- RAN”) architecture. The NG-RAN architecture can be further described as follows. The NG- RAN includes a set of 5th generation (“5G”) base stations (referred to herein as gNBs) connected to the 5th 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 F1 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 F1 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 F1) the related TNL protocol and the functionality are specified. The TNL provides services for user plane transport and signaling transport. [0003] A gNB may also be connected to a long term evolution (“LTE”) base station (referred to herein as an eNB) via the 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. [0004] 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. [0005] The architecture illustrated in FIG.1 is an example of what the 3rd generation partnership project (“3GPP”) has defined for 5G. 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. SUMMARY [0006] According to some embodiments, a method of operating a network node in a communications network is provided. The method includes, for each of a number (N(T)) of respective samples over a period of time (T), determining a respective number (M11jk(T)) of physical resource blocks (“PRBs”) used for traffic transmission for a first communication device (UE ₁ ) on a single multiple-input-multiple-output (“MIMO”) layer per transmission point (“TRP”) (k) for the respective sample. The method further includes, for each of the number (N(T)) of respective samples over the period of time (T), determining a respective number (L _1jk (T)) of MIMO layers from a single TRP (k) scheduled for the first communication device (UE1) for the respective sample. The method further includes, determining a PRB usage value (M(T)) for the period of time (T) based on the respective number (M11jk(T)) of PRBs used for traffic transmission for the first communication device (UE ₁ ) on the single MIMO layer per TRP (k) for each of the number (N(T)) of respective samples over the period of time (T) and based on the respective number (L1jk(T)) of MIMO layers from the single TRP (k) scheduled for the first communication device (UE ₁ ) for each of the number (N(T)) of respective samples over the period of time (T). [0007] According to other embodiments, a method of operating a network node in a communications network is provided. The method includes, for each of a number (N(T)) of respective samples over a period of time (T), determining a respective number (M1 _ijk (T)) of physical resource blocks (“PRBs”) used for traffic transmission for each of a plurality of communication devices (UEi) on a single massive input multiple output (“MIMO”) layer per transmission point (“TRP”) (TRP _k ) for the respective sample. The method further includes, for each of the number (N(T)) of respective samples over the period of time (T), determining a respective number (Lijk(T)) of MIMO layers from a single TRP (TRPk) scheduled for each of the plurality of communication devices (UE _i ) for the respective sample. The method further includes determining a PRB usage value (M(T)) for the period of time (T) based on the respective number (M1ijk(T)) of PRBs used for traffic transmission for each of the plurality of communication devices (UE _i ) on a single MIMO layer per TRP (TRP _k ) for each of the number (N(T)) of respective samples over the period of time (T) and based on the respective number (L _ijk (T)) of MIMO layers from a single TRP (TRP _k ) scheduled for each of the plurality of communication devices (UE _i ) for each of the number (N(T)) of respective samples over the period of time (T). [0008] According to other embodiments, a method performed by a network node for calculating physical resource block (“PRB”) utilization in multi-transmission point (“mTRP”) transmission is provided. The method includes receiving transmission point (“TRP”) load information from a second network node. The method further includes determining an optimal TRP in the second network node for mTRP configuration at a communication device. The method further includes configuring the communication device with mTRP communication. [0009] According to other embodiments, a network node, a host, a computer program, a computer program product, or a non-transitory computer-readable medium is provided to perform one of the methods above. BRIEF DESCRIPTION OF THE DRAWINGS [0010] 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: [0011] FIG.1 is a block diagram illustrating an example of a NG-RAN architecture; [0012] FIG.2 is a table illustrating an example of a definition for PDSCH PRB usage for MIMO in the DL per cell; [0013] FIG.3 is a table illustrating an example of a parameter description for PDSCH PRB usage for MIMO in the DL per cell; [0014] FIG.4 is a table illustrating an example of a definition for PDSCH PRB usage for MIMO in the UL per cell; [0015] FIG.5 is a table illustrating an example of a parameter description for PDSCH PRB usage for MIMO in the UL per cell; [0016] FIG.6 is a table illustrating an example of a definition for PDSCH PRB usage based on statistical MIMO layer in the DL per cell; [0017] FIG.7 is a table illustrating an example of a parameter description for PDSCH PRB usage based on statistical MIMO layer in the DL per cell; [0018] FIG.8 is a table illustrating an example of a definition for PDSCH PRB usage based on statistical MIMO layer in the UL per cell; [0019] FIG.9 is a table illustrating an example of a parameter description for PDSCH PRB usage based on statistical MIMO layer in the UL per cell; [0020] FIG.10 is a table illustrating an example of elements in a formula for calculating a total PDSCH PRB usage per cell according to some embodiments of inventive concepts; [0021] FIG.11 is a table illustrating an example of elements in another formula for calculating a total PDSCH PRB usage per cell according to some embodiments of inventive concepts; [0022] FIG.12 is a table illustrating an example of elements in a formula for calculating a total PUSCH PRB usage per cell according to some embodiments of inventive concepts; [0023] FIG.13 is a table illustrating an example of elements in another formula for calculating a total PUSCH PRB usage per cell according to some embodiments of inventive concepts; [0024] FIG.14 is a table illustrating an example of PRB utilization for different sampling instances according to some embodiments of inventive concepts; [0025] FIG.15 is a signal flow diagram illustrating an example of per TRP load information exchange for optimal multi-TRP configuration at the UE according to some embodiments of inventive concepts; [0026] FIGS.16-17 are flow charts illustrating an example of operations of a network node according to some embodiments of inventive concepts; [0027] FIG.18 is a block diagram of a communication system in accordance with some embodiments; [0028] FIG.19 is a block diagram of a user equipment in accordance with some embodiments [0029] FIG.20 is a block diagram of a network node in accordance with some embodiments; [0030] FIG.21 is a block diagram of a host computer communicating with a user equipment in accordance with some embodiments; [0031] FIG.22 is a block diagram of a virtualization environment in accordance with some embodiments; and [0032] FIG.23 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 [0033] 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. [0034] Physical resource block (“PRB”) utilization for multiple-input-multiple-output (“MIMO”) systems is described below. [0035] Physical downlink shared channel (“PDSCH”) PRB usage for MIMO in the downlink (“DL”) per cell is described below. This measurement provides the total usage (in percentage) of PDSCH PRBs for MIMO in the DL per cell. An objective of the measurement is to measure usage of time and frequency resources. A use-case is operations, administration, and maintenance (“OAM”) performance observability. [0036] FIG.2 is a table illustrating an example of a definition for PDSCH PRB usage for MIMO in the DL per cell. [0037] FIG.3 is a table illustrating an example of a parameter description for PDSCH PRB usage for MIMO in the DL per cell. [0038] Physical uplink shared channel (“PUSCH”) PRB usage for MIMO in the uplink (“UL”) per cell is described below. This measurement provides the total usage (in percentage) of PUSCH PRBs for MIMO in the UL per cell. An objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. [0039] FIG.4 is a table illustrating an example of a definition for PUSCH PRB usage for MIMO in the UL per cell. [0040] FIG.5 is a table illustrating an example of a parameter description for PUSCH PRB usage for MIMO in the UL per cell. [0041] Multi-transmission points (“TRP”) transmission is described below. [0042] Inter-cell multi-TRP (“mTRP”) is described below. [0043] In Rel-17, 3GPP is going to standardize what is called inter-cell mTRP. That is justified in the Work Item Description (“WID”) RP-193133 (Further enhancements on MIMO for NR) in the following objective: Enhancement on the support for multi-TRP deployment, targeting both FR1 and FR2: a. […] b. Identify and specify QCL/TCI-related enhancements to enable inter-cell multi-TRP operations, assuming multi-DCI based multi-PDSCH reception c. […] [0044] When discussions in Rel-17 started in RAN2, the following agreements were made in RAN2#114e concerning the so-called Scenario 1: Inter-cell multi-TRP-like model: RAN2 confirm the simplified procedures on the inter-cell multi-TRP-like model as a baseline RAN2 understanding: Scenario 1: Inter-cell multi-TRP-like model 1. UE receives from serving cell, configuration of SSBs of the TRP with different PCI for beam measurement, and configurations needed to use radio resources for data transmission/reception incl resources for different PCIs. 2. UE performs beam measurement for the TRP with different PCI and report it to serving cell. 3. Based on the above reports, TCI state(s) associated to the TRP with different PCI is activated from the serving cell (by L1/L2 signaling). 4. UE receives and transmits using UE-dedicated channel on TRP with different PCI. 5. UE should be in coverage of a serving cell always, also for multi-TRP case, e.g. UE should use common channels BCCH PCH etc. from the serving cell (as in legacy). [0045] Discussion of Scenario 1 continued in RAN2#115 and the following suboptions were identified: FFS whether common framework is feasible to support both “inter-cell beam management” and “inter-cell multi-TRP” considering differences/similarities between two operations. R2 assumes at least TCI state information is required for TRP with different PCI. R2 further discuss RRC parameters based on RAN1 RRC parameters andor R1 reply LS. At R2115-e the following RRC models is/were on the table: Option 1: Cell, Option 2: BWP, Option 3: beam resource (e.g. TCI state, QCL-info), Option 4: new structure (on high level similar to either of the other options) [0046] These options are describing how the “configurations needed to use radio resources for data transmission/reception incl resources for different PCIs” is organized within the UEs dedicated RRC configuration. [0047] RAN2 is currently discussing possible RRC models for configuring inter-cell mTRP for Rel-17, which might be also called inter-cell beam management operation. [0048] Option 1: Cell, is described below. [0049] In this option, TRP with different PCI is defined as an independent cell the following aspects are summarized based on [R2-2107948], [R2-2108478], [R2-2108632]. . This new cell is always “associated” with a legacy serving cell via the inter-cell mTRP operation. In Rel-17, the two cells share the same frequency. . The secondary TRP cell (Assisting Cell) can have same or different C-RNTI than the associated primary cell (Main cell). . The configuration of the secondary TRP cells (Assisting Cell) for addition, modification, and release is done by RRC signaling. . Every legacy serving cell (SpCell or SCell) can have an associated secondary TRP cell. . When Assisting Cell is used for UL, RLM should follow Assisting Cell signals (FFS whether this is part of Main cell (legacy serving cell) or as separate Assisting Cell RLM). [0050] There could be different sub-options derived from option 1, such as the following:. Each inter-cel lmTRP configuration has its own ServingCellConfig (so the UE is configured with multiple ServingCellConfig(s), one per TRP) and its own ServingCellConfigCommon (so the UE is configured with multiple ServingCellConfig(s), one per TRP); . Each inter-cell TRP configuration has its own ServingCellConfig (so the UE is configured with multiple ServingCellConfig(s), one per TRP), but there is a single ServingCellConfigCommon, possibly associated to the initial PCell (the PCell the UE initially connects to and/or performs reconfiguration with sync). [0051] Option 2: BWP, is described below. [0052] In this option, TRP with different PCI is modelled as additional BWP. The following aspects are summarized based on [R2-2107585] and [R2-2108632]. . Configure the different TRP as the different BWP, and the TRP activation/deactivation can be achieved via the BWP switching mechanism. . the common configuration would be kept for source cell i.e. UE keep monitoring the source cell’s common channel. . For the TRP with different PCI, it has the full set of the PxxCH configuration, and the full set of common and dedicated configuration. Switching to TRP with different PCI is based on L1 signaling [0053] Option 3: Beam resource (e.g. TCI state, QCL-info), is described below. [0054] In this option, TRP with different PCI is modelled as a dedicated resource to enable separate beam i.e. separate TCI-state/QCL-info. The following is summarized based on [R2- 2107906], [R2-2108632], [R2-2108656], [R2-2108807]. . The additional SSB set(s) from non-serving cell (TRP with different PCI) is configured within the serving cell configuration and be associated with an index. This index can then be used associating TCI states, CSI measurement configurations, potential UL configurations, etc to the additional SSB set (PCI). . TCI state is also configured in serving cell configuration but assigned with SSB index associated to the different PCI. . In inter-cell multi-TRP operation, the CORESETPoolIndex with value 0 is associated with the serving cell, while CORESETPoolIndex with value 1 is associated with the non-serving cell. . All other configuration in BWP could be shared by neighbor cell except for PHY dedicated channels (PxxCH) . Cell-specific parameters for neighbor TRPs/Cells are shared with the source cell or cell-specific parameters are not needed on the neighbor TRPs/Cells e.g. RACH is not needed on the neighbor cell and RACH is triggered by PDCCH-command if needed. It is assumed that TA is always aligned between source and neighbor cell. . SSB related information of the non-serving PCI is included in the CSI configuration to configure CSI for TRP with different PCI. [0055] One sub-option derived from option 3 is the following: . The inter-cell mTRP configurations are within a single ServingCellConfig and there is a single ServingCellConfigCommon, even though there may be PCI-specific configurations. [0056] Option 4: New structure, is described below. [0057] In [R2-2107415], a new approach is proposed, in which a new IE (e.g. NonServingCellConfig) is defined to include all non-serving cell information (i.e. TRP with different PCI). . Non-serving cell SSB information (at least SSB time domain position, SSB transmission periodicity, SSB transmission power) are needed in inter-cell MTRP operation:. . PCI of non-serving cell is included in the new IE (e.g. NonServingCellConfig) for non-serving cell. . An index of non-serving cell with corresponding configurations is introduced to associate with TCI state. [0058] In Option 1 and 2 all physical layer configuration parameters may be set differently among the TRPs while Option 3 most parameters are shared. Option 4 is ASN1 coding specific hybrid which may coincide to option 1 or option 3. [0059] Inter-cell multi-TRP (mTRP) in Rel-18 and possibly 6G is described below. [0060] In the last RAN plenary meeting the scope of Rel-18, currently called 5G Advanced is being discussion. Inter-cell beam management is one of the main topics in the area of mobility enhancements. Although it is not clear what exact solution would be adopted in Rel-18 in comparison to Rel-17 inter-cell mTRP, one possible different is that while in Rel-17 the UE relies on control channels from a single serving cell, while it possibly receive/ transmit data from/to other cells (dedicated channels having TCI state whose QCL source is associated to a reference signal with Physical Cell Identity of that other cell), in Rel-18 it might also be possible to use common channels from these other cells. For example, Rel-17 may end up modeling inter-cell mTRP as in option 3, while in Rel-18 as in option 1. However, these difference may not be fundamental for the present invention, i.e., the invention is likely applicable in Rel-17 scenario, but also in a possible Rel-18 scenario for inter-cell mTRP. [0061] In the email discussion in the RAN plenary # 93, the following is part of the agreed scope for mobility enhancements: [0062] 1. Configuration and maintenance for multiple candidate cells; [0063] In 5G times, some topics from the 4G evolution made in the first 5G release (Release-15). It may also happen that 5G evolution topics, e.g., from 5G advanced, become part of the 6G standard. Inter-cell beam management / inter-cell mTRP are topics that may gain some attention in 6G times. And, if one solution is adopted in 5G evolution, another solution may be adopted in 6G. [0064] Current Progress in 3GPP is described below. [0065] In 3GPP SA5 meeting, average value of scheduled MIMO layer per PRB on the DL and UL was discussed and the CR S5-215332 was agreed. Based on the agreement, some contribution was proposed in RAN2 meeting to enhance the agreed formulae. The proposed enhanced formulae are as follows. [0066] FIG.6 is a table illustrating an example of a definition for PDSCH PRB usage based on statistical MIMO layer in the DL per cell. [0067] FIG.7 is a table illustrating an example of a parameter description for PDSCH PRB usage based on statistical MIMO layer in the DL per cell. [0068] PUSCH PRB Usage based on statistical MIMO layer in the UL per cell is described below. This measurement provides the total usage (in percentage) of PUSCH physical resource blocks (PRBs) for MIMO based on statistical MIMO layer in the uplink per cell. The objective of the measurement is to measure usage of time and frequency resources. A use-case is OAM performance observability. [0069] FIG.8 is a table illustrating an example of a definition for PUSCH PRB usage based on statistical MIMO layer in the UL per cell. [0070] FIG.9 is a table illustrating an example of a parameter description for PUSCH PRB usage based on statistical MIMO layer in the UL per cell. [0071] There currently exist certain challenges. [0072] The current standard formula and the proposed new formula assume that a UE would have same number of MIMO layers in a given occasion. This assumption does not hold for an intra-cell multi-TRP transmission towards the UE. In multi-TRP transmission, each TRP can potentially use a different number of MIMO layers for transmission towards a UE. [0073] In some examples, there are two UEs in the cell and two TRPs serving both of the UEs. For TRP-1 between 0-40 ms: UE-1 is scheduled with 10% of the PRBs and with 2 layer MIMO and UE-2 is scheduled with 90% of the PRBs and with 1 layer MIMO. For TRP-1 between 41-100 ms: UE-1 is scheduled with 40% of the PRBs and with 1 layer MIMO and UE-2 is scheduled with 60% of the PRBs and with 2 layer MIMO. For TRP -2 between 0-40 ms: UE- 1 is scheduled with 90% of the PRBs and with 1 layer MIMO and UE-2 is scheduled with 10% of the PRBs and with 2 layer MIMO. For TRP-2 between 41-100 ms: UE-1 is scheduled with 60% of the PRBs and with 2 layer MIMO and UE-2 is scheduled with 40% of the PRBs and with 1 layer MIMO. [0074] In this example, between 0-40 ms, for some PRBs, UE-1 has 3-layer MIMO and for some has 1-layer MIMO. Similar observation is valid for UE-2. However, current formula does not capture this dynamic nature of MIMO layer allocation and requires some additional changes. The current method used to calculate the average PRB utilization is restricted to the assumption that at a given time instance, a UE can be scheduled with only a fixed number of MIMO layers in a given cell across the entire bandwidth in which the UE is scheduled. [0075] The problem extends to how PRB utilization is calculated at the RAN side in case of multi TRP transmission. Two different RAN nodes can exchange PRB utilization information and other metrics that allow to derive how much resources are available in a given cell. For multi TRP transmission across different RAN nodes (e.g. across different gNB-DUs or across different gNBs) it is not possible to understand how much resources are available at one TRP. The latter is due to an inaccurate way of expressing PRB utilization for one TRP. [0076] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. An enhanced formula for PRB utilization in Multi-TRP deployments that takes into account the dynamic changes in the number of MIMO layers used and the changes in the allocated PRBs for each user during the measurement period is proposed. The proposed formula is a triple summation over the time, number of UEs, and number of TRPs to calculate total PRB utilization in the measurement period from where a percentage utilization is calculated. [0077] In some embodiments, a network node calculates a total PRB utilization per TRP. From such utilization the node serving the TRP can derive the available resources at one TRP, namely the available capacity. These metrics (e.g. PRB utilization per TRP, available capacity per TRP) can be exchanged between RAN nodes to enable an appropriate choice of optimal TRPc for multi TRP configuration for a UE. [0078] In additional or alternative embodiments, a formula is proposed to calculate PRB utilization in case of Multi-TRP deployment and to allow a RAN node to derive an accurate PRB utilization and available capacity per TRP, which can be exchanged with neighbour RAN nodes for optimal TRP selection for multi TRP communication for a UE [0079] Certain embodiments may provide one or more of the following technical advantages. Some embodiments allow a network to calculate PRB utilization (both DL and UL) and available capacity of a cell taking account of multi-TRP deployment, utilization of MIMO techniques and dynamic properties of PRB allocation. The invention allows the RAN node serving the TRP for which the resource utilization and available capacity to exchange such parameters with neighbour nodes and to enable optimal configuration of multi TRP communication for a UE, across different RAN nodes (e.g., across different gNB-DUs or across different O-RUs). [0080] In some embodiments, an averaging procedure enhances the formula from to calculate DL and UL PRB utilizations for multi-TRP deployment. [0081] PDSCH PRB utilization in the DL for Multi-TRP is described below. [0082] In some embodiments, total PDSCH PRB usage per cell M(T) is calculated using the following formula: Where, [0083] FIG.10 is a table illustrating an example of elements in the above formula for calculating a total PDSCH PRB usage per cell. [0084] In additional or alternative embodiments, the value Alpha is defined as: [0085] In additional or alternative embodiments, the value Alpha is defined as: where N(k) is the total number of TRPs. [0086] In additional or alternative embodiments, the value Alpha is configurable by the network. [0087] In additional or alternative embodiments, the proposed formula for DL in is enhanced according to the following: Where, [0088] FIG.11 is a table illustrating an example of elements in the above formula for calculating a total PDSCH PRB usage per cell. [0089] In additional or alternative embodiments, the value β is defined as: [0090] In additional or alternative embodiments, the value β is defined as: whereN(k) is the total number of TRPs. [0091] In additional or alternative embodiments, the valueβ is configurable by the network. [0092] PUSCH PRB Usage for Multi-TRP is described below [0093] In some embodiments, total PUSCH PRB usage per cell N(k) is calculated using the following formula: Where, [0094] FIG.12 is a table illustrating an example of elements in the above formula for calculating a total PUSCH PRB usage per cell. [0095] In additional or alternative embodiments, the value Alpha is defined as: [0096] In additional or alternative embodiments, the value Alpha is defined as: where N(k) is the total number of TRPs. [0097] In additional or alternative embodiments, the value Alpha is configurable by the network. [0098] In additional or alternative embodiments, the proposed formula for UL is enhanced according to the following: Where, [0099] FIG.13 is a table illustrating an example of elements in the above formula for calculating a total PUSCH PRB usage per cell. [0100] In additional or alternative embodiments, the value β is defined as: [0101] In additional or alternative embodiments, the value β is defined as: where N(k) is the total number of TRPs. [0102] In additional or alternative embodiments, the value β is configurable by the network. [0103] In some examples, there are two UEs in the cell and two TRPs serving both of the UEs. For TRP-1 between 0-40 ms: UE-1 is scheduled with 10% of the PRBs and with 2 layer MIMO and UE-2 is scheduled with 90% of the PRBs and with 1 layer MIMO. For TRP-1 between 41-100 ms: UE-1 is scheduled with 40% of the PRBs and with 1 layer MIMO and UE-2 is scheduled with 60% of the PRBs and with 2 layer MIMO. For TRP -2 between 0-40 ms: UE- 1 is scheduled with 90% of the PRBs and with 1 layer MIMO and UE-2 is scheduled with 10% of the PRBs and with 2 layer MIMO. For TRP-2 between 41-100 ms: UE-1 is scheduled with 60% of the PRBs and with 2 layer MIMO and UE-2 is scheduled with 40% of the PRBs and with 1 layer MIMO. [0104] In some embodiments, M(T) as can be determined as follows (assumption: sampling interval = 10ms and measurement period, T = 100ms and Alpha =3 for each TRP. Hence, number of samples taken during sampling interval is 10). FIG.14 is a table illustrating an example of information for determining M(T) for this example. The PRB utilization can be calculated as: M(T) × 100 23.33% [0105] Hence, the total PRB utilization is 23.33%. [0106] In additional or alternative embodiments, the formula above is used to derive the total PRB utilization per TRP in UL and DL. Namely, this can be derived by summing all the PRB utilizations for the traffic served by a TRP for each connected UE. With such calculation the RAN node serving the TRP is also able to derive the overall available capacity for a given TRP. This can be derived in a number of ways such as: . Knowing the total number of PRBs at a TRP and deriving the un-utilised PRBs for that TRP. This metric gives the absolute number of available PRBs . Knowing the total number of PRBs at a TRP and deriving the un-utilised PRBs for that TRP. Dividing this by the total number of PRBs one can derive the available PRB percentage at the TRP . Taking a linear scale, where value 0 equals no capacity and value 100 equals a maximum capacity value configured a priori and representing the percentage of available PRBs as a value along such linear scale. This can be called composite available TRP capacity. [0107] In additional or alternative embodiments, the RAN Node 1 serving the TRP may request to another RAN node 2 to report its PRB utilization per TRP potentially together with its Composite Available TRP Capacity. The RAN Node 2 may reply with an acceptance to such request and after that it may start reporting on an event basis or in a periodic way, the requested load metrics. [0108] Assuming that the TRPs in RAN Node 2 can be selected to configure a UE served by RAN Node 1 with multi TRP communication, where some TRPs are served by RAN Node 1 and some others by RAN Node 2, the information exchange described above can enable RAN Node 1 to select the optimal TRP in RAN Node 2 for such UE configuration. This is because RAN Node 1 will be able to select the RAN Node 2 TRP with the best radio performance (e.g. best signal strength) combined with the best resource availability. [0109] It needs to be highlighted that PRB utilization and PRB available capacity and the consequent exchange of TRP load information between RAN nodes can be also achieved via a different PRB utilization formula than that described in the methods above. [0110] FIG.15 is a signal flow diagram illustrating an example of per TRP load information exchange for optimal multi TRP configuration at the UE. [0111] At block 1510, the NG-RAN Node 1 and NG-RAN Node 2 calculate the PRB utilization per TRP for their served UEs. PRB utilization and available capacity per TRP can be also calculated. [0112] At block 1520, NG-RAN Node 1 transmits a request to NG-RAN Node 2 to subscribe to receiving per TRP load information. [0113] At block 1530, NG-RAN Node 2 transmits an accept/reject/partial-accept response to the request. [0114] At block 1540, NG-RAN Node 2 transmits periodic or event based per TRP load information. [0115] At block 1550, NG-RAN Node 1 makes a decision on optimal TRP in NG-RAN Node 2 for multi TRP configuration at the UE. [0116] At block 1560, NG-RAN Node 1 transmits configuration information to the UE configuring the UE with multi-TRP communication. [0117] In the description that follows, while the network node may be any of the network node 1810A, 1810B, 2000, 2306, hardware 2204, or virtual machine 2208A, 2208B, the network node 2000 shall be used to describe the functionality of the operations of the network node. Operations of the network node 2000 (implemented using the structure of FIG.20) will now be discussed with reference to the flow charts of FIGS.16-17 according to some embodiments of inventive concepts. For example, modules may be stored in memory 2004 of FIG.20, and these modules may provide instructions so that when the instructions of a module are executed by respective network node processing circuitry 2002, processing circuitry 2002 performs respective operations of the flow charts. [0118] FIG.16 illustrates an example of operations performed by a network node for calculating PRB utilization in mTRP transmission. [0119] At block 1601, for each of a number (N(T)) of respective samples (j) over a period of time (T), processing circuitry 2002 determines a respective number (M1ijk(T)) of physical resource blocks PRBs used for traffic transmission for each of a plurality of communication devices (UEi) on single MIMO layer per TRP (k) for the respective sample (j). [0120] At block 1603, for each of the number (N(T)) of respective samples over the period of time (T), processing circuitry 2002 determines a respective number (Lijk(T)) of multiple input multiple output MIMO layers from a single TRP (k) scheduled for each of the plurality of communication devices (UEi) for the respective sample (j). [0121] At block 1605, for each of the number (N(T)) of respective samples over the period of time (T) for each of the plurality of communication devices (UEi) for each of the TRP (k), processing circuitry 2002 determines a product of the respective number (M1ijk(T)) of PRBs used for traffic transmission for a respective one of the plurality of communication device (UEi) on single MIMO layer per TRP (k) during the respective sample (j) and the respective number (Lijk(T)) of MIMO layers from a single TRP (k) scheduled for the respective one of the plurality of communication devices (UEi) during the respective sample (j). [0122] At block 1607, for the period of time (T), processing circuitry 2002 determines a summation of the products for each of the number of respective samples over the period of time (T) for each of the plurality of communication devices (UEi). [0123] At block 1609, processing circuitry 2002 determines a PRB usage value (M(T)) for the period of time (T) based on the respective number (M1ijk(T)) of PRBs for each of the TRP for each of the plurality of communication devices (UEi) for each of the number (N(T)) of respective samples over the period of time (T) and based on the respective number (L _ijk (T)) of MIMO layers from a single TRP scheduled for each of the TRP for each of plurality of communication devices (UEi) for each of the number (N(T)) of respective samples over the period of time (T). More particularly, processing circuitry 2002 may determine the PRB usage value (M(T)) based on the summation of the products for each of the respective samples over the time period (T) for each of the plurality of communication devices (UEi) for each of the TRP. [0124] At block 1611, processing circuitry 2002 transmits (through a network interface) an indication of the PRB usage value (M(T)) for the period of time (T) to a second network node. For example, the indication of the PRB usage value (M(T)) may be transmitted to a second RAN node and/or to a core network CN node (e.g., an operations, administration, and maintenance OAM node of the CN). [0125] At block 1615, processing circuitry 2002 performs load balancing between cells of the network node based on the PRB usage value (M(T)). [0126] Various operations from the flow chart of FIG.16 may be optional with respect to some embodiments of RAN nodes and related methods. Regarding methods of example embodiments 1 and 11 (set forth below), for example, operations of blocks 1605, 1607, 1611, and 1615 may be optional. [0127] FIG.17 illustrates an example of operations performed by a network node (independently or in addition to the operations of FIG.16). [0128] At block 1710, processing circuitry 2002 receives TRP load information from a second network node. At block 1720, processing circuitry 2002 determines an optimal TRP in the second network node for mTRP configuration at a communication device. At block 1730, processing circuitry 2002 configures the communication device with mTRP communication. [0129] Various operations from the flow chart of FIG.17 may be optional with respect to some embodiments of network nodes and related methods. [0130] FIG.18 shows an example of a communication system 1800 in accordance with some embodiments. [0131] In the example, the communication system 1800 includes a telecommunication network 1802 that includes an access network 1804, such as a radio access network (RAN), and a core network 1806, which includes one or more core network nodes 1808. The access network 1804 includes one or more access network nodes, such as network nodes 1810a and 1810b (one or more of which may be generally referred to as network nodes 1810), or any other similar 3rd Generation Partnership Project (3GPP) access node or non-3GPP access point. The network nodes 1810 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs 1812a, 1812b, 1812c, and 1812d (one or more of which may be generally referred to as UEs 1812) to the core network 1806 over one or more wireless connections. [0132] 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 1800 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 1800 may include and/or interface with any type of communication, telecommunication, data, cellular, radio network, and/or other similar type of system. [0133] The UEs 1812 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 1810 and other communication devices. Similarly, the network nodes 1810 are arranged, capable, configured, and/or operable to communicate directly or indirectly with the UEs 1812 and/or with other network nodes or equipment in the telecommunication network 1802 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 1802. [0134] In the depicted example, the core network 1806 connects the network nodes 1810 to one or more hosts, such as host 1816. 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 1806 includes one more core network nodes (e.g., core network node 1808) 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 1808. 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). [0135] The host 1816 may be under the ownership or control of a service provider other than an operator or provider of the access network 1804 and/or the telecommunication network 1802, and may be operated by the service provider or on behalf of the service provider. The host 1816 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. [0136] As a whole, the communication system 1800 of FIG.18 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. [0137] In some examples, the telecommunication network 1802 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network 1802 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network 1802. For example, the telecommunications network 1802 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 IoT services to yet further UEs. [0138] In some examples, the UEs 1812 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 1804 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network 1804. 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). [0139] In the example, the hub 1814 communicates with the access network 1804 to facilitate indirect communication between one or more UEs (e.g., UE 1812c and/or 1812d) and network nodes (e.g., network node 1810b). In some examples, the hub 1814 may be a controller, router, content source and analytics, or any of the other communication devices described herein regarding UEs. For example, the hub 1814 may be a broadband router enabling access to the core network 1806 for the UEs. As another example, the hub 1814 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 1810, or by executable code, script, process, or other instructions in the hub 1814. As another example, the hub 1814 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 1814 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub 1814 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub 1814 then provides to the UE either directly, after performing local processing, and/or after adding additional local content. In still another example, the hub 1814 acts as a proxy server or orchestrator for the UEs, in particular in if one or more of the UEs are low energy IoT devices. [0140] The hub 1814 may have a constant/persistent or intermittent connection to the network node 1810b. The hub 1814 may also allow for a different communication scheme and/or schedule between the hub 1814 and UEs (e.g., UE 1812c and/or 1812d), and between the hub 1814 and the core network 1806. In other examples, the hub 1814 is connected to the core network 1806 and/or one or more UEs via a wired connection. Moreover, the hub 1814 may be configured to connect to an M2M service provider over the access network 1804 and/or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes 1810 while still connected via the hub 1814 via a wired or wireless connection. In some embodiments, the hub 1814 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 1810b. In other embodiments, the hub 1814 may be a non-dedicated hub – that is, a device which is capable of operating to route communications between the UEs and network node 1810b, but which is additionally capable of operating as a communication start and/or end point for certain data channels. [0141] FIG.19 shows a UE 1900 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 (3GPP), including a narrow band internet of things (NB-IoT) UE, a machine type communication (MTC) UE, and/or an enhanced MTC (eMTC) UE. [0142] A UE may support device-to-device (D2D) communication, for example by implementing a 3GPP 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). [0143] The UE 1900 includes processing circuitry 1902 that is operatively coupled via a bus 1904 to an input/output interface 1906, a power source 1908, a memory 1910, a communication interface 1912, and/or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in FIG.19. 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. [0144] The processing circuitry 1902 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 1910. The processing circuitry 1902 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 1902 may include multiple central processing units (CPUs). [0145] In the example, the input/output interface 1906 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 1900. 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. [0146] In some embodiments, the power source 1908 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 1908 may further include power circuitry for delivering power from the power source 1908 itself, and/or an external power source, to the various parts of the UE 1900 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source 1908. Power circuitry may perform any formatting, converting, or other modification to the power from the power source 1908 to make the power suitable for the respective components of the UE 1900 to which power is supplied. [0147] The memory 1910 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 read- only memory (EEPROM), magnetic disks, optical disks, hard disks, removable cartridges, flash drives, and so forth. In one example, the memory 1910 includes one or more application programs 1914, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data 1916. The memory 1910 may store, for use by the UE 1900, any of a variety of various operating systems or combinations of operating systems. [0148] The memory 1910 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 1910 may allow the UE 1900 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 1910, which may be or comprise a device-readable storage medium. [0149] The processing circuitry 1902 may be configured to communicate with an access network or other network using the communication interface 1912. The communication interface 1912 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna 1922. The communication interface 1912 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 1918 and/or a receiver 1920 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter 1918 and receiver 1920 may be coupled to one or more antennas (e.g., antenna 1922) and may share circuit components, software or firmware, or alternatively be implemented separately. [0150] In the illustrated embodiment, communication functions of the communication interface 1912 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/internet protocol (TCP/IP), synchronous optical networking (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), and so forth. [0151] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface 1912, 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). [0152] 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. [0153] A UE, when in the form of an Internet of Things (IoT) 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 IoT 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 IoT device comprises circuitry and/or software in dependence of the intended application of the IoT device in addition to other components as described in relation to the UE 1900 shown in FIG.19. [0154] As yet another specific example, in an IoT 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 3GPP 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. [0155] 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. [0156] FIG.20 shows a network node 2000 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 NR NodeBs (gNBs)). [0157] 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). [0158] 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). [0159] The network node 2000 includes a processing circuitry 2002, a memory 2004, a communication interface 2006, and a power source 2008. The network node 2000 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 2000 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 2000 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory 2004 for different RATs) and some components may be reused (e.g., a same antenna 2010 may be shared by different RATs). The network node 2000 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node 2000, 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 2000. [0160] The processing circuitry 2002 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 2000 components, such as the memory 2004, to provide network node 2000 functionality. [0161] In some embodiments, the processing circuitry 2002 includes a system on a chip (SOC). In some embodiments, the processing circuitry 2002 includes one or more of radio frequency (RF) transceiver circuitry 2012 and baseband processing circuitry 2014. In some embodiments, the radio frequency (RF) transceiver circuitry 2012 and the baseband processing circuitry 2014 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 2012 and baseband processing circuitry 2014 may be on the same chip or set of chips, boards, or units. [0162] The memory 2004 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 2002. The memory 2004 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 2002 and utilized by the network node 2000. The memory 2004 may be used to store any calculations made by the processing circuitry 2002 and/or any data received via the communication interface 2006. In some embodiments, the processing circuitry 2002 and memory 2004 is integrated. [0163] The communication interface 2006 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 2006 comprises port(s)/terminal(s) 2016 to send and receive data, for example to and from a network over a wired connection. The communication interface 2006 also includes radio front-end circuitry 2018 that may be coupled to, or in certain embodiments a part of, the antenna 2010. Radio front-end circuitry 2018 comprises filters 2020 and amplifiers 2022. The radio front-end circuitry 2018 may be connected to an antenna 2010 and processing circuitry 2002. The radio front-end circuitry may be configured to condition signals communicated between antenna 2010 and processing circuitry 2002. The radio front-end circuitry 2018 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 2018 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters 2020 and/or amplifiers 2022. The radio signal may then be transmitted via the antenna 2010. Similarly, when receiving data, the antenna 2010 may collect radio signals which are then converted into digital data by the radio front-end circuitry 2018. The digital data may be passed to the processing circuitry 2002. In other embodiments, the communication interface may comprise different components and/or different combinations of components. [0164] In certain alternative embodiments, the network node 2000 does not include separate radio front-end circuitry 2018, instead, the processing circuitry 2002 includes radio front-end circuitry and is connected to the antenna 2010. Similarly, in some embodiments, all or some of the RF transceiver circuitry 2012 is part of the communication interface 2006. In still other embodiments, the communication interface 2006 includes one or more ports or terminals 2016, the radio front-end circuitry 2018, and the RF transceiver circuitry 2012, as part of a radio unit (not shown), and the communication interface 2006 communicates with the baseband processing circuitry 2014, which is part of a digital unit (not shown). [0165] The antenna 2010 may include one or more antennas, or antenna arrays, configured to send and/or receive wireless signals. The antenna 2010 may be coupled to the radio front-end circuitry 2018 and may be any type of antenna capable of transmitting and receiving data and/or signals wirelessly. In certain embodiments, the antenna 2010 is separate from the network node 2000 and connectable to the network node 2000 through an interface or port. [0166] The antenna 2010, communication interface 2006, and/or the processing circuitry 2002 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 2010, the communication interface 2006, and/or the processing circuitry 2002 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. [0167] The power source 2008 provides power to the various components of network node 2000 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source 2008 may further comprise, or be coupled to, power management circuitry to supply the components of the network node 2000 with power for performing the functionality described herein. For example, the network node 2000 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 2008. As a further example, the power source 2008 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. [0168] Embodiments of the network node 2000 may include additional components beyond those shown in FIG.20 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 2000 may include user interface equipment to allow input of information into the network node 2000 and to allow output of information from the network node 2000. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node 2000. [0169] FIG.21 is a block diagram of a host 2100, which may be an embodiment of the host 1816 of FIG.18, in accordance with various aspects described herein. As used herein, the host 2100 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 2100 may provide one or more services to one or more UEs. [0170] The host 2100 includes processing circuitry 2102 that is operatively coupled via a bus 2104 to an input/output interface 2106, a network interface 2108, a power source 2110, and a memory 2112. 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 19 and 20, such that the descriptions thereof are generally applicable to the corresponding components of host 2100. [0171] The memory 2112 may include one or more computer programs including one or more host application programs 2114 and data 2116, which may include user data, e.g., data generated by a UE for the host 2100 or data generated by the host 2100 for a UE. Embodiments of the host 2100 may utilize only a subset or all of the components shown. The host application programs 2114 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 2114 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 2100 may select and/or indicate a different host for over-the-top services for a UE. The host application programs 2114 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. [0172] FIG.22 is a block diagram illustrating a virtualization environment 2200 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 2200 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. [0173] Applications 2202 (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. [0174] Hardware 2204 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 2206 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs 2208a and 2208b (one or more of which may be generally referred to as VMs 2208), and/or perform any of the functions, features and/or benefits described in relation with some embodiments described herein. The virtualization layer 2206 may present a virtual operating platform that appears like networking hardware to the VMs 2208. [0175] The VMs 2208 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer 2206. Different embodiments of the instance of a virtual appliance 2202 may be implemented on one or more of VMs 2208, 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. [0176] In the context of NFV, a VM 2208 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 2208, and that part of hardware 2204 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 2208 on top of the hardware 2204 and corresponds to the application 2202. [0177] Hardware 2204 may be implemented in a standalone network node with generic or specific components. Hardware 2204 may implement some functions via virtualization. Alternatively, hardware 2204 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 2210, which, among others, oversees lifecycle management of applications 2202. In some embodiments, hardware 2204 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 2212 which may alternatively be used for communication between hardware nodes and radio units. [0178] FIG.23 shows a communication diagram of a host 2302 communicating via a network node 2304 with a UE 2306 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE 1812a of FIG.18 and/or UE 1900 of FIG.19), network node (such as network node 1810a of FIG.18 and/or network node 2000 of FIG.20), and host (such as host 1816 of FIG.18 and/or host 2100 of FIG.21) discussed in the preceding paragraphs will now be described with reference to FIG.23. [0179] Like host 2100, embodiments of host 2302 include hardware, such as a communication interface, processing circuitry, and memory. The host 2302 also includes software, which is stored in or accessible by the host 2302 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 2306 connecting via an over-the-top (OTT) connection 2350 extending between the UE 2306 and host 2302. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection 2350. [0180] The network node 2304 includes hardware enabling it to communicate with the host 2302 and UE 2306. The connection 2360 may be direct or pass through a core network (like core network 1806 of FIG.18) 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. [0181] The UE 2306 includes hardware and software, which is stored in or accessible by UE 2306 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 2306 with the support of the host 2302. In the host 2302, an executing host application may communicate with the executing client application via the OTT connection 2350 terminating at the UE 2306 and host 2302. 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 2350 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 2350. [0182] The OTT connection 2350 may extend via a connection 2360 between the host 2302 and the network node 2304 and via a wireless connection 2370 between the network node 2304 and the UE 2306 to provide the connection between the host 2302 and the UE 2306. The connection 2360 and wireless connection 2370, over which the OTT connection 2350 may be provided, have been drawn abstractly to illustrate the communication between the host 2302 and the UE 2306 via the network node 2304, without explicit reference to any intermediary devices and the precise routing of messages via these devices. [0183] As an example of transmitting data via the OTT connection 2350, in step 2308, the host 2302 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 2306. In other embodiments, the user data is associated with a UE 2306 that shares data with the host 2302 without explicit human interaction. In step 2310, the host 2302 initiates a transmission carrying the user data towards the UE 2306. The host 2302 may initiate the transmission responsive to a request transmitted by the UE 2306. The request may be caused by human interaction with the UE 2306 or by operation of the client application executing on the UE 2306. The transmission may pass via the network node 2304, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step 2312, the network node 2304 transmits to the UE 2306 the user data that was carried in the transmission that the host 2302 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step 2314, the UE 2306 receives the user data carried in the transmission, which may be performed by a client application executed on the UE 2306 associated with the host application executed by the host 2302. [0184] In some examples, the UE 2306 executes a client application which provides user data to the host 2302. The user data may be provided in reaction or response to the data received from the host 2302. Accordingly, in step 2316, the UE 2306 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 2306. Regardless of the specific manner in which the user data was provided, the UE 2306 initiates, in step 2318, transmission of the user data towards the host 2302 via the network node 2304. In step 2320, in accordance with the teachings of the embodiments described throughout this disclosure, the network node 2304 receives user data from the UE 2306 and initiates transmission of the received user data towards the host 2302. In step 2322, the host 2302 receives the user data carried in the transmission initiated by the UE 2306. [0185] One or more of the various embodiments improve the performance of OTT services provided to the UE 2306 using the OTT connection 2350, in which the wireless connection 2370 forms the last segment. More precisely, the teachings of these embodiments may allow a source node to determine whether to configure or not configure the SHR to the UE, and thereby saving configuration signaling and UE memory consumption. [0186] In an example scenario, factory status information may be collected and analyzed by the host 2302. As another example, the host 2302 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host 2302 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host 2302 may store surveillance video uploaded by a UE. As another example, the host 2302 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 2302 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. [0187] 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 2350 between the host 2302 and UE 2306, 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 2302 and/or UE 2306. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection 2350 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 2350 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node 2304. 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 2302. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection 2350 while monitoring propagation times, errors, etc. [0188] 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. [0189] 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.