Receiving and sending information

Abstract

According to an example, a method performed by a first network node for receiving information is provided The method comprises receiving, from a second network node, information identifying one or more cells and / or carriers and, for each cell or carrier, one or more identifiers of one or more groups of hardware resources associated with the cell or carrier.

Description

[0001] RECEIVING AND SENDING INFORMATION

[0002] Technical Field

[0003] Examples of this disclosure relate to sending and receiving information, for example sending and receiving information identifying energy consumption of one or more groups of hardware resources.

[0004] Background

[0005] The current 5th Generation Radio Access Network (5G RAN), also referred to as NG-RAN, architecture is illustrated in Figure 1 and described in the 3rd Generation Partnership Project (3GPP) Technical Specification (TS) 38.401 v17.2.0 as follows. The NG-RAN consists of a set of gNodeBs (gNBs) connected to the 5th Generation Core (5GC) through the NG interface. As specified in 3GPP TS 38.300, the NG-RAN could also consist of a set of ng- eNodeBs (ng-eNBs). An ng-eNB may consist of an ng-eNB-Centralized Unit (CU) and one or more ng-eNB-Distributed Units (DUs). An ng-eNB-CU and an ng-eNB-DU are connected via W1 interface. The general principle described here also applies to ng-eNB and W1 interface, if not explicitly specified otherwise.

[0006] 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 may consist of a gNB-CU and one or more gNB-DU(s). A gNB-CU and a gNB-DU is connected via F1 interface. One gNB-DU is connected to only one gNB-CU. NG, Xn, and F1 are logical interfaces.

[0007] 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 Evolved Non-standalone Dual Connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB consisting of 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.

[0008] The overall architecture for separation of gNB-CU-Control Plane (CP) and gNB-CU-User Plane (UP) is depicted in Figure 2. 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 F1-C interface. The gNB-CU-UP is connected to the gNB-DU through the F1-U interface. The gNB-CU-UP is connected to the gNB-CU-CP through the E1 interface. One gNB-DU is connected to only one gNB-CU-CP. One gNB-CU-UP is connected to only one gNB-CU-CP. The architecture shown in Figures 1 and 2 is what 3GPP has defined for 5G. Other standardization groups, such as the O-RAN Alliance, have further extended the architecture above and have, for example, split the gNB-Dll into two further nodes connected by a fronthaul interface. Figure 3 illustrates the O-RAN architecture. The lower node of the split gNB-Dll would contain the PHY protocol and the RF parts, the upper node of the split gNB- Dll would host Radio Link Control (RLC) and Medium Access Control (MAC). In the O-RAN architecture, the upper node is called 0-Dll, while the lower node is called 0-Rll.

[0009] The O-RAN architecture further adds a new node in the RAN, the near Real Time (RT) RAN Intelligent Controller (RIC), which is responsible for controlling and optimizing RAN functions. The near-RT RIC interacts with E2 nodes, e.g., 0-Dll, O-CU-CP, and O-CU-UP, through the E2 interface.

[0010] Clause 8.4.1 of TS 38.423 describes the Xn setup procedure. The Xn Setup procedure, also illustrated in Figure 4, is used to exchange application-level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. The procedure uses non-U E-associated signaling.

[0011] The first NG-RAN node initiates the procedure by sending an XN SETUP REQUEST message to a second NG-RAN node. Upon receipt of this message, the second NG-RAN node should store the received configuration data associated to the first NG-RAN node. The second NG-RAN node replies with an XN SETUP RESPONSE message.

[0012] The XN SETUP REQUEST message may comprise a list of served NR cells, or a list of served E-UTRA cells, or both, which may in turn comprise a so-called Served Cell Information NR IE or a so-called Served Cell Information E-UTRA IE for each cell.

[0013] For further details, refer to 3GPP TS 38.423 and below.

[0014] Clause 8.4.2 of TS 38.423 describes the NG-RAN node Configuration Update procedure, which is also illustrated in Figure 5 for successful operation. The NG-RAN node Configuration Update procedure is used to update application-level configuration data needed for two NG-RAN nodes to interoperate correctly over the Xn-C interface. The procedure uses non-UE-associated signaling.

[0015] The first NG-RAN node initiates the procedure by sending a NG-RAN NODE CONFIGURATION UPDATE message to a second NG-RAN node. Upon receipt of this message, the second NG-RAN node should update the configuration data associated to the first NG-RAN node that it has stored locally.

[0016] The NG-RAN NODE CONFIGURATION UPDATE message may comprise a list of served NR cells to update, or a list of served E-UTRA cells to update, or both, which may comprise a so-called Served Cell Information NR IE or a so-called Served Cell Information E-UTRA IE for each cell to update.

[0017] Clause 8.2.3 of TS 38.473 describes the F1 Setup procedure. The F1 Setup procedure, which is also illustrated in Figure 6 for successful operation, is used to exchange application-level data needed for the gNB-DU and the gNB-CU to correctly interoperate on the F1 interface. The procedure uses non-U E-associated signaling.

[0018] The gNB-DU initiates the procedure by sending a F1 SETUP REQUEST message including the appropriate data to the gNB-CU. The gNB-CU responds with a F1 SETUP RESPONSE message including the appropriate data. The exchanged data shall be stored in gNB-CU and the gNB-DU, respectively. When this procedure is finished, the F1 interface is operational and other F1 messages may be exchanged.

[0019] The F1 SETUP REQUEST message may comprise a list of cells served by the gNB-DU, which in turn comprises a so-called Served Cell Information IE for each cell.

[0020] Clause 8.2.4 of TS 38.473 describes the gNB-DU Configuration Update procedure. The gNB-DU Configuration Update procedure, which is also illustrated in Figure 7 for successful operation, is to update application-level configuration data needed for the gNB-DU and the gNB-CU to interoperate correctly on the F1 interface. The procedure uses non-UE- associated signaling.

[0021] The gNB-DU initiates the procedure by sending a GNB-DU CONFIGURATION UPDATE message to the gNB-CU including an appropriate set of updated configuration data that it has just taken into operational use. The gNB-CU responds with GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it successfully updated the configuration data. The exchanged data shall be stored in gNB-CU and the gNB-DU, respectively.

[0022] The GNB-DU CONFIGURATION UPDATE message may comprise a list of served cells to modify, which in turn comprises a so-called Served Cell Information IE for each cell. For further details, refer to 3GPP TS 38.473 and below.

[0023] Figure 8 illustrates an example of the Generic RAN Network Resource Model (NRM). The current NR and NG-RAN NRM is described in 3GPP TS 28.541 v18.5.0 and the Generic RAN NRM is described in TS 28.662 v17.0.0.

[0024] The definition of SectorEquipmentFunction shown in Figure 8 is as follows. This Information Object Class (IOC) represents a set of cells within a geographical area that has common functions relating to AntennaFunction, TMAFunction and supporting equipment, such as power amplifier. The attributes of SectorEquipmentFunction are illustrated in clause 4.3.1.2 of 3GPP TS 28.662. The problem with this definition is mainly the granularity and the information it conveys. It lacks the possibility of identifying the physical HW unit or component where energy is consumed by the set of cells or carriers.

[0025] RAN3 Rel-18 work item RP-220635 has an objective to specify data collection enhancements and signaling support within existing NG-RAN interfaces and architecture (including non-split architecture and split architecture) for AI / ML-based Network Energy Saving, Load Balancing and Mobility Optimization.

[0026] O-RAN Network Energy Saving Use Cases Technical Report 2.0 describes different Energy Saving features:

[0027] • Carrier and Cell Switch Off / On

[0028] • RF Channel Reconfiguration Off / On

[0029] • Advanced Sleep Mode Selection

[0030] • O-Cloud Resource Energy Saving Mode

[0031] Figure 9 illustrates examples of different levels of energy saving functions with their respective network node deployment. On the right of Figure 9 is an indicative reference time scale on which these energy saving functions operate.

[0032] There currently exist certain challenge(s). For example, every RAN Energy Performance (EP) feature on carrier level, node level, and network level requires a careful tuning of traffic load thresholds and time durations that indicate how long the load needs to have been below a threshold to allow a cell to enter energy saving state and, similarly, above a threshold to exit the energy saving state and resume full system performance. For example, those load threshold values and time durations must be set based on the traffic pattern in the cell. Setting conservative values would mean to miss out on energy saving opportunities while setting more aggressive values would mean to degrade certain KPIs.

[0033] Tweaking RAN EP features to find an optimized balance between energy saving and maintaining KPIs requires certain network topology related information that is not yet available.

[0034] One problem is that RAN EP features are applied to, or affect, cells or (sector) carriers, which are logical network (NW) entities, and are thus logical energy consumers, while energy is factually consumed in physical hardware (HW) products and / or components thereof, which are physical energy consumers and whose energy consumption can be measured / metered. This makes tuning the EP features even more difficult since in real NW deployments, multiple cells or (sector) carriers are usually allocated to the same HW products / units, which may lead to suboptimal use of the EP features, and thus suboptimal energy saving gains.

[0035] Moreover, in some cases, there is a need for orchestration between EP features. For instance, on some HW product deployments, it might be beneficial to activate EP feature 1 instead of EP feature 2, because it enables higher energy saving gains, while it might be the other way around in other HW product deployments, assuming similar traffic situations.

[0036] Summary

[0037] Certain aspects of the disclosure and their embodiments may provide solutions to these or other challenges. Examples of this disclosure introduce the concept of an Energy Consumers Group (ECG), which groups all cells and / or (sector) carriers that share a HW unit or a HW component and thus the energy consumption of the HW unit or component. Certain embodiments may provide one or more of the following technical advantages. For example, by exploiting the information sent / received relating to groups of hardware resources (logical and / or physical), e.g., ECGs, local RAN EP optimization on cells or carriers as purely logical energy-consumers can be avoided. Energy savings can be maximized on cluster and network level for example.

[0038] One aspect of the present disclosure provides a method performed by a first network node for receiving information. The method comprises receiving, from a second network node, information identifying one or more cells and / or carriers, and, for each cell or carrier, one or more identifiers of one or more groups of hardware resources associated with the cell or carrier. Another aspect of the present disclosure provides a method performed by a second network node for sending information. The method comprises sending, to a first network node, information identifying one or more cells and / or carriers, and, for each cell or carrier, one or more identifiers of one or more groups of hardware resources associated with the cell or carrier.

[0039] Brief Description of the Drawings

[0040] For a better understanding of examples of the present disclosure, and to show more clearly how the examples may be carried into effect, reference will now be made, by way of example only, to the following drawings in which:

[0041] Figure 1 illustrates the current 5G RAN architecture;

[0042] Figure 2 illustrates the overall architecture for separation of gNB-CU-CP and gNB-CU- UP;

[0043] Figure 3 illustrates the O-RAN architecture;

[0044] Figure 4 illustrates the Xn Setup procedure;

[0045] Figure 5 illustrates the NG-RAN node Configuration Update procedure for successful operation;

[0046] Figure 6 illustrates the F1 Setup procedure for successful operation;

[0047] Figure 7 illustrates the gNB-DU Configuration Update procedure for successful operation;

[0048] Figure 8 illustrates an example of the Generic RAN Network Resource Model (NRM);

[0049] Figure 9 illustrates examples of different levels of energy saving functions with their respective network node deployment;

[0050] Figure 10 illustrates an example of a hardware unit according to an example of this disclosure;

[0051] Figure 11 illustrates an example of another hardware unit according to an example of this disclosure;

[0052] Figure 12 is a flow chart illustrating a method according to examples of this disclosure;

[0053] Figure 13 shows a method performed by a network node according to embodiments of the disclosure;

[0054] Figure 14 shows a method performed by a network node according to embodiments of the disclosure;

[0055] Figure 15 shows a method performed by a network node according to embodiments of the disclosure; Figure 16 shows a method performed by a network node according to embodiments of the disclosure;

[0056] Figure 17 illustrates an example of mapping of cells to energy consumer groups according to examples of this disclosure;

[0057] Figure 18 illustrates an example of how ECG assistance information and ECG information is exchanged over network interfaces;

[0058] Figure 19 illustrates an example of a Non-Real-time RIC obtaining ECG information from O-DU for network level energy saving function optimization;

[0059] Figure 20 illustrates an example of a gNB-CU-CP obtaining ECG information from a gNB-Dll, an eNB, and another gNB-CU-CP (#2), and used for Node level energy saving function optimization;

[0060] Figure 21 illustrates an example overview of an Energy Saving function taking inputs data including ECGs and providing thresholds for different RAN EP features as output based on operator intent;

[0061] Figure 22 shows an example of a communication system in accordance with some embodiments;

[0062] Figure 23 shows a UE in accordance with some embodiments;

[0063] Figure 24 shows a network node in accordance with some embodiments;

[0064] Figure 25 is a block diagram of a host in accordance with various aspects described herein;

[0065] Figure 26 is a block diagram illustrating a virtualization environment in which functions implemented by some embodiments may be virtualized;

[0066] Figure 27 shows a communication diagram of a host communicating via a network node with a UE over a partially wireless connection in accordance with some embodiments; and

[0067] Figure 28 shows a network node in accordance with further embodiments.

[0068] Detailed Description

[0069] The following sets forth specific details, such as particular embodiments or examples for purposes of explanation and not limitation. It will be appreciated by one skilled in the art that other examples may be employed apart from these specific details.

[0070] In this disclosure, a hardware resource may be, for example, one or more physical hardware components but may, additionally or alternatively, in some examples include one or more logical energy consumers, e.g., network nodes or other logical hardware units / components. As indicated above, examples of this disclosure introduce the concept of an Energy Consumers Group (ECG), which groups all cells and / or (sector) carriers that share a HW unit or a HW component and thus the energy consumption of the HW unit or component. An ECG may be, for example, a group of one or more hardware resources used when a cell and / or carrier (or multiple cells and / or carriers) is operational. Alternatively, for example, an ECG may be a logical entity representing or associated with one or more hardware resources used when a cell and / or carrier (or multiple cells and / or carriers) is operational. In other examples, an ECG may represent or be associated with cells / carriers sharing one or more hardware components when operational. Thus, in some examples, an ECG is a logical entity that is representing (or is associated to) certain physical hardware and exposing or expressing the connection or dependence of other logical entities, such as the cells and / or carriers, to the physical hardware resource(s). In some examples, the recipient of the ECG information (the entity using the ECG information) does not need to know the specific physical hardware associated to the ECG to make use of the ECG information.

[0071] The ECG information may, in some examples, be (dynamically) created and updated based on the network configuration, namely the allocation of cells and (sector) carriers to physical HW. An ECG may in some examples span across two or more network nodes, e.g., NG- RAN nodes or logical entities thereof. For example, two NG-RAN nodes or logical entities thereof may share a HW unit such as a radio unit. An ECG may be identified for example by a globally unique identifier.

[0072] In some examples, the ECG information may be propagated over network interfaces, e.g., F1 , Xn, X2, E2 and / or 01 , to update and / or merge ECG information and to serve as additional input for better orchestration of RAN Energy Performance (EP) features, namely to derive EP feature combinations that are most suitable to activate and adapt their respective threshold values based on the HWs energy saving capabilities, traffic load predictions, observed KPIs, and operator intents.

[0073] Some examples of this disclosure are described for the energy saving / optimization use case but could be applied to other use cases where the mapping of cells and / or (sector) carriers to the physical HW they are allocated on is required or beneficial. Another example use case could be Passive Inter-Modulation (PIM) avoidance / mitigation.

[0074] Some examples of this disclosure may create a mapping between cells and / or carriers, as logical energy-consuming entities, and the logical and / or physical energy-consuming HW they are allocated to, for example an Energy Consumers Group (ECG). A network node or function controlling, tuning, or otherwise affecting RAN EP features can make use of this ECG information, for example, to achieve a more energy-efficient traffic management and more network energy savings.

[0075] An ECG may represent, for example, a HW unit (such as a radio unit), or a component part or a group of component parts of a HW unit (such as an antenna segment of a radio unit).

[0076] Figure 10 illustrates an example of a hardware unit 1000 according to an example of this disclosure. In this example, the hardware unit 1000 is associated with three cells, Celli , Cel 12 , and Cel 13. Figure 11 illustrates another example of a hardware unit 1100 according to an example of this disclosure. The hardware unit comprises HW component 1102, HW component 1104, and HW component 1106. A first ECG 1108 includes HW component 1102 and is associated with Celli , Cell2, and Cell3. A second ECG 1110 includes HW component 1104 and is associated with Celli . A third ECG 1112 includes HW component 1106 and is associated with Cell2 and Cell3.

[0077] An ECG, in some examples, consists of all cells and / or (sector) carriers that share energy consumption by sharing at least certain physical HW.

[0078] A cell or carrier can, in some examples, be part of multiple ECGs (i.e., consuming energy in multiple HW units or components). Similarly, a HW unit or component can, in some examples, be part of multiple ECGs, e.g., if multiple ECGs are combined into a single ECG. Considering Figures 10 and 11 , ECGs 1a, 1b, and 1 c can be combined into ECG 1 while ECGs 1a, 1b, and 1c can remain unchanged, i.e., the HW components within HW unit 1 can, in this example, be part of two ECGs.

[0079] A first network node can, in some examples, obtain ECG information (related to one or more ECGs) from a second network node in a fourth message over network interfaces, e.g., F1 , Xn, X2, E2 and / or 01. The first network node may optionally have to request the ECG information from the second network node in a third message, prior to receiving them. This is shown as an example in Figure 12, which is a flow chart illustrating a method according to examples of this disclosure.

[0080] An ECG may in some examples have a unique identity on at least a network level (or part of a network). A unique identifier may, in some examples, be or may be derived based on, a unique identifier of the underlying HW unit or component that the ECG represents. For example, the identifier may be the result of a hash function taking the serial number of the underlying HW unit or component (or one or more of the units / components) as an input. This will ensure non-ambiguous distribution, identification, and merging of ECG information between network nodes, since cells and carriers in different network nodes might share the same physical HW.

[0081] ECG information can in some examples comprise a list of RAN EP features that are supported by the underlying HW unit or component and their energy saving potential or gain. This would indicate if a certain HW product is more optimized by design for a specific EP feature. For instance, if a HW unit does not have possibility of granular power domains to turn on / off without affecting all cells or carriers sharing it, a cell or carrier on / off EP feature has very low energy saving potential (unless all cells or carriers of the corresponding ECG are jointly turned on / off).

[0082] An ECG or the underlying HW unit or component may in some examples comprise an energy meter and may thus be able to provide energy consumption measurements.

[0083] Certain embodiments may provide one or more of the following technical advantages. For example, by exploiting the information sent / received relating to groups of hardware resources (logical and / or physical), e.g., ECGs, local RAN EP optimization on cells or carriers as purely logical energy-consumers can be avoided. Energy savings can be maximized on cluster and network level for example.

[0084] This can be used, for example, by both centralized and distributed energy saving functions, in split and non-split architecture, in cloud environments and on purpose-built hardware, since the ECG information can be exchanged over NG-RAN F1 , X2, Xn, NG, and O-RAN E2, 01 interfaces, and potentially other interfaces. The 01 interface connects the SMO to the RAN managed elements. These include the near real-time RIC, O-CU-CP, O-CU-UP, O-DU, O-RU, and the open evolved NodeB (O-eNB).

[0085] The sharing of the information according to examples of this disclosure can, for example, be optional for inter-vendor operability / deployments, but it can also be included in the 3GPP, O- RAN, and related standards.

[0086] The information can, for example, be used by a traffic management function and / or an AI / ML orchestration function to free up all the cells in an ECG from traffic / UEs by reallocating traffic / UEs to other cells in other ECGs to maximize energy savings by putting the HW unit into deep sleep. Similarly, this information can also be used in some examples by such function(s) to ensure that a RAN EP feature, e.g., a cell-specific RAN EP feature such as Cell DTX / DRX, is used across all the cells in the ECG in order to achieve energy saving gains.

[0087] 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.

[0088] Figure 13 depicts a method 1300 in accordance with particular embodiments, such as for example a method performed by a first network node for receiving information. The method 1300 may be performed by a network node (e.g., the network node QQ110 or network node QQ300 as described later with reference to Figures 22 and 24, respectively). The method 1300 begins at step 1302 with receiving, from a second network node, information identifying one or more cells and / or carriers, and, for each cell or carrier, one or more identifiers of one or more groups of hardware resources associated with the cell or carrier.

[0089] Figure 14 depicts a method 1400 in accordance with particular embodiments, such as for example a method performed by a second network node for sending information. The method 1400 may be performed by a network node (e.g., the network node QQ110 or network node QQ300 as described later with reference to Figures 22 and 24, respectively). The method 1400 begins at step 1402 with sending, to a first network node, information identifying one or more cells and / or carriers, and, for each cell or carrier, one or more identifiers of one or more groups of hardware resources associated with the cell or carrier.

[0090] Figure 15 depicts a method 1500 in accordance with particular embodiments, such as for example a method performed by a first network node for receiving information. The method 1500 may be performed by a network node (e.g., the network node QQ110 or network node QQ300 as described later with reference to Figures 22 and 24, respectively). The method 1500 begins at step 1502 with receiving, from a second network node, information identifying one or more cells and / or carriers and, for each cell or carrier, one or more hardware resources used when the cell and / or carrier is operational.

[0091] Figure 16 depicts a method 1600 in accordance with particular embodiments, such as for example a method performed by a second network node for sending information. The method 1600 may be performed by a network node (e.g., the network node QQ110 or network node QQ300 as described later with reference to Figures 22 and 24, respectively). The method 1600 begins at step 1602 with sending, to a first network node, information identifying one or more cells and / or carriers and, for each cell or carrier, one or more hardware resources used when the cell and / or carrier is operational.

[0092] Specific example embodiments are now described for illustrative purposes.

[0093] Examples of this disclosure relate to a method executed by a first network node to obtain Energy Consumers Group (ECG) information for one or more ECGs from one or more second network nodes. In these examples, the ECG is a specific non-limiting example of a group of hardware resources as referred to herein, or one or more hardware resources associated with one or more cells and / or carriers, or one or more hardware resources used when a cell and / or carrier is operational. Other groups of hardware resources, or one or more hardware resources used when each of one or more cells and / or carriers is operational, are possible in all of these examples.

[0094] A network node may be one or more of the following examples:

[0095] • gNB-CU, gNB-CU-CP, gNB-DU, Near-RT RIC, Non-RT RIC, eNB, O-CU-UP, O- CLI-CP, O-DU, O-eNB, SMO system / node, OAM system / node

[0096] An ECG may be for example a logical entity, with a unique identifier, comprising one or more cells or carriers, with unique identifiers. Thus, in one embodiment, ECG information comprises (and can be conveyed as) a unique ECG identifier and one or more unique cell or carrier identifiers for the cell(s) or carrier(s) associated to the ECG. Alternatively, in another embodiment, ECG information comprises (and can be conveyed as) a unique cell or carrier identifier and one or more unique ECG identifiers for the ECGs the cell or carrier is associated to (i.e. one or more identifiers of one or more groups of hardware resources associated with the cell or carrier).

[0097] Unique, in this case, may mean globally unique, unique within a network, e.g., PLMN, or at least a part or area of a network, e.g., an area where ECG information is exchanged and / or obtained from, such that any kind of confusion of ECGs is precluded.

[0098] An ECG generally represents (or is associated with) a physical HW unit or component where energy is consumed, regardless of whether that energy consumption can be measured / metered, or multiple such components and / or units.

[0099] In one embodiment, a first network node may additionally, prior to receiving the ECG information, request the ECG information from the second network node. The request may indicate to the second network node to include ECG information for all ECGs the second network node is aware of, or the ECGs that are indicated as shared with other network nodes, or to include ECG information for one or more specific ECGs, if available. The first network node may request ECG information for one or more specific ECGs by including one or more (globally) unique identifiers corresponding to the one or more specific ECGs.

[0100] Figure 17 illustrates an example of mapping of cells to energy consumer groups according to examples of this disclosure. The left side of Figure 17 illustrates an example of energy consumer groups in different HW architecture variants. This does not reflect scalability aspects of actual deployments, meaning that in some examples there could be more radio units of similar HW architecture that would results in similar energy consumers groups. The right side of Figure 17 illustrates an example of mapping of cells to energy consumer groups in the left side of Figure 17, as a result of how cells are allocated on different HW.

[0101] In another embodiment, ECG information could additionally comprise one or more of the following examples: o A description of the ECG (e.g., which type of HW unit or component it is, e.g., radio unit, power amplifier, baseband processing unit, etc.). o An indication that / whether an ECG (thus, the underlying HW unit or component) is being shared by different network nodes. o A capability indication of whether an ECG (thus, the underlying HW unit or component) can provide energy consumption measurements, i.e. , has energy metering capabilities. o A capability indication of energy saving (or low power) modes / states or features that an ECG (thus, the underlying HW unit or component) supports. o A status indication of energy saving (or low power) modes / states or features that are active and / or inactive per ECG (thus, the underlying HW unit or component) (e.g., number of active transceivers, TRX, chains, or list of active energy saving features).

[0102] In a related embodiment, the capability indication may comprise one or more inactive / sleep modes / states with an associated absolute and / or relative power level / consumption.

[0103] Additionally, or alternatively, the capability indication may comprise one or more reduced capability / capacity modes / states with an associated absolute and / or relative power level / consumption. The capability indication may also include an additional transition energy and / or a total transition time for the different modes / states. The capability indication may, e.g., comprise one or more of the following information, for example in form of a table or list:

[0104] If an ECG (thus, the underlying HW unit or component) is in a sleep mode, transmission and reception of signals related to the cells or carriers in said ECG (thus, using the underlying HW unit or component) is generally not possible in some examples. However, if the ECG represents a certain HW component needed for transmission or reception only, reception or transmission, respectively, is still possible in some examples, given that none of the other ECGs the cells or carriers are associated with are in a sleep mode.

[0105] If an ECG (thus, the underlying HW unit or component) is in a reduced capability / capacity mode, transmission and reception of signals related to the cells or carriers of the ECG (thus, using the underlying HW unit or component) is generally possible in some examples, given that none of the other ECGs the cells or carriers are associated with are in a sleep mode. However, transmission and reception of signals may be limited, e.g., in terms of NW / system capacity. For example, certain HW components like digital signal processing units / circuits may run at reduced clock speed, which effectively reduces their energy consumption but also the compute capacity, and consequently the NW / system capacity, since less data can be transmitted and received in a certain time.

[0106] The absolute or relative power in full capability / capacity mode, PF, may be the absolute or relative power level / consumption in some examples if the underlying HW unit or component is under full load.

[0107] In some examples, if ECG information is, was, or will be conveyed as a unique cell or carrier identifier and one or more unique ECG identifiers for the ECGs the cell or carrier is associated to, additional information related to an ECG (or the underlying HW unit or component), e.g., a description of the ECG, certain capabilities of the ECG, etc. can be conveyed separately, either at the same time (e.g., in (a) different part(s) of the same message), afterwards (in a subsequent message), or beforehand (in a preceding message). The unique ECG identifier comprised in all messages conveying ECG related information allows to merge ECG information across signaling messages as it does across network nodes.

[0108] In a related embodiment, the ECG identifier may for example be, or may be derived from, a unique identifier, e.g., a serial number, of the physical HW unit or component that it represents, e.g., using a hash function.

[0109] As exemplified above, multiple ECGs can arbitrarily be combined into one ECG for any reason in some examples. In this case, the individual ECGs can remain in some examples, i.e. , the individual ECGs and the combined ECG can coexist. Thus, HW units or components thereof can be part of multiple ECGs and ECGs can follow a hierarchical structure / order.

[0110] In some examples, the hierarchy of ECGs can be reflected in the ECGs’ identifiers. For example, the identifier of one ECG may be part of the identifier of one or more other ECGs, e.g., a prefix or suffix. For example, the identifiers of the ECGs representing components of a HW unit may have a common part, which is representing the HW unit, explicitly or implicitly. For this, there is no need for the existence of an ECG representing the HW unit as such. In one related embodiment, the ECG identifier can be derived and / or communicated as two or more distinct parts / information elements (lEs), thereby explicitly expressing some form of hierarchy.

[0111] In some examples, the second network node creates the ECG information that it sends to the first network node. However, in other examples, the second network obtains the said ECG information from another network node (or multiple other nodes) prior to sending them to the first network node. In such way, ECG information can be exchanged between two network nodes that do not have a signaling connection / interface between themselves or do not have an appropriate signaling procedure to exchange it directly, e.g., two gNB-DUs, or two NG-RAN nodes without a functioning Xn interface. In case of two gNB-DUs, for example, ECG information can be exchanged over F1 (and Xn, if the two gNB-DUs are connected to different gNB-CUs). In case of two NG-RAN nodes without a functioning Xn interface, for example, ECG information can be exchanged through the Core Network, CN, such as 5G Core, 5GC, via the NG interface. It is assumed in some examples that the second network node in some sense owns or controls the cells or carriers (as logical entities) for which it creates ECG information. In some cases, the second network node additionally or alternatively controls the underlying HW, which is used to realize transmission and reception of signals for the respective cells or carriers. However, in other cases, part of the underlying HW may be controlled by another logical entity, herein referred to as third network node, such as an 0-Rll in the O-RAN architecture. In such cases, the second network node knows the logical identity of the third network node but does not know the details about the underlying HW. Hence, the second network node may communicate with the third network node to get ECG assistance information to create the said ECG information.

[0112] Prior to creating the said ECG information, in some examples the second network node can obtain ECG assistance information (related to one or more ECGs) from a third network node in a SECOND MESSAGE over network interfaces, e.g., Open Fronthaul. The second network node may optionally have to request the ECG assistance information from the third network node in a FIRST MESSAGE, prior to receiving them. This is illustrated in the Figure 18, which illustrates an example of how ECG assistance information and ECG information is exchanged over network interfaces. Figure 18 may in some examples be an extension of some examples of Figure 12, where the second network node obtains ECG assistance information from a third network node prior to creating the said ECG information.

[0113] In some examples, an ECG assistance information may include one or more of:

[0114] • A unique identifier for HW component, or a group of HW components, that the assistance information represents. The identifier may for example uniquely identify the HW component by itself or in combination with a HW unit identifier, which may already be known to the second network node and may not have to be communicated as such. Along with:

[0115] ■ One or more, at least locally unique, cell or carrier identifier known between the second network node and the third network node (hence, not known to the first network node) for which the second network node has a mapping to the global cell or carrier identifier.

[0116] ■ For example, an eAxC_ID, a [tr]x-array-carrier identifier, or an low- level-[tr]x-endpoint identifier in O-RAN M-plane.

[0117] Embodiments of this disclosure can be realized in some examples through enhancements of existing inter-node procedures and signaling messages defined in 3GPP and O-RAN specifications, e.g., for the Xn, X2, F1 , E2, and 01 interfaces as shown below. For example, embodiments can be realized through enhancements of the Xn Setup and / or NG-RAN node Configuration Update procedures as well as the corresponding signaling messages defined in the XnAP specification (3GPP TS 38.423).

[0118] In one embodiment, the ECG information (i.e., the contents of the FOURTH MESSAGE) can be comprised in the XN SETUP REQUEST and / or NG-RAN NODE CONFIGURATION UPDATE messages over the Xn interface, without preceding request.

[0119] In another embodiment, the ECG information request (i.e., the contents of the THIRD MESSAGE) can be comprised in the XN SETUP REQUEST and / or NG-RAN NODE CONFIGURATION UPDATE messages over the Xn interface, and in response to this, the ECG information (i.e., the contents of the FOURTH MESSAGE) can be comprised in the corresponding XN SETUP RESPONSE and / or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE messages over the Xn interface, e.g., as requested.

[0120] This can be realized for example by enhancing the Served Cell Information NR IE as well as the Served Cell Information E-UTRA IE, so that they additionally comprise the ECG information, as exemplified herein.

[0121] In examples with split architecture (disaggregated gNB), enhancements of the gNB-DU Configuration Update and gNB-CU Configuration Update procedures as well as the corresponding signaling messages defined in the F1AP specification (3GPP TS 38.473) may be implemented in some examples.

[0122] In one embodiment, the ECG information (i.e., the contents of the FOURTH MESSAGE) can be comprised in the F1 SETUP REQUEST and / or GNB-DU CONFIGURATION UPDATE messages over the F1 interface. With such enhancement, ECG information created at the gNB-DU can be signaled to the gNB-CU, e.g., to be used at the gNB-CU and / or to be further distributed to other NG-RAN nodes or other network nodes or entities.

[0123] In another embodiment, the ECG information (i.e., the contents of the FOURTH MESSAGE) can be comprised in the GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE and / or GNB-CU CONFIGURATION UPDATE messages over the F1 interface. With this enhancement, ECG information created at (i.e., originating from) another gNB-DU can be signaled to (shared with) the gNB-DU to be used at the gNB-DU, e.g., for DU-local energy saving function optimization. This can be realized for example by enhancing the Cells for SON List IE, or the Neighbour NR Cells for SON List IE included therein, so that it additionally comprises the ECG information. Note that the gNB-Dll creating ECG information and the gNB-Dll receiving ECG information in this scenario may be connected to (i.e. , associated with) the same or different gNB-CUs.

[0124] In case of O-RAN architecture, the invention can be realized through enhancements of the E2 Setup and / or E2 Node Configuration Update procedures as well as the corresponding signaling messages defined in the E2AP specification (O-RAN. WG3.E2AP).

[0125] In one embodiment, the ECG information (i.e., the contents of the FOURTH MESSAGE) can be comprised in the E2 SETUP REQUEST message and / or the E2 NODE CONFIGURATION UPDATE message over the E2 interface.

[0126] Note that the introduction of new inter-node procedures and signaling messages in 3GPP and O-RAN specifications for such purposes is not precluded in some examples.

[0127] Figures 19-21 show example sequence diagrams of how the ECG information may be signaled between different network nodes in some examples of this disclosure using NG- RAN and / or O-RAN interfaces and how the ECG information is used to optimize Energy Saving function on different levels. Figure 19 illustrates an example of a Non-Real-time RIC obtaining ECG information from O-DU for network level energy saving function optimization. Figure 20 illustrates an example of a gNB-CU-CP (#1) obtaining ECG information from a gNB-DU, an eNB, and another gNB-CU-CP (#2), and used for Node level energy saving function optimization. Figure 21 illustrates an example overview of an Energy Saving function taking inputs data including ECGs (from the left) and providing thresholds for different RAN EP features as output (to the right) based on operator intent such as user experience (from the top).

[0128] In one embodiment, a first network node may additionally use the received ECG information from one or more second network nodes to update its own ECG information.

[0129] For example, a network node 1 is aware of ECG 1 comprising cell 1 and cell 2 (which it controls) and receives ECG information for ECG 1 from a network node 2 comprising cell 3 and cell 4 (which network node 2 controls). Based on the unique identifier of the ECG, node 1 can update the ECG information for ECG1 to comprise cell 1 , cell 2, cell 3, and cell 4.

[0130] In one embodiment, the first network node uses the information related to ECGs for orchestrating energy saving functions, which may be implemented, for example, but not limited to, as a rule-based algorithm or as an AI / ML model, in conjunction with one or more of:

[0131] • A traffic load prediction for each cell within an ECG.

[0132] • One or more performance measurements to calculate key performance indicators.

[0133] • Information related to cell and carrier configuration including cell relation, network topology information, e.g., capacity or coverage cells.

[0134] • An operator intent which may be a wanted user experience, e.g.,

[0135] • X-percentile of UE sessions with at least Y Mbps DL throughput for Mobile Broadband services,

[0136] • Max latency for time critical services.

[0137] Additions in the XnAP specification (3GPP TS 38.423)

[0138] The ECG information, e.g., the mapping between cells (or carriers) and ECGs, can in some examples be conveyed between NG-RAN nodes over the Xn interface, as disclosed hereafter in the following specific example implementation in the XnAP specification. Changes and additions are underlined. Unchanged rows of a table may be omitted as indicated by an ellipsis (...) in some examples.

[0139] The Served Cell Information NR IE and the Served Cell Information E-UTRA IE are exchanged between NG-RAN nodes during the Xn Setup procedure and the NG-RAN node Configuration Update procedure per cell served by a NG-RAN node, requested or nonrequested, for all cells or for individual cells, etc.

[0140] These two lEs may thus be enhanced to additionally comprise a list of ECG identifiers, one for each ECG the respective cell identified by the NR-PCI (or E-UTRA PCI) and / or NR CGI (or ECGI) is associated to.

[0141] 9.2.2.11 Served Cell Information NR

[0142] This IE contains cell configuration information of an NR cell that a neighbouring NG-RAN node may need for the Xn AP interface.

[0143] 9.2.2.12 Served Cell Information E-UTRA

[0144] This IE contains cell configuration information of an E-UTRA cell that a neighbour NG-RAN node may need for the Xn AP interface.

[0145] Additions in the F1AP specification (3GPP TS 38.473)

[0146] The ECG information, e.g., the mapping between cells (or carriers) and ECGs, can be conveyed in some examples between logical nodes of the split architecture over the F1 interface, as disclosed in the following specific example implementation in the F1AP specification. Changes and additions are underlined.

[0147] The Served Cell Information IE is exchanged between gNB-Dll and gNB-Cll during the gNB-Dll Configuration Update procedure and the gNB-CU Configuration Update procedure per cell configured in a gNB-DU.

[0148] This IE may thus be enhanced to additionally comprise a list of ECG identifiers, one for each ECG the respective cell identified by the NR PCI and / or NR CGI is associated to.

[0149] 9.3.1.10 Served Cell Information

[0150] This IE contains cell configuration information of a cell in the gNB-DU.

[0151] Figure 22 shows an example of a communication system QQ100 in accordance with some embodiments.

[0152] In the example, the communication system QQ100 includes a telecommunication network QQ102 that includes an access network QQ104, such as a radio access network (RAN), and a core network QQ106, which includes one or more core network nodes QQ108. The access network QQ104 includes one or more access network nodes, such as network nodes QQ110a and QQ110b (one or more of which may be generally referred to as network nodes QQ110), or any other similar 3rdGeneration Partnership Project (3GPP) access nodes or non-3GPP access points. Moreover, as will be appreciated by those of skill in the art, a network node is not necessarily limited to an implementation in which a radio portion and a baseband portion are supplied and integrated by a single vendor. Thus, it will be understood that network nodes include disaggregated implementations or portions thereof. For example, in some embodiments, the telecommunication network QQ102 includes one or more Open-RAN (ORAN) network nodes. An ORAN network node is a node in the telecommunication network QQ102 that supports an ORAN specification (e.g., a specification published by the O-RAN Alliance, or any similar organization) and may operate alone or together with other nodes to implement one or more functionalities of any node in the telecommunication network QQ102, including one or more network nodes QQ110 and / or core network nodes QQ108.

[0153] Examples of an ORAN network node include an open radio unit (0-Rll), an open distributed unit (O-DU), an open central unit (O-CU), including an O-CU control plane (O-CU-CP) or an O-CU user plane (O-CU-UP), a RAN intelligent controller (near-real time or non-real time) hosting software or software plug-ins, such as a near-real time control application (e.g., xApp) or a non-real time control application (e.g., rApp), or any combination thereof (the adjective “open” designating support of an ORAN specification). The network node may support a specification by, for example, supporting an interface defined by the ORAN specification, such as an A1 , F1 , W1 , E1 , E2, X2, Xn interface, an open fronthaul user plane interface, or an open fronthaul management plane interface. Moreover, an ORAN access node may be a logical node in a physical node. Furthermore, an ORAN network node may be implemented in a virtualization environment (described further below) in which one or more network functions are virtualized. For example, the virtualization environment may include an O-Cloud computing platform orchestrated by a Service Management and Orchestration Framework via an 0-2 interface defined by the O-RAN Alliance or comparable technologies. The network nodes QQ110 facilitate direct or indirect connection of user equipment (UE), such as by connecting UEs QQ112a, QQ112b, QQ112c, and QQ112d (one or more of which may be generally referred to as UEs QQ112) to the core network QQ106 over one or more wireless connections.

[0154] 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 QQ100 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 QQ100 may include and / or interface with any type of communication, telecommunication, data, cellular, radio network, and / or other similar type of system.

[0155] The UEs QQ112 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 QQ110 and other communication devices. Similarly, the network nodes QQ110 are arranged, capable, configured, and / or operable to communicate directly or indirectly with the UEs QQ112 and / or with other network nodes or equipment in the telecommunication network QQ102 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 QQ102.

[0156] In the depicted example, the core network QQ106 connects the network nodes QQ110 to one or more hosts, such as host QQ116. 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 QQ106 includes one more core network nodes (e.g., core network node QQ108) 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 QQ108. 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 (ALISF), Subscription Identifier De-concealing function (SIDF), Unified Data Management (UDM), Security Edge Protection Proxy (SEPP), Network Exposure Function (NEF), Policy Control Function (PCF) and / or a User Plane Function (UPF).

[0157] The host QQ116 may be under the ownership or control of a service provider other than an operator or provider of the access network QQ104 and / or the telecommunication network QQ102, and may be operated by the service provider or on behalf of the service provider. The host QQ116 may host a variety of applications to provide one or more services. Examples of such applications include the provision of live and / or pre-recorded audio / video content, data collection services, for example, 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.

[0158] As a whole, the communication system QQ100 of Figure 22 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.

[0159] In some examples, the telecommunication network QQ102 is a cellular network that implements 3GPP standardized features. Accordingly, the telecommunications network QQ102 may support network slicing to provide different logical networks to different devices that are connected to the telecommunication network QQ102. For example, the telecommunications network QQ102 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. In some examples, the UEs QQ112 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 QQ104 on a predetermined schedule, when triggered by an internal or external event, or in response to requests from the access network QQ104. 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).

[0160] In the example illustrated in Figure 22, the hub QQ114 communicates with the access network QQ104 to facilitate indirect communication between one or more UEs (e.g., UE QQ112c and / or QQ112d) and network nodes (e.g., network node QQ110b). In some examples, the hub QQ114 may be a controller, router, a content source and analytics node, or any of the other communication devices described herein regarding UEs. For example, the hub QQ114 may be a broadband router enabling access to the core network QQ106 for the UEs. As another example, the hub QQ114 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 QQ110, or by executable code, script, process, or other instructions in the hub QQ114. As another example, the hub QQ114 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 QQ114 may be a content source. For example, for a UE that is a VR headset, display, loudspeaker or other media delivery device, the hub QQ114 may retrieve VR assets, video, audio, or other media or data related to sensory information via a network node, which the hub QQ114 then provides to the UE either directly, after performing local processing, and / or after adding additional local content. In still another example, the hub QQ114 acts as a proxy server or orchestrator for the UEs, in particular if one or more of the UEs are low energy loT devices.

[0161] The hub QQ114 may have a constant / persistent or intermittent connection to the network node QQ110b. The hub QQ114 may also allow for a different communication scheme and / or schedule between the hub QQ114 and UEs (e.g., UE QQ112c and / or QQ112d) , and between the hub QQ114 and the core network QQ106. In other examples, the hub QQ114 is connected to the core network QQ106 and / or one or more UEs via a wired connection. Moreover, the hub QQ114 may be configured to connect to an M2M service provider over the access network QQ104 and / or to another UE over a direct connection. In some scenarios, UEs may establish a wireless connection with the network nodes QQ110 while still connected via the hub QQ114 via a wired or wireless connection. In some embodiments, the hub QQ114 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 QQ110b. In other embodiments, the hub QQ114 may be a non-dedicated hub - that is, a device which is capable of operating to route communications between the UEs and network node QQ110b, but which is additionally capable of operating as a communication start and / or end point for certain data channels.

[0162] Figure 23 shows a UE QQ200 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 camera, 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, 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-loT) UE, a machine type communication (MTC) UE, and / or an enhanced MTC (eMTC) UE.

[0163] 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).

[0164] The UE QQ200 includes processing circuitry QQ202 that is operatively coupled via a bus QQ204 to an input / output interface QQ206, a power source QQ208, a memory QQ210, a communication interface QQ212, and / or any other component, or any combination thereof. Certain UEs may utilize all or a subset of the components shown in Figure 23. 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.

[0165] The processing circuitry QQ202 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 QQ210. The processing circuitry QQ202 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 QQ202 may include multiple central processing units (CPUs). The processing circuitry QQ202 may be operable to provide, either alone or in conjunction with other UE QQ200 components, such as the memory QQ210, UE QQ200 functionality.

[0166] In the example, the input / output interface QQ206 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 QQ200. 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.

[0167] In some embodiments, the power source QQ208 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 QQ208 may further include power circuitry for delivering power from the power source QQ208 itself, and / or an external power source, to the various parts of the UE QQ200 via input circuitry or an interface such as an electrical power cable. Delivering power may be, for example, for charging of the power source QQ208. Power circuitry may perform any formatting, converting, or other modification to the power from the power source QQ208 to make the power suitable for the respective components of the UE QQ200 to which power is supplied.

[0168] The memory QQ210 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 QQ210 includes one or more application programs QQ214, such as an operating system, web browser application, a widget, gadget engine, or other application, and corresponding data QQ216. The memory QQ210 may store, for use by the UE QQ200, any of a variety of various operating systems or combinations of operating systems.

[0169] The memory QQ210 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 (eUlCC), integrated UICC (iUICC) or a removable UICC commonly known as ‘SIM card.’ The memory QQ210 may allow the UE QQ200 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 QQ210, which may be or comprise a device-readable storage medium.

[0170] The processing circuitry QQ202 may be configured to communicate with an access network or other network using the communication interface QQ212. The communication interface QQ212 may comprise one or more communication subsystems and may include or be communicatively coupled to an antenna QQ222. The communication interface QQ212 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 QQ218 and / or a receiver QQ220 appropriate to provide network communications (e.g., optical, electrical, frequency allocations, and so forth). Moreover, the transmitter QQ218 and receiver QQ220 may be coupled to one or more antennas (e.g., antenna QQ222) and may share circuit components, software or firmware, or alternatively be implemented separately.

[0171] In some embodiments, communication functions of the communication interface QQ212 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.

[0172] Regardless of the type of sensor, a UE may provide an output of data captured by its sensors, through its communication interface QQ212, 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).

[0173] 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 controls a robotic arm performing a medical procedure according to the received input.

[0174] 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 devices which are or which are 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 smartwatch, 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 on the intended application of the loT device in addition to other components as described in relation to the UE QQ200 shown in Figure 23.

[0175] 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 3GPP NB-loT 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.

[0176] 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.

[0177] Figure 24 shows a network node QQ300 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)), O-RAN nodes or components of an O-RAN node (e.g., 0-Rll, 0-Dll, O-CU).

[0178] 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, distributed units (e.g., in an O- RAN access node) 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).

[0179] 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).

[0180] The network node QQ300 includes processing circuitry QQ302, a memory QQ304, a communication interface QQ306, and a power source QQ308, and / or any other component, or any combination thereof. The network node QQ300 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 QQ300 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 QQ300 may be configured to support multiple radio access technologies (RATs). In such embodiments, some components may be duplicated (e.g., separate memory QQ304 for different RATs) and some components may be reused (e.g., a same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include multiple sets of the various illustrated components for different wireless technologies integrated into network node QQ300, 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 QQ300.

[0181] The processing circuitry QQ302 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 QQ300 components, such as the memory QQ304, network node QQ300 functionality. For example, the processing circuitry QQ302 may be configured to cause the network node to perform the methods as described with reference to any of Figures 13 to 16.

[0182] In some embodiments, the processing circuitry QQ302 includes a system on a chip (SOC). In some embodiments, the processing circuitry QQ302 includes one or more of radio frequency (RF) transceiver circuitry QQ312 and baseband processing circuitry QQ314. In some embodiments, the radio frequency (RF) transceiver circuitry QQ312 and the baseband processing circuitry QQ314 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 QQ312 and baseband processing circuitry QQ314 may be on the same chip or set of chips, boards, or units.

[0183] The memory QQ304 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 QQ302. The memory QQ304 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 QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations made by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and memory QQ304 is integrated.

[0184] The communication interface QQ306 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 QQ306 comprises port(s) / terminal(s) QQ316 to send and receive data, for example to and from a network over a wired connection. The communication interface QQ306 also includes radio front-end circuitry QQ318 that may be coupled to, or in certain embodiments a part of, the antenna QQ310. Radio front-end circuitry QQ318 comprises filters QQ320 and amplifiers QQ322. The radio front-end circuitry QQ318 may be connected to an antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry may be configured to condition signals communicated between antenna QQ310 and processing circuitry QQ302. The radio front-end circuitry QQ318 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 QQ318 may convert the digital data into a radio signal having the appropriate channel and bandwidth parameters using a combination of filters QQ320 and / or amplifiers QQ322. The radio signal may then be transmitted via the antenna QQ310.

[0185] Similarly, when receiving data, the antenna QQ310 may collect radio signals which are then converted into digital data by the radio front-end circuitry QQ318. The digital data may be passed to the processing circuitry QQ302. In other embodiments, the communication interface may comprise different components and / or different combinations of components.

[0186] In certain alternative embodiments, the network node QQ300 does not include separate radio front-end circuitry QQ318, instead, the processing circuitry QQ302 includes radio frontend circuitry and is connected to the antenna QQ310. Similarly, in some embodiments, all or some of the RF transceiver circuitry QQ312 is part of the communication interface QQ306. In still other embodiments, the communication interface QQ306 includes one or more ports or terminals QQ316, the radio front-end circuitry QQ318, and the RF transceiver circuitry QQ312, as part of a radio unit (not shown), and the communication interface QQ306 communicates with the baseband processing circuitry QQ314, which is part of a digital unit (not shown).

[0187] The antenna QQ310 may include one or more antennas, or antenna arrays, configured to send and / or receive wireless signals. The antenna QQ310 may be coupled to the radio frontend circuitry QQ318 and may be any type of antenna capable of transmitting and receiving data and / or signals wirelessly. In certain embodiments, the antenna QQ310 is separate from the network node QQ300 and connectable to the network node QQ300 through an interface or port.

[0188] The antenna QQ310, communication interface QQ306, and / or the processing circuitry QQ302 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 QQ310, the communication interface QQ306, and / or the processing circuitry QQ302 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.

[0189] The power source QQ308 provides power to the various components of network node QQ300 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ308 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ300 with power for performing the functionality described herein. For example, the network node QQ300 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 QQ308. As a further example, the power source QQ308 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.

[0190] Embodiments of the network node QQ300 may include additional components beyond those shown in Figure 24 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 QQ300 may include user interface equipment to allow input of information into the network node QQ300 and to allow output of information from the network node QQ300. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ300.

[0191] Figure 25 is a block diagram of a host QQ400, which may be an embodiment of the host QQ116 of Figure 22, in accordance with various aspects described herein. As used herein, the host QQ400 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 QQ400 may provide one or more services to one or more UEs.

[0192] The host QQ400 includes processing circuitry QQ402 that is operatively coupled via a bus QQ404 to an input / output interface QQ406, a network interface QQ408, a power source QQ410, and a memory QQ412. 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 23 and 24, such that the descriptions thereof are generally applicable to the corresponding components of host QQ400.

[0193] The memory QQ412 may include one or more computer programs including one or more host application programs QQ414 and data QQ416, which may include user data, e.g., data generated by a UE for the host QQ400 or data generated by the host QQ400 for a UE. Embodiments of the host QQ400 may utilize only a subset or all of the components shown. The host application programs QQ414 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., FLAG, 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 QQ414 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 QQ400 may select and / or indicate a different host for over-the-top services for a UE. The host application programs QQ414 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.

[0194] Figure 26 is a block diagram illustrating a virtualization environment QQ500 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 QQ500 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. In some embodiments, the virtualization environment QQ500 includes components defined by the O-RAN Alliance, such as an O-Cloud environment orchestrated by a Service Management and Orchestration Framework via an 0-2 interface.

[0195] Applications QQ502 (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.

[0196] Hardware QQ504 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 QQ506 (also referred to as hypervisors or virtual machine monitors (VMMs)), provide VMs QQ508a and QQ508b (one or more of which may be generally referred to as VMs QQ508), and / or perform any of the functions, features and / or benefits described in relation with some embodiments described herein. The virtualization layer QQ506 may present a virtual operating platform that appears like networking hardware to the VMs QQ508.

[0197] The VMs QQ508 comprise virtual processing, virtual memory, virtual networking or interface and virtual storage, and may be run by a corresponding virtualization layer QQ506. Different embodiments of the instance of a virtual appliance QQ502 may be implemented on one or more of VMs QQ508, 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.

[0198] In the context of NFV, a VM QQ508 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 QQ508, and that part of hardware QQ504 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 QQ508 on top of the hardware QQ504 and corresponds to the application QQ502.

[0199] Hardware QQ504 may be implemented in a standalone network node with generic or specific components. Hardware QQ504 may implement some functions via virtualization. Alternatively, hardware QQ504 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 QQ510, which, among others, oversees lifecycle management of applications QQ502. In some embodiments, hardware QQ504 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 QQ512 which may alternatively be used for communication between hardware nodes and radio units.

[0200] Figure 27 shows a communication diagram of a host QQ602 communicating via a network node QQ604 with a UE QQ606 over a partially wireless connection in accordance with some embodiments. Example implementations, in accordance with various embodiments, of the UE (such as a UE QQ112a of Figure 22 and / or UE QQ200 of Figure 23), network node (such as network node QQ110a of Figure 22 and / or network node QQ300 of Figure 24), and host (such as host QQ116 of Figure 22 and / or host QQ400 of Figure 25) discussed in the preceding paragraphs will now be described with reference to Figure 27.

[0201] Like host QQ400, embodiments of host QQ602 include hardware, such as a communication interface, processing circuitry, and memory. The host QQ602 also includes software, which is stored in or accessible by the host QQ602 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 QQ606 connecting via an over-the-top (OTT) connection QQ650 extending between the UE QQ606 and host QQ602. In providing the service to the remote user, a host application may provide user data which is transmitted using the OTT connection QQ650.

[0202] The network node QQ604 includes hardware enabling it to communicate with the host QQ602 and UE QQ606. The connection QQ660 may be direct or pass through a core network (like core network QQ106 of Figure 22) 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.

[0203] The UE QQ606 includes hardware and software, which is stored in or accessible by UE QQ606 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 QQ606 with the support of the host QQ602. In the host QQ602, an executing host application may communicate with the executing client application via the OTT connection QQ650 terminating at the UE QQ606 and host QQ602. 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 QQ650 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 QQ650.

[0204] The OTT connection QQ650 may extend via a connection QQ660 between the host QQ602 and the network node QQ604 and via a wireless connection QQ670 between the network node QQ604 and the UE QQ606 to provide the connection between the host QQ602 and the UE QQ606. The connection QQ660 and wireless connection QQ670, over which the OTT connection QQ650 may be provided, have been drawn abstractly to illustrate the communication between the host QQ602 and the UE QQ606 via the network node QQ604, without explicit reference to any intermediary devices and the precise routing of messages via these devices.

[0205] As an example of transmitting data via the OTT connection QQ650, in step QQ608, the host QQ602 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 QQ606. In other embodiments, the user data is associated with a UE QQ606 that shares data with the host QQ602 without explicit human interaction. In step QQ610, the host QQ602 initiates a transmission carrying the user data towards the UE QQ606. The host QQ602 may initiate the transmission responsive to a request transmitted by the UE QQ606. The request may be caused by human interaction with the UE QQ606 or by operation of the client application executing on the UE QQ606. The transmission may pass via the network node QQ604, in accordance with the teachings of the embodiments described throughout this disclosure. Accordingly, in step QQ612, the network node QQ604 transmits to the UE QQ606 the user data that was carried in the transmission that the host QQ602 initiated, in accordance with the teachings of the embodiments described throughout this disclosure. In step QQ614, the UE QQ606 receives the user data carried in the transmission, which may be performed by a client application executed on the UE QQ606 associated with the host application executed by the host QQ602.

[0206] In some examples, the UE QQ606 executes a client application which provides user data to the host QQ602. The user data may be provided in reaction or response to the data received from the host QQ602. Accordingly, in step QQ616, the UE QQ606 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 QQ606. Regardless of the specific manner in which the user data was provided, the UE QQ606 initiates, in step QQ618, transmission of the user data towards the host QQ602 via the network node QQ604. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, the network node QQ604 receives user data from the UE QQ606 and initiates transmission of the received user data towards the host QQ602. In step QQ622, the host QQ602 receives the user data carried in the transmission initiated by the UE QQ606.

[0207] One or more of the various embodiments improve the performance of OTT services provided to the UE QQ606 using the OTT connection QQ650, in which the wireless connection QQ670 forms the last segment. More precisely, the teachings of these embodiments may improve sharing of hardware related information and thereby provide benefits such as the possibility of improved energy saving decisions in a network.

[0208] In an example scenario, factory status information may be collected and analyzed by the host QQ602. As another example, the host QQ602 may process audio and video data which may have been retrieved from a UE for use in creating maps. As another example, the host QQ602 may collect and analyze real-time data to assist in controlling vehicle congestion (e.g., controlling traffic lights). As another example, the host QQ602 may store surveillance video uploaded by a UE. As another example, the host QQ602 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 QQ602 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. 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 QQ650 between the host QQ602 and UE QQ606, 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 QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or in association with other devices through which the OTT connection QQ650 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 QQ650 may include message format, retransmission settings, preferred routing etc.; the reconfiguring need not directly alter the operation of the network node QQ604. 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 QQ602. The measurements may be implemented in that software causes messages to be transmitted, in particular empty or ‘dummy’ messages, using the OTT connection QQ650 while monitoring propagation times, errors, etc.

[0209] Figure 28 shows a network node QQ700 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. The network node QQ700 may be operable as a core network node, a core network function or, more generally, a core network entity, such as the core network node QQ108 described above with respect to Figure 22). Examples of network nodes in this context include core network entities such as 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), Policy Control Function (PCF) and / or a User Plane Function (UPF).

[0210] The network node QQ700 includes processing circuitry QQ702, a memory QQ704, a communication interface QQ706, and a power source QQ708, and / or any other component, or any combination thereof. The network node QQ700 may be composed of multiple physically separate components, which may each have their own respective components. In certain scenarios in which the network node QQ700 comprises multiple separate components, one or more of the separate components may be shared among several network nodes.

[0211] The processing circuitry QQ702 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 QQ700 components, such as the memory QQ704, network node QQ700 functionality. For example, the processing circuitry QQ702 may be configured to cause the network node to perform the methods as described with reference to any of Figures 13 to 16.

[0212] The memory QQ704 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 QQ702. The memory QQ704 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 QQ702 and utilized by the network node QQ700. The memory QQ704 may be used to store any calculations made by the processing circuitry QQ702 and / or any data received via the communication interface QQ706. In some embodiments, the processing circuitry QQ702 and memory QQ704 is integrated.

[0213] The communication interface QQ706 is used in wired or wireless communication of signaling and / or data between a network node, access network, and / or UE.

[0214] The power source QQ708 provides power to the various components of network node QQ700 in a form suitable for the respective components (e.g., at a voltage and current level needed for each respective component). The power source QQ708 may further comprise, or be coupled to, power management circuitry to supply the components of the network node QQ700 with power for performing the functionality described herein. For example, the network node QQ700 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 QQ708. As a further example, the power source QQ708 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.

[0215] Embodiments of the network node QQ700 may include additional components beyond those shown in Figure 28 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 QQ700 may include user interface equipment to allow input of information into the network node QQ700 and to allow output of information from the network node QQ700. This may allow a user to perform diagnostic, maintenance, repair, and other administrative functions for the network node QQ700.

[0216] This disclosure includes the following enumerated embodiments.

[0217] Group B Embodiments

[0218] 1. A method performed by a first network node for receiving information, the method comprising: receiving, from a second network node, information identifying one or more cells and / or carriers and, for each cell or carrier, one or more hardware resources used when the cell and / or carrier is operational.

[0219] 2. The method of embodiment 1 , wherein the information identifies one or more groups of hardware resources, wherein each group contains one or more of the hardware resources.

[0220] 3. The method of embodiment 2, wherein each of the hardware resources may be included in one or more of the groups.

[0221] 4. The method of embodiment 2 or 3, wherein the information identifies the one or more hardware resources used when each cell or carrier is operational by identifying, for each cell or carrier, one or more of the groups used when the cell and / or carrier is operational. 5. The method of any of embodiments 2 to 4, wherein the information identifies that one or more of the groups is included in one or more other groups.

[0222] 6. The method of any of embodiments 2 to 5, wherein the information identifies an identifier for each of the one or more groups.

[0223] 7. The method of embodiment 6, wherein the information identifies, for each of the cells and / or carriers, one or more identifiers of one or more groups of hardware resources used when the cell and / or carrier is operational.

[0224] 8. The method of embodiment 6 or 7, wherein at least part of the identifier of a group is based on the one or more hardware resources in the group and / or one or more groups in the group.

[0225] 9. The method of any of embodiments 6 to 8, wherein: the identifier for each group is unique within a network including the first network node and / or the second network node or a part of the network; and / or the identifier for each group is globally unique.

[0226] 10. The method of any of embodiments 1 to 9, wherein the information identifies that one or more of the hardware resources is used by multiple network nodes.

[0227] 11. The method of any of embodiments 1 to 10, comprising receiving capability information from the second network node identifying one or more capabilities of the one or more hardware resources used when each of one or more of the cells and / or carriers is operational.

[0228] 12. The method of embodiment 11 , wherein the capability information for the one or more hardware resources used when a cell and / or carrier is operational comprises one or more of: a plurality of sleep and / or power modes supported by the one or more hardware resources; a current sleep and / or power modes of the one or more hardware resources; a plurality of capability and / or capacity levels supported by the one or more hardware resources; a current capability and / or capacity level of the one or more hardware resources; an indication of whether the one or more hardware resources can provide energy consumption measurements.

[0229] 13. The method of embodiment 12, wherein the capability information for the one or more hardware resources used when a cell and / or carrier is operational comprises one or more of: power consumption of the one or more hardware resources in each of the sleep and / or power modes; power consumption of the one or more hardware resources in each of the capability and / or capacity levels; a transition energy and / or transition time for the one or more hardware resources to transition between sleep and / or power modes and / or capability and / or capacity levels.

[0230] 14. The method of embodiment 13, wherein the power consumption comprises an absolute and / or relative power consumption.

[0231] 15. The method of any of embodiments 1 to 14, comprising determining one or more energy saving features in a network including the first network node and the second network node based on the information.

[0232] 16. The method of embodiment 15, wherein determining the one or more energy saving features in the network comprises determining to deactivate one or more cells or carriers and deactivate the one or more hardware resources used when the one or more cells or carriers are operational.

[0233] 17. The method of any of embodiments 1 to 16, comprising forwarding the information to a third network node.

[0234] 18. The method of any of embodiments 1 to 17, comprising receiving, from one or more further network nodes, further information identifying one or more further cells and / or carriers and, for each further cell or carrier, one or more further hardware resources used when the further cell and / or carrier is operational.

[0235] 19. The method of any of embodiments 1 to 18, wherein each of one or more of the hardware resources comprises one or more of: one or more hardware components; one or more network nodes; one or more network functions; one or more antennas; one or more antenna arrays; one or more antenna segments; one or more data processors; one or more baseband processors; one or more digital signal processors (DSPs); one or more radio units; one or more distributed units (Dlls); one or more central units (CUs); one or more circuits; one or more power amplifiers.

[0236] 20. The method of any of embodiments 1 to 19, wherein each of the first network node and / or the second network node comprises one or more of: a base station; an eNodeB; a gNodeB;

[0237] O-DU;

[0238] O-CU;

[0239] O-CU-CP;

[0240] O-CU-UP;

[0241] O-eNB; gNB-CU; gNB-CU-CP; gNB-DU; near-RT RIC; non-RT RIC;

[0242] SMO node;

[0243] CAM node; core network node. 21. The method of any of embodiments 1 to 20, wherein the one or more hardware resources used when a cell and / or carrier is operational comprises: the one or more hardware resources used when a cell and / or carrier is available, enabled, active, provided, functional and / or useable; the one or more hardware resources used to support, enable, activate, provide, maintain and / or sustain a cell and / or carrier; the one or more hardware resources used to transmit and / or receive signals associated with the cell and / or carrier; and / or the one or more hardware resources used to transmit and / or receive user data.

[0244] 22. The method of any of embodiments 1 to 21 , comprising sending a request for the information to the second network node, wherein the information is received from the second network node in response to the request.

[0245] 23. The method of any of embodiments 1 to 22, wherein the first network node or the second network node controls, operates and / or serves the one or more cells and / or carriers and / or the one or more hardware resources.

[0246] 24. A method performed by a second network node for sending information, the method comprising: sending, to a first network node, information identifying one or more cells and / or carriers and, for each cell or carrier, one or more hardware resources used when the cell and / or carrier is operational.

[0247] 25. The method of embodiment 24, comprising determining the one or more hardware resources used when each cell and / or carrier is operational.

[0248] 26. The method of embodiment 25, comprising receiving, from one or more further network nodes, hardware information identifying one or more of the one or more hardware resources, wherein determining the one or more hardware resources comprises determining the one or more hardware resources based on the further information.

[0249] 27. The method of embodiment 26, wherein the hardware information identifying a hardware resource is received from a further network node that controls and / or operates the hardware resource. 28. The method of embodiment 26 or 27, wherein the hardware information identifies one or more of: an association between the one or more of the one or more hardware resources and one or more of the cells and / or carriers; an indication that the one or more of the one or more hardware resources is used when one or more of the cells and / or carriers is operational.

[0250] 29. The method of any of embodiments 26 to 28, comprising receiving capability information from the one or more further network nodes identifying one or more capabilities of the one or more hardware resources.

[0251] 30. The method of any of embodiments 25 to 29, comprising receiving, from one or more further network nodes, cell / carrier information identifying one or more of the cells and / or carriers, wherein determining the one or more hardware resources comprises determining the one or more hardware resources based on the cell / carrier information.

[0252] 31. The method of embodiment 30, wherein the cell / carrier information identifying a cell or carrier is received from a further network node that controls operates and / or serves the cell or carrier.

[0253] 32. The method of any of embodiments 24 to 31 , wherein the information identifies one or more groups of hardware resources, wherein each group contains one or more of the hardware resources.

[0254] 33. The method of embodiment 32, wherein each of the hardware resources may be included in one or more of the groups.

[0255] 34. The method of embodiment 32 or 33, wherein the information identifies the one or more hardware resources used when each cell or carrier is operational by identifying, for each cell or carrier, one or more of the groups used when the cell and / or carrier is operational.

[0256] 35. The method of any of embodiments 32 to 34, wherein the information identifies that one or more of the groups is included in one or more other groups. 36. The method of any of embodiments 32 to 35, wherein the information identifies an identifier for each of the one or more groups.

[0257] 37. The method of embodiment 36, wherein the information identifies, for each of the cells and / or carriers, one or more identifiers of one or more groups of hardware resources used when the cell and / or carrier is operational.

[0258] 38. The method of embodiment 36 or 37, wherein at least part of the identifier of a group is based on the one or more hardware resources in the group and / or one or more groups in the group.

[0259] 39. The method of any of embodiments 36 to 38, wherein: the identifier for each group is unique within a network including the first network node and / or the second network node or a part of the network; and / or the identifier for each group is globally unique.

[0260] 40. The method of any of embodiments 24 to 39, wherein the information identifies that one or more of the hardware resources is used by multiple network nodes.

[0261] 41. The method of any of embodiments 24 to 40, comprising sending, to the first network node, capability information identifying one or more capabilities of the one or more hardware resources used when each of one or more of the cells and / or carriers is operational.

[0262] 42. The method of embodiment 28 or 41 , wherein the capability information for the one or more hardware resources used when a cell and / or carrier is operational comprises one or more of: a plurality of sleep and / or power modes supported by the one or more hardware resources; a current sleep and / or power modes of the one or more hardware resources; a plurality of capability and / or capacity levels supported by the one or more hardware resources; a current capability and / or capacity level of the one or more hardware resources; an indication of whether the one or more hardware resources can provide energy consumption measurements. 43. The method of embodiment 42, wherein the capability information for the one or more hardware resources used when a cell and / or carrier is operational comprises one or more of: power consumption of the one or more hardware resources in each of the sleep and / or power modes; power consumption of the one or more hardware resources in each of the capability and / or capacity levels; a transition energy and / or transition time for the one or more hardware resources to transition between sleep and / or power modes and / or capability and / or capacity levels.

[0263] 44. The method of embodiment 43, wherein the power consumption comprises an absolute and / or relative power consumption.

[0264] 45. The method of any of embodiments 24 to 44, wherein each of one or more of the hardware resources comprises one or more of: one or more hardware components; one or more network nodes; one or more network functions; one or more antennas; one or more antenna arrays; one or more antenna segments; one or more data processors; one or more baseband processors; one or more digital signal processors (DSPs); one or more radio units; one or more distributed units (Dlls); one or more central units (CUs); one or more circuits; one or more power amplifiers.

[0265] 46. The method of any of embodiments 24 to 45, wherein each of the first network node and / or the second network node comprises one or more of: a base station; an eNodeB; a gNodeB; O-DU;

[0266] O-CU;

[0267] O-CU-CP;

[0268] O-CU-UP;

[0269] O-eNB; gNB-CU; gNB-CU-CP; gNB-DU; near-RT RIC; non-RT RIC;

[0270] SMO node;

[0271] CAM node; core network node.

[0272] 47. The method of any of embodiments 24 to 46, wherein the one or more hardware resources used when a cell and / or carrier is operational comprises: the one or more hardware resources used when a cell and / or carrier is available, enabled, active, provided, functional and / or useable; the one or more hardware resources used to support, enable, activate, provide, maintain and / or sustain a cell and / or carrier; the one or more hardware resources used to transmit and / or receive signals associated with the cell and / or carrier; and / or the one or more hardware resources used to transmit and / or receive user data.

[0273] 48. The method of any of embodiments 24 to 47, comprising receiving a request for the information from the second network node, wherein the information is sent to the first network node in response to the request.

[0274] 49. The method of any of embodiments 24 to 48, wherein the first network node or the second network node controls, operates and / or serves the one or more cells and / or carriers and / or the one or more hardware resources.

[0275] 50. The method of any of the previous embodiments, further comprising: obtaining user data; and forwarding the user data to a host or a user equipment. Group D Embodiments

[0276] 51. A network node comprising: processing circuitry configured to cause the network node to perform any of the steps of any of the Group B embodiments; power supply circuitry configured to supply power to the processing circuitry.

[0277] 52. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to provide user data; and a network interface configured to initiate transmission of the user data to a network node in a cellular network for transmission to a user equipment (UE), the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0278] 53. The host of the previous embodiment, wherein: the processing circuitry of the host is configured to execute a host application that provides the user data; and the UE comprises processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0279] 54. A method implemented in a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: providing user data for the UE; and initiating a transmission carrying the user data to the UE via a cellular network comprising the network node, wherein the network node performs any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0280] 55. The method of the previous embodiment, further comprising, at the network node, transmitting the user data provided by the host for the UE.

[0281] 56. The method of any of the previous 2 embodiments, wherein the user data is provided at the host by executing a host application that interacts with a client application executing on the UE, the client application being associated with the host application. 57. A communication system configured to provide an over-the-top (OTT) service, the communication system comprising: a host comprising: processing circuitry configured to provide user data for a user equipment (UE), the user data being associated with the over-the-top service; and a network interface configured to initiate transmission of the user data toward a cellular network node for transmission to the UE, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to transmit the user data from the host to the UE.

[0282] 58. The communication system of the previous embodiment, further comprising: the network node; and / or the UE.

[0283] 59. A host configured to operate in a communication system to provide an over-the-top (OTT) service, the host comprising: processing circuitry configured to initiate receipt of user data; and a network interface configured to receive the user data from a network node in a cellular network, the network node having a communication interface and processing circuitry, the processing circuitry of the network node configured to perform any of the operations of any of the Group B embodiments to receive the user data from a user equipment (UE) for the host.

[0284] 60. The host of the previous 2 embodiments, wherein: the processing circuitry of the host is configured to execute a host application that receives the user data; and the host application is configured to interact with a client application executing on the UE, the client application being associated with the host application.

[0285] 61. The host of the any of the previous 2 embodiments, wherein the initiating receipt of the user data comprises requesting the user data. 62. A method implemented by a host configured to operate in a communication system that further includes a network node and a user equipment (UE), the method comprising: at the host, initiating receipt of user data from the UE, the user data originating from a transmission which the network node has received from the UE, wherein the network node performs any of the steps of any of the Group B embodiments to receive the user data from the UE for the host.

[0286] 63. The method of the previous embodiment, further comprising at the network node, transmitting the received user data to the host.

[0287] 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.

[0288] 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

Claims1. A method (1300) performed by a first network node for receiving information, the method comprising: receiving (1302), from a second network node, information identifying: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier.

2. The method of claim 1 , wherein, for each cell or carrier, the one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier comprise one or more identifiers of one or more groups of hardware resources used when the cell or carrier is operational.

3. The method of claim 1 or 2, wherein the information identifies that one or more of the groups (1108, 1110, 1112) of hardware resources is included in one or more other groups.

4. The method of any of claims 1 to 3, wherein at least part of the identifier of a group (1108, 1110, 1112) is based on an identifier of one or more hardware resources in the group and / or the identifier of one or more groups in the group.

5. The method of any of claims 1 to 4, wherein: the identifier for each group (1108, 1110, 1112) is unique within a network including the first network node and / or the second network node or a part of the network; and / or the identifier for each group is globally unique.

6. The method of any of claims 1 to 5, wherein the information identifies that one or more of the groups (1108, 1110, 1112) of hardware resources is used by multiple network nodes.

7. The method of any of claims 1 to 6, comprising receiving capability information from the second network node identifying one or more capabilities of the one or more groups (1108, 1110, 1112) of hardware resources.

8. The method of claim 7, wherein the capability information for the one or more groups (1108, 1110, 1112) of hardware resources comprises one or more of:a plurality of sleep and / or power modes supported by the one or more groups (1108, 1110, 1112) of hardware resources; a current sleep and / or power modes of the one or more groups of hardware resources; a plurality of capability and / or capacity levels supported by the one or more groups of hardware resources; a current capability and / or capacity level of the one or more groups of hardware resources; an indication of whether the one or more groups of hardware resources can provide energy consumption measurements.

9. The method of claim 8, wherein the capability information for the one or more groups (1108, 1110, 1112) of hardware resources comprises one or more of: absolute and / or relative power consumption of the one or more groups of hardware resources in each of the sleep and / or power modes; absolute and / or relative power consumption of the one or more groups of hardware resources in each of the capability and / or capacity levels; a transition energy and / or transition time for the one or more groups of hardware resources to transition between sleep and / or power modes and / or capability and / or capacity levels.

10. The method of any of claims 1 to 9, comprising determining one or more energy saving features in a network including the first network node and the second network node based on the information.

11. The method of claim 10, wherein determining the one or more energy saving features in the network comprises determining to deactivate one or more cells or carriers and deactivate the one or more groups (1108, 1110, 1112) of hardware resources associated with the deactivated one or more cells or carriers.

12. A method (1400) performed by a second network node for sending information, the method comprising: sending (1402), to a first network node, information identifying: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more groups (1108, 1110,13. The method of claim 12, wherein, for each cell or carrier, the one or more identifiers of one or more groups of hardware resources associated with the cell or carrier comprise one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources used when the cell or carrier is operational.

14. The method of claim 12 or 13, comprising receiving, from one or more further network nodes, hardware information identifying one or more of the one or more groups (1108, 1110, 1112) of hardware resources, and determining the one or more groups of hardware resources based on the hardware information.

15. The method of claim 14, wherein the hardware information identifying a group (1108, 1110, 1112) of hardware resources is received from a further network node that controls and / or operates the group of hardware resources.

16. The method of claim 14 or 15, wherein the hardware information identifies one or more of: an association between the one or more of the one or more groups (1108, 1110, 1112) of hardware resources and one or more of the cells and / or carriers; an indication that the one or more of the one or more groups of hardware resources is used when one or more of the cells and / or carriers is operational.

17. The method of any of claims 14 to 16, comprising receiving capability information from the one or more further network nodes identifying one or more capabilities of the one or more groups (1108, 1110, 1112) of hardware resources.

18. The method of any of claims 14 to 17, comprising receiving, from one or more further network nodes, cell / carrier information identifying one or more of the cells and / or carriers, wherein determining the one or more groups (1108, 1110, 1112) of hardware resources comprises determining the one or more groups of hardware resources based on the cell / carrier information.

19. The method of claim 18, wherein the cell / carrier information identifying a cell or carrier is received from a further network node that controls, operates and / or serves the cell or carrier.

20. The method of any of claims 12 to 19, wherein the information identifies that one or more of the groups (1108, 1110, 1112) of hardware resources is included in one or more other groups of hardware resources.

21. The method of claim 12 or 20, wherein at least part of the identifier of a group (1108, 1110, 1112) is based on an identifier of one or more hardware resources in the group and / or an identifier of one or more groups in the group.

22. The method of any of claims 12 to 21 , wherein: the identifier for each group is unique within a network including the first network node and / or the second network node or a part of the network; and / or the identifier for each group (1108, 1110, 1112) is globally unique.

23. The method of any of claims 12 to 22, wherein the information identifies that one or more of the groups (1108, 1110, 1112) of hardware resources is used by multiple network nodes.

24. The method of any of claims 12 to 23, comprising sending, to the first network node, capability information identifying one or more capabilities of the one or more groups (1108, 1110, 1112) of hardware resources.

25. The method of claim 17 or 24, wherein the capability information for the one or more groups (1108, 1110, 1112) of hardware resources comprises one or more of: a plurality of sleep and / or power modes supported by the one or more groups of hardware resources; a current sleep and / or power modes of the one or more groups of hardware resources; a plurality of capability and / or capacity levels supported by the one or more groups of hardware resources; a current capability and / or capacity level of the one or more groups of hardware resources; an indication of whether the one or more groups of hardware resources can provide energy consumption measurements.

26. The method of claim 25, wherein the capability information for the one or more hardware resources comprises one or more of: absolute and / or relative power consumption of the one or more groups of hardware resources in each of the sleep and / or power modes; absolute and / or relative power consumption of the one or more groups of hardware resources in each of the capability and / or capacity levels; a transition energy and / or transition time for the one or more groups of hardware resources to transition between sleep and / or power modes and / or capability and / or capacity levels.

27. The method of any of claims 12 to 26, comprising receiving a request for the information from the first network node, wherein the information is sent to the first network node in response to the request.

28. The method of any of claims 1 to 27, wherein each of one or more of the groups (1108, 1110, 1112) of hardware resources comprises one or more of: one or more hardware components; one or more network nodes; one or more network functions; one or more antennas; one or more antenna arrays; one or more antenna segments; one or more data processors; one or more baseband processors; one or more digital signal processors (DSPs); one or more radio units; one or more distributed units (Dlls); one or more central units (CUs); one or more circuits; one or more power amplifiers.

29. The method of any of claims 1 to 28, wherein each of the first network node and / or the second network node comprises one or more of: a base station; an eNodeB;a gNodeB;O-DU;O-CU;O-CU-CP;O-CU-UP;O-eNB; gNB-CU; gNB-CU-CP; gNB-DU; near-RT RIC; non-RT RIC;SMO node;CAM node; core network node.

30. The method of any of claims 1 to 29, wherein the one or more groups (1108, 1110, 1112) of hardware resources comprises: the one or more groups of hardware resources used when a cell and / or carrier is available, enabled, active, provided, functional and / or useable; the one or more groups of hardware resources used to support, enable, activate, provide, maintain and / or sustain a cell and / or carrier; the one or more groups of hardware resources used to transmit and / or receive signals associated with the cell and / or carrier; and / or the one or more groups of hardware resources used to transmit and / or receive user data.

31. The method of any of claims 1 to 30, wherein the first network node or the second network node controls, operates and / or serves the one or more cells and / or carriers and / or the one or more hardware resources.

32. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations comprising: receiving (1302), from a second network node, information identifying: one or more cells and / or carriers; andfor each cell or carrier, one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier.

33. The computer-readable medium of claim 32, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (1300) of any of claims 2 to 11 , and 28 to 31 when dependent on any of claims 2 to 11 .

34. A tangible, non-transient computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform operations comprising: sending (1402), to a first network node, information identifying: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier.

35. The computer-readable medium of claim 34, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform the method (1400) of any of claims 13 to 27, and 28 to 31 when dependent on any of claims 13 to 27.

36. A computer program, comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (1300, 1400) according to any of claims 1 to 31.

37. A computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to carry out the method (1300, 1400) according to any of claims 1 to 31.

38. A carrier containing the computer program of claim 37, wherein the carrier is one of an electronic signal, optical signal, radio signal, or computer-readable medium.

39. An apparatus for receiving information, the apparatus comprising processing circuitry and a memory, the apparatus configured to: receive (1302), from a second network node, information identifying: one or more cells and / or carriers; andfor each cell or carrier, one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier.

40. The apparatus of claim 39, wherein the apparatus is configured to perform the method (1300) of any of claims 2 to 11 , and 28 to 31 when dependent on any of claims 2 to 11.

41. An apparatus for sending information, the apparatus comprising processing circuitry and a memory, the apparatus configured to: sending (1402), to a first network node, information identifying: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more groups (1108, 1110, 1112) of hardware resources associated with the cell or carrier.

42. The apparatus of claim 41 , wherein the apparatus is configured to perform the method (1400) of any of claims 13 to 27, and 28 to 31 when dependent on any of claims 13 to 27.

Images