Receiving and transmitting information

Abstract

According to one 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 hardware resource groups associated with the cell or carrier.

Description

Technical Field

[0001] Examples of this disclosure relate to sending and receiving information, such as sending and receiving information that identifies the energy consumption of one or more hardware resource groups. Background Technology

[0002] The current fifth-generation radio access network (5G RAN) (also known as NG-RAN) architecture is in Figure 1 As shown in and described in 3GPP Technical Specification (TS) 38.401 v17.2.0, NG-RAN comprises a set of gNodeBs (gNBs) connected to the 5th Generation Core (5GC) via NG interfaces. As specified in 3GPP TS 38.300, NG-RAN may also comprise a set of ng-eNodeBs (ng-eNBs). An ng-eNB may comprise an ng-eNB-Centralized Unit (CU) and one or more ng-eNB-Distributed Units (DUs). The ng-eNB-CU and ng-eNB-DU are connected via W1 interfaces. Unless otherwise explicitly specified, the general principles described herein also apply to ng-eNBs and W1 interfaces.

[0003] gNBs can support Frequency Division Duplex (FDD), Time Division Duplex (TDD), or dual-mode operation. gNBs can be interconnected via the Xn interface. A gNB can include a gNB-CU and one or more gNB-DUs. The gNB-CU and gNB-DU are connected via the F1 interface. One gNB-DU is connected to only one gNB-CU. NG, Xn, and F1 are logical interfaces.

[0004] For NG-RAN, the NG and Xn-C interfaces for a gNB including gNB-CU and gNB-DU terminate in the gNB-CU. For Evolved Non-Standalone Dual Connectivity (EN-DC), the S1-U and X2-C interfaces for a gNB including gNB-CU and gNB-DU terminate in the gNB-CU. The gNB-CU and the connected gNB-DU are visible to other gNBs and 5GC only as gNBs.

[0005] exist Figure 2The diagram illustrates a separate overall architecture for the gNB-CU control plane (CP) and gNB-CU user plane (UP). A gNB can include a gNB-CU-CP, multiple gNB-CU-UPs, and multiple gNB-DUs. The gNB-CU-CP is connected to the gNB-DU via an F1-C interface. The gNB-CU-UP is connected to the gNB-DU via an F1-U interface. The gNB-CU-UP is connected to the gNB-CU-CP via an 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.

[0006] Figure 1 and 2 The architecture shown is the one that 3GPP has already defined for 5G. Other standardization organizations (such as the O-RAN Alliance) have further extended the above architecture and have, for example, separated the gNB-DU into two other nodes connected via a fronthaul interface. Figure 3 The O-RAN architecture is illustrated. The lower-layer node of the separated gNB-DU will contain the PHY protocol and RF components, while the upper-layer node of the separated gNB-DU will host Radio Link Control (RLC) and Media Access Control (MAC). In the O-RAN architecture, the upper-layer node is referred to as the O-DU, and the lower-layer node is referred to as the O-RU.

[0007] The O-RAN architecture also adds a new node to the RAN, namely 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 (such as O-DU, O-CU-CP, and O-CU-UP) through E2 interfaces.

[0008] Section 8.4.1 of TS 38.423 describes the Xn setup procedure. The Xn setup procedure (also as...) Figure 4 (As shown in the image) is used to exchange the application-level configuration data required for two NG-RAN nodes to interoperate correctly via the Xn-C interface. This process uses non-UE-associated signaling.

[0009] The first NG-RAN node initiates the process by sending an XN SETUP REQUEST message to the second NG-RAN node. Upon receiving this message, the second NG-RAN node should store the configuration data associated with the first NG-RAN node. The second NG-RAN node responds with an XN SETUP RESPONSE message.

[0010] The XN establishment request message may include a list of servable NR cells or a list of servable E-UTRA cells, or both, and may further include so-called servable cell information NR IE or so-called servable cell information E-UTRA IE for each cell.

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

[0012] Section 8.4.2 of TS 38.423 describes the NG-RAN node configuration update process, and it also addresses successful operations in... Figure 5 The NG-RAN node configuration update procedure is shown in the diagram. This procedure is used to update the application-level configuration data required for proper interoperability between two NG-RAN nodes via the Xn-C interface. This procedure uses non-UE-associated signaling.

[0013] The first NG-RAN node initiates this process by sending an NG-RAN NODECONFIGURATION UPDATE message to the second NG-RAN node. Upon receiving this message, the second NG-RAN node should update the configuration data it already stores locally that is associated with the first NG-RAN node.

[0014] NG-RAN node configuration update messages may include a list of servable NR cells to be updated or a list of servable E-UTRA cells to be updated, or both. These messages may include so-called servable cell information (NRIE) or so-called servable cell information (E-UTRA IE) for each cell to be updated.

[0015] Section 8.2.3 of TS 38.473 describes the F1 setup procedure. The F1 setup procedure (which also addresses successful operation in...) Figure 6 (As shown in the image) is used to exchange the application-level data required for proper interoperability between the gNB-DU and gNB-CU via the F1 interface. This process uses non-UE-associated signaling.

[0016] The gNB-DU initiates the process by sending an F1 SETUP REQUEST message containing appropriate data to the gNB-CU. The gNB-CU responds with an F1 SETUP RESPONSE message containing appropriate data. The exchanged data should be stored in both the gNB-CU and gNB-DU. When the process is complete, the F1 interface is operational and can exchange further F1 messages.

[0017] The F1 setup request message may include a list of cells served by the gNB-DU, which in turn includes the so-called Served Cell Information (IE) for each cell.

[0018] Section 8.2.4 of TS 38.473 describes the gNB-DU configuration update procedure. The gNB-DU configuration update procedure (which also addresses successful operations on...) Figure 7 (As shown in the image) This process updates the application-level configuration data required for proper interoperability between the gNB-DU and gNB-CU via the F1 interface. This procedure uses non-UE-associated signaling.

[0019] The gNB-DU initiates the process by sending a GNB-DU CONFIGURATION UPDATE message to the gNB-CU, which includes a set of appropriately updated configuration data that has just been put into use. The gNB-CU responds with a GNB-DU CONFIGURATION UPDATE ACKNOWLEDGE message to acknowledge that it has successfully updated the configuration data. The exchanged data should be stored in both the gNB-CU and gNB-DU.

[0020] GNB-DU configuration update messages may include a list of served cells to be modified, which in turn includes the so-called Served Cell Information (IE) for each cell.

[0021] For further details, please refer to 3GPP TS 38.473 and below.

[0022] Figure 8 An example of a generic RAN network resource model (NRM) is shown. Current NR and NG-RAN NRMs are described in 3GPP TS 28.541 v18.5.0, and generic RAN NRMs are described in TS 28.662 v17.0.0.

[0023] Figure 8 The definition of SectorEquipmentFunction shown is as follows. This Information Object Class (IOC) represents a group of cells within a geographic area that share common functions with AntennaFunction, TMAFunction, and supporting equipment (e.g., power amplifiers). The attributes of SectorEquipmentFunction are described in Clause 4.3.1.2 of 3GPP TS 28.662. The main problem with this definition is its granularity and the information it transmits. It cannot identify the physical hardware units or components in which the group of cells or carriers consume power.

[0024] The goal of RAN3 Rel-18 work item RP-220635 is to specify data collection enhancements and signaling support within existing NG-RAN interfaces and architectures (including non-split and split architectures) for AI / ML-based network power saving, load balancing, and mobility optimization.

[0025] O-RAN Network Energy Saving Use Case Technical Report 2.0 describes different energy-saving features:

[0026] Carrier and cell off / on

[0027] RF channel reconfiguration off / on

[0028] Advanced hibernation mode selection

[0029] O-Cloud resource energy-saving mode

[0030] Figure 9 Examples of different levels of energy-saving features and their corresponding network node deployments are shown. Figure 9 To the right of this is an indicative reference time scale for the operation of these energy-saving functions.

[0031] Specific challenges exist. For example, each RAN energy performance (EP) characteristic at the carrier, node, and network levels requires fine-tuning of traffic load thresholds and durations. These durations indicate how long the load needs to be below a threshold to allow the cell to enter energy-saving mode, and similarly, how long the load needs to be above a threshold to allow the cell to exit energy-saving mode and restore full system performance. For instance, these load thresholds and durations must be set based on the traffic patterns within the cell. Setting conservative values ​​will mean missing energy-saving opportunities, while setting more aggressive values ​​will mean lowering specific KPIs.

[0032] Adjusting RAN EP characteristics to find an optimal balance between energy saving and maintaining KPIs requires specific network topology-related information that is not yet available.

[0033] One issue is that RAN EP characteristics are applied to or affect cells or (sector) carriers, which are logical network (NW) entities and therefore logical energy consumers, while the energy is actually consumed in physical hardware (HW) products and / or their components, which are physical energy consumers and whose energy consumption can be measured / metered. This makes adjusting EP characteristics even more difficult because in actual network deployments, multiple cells or (sector) carriers are often allocated to the same hardware product / unit, which can lead to suboptimal use of EP characteristics and thus suboptimal energy-saving gains.

[0034] Furthermore, in some cases, coordination between EP features is required. For example, in some hardware product deployments, activating EP feature 1 instead of EP feature 2 may be beneficial because it achieves greater energy savings, while in other hardware product deployments, the opposite may be true (assuming similar business scenarios). Summary of the Invention

[0035] Specific aspects and embodiments of this disclosure can provide solutions to these or other challenges. Examples of this disclosure introduce the concept of an Energy Consumer Group (ECG), which groups all cells and / or (sector) carriers sharing hardware units or hardware components, and thus groups the energy consumption of those hardware units or components. Specific embodiments can provide one or more of the following technical advantages. For example, by utilizing transmitted / received information related to hardware resource groups (logical and / or physical) (e.g., ECGs), local RAN EP optimization for cells or carriers that are purely logical energy consumers can be avoided. Energy savings can be maximized, for example, at the cluster and network levels.

[0036] One aspect of this disclosure provides a method for receiving information performed by a first network node. The method includes 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 hardware resource groups associated with said cell or carrier.

[0037] Another aspect of this disclosure provides a method for transmitting information performed by a second network node. The method includes: transmitting 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 hardware resource groups associated with said cell or carrier. Attached Figure Description

[0038] To better understand the examples of this disclosure, and to more clearly illustrate how these examples can be implemented, reference will now be made to the accompanying drawings by way of example only, wherein:

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

[0040] Figure 2 The separate overall architecture for gNB-CU-CP and gNB-CU-UP is shown;

[0041] Figure 3 The O-RAN architecture is shown;

[0042] Figure 4 The process of establishing Xn is shown;

[0043] Figure 5 The configuration update process for a successfully operated NG-RAN node is illustrated.

[0044] Figure 6 The F1 setup process for a successful operation is shown;

[0045] Figure 7 The gNB-DU configuration update process for a successful operation is shown;

[0046] Figure 8 An example of a generic RAN network resource model (NRM) is shown;

[0047] Figure 9 Examples of different levels of energy-saving features and their corresponding network node deployments are shown.

[0048] Figure 10 An example of a hardware unit according to the present disclosure is shown;

[0049] Figure 11 An example of another hardware unit according to the present disclosure is shown;

[0050] Figure 12 This is a flowchart illustrating an example of a method according to this disclosure;

[0051] Figure 13 A method performed by a network node according to an embodiment of the present disclosure is illustrated;

[0052] Figure 14 A method performed by a network node according to an embodiment of the present disclosure is illustrated;

[0053] Figure 15 A method performed by a network node according to an embodiment of the present disclosure is illustrated;

[0054] Figure 16 A method performed by a network node according to an embodiment of the present disclosure is illustrated;

[0055] Figure 17 An example of a mapping from a cell to a group of energy consumers according to this disclosure is shown;

[0056] Figure 18 This illustrates an example of how ECG auxiliary information and ECG information are exchanged through a network interface;

[0057] Figure 19 This illustrates an example of a non-real-time RIC obtaining ECG information from an O-DU for network-level power saving feature optimization;

[0058] Figure 20An example is shown where the gNB-CU-CP obtains ECG information from the gNB-DU, eNB, and another gNB-CU-CP (#2) and uses it for node-level power saving optimization.

[0059] Figure 21 An example overview of a power-saving function is shown, which receives input data including ECG and provides thresholds for different RAN EP characteristics as output based on the operator's intent;

[0060] Figure 22 Examples of communication systems according to some embodiments are shown;

[0061] Figure 23 A UE according to some embodiments is shown;

[0062] Figure 24 A network node according to some embodiments is shown;

[0063] Figure 25 This is a block diagram of the host based on the various aspects described in this article;

[0064] Figure 26 This is a block diagram illustrating a virtualized environment in which functionality implemented by some embodiments can be virtualized;

[0065] Figure 27 A communication diagram is shown illustrating communication between a host and a UE via a network node through a partial wireless connection, according to some embodiments; and

[0066] Figure 28 A network node according to another embodiment is shown. Detailed Implementation

[0067] For purposes of explanation and not limitation, specific details, such as particular embodiments or examples, are set forth below. Those skilled in the art will understand that other examples may be used in addition to these specific details.

[0068] In this disclosure, hardware resources may be, for example, one or more physical hardware components, but additionally or alternatively, in some examples, may include one or more logical energy consumers, such as network nodes or other logical hardware units / components.

[0069] As described above, the examples of this disclosure introduce the concept of an Energy Consumer Group (ECG), which groups all cells and / or (sector) carriers sharing a hardware unit or hardware component, and thus groups the energy consumption of that hardware unit or component. An ECG can 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 can 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 can represent or associated with a cell / carrier sharing one or more hardware components when operational. Thus, in some examples, an ECG is a logical entity representing (or associated with) a specific physical hardware and discloses or expresses connections or dependencies of other logical entities (e.g., cells and / or carriers) to physical hardware resources. In some examples, the recipient of ECG information (the entity using the ECG information) can utilize the ECG information without knowing the specific physical hardware associated with the ECG.

[0070] In some examples, ECG information can be created and updated dynamically based on network configuration (i.e., the allocation of cells and (sector) carriers to physical hardware). In some examples, an ECG can span two or more network nodes, such as NG-RAN nodes or their logical entities. For example, two NG-RAN nodes or their logical entities can share hardware units, such as radio units. An ECG can be identified, for example, by a globally unique identifier.

[0071] In some examples, ECG information can be propagated through network interfaces (e.g., F1, Xn, X2, E2, and / or O1) to update and / or merge ECG information, and used as additional input for better orchestration of RAN energy performance (EP) characteristics, i.e., deriving the most suitable combination of EP characteristics to activate and adapting their corresponding thresholds based on hardware energy-saving capabilities, traffic load forecasts, observed KPIs, and operator intent.

[0072] Some examples in this disclosure are described for energy-saving / optimization use cases, but can be applied to other use cases where mapping cell and / or (sector) carriers to the physical hardware to which they are assigned is necessary or beneficial. Another example use case could be passive intermodulation (PIM) avoidance / mitigation.

[0073] Some examples of this disclosure can create a mapping between cells and / or carriers, which are logical energy-consuming entities, and the logical and / or physical energy-consuming hardware to which they are assigned (e.g., energy consumer groups (ECGs)). Network nodes or functions that control, adjust, or otherwise influence the characteristics of the RAN EP can utilize this ECG information, for example, to achieve more energy-efficient service management and greater network energy savings.

[0074] ECG can represent, for example, a hardware unit (such as a radio unit), or a component or group of components of a hardware unit (such as the antenna segment of a radio unit).

[0075] Figure 10 An example of a hardware unit 1000 according to the present disclosure is shown. In this example, the hardware unit 1000 is associated with three cells, namely cell 1, cell 2 and cell 3. Figure 11 Another example of a hardware unit 1100 according to the present disclosure is shown. The hardware unit includes hardware component 1102, hardware component 1104, and hardware component 1106. A first ECG 1108 includes hardware component 1102 and is associated with cell 1, cell 2, and cell 3. A second ECG 1110 includes hardware component 1104 and is associated with cell 1. A third ECG 1112 includes hardware component 1106 and is associated with cell 2 and cell 3.

[0076] In some examples, ECG includes all cell and / or (sector) carriers that share power consumption by sharing at least certain physical hardware.

[0077] In some examples, a cell or carrier can be part of multiple ECGs (i.e., consuming power in multiple hardware units or components). Similarly, in some examples, a hardware unit or component can be part of multiple ECGs, for example, if multiple ECGs are combined into a single ECG. Consider... Figure 10 and 11 ECGs 1a, 1b, and 1c can be combined into ECG 1, while ECGs 1a, 1b, and 1c can remain unchanged. That is, in this example, the hardware components within hardware unit 1 can be part of two ECGs.

[0078] In some examples, the first network node may obtain ECG information (related to one or more ECGs) from the second network node in a fourth message via a network interface (e.g., F1, Xn, X2, E2, and / or O1). The first network node may optionally be required to request the ECG information from the second network node in a third message before receiving it. This is in... Figure 12 The example shown is as follows. Figure 12 This is a flowchart illustrating an example of a method according to this disclosure.

[0079] In some examples, an ECG can have a unique identifier at least at the network level (or a portion of the network). In some examples, the unique identifier can be based on, or derived from, the unique identifier of the underlying hardware unit or component represented by the ECG. For example, the identifier could be the result of a hash function that takes the sequence number of the underlying hardware unit or component (or one or more units / components) as input. This ensures unambiguous distribution, identification, and merging of ECG information among network nodes, as cells and carriers in different network nodes may share the same physical hardware.

[0080] In some examples, ECG information may include a list of RAN EP features supported by the underlying hardware units or components, along with their energy-saving potential or gains. This indicates whether a particular hardware product is more optimized in design for a specific EP feature. For example, if a hardware unit cannot perform fine-grained power domain on / off without affecting all cells or carriers sharing that hardware unit, then the cell or carrier on / off EP feature has very low energy-saving potential (unless all cells and carriers corresponding to the ECG are collectively on / off).

[0081] In some examples, the ECG or underlying hardware unit or component may include an energy meter and thus be able to provide energy consumption measurements.

[0082] Specific embodiments can provide one or more of the following technical advantages. For example, by utilizing the transmitted / received information related to hardware resource groups (logical and / or physical) (e.g., ECG), local RAN EP optimization for cells or carriers that are purely logical energy consumers can be avoided. Energy savings can be maximized, for example, at the cluster and network levels.

[0083] This can be used for both centralized and distributed energy-saving functions, decoupled and non-decoupled architectures, cloud environments, and dedicated hardware, as ECG information can be exchanged through NG-RAN F1, X2, Xn, NG and O-RAN E2, O1 interfaces, and potentially other interfaces. The O1 interface connects the SMO to the RAN managed units. These units include near real-time RICs, O-CU-CPs, O-CU-UPs, O-DUs, O-RUs, and Open Evolved Node Bs (O-eNBs).

[0084] Information sharing, as exemplified by this disclosure, may be optional for inter-vendor operability / deployment, but it may also be included in 3GPP, O-RAN, and related standards.

[0085] This information can be used, for example, by service management functions and / or AI / ML orchestration functions to free all cells in an ECG from services / UEs by reassigning services / UEs to other cells in other ECGs, thereby maximizing energy savings by placing hardware units into deep sleep. Similarly, in some examples, this information can also be used by one or more functions to ensure that all cells across an ECG use RAN EP features (e.g., cell-specific RAN EP features such as cell DTX / DRX) to achieve energy savings gains.

[0086] Some embodiments conceived herein will now be described more fully with reference to the accompanying drawings. These embodiments are provided by way of example to convey the scope of the subject matter to those skilled in the art.

[0087] Figure 13 A method 1300 according to a particular embodiment is illustrated, such as a method for receiving information performed by a first network node. Method 1300 can be performed by a network node (e.g., as referred to separately below). Figure 22 and 24 The method is performed by the network node QQ110 or network node QQ300 described. Method 1300 begins at step 1302 by receiving information from the second network node identifying the following: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more hardware resource groups associated with that cell or carrier.

[0088] Figure 14 A method 1400 according to a particular embodiment is illustrated, such as a method for sending information performed by a second network node. Method 1400 can be performed by a network node (e.g., as referred to separately below). Figure 22 and 24 The method is performed by the described network node QQ110 or network node QQ300. Method 1400 begins at step 1402 by sending information to the first network node identifying the following: one or more cells and / or carriers; and for each cell or carrier, one or more identifiers of one or more hardware resource groups associated with that cell or carrier.

[0089] Figure 15 A method 1500 according to a particular embodiment is illustrated, such as a method for receiving information performed by a first network node. Method 1500 can be performed by a network node (e.g., as referred to separately below). Figure 22 and 24The method is performed by the network node QQ110 or network node QQ300 described. Method 1500 begins at step 1502 by receiving information from the second network node identifying the following: one or more cells and / or carriers; and for each cell or carrier, one or more hardware resources used when that cell and / or carrier is operational.

[0090] Figure 16 A method 1600 according to a particular embodiment is illustrated, such as a method for sending information performed by a second network node. Method 1600 can be performed by a network node (e.g., as referred to separately below). Figure 22 and 24 The method is performed by the network node QQ110 or network node QQ300 described. Method 1600 begins at step 1602 by sending information to the first network node identifying one or more cells and / or carriers; and for each cell or carrier, one or more hardware resources to be used when that cell and / or carrier is operational.

[0091] Specific example embodiments will now be described for illustrative purposes.

[0092] Examples of this disclosure relate to a method performed by a first network node for obtaining ECG information for one or more energy consumer groups (ECGs) from one or more second network nodes. In these examples, an ECG is a specific, non-limiting example of a hardware resource group as mentioned 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. In all these examples, other hardware resource groups, or one or more hardware resources used when each of one or more cells and / or carriers is operational, are possible.

[0093] Network nodes can be one or more of the following examples:

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

[0095] An ECG can be, for example, a logical entity with a unique identifier, including one or more cells or carriers with unique identifiers. Therefore, in one embodiment, ECG information includes (and can be transmitted as) a unique ECG identifier and one or more unique cell or carrier identifiers for the cell(s) or carrier(s) associated with the ECG. Alternatively, in another embodiment, ECG information includes (and can be transmitted as) a unique cell or carrier identifier and one or more unique ECG identifiers for the ECG associated with the cell or carrier (i.e., one or more identifiers for one or more hardware resource groups associated with the cell or carrier).

[0096] In this context, uniqueness can mean globally unique, unique within a network (e.g., a PLMN) or at least a portion or region of the network (e.g., the region from which ECG information is exchanged and / or obtained), so that any kind of ECG confusion is excluded.

[0097] ECG typically refers to a physical hardware unit or component that consumes energy (whether or not that energy consumption can be measured / metered) or multiple such components and / or units (or associated with them).

[0098] In one embodiment, the first network node may additionally request ECG information from the second network node before receiving ECG information. This request may indicate to the second network node ECG information including all ECGs known to the second network node or ECGs indicated to be shared with other network nodes, or 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 one or more specific ECGs.

[0099] Figure 17 An example of a mapping from a cell to a group of energy consumers according to this disclosure is shown. Figure 17 The left side shows examples of energy consumer groups in different hardware architecture variants. This does not reflect the scalability aspects of actual deployments, meaning that in some examples, there may be more radio units with similar hardware architectures, resulting in similar energy consumer groups. Figure 17 The right side shows the cell to Figure 17 The left side of the energy consumer group is an example of how cells are allocated on different hardware.

[0100] In another embodiment, the ECG information may additionally include one or more of the following examples:

[0101] Description of ECG (e.g., what type of hardware unit or component it is, such as a radio unit, power amplifier, baseband processing unit, etc.).

[0102] An indication of whether the ECG (and therefore the underlying hardware unit or component) is being shared by / is being shared by different network nodes.

[0103] Whether the ECG (and therefore the underlying hardware unit or component) can provide an indication of its ability to measure energy consumption (i.e., whether it has energy metering capabilities).

[0104] An indication of the ability of the ECG (and therefore the underlying hardware unit or component) to support energy-saving (or low-power) modes / states or characteristics.

[0105] Status indication of the active and / or inactive power-saving (or low-power) modes / states or characteristics of each ECG (and therefore, the underlying hardware unit or component) (e.g., the number of active transceiver TRX chains, or a list of active power-saving characteristics).

[0106] In relevant embodiments, the capability indicator may include one or more inactive / dormant modes / states having associated absolute and / or relative power levels / consumption. Additionally or alternatively, the capability indicator may include one or more reduced capability / capacity modes / states having associated absolute and / or relative power levels / consumption. The capability indicator may also include additional switching energy and / or total switching time for different modes / states.

[0107] Capability indicators may include one or more of the following information, for example, in the form of a table or list:

[0108] If an ECG (and therefore the underlying hardware unit or component) is in sleep mode, in some examples, the transmission and reception of signals associated with the cell or carrier in that ECG (and therefore, using the underlying hardware unit or component) is typically not possible. However, if an ECG represents only the specific hardware components required for transmission or reception, in some examples, reception or transmission can still be possible separately, provided that no other ECG associated with the cell or carrier is in sleep mode.

[0109] If an ECG (and therefore the underlying hardware unit or component) is in a reduced capacity / performance mode, in some examples, the transmission and reception of signals associated with the ECG's cell or carrier (and therefore, using the underlying hardware unit or component) is generally possible, provided that no other ECGs associated with the cell or carrier are in sleep mode. However, signal transmission and reception may be limited, for example, in terms of network / system capacity. For instance, certain hardware components (such as digital signal processing units / circuits) may operate at a reduced clock speed, which effectively reduces their power consumption but also reduces computational capacity, and thus network / system capacity, as less data may be sent and received within a given timeframe.

[0110] In some examples, if the underlying hardware unit or component is at full load, the absolute or relative power P in full-capacity / full-capacity mode is... F It can be an absolute or relative power level / consumption.

[0111] In some examples, if ECG information is, has been, or will be transmitted as a unique cell or carrier identifier and one or more unique ECG identifiers for the ECG associated with the cell or carrier, additional information related to the ECG (or underlying hardware unit or component), such as a description of the ECG, specific capabilities of the ECG, etc., can be transmitted simultaneously (e.g., in different parts of the same message), after (in subsequent messages), or before (in previous messages). Including a unique ECG identifier in all messages transmitting ECG-related information allows ECG information to be merged across signaling messages, just as it would be merged across network nodes.

[0112] In relevant embodiments, the ECG identifier may be, for example, a unique identifier (e.g., a serial number) of the physical hardware unit or component it represents, or may be derived from the unique identifier (e.g., a serial number) of the physical hardware unit or component it represents, for example, using a hash function.

[0113] As illustrated above, in some examples, multiple ECGs can be arbitrarily combined into one ECG for any reason. In such cases, in some examples, individual ECGs can be retained; that is, individual ECGs and combined ECGs can coexist. Therefore, a hardware unit or its components can be part of multiple ECGs, and the ECGs can follow a hierarchy / sequence.

[0114] In some examples, the hierarchy of an ECG can be reflected in its identifier. For example, an ECG identifier can be part of the identifiers of one or more other ECGs, such as a prefix or suffix. For instance, the identifier of an ECG representing a hardware unit component can have a common part that explicitly or implicitly represents the hardware unit. Therefore, it is not necessary to have an ECG representing the hardware unit itself. In a related embodiment, the ECG identifier can be derived and / or transmitted as two or more distinct part / information elements (IEs), thereby explicitly expressing some form of hierarchy.

[0115] In some examples, the second network node creates the ECG information it sends to the first network node. However, in other examples, the second network obtains the ECG information from another network node (or multiple other nodes) before sending it to the first network node. In this way, ECG information can be exchanged between two network nodes (e.g., two gNB-DUs, or two NG-RAN nodes without a properly functioning Xn interface) that do not have a signaling connection / interface between themselves or a suitable signaling procedure to directly exchange ECG information. For example, in the case of two gNB-DUs, ECG information can be exchanged via F1 (and Xn, if the two gNB-DUs are connected to different gNB-CUs). Similarly, in the case of two NG-RAN nodes without a properly functioning Xn interface, ECG information can be exchanged via the NG interface through the core network CN (e.g., 5G core 5GC).

[0116] In some examples, it is assumed that a second network node, in a sense, owns or controls the cell or carrier for which it creates ECG information (as a logical entity). In some cases, the second network node additionally or alternatively controls the underlying hardware used to implement signal transmission and reception for the corresponding cell or carrier. However, in other cases, a portion of the underlying hardware may be controlled by another logical entity (referred to herein as a third network node), such as an O-RU in an O-RAN architecture. In this case, the second network node knows the logical identifier of the third network node but is unaware of the details regarding the underlying hardware. Therefore, the second network node can communicate with the third network node to obtain ECG auxiliary information in order to create the ECG information.

[0117] Before creating the ECG information, in some examples, the second network node may obtain ECG auxiliary information (related to one or more ECGs) from the third network node in a second message via a network interface (e.g., Open Fronthaul). Optionally, the second network node must request the ECG auxiliary information from the third network node in a first message before receiving it. This is in... Figure 18As shown in the figure, Figure 18 This illustrates an example of how ECG auxiliary information and ECG information are exchanged via a network interface. In some examples, Figure 18 It can be Figure 12 An extension of some examples, in which the second network node obtains ECG auxiliary information from the third network node before creating the ECG information.

[0118] In some examples, ECG ancillary information may include one or more of the following:

[0119] Auxiliary information represents a unique identifier for a hardware component or group of hardware components. This identifier can uniquely identify a hardware component, either alone or in combination with a hardware unit identifier, which may already be known to a second network node and therefore may not need to be transmitted. Additionally, it includes:

[0120] One or more cell or carrier identifiers that are at least locally unique are known between the second network node and the third network node (and therefore unknown to the first network node), and the second network node has a mapping to global cell or carrier identifiers for the one or more cell or carrier identifiers that are at least locally unique.

[0121] For example, eAxC_ID, [tr]x-array-carrier identifier, or low-level-[tr]x-endpoint identifier in the O-RAN M plane.

[0122] In some examples, embodiments of this disclosure can be implemented by enhancing existing inter-node procedures and signaling messages defined in the 3GPP and O-RAN specifications, for example, for the Xn, X2, F1, E2, and O1 interfaces shown below. For example, embodiments can be implemented by enhancing the Xn setup and / or NG-RAN node configuration update procedures and corresponding signaling messages as defined in the XnAP specification (3GPP TS 38.423).

[0123] In one embodiment, ECG information (i.e., the content of the fourth message) can be included in the XN SETUP REQUEST and / or NG-RAN NODE CONFIGURATIONUPDATE messages via the Xn interface without prior request.

[0124] In another embodiment, the ECG information request (i.e., the content of the third message) may be included in the XN SETUP REQUEST and / or NG-RAN NODECONFIGURATION UPDATE message via the Xn interface, and in response to this, the ECG information (i.e., the content of the fourth message) may be included in the corresponding XN SETUP RESPONSE and / or NG-RAN NODE CONFIGURATION UPDATE ACKNOWLEDGE message via the Xn interface (e.g., as requested).

[0125] This can be achieved, for example, by enhancing the Served Cell Information NR IE and the Served Cell Information E-UTRA IE so that they additionally include ECG information, as illustrated herein.

[0126] In examples with a decoupled architecture (decomposed gNB), enhancements can be implemented to the gNB-DU configuration update and gNB-CU configuration update procedures and corresponding signaling messages as defined in the F1AP specification (3GPP TS 38.473).

[0127] In one embodiment, the ECG information (i.e., the content of the fourth message) can be included in the F1 SETUP REQUEST and / or GNB-DU CONFIGURATION UPDATE messages via the F1 interface. With this enhancement, the ECG information created at the gNB-DU can be signaled to the gNB-CU, for example, to be used at the gNB-CU and / or further distributed to other NG-RAN nodes or other network nodes or entities.

[0128] In another embodiment, the ECG information (i.e., the content of the fourth message) can be included in the GNB-DU configuration update acknowledgment and / or GNB-CU configuration update message via the F1 interface. With this enhancement, ECG information created at another gNB-DU (i.e., originating from another gNB-DU) can be signaled to the gNB-DU (shared with the gNB-DU) for use at the gNB-DU, for example, for DU local power saving optimization. This can be achieved, for example, by enhancing the included cell list IE for SON or the neighbor NR cell list IE for SON to additionally include the ECG information. Note that in this scenario, the gNB-DU that creates the ECG information and the gNB-DU that receives the ECG information can be connected to the same or different gNB-CUs (i.e., associated with the same or different gNB-CUs).

[0129] In the case of O-RAN architecture, this invention can be implemented by enhancing the E2 establishment and / or E2 node configuration update process and the corresponding signaling messages as defined in the E2AP specification (O-RAN.WG3.E2AP).

[0130] In one embodiment, ECG information (i.e., the content of the fourth message) may be included in an E2 SETUP REQUEST message and / or an E2 NODE CONFIGURATION UPDATE message via the E2 interface.

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

[0132] Figure 19-21 The following are some examples of how ECG information can be signaled between different network nodes using NG-RAN and / or O-RAN interfaces, and how ECG information can be used to optimize energy-saving functions at different levels, as illustrated in this disclosure. Figure 19 An example is shown where a non-real-time RIC obtains ECG information from an O-DU for network-level power saving feature optimization. Figure 20 An example is shown where gNB-CU-CP (#1) obtains ECG information from gNB-DU, eNB and another gNB-CU-CP (#2) and uses it for node-level energy-saving feature optimization. Figure 21An example overview of a power-saving function is shown, which receives input data including ECG (from the left) and provides thresholds for different RAN EP characteristics as output (to the right) based on operator intent such as user experience (from the top).

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

[0134] For example, network node 1 knows ECG 1, which includes cell 1 and cell 2 (controlled by network node 1), and receives ECG information for ECG 1 from network node 2, which includes cell 3 and cell 4 (controlled by network node 2). Based on the unique identifier of the ECG, node 1 can update the ECG information for ECG 1 to include cell 1, cell 2, cell 3, and cell 4.

[0135] In one embodiment, the first network node uses ECG-related information to coordinate power-saving functions, which can be implemented in combination with one or more of the following as, for example, but not limited to, rule-based algorithms or AI / ML models:

[0136] Service load forecasting for each cell within the ECG.

[0137] One or more performance measurements used to calculate key performance indicators.

[0138] Information related to cell and carrier configuration, including cell relationships and network topology information, such as capacity or coverage cells.

[0139] The operator's intent could be the desired user experience, for example,

[0140] For mobile broadband services, the X percentile of UE sessions with at least Y Mbps DL throughput.

[0141] Maximum latency for time-critical services.

[0142] New features in the XnAP specification (3GPP TS 38.423)

[0143] In some examples, ECG information (e.g., the mapping between cell (or carrier) and ECG) can be transmitted between NG-RAN nodes via the Xn interface, as disclosed in the following specific example implementations in the XnAP specification. Changes and additions are underlined. In some examples, rows in the table that have not changed may be omitted, as indicated by ellipses (...).

[0144] Depending on whether the cell is served by the NG-RAN node (whether requested or not), for all cells or for individual cells, the Served Cell Information (NR IE) and Served Cell Information (E-UTRA IE) are exchanged between NG-RAN nodes during the Xn setup process and the NG-RAN node configuration update process.

[0145] Therefore, these two IEs can be enhanced to additionally include a list of ECG identifiers, with one identifier for each ECG associated with the corresponding cell identified by NR-PCI (or E-UTRAPCI) and / or NR CGI (or ECGI).

[0146] 9.2.2.11 Served Cell Information (NR)

[0147] This IE contains cell configuration information that adjacent NG-RAN nodes may need for NR cells used in the Xn AP interface.

[0148] 9.2.2.12 Served Cell Information E-UTRA

[0149] This IE contains cell configuration information that neighboring NG-RAN nodes may need for E-UTRA cells used for the Xn AP interface.

[0150] New features in the F1AP specification (3GPP TS 38.473)

[0151] In some examples, ECG information (e.g., a mapping between cell (or carrier) and ECG) can be transmitted between logical nodes in a split architecture via the F1 interface, as disclosed in the following specific example implementation in the F1AP specification. Changes and additions are underlined.

[0152] According to the cell configured in gNB-DU, the Served Cell Information (IE) is exchanged between gNB-DU and gNB-CU during the gNB-DU configuration update process and the gNB-CU configuration update process.

[0153] Therefore, the IE can be enhanced to additionally include a list of ECG identifiers, with one identifier for each ECG associated with the corresponding cell identified by NR PCI and / or NR CGI.

[0154] 9.3.1.10 Information on Served Communities

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

[0156] Figure 22 An example of a communication system QQ100 according to some embodiments is shown.

[0157] In this example, the communication system QQ100 includes a telecommunications network QQ102, which includes an access network QQ104 (e.g., 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 generally be referred to as network node QQ110), or any other similar 3GPP access node or non-3GPP access point. Furthermore, as those skilled in the art will understand, network nodes are not necessarily limited to implementations in which the radio and baseband portions are provided and integrated by a single vendor. Therefore, it will be understood that network nodes include decomposed implementations or portions thereof. For example, in some embodiments, the telecommunications network QQ102 includes one or more Open RAN (ORAN) network nodes. An ORAN network node is a node in the QQ102 telecommunications network that supports ORAN specifications (such as those published by the O-RAN Alliance or any similar organization) and can operate alone or together with other nodes to perform one or more functions of any node in the QQ102 telecommunications network (including one or more network nodes QQ110 and / or core network node QQ108).

[0158] Examples of ORAN network nodes include Open Radio Units (O-RUs), Open Distributed Units (O-DUs), Open Central Units (O-CUs) (including O-CU control planes (O-CU-CPs) or O-CU user planes (O-CU-UPs)), RAN Intelligent Controllers (near real-time or non-real-time) managed software or software plugins (e.g., near real-time control applications (e.g., xApps) or non-real-time control applications (e.g., rApps)), or any combination thereof (the adjective "open" specifies support for the ORAN specification). Network nodes can support the specification by, for example, supporting interfaces defined by the ORAN specification, such as A1, F1, W1, E1, E2, X2, Xn interfaces, Open Fronthaul User Plane interfaces, or Open Fronthaul Management Plane interfaces. Furthermore, ORAN access nodes can be logical nodes within physical nodes. Additionally, ORAN network nodes can be implemented in a virtualized environment (described further below) where one or more network functions are virtualized. For example, the virtualized environment can include an O-Cloud computing platform orchestrated by a service management and orchestration framework via the O-2 interface or similar technologies defined by the O-RAN Consortium. Network node QQ110 facilitates direct or indirect connections of user equipment (UE), such as connecting UE QQ112a, QQ112b, QQ112c and QQ112d (one or more of which may generally be referred to as UE QQ112) to core network QQ106 via one or more wireless connections.

[0159] Examples of wireless communication via wireless connection include sending and / or receiving wireless signals using electromagnetic waves, radio waves, infrared waves, and / or other types of signals suitable for transmitting information without the use of wires, cables, or other conductors. Furthermore, in various 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 can facilitate or participate in the communication of data and / or signals (whether via wired or wireless connections). The communication system QQ100 may include and interface with any type of communication, telecommunications, data, cellular, radio network, and / or other similar type of system.

[0160] UE QQ112 can be any of a variety of communication devices, including wireless devices that are deployed, configured, and / or operable to communicate wirelessly with network node QQ110 and other communication devices. Similarly, network node QQ110 is deployed, capable of, configured, and / or operable to communicate directly or indirectly with UE QQ112 and / or other network nodes or devices in telecommunication network QQ102 to enable and / or provide network access (e.g., wireless network access) and / or perform other functions (e.g., management) in telecommunication network QQ102.

[0161] In the depicted example, core network QQ106 connects network node QQ110 to one or more hosts, such as host QQ116. These connections can be direct or indirect, via one or more intermediate networks or devices. In other examples, network nodes can be directly coupled to hosts. Core network QQ106 includes one or more core network nodes (e.g., core network node QQ108) composed of hardware and software components. The characteristics of these components can be substantially similar to those described for UEs, network nodes, and / or hosts, such that the description generally applies to the corresponding components of core network node QQ108. Example core network nodes include one or more of the following functions: 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 Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), Policy Control Function (PCF), and / or User Plane Function (UPF).

[0162] The host QQ116 may be owned or controlled by a service provider other than the operator or provider of the access network QQ104 and / or the telecommunications network QQ102, and may be operated by or on behalf of the service provider. The host QQ116 may host various applications to provide one or more services. Examples of such applications include providing real-time and / or pre-recorded audio / video content, data collection services (e.g., acquiring and editing data on various environmental conditions detected by multiple UEs), analytics functions, social media, functions for controlling or otherwise interacting with remote devices, functions for alarm and monitoring centers, or any other such functions performed by the server.

[0163] Overall, Figure 22The QQ100 communication system enables connections between the UE, network nodes, and the host. In this sense, the communication system can be configured to operate according to predefined rules or procedures, such as specific standards, including but 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 standard (WiFi); and / or any other suitable wireless communication standards, such as Global Microwave Access Interoperability (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.

[0164] In some examples, the QQ102 telecommunications network is a cellular network implementing 3GPP standardized features. Therefore, the QQ102 network can support network slicing to provide different logical networks to different devices connected to it. For example, the QQ102 network can provide Ultra Reliable Low Latency Communication (URLLC) services to some UEs while providing enhanced mobile broadband (eMBB) services to other UEs, and / or massive machine-type communication (mMTC) / massive IoT services to yet another set of UEs.

[0165] In some examples, UE QQ112 is configured to send and / or receive information without direct human interaction. For example, the UE may be designed to send information to access network QQ104 according to a predetermined schedule when triggered by an internal or external event or in response to a request from access network QQ104. Additionally, the UE may be configured to operate in single RAT, multi-RAT, or multi-standard modes. For example, the UE may operate using any one or a combination of Wi-Fi, New Radio (NR), and LTE, i.e., configured for Multi-Radio Dual Connectivity (MR-DC), such as Evolved UMTS Terrestrial Radio Access Network (E-UTRAN) New Radio-Dual Connectivity (EN-DC).

[0166] exist Figure 22In the example shown, hub QQ114 communicates with 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, hub QQ114 may be a controller, router, content source and analysis node, or any other communication device described herein relating to the UE. For example, hub QQ114 may be a broadband router that enables the UE to access core network QQ106. As another example, hub QQ114 may be a controller that sends commands or instructions to one or more actuators in the UE. Commands or instructions may be received from the UE, network node QQ110, or via executable code, scripts, procedures, or other instructions in hub QQ114. As another example, hub QQ114 may be a data collector that acts as a temporary storage device for UE data, and in some embodiments, may perform data analysis or other processing. As another example, hub QQ114 may be a content source. For example, for a UE acting as a VR headset, display, speaker, or other media delivery device, the hub QQ114 can acquire VR assets, video, audio, or other media or data related to sensing information via a network node, and then provide them to the UE directly, after performing local processing, and / or after adding additional local content. In yet another example, the hub QQ114 acts as a proxy server or orchestrator for the UE, particularly when one or more UEs are low-power IoT devices.

[0167] Hub QQ114 may have a constant / persistent or intermittent connection to network node QQ110b. Hub QQ114 may also allow different communication schemes and / or scheduling between hub QQ114 and UEs (e.g., UEs QQ112c and / or QQ112d) and between hub QQ114 and core network QQ106. In other examples, hub QQ114 is connected to core network QQ106 and / or one or more UEs via a wired connection. Furthermore, hub QQ114 may be configured to connect to an M2M service provider via access network QQ104 and / or to another UE via a direct connection. In some scenarios, a UE may establish a wireless connection with network node QQ110 while still being connected via hub QQ114 via a wired or wireless connection. In some embodiments, hub QQ114 may be a dedicated hub, that is, a hub whose primary function is to route communication from network node QQ110b to UE / from UE to network node QQ110b. In other embodiments, hub QQ114 may be a non-dedicated hub, that is, a device capable of operating to route communication between the UE and network node QQ110b, but also capable of operating as a communication start and / or end point for a specific data channel.

[0168] Figure 23 A UE QQ200 according to some embodiments is illustrated. As used herein, UE refers to a device capable of, configured, positioned, and / or operable to wirelessly communicate with network nodes and / or other UEs. Examples of UEs include, but are not limited to, smartphones, mobile phones, cellular phones, Voice over IP (VoIP) phones, wireless local loop phones, desktop computers, personal digital assistants (PDAs), wireless cameras, game consoles or devices, music storage devices, playback devices, wearable terminal devices, wireless endpoints, mobile stations, tablet computers, laptops, devices with built-in laptops (LEEs), devices with laptops installed (LMEs), smart devices, wireless client devices (CPEs), vehicles, in-vehicle or in-vehicle embedded / integrated wireless devices, etc. Other examples include any UE identified by the 3rd Generation Partnership Project (3GPP), including Narrowband Internet of Things (NB-IoT) UEs, Machine-Type Communication (MTC) UEs, and / or Enhanced MTC (eMTC) UEs.

[0169] The UE may support device-to-device (D2D) communication, for example, by implementing 3GPP standards for secondary link communication, dedicated short-range communication (DSRC), vehicle-to-vehicle (V2V), vehicle-to-infrastructure (V2I), or vehicle-to-everything (V2X). In other examples, the UE may not necessarily have a user in the sense of a human user who owns and / or operates the associated equipment. Instead, the UE may represent a device intended for sale to or operated by a human user but which may not, or initially may not, be associated with a particular human user (e.g., a smart sprinkler controller). Alternatively, the UE may represent a device not intended for sale to or operated by an end user but which may be associated with or operated for the benefit of a user (e.g., a smart power meter).

[0170] UE QQ200 includes processing circuitry QQ202, which is operatively coupled via bus QQ204 to input / output interface QQ206, power supply QQ208, memory QQ210, communication interface QQ212, and / or any other component or any combination thereof. A particular UE may utilize... Figure 23 All components or subsets of components are shown. The level of integration between components can vary from UE to UE. Furthermore, a particular UE may contain multiple instances of a component, such as multiple processors, memories, transceivers, transmitters, receivers, etc.

[0171] The processing circuit QQ202 is configured to process instructions and data and can be configured to implement any sequential state machine operable to execute instructions of a machine-readable computer program stored in memory QQ210. The processing circuit QQ202 can be implemented as one or more hardware-implemented state machines (e.g., using discrete logic, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), etc.); programmable logic and appropriate firmware; one or more stored computer programs, a general-purpose processor (e.g., a microprocessor or digital signal processor (DSP)) and appropriate software; or any combination thereof. For example, the processing circuit QQ202 may include multiple central processing units (CPUs). The processing circuit QQ202 is operable to provide UE QQ200 functionality, either alone or in combination with other UE QQ200 components (e.g., memory QQ210).

[0172] In this example, the input / output interface QQ206 can be configured to provide one or more interfaces to input devices, output devices, or one or more input and / or output devices. Examples of output devices include speakers, sound cards, video cards, displays, monitors, printers, actuators, transmitters, smart cards, another output device, or any combination thereof. Input devices can allow users to capture information into the UE QQ200. Examples of input devices include touch-sensitive or presence-sensitive displays, cameras (e.g., digital cameras, digital camcorders, webcams, etc.), microphones, sensors, mice, trackballs, steering wheels, scroll wheels, smart cards, etc. Presence-sensitive displays may include capacitive or resistive touch sensors to sense input from the user. Sensors may be, for example, accelerometers, gyroscopes, tilt sensors, force sensors, magnetometers, optical sensors, proximity sensors, biometric sensors, etc., or any combination thereof. Output devices can use the same type of interface port as input devices. For example, a Universal Serial Bus (USB) port can be used to provide both input and output devices.

[0173] In some embodiments, the power supply QQ208 is configured as a battery or battery pack. Other types of power sources can be used, such as an external power source (e.g., a power outlet), a photovoltaic device, or a battery. The power supply QQ208 may also include power circuitry for delivering power from the power supply QQ208 itself and / or an external power source to various parts of the UE QQ200 via input circuitry or an interface (e.g., a power cord). The power delivery may be used, for example, to charge the power supply QQ208. The power circuitry may perform any formatting, conversion, or other modifications to the power from the power supply QQ208 to suit the appropriate components of the UE QQ200 to which power is supplied.

[0174] The memory QQ210 can be, or can 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), disk, optical disk, hard disk, removable cassette tape, flash drive, etc. In one example, the memory QQ210 includes one or more application programs QQ214 (such as an operating system, web browser application, widget, utility engine, or other application) and corresponding data QQ216. The memory QQ210 can store any one or a combination of various operating systems for use by the UE QQ200.

[0175] The QQ210 memory can be configured to include multiple physical drive units, such as a Redundant Array of Independent Disks (RAID), flash memory, a USB flash drive, an external hard drive, a thumb drive, a pen drive, a key drive, a high-density digital versatile optical disc (HD-DVD) drive, an internal hard drive, a Blu-ray disc drive, a holographic digital data storage (HDDS) disc drive, an external mini dual in-line memory module (DIMM), synchronous dynamic random access memory (SDRAM), external micro DIMM SDRAM, smart card memory (e.g., a tamper-proof module in the form of a universal integrated circuit card (UICC), including one or more subscriber identification modules (SIMs), such as USIM and / or ISIM), other memory, or any combination thereof. The UICC can be, for example, an embedded UICC (eUICC), an integrated UICC (iUICC), or a removable UICC, often referred to as a "SIM card." The QQ210 memory allows the UE QQ200 to access instructions, applications, etc., stored on transient or non-transient storage media to offload or upload data. Articles manufactured using communication systems may be tangibly embodied in or contained in memory QQ210, which may be or include a device-readable storage medium.

[0176] The processing circuitry QQ202 can be configured to communicate with an access network or other network using a communication interface QQ212. The communication interface QQ212 may include 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 for communication (e.g., via one or more remote transceivers capable of wireless communication with another device (e.g., another UE or a network node in the access network). Each transceiver may include a transmitter QQ218 and / or a receiver QQ220 adapted to provide network communication (e.g., optical, electrical, frequency allocation, etc.). Furthermore, 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.

[0177] In some embodiments, the communication functions of the communication interface QQ212 may include cellular communication, Wi-Fi communication, LPWAN communication, data communication, voice communication, multimedia communication, short-range communication such as Bluetooth, near-field communication, location-based communication such as using a Global Positioning System (GPS) to determine location, another similar communication function, or any combination thereof. Communication may be implemented according to one or more communication protocols and / or standards, such as IEEE 802.11, Code Division Multiple 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 Network (SONET), Asynchronous Transfer Mode (ATM), QUIC, Hypertext Transfer Protocol (HTTP), etc.

[0178] Regardless of the sensor type, the UE can provide the output of data captured by its sensors via its communication interface QQ212 through a wireless connection with a network node. Data captured by the UE's sensors can be transmitted via another UE through the same wireless connection. The output can be periodic (e.g., every 15 minutes if it reports the sensed temperature), random (e.g., to balance the reporting load from multiple sensors), responsive to a triggered event (e.g., sending an alarm when humidity is detected), responsive to a request (e.g., a user-initiated request), or a continuous stream (e.g., real-time video feed of a patient).

[0179] As another example, the UE includes an actuator, motor, or switch associated with a communication interface configured to receive wireless input from a network node via a wireless connection. The state of the actuator, motor, or switch can change in response to the received wireless input. For example, the UE may include a motor that adjusts the control surfaces or rotors of a flying drone based on the received input, or control a robotic arm performing a medical procedure based on the received input.

[0180] When taking the form of an Internet of Things (IoT) device, the UE can be a device for one or more application areas, including but not limited to urban wearable technology, extended industry applications, and healthcare. Non-limiting examples of such IoT devices include devices that are or are embedded in the following: connected refrigerators or freezers, televisions, connected lighting devices, electricity meters, robotic vacuum cleaners, voice-controlled smart speakers, home security cameras, motion detectors, thermostats, smoke detectors, door / window sensors, flood / humidity sensors, electric door locks, connected doorbells, air conditioning systems such as heat pumps, autonomous vehicles, surveillance systems, weather monitoring devices, vehicle parking monitoring devices, electric vehicle charging stations, smartwatches, fitness trackers, head-mounted displays for augmented reality (AR) or virtual reality (VR), wearable devices for haptic or sensory enhancement, sprinklers, animal or object tracking devices, sensors for monitoring plants or animals, industrial robots, unmanned aerial vehicles (UAVs), and any kind of medical device, such as heart rate monitors or remote-controlled surgical robots. The UE in the form of an IoT device includes the circuitry and / or software associated with the intended application of the IoT device and for... Figure 23 Other components described in the UE QQ200 shown.

[0181] As another specific example, in IoT scenarios, a UE can represent a machine or other device that performs monitoring and / or measurement and sends the results of such monitoring and / or measurement to another UE and / or network node. In this case, the UE can be an M2M device, which can be referred to as an MTC device in the 3GPP context. As a specific example, a UE can implement the 3GPP NB-IoT standard. In other scenarios, a UE can represent a vehicle (e.g., car, bus, truck), ship, aircraft, or other equipment capable of monitoring and / or reporting its operational status or other functions associated with its operation.

[0182] In practice, any number of UEs can be used together for a single use case. For example, the first UE may be or be integrated into the drone and provide the drone's speed information (obtained via a speed sensor) to a second UE, which acts as a remote controller for operating the drone. When the user makes changes from the remote controller, the first UE can adjust the throttle on the drone (e.g., by controlling the actuators) to increase or decrease the drone's speed. The first UE and / or the second UE may also include multiple functions described above. For example, the UE may include sensors and actuators and handle data communication between both the speed sensor and the actuators.

[0183] Figure 24A network node QQ300 according to some embodiments is illustrated. As used herein, a network node refers to a device that is capable of, configured, arranged, and / or operable to communicate directly or indirectly with a UE and / or other network nodes or devices in a telecommunications 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), NR Node Bs (gNBs)), O-RAN nodes, or components of O-RAN nodes (e.g., O-RUs, O-DUs, O-CUs).

[0184] Base stations can be classified based on the coverage they provide (or in other words, their transmit power level), and therefore, depending on the coverage provided, they can be called femtocells, picocells, microcells, or macrocells. A base station can be a relay node or a relay donor node controlling a relay. A network node can also include one or more (or all) portions of a distributed radio base station (e.g., centralized digital units, distributed units (e.g., in O-RAN access nodes), and / or remote radio units (RRUs) (sometimes referred to as remote radio heads (RRHs)). Such RRUs may or may not be integrated with an antenna as antenna-integrated radios. A portion of a distributed radio base station can also be referred to as a node in a distributed antenna system (DAS).

[0185] Other examples of network nodes include multi-transmission point (multi-TRP) 5G access nodes, multi-standard radio (MSR) equipment (such as MSR BS), network controllers such as radio network controllers (RNC) or base station controllers (BSC), base transceiver stations (BTS), transmission points, transmission nodes, multi-cell / multicast coordination entities (MCE), operations and maintenance (O&M) nodes, operations support system (OSS) nodes, self-organizing network (SON) nodes, location nodes (e.g., evolved serving mobile location center (E-SMLC)), and / or minimized drive test (MDT).

[0186] Network node QQ300 includes processing circuitry QQ302, memory QQ304, communication interface QQ306, and power supply QQ308 and / or any other components or any combination thereof. Network node QQ300 may include multiple physically separate components (e.g., node B components and RNC components, or BTS components and BSC components, etc.), each component may have its own corresponding components. In a specific scenario where network node QQ300 includes multiple separate components (e.g., BTS and BSC components), one or more separate components may be shared among multiple network nodes. For example, a single RNC can control multiple node Bs. In such scenarios, under certain circumstances, each unique node B and RNC pair may be considered a single, separate network node. In some embodiments, 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), while some components may be reused (e.g., the same antenna QQ310 may be shared by different RATs). The network node QQ300 may also include a variety of example components for integrating different wireless technologies (such as GSM, WCDMA, LTE, NR, Wi-Fi, Zigbee, Z-wave, LoRaWAN, RFID, or Bluetooth wireless technologies) into the network node QQ300. These wireless technologies may be integrated into the same or different chipsets and other components within the network node QQ300.

[0187] The processing circuitry QQ302 may include one or more of the following, operable to provide network node QQ300 functionality, either alone or in combination with other network node QQ300 components (e.g., memory QQ304): 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 coding logic. For example, the processing circuitry QQ302 may be configured to cause the network node to perform actions as described in the reference. Figures 13 to 16 Any of the methods described.

[0188] In some embodiments, the processing circuit QQ302 includes a system-on-a-chip (SOC). In some embodiments, the processing circuit QQ302 includes one or more of a radio frequency (RF) transceiver circuit QQ312 and a baseband processing circuit QQ314. In some embodiments, the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on separate chips (or chipsets), boards, or units (e.g., radio units and digital units). In alternative embodiments, some or all of the RF transceiver circuit QQ312 and the baseband processing circuit QQ314 may be on the same chip or chipset, board, or unit.

[0189] The memory QQ304 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, optical disc (CD), or digital video disk (DVD)) and / or any other volatile or non-volatile, non-transitory device-readable and / or computer-executable storage device that stores information, data, and / or instructions that can be used by the processing circuitry QQ302. The memory QQ304 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions that can be executed by the processing circuitry QQ302 and utilized by the network node QQ300. The memory QQ304 may be used to store any calculations performed by the processing circuitry QQ302 and / or any data received via the communication interface QQ306. In some embodiments, the processing circuitry QQ302 and the memory QQ304 are integrated.

[0190] Communication interface QQ306 is used in wired or wireless communication of signaling and / or data between network nodes, access networks, and / or UEs. As shown, communication interface QQ306 includes a port / terminal QQ316 for sending and receiving data to and from the network, for example, via a wired connection. Communication interface QQ306 also includes radio front-end circuitry QQ318, which may be coupled to antenna QQ310 or, in a particular embodiment, is part of antenna QQ310. Radio front-end circuitry QQ318 includes a filter QQ320 and an amplifier QQ322. Radio front-end circuitry QQ318 may be connected to antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 may be configured to modulate the signal transmitted between antenna QQ310 and processing circuitry QQ302. Radio front-end circuitry QQ318 may receive digital data that will be transmitted to other network nodes or UEs via a wireless connection. Radio front-end circuitry QQ318 may use a combination of filter QQ320 and / or amplifier QQ322 to convert the digital data into radio signals with appropriate channel and bandwidth parameters. The radio signals may then be transmitted via antenna QQ310. Similarly, when receiving data, the antenna QQ310 can collect radio signals, which are then converted into digital data by the radio front-end circuit QQ318. The digital data can then be passed to the processing circuit QQ302. In other embodiments, the communication interface may include different components and / or different combinations of components.

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

[0192] Antenna QQ310 may include one or more antennas or antenna arrays configured to transmit and / or receive wireless signals. Antenna QQ310 may be coupled to radio front-end circuitry QQ318 and may be any type of antenna capable of wirelessly transmitting and receiving data and / or signals. In a particular embodiment, antenna QQ310 is decoupled from network node QQ300 and may be connected to network node QQ300 via an interface or port.

[0193] Antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any receive operation and / or specific acquisition operation described herein as being performed by a network node. Any information, data, and / or signals can be received from the UE, another network node, and / or any other network device. Similarly, antenna QQ310, communication interface QQ306, and / or processing circuitry QQ302 can be configured to perform any transmit operation described herein as being performed by a network node. Any information, data, and / or signals can be transmitted to the UE, another network node, and / or any other network device.

[0194] The power supply QQ308 provides power to the various components of the network node QQ300 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply QQ308 may also include or be coupled to power management circuitry to provide power to the components of the network node QQ300 for performing the functions described herein. For example, the network node QQ300 may be connected to an external power source (e.g., the mains or a power outlet) via input circuitry or an interface (e.g., a cable), whereby the external power source provides power to the power circuitry of the power supply QQ308. As yet another example, the power supply QQ308 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0195] Implementation examples of network node QQ300 may include Figure 24 Additional components beyond those shown may be used to provide specific aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, the network node QQ300 may include a user interface device to allow information to be input into and output from the network node QQ300. This allows users to perform diagnostic, maintenance, repair, and other management functions on the network node QQ300.

[0196] Figure 25 This is a block diagram of the QQ400 host based on the various aspects described in this article. The QQ400 host can be... Figure 12 The embodiment of host QQ116. As used herein, host QQ400 can be or include various combinations of hardware and / or software, including standalone servers, blade servers, cloud-implemented servers, distributed servers, virtual machines, containers, or processing resources in a server farm. Host QQ400 can provide one or more services to one or more UEs.

[0197] The host QQ400 includes processing circuitry QQ402, which is operatively coupled via bus QQ404 to input / output interface QQ406, network interface QQ408, power supply QQ410, and memory QQ412. Other components may be included in other embodiments. These components may be characterized substantially similarly to those shown in the previous figures (e.g., Figure 23 and 24 The device description features are designed to be applicable to the corresponding components of the host QQ400.

[0198] The memory QQ412 may include one or more computer programs, including one or more host applications QQ414 and data QQ416. Data QQ416 may include user data, such as data generated by the UE for the host QQ400 or data generated by the host QQ400 for the UE. Embodiments of the host QQ400 may utilize some or all of the illustrated components. The host application QQ414 may be implemented in a container-based architecture and may provide support for video codecs (e.g., Multifunction Video Coding (VVC), High Efficiency Video Coding (HEVC), Advanced Video Coding (AVC), MPEG, VP9) and audio codecs (e.g., FLAC, Advanced Audio Coding (AAC), MPEG, G.711), including transcoding for multiple different classes, types, or implementations of the UE (e.g., mobile phone, desktop computer, wearable display system, head-up display system). The host application QQ414 may also provide user authentication and authorization checks and may periodically report health status, routing, and content availability to a central node (e.g., a device in the core network or at the edge). Therefore, the host QQ400 may select and / or instruct different hosts for over-the-top services for the UE. The host application QQ414 supports various protocols, such as HTTP Real-Time Streaming (HLS), Real-Time Messaging Protocol (RTMP), Real-Time Streaming Protocol (RTSP), and HTTP Dynamic Adaptation Streaming (MPEG-DASH).

[0199] Figure 26This is a block diagram illustrating a virtualization environment QQ500 in which functionality implemented by some embodiments can be virtualized. In the current context, virtualization means creating a virtual version of a device or equipment, which may include a virtualized hardware platform, storage devices, and networking resources. As used herein, virtualization can be applied to any device or component thereof described herein 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 functionality described herein can be implemented as virtual components executed by one or more virtual machines (VMs) in one or more virtual environments QQ500 hosted by one or more hardware nodes, such as hardware computing devices operating as network nodes, UEs, core network nodes, or hosts. Furthermore, in embodiments in which virtual nodes do not require radio connectivity (e.g., core network nodes or hosts), the nodes can be fully 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 O-2 interface.

[0200] The application QQ502 (which may also be referred to as a software instance, virtual device, network function, virtual node, virtual network function, etc.) runs in the virtualization environment QQ500 to implement certain features, functions and / or benefits of some embodiments disclosed herein.

[0201] Hardware QQ504 includes processing circuitry, memory storing software and / or instructions executable by the hardware processing circuitry, and / or other hardware devices as described herein, such as network interfaces, input / output interfaces, etc. Software can be executed by the processing circuitry to instantiate one or more virtualization layers QQ506 (also referred to as a hypervisor or virtual machine monitor (VMM)), provide virtual machines QQ508a and QQ508b (one or more of which may generally be referred to as virtual machine QQ508), and / or perform any functionality, features, and / or benefits described for some embodiments described herein. Virtualization layer QQ506 can present a virtual operating platform to virtual machine QQ508 that appears to be networked hardware.

[0202] Virtual machine QQ508 includes virtual processing, virtual memory, virtual networks or interfaces, and virtual storage devices, and can be run by the corresponding virtualization layer QQ506. Different embodiments of virtual device QQ502 instances can be implemented on one or more virtual machines QQ508, and can be implemented in different ways. In some contexts, hardware virtualization is referred to as Network Functions Virtualization (NFV). NFV can be used to consolidate many types of network devices onto industry-standard, high-capacity server hardware, physical switches, and physical storage devices that can reside in data centers and client devices.

[0203] In the context of NFV, a virtual machine QQ508 can be a software implementation of a physical machine, which runs programs as if they were running on a physical, non-virtualized machine. Each virtual machine QQ508, along with the portion of the hardware QQ504 that executes that virtual machine (hardware dedicated to that virtual machine and / or hardware shared by that virtual machine with other virtual machines), forms a separate virtual network unit. Still within the NFV context, the virtual network function is responsible for handling specific network functions running on one or more virtual machines QQ508 running on top of the hardware QQ504, and corresponds to the application QQ502.

[0204] The hardware QQ504 can be implemented in a standalone network node with general or specific components. Some functions of the hardware QQ504 can be implemented via virtualization. Alternatively, the hardware QQ504 can be part of a larger hardware cluster (e.g., in a data center or CPE), where many hardware nodes work together and are managed via management and orchestration QQ510, which, among other things, oversees the lifecycle management of application QQ502. In some embodiments, the hardware QQ504 is coupled to one or more radio units, each including one or more transmitters and one or more receivers that can be coupled to one or more antennas. The radio units can communicate directly with other hardware nodes via one or more suitable network interfaces and can be used in combination with virtual components to provide a radio-capable virtual node, such as a radio access node or base station. In some embodiments, a control system QQ512 can be used to provide signaling, which can alternatively be used for communication between the hardware node and the radio unit.

[0205] Figure 27 A communication diagram is shown illustrating communication between host QQ602 and UE QQ606 via a partial wireless connection through network node QQ604, according to some embodiments. Reference will now be made to... Figure 27 To describe the UE discussed in the preceding paragraphs according to various embodiments (e.g. Figure 22 UE QQ112a and / or Figure 23 UE QQ200), network nodes (e.g. Figure 22 Network node QQ110a and / or Figure 24 Network node QQ300) and host (e.g. Figure 22 The host QQ116 and / or Figure 25 Example implementation of QQ400 (host).

[0206] Similar to host QQ400, embodiments of host QQ602 include hardware such as a communication interface, processing circuitry, and memory. Host QQ602 also includes software stored in or accessible by host QQ602 and executable by the processing circuitry. The software includes a host application operable to provide services to remote users, such as UE QQ606 connected via an over-the-top (OTT) connection QQ650 extending between UE QQ606 and host QQ602. When providing services to remote users, the host application can provide user data transmitted using the OTT connection QQ650.

[0207] Network node QQ604 includes hardware that enables it to communicate with host QQ602 and UE QQ606. Connection to QQ604 can be direct or via a core network (such as...). Figure 22 The core network (QQ106) and / or one or more other intermediate networks, such as one or more public, private, or hosted networks. For example, an intermediate network could be a backbone network or the Internet.

[0208] UE QQ606 includes hardware and software, the software being stored in or accessible by UE QQ606 and executable by the UE's processing circuitry. This software includes client applications, such as web browsers or carrier-specific "applications," operable to provide services to human or non-human users via UE QQ606 with the support of host QQ602. In host QQ602, the executing host application can communicate with the executing client application via OTT connection QQ650, which terminates between UE QQ606 and host QQ602. When providing services to a user, the UE's client application can receive request data from the host application of the host and provide user data in response to that request data. OTT connection QQ650 can transmit both request data and user data. The UE's client application can interact with the user to generate the user data it provides to the host application via OTT connection QQ650.

[0209] The OTT connection QQ650 can be extended via connection QQ660 between host QQ602 and network node QQ604, and via wireless connection QQ670 between network node QQ604 and UE QQ606, to provide connectivity between host QQ602 and UE QQ606. Connection QQ660 and wireless connection QQ670, which can provide OTT connection QQ650, have been abstractly drawn to illustrate communication between host QQ602 and UE QQ606 via network node QQ604, without explicitly referencing any intermediate devices or the precise routing of messages via these devices.

[0210] As an example of sending data via an OTT connection QQ650, in step QQ608, host QQ602 provides user data, which can be performed by executing a host application. In some embodiments, the user data is associated with a specific human user interacting with UE QQ606. In other embodiments, the user data is associated with UE QQ606, which shares data with host QQ602 without explicit human interaction. In step QQ610, host QQ602 initiates a transmission carrying user data toward UE QQ606. Host QQ602 may initiate the transmission in response to a request sent by UE QQ606. This request may be caused by human interaction with UE QQ606 or by the operation of a client application executed on UE QQ606. According to the teachings of the embodiments described throughout this disclosure, the transmission can be performed via network node QQ604. Therefore, in step QQ612, according to the teachings of the embodiments described throughout this disclosure, network node QQ604 sends the user data carried in the transmission initiated by host QQ602 to UE QQ606. In step QQ614, UE QQ606 receives user data carried in the transmission, which can be performed by a client application running on UE QQ606, which is associated with a host application running by host QQ602.

[0211] In some examples, UE QQ606 executes a client application that provides user data to host QQ602. User data can be provided in response to data received from host QQ602. Therefore, in step QQ616, UE QQ606 can provide user data, which can be done by executing the client application. When providing user data, the client application can further consider user input received from the user via the input / output interface of UE QQ606. Regardless of the specific manner in which user data is provided, UE QQ606 initiates a transmission of user data to host QQ602 via network node QQ604 in step QQ618. In step QQ620, in accordance with the teachings of the embodiments described throughout this disclosure, network node QQ604 receives user data from UE QQ606 and initiates a transmission of the received user data to host QQ602. In step QQ622, host QQ602 receives the user data carried in the transmission initiated by UE QQ606.

[0212] One or more of the various embodiments improve the performance of OTT services provided to UE QQ606 using OTT connection QQ650 (where wireless connection QQ670 forms the final segment). More precisely, the teachings of these embodiments enable improved sharing of hardware-related information, thereby providing benefits such as the possibility of improved energy-saving decisions in the network.

[0213] In the example scenario, host QQ602 can collect and analyze plant status information. As another example, host QQ602 can process audio and video data that may have been obtained from the UE for map creation. As another example, host QQ602 can collect and analyze real-time data to assist in controlling traffic congestion (e.g., controlling traffic lights). As another example, host QQ602 can store surveillance video uploaded by the UE. As another example, host QQ602 can store or control access to media content such as video, audio, VR, or AR, which host QQ602 can broadcast, multicast, or unicast to the UE. As other examples, host QQ602 can be used for energy pricing, remote control of non-time-critical power loads to balance generation demand, location services, presentation services (e.g., editing maps based on data collected from remote devices), or any other function that collects, acquires, stores, analyzes, and / or transmits data.

[0214] In some examples, a measurement process may be provided for the purpose of monitoring data rates, latency, and other factors improved thereon in one or more embodiments. Optional network functions may also be available for reconfiguring the OTT connection QQ650 between host QQ602 and UE QQ606 in response to changes in measurement results. The measurement process and / or network functions for reconfiguring the OTT connection may be implemented in the software and hardware of host QQ602 and / or UE QQ606. In some embodiments, sensors (not shown) may be deployed in or associated with other devices through which the OTT connection QQ650 passes; the sensors may participate in the measurement process by providing values ​​of the monitored quantities as exemplified above or by providing values ​​of other physical quantities from which the software can calculate or estimate the monitored quantities. Reconfiguration of the OTT connection QQ650 may include message formats, retransmission settings, preferred routing, etc.; reconfiguration does not require a direct change in the operation of network node QQ604. Such processes and functions may be known and practiced in the art. In certain embodiments, the measurement may involve proprietary UE signaling, which facilitates host QQ602's measurement of throughput, propagation time, latency, etc. Measurements can be made because the software causes messages to be sent using an OTT connection to QQ650 during its monitoring of propagation time, errors, etc., especially empty messages or "dummy" messages.

[0215] Figure 28A network node QQ700 according to some embodiments is illustrated. As used herein, a network node refers to a device capable of, configured, arranged, and / or operable to communicate directly or indirectly with the UE and / or other network nodes or devices in a telecommunications network. The network node QQ700 may operate as a core network node, a core network function, or more generally as a core network entity, as described above for... Figure 22 The core network node described is QQ108. In this context, examples of network nodes include core network entities such as one or more of the following: 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 Dehiding Function (SIDF), Unified Data Management (UDM), Security Edge Protection Agent (SEPP), Network Open Function (NEF), Policy Control Function (PCF), and / or User Plane Function (UPF).

[0216] Network node QQ700 includes processing circuitry QQ702, memory QQ704, communication interface QQ706, and power supply QQ708, and / or any other components or any combination thereof. Network node QQ700 may include multiple physically separate components, each of which may have its own corresponding components. In specific scenarios where network node QQ700 includes multiple separate components, one or more separate components may be shared among multiple network nodes.

[0217] The processing circuitry QQ702 may include one or more of the following, operable to provide network node QQ700 functionality individually or in combination with other network node QQ700 components (e.g., memory QQ704): 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 coding logic. For example, the processing circuitry QQ702 may be configured to cause the network node to perform actions as described in the reference. Figures 13 to 16 Any of the methods described.

[0218] The memory QQ704 may include any form of volatile or non-volatile computer-readable storage, including but not limited to permanent storage devices, solid-state storage, remotely mounted memory, magnetic media, optical media, random access memory (RAM), read-only memory (ROM), mass storage media (e.g., hard disk), removable storage media (e.g., flash drive, optical disc (CD), or digital video disc (DVD)) and / or any other volatile or non-volatile, non-transitory device that stores information, data, and / or instructions that can be used by the processing circuitry QQ702. The memory QQ704 may store any suitable instructions, data, or information, including computer programs, software, applications (including one or more of logic, rules, code, tables, etc.) and / or other instructions that can be executed by the processing circuitry QQ702 and utilized by the network node QQ700. The memory QQ704 may be used to store any calculations performed by the processing circuitry QQ702 and / or any data received via the communication interface QQ706. In some embodiments, the processing circuitry QQ702 and the memory QQ704 are integrated.

[0219] The QQ706 communication interface is used in wired or wireless communication of signaling and / or data between network nodes, access networks and / or UEs.

[0220] The power supply QQ708 provides power to the various components of the network node QQ700 in a form suitable for the respective components (e.g., at the voltage and current levels required by each respective component). The power supply QQ708 may also include or be coupled to power management circuitry to provide power to the components of the network node QQ700 for performing the functions described herein. For example, the network node QQ700 may be connected to an external power source (e.g., the mains or a power outlet) via input circuitry or an interface (e.g., a cable), whereby the external power source provides power to the power circuitry of the power supply QQ708. As yet another example, the power supply QQ708 may include a power source in the form of a battery or battery pack connected to or integrated into the power circuitry. The battery can provide backup power if the external power source fails.

[0221] Implementation examples of the network node QQ700 may include Figure 28 Additional components beyond those shown may be used to provide specific aspects of the functionality of the network node, including any functionality described herein and / or any functionality necessary to support the topics described herein. For example, the network node QQ700 may include a user interface device to allow information to be input into and output from the network node QQ700. This allows users to perform diagnostic, maintenance, repair, and other management functions on the network node QQ700.

[0222] This disclosure includes the embodiments listed below.

[0223] Group B Implementation Examples

[0224] 1. A method for receiving information, performed by a first network node, the method comprising:

[0225] Receive information from the second network node identifying the following: 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.

[0226] 2. The method according to Embodiment 1, wherein the information identifies one or more hardware resource groups, wherein each group contains one or more hardware resources among the hardware resources.

[0227] 3. The method according to embodiment 2, wherein each of the hardware resources may be included in one or more groups within the group.

[0228] 4. The method according to embodiment 2 or 3, wherein, for each cell or carrier, by identifying one or more groups of the groups used when the cell and / or carrier is operable, the information identifies one or more hardware resources used when each cell or carrier is operable.

[0229] 5. The method according to any one of embodiments 2 to 4, wherein the information identifies one or more groups in the group as being included in one or more other groups.

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

[0231] 7. The method according to Embodiment 6, wherein, for each of the cells and / or carriers, the information identifies one or more identifiers of one or more hardware resource groups used when the cell and / or carrier is operable.

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

[0233] 9. The method according to any one of embodiments 6 to 8, wherein:

[0234] The identifier for each group is unique within the network including the first network node and / or the second network node, or within a portion of the network; and / or

[0235] The identifier used for each group is globally unique.

[0236] 10. The method according to any one of embodiments 1 to 9, wherein the information identifies one or more hardware resources among the hardware resources as being used by a plurality of network nodes.

[0237] 11. The method according to any one of embodiments 1 to 10, comprising: receiving capability information from the second network node, the 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 operable.

[0238] 12. The method according to embodiment 11, wherein the capability information for the one or more hardware resources used when the cell and / or carrier is operational includes one or more of the following:

[0239] Multiple sleep and / or power modes supported by the one or more hardware resources;

[0240] The current sleep and / or power mode of the one or more hardware resources;

[0241] Multiple capability and / or capacity levels supported by the one or more hardware resources;

[0242] The current capabilities and / or capacity levels of the one or more hardware resources;

[0243] Whether the one or more hardware resources are able to provide an indication of energy consumption measurement.

[0244] 13. The method according to embodiment 12, wherein the capability information for the one or more hardware resources used when the cell and / or carrier is operational includes one or more of the following:

[0245] The power consumption of the one or more hardware resources in each of the sleep and / or power modes;

[0246] The power consumption of the one or more hardware resources in each of the capability and / or capacity levels;

[0247] Transition energy and / or transition time for the one or more hardware resources to transition between hibernation and / or power modes and / or between capacity and / or power levels.

[0248] 14. The method according to embodiment 13, wherein the power consumption includes absolute and / or relative power consumption.

[0249] 15. The method according to any one 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.

[0250] 16. The method according to embodiment 15, wherein determining the one or more energy-saving features in the network includes: determining to deactivate one or more cells or carriers and deactivating the one or more hardware resources used when the one or more cells or carriers are operational.

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

[0252] 18. The method according to any one of Embodiments 1 to 17, comprising: receiving from one or more other network nodes additional information identifying one or more other cells and / or carriers; and for each other cell or carrier, one or more other hardware resources used when the other cell and / or carrier is operable.

[0253] 19. The method according to any one of embodiments 1 to 18, wherein each of the one or more hardware resources in the hardware resources includes one or more of the following:

[0254] One or more hardware components;

[0255] One or more network nodes;

[0256] One or more network functions;

[0257] One or more antennas;

[0258] One or more antenna arrays;

[0259] One or more antenna segments;

[0260] One or more data processors;

[0261] One or more baseband processors;

[0262] One or more digital signal processors (DSPs);

[0263] One or more radio units;

[0264] One or more distributed units (DUs);

[0265] One or more central units (CUs);

[0266] One or more circuits;

[0267] One or more power amplifiers.

[0268] 20. The method according to any one of embodiments 1 to 19, wherein each of the first network node and / or the second network node comprises one or more of the following:

[0269] Base station;

[0270] eNodeB;

[0271] gNodeB;

[0272] O-DU;

[0273] O-CU;

[0274] O-CU-CP;

[0275] O-CU-UP;

[0276] O-eNB;

[0277] gNB-CU;

[0278] gNB-CU-CP;

[0279] gNB-DU;

[0280] Near RT RIC;

[0281] Non-RT RIC;

[0282] SMO node;

[0283] OAM node;

[0284] Core network nodes.

[0285] 21. The method according to any one of embodiments 1 to 20, wherein the one or more hardware resources used when the cell and / or carrier is operable include:

[0286] The one or more hardware resources used when the cell and / or carrier are available, enabled, active, provided, functional and / or usable;

[0287] The one or more hardware resources used to support, enable, activate, provide, maintain and / or sustain cells and / or carriers;

[0288] The one or more hardware resources used for transmitting and / or receiving signals associated with the cell and / or carrier; and / or

[0289] The one or more hardware resources used for sending and / or receiving user data.

[0290] 22. The method according to any one 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.

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

[0292] 24. A method for sending information, performed by a second network node, the method comprising:

[0293] Send information to the first network node identifying the following: 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.

[0294] 25. The method according to embodiment 24, comprising: determining the one or more hardware resources to be used when each cell and / or carrier is operational.

[0295] 26. The method according to embodiment 25, comprising: receiving hardware information identifying one or more hardware resources among the one or more hardware resources from one or more other network nodes, wherein determining the one or more hardware resources comprises: determining the one or more hardware resources based on the other information.

[0296] 27. The method according to embodiment 26, wherein the hardware information identifying the hardware resource is received from other network nodes that control and / or operate the hardware resource.

[0297] 28. The method according to embodiment 26 or 27, wherein the hardware information identifies one or more of the following:

[0298] The association between the one or more hardware resources and the one or more cells and / or carriers;

[0299] An indication of when the one or more hardware resources are used when one or more of the cells and / or carriers are operational.

[0300] 29. The method according to any one of embodiments 26 to 28, comprising: receiving capability information from the one or more other network nodes that identifies one or more capabilities of the one or more hardware resources.

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

[0302] 31. The method according to embodiment 30, wherein the cell / carrier information identifying the cell or carrier is received from other network nodes that control, operate, and / or serve the cell or carrier.

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

[0304] 33. The method according to embodiment 32, wherein each hardware resource in the hardware resources may be included in one or more groups in the group.

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

[0306] 35. The method according to any one of embodiments 32 to 34, wherein the information identifies one or more groups in the group as being included in one or more other groups.

[0307] 36. The method according to any one of embodiments 32 to 35, wherein the information identifier is used as an identifier for each of the one or more groups.

[0308] 37. The method according to embodiment 36, wherein, for each of the cells and / or carriers, the information identifies one or more identifiers of one or more hardware resource groups used when the cell and / or carrier is operable.

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

[0310] 39. The method according to any one of embodiments 36 to 38, wherein:

[0311] The identifier for each group is unique within the network including the first network node and / or the second network node, or within a portion of the network; and / or

[0312] The identifier used for each group is globally unique.

[0313] 40. The method according to any one of embodiments 24 to 39, wherein the information identifies one or more hardware resources among the hardware resources as being used by multiple network nodes.

[0314] 41. The method according to any one of embodiments 24 to 40, comprising: sending capability information to the first network node, the 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 operable.

[0315] 42. The method according to embodiment 28 or 41, wherein the capability information for the one or more hardware resources used when the cell and / or carrier is operational includes one or more of the following:

[0316] Multiple sleep and / or power modes supported by the one or more hardware resources;

[0317] The current sleep and / or power mode of the one or more hardware resources;

[0318] Multiple capability and / or capacity levels supported by the one or more hardware resources;

[0319] The current capabilities and / or capacity levels of the one or more hardware resources;

[0320] Whether the one or more hardware resources are able to provide an indication of energy consumption measurement.

[0321] 43. The method according to embodiment 42, wherein the capability information for the one or more hardware resources used when the cell and / or carrier is operational includes one or more of the following:

[0322] The power consumption of the one or more hardware resources in each of the sleep and / or power modes;

[0323] The power consumption of the one or more hardware resources in each of the capability and / or capacity levels;

[0324] Transition energy and / or transition time for the one or more hardware resources to transition between hibernation and / or power modes and / or between capacity and / or power levels.

[0325] 44. The method according to embodiment 43, wherein the power consumption includes absolute and / or relative power consumption.

[0326] 45. The method according to any one of embodiments 24 to 44, wherein each of the one or more hardware resources comprises one or more of the following:

[0327] One or more hardware components;

[0328] One or more network nodes;

[0329] One or more network functions;

[0330] One or more antennas;

[0331] One or more antenna arrays;

[0332] One or more antenna segments;

[0333] One or more data processors;

[0334] One or more baseband processors;

[0335] One or more digital signal processors (DSPs);

[0336] One or more radio units;

[0337] One or more distributed units (DUs);

[0338] One or more central units (CUs);

[0339] One or more circuits;

[0340] One or more power amplifiers.

[0341] 46. ​​The method according to any one of embodiments 24 to 45, wherein each of the first network node and / or the second network node comprises one or more of the following:

[0342] Base station;

[0343] eNodeB;

[0344] gNodeB;

[0345] O-DU;

[0346] O-CU;

[0347] O-CU-CP;

[0348] O-CU-UP;

[0349] O-eNB;

[0350] gNB-CU;

[0351] gNB-CU-CP;

[0352] gNB-DU;

[0353] Near RT RIC;

[0354] Non-RT RIC;

[0355] SMO node;

[0356] OAM node;

[0357] Core network nodes.

[0358] 47. The method according to any one of embodiments 24 to 46, wherein the one or more hardware resources used when the cell and / or carrier is operable include:

[0359] The one or more hardware resources used when the cell and / or carrier are available, enabled, active, provided, functional and / or usable;

[0360] The one or more hardware resources used to support, enable, activate, provide, maintain and / or sustain cells and / or carriers;

[0361] The one or more hardware resources used for transmitting and / or receiving signals associated with the cell and / or carrier; and / or

[0362] The one or more hardware resources used for sending and / or receiving user data.

[0363] 48. The method according to any one 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.

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

[0365] 50. The method according to any of the foregoing embodiments further comprises:

[0366] Obtaining user data; and

[0367] The user data is forwarded to the host or user device.

[0368] Group D Implementation Examples

[0369] 51. A network node, comprising:

[0370] The processing circuitry is configured to cause the network node to perform any step of any of the Group B embodiments;

[0371] A power supply circuit is configured to provide power to the processing circuit.

[0372] 52. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0373] Processing circuitry, configured to provide user data; and

[0374] A network interface configured to initiate the 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 being configured to perform any operation of any of the Group B embodiments to send the user data from the host to the UE.

[0375] 53. The host according to the preceding embodiment, wherein:

[0376] The processing circuitry of the host is configured to execute a host application that provides the user data; and

[0377] The UE includes processing circuitry configured to execute a client application associated with the host application to receive the transmission of user data from the host.

[0378] 54. A method implemented in a host, the host being configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising:

[0379] Provide user data to the UE; and

[0380] Initiate a transmission carrying the user data to the UE via a cellular network including the network node, wherein the network node performs any operation of any of the Group B embodiments to send the user data from the host to the UE.

[0381] 55. The method according to the preceding embodiment further includes: at the network node, transmitting the user data provided by the host to the UE.

[0382] 56. The method according to any one of the preceding two embodiments, wherein the user data is provided at the host by executing a host application, the host application interacting with a client application executed on the UE, the client application being associated with the host application.

[0383] 57. A communication system configured to provide over-the-top (OTT) services, the communication system comprising:

[0384] The host includes:

[0385] Processing circuitry configured to provide user data to a user equipment (UE), the user data being associated with the overlay service; and

[0386] A network interface configured to initiate the transmission of the user data to 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 being configured to perform any operation of any of the Group B embodiments to send the user data from the host to the UE.

[0387] 58. The communication system according to the preceding embodiment further includes:

[0388] The network node; and / or

[0389] The UE.

[0390] 59. A host configured to operate in a communication system to provide over-the-top (OTT) services, the host comprising:

[0391] Processing circuitry, configured to initiate the reception of user data; and

[0392] 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 being configured to perform any operation of any of the Group B embodiments to receive the user data from the user equipment (UE) for the host.

[0393] 60. The host according to the preceding embodiment, wherein:

[0394] The processing circuitry of the host is configured to execute a host application that receives the user data; and

[0395] The host application is configured to interact with a client application running on the UE, the client application being associated with the host application.

[0396] 61. The host according to any one of the preceding two embodiments, wherein initiating the reception of the user data includes: requesting the user data.

[0397] 62. A method implemented by a host, the host being configured to operate in a communication system further comprising network nodes and user equipment (UE), the method comprising:

[0398] At the host, the reception of user data from the UE is initiated, the user data originating from a transmission already received by the network node from the UE, wherein the network node performs any step of any of the Group B embodiments to receive the user data from the UE for the host.

[0399] 63. The method according to the preceding embodiment further includes: at the network node, sending the received user data to the host.

[0400] While the computing devices described herein (e.g., UE, network node, host) may include combinations of the hardware components shown, other embodiments may include computing devices with different combinations of components. It will be understood that these computing devices may include any suitable combination of hardware and / or software required to perform the tasks, features, functions, and methods disclosed herein. The determination, calculation, acquisition, or similar operations described herein may be performed by processing circuitry, which may process information, for example, by: converting acquired information into other information, comparing the acquired or converted information with information stored in a network node, and / or performing one or more operations based on the acquired or converted information, and making a determination as a result of said processing. Furthermore, although components are depicted as single boxes located within larger boxes or nested within multiple boxes, in practice, a computing device may include multiple different physical components constituting a single illustrated component, and functionality may be partitioned between individual components. For example, a communication interface may be configured to include any of the components described herein, and / or the functionality of a component may be partitioned between processing circuitry and the communication interface. In another example, non-computationally intensive functions of any such component may be implemented in software or firmware, while computationally intensive functions may be implemented in hardware.

[0401] In certain embodiments, some or all of the functions described herein may be provided by processing circuitry executing instructions stored in memory, which 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 functions may be provided by processing circuitry without requiring, for example, hard-wired execution of instructions stored on separate or separate device-readable storage media. In any of these particular embodiments, processing circuitry may be configured to perform the described functions regardless of whether instructions stored on a non-transitory computer-readable storage medium are executed. The benefits provided by such functions are not limited to the processing circuitry or other components of the computing device, but are enjoyed by the computing device as a whole and / or generally by the end user and wireless network.

Claims

1. A method (1300) for receiving information, performed by a first network node, the method comprising: Receive (1302) information identifying the following items from the second network node: One or more cells and / or carriers; as well as For each cell or carrier, one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) associated with the cell or carrier.

2. The method according to claim 1, wherein, For each cell or carrier, the one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) associated with the cell or carrier include one or more identifiers of one or more hardware resource groups used when the cell or carrier is operational.

3. The method according to claim 1 or 2, wherein, The information indicates that one or more hardware resource groups (1108, 1110, 1112) are included in one or more other groups.

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

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

6. The method according to any one of claims 1 to 5, wherein, The information indicates that one or more hardware resource groups (1108, 1110, 1112) are used by multiple network nodes.

7. The method according to any one of claims 1 to 6, comprising: Receive capability information from the second network node that identifies one or more capabilities of the one or more hardware resource groups (1108, 1110, 1112).

8. The method according to claim 7, wherein, The capability information for the one or more hardware resource groups (1108, 1110, 1112) includes one or more of the following: Multiple sleep and / or power modes supported by the one or more hardware resource groups (1108, 1110, 1112); The current hibernation and / or power mode of the one or more hardware resource groups; Multiple capability and / or capacity levels supported by the one or more hardware resource groups; The current capacity and / or capacity level of the one or more hardware resource groups; Whether the one or more hardware resource groups are able to provide an indication of energy consumption measurement.

9. The method according to claim 8, wherein, The capability information for the one or more hardware resource groups (1108, 1110, 1112) includes one or more of the following: Absolute and / or relative power consumption of the one or more hardware resource groups in each of the hibernation and / or power modes; Absolute and / or relative power consumption of the one or more hardware resource groups in each of the capability and / or capacity levels; Transition energy and / or transition time for the one or more hardware resource groups to transition between hibernation and / or power modes and / or between capacity and / or power levels.

10. The method according to any one of claims 1 to 9, comprising: Based on the information, one or more energy-saving features in the network, including the first network node and the second network node, are determined.

11. The method according to claim 10, wherein, Determining the one or more energy-saving features in the network includes: determining to deactivate one or more cells or carriers and deactivating the one or more hardware resource groups (1108, 1110, 1112) associated with the deactivated one or more cells or carriers.

12. A method (1400) for sending information, performed by a second network node, the method comprising: Send (1402) information identifying the following items to the first network node: One or more cells and / or carriers; as well as For each cell or carrier, one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) associated with the cell or carrier.

13. The method according to claim 12, wherein, For each cell or carrier, the one or more identifiers of one or more hardware resource groups associated with the cell or carrier include one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) used when the cell or carrier is operational.

14. The method according to claim 12 or 13, comprising: Receive hardware information from one or more other network nodes that identifies one or more hardware resource groups (1108, 1110, 1112), and determine the one or more hardware resource groups based on the hardware information.

15. The method according to claim 14, wherein, The hardware information identifying the hardware resource group (1108, 1110, 1112) is received from other network nodes that control and / or operate the hardware resource group.

16. The method according to claim 14 or 15, wherein, The hardware information identifier is one or more of the following: The association between the one or more hardware resource groups (1108, 1110, 1112) and the one or more cells and / or carriers; The one or more hardware resource groups are indicated as to their use when one or more cells and / or carriers are operational.

17. The method according to any one of claims 14 to 16, comprising: Receive capability information from the one or more other network nodes that identifies one or more capabilities of the one or more hardware resource groups (1108, 1110, 1112).

18. The method according to any one of claims 14 to 17, comprising: Receiving cell / carrier information identifying one or more cells and / or carriers from one or more other network nodes, wherein determining the one or more hardware resource groups (1108, 1110, 1112) includes: determining the one or more hardware resource groups based on the cell / carrier information.

19. The method according to claim 18, wherein, The cell / carrier information that identifies a cell or carrier is received from other network nodes that control, operate, and / or serve the cell or carrier.

20. The method according to any one of claims 12 to 19, wherein, The information indicates that one or more hardware resource groups (1108, 1110, 1112) are included in one or more other hardware resource groups.

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

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

23. The method according to any one of claims 12 to 22, wherein, The information indicates that one or more hardware resource groups (1108, 1110, 1112) are used by multiple network nodes.

24. The method according to any one of claims 12 to 23, comprising: Send capability information to the first network node that identifies one or more capabilities of the one or more hardware resource groups (1108, 1110, 1112).

25. The method according to claim 17 or 24, wherein, The capability information for the one or more hardware resource groups (1108, 1110, 1112) includes one or more of the following: Multiple hibernation and / or power modes supported by the one or more hardware resource groups; The current hibernation and / or power mode of the one or more hardware resource groups; Multiple capability and / or capacity levels supported by the one or more hardware resource groups; The current capacity and / or capacity level of the one or more hardware resource groups; Whether the one or more hardware resource groups are able to provide an indication of energy consumption measurement.

26. The method of claim 25, wherein, The capability information for the one or more hardware resources includes one or more of the following: Absolute and / or relative power consumption of the one or more hardware resource groups in each of the hibernation and / or power modes; Absolute and / or relative power consumption of the one or more hardware resource groups in each of the capability and / or capacity levels; Transition energy and / or transition time for the one or more hardware resource groups to transition between hibernation and / or power modes and / or between capacity and / or power levels.

27. The method according to any one of claims 12 to 26, comprising: A request for the information is received from the first network node, wherein the information is sent to the first network node in response to the request.

28. The method according to any one of claims 1 to 27, wherein, Each of one or more of the hardware resource groups (1108, 1110, 1112) includes one or more of the following: 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 (DUs); One or more central units (CUs); One or more circuits; One or more power amplifiers.

29. The method according to any one of claims 1 to 28, wherein, Each of the first network node and / or the second network node includes one or more of the following: Base station; eNodeB; 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; OAM node; Core network nodes.

30. The method according to any one of claims 1 to 29, wherein, The one or more hardware resource groups (1108, 1110, 1112) include: The one or more hardware resource groups used when a cell and / or carrier is available, enabled, active, provided, functional and / or usable; The one or more hardware resource groups used to support, enable, activate, provide, maintain and / or sustain cells and / or carriers; The one or more hardware resource groups used for transmitting and / or receiving signals associated with the cell and / or carrier; and / or The one or more hardware resource groups used for sending and / or receiving user data.

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

32. A tangible, non-transitory computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform an operation, the operation comprising: Receive (1302) information identifying the following items from the second network node: One or more cells and / or carriers; as well as For each cell or carrier, one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) associated with the cell or carrier.

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

34. A tangible, non-transitory computer-readable medium comprising instructions that, when executed by processing circuitry, cause the processing circuitry to perform an operation, the operation comprising: Send (1402) information identifying the following items to the first network node: One or more cells and / or carriers; as well as For each cell or carrier, one or more identifiers of one or more hardware resource groups (1108, 1110, 1112) associated with the cell or carrier.

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

36. A computer program comprising instructions that, when executed by a processing circuit, cause the processing circuit to perform the method (1300, 1400) according to any one of claims 1 to 31.

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

38. A carrier comprising the computer program according to claim 37, wherein, The carrier is one of an electronic signal, an optical signal, a radio signal, or a computer-readable medium.

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

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

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

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

Images