Linking information with network resources to achieve energy optimization and exposure.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-02-12
- Publication Date
- 2026-08-14
Smart Images
Figure CN122579158A_ABST
Abstract
Description
Technical Field
[0001] The examples of embodiments described herein generally relate to wireless networks, and more specifically, to accessing information about network resources to allow for energy optimization and exposure within the wireless network. Background Technology
[0002] For wireless networks such as cellular networks, network elements and functions can be powered by multiple energy sources at different times. These power sources include the power grid, batteries, UPS (Uninterruptible Power Supply), generators (e.g., diesel backup generators), and / or on-site power generation (e.g., solar, wind power). These energy sources are generally considered to be grid power, backup energy, and locally generated energy. These power sources are not managed by the 3GPP (3rd Generation Partnership Project) system, at least as applied to cellular networks, but are integrated by interfaces defined by ETSI (European Telecommunications Standards Institute). However, the 3GPP system uses information related to these power sources to power network elements and functions.
[0003] The carbon emission factor and renewable energy factor differ for each of these power sources. Several proposals have been made for software architectures, such as IOC (Information Object Class, representing the management aspect of network resources), which can be accessed and used by operators in cellular networks to configure this information within the 3GPP system, and can also be distributed and utilized within the 3GPP system (including 5GC (fifth-generation core network) and external third parties). While these software architectures and their implementations by hardware components have advantages, they can be improved. Summary of the Invention
[0004] This section is intended to include examples and is not intended to be restrictive.
[0005] In the example, a method is disclosed that includes a manager entity in a wireless network performing operations including: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving the value of an attribute representing a group to which the managed entity participates; navigating to the group at least using the attribute; retrieving a reference to information associated with the group; navigating to information associated with the group at least based on the reference; and obtaining the information associated with the group.
[0006] Additional examples include a computer program that includes instructions that, when executed on a device, perform the methods described in the preceding paragraph. The computer program according to this paragraph is a computer program product comprising a computer-readable medium carrying instructions implemented therein for use with a device. Another example is a computer program according to this paragraph in which the program can be directly loaded into the internal memory of the device.
[0007] An example of an apparatus includes one or more processors and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least the following operations by a manager entity in a wireless network: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving the value of an attribute representing a group to which the managed entity participates; navigating to the group at least using the attribute; retrieving a reference to information associated with the group; navigating to information associated with the group at least based on the reference; and obtaining the information associated with the group.
[0008] An example of a computer program product includes a computer-readable storage medium carrying instructions that, when executed by a device, cause the device to perform at least the following operations: by a manager entity in a wireless network, the manager entity identifies a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieves the value of an attribute representing a group to which the managed entity participates; navigates to the group at least using the attribute; retrieves a reference to information associated with the group; navigates to information associated with the group at least based on the reference; and obtains the information associated with the group.
[0009] In another example, an apparatus includes components for performing the following operations by a manager entity in a wireless network: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving the value of an attribute representing a group to which the managed entity participates; navigating to the group at least using the attribute; retrieving a reference to information associated with the group; navigating to information associated with the group at least based on the reference; and obtaining information associated with the group. Attached Figure Description
[0010] The accompanying drawings use reference numerals, where the same reference numerals can always be used to refer to the same parts, but parts with the same reference numerals may differ in operation and composition. In the drawings: Figure 1 This is a class diagram illustrating the relationships between NRM fragments related to PowerSupplyInfo (power supply information); Figure 2 This is a class diagram illustrating fragments of the general set NRM; Figure 3 It is a class diagram that shows NRM fragments of energy supply information; Figure 4 This is a class diagram showing NRM segments of the energy information group; Figure 5 This is a class diagram showing NRM segments of the energy information group; Figure 6 This is a class diagram of TopX IOC, showing an NRM fragment; Figure 7 This is a class diagram of the generic collection of NRM fragments for the example; Figure 8 This is a flowchart of a method for associating information with network resources to achieve energy optimization and exposure; Figure 9 This is a block diagram of one possible and non-limiting example system in which exemplary embodiments can be practiced; and Figure 10 It is an instruction Figure 9 The diagram also shows a possible implementation of the manager entity. Detailed Implementation
[0011] The abbreviations that can be found in the specification and / or drawings are defined at the end of the Detailed Description section below.
[0012] The word "example" is used herein to mean "used as an example, instance, or illustration." Any embodiment described herein as an "example" is not necessarily to be construed as preferred or advantageous over other embodiments. All embodiments described in this detailed description are exemplary embodiments provided to enable those skilled in the art to make or use them.
[0013] When more than one figure mark, number, word, or acronym with " / " is used in this specification, and as is generally used in this specification, " / " can be interpreted as "or", "and", or "both". As used herein, "at least one of the following: " and "at least one of " and similar wording, wherein the list of two or more elements is connected by "and" or "or", indicates at least any one of the elements, or at least any two or more of the elements, or at least all of the elements.
[0014] As used herein, the singular forms “a,” “an,” and “the” are also intended to include the plural forms, unless the context clearly indicates otherwise. It will also be understood that the terms “comprising,” “including,” “having,” “having,” “containing,” and / or “comprising” as used herein specify the presence of the stated features, elements, and / or components, but do not exclude the presence or addition of one or more other features, elements, components, and / or combinations thereof.
[0015] Note that words or phrases in uppercase and lowercase are considered the same in this article. For example, the words “Slice,” “slice,” and “SLICE” are the same, as are the phrases “Network Repository Function,” “network repository function,” and “NETWORK REPOSITORY FUNCTION.”
[0016] Any flowchart or signaling diagram in this document is considered a logic flowchart and illustrates the operation of an example method, the result of execution of computer program instructions implemented on a computer-readable storage medium, and / or the function executed by logic implemented in a circuit. For methods, flowcharts, and signaling diagrams, the order of method steps, boxes, or signaling in the flow are not required but are examples.
[0017] Technical context is now provided for understanding the technical fields relevant to the example. This is provided as a brief overview of potentially relevant technical fields.
[0018] Energy consumption constitutes a major portion of an operator's OPEX (operational expenditure). In most operator network deployments, networks are designed to support maximum load configurations, and therefore energy-saving optimizations directly translate into OPEX savings for the operator. Recently, there has been a global push towards energy awareness, reducing carbon footprints, and shifting towards renewable energy.
[0019] In 3GPP (3rd Generation Partnership Project) Rel-19 (Release 19), solutions are being researched and developed across all domains (RAN (Radio Access Network), Core, and OAM (Operations, Administration, and Maintenance)) to achieve energy savings, energy efficiency, and energy awareness within the network. 3GPP recognizes that energy-related information (including energy consumption, renewable energy information, and carbon emissions information) for each network element and function is important for optimizing the network and exposing this information to third parties.
[0020] The examples in this article involve energy-related information (including energy consumption, renewable energy information, and carbon emission information) for network elements and network functions.
[0021] Network elements are managed using ManagedElement, and network functions are managed using the ManagedFunction model. A ManagedElement is an IOC representing a telecommunications device within a telecommunications network that provides support and / or services to subscribers. An IOC represents the management aspect of a network resource. It describes the information that can be passed / used in the management interface. They are represented as technology-agnostic software objects. IOCs have attributes representing various properties of the object class. See Clause 3.1 of 3GPP TS 28.622.
[0022] The ManagedElement IOC is used to represent network elements, including virtualized or non-virtualized scenarios (e.g., discrete telecommunications entities that can be managed through specific interfaces). A ManagementElement instance is used to communicate with a manager (directly or indirectly) through one or more management interfaces for monitoring and / or control. A ManagedElement may or may not perform additional element management functions. A ManagedElement contains devices that may or may not be geographically distributed. See, for example, Clause 4.3.3.1 of 3GPP TS 28.622.
[0023] The ManagedFunction IOC is provided only for subclasses. It provides the properties common to all functional IOCs. Note that a ManagedElement can contain several managed functions, and managed functions can contain additional managed functions specified for a particular subclass. See, for example, Clause 4.3.4.1 of 3GPP TS 28.622.
[0024] The model in 3GPP SA5 (3GPP Technical Specification Group (TSG) Services and Systems Aspects, Working Group 5) should support energy-related information about network elements and network functions that can be retrieved by any authorized consumer (third party or 3GPP entity).
[0025] In the ongoing Release 19, 3GPP is researching and developing solutions across all domains (RAN, core, and OAM) to achieve energy savings, energy efficiency, and energy awareness within the network.
[0026] In this context, 3GPP SA1 (3GPP Technical Specification Group (TSG) Services and Systems Aspects, Working Group 1), which is responsible for system-level requirements, has specified requirements for 5G (fifth generation) systems to expose energy consumption-related information, including renewable energy and carbon emission information, to third parties. See Clause 6.15a.5.2 of 3GPP TS 22.261.
[0027] Furthermore, 3GPP TS 23.501 (from SA2) Clause 5.51.2 specifies that the EIF (Energy Information Function) retrieves this energy consumption information of network elements and network functions from the OAM.
[0028] Relevant use cases and potential requirements were studied as part of 3GPP SA5 Release 19 study FS_Energy_OAM_Ph3 and are documented in Clause 5.3 of 3GPP TR 28.880. The same specification work planned as part of the WT-2 work project objectives of 3GPP SA5 Release 19 Energy_OAM_Ph3 is to specify energy supply, carbon emissions, and renewable energy information relative to gNB and 5G NF.
[0029] The use cases and potential solutions described in 3GPP TR 28.880 (e.g., 3GPP TR 28.880 V2.0.0 (2024-12)) released in December 2024 propose a new information element that will be defined to associate energy-related information with managed functions. However, the details of the information element and its association with managed functions are left to the specification phase, namely 3GPPSA5 Release 19 Work Item Energy_OAM_Ph3, which is intended to be completed by September 2025.
[0030] During the recently concluded version 19 research, a potential solution (pCR (pseudo-change request), S5-245619) was proposed to model energy-related information as a class (PowerSupplyInfo) and associate this class with a name-inclusion relationship (e.g., Figure 1 (As shown). Name-inclusive relationships are due to naming conventions that use hierarchical inclusive structures. See, for example, Clause 3.1.5 of 3GPP TS 32.300. Figure 1 This is a class diagram illustrating the relationships between NRM (Network Resource Model) fragments for PowerSupplyInfo. NRMs are management service components, corresponding, for example, to some resources in the network introduced starting with version 16. Starting with version 15, control NRM fragments were introduced for different management tasks, such as subscribing to receive notifications or managing performance metrics production jobs. Figure 1In the example, the PowerSupplyInfo IOC (Information Object Class) is proposed to be included by the name of a ProxyClass representing a SubNetwork or ManagedEntity. PowerSupplyInfo has a composition relationship with ManagedEntity. A SubNetwork is defined as follows: A SubNetwork is an IOC representing a set of managed entities. A SubNetwork can have zero or more instances. A SubNetwork should exist if there is a ManagementNode or multiple ManagedElements (i.e., instances of ManagementNode and multiple ManagedElements should have a SubNetwork as a parent). A SubNetwork instance not included in any other instance of a SubNetwork is called the "root" SubNetwork instance. See Clause 4.3.7.1 of 3GPP TS28.622 V19.2.0 (2024-12).
[0031] One discussion is based on grouping a set of network functions and / or network elements and / or entire subnetworks, using a generic collection class (such as EnergyInfoGroup / CoLocatedNF) (where NF is a network function). Figure 2 As shown, it was proposed as part of a CR (Change Request) in SA5#156 (S5-243592) and has been shared with 3GPP participants. Figure 2 The diagram illustrates a class diagram of a generic collection NRM fragment. It shows an example where any proxy class has an aggregation relationship with a GenericCollection IOC, and the GenericCollection IOC has a composition relationship with a SubNetwork IOC. In this proposal, energy-related information is associated with the group (e.g., ...). Figure 3 , Figure 4 and Figure 5 (as shown in the image). Figure 3This is a class diagram illustrating fragments of the Energy Supply Information (NRM). The ManagedEntity proxy class represents the following IOCs: subnetwork, CoLocatedNFsGroup, ManagedFunction, or ManagedElement. The EnergySourceInfo IOC has a composition relationship with the EnergySuppyInfo IOC, and the EnergySuppyInfo IOC has a composition relationship with ManagedEntity.
[0032] Figure 4 This is a class diagram illustrating an NRM (Number Retention Module) fragment. In this example, the ManagedEntity proxy class can be SubNetwork, ManagedElement, or ManagedFunction, and it has an aggregation relationship with the EnergyInfoGroup IOC, which is directly associated with the EnergyUsageInfo (Energy Usage Information) IOC. Figure 5 This is a class diagram illustrating NRM fragments of the energy information group. It is similar to... Figure 4 In addition to ManagedEntity, it can also represent EnergyUsageInfo IOC, and EnergyInfoGroup IOC has a composition relationship with SubNetwork IOC.
[0033] All of the above proposals have the drawback that energy-related information cannot be retrieved for network elements and / or network functions unless consumers who require energy-related information for a specific network element or function perform the following additional steps: Step #1) Traverse all groups in the management MIB (Management Information Base) tree to identify the group to which a network element or network function belongs; and Step #2) Retrieve energy-related information associated with the group.
[0034] Given the typical size of a large MIB, this requires processing a large amount of data to retrieve this information for any network element or function. The complexity and time required for such processing, as well as the computational and memory resources required for such an operation, can be high. Since network elements and functions (e.g., EIF (Energy Information Function), UPF (User Plane Function), etc.) require such information, this processing may introduce adverse effects on the network.
[0035] For example, consider an operator network comprising 10,000 operator sites. When EnergyInfoGroup represents an operator site, the number of instances of EnergyInfoGroup will be 10,000. To retrieve energy-related information for a network element (e.g., a gNB), the consumer would need to iterate through groups ranging from a minimum of 1 (one group) (in the best-case scenario, the first group during iteration) to a maximum of 10,000 (in the worst-case scenario, the last group during iteration) to identify the group to which a network element or network function belongs.
[0036] As mentioned above, 3GPP network functions need to be associated with energy-related information, which can be retrieved for further exposure or optimization. Also as mentioned above, existing proposals involving retrieving energy-related information from ManagedElement (used to manage network elements) or ManagedFunction (used to manage network functions) are complex. Consumers of such information will be required to: 1) Possesses knowledge of the entire management MIB tree. 2) Load the information into the MIB tree. 3) Traverse the MIB tree to identify the groups associated with network functions or network elements (i.e., the DN (proprietary name) of managedFunction or managedElement). 4) Traverse all groups in the management MIB tree to identify the group to which a network element or network function belongs, and 5) Retrieve energy-related information associated with the group.
[0037] The consumer of this information can be a web element or the web function itself.
[0038] Therefore, none of the existing proposals support navigation to energy-related information from ManagedElement (used to manage network elements) or ManagedFunction (used to manage network functions).
[0039] Therefore, based on the existing mechanism, network elements or network functions that require this information for optimization cannot retrieve this information without knowing the entire network (i.e., the entire management tree).
[0040] To address these and other issues, the examples in this paper introduce enablers to navigate from ManagedElement (used to manage network elements) or ManagedFunction (used to manage network functions) to their energy-related information. Using enablers, consumers can directly retrieve information from ManagedElement or ManagedFunction. Consumers do not need to load and traverse the entire management tree. In scenarios where the consumer is the 5G network function itself, the network function can directly retrieve energy-related information associated with it without traversing the entire management MIB tree. Furthermore, this mechanism can be generalized to any group and its members, enabling navigation from any member to the group to which those members belong.
[0041] As mentioned earlier, the existing proposals do not solve the problem because all of them require consumers to know the entire management tree, traverse the tree to identify groups associated with network elements or network functions, and then retrieve energy-related information.
[0042] The example solves at least the following problems.
[0043] 1) The definition of a generic collection object is improved by defining group members using abstract base classes (Derived from abstract base classes: SubNetwork, ManagedElements, ManagedFunction) instead of proxy classes. An abstract class is a class that cannot be instantiated itself; it needs to be subclassed by another class to use its properties. A proxy class is an alias that replaces multiple classes. A typical use case is to merge multiple alternative / parallel components into one. This can be achieved, for example, by using the abstract class TopX in the group. The TopX IOC is only provided for subclassing.
[0044] GenericCollection IOC can be used to aggregate group instances of any objects that inherit from the abstract class TopX, because the SubNetwork, ManagedElement, ManagedFunction, and Link classes inherit from TopX (see 3GPP TS 28.622). Figure 4 .2.2-1). See also Figure 6This diagram is a class diagram of the TopX IOC and shows an NRM fragment. The diagram illustrates the inheritance relationships, where managed entity 620 inherits from TopX IOC 610 and also from traditional classes ending in underscores. Italicized IOCs (e.g., TopX and ManagedFunction) are abstract classes. TopX IOC 610 and the inheritance structure show how much managed entity 520 can inherit, inheriting all the properties and characteristics of TopX IOC 610. That is, managed entity 620 demonstrates the breadth of inheritance from TopX IOC 610, as the various IOCs—Link, ManagedFunction, ManagedElement, ManagementNode, and SubNetwork—enable access to most or all of the wireless network, and any changes to TopX IOC 610 have an impact throughout the entire wireless network.
[0045] 2) Associated properties are introduced into the generic collection in this abstract base class. This introduces an enabler to navigate from the group's members to the generic collection object.
[0046] The inventors have recognized the following. As previously stated, TopX is an abstract class. A primary purpose of Top (and TopX, which is the renamed "traditional" 3GPPTop class) is to serve as a common ancestor of all 3GPP classes. Common characteristics / properties that should exist everywhere are defined here.
[0047] Therefore, the inventors have recognized that an enabler can be implemented by introducing an attribute in the abstract class TopX (defined in Clause 4.3.8 of 3GPP TS 28.622) to associate an object with the group it belongs to. The new attribute (groupReferenceList) will reference the group to which the object belongs (the DN of GenericCollection or its subclasses). A proper name (DN) is used to uniquely identify a managed object (MO) within a namespace, which is a collection of names. A DN is constructed based on a set of “name components” called relative proper names (RDNs). A managed object (MO) is a software object that encapsulates the manageable characteristics and behaviors of a specific network resource. Specifically, an MO is an encapsulation of the management characteristics of anything being managed.
[0048] ManagedElement (used to manage network elements) or ManagedFunction (used to manage network functions) can use this new property (groupReferenceList) to retrieve energy-related information.
[0049] Consumers that require energy-related information (e.g., 5GC NF) using these enablers should call the getMOIAttribute API (Application Programming Interface) (defined in 3GPP TS 28.532) twice, as described below: 1) Using the DN of ManagedElement or ManagedFunction, retrieve the value from the new property groupReferenceList in the MOI. This provides the DN(s) of the GenericCollection instance, i.e., the group associated with the ManagedElement or ManagedFunction.
[0050] 2) Using the (multiple) DNs of a GenericCollection, energy-related information can be retrieved using the properties of the DN that maintains the EnergySuppyInfo. This reduces the complexity involved in traversing the entire administrative MIB tree.
[0051] The following are planned changes, such as standardization of specification 3GPP TS 28.622.
[0052] 1) According to Figure 7 Introduce or enhance the relational graph for GenericCollection in Clause 4.2.1 of TS 28.622.
[0053] 2) The groupReferenceList property is introduced in TopX IOC by enhancing TS 28.622 by clauses 4.3.8.2 and 4.4.1 as described below.
[0054] about Figure 7 The relationship is described. Figure 7 This is a class diagram of the example generic collection NRM fragment. TopX IOC 610 (also simply TopX) is provided for subcategories. TopX IOC 610 has an aggregation relationship 725 with GenericCollection IOC 720. GenericCollection IOC 720 represents a generic collection of managed entities. The memberDN attribute can be used to identify members of groups within the generic collection. GenericCollection IOC 720 has a composition relationship 715 with SubNetwork IOC 710. Aggregation relationship 725 allows groups to form any derivative of TopX, and group membership can be recursive. The term recursive here means that a group can be a member of another group, which in turn can be a member of yet another group, making a group of groups a possible implementation. Regarding grouping, this means that a group can be formed from... Figure 6 Any single or multiple managed entities 620 can be formed. That is, any object instantiated from TopX (such as ManagedElement) can be grouped under GenericCollection IOC 720, and the object can be referenced via a property inherited from TopX that is a member of the GenericCollection. Note that not only information under the GenericCollection (i.e., members) can be accessed, but also any information associated with the GenericCollection (i.e., references from GenericCollection to any other class, such as EnergyUsageInfo from the Nokia pCR mentioned above).
[0055] In one example, all information object classes defined in all TSs that claim to conform to 3GPP TS 32.102 should inherit from TopX. The attributes include the following:
[0056] In this table, M = mandatory, T = true, and F = false. No attribute constraints are defined, and no notifications are defined.
[0057] Regarding attribute characteristics, the following table defines the characteristics of the attributes specified in this document.
[0058]
[0059] Because the `groupReferenceList` property contains the DN (property name) of the group associated with the managed object instance (MOI), all objects instantiated from TopX IOC 610 (e.g., managed entity 620) can access this property, and through this property, access (multiple) groups, and thus access the information associated with (multiple) groups. This information may be related to one or more energy supplies, or energy-related information. Such energy-related information may include one or more of the following corresponding to network resources: energy consumption, renewable energy information, or carbon emission information.
[0060] refer to Figure 8 This diagram is a flowchart of a method 800 for associating information with network resources to achieve energy optimization and exposure. It is assumed that the operations in this diagram are performed by a manager entity in a wireless network, as described below. Figure 9 and Figure 10An example of manager entity 940 is shown. In operation 805, manager entity 940 identifies managed entities. Managed entities correspond to network resources in a wireless network. More specifically, the managed entities identified in this operation can be considered "entities of interest". Consider the following use case: enabling operators to efficiently handle / manage the energy consumption of entities and to clearly (e.g., quickly) identify what energy is available to an entity. One purpose of adding a new attribute to the very top—the TopX ancestor of all managed objects—is to achieve this. The use case also allows operators to clearly (e.g., quickly) identify all entities by utilizing (or depending on) specific energy sources.
[0061] Manager entity 940 retrieves the values of attributes representing the groups in which the managed entity participates. See operation 810. In operation 815, manager entity 940 navigates to the group using at least the attributes, and in operation 820 retrieves a reference to the information associated with the group. In operation 825, manager entity 940 navigates to the information associated with the group based at least on the reference. In operation 830, manager entity 940 retrieves the information associated with the group.
[0062] In method 800, managed entities can be represented by objects, the categories of which are derived from TopX. For method 800 and this paragraph, managed entities can be represented by objects instantiated from the ManagedElement class, or by objects instantiated from classes derived from the ManagedFunction class. For method 800 and this paragraph, the group can be identified by its proprietary name (DN). Information associated with this group relates to one or more energy supplies.
[0063] Method 800 may include information associated with the group that relates to energy-related information. Energy-related information may include one or more of the following: energy consumption, renewable energy information, or carbon emission information. In method 800, the group may include one or more other managed entities corresponding to other network resources in the wireless network.
[0064] Turn Figure 9The figure illustrates a block diagram of a possible, non-limiting system 900, of which a practical example may be implemented. For the purposes of this example, the manager entity 940 interacts with at least network resources 925 in the system. Network resources 925 are considered to be UE 10 (network resource 925-1), gNB 70 (network resource 925-2), (multiple) network functions (NF(s)) 99 (network resource 925-3), and other network resources 952-4. Examples of network resources include switches, scanners for monitoring performance data, cells, sites, transmission links (e.g., and corresponding circuits), satellites, etc. The other network resources 925-4 are intended to capture those network resources not shown, and are assumed to have (multiple) processors, one or more memories, and corresponding instructions.
[0065] One or more manager entities 940 interact with manager agents 910, which are: manager agent 910-1 on UE 10; manager agent 910-2 on NF 99; manager agent 910-3 on gNB 70; and manager agents 910-4 on other network resources 925-4. Note that a manager entity may also be referred to as a management entity, and a manager agent may be referred to as a management agent. The terminology used is not as important as the operations performed by these terms in relation to the examples herein. Manager agent 910 corresponds to managed entity 620, such as an object instantiated from ManagedFunction IOC or ManagedElement IOC. Manager agent 910 relates to possible embodiments (i.e., the methods of the examples can be applied to agent-based implementations), but this is only one possibility. Manager agent 910 is part of corresponding instructions that, when executed by the corresponding processor(s), cause network resource 925 to perform operations. Figure 10 As shown, the manager entity has instructions 920, which are retrieved and executed by circuitry including processors(s), as described below.
[0066] Manager entity 940 performs the operations described in this document, such as Figure 8The manager entity 940 can also communicate with one or more energy systems 930, and in particular, (multiple) energy management systems 935. This is shown as direct, i.e., utilizing energy system 930, but can be via the operator of (cellular) network 1. In this example, the energy systems themselves have their own managers (i.e., "energy management systems"), with which the energy systems communicate. Energy system 930 can be a nuclear power plant, an energy supplier, a green energy supplier (e.g., from wind / solar / batteries or other storage devices), etc. This allows the manager entity 940 to report information from the system to the energy system 930, or to take action on information from the energy system 930, such as notification of pending / planned / imminent power outages.
[0067] Figure 9 This is an example of a system 900 having a cellular network 1 connected to a user equipment (UE) 10. Figure 9 The cellular network shows several network elements: gNB 70, which can be an access network; and core network 90.
[0068] exist Figure 9 In this embodiment, User Equipment (UE) 10 wirelessly communicates with gNB 70 of Cellular Network 1 via radio link 11. UE 10 is a wireless communication device, such as a mobile device, configured to access the cellular network. UE 10 is shown having one or more antennas 28. UE 10 includes one or more processors 13, one or more memories 15, and other circuitry 16. The other circuitry 16 includes one or more receivers (Rx) 17 and one or more transmitters (Tx) 18. Instructions 12 (e.g., from a program or other software) are used to cause UE 10 to perform the operations described herein. For UE 10, the other circuitry 16 may include circuitry such as user interface elements (not shown) for a display-like device. Instructions 12 may be stored in one or more memories 15 and executed by processor(s) 13, or by circuitry such as those implemented as part of processor(s) or other circuitry elements, or both.
[0069] As a network element of cellular network 1, gNB 70 provides UE 10 with access to cellular network 1 and data network 91 via core network 90 (e.g., via the User Plane Function (UPF) of core network 90). Therefore, gNB 70 can be considered a base station, which is an access node providing access to cellular network 1 for (multiple) UE 10s. gNB 70 is shown having one or more antennas 58. Typically, gNB 70 can be referred to as a RAN (Radio Access Network) node or (equivalently) an access network, and can be abbreviated as (R)AN. Alternatively, it is mostly referred to as gNB (gNode B, NR (New Radio) base station) 70. However, many other examples exist that include RAN nodes such as eNB (Evolved Node B) or TRP (Transmitter Receiver Point).
[0070] The gNB 70 can be monolithic, meaning that all functionality, such as layers in the protocol stack, is executed in a single element. The gNB as an access network can also be implemented with functional decomposition, where some (e.g., lower) layers of the protocol stack are implemented in the DU (Distributed Unit) 42, and some (e.g., higher) layers are implemented in the CU (Central Unit) 43, with a “mid-haul” interface 44 connecting the DU 42 and CU 43. Each CU 43 can have multiple DU 42s, although... Figure 9 Only one DU 42 is shown. Furthermore, (multiple) DU 42s can be connected to a radio unit (RU) 41, which handles at least the physical layer portion for transmission and reception. (Multiple) DU 42s can be connected to the radio unit (RU) 41 via a "fronthaul" interface 46. CU 43 and DU 42 can be logical nodes, implemented by the gNB 70 via (multiple) processors 73 by fetching instructions 72 from memory 75 and executing those instructions 72. Note that, at least for functional splitting, there may be a split of several kilometers between (multiple) DU 42s and CU 43.
[0071] The gNB 70 includes one or more processors 73, one or more memories 75, and other circuitry 76. The other circuitry 76 includes one or more receivers (Rx) 77 and one or more transmitters (Tx) 78. Instructions 72 (e.g., from a program or other software) are used to cause the gNB 70 to perform the operations described herein. Instructions 72 may be stored in one or more memories 75 and executed by the processor(s) 73, or by circuitry such as being implemented as part of the processor(s) or other circuitry elements, or both. If functional splitting is used, DU 42 and CU 43 (which may be referred to as logic elements) are implemented using circuitry of the processor 73, memories 75, and potentially other circuitry 76.
[0072] The example shows a manager agent 910-3 for the primary gNB 70, but multiple manager agents 910 can be used, for example, one manager agent 910 for each CU 43, DU 42, and RU 41. This example uses CU 43, DU 42, and RU 41 as separate network resources 925.
[0073] It should be noted that gNB 70 can alternatively be implemented via other wireless technologies such as Wi-Fi (a wireless network protocol used by devices to communicate without a direct cable connection). In the case of Wi-Fi, link 11 can be characterized as a wireless link. More specifically, the examples are not technology-specific. These are applicable to any communication technology where management is model-driven (with (multiple) MIBs / NRMs). This article focuses on 3GPP NRMs, but the other examples do not need to be specific to 3GPP technologies (LTE / 5G / 6G).
[0074] Two or more gNBs 70 communicate using, for example, multiple links 79. The multiple links 79 can be wired or wireless or both, and can implement, for example, an Xn interface for 5G (fifth generation), an X2 interface for LTE (long-term evolution), or other suitable interfaces for other standards.
[0075] Cellular network 1 may include a core network 90 as one or more second network elements. Core network 90 may include core network functions and provide connectivity to data network 91 (such as telephone networks and / or data communication networks (e.g., the Internet)) via one or more links 81. Core network 90 includes one or more processors 93, one or more memories 95, and other circuitry 96. The other circuitry 96 includes one or more receivers (Rx) 97 and one or more transmitters (Tx) 98. Instructions 92 (such as those from a program or other software) are used to cause core network 90 to perform the operations described herein. Instructions 92 may be stored in one or more memories 95 and executed by one or more processors 93, or by circuitry such as that implemented as part of one or more processors or other circuitry elements, or both.
[0076] The core network 90 can be a 5GC (5G core network). The core network 90 can implement or include multiple network functions (NF(s)) 99, and instructions 92 can include one or more NF(s) 99. The 5G core network can use circuitry such as memory and processors, which can implement a virtualization layer. It can be a single standalone computing system, a distributed computing system, or a cloud computing system. The NF 99 of the core network (as network elements) can be containers or virtual machines running on the circuitry of the computing system(s) constituting the core network 90.
[0077] Core network functions for 5G may include access and mobility management functions provided by network function 99, such as Access and Mobility Management Function (AMF), and session management functions provided by network functions, such as Session Management Function (SMF). Core network functions for access and mobility management in LTE (Long Term Evolution) networks may be provided by MME (Mobility Management Entity) and / or SGW (Serving Gateway) functions that route data to the data network. Many others are possible, such as... Figure 9 Examples shown include: AMF; SMF; MME; SGW; GMLC (Gateway Mobility Location Center); LMF (Location Management Function); UDM (Unified Data Management) / UDR (Unified Data Repository); NRF (Network Repository Function); and / or E-SMLC (Evolved Serving Mobility Location Center). These are merely examples of core network functions that can be provided by the core network 90, and note that both 5G and LTE core network functions can be provided by the core network 90. The gNB 70 is coupled to the core network 90 via backhaul link 31. The gNB 70 and the core network 90 may include an NG (Next Generation) interface for 5G, or an S1 interface for LTE, or other suitable interfaces for other radio access technologies communicating via backhaul link 31.
[0078] In data network 91, there is instruction 94 stored in computer-readable storage medium 4-1, which may be circuitry such as long-term memory (e.g., hard disk drive or solid-state drive), short-term memory (e.g., dynamic random access memory), or a combination of both (e.g., reading from long-term memory to temporarily place in short-term memory and then downloading). Computer-readable medium 4-1 contains instruction 94, which, when downloaded and installed into instruction 12, instruction 72, and instruction 92 and / or memory 15, memory 75, or memory 95 of the corresponding UE 10, gNB 70, and / or (multiple) core network elements 90 and executed by (multiple) processors 13, (multiple) processors 73, or (multiple) processors 93, causes the corresponding device to perform the corresponding action described herein. Computer-readable storage medium 4-1 may be implemented in other forms, such as via optical disc (as computer-readable storage medium 4-2) or memory stick containing instruction 94.
[0079] Instructions 12, 72, and 92 are stored in one or more corresponding memories 15, 75, or 9. When executed by one or more corresponding processors 13, 73, or 93, these instructions cause the corresponding device 10, 70, or 90 to perform the operations described herein. The computer-readable memory 15, 75, or 95 is circuitry and can be of any type suitable for the local technical environment, and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, firmware, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Processors 13, 73, and 93 are circuitry and can be of any type suitable for the local technical environment. For example, by non-limiting example, these processors may include one or more of the following: general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), processors based on multi-core processor architectures, and may also include special-purpose circuitry such as field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), signal processing devices, and other devices, or combinations thereof. Processors 13, 73 and 93 are circuits that can be programmed to perform functions via software, firmware and other means, including microcode, and not just software.
[0080] Receivers 17, 77, and 97, and transmitters 18, 78, and 98 can implement wired or wireless interfaces. Receivers and transmitters can be grouped together as transceivers.
[0081] Cellular network 1 can achieve network virtualization, which is the process of combining circuit and software network resources and network functions into a single software-based management entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as external: combining many networks or parts of networks into virtual units or internal: providing network-like functionality to a software container on a single system. Note that virtualized entities (such as network function 99) resulting from network virtualization are still implemented to some extent using circuitry such as processor 73 and / or processor 93 and memory 75 and / or memory 95, and such virtualized entities also produce technical effects.
[0082] refer to Figure 10The diagram illustrates possible implementations 1001, 1002, or 1003 for one or more manager entities 940, which can be implemented as one or more of a standalone implementation 1001, a virtualized implementation 1002, or a container implementation 1003. Circuits 1010 are implementations, each including a processor, memory, and possibly other circuitry. As an example, the manager entity 940 could be controlled by a telecommunications operator.
[0083] The standalone implementation 1001 includes circuitry 1010-1, an operating system (OS) 1015, and instructions 920 to implement the manager entity 940. This example is one where the application (in this case, the manager entity 940) runs on a physical server. This is an example where a single "box" would exist. For example, a server that can be physically touched and would be implemented in or coupled to, for example, a telecommunications network 1.
[0084] Virtualization implementation 1002 includes circuitry 1010-2, OS 1015, virtual machine monitor 1025, a first VM 1030-1 executing its own OS 1035-1 and binary / library 1040-1, and instructions 920-1 implementing a manager entity 940; a second VM 1030-2 executing its own OS 1035-2 and binary / library 1040-2, and instructions 920-2 implementing another manager entity 940. Compared to standalone implementation 1010, virtualization allows multiple virtual machines (VMs) to run on the circuitry (such as the CPU (Central Processing Unit)) of a single physical server. Virtualization allows applications (in this case, two manager entities 940 running as part of instructions 920-1 and 920-2 respectively) to be isolated between VMs 1030 and provides a certain level of security because information from one application cannot be freely accessed by another. Virtualization allows for better utilization of resources in the physical server and allows for better scalability because applications can be easily added or updated. Each VM is a complete software-based machine that runs all components (including its own operating system) on top of circuit 1010-2.
[0085] Container implementation 1003 is a further improvement and includes circuitry 1010-3, OS 1015, container runtime 1043, and container 1045. Container 1045 contains binaries / libraries 1015 and instructions 920 for manager entity 940. Container 1045 is similar to VM 1030 but has looser isolation features to share the operating system (OS) 1015 between applications. Similar to VM 1030, container 1045 has its own file system, sharing resources such as CPU, memory, process space, etc., with circuitry 1010-3. Because containers 1045 are decoupled from the underlying infrastructure, they are portable across clouds and OS distributions. Corresponding to this application, in this example, one or more manager entities 940 run on container 1045.
[0086] Container implementation 1003 offers many advantages over both implementations 1001 and 1002. For example, applications (e.g., manager entity 940) can be developed for the container runtime 1043, and this is not only independent of OS 1015, but also supports many different OS 1015 implementations. Figure 10 In the examples, OS 1015 used for implementations 1001 and 1002, and OS 1035 used for VM 1030, can all be the same OS. Another benefit is that application container images can be created at build / release time rather than deployment time, thus decoupling the application from the infrastructure. Multiple instances of the manager entity 940 can be created and used based on the container image, and the number of instances can be changed based on various criteria (e.g., in real-time).
[0087] Although virtualization implementation 1002 and container implementation 1003 are less "touchable" in determining the physical "box" assigned to execute the corresponding manager entity 940, each manager entity 940 has a direct relationship with its corresponding manager entity 940 via circuit 1010-2 or circuit 1010-3. That is, for circuits 1010-1, 1010-2, and 1010-3 that can use different processors, memories, and other circuits, and even for different instructions 920 used by the manager entity 940, the manager entity 940 is executed by physical circuits 1010-1, 1010-2, and 1010-3, and the processors or other circuits are not strictly software.
[0088] There can be a mixture of implementations 1001, 1002, and 1003 for the implementation manager entity 940. For example, VM 1030-1 can be implemented such that it runs container implementation 1003, except for circuit 1010-3 (whose functionality is performed by the VM). That is, VM 1030-1 will run elements 1015, 1043, and 1045 (including elements 1050 and 920).
[0089] Without limiting the scope, interpretation, or application of the claims below in any way, the technical effects and / or advantages of one or more exemplary embodiments disclosed herein are: reduced complexity of the model (and implementation). Another technical effect and / or advantage of one or more exemplary embodiments disclosed herein is reduced computational requirements of the management system, resulting in reduced energy consumption.
[0090] Here are some other examples.
[0091] Example 1. A method comprising: a manager entity in a wireless network performing operations including: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving a value of an attribute representing a group to which the managed entity participates; navigating to the group using at least the attribute; retrieving a reference to information associated with the group; navigating to the information associated with the group based at least on the reference; and obtaining the information associated with the group.
[0092] Example 2. The method described in Example 1, wherein the managed entity is represented by an object whose category is derived from TopX.
[0093] Example 3. The method described in Example 1 or 2, wherein the managed entity is represented by an object instantiated from the ManagedElement class, or by an object instantiated from a class derived from the ManagedFunction class.
[0094] Example 4. The method according to any one of Examples 1 to 3, wherein the group is identified by the group’s proprietary name (DN).
[0095] Example 5. The method according to any one of Examples 1 to 4, wherein the information associated with the group is related to one or more energy supplies.
[0096] Example 6. The method according to any one of Examples 1 to 4, wherein the information associated with the group is related to energy-related information.
[0097] Example 7. According to the method of Example 6, the energy-related information includes one or more of the following: energy consumption, renewable energy information, or carbon emission information.
[0098] Example 8. The method according to any one of Examples 1 to 7, wherein the group includes one or more other managed entities corresponding to other network resources in the wireless network.
[0099] Example 9. An apparatus comprising components for performing operations by a manager entity in a wireless network, including: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving a value of an attribute representing a group to which the managed entity participates; navigating to the group using at least the attribute; retrieving a reference to information associated with the group; navigating to the information associated with the group based at least on the reference; and acquiring the information associated with the group.
[0100] Example 10. The apparatus according to Example 9, wherein the managed entity is represented by an object whose category is derived from TopX.
[0101] Example 11. The apparatus according to Example 9 or 10, wherein the managed entity is represented by an object instantiated from the ManagedElement class, or by an object instantiated from a class derived from the ManagedFunction class.
[0102] Example 12. The apparatus according to any one of Examples 9 to 11, wherein the group is identified by the group’s proprietary name (DN).
[0103] Example 13. The apparatus according to any one of Examples 9 to 12, wherein the information associated with the group is related to one or more energy supplies.
[0104] Example 14. The apparatus according to any one of Examples 9 to 12, wherein the information associated with the group is related to energy-related information.
[0105] Example 15. The apparatus according to Example 14, wherein the energy-related information includes one or more of the following: energy consumption, renewable energy information, or carbon emission information.
[0106] Example 16. An apparatus according to any one of Examples 9 to 15, wherein the group includes one or more other managed entities corresponding to other network resources in the wireless network.
[0107] Example 17. An apparatus comprising: one or more processors; and one or more memories storing instructions that, when executed by the one or more processors, cause the apparatus to perform at least the following operations by a manager entity in a wireless network: identifying a managed entity, wherein the managed entity corresponds to a network resource in the wireless network; retrieving a value of an attribute representing a group to which the managed entity participates; navigating to the group using at least the attribute; retrieving a reference to information associated with the group; navigating to the information associated with the group based at least on the reference; and obtaining the information associated with the group.
[0108] Example 18. The apparatus according to Example 17, wherein the managed entity is represented by an object whose category is derived from TopX.
[0109] Example 19. The apparatus according to Example 17 or 18, wherein the managed entity is represented by an object instantiated from the ManagedElement class, or by an object instantiated from a class derived from the ManagedFunction class.
[0110] Example 20. An apparatus according to any one of Examples 17 to 19, wherein the group is identified by a proprietary name (DN) of the group.
[0111] Example 21. The apparatus according to any one of Examples 17 to 20, wherein the information associated with the group is related to one or more energy supplies.
[0112] Example 22. The apparatus according to any one of Examples 17 to 20, wherein the information associated with the group is related to energy-related information.
[0113] Example 23. The apparatus according to Example 22, wherein the energy-related information includes one or more of the following: energy consumption, renewable energy information, or carbon emission information.
[0114] Example 24. An apparatus according to any one of Examples 17 to 23, wherein the group includes one or more other managed entities corresponding to other network resources in the wireless network.
[0115] Example 25. A computer program comprising instructions that, when executed by a device, cause the device to perform the method described in any one of Examples 1 to 8.
[0116] Example 26. A computer program according to Example 25, wherein the computer program is a computer program product including a computer-readable medium carrying instructions implemented therein for use with the device.
[0117] Example 27. A computer program according to Example 25, wherein the computer program can be directly loaded into the internal memory of the device.
[0118] As used in this application, the term "circuit" may refer to one or more of the following: (a) Hardware circuit implementation only (such as implementations in analog, digital, and / or quantum circuits), and (b) A combination of hardware circuitry and software, such as (if applicable): (i) a combination of (multiple) analog, digital, and / or quantum hardware circuitry with software / firmware, and (ii) any or all portions of (multiple) hardware processors (including (multiple) digital and / or quantum processors) and (multiple) memories having software, which work together to enable a device (such as a mobile device, computing device, or server) to perform various functions, and (c) Any or all portions of the hardware circuitry (such as the microprocessors, processors and / or quantum processors) required for operation of the software (e.g., firmware), but the software may not exist if it is not required for operation.
[0119] This definition of "circuit" applies to all uses of the term in this application (including any claims). As another example, as used in this application, the term "circuit" also covers only hardware circuitry or a processor (or multiple processors) or a portion thereof, and its (or their) accompanying software and / or firmware implementations. For example, and if applicable to a particular claim element, the term "circuit" also covers baseband integrated circuits or processor integrated circuits for mobile devices or similar integrated circuits in servers, cellular network devices, or other computing or networking devices.
[0120] In the example embodiments, software as used herein (e.g., application logic, instruction set) is maintained on any of a variety of conventional computer-readable media. In the context of this document, "computer-readable media" can be any medium or component that can contain, store, communicate, propagate, or transmit instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer), wherein an example of a computer is, for example, in… Figure 9The computer-readable medium may include computer-readable storage media (e.g., memory 15, memory 75, memory 95, and circuitry 1010 or other devices), which may be any medium or component that can contain, store, and / or transmit instructions for use by or in conjunction with an instruction execution system, apparatus, or device (such as a computer). Computer-readable storage media do not include propagating signals and can therefore be considered non-transitory. As used herein, the term "non-transitory" is a limitation of the medium itself (i.e., tangible, not signaling), not a limitation of the persistence of data storage (e.g., RAM (random access memory) versus ROM (read-only memory)).
[0121] If necessary, the different functions discussed in this article may be executed in different orders and / or simultaneously with each other. Furthermore, if necessary, one or more of the above functions may be optional or may be combined.
[0122] Although various aspects of the invention are set forth in the independent claims, other aspects of the invention include other combinations of features from the described embodiments and / or dependent claims with features of the independent claims, and not only combinations expressly set forth in the claims.
[0123] This document also notes that while exemplary embodiments of the invention have been described above, these descriptions should not be construed as limiting. Rather, various changes and modifications may be made without departing from the scope of the invention as defined in the appended claims.
[0124] The following abbreviations, which can be found in the instruction manual and / or accompanying drawings, are defined as follows: 3GP Third Generation Partner Program 5G fifth generation AMF access and mobility management functions API Application Programming Interface CR Change Request DN proprietary name EIFE Energy Information Function E-SML Evolutionary Service Mobile Location Center eNB (or eNodeB) evolved Node B (e.g., LTE base station) GMLC Gateway Mobile Location Center gNB (or gNodeB) for 5G / NR base stations IOC Information Object Class I / F interface LMF location management function LTE Long Term Evolution MME Mobility Management Entity MO managed objects MOI Managed Object Instances NF Network Functions ng or NG next generation NR New Radio NRF Network Repository Functionality NRM Network Resource Model N / W or NW network MO managed objects MOI Managed Object Instances OAM Operation, Management and Maintenance OPEX operating expenses RAN Radio Access Network RDN related special names Rel version Rx receiver SGW Service Gateway SMF Session Management Function TRP Transmitter / Receiver Point Tx Transmitter UDM Unified Data Management UDR Unified Data Storage UE (User Equipment) (e.g., wireless, typically mobile devices) UPF User Plane Functions
Claims
1. A communication apparatus comprising components for: The following operations are performed by the manager entity in the wireless network: Identify managed entities, wherein the managed entities correspond to network resources in the wireless network; Retrieve the value of the attribute representing the group to which the managed entity participates; Navigate to the group using at least the aforementioned attributes; Retrieve references to information associated with the group; Navigation to the information associated with the group is based at least on the reference; and Obtain the information associated with the group.
2. The apparatus of claim 1, wherein the managed entity is represented by an object, the category of which is derived from TopX.
3. The apparatus of claim 1 or 2, wherein the managed entity is represented by an object instantiated from the ManagedElement class, or by an object instantiated from a class derived from the ManagedFunction class.
4. The apparatus according to claim 1 or 2, wherein the group is identified by the group’s proprietary name (DN).
5. The apparatus of claim 1 or 2, wherein the information associated with the group is related to one or more energy supplies.
6. The apparatus of claim 1 or 2, wherein the information associated with the group is related to energy-related information.
7. The apparatus of claim 6, wherein the energy-related information includes one or more of the following: energy consumption, renewable energy information, or carbon emission information.
8. The apparatus of claim 1 or 2, wherein the group includes one or more other managed entities corresponding to other network resources in the wireless network.
9. A device for communication, comprising: One or more processors; as well as One or more memories storing instructions that, when executed by the one or more processors, cause the device to perform at least the following: The following operations are performed by the manager entity in the wireless network: Identify managed entities, wherein the managed entities correspond to network resources in the wireless network; Retrieve the value of the attribute representing the group to which the managed entity participates; Navigate to the group using at least the aforementioned attributes; Retrieve references to information associated with the group; Navigation to the information associated with the group is based at least on the reference; and Obtain the information associated with the group.
10. The apparatus of claim 9, wherein the managed entity is represented by an object, the category of which is derived from TopX.