Multi-solution cloud-based reporting of infrastructure management service performance monitoring data

Abstract

An apparatus includes an infrastructure management service (IMS), the IMS configured to collect performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, node clusters. The IMS is further configured to exchange data about data reporting methods with an IMS consumer. The IMS coordinates with the IMS consumer to select a selected data reporting method from the data reporting methods. The IMS configures the IMS to implement the selected data reporting method. The IMS transmits the PM data to the IMS consumer according to the selected data reporting method.

Description

Attorney Docket No. RAKU-12101 Title: Multi-Solution Cloud-Based Reporting of Infrastructure Management Service Performance Monitoring DataCROSS-REFERENCE TO RELATED APPLICATION

[0001] This application claims priority to U.S Provisional Application Serial No.63 / 749,266 filed January 24, 2025; the entire contents of which are incorporated herein by reference.FIELD

[0002] The present disclosure relates to multi -solution cloud-based reporting of infrastructure management service performance monitoring data.BACKGROUND

[0003] The information disclosed in this background section is only for enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0004] The open radio access network (0-RAN) standards are non-proprietary standards used to implement hardware and software in a cellular communication network. One aspect of the 0-RAN standards is a service management and orchestration (SMO) framework for implementing back-end software for managing a cellular communication network. The 0-RAN 02 interface is a component that provides an interface between the SMO framework and an infrastructure management (O-Cloud) framework for supportingAttorney Docket No. RAKU-12101 virtual network functions of an O-RAN network. In particular, the 02 interface enables infrastructure management service (IMS) performance measurement (PM) in order to measure and report the performance of components of a cellular communication network. SUMMARY

[0005] In one aspect, an apparatus includes an infrastructure management service (IMS), the IMS configured to collect performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, node clusters. The IMS is further configured to exchange data about data reporting methods with an IMS consumer. The IMS coordinates with the IMS consumer to select a selected data reporting method from the data reporting methods. The IMS configures the IMS to implement the selected data reporting method. The IMS transmits the PM data to the IMS consumer according to the selected data reporting method.

[0006] In another aspect, a method includes collecting, by an infrastructure management service (IMS), performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters. The IMS exchanges data about data reporting methods with an IMS consumer. The IMS coordinates with the IMS consumer to select a selected data reporting method from the data reporting methods. The IMS configures the IMS to implement the selected data reporting method. The IMS transmits the PM data to the IMS consumer according to the selected data reporting method.

[0007] In another aspect, a non-transitory computer readable medium, when executed by a system, causes the system to collect, by an infrastructure management service (IMS) inAttorney Docket No. RAKU-12101 the system, performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters. The IMS exchanges data about data reporting methods with an IMS consumer. The IMS coordinates with the IMS consumer to select a selected data reporting method from the data reporting methods. The IMS configures the IMS to implement the selected data reporting method. The IMS transmits the PM data according to the selected data reporting method.BRIEF DESCRIPTION OF THE DRAWINGS

[0008] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0009] Fig. 1 is a schematic block diagram illustrating a cellular communication network in accordance with an embodiment;

[0010] Fig. 2 is a schematic block diagram illustrating the flow of information between an O-cloud, IMS, and a consumer of IMS data in accordance with an embodiment;

[0011] Fig. 3 is a process flow diagram of a method for setting up the exchange of IMS PM data in accordance with an embodiment;

[0012] Fig. 4 is a schematic block diagram illustrating scalable WEBSOCKET based solution for 02-IMS PM reporting in accordance with an embodiment;

[0013] Fig. 5 is a schematic block diagram illustrating scalable HTTP or PROMETHEUS based solution for 02-IMS PM reporting in accordance with an embodiment;

[0014] Fig. 6 is a schematic block diagram illustrating scalable KAFKA based 02-IMS PM reporting in accordance with an embodiment;Attorney Docket No. RAKU-12101

[0015] Fig. 7 is a process flow diagram of a method for PM reporting in accordance with an embodiment;

[0016] Fig. 8 is a schematic block diagram of an example computing device suitable for implementing methods in accordance with embodiments of the disclosure DETAILED DESCRIPTION

[0017] The following detailed description of example embodiments refers to the accompanying drawings. The present disclosure provides illustrations and descriptions, but is not intended to be exhaustive or to limit the implementations to the precise form disclosed. Modifications and variations are possible in light of the present disclosure or may be acquired from practice of the implementations. Further, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, the flowchart and description of operations provided below relate to at least one of the embodiments in the present disclosure. It should be noted that it is possible to make other embodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

[0018] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, software, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods should not limit their implementations. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code. It is understood that software and hardware may be designed to implementAttorney Docket No. RAKU-12101 the systems and / or methods based on the description herein.

[0019] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, the particular combinations are not intended to limit the disclosure of implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Even if a dependent claim directly depends on only one claim, the present disclosure may indicate that the dependent claim is dependent on other claims in the claim set.

[0020] No element, act, or instruction used herein should be construed as critical or essential unless explicitly described as such. Also, as used herein, the articles “a” and “an” (in other words, nouns not mentioned in the plural) are intended to include one or more items, and may be used interchangeably with “one or more.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and [B],” “[A] and / or [B],” or “at least one of [A] or [B]” are to be understood as including only A, only B, or both A and B.

[0021] Referring to Fig. 1, in a cellular communication system 100 user equipment (UE) 102 transmits wireless signals to one or more antennas 104 coupled to a radio unit (RU) 106 configured to manage generated signals to be transmitted over the antenna 104 and to detect signals received by the antenna 104. The RU 106 may be implemented as a gNodeB (gNB) in a fifth generation (5G) network, sixth generation network (6G) (e.g., a 6NB), or other type of network. The data transmitted to the UE 102 and received from the UE 102 as well as managing a logical connection with the UE 102 according to a cellularAttorney Docket No. RAKU-12101 communication protocol may be managed by a distributed unit (DU) 108 coupled to the RU 106. Each DU 108 may be in data communication with a central unit (CU) 112. The CU 112 may perform functions that require coordination among DUs 108 such as performing handoffs of connections to UE 102 between RU 106.

[0022] Some or all of the RU 106, DU 108, and CU 112 may be connected to a service management and orchestration (SMO) platform 114. The SMO platform 114 may gather data reported by the RU 106, DU 108, or CU 112, such as performance data. The SMO platform 114 may further control operation of one or more of the RU 106, DU 108, or CU 112. The SMO platform 114 may gather data reported by the UE 102, such as by way of the RU 106, DU 108, and / or CU 112.

[0023] The SMO platform 114 may manage one or more open radio access network (O-RAN) cloud computing platforms (“O-cloud 116”). There may be any number of O-clouds 116 in a cellular communication system 100 and be managed by the SMO platform 114. An O-cloud 116 may itself be implemented on a general-purpose cloud computing platform, e g., AMAZON Web Services (AWS), MICROSOFT AZURE, GOOGLE CLOUD, or the like.

[0024] Each O-cloud 116 and / or the general-purpose cloud computing platform may have different capacity, whether in terms of throughput of a network connection to the cloud computing platform, services, data transport protocols, data serialization techniques, data compression algorithms, data transport techniques, and computing resources (e.g., processing, memory, storage, etc.).

[0025] Referring to Fig. 2, an O-cloud 116 may be incorporated into a reporting service 200 that collects, processes, and distributes PM data to various applications in order toAttorney Docket No. RAKU-12101 monitor the cellular communication system 100. A consumer 202 of the PM data may be SMO functions (SMOF), SMO services (SMOS), or rApps. The consumer 202 may include a federated O-cloud orchestration and management (FOCOM) system (hereinafter simply “FOCOM”) that interfaces with an infrastructure management service (IMS) 204 of the O-cloud 116 through an 02 interface.

[0026] In some embodiments, the IMS 204 implements a performance subscription manager 206. The FOCOM may transmit subscription requests 208 to the performance subscription manager 206, which will create a corresponding subscription 210. The subscription requests 208 and subscriptions 210 may describe a type of data to be transmitted to the subscribing SMOF, e.g., a particular metric, data relating to a particular piece of O-Cloud resource (e.g., server node, network equipment, accelerator, and / or node cluster), a type of equipment, equipment in a particular geographic region, or other subdivision of the cellular communication system.

[0027] PM data received from the O-Cloud 116 and matching a subscription 210 may be transmitted by the IMS 204 to the FOCOM that requested the subscription 210, such as in the form of a measurement report 212.

[0028] The O-Cloud 116 itself may include a plurality of O-Cloud resources 214 (e.g., server node, network equipment, accelerator, and / or node cluster). The O-Cloud may process the O-Cloud resources 214 to obtain measurements 216, such as PM data. The measurements may be processed by PM jobs 218 to obtain PM data, which may be stored in a database 220. The IMS 204 may fetch data from the database 220 relating to subscriptions 210 and transmit measurement reports 212 including the fetched data to the FOCOM that invoked creation of the subscriptions 210.Attorney Docket No. RAKU-12101

[0029] In typical implementations, massive amounts of data must move from the O-Cloud to the consumer 202. This data movement must be performed with high availability, resiliency, and fault protection inasmuch as failures can affect operation of the cellular communication system 100.

[0030] Referring to Fig. 3, the IMS consumer 202 (e.g., FOCOM) and IMS 204 may, for example, exchange measurement requirements at step 302. Step 302 may include the FOCOM specifying a resource, resource types to be measured, a measurement selection criteria, a measurement report format, and / or a measurement reporting frequency. Step 302 may be part of transmitting a subscription request 208.

[0031] The method 300 may include exchanging, at step 304, supported data reporting methods, e.g., the IMS 204 transmitting reporting methods that the IMS 204 supports to the FOCOM and / or the FOCOM transmitting the data reporting methods that the FOCOM supports to the IMS 204. In the examples disclosed herein, data reporting methods may include the use of WEBSOCKETS (see Fig. 4 and corresponding description), hypertext transfer protocol (HTTP) (see Fig. 5 and corresponding description), and KAFKA (see Fig.6 and corresponding description). These are exemplary only and other data reporting methods may be used, such as PROMETHEUS, file transfer protocol (FTP), or the like. The data reporting methods supported by the IMS and FOCOM may correspond to available software, available computing resources (e.g., some reporting methods may require more resources), available network throughput (e.g., some reporting methods may require more network throughput than others), or other attribute of the IMS 204, FOCOM, and / or a cloud computing platform hosting the FOCOM and / or IMS 204.

[0032] The method may include selecting, at step 306, a data reporting method. ForAttorney Docket No. RAKU-12101 example, the IMS 204 and FOCOM may coordinate with one another, e.g., negotiate, to select a data reporting method. For example, the IMS 204 and FOCOM may identify a set of data reporting methods that are included in the data reporting methods reported by both of the IMS 204 and FOCOM at step 304. Where the set of data reporting methods includes more than one data reporting methods, step 306 may include selecting a selected data reporting method from among the set of data reporting methods, such as the data reporting method having the highest ranking. For example, data reporting methods may have the following ranking (most desirable listed first): KAFKA, HTTP, WEBSOCKET. Where the set only includes one data reporting method, that data reporting method is used.

[0033] In one example, the IMS 204 and the FOCOM support all data reporting methods such that selection at step 306 is performed. In another example, both the IMS 204 and the FOCOM support a common fallback option (e.g. HTTP notification) to guarantee compatibility while other options (e.g. KAFKA, WEB SOCKET) are choices for better performance in certain deployment scenarios.

[0034] The method 300 may include performing, at step 308, configuration relating to the selected data reporting method. Where the selected data reporting method is WEBSOCKET, the configuration may include setting up a WEBSOCKET server endpoint. Where the selected data reporting method is HTTP (e.g., HTTP 1.0 / 2.0 Polling), the configuration may include setting up a polling endpoint, setting up a callback uniform resource identifier (URI), and possibly performing other configuration steps. Where the selected data reporting method is KAFKA, configuration may include setting up a KAFKA broker, assigning a URI to the KAFKA broker, and possibly performing other configuration steps.Attorney Docket No. RAKU-12101

[0035] The method 300 may further include selecting, at step 310, one or more parameters defining data exchange between the IMS 204 and FOCOM. For example, step 310 may include the IMS 204 and FOCOM coordinating, e.g., negotiating, to select some or all of a serialization method, a compression algorithm, and / or other parameters.

[0036] There are various industry solutions for serialization and compression. Serialization formats include PROMETHEUS (open-source event monitoring and reporting software), open-source remote procedure call (gRPC), JavaScript Object Notation (JSON), extensible markup language (XML), abstract syntax notation one (ASN.l). Compression algorithms include Zstandard (zstd), gzip, lz4, and snappy. Certain formats are used in the cloud for data reporting depending on deployment scenarios and vendors’ or operators’ design choices and compatibility requirement to existing data framework.

[0037] Similar to the data reporting method, serialisation format and compression algorithm may be standardized for a PM data reporting service with the following considerations: meeting the functional and performance requirements of the O-Cloud 116; providing compatibility to existing industry implementations; and providing interoperability among vendors. Using the approach described herein, multiple data reporting methods, serialization formats, and compression algorithms may be supported.

[0038] Following execution of the method 300, the IMS 204 and FOCOM may perform transfer of PM data from an IMS producer (e.g., one or more nodes of the O-cloud 116) to the IMS consumer 202 (e g., FOCOM).

[0039] Fig. 4 illustrates an example configuration in which the selected data reporting method is WEBSOCKET. In the illustrated embodiment, the IMS producer is one or moreAttorney Docket No. RAKU-12101 nodes of an O-Cloud 116 and the IMS consumer 202 is a SMOF 400 of the FOCOM. The IMS 204 implements a plurality of WEBSOCKET clients 402. The WEBSOCKET clients 402 establish connections to FOCOM server nodes, e.g., WEBSOCKET server nodes 404 that are persistent and dedicated to transfer of data from the WEBSOCKET clients 402. The WEBSOCKET clients 402 may also optionally connect to high-availability WEB SOCKET server nodes 406. The high-availability WEB SOCKET server nodes 406 may be instantiated or de-instantiated on demand according to the amount of traffic generated by the WEB SOCKET clients. The PM data traffic load from the O-Cloud 116 can easily exceed the capacity of a single WEBSOCKET server node 406. Likewise, new nodes of the O-Cloud 116 may be added dynamically, which will increase PM data traffic load.

[0040] Scaling the number of WEBSOCKET server nodes 406 enables the combined capacity of the WEB SOCKET server nodes 404, 406 to match increases and decreases in demand from nodes of the O-Cloud 116 and corresponding increases in the number of WEBSOCKET connections to the WEB SOCKET server nodes 404, 406. In some embodiments the high-availability server nodes 406 implement backup connections that reduce downtime. The multiple WEB SOCKET server nodes 404, 406 are more resilient to failure of a single WEBSOCKET server node 404, 406. Eliminating a single point of failure is helpful inasmuch as failure could impact service significantly, such as for an entire city.

[0041] The FOCOM may include a WEB SOCKET load balancer 408 that routes connection requests from the WEB SOCKET clients to the WEB SOCKET server nodes 404, 406 according to a load balancing algorithm. The WEBSOCKET load balancer 408Attorney Docket No. RAKU-12101 distributes connections to balance loading on each WEB SOCKET server node 404, 406. Once a connection is established with a particular WEBSOCKET server node 404, 406, the connection remains persistent with that WEBSOCKET server node 404, 406.

[0042] The IMS 204 may setup one or more persistent WEB SOCKET connections to the SMOF 400 using the WEBSOCKET clients 402 and WEBSOCKET server nodes 406 and stream PM data to the SMOF 400 via the persistent WEB SOCKET connections.

[0043] PM data received by a WEB SOCKET server node 404, 406 may be transmitted to a message broker 410 of the FOCOM. The message broker 410 may act as a middleware layer that decouples the front-end WEB SOCKET server nodes 406, 406 from backend services (e.g., one or more SMOF 400) so that each backend service can see data from all independent WEB SOCKET server nodes 404, 406. The message broker 410 further facilitates routing of data to backend services independent of data routing among the frontend WEB SOCKET server nodes 404, 406. The message broker 410 may operate independent of the protocol used to transfer data between the WEB SOCKET clients 402 and the WEB SOCKET server nodes 404, 406. Likewise, scaling of the message broker 410 may be performed independently of scaling of the WEBSOCKET server nodes 406.

[0044] Fig. 6 illustrates an example configuration in which the selected data reporting method is HTTP, such as HTTP polling according to HTTP 1.0, HTTP 2.0, or other version. In the illustrated embodiment the IMS 204 implements a plurality of PM data reporting workloads 500. The PM data reporting workloads 500 establish connections to HTTP server nodes 502, e.g., HTTP server nodes 502 that are persistent and dedicated to transfer of data from the PM data reporting workloads 500. The PM data reporting workloads 500 may optionally connect to high-availability HTTP server nodes 504. TheAttorney Docket No. RAKU-12101 high-availability HTTP server nodes 504 may be instantiated or de-instantiated on demand according to the amount of traffic generated by the PM data reporting workloads 500. The PM data traffic load from the O-Cloud 116 can easily exceed the capacity of a single HTTP server node 504. Likewise, new nodes of the O-Cloud 116 may be added dynamically, which will increase PM data traffic load.

[0045] Scaling the number of HTTP server nodes 504 enables the combined capacity of the HTTP server nodes 502, 504 to match increases and decreases in demand from nodes of the O-Cloud 116 and corresponding increases in the number of HTTP traffic to the HTTP server nodes 502, 504. The multiple HTTP server nodes 502, 504 are more resilient to failure of a single HTTP server node 502, 504. Eliminating a single point of failure is helpful inasmuch as failure could impact service significantly, such as for an entire city.

[0046] The FOCOM may include a HTTP load balancer 506 that routes HTTP traffic to the HTTP server nodes 502, 504 and response traffic from the HTTP server nodes 502, 504 according to a load balancing algorithm. The load balancer distributes traffic to balance loading on each HTTP server node 502, 504. Since HTTP is a connectionless protocol, no persistent connections between PM reporting workloads and HTTP server nodes 502, 504 may are created in some embodiments. The HTTP load balancer 506 may be a high-availability load balancer, e.g., with one or more redundant instances to reduce outages due to server crashes, network issues, data center outages, or other issues. Multiple HTTP load balancers 506 (e.g., 4 to 7) may be active simultaneously with traffic being balanced between them.

[0047] The PM data reporting workloads 500 of the IMS 204 may transmit PM data to theAttorney Docket No. RAKU-12101 SMOF 400 in the form of HTTP POST requests (push delivery) or HTTP GET responses (polling), in either case without maintaining a persistent connection.

[0048] PM data received by an HTTP server node 502, 504 may be transmitted to the message broker 410 of the FOCOM. The message broker 410 may act as a middleware layer that decouples the front-end HTTP server nodes 502, 504 from backend services (e.g., one or more SMOF 400) so that each backend service can see data from all independent HTTP server nodes 502, 504. The message broker 410 further facilitates routing of data to backend services independent of data routing among the front-end HTTP server nodes 502, 504. The message broker 410 may operate independent of the protocol used to transfer data between the PM data reporting workloads 500 and the HTTP server nodes 502, 504. Likewise, scaling of the message broker 410 may be performed independently of scaling of the HTTP server nodes 504.

[0049] Fig. 6 illustrates an example configuration in which the selected data reporting method is KAFKA, e.g., a distributed streaming platform for implementing real-time data feeds and high-performance data pipelines. In the approach of Fig. 6, the FOCOM may be implemented as a cluster 600 of message broker server nodes 602, such as a KAFKA cluster of KAFKA message broker server nodes.

[0050] In the approach of Fig. 6, PM reporting workloads 604 of the IMS 204 send messages containing PM data to the cluster 600 according to a streaming protocol implemented by the cluster 600, such as a KAFKA protocol . The cluster 600 and message broker server nodes 602 implement a framework for routing PM data to a SMOF 400 addressed by the data. The cluster 600 and message broker server nodes 602 may perform tasks such as some or all of ensuring successful delivery of messages, load balancingAttorney Docket No. RAKU-12101 among the server nodes 602, data replication for fault tolerance, and autoscaling of the number of message broker server nodes.

[0051] As apparent from the description of Figs. 3 to 6, the approach described herein provides a service-based solution supporting the flexible selection of data reporting method. The solution is abstracted and technology agnostic and can support any data reporting mechanism or technology. The approach described herein provides a scalable and resilient data transport architecture that implements a service-based solution using different data reporting technologies (WEB SOCKET, HTTP, KAFKA, PROMETHEUS, FTP, etc ).

[0052] Referring to Fig. 7, a method 700 may include collecting, at step 702, by an infrastructure management service (IMS), performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters. The method 700 includes exchanging, at step 704, by the IMS 204, data about data reporting methods with an IMS consumer. The method 700 includes coordinating, at step 706, by the IMS, with the IMS consumer to select a selected data reporting method from the data reporting methods. The method 700 includes configuring, by the IMS, at step 708, the IMS to implement the selected data reporting method. The method 700 includes transmitting, at step 710, the PM data to the IMS consumer according to the selected data reporting method.

[0053] The approach described above enables massive amounts of data movement from O-Cloud 116 to the SMOF with high availability, strong resiliency, and fault protection. The approach described above enables dynamic scaling and load balancing; efficient, high throughput, highly scalable, and fault-tolerant data streaming framework is needed for sharing data between cloud native network functions and management system.Attorney Docket No. RAKU-12101

[0054] In addition, the approach described above supports a wide variety of solutions in terms of data reporting method, serialization method, and compression algorithm. The solutions implemented may be adapted using the method 300 to suit a given deployment environment, the scale of data transfer needed, and data reporting methods and data formats supported by an operator’s existing data lake. Using the approach described herein the 02-IMS standard is made flexible for vendors and operators to choose their own preferable transport mechanism for PM data reporting.

[0055] Fig. 8 illustrates an embodiment of a computing device 800 that may be used to implement any of the components described above. As shown in Fig. 8, the device 800 includes processor 810, a memory 820, a storage component 830, an input component 840, an output component 850, a communication interface 860, and a bus 870.

[0056] The processor 810, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 810 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 810 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an applicationspecific integrated circuit (ASIC), or another type of processing component.

[0057] Memory 820 includes a non-transitory computer readable medium. Memory 820 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 810. The memory 820 comprises machine-readable instructions which are executable by theAttorney Docket No. RAKU-12101 processor 810. These machine-readable instructions when executed by the processor 810 cause the processor 810 to perform one or more method steps of an embodiment described above.

[0058] Storage component 830 stores information and / or software related to the operation and use of the device 800. For example, storage component 830 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0059] Input component 840 is configured to receive information, such as user input. For example, the input component 840 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 840 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0060] Output component 850 is configured to provide output information from the device 800. For example, the output component 850 may be, but not limited to, a display, a speaker, instructions to an external device, and / or one or more light-emitting diodes (LEDs).

[0061] Communication interface 860 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 860 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or anAttorney Docket No. RAKU-12101 indirect connection via a communication network that exists between the device 800 and other devices. In other words, the standard of the communication interface 860 is not limited.

[0062] The bus 870 acts as an interconnect between the processor 810, the memory 820, the storage component 830, the input component 840, the output component 850, and the communication interface 860 of the device 800. The bus 870 may include a wired interconnection or a wireless interconnection.

[0063] The number and arrangement of components shown in Fig. 8 are provided as an example. In practice, device 800 may include additional components, fewer components, different components, or differently arranged components than those shown in Fig. 8. Additionally, or alternatively, a set of components (e.g., one or more components) of device 800 may perform one or more functions described as being performed by another set of components of device 800. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 800 in communication with one another.

[0064] In a first example embodiment an apparatus includes: an infrastructure management service (IMS), the IMS configured to collect performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, node clusters; wherein the IMS is configured to: exchange data about data reporting methods with an IMS consumer; coordinate with the IMS consumer to select a selected data reporting method from the data reporting methods; configure the IMS to implement the selected data reporting method; and transmit the PM data to the IMS consumer according to the selected data reporting method.Attorney Docket No. RAKU-12101

[0065] In a second example embodiment according to the first example embodiment, the data reporting methods include a connectionless protocol, a persistent connection protocol, and a dynamic streaming protocol.

[0066] In a third example embodiment according to the second example embodiment, the connectionless protocol is hypertext transfer protocol (HTTP), the persistent connection protocol is WEBSOCKET, and the dynamic streaming protocol is KAFKA.

[0067] In a fourth example embodiment according to the first example embodiment, the IMS is further configured to coordinate with the IMS consumer to select a serialization method from a plurality of serialization methods.

[0068] In a fifth example embodiment according to the fourth example embodiment, the plurality of serialization methods include two or more of PROMETHEUS, open-source remote procedure call (gRPC), JavaScript Object Notation (JSON), extensible markup language (XML), abstract syntax notation (ASN.1).

[0069] In a sixth example embodiment according to the first example embodiment, the IMS is further configured to coordinate with the IMS consumer to select a selected compression algorithm from a plurality of compression algorithms.

[0070] In a seventh example embodiment according to the sixth example embodiment, the plurality of compression algorithms include two or more of Zstandard (zstd), gzip, lz4, and snappy.

[0071] In an eight example embodiment according to the first example embodiment, the apparatus further includes the IMS consumer, wherein the IMS and the IMS consumer are further configured to: configure the IMS with a plurality of PM data workloads; configure the IMS consumer with a plurality of servers configured to communicate withAttorney Docket No. RAKU-12101 the plurality of PM data workloads; and configure the IMS consumer with one or more message brokers deployed on the plurality of servers for receiving the PM data from the plurality of PM data workloads.

[0072] In a ninth example embodiment according to the eighth example embodiment, the plurality of servers are configured to establish persistent connections with the plurality of PM data workloads.

[0073] In a tenth example embodiment according to the eighth example embodiment, the plurality of servers are configured to perform connectionless communication with the plurality of PM data workloads.

[0074] In an eleventh example embodiment according to the eighth example embodiment, the IMS consumer is further configured with a load balancer configured to distribute traffic from the plurality of PM data workloads to the plurality of servers.

[0075] In a twelfth example embodiment according to the first example embodiment, the IMS is configured to receive the PM data from an O-Cloud.

[0076] In a thirteenth example embodiment according to the twelfth example embodiment, the apparatus further includes the IMS consumer, wherein the IMS consumer is a service management and orchestration function (SMOF) of a federated O-cloud orchestration and management (FOCOM) system.

[0077] In a fourteenth example embodiment, a method includes: collecting, by an infrastructure management service (IMS), performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters; and performing, by the IMS: exchanging data about data reporting methods with an IMS consumer; coordinating withAttorney Docket No. RAKU-12101 the IMS consumer to select a selected data reporting method from the data reporting methods; configuring the IMS to implement the selected data reporting method; and transmitting the PM data to the IMS consumer according to the selected data reporting method.

[0078] In a fifteenth example embodiment according to the fourteenth example embodiment, the data reporting methods include a connectionless protocol, a persistent connection protocol, and a dynamic streaming protocol.

[0079] In a sixteenth example embodiment according to the fifteenth example embodiment, wherein the connectionless protocol is hypertext transfer protocol (HTTP), the persistent connection protocol is WEBSOCKET, and the dynamic streaming protocol is KAFKA.

[0080] In a seventeenth example embodiment according to the fourteenth example embodiment, the method further includes coordinating, by the IMS, with the IMS consumer, to select a serialization method from a plurality of serialization methods and a compression algorithm from a plurality of compression algorithms.

[0081] In an eighteenth example embodiment according to the fourteenth example embodiment, the method further includes: configuring, by the IMS, the IMS with a plurality of PM data workloads; configuring, by the IMS consumer, the IMS consumer with a plurality of servers configured to communicate with the plurality of PM data workloads; and configuring, by the IMS consumer, the IMS consumer with a message broker configured to transfer the PM data between the plurality of servers and the IMS consumer.Attorney Docket No. RAKU-12101

[0082] In a nineteenth example embodiment according to the fourteenth example embodiment, wherein the IMS receives the PM data from an O-Cloud and the IMS consumer is a service management and orchestration function (SMOF) of a federated O-cloud orchestration and management (FOCOM) system.

[0083] In a twentieth example embodiment, a non-transitory computer readable medium that, when executed by a system, causes the system to: collect, by an infrastructure management service (IMS) in the system, performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters; and perform: exchanging data about data reporting methods with an IMS consumer; coordinating with the IMS consumer to select a selected data reporting method from the data reporting methods; configuring the IMS to implement the selected data reporting method; and transmitting the PM data according to the selected data reporting method.

Claims

Attorney Docket No. RAKU-12101 Claims:

1. An apparatus comprising:an infrastructure management service (IMS), the IMS configured to collect performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, node clusters;wherein the IMS is configured to:exchange data about data reporting methods with an IMS consumer; coordinate with the IMS consumer to select a selected data reporting method from the data reporting methods;configure the IMS to implement the selected data reporting method; and transmit the PM data to the IMS consumer according to the selected data reporting method.

2. The apparatus of claim 1, wherein the data reporting methods include a connectionless protocol, a persistent connection protocol, and a dynamic streaming protocol.

3. The apparatus of claim 2, wherein the connectionless protocol is hypertext transfer protocol (HTTP), the persistent connection protocol is WEBSOCKET, and the dynamic streaming protocol is KAFKA.Attorney Docket No. RAKU-12101 4. The apparatus of claim 1, wherein the IMS is further configured to coordinate with the IMS consumer to select a serialization method from a plurality of serialization methods.

5. The apparatus of claim 4, wherein the plurality of serialization methods include two or more of PROMETHEUS, open-source remote procedure call (gRPC), JavaScript Object Notation (JSON), extensible markup language (XML), abstract syntax notation (ASN.l).

6. The apparatus of claim 1, wherein the IMS is further configured to coordinate with the IMS consumer to select a selected compression algorithm from a plurality of compression algorithms.

7. The apparatus of claim 6, wherein the plurality of compression algorithms include two or more of / standard (zstd), gzip, lz4, and snappy.

8. The apparatus of claim 1, further comprising the IMS consumer, wherein the IMS and the IMS consumer are further configured to:configure the IMS with a plurality of PM data workloads;configure the IMS consumer with a plurality of servers configured to communicate with the plurality of PM data workloads; andconfigure the IMS consumer with one or more message brokers deployed on the plurality of servers for receiving the PM data from the plurality of PM data workloads.Attorney Docket No. RAKU-121019. The apparatus of claim 8, wherein the plurality of servers are configured to establish persistent connections with the plurality of PM data workloads.

10. The apparatus of claim 8, wherein the plurality of servers are configured to perform connectionless communication with the plurality of PM data workloads.

11. The apparatus of claim 8, wherein the IMS consumer is further configured with a load balancer configured to distribute traffic from the plurality of PM data workloads to the plurality of servers.

12. The apparatus of claim 1, wherein the IMS is configured to receive the PM data from an O-Cloud.

13. The apparatus of claim 12, further comprising the IMS consumer, wherein the IMS consumer is a service management and orchestration function (SMOF) of a federated O-cloud orchestration and management (FOCOM) system.

14. A method comprising:collecting, by an infrastructure management service (IMS), performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters; andAttorney Docket No. RAKU-12101 performing, by the IMS :exchanging data about data reporting methods with an IMS consumer; coordinating with the IMS consumer to select a selected data reporting method from the data reporting methods;configuring the IMS to implement the selected data reporting method; and transmitting the PM data to the IMS consumer according to the selected data reporting method.

15. The method of claim 14, wherein the data reporting methods include a connectionless protocol, a persistent connection protocol, and a dynamic streaming protocol.

16. The method of claim 15, wherein the connectionless protocol is hypertext transfer protocol (HTTP), the persistent connection protocol is WEBSOCKET, and the dynamic streaming protocol is KAFKA.

17. The method of claim 14, further comprising coordinating, by the IMS, with the IMS consumer, to select a serialization method from a plurality of serialization methods and a compression algorithm from a plurality of compression algorithms.

18. The method of claim 14, further comprising:configuring, by the IMS, the IMS with a plurality of PM data workloads;Attorney Docket No. RAKU-12101 configuring, by the IMS consumer, the IMS consumer with a plurality of servers configured to communicate with the plurality of PM data workloads; and configuring, by the IMS consumer, the IMS consumer with a message broker configured to transfer the PM data between the plurality of servers and the IMS consumer.

19. The method of claim 14, wherein the IMS receives the PM data from an O-Cloud and the IMS consumer is a service management and orchestration function (SMOF) of a federated O-cloud orchestration and management (FOCOM) system.

20. A non-transitory computer readable medium that, when executed by a system, causes the system to:collect, by an infrastructure management service (IMS) in the system, performance measurement (PM) data for a plurality of components, the plurality of components including at least one of server nodes, network equipment, accelerators, and node clusters; andperform:exchanging data about data reporting methods with an IMS consumer; coordinating with the IMS consumer to select a selected data reporting method from the data reporting methods;configuring the IMS to implement the selected data reporting method; and transmitting the PM data according to the selected data reporting method.

Images