Dynamic hash framework for synchronization between network telemetry producers and consumers

Through the telemetry registration framework, the parameters between telemetry producers and consumers are negotiated at runtime, and dynamic synchronization is solved, and the flexibility and efficiency problems caused by static synchronization in the existing technology are solved, and the changes in flexible network resources and data collection requirements are achieved. .

CN118923095APending Publication Date: 2024-11-08CISCO TECHNOLOGY INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380027539.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-16
Filing Date
2023-03-15
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

In the prior art, synchronization between telemetry producers and telemetry consumers is static and cannot be changed dynamically at runtime, resulting in changes in network resource and data collection requirements that require redesign and reconstruction, resulting in economic expenditure and time delays.

Method used

Using the telemetry registration framework, through the telemetry registration controller and database, dynamic synchronization is eliminated, and the need for redesign and reconstruction during the static synchronization process is negotiated at runtime.

Benefits of technology

Achieve flexibility and scalability at runtime, allowing changes in network resource and data collection requirements without redesign, reducing economic expenditure and time delays, and improving flexibility and efficiency of telemetry data consumption.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118923095A_ABST
    Figure CN118923095A_ABST
Patent Text Reader

Abstract

A telemetry producer sends a greeting message to a telemetry registration interface. The interface returns a greeting message. The producer sends the producer protocol group to the interface. The protocol group has been accepted and an indication that the protocol group has been forwarded to the telemetry registration controller is returned. The producer sends a greeting message to the controller. The controller returns an acknowledgement and a producer identifier (ID). The second greeting message and the producer ID are sent from the producer to the controller. The controller returns a second confirmation indicating the producer registration and the producer ID. The telemetry consumer sends a greeting message to the controller. An acknowledgement with a consumer identifier (ID) is returned to the consumer. The consumer sends a consumer request packet to the controller. The controller sends the producer ID and an indication regarding the consumer registration to the consumer.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Patent Application No. 17 / 696,493, filed on March 16, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure generally relates to enabling dynamic synchronization between telemetry producers and consumers at runtime by utilizing a telemetry registry architecture. Background Art

[0004] In computer networks, network telemetry is becoming increasingly important as the amount of network data and the size of networks continue to increase. Network telemetry, the process of collecting measurements and other data from remote network devices (such as switches and routers) and sending these data to another location for analysis, can be used to monitor the health of network devices and accurately and quickly identify any problem areas. Network telemetry enables network operators to proactively locate network blind spots, improve network availability and security, and effectively maintain network operations. Network telemetry can accelerate network troubleshooting, increase network capacity, and improve network performance and user experience.

[0005] Today, data is typically collected and published by telemetry producers from network devices or sent to a centralized message broker. Telemetry consumers then subscribe to or request data from a message broker for processing and analysis. In order for telemetry consumers to subscribe to telemetry data published by telemetry producers, the telemetry producer and telemetry consumer must agree on certain parameters in advance. This agreement or static synchronization between telemetry producers and telemetry consumers is achieved at compile time. Telemetry consumers rely on available telemetry producer documentation to design subscription strategies and hashing mechanisms for telemetry data consumption. Therefore, all telemetry consumers of a given telemetry producer must have the same fixed design that does not allow for scaling, flexibility, or dynamic runtime changes.

[0006] Therefore, to improve network telemetry data consumption, there is a need for a dynamic runtime consensus between telemetry producers and telemetry consumers that allows for greater flexibility, scaling consumption based on user demand, adding more consumers, and runtime changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The detailed description is given below with reference to the accompanying drawings. In the drawings, the leftmost digit of a reference number identifies the drawing in which the reference number first appears. The use of the same reference number in different drawings indicates similar or identical items. The systems shown in the drawings are not drawn to scale, and the components in the drawings may not be drawn to scale with each other.

[0008] Figure 1 A system architecture diagram illustrating an example of a network in which a telemetry registration framework is used to achieve dynamic consensus between telemetry producers and telemetry consumers.

[0009] Figure 2 A detailed view of the telemetry registration framework is shown.

[0010] Figure 3 An example of registering a telemetry producer with the telemetry registration framework is shown.

[0011] Figure 4 An example of registering a telemetry consumer with the telemetry registration framework is shown.

[0012] Figure 5a-5b A flow chart illustrating an example method for registering telemetry producers and telemetry consumers with a telemetry registration framework is shown.

[0013] Figure 6 A computer architecture diagram illustrating an illustrative computer hardware architecture for implementing a telemetry registration framework that can be used to implement various aspects of the various techniques presented herein. DETAILED DESCRIPTION

[0014] Overview

[0015] Various aspects of the invention are set out in the independent claims, preferred features are set out in the dependent claims. Features of one aspect may be applicable to each aspect alone or in combination with other aspects.

[0016] The present disclosure describes techniques for achieving dynamic consensus between telemetry producers and telemetry consumers using a telemetry registration framework. The examples described herein provide a system that includes a processor and a non-transitory computer-readable medium storing instructions that, when executed by the processor, cause the processor to perform operations. The operations include assigning a unique telemetry producer identifier (ID) to a telemetry producer by a telemetry registration controller, registering parameters associated with the telemetry producer with the telemetry registration controller, storing the telemetry producer ID and the parameters associated with the telemetry producer in a telemetry registration database, assigning a unique telemetry consumer ID to a telemetry consumer by the telemetry registration controller, registering parameters associated with the telemetry consumer with the telemetry registration controller, storing the telemetry consumer ID and the parameters associated with the telemetry consumer in the telemetry registration database, determining that the parameters associated with the telemetry producer and the parameters associated with the telemetry consumer are compatible, and requesting telemetry data published by the telemetry producer from a telemetry message broker by the telemetry consumer.

[0017] In some cases, the telemetry registration controller is able to register multiple telemetry producers and multiple telemetry consumers simultaneously.

[0018] According to some embodiments, the telemetry registration controller is a centralized controller with a scale-out architecture.

[0019] In some cases, the telemetry database is a strongly consistent key-value database.

[0020] Some examples described herein provide a system that includes a processor and a non-transitory computer-readable medium storing instructions that, when executed by the processor, cause the processor to perform operations. The operations include registering a telemetry producer with a telemetry registration controller. The registration includes: receiving a first message including a telemetry producer hello message from the telemetry producer by the telemetry registration interface; sending a second message including a telemetry registration interface hello message to the telemetry producer by the telemetry registration interface; receiving a third message including a telemetry producer protocol group from the telemetry producer by the telemetry registration interface; sending the third message to the telemetry registration controller by the telemetry registration interface; sending a fourth message to the telemetry producer by the telemetry registration interface, the fourth message including telemetry acceptance of the producer protocol group and indicating that the telemetry producer protocol group has been forwarded to the telemetry registration controller; receiving a fifth message including the second telemetry producer hello message from the telemetry producer by the telemetry registration interface; sending a fifth message to the telemetry registration controller by the telemetry registration interface; receiving a sixth message from the telemetry registration controller by the telemetry registration interface, the sixth message including a unique telemetry producer identifier (ID) confirmed and assigned by the telemetry registration controller; and sending a telemetry producer protocol group to the telemetry producer by the telemetry registration interface. The interface sends a sixth message to the telemetry producer; the telemetry registration interface receives a seventh message from the telemetry producer, the seventh message including a third telemetry producer hello message with a unique telemetry producer ID; the telemetry registration interface sends the seventh message to the telemetry registration controller; the telemetry registration controller sends an eighth message to the telemetry registration database, the eighth message including an instruction for storing a telemetry producer registration for the telemetry producer, the telemetry producer registration including a telemetry producer protocol group and a unique telemetry producer ID; the telemetry registration database stores the telemetry producer registration including the telemetry producer protocol group and the unique telemetry producer ID for the telemetry producer; the telemetry registration interface receives a ninth message from the telemetry registration controller, the ninth message including a second telemetry registration controller confirmation and a unique telemetry producer ID and indicating acceptance of the registration of the telemetry producer to the telemetry registration controller; and the telemetry registration interface sends the eighth message to the telemetry producer.

[0021] In some cases, the computer-readable medium is also configured to cause one or more processors to perform actions including registering a telemetry consumer with a telemetry registration controller. The registration includes: receiving a first message including a telemetry consumer hello message from a telemetry consumer by a telemetry registration interface; sending a first message to a telemetry registration controller by the telemetry registration interface; receiving a second message from a telemetry registration controller by the telemetry registration interface, the second message including a telemetry registration controller confirmation, the telemetry registration controller confirmation having a unique telemetry consumer identifier (ID) assigned to the telemetry consumer; sending a second message to the telemetry consumer by the telemetry registration interface; receiving a third message from the telemetry consumer by the telemetry registration interface, the third message including a telemetry consumer request packet, the telemetry consumer request packet having a list of telemetry consumer parameters that the telemetry consumer can use to consume telemetry data; sending a third message to the telemetry registration controller by the telemetry registration interface; sending a fourth message to a telemetry registration database by the telemetry registration controller, the fourth message including instructions for storing a telemetry consumer registration for the telemetry consumer; The telemetry consumer registration includes a list of telemetry consumer parameters that the consumer can use to consume telemetry data and a unique telemetry consumer ID; the telemetry consumer registration including the list of telemetry consumer parameters that the consumer can use to consume telemetry data and the unique telemetry consumer ID is stored by the telemetry registration database for the telemetry consumer; the telemetry producer that can produce telemetry data that is compatible with the list of telemetry consumer parameters that the consumer can use to consume telemetry data is queried from the telemetry registration database; the telemetry registration controller receives a fifth message from the telemetry registration database, the fifth message including the telemetry producer ID associated with the telemetry producer, the telemetry producer having a telemetry producer protocol group that is compatible with the list of telemetry consumer parameters that the consumer can use to consume telemetry data; the telemetry registration interface receives the fifth message from the telemetry registration controller; and the telemetry registration interface sends the fifth message to the telemetry consumer.

[0022] Some examples also include sending, by the telemetry consumer, a sixth message to the telemetry message broker, the sixth message requesting telemetry data published by the telemetry producer associated with the telemetry producer ID.

[0023] In some implementations, the list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data includes: a list of types of collection protocols that the telemetry consumer can support, the number of unique keys in a telemetry message, a list of available serialization formats that the telemetry consumer can support, a list of available sensor paths, and a list of available hashing mechanisms that the telemetry consumer is compatible with.

[0024] In some cases, registering a telemetry consumer with a telemetry registration controller includes: registering a first telemetry consumer, wherein the list of telemetry consumer parameters is a first telemetry consumer parameter list; registering a telemetry consumer with the telemetry registration controller also includes: registering a second telemetry consumer with the telemetry registration controller, wherein the second telemetry consumer parameter list that the second telemetry consumer can utilize is different from the first telemetry consumer parameter list that the first telemetry consumer can utilize.

[0025] According to some instances, a telemetry producer ID associated with a telemetry producer capable of producing telemetry data compatible with a second telemetry consumer parameter list that can be utilized by a second telemetry consumer is the same telemetry producer ID associated with the same telemetry producer capable of producing telemetry data compatible with a first telemetry consumer parameter list that can be utilized by a first telemetry consumer.

[0026] In some implementations, the telemetry registration controller is able to register multiple telemetry producers simultaneously.

[0027] According to some examples, the telemetry registration interface is a multi-protocol registration interface.

[0028] In various examples, the telemetry producer protocol group includes: a list of types of collection protocols that the telemetry producer can support, the number of keys that can be collected, a list of available serialization formats that the telemetry producer can support, a list of available sensor paths, and a list of available hashing mechanisms that are compatible with the telemetry producer.

[0029] The examples described herein also provide a method implemented at least in part by a telemetry registration interface, the method comprising: receiving a first message including a telemetry producer hello message from a telemetry producer; sending a second message including a telemetry registration interface hello message to the telemetry producer; receiving a third message including a telemetry producer protocol group from the telemetry producer; sending the third message to a telemetry registration controller; sending a fourth message to the telemetry producer, the fourth message including acceptance of the telemetry producer protocol group and indicating that the telemetry producer protocol group has been forwarded to the telemetry registration controller; receiving a fifth message including a second telemetry producer hello message from the telemetry producer; sending the fifth message to the telemetry registration controller; receiving a sixth message from the telemetry registration controller, the sixth message including a telemetry registration controller confirmation and a unique telemetry producer identifier (ID) assignment; sending the sixth message to the telemetry producer; receiving a seventh message from the telemetry producer, the seventh message including the second telemetry producer hello message and the unique telemetry producer ID; sending the seventh message to the telemetry registration controller Seven messages; receiving an eighth message from a telemetry registration controller, the eighth message including a second telemetry registration controller confirmation and a unique telemetry producer ID and indicating that the telemetry producer has been registered with the telemetry registration controller; sending the eighth message to the telemetry producer; receiving a ninth message including a telemetry consumer hello message from a telemetry consumer; sending the ninth message to the telemetry registration controller; receiving a tenth message from the telemetry registration controller, the tenth message including a telemetry registration controller confirmation with a unique telemetry consumer identifier (ID) assigned; sending the tenth message to the telemetry consumer; receiving an eleventh message from the telemetry consumer, the eleventh message including a telemetry consumer request packet having a list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data; sending the eleventh message to the telemetry registration controller; receiving a twelfth message from the telemetry registration controller, the twelfth message including a unique telemetry producer ID and indicating that the telemetry consumer has been registered with the telemetry registration controller; and sending the twelfth message to the telemetry consumer.

[0030] In various examples, the method is initiated at runtime.

[0031] In some implementations, the telemetry registration controller is capable of registering multiple telemetry producers and multiple telemetry consumers simultaneously.

[0032] In some cases, a telemetry producer is compatible with multiple telemetry consumers with various telemetry consumer parameters.

[0033] Additionally, the techniques described herein may be performed by a system and / or device having a non-transitory computer-readable medium storing computer-executable instructions that, when executed by one or more processors, implement the methods described above.

[0034] Exemplary Embodiments

[0035] Typically, for workload handling between telemetry producers (client applications that publish or write telemetry events) and telemetry consumers (client applications that subscribe or read and process these events), a centralized messaging broker (e.g., Apache Kafka) is used as a messaging platform. However, in order to successfully communicate using a messaging broker, the telemetry producer and telemetry consumer must agree on some parameters in advance so that the telemetry consumer successfully consumes the telemetry data published by the telemetry producer. This synchronization between telemetry producers and telemetry consumers is currently achieved at design time by having a shared model that is used to design and build communication strategies. Typically, telemetry consumers will rely on available telemetry producer documentation in order to design and build subscription strategies. Once the communication strategy is established, the producer and consumer are instantiated as microservices, and the producer and consumer interact with the telemetry message broker (e.g., Kafka) so that the telemetry consumer consumes and processes the telemetry data. Once the synchronization strategy is agreed upon and instantiated, it cannot be changed without completely rebuilding the subscription strategy.

[0036] When consumers upgrade or change network resources, expand network resources, change or add specific data to be collected, or plan to change network resources or telemetry data collection in any other way, telemetry producers and consumers must agree on a new model and start the process from the beginning. Telemetry producers redesign and provide new documents for the newly agreed model, and telemetry consumers are redesigned and rebuilt based on producer documents, resulting in a long production cycle before deployment. This redesign and reconstruction process results in a large amount of economic expenditure and significant time delays.

[0037] The present disclosure describes techniques for dynamic synchronization between telemetry producers and telemetry consumers that are implemented at runtime and allow for runtime changes in network resources and changes in telemetry data collection requirements. This dynamic synchronization is achieved using a telemetry registration framework to negotiate between telemetry producers and telemetry consumers at runtime, thereby eliminating the redesign and rebuild process required to implement changes in the static synchronization process of the prior art.

[0038] The telemetry registration framework eliminates the need for telemetry producers and telemetry consumers to agree on parameters at design time, and acts as a negotiator to find and pair telemetry producers and telemetry consumers with compatible parameters at runtime. The telemetry producer communicates with the telemetry registration interface and sends the telemetry registration interface a list of parameters that the telemetry producer can use to publish telemetry data. The telemetry registration interface sends this information to the telemetry registration controller, which assigns a unique telemetry producer identifier (ID) to the telemetry producer, and the telemetry registration database stores the telemetry producer parameters and the telemetry producer ID, effectively registering the telemetry producer with the telemetry registration framework. At runtime, the telemetry consumer sends the telemetry registration controller a list of parameters that the telemetry consumer can use to consume telemetry data through the telemetry registration interface. The telemetry registration controller registers the telemetry consumer and assigns a unique telemetry consumer ID to the telemetry consumer. The telemetry registration database stores the telemetry consumer ID and a list of telemetry consumer parameters. The telemetry registration controller queries the telemetry registration database for telemetry producer IDs associated with telemetry producers having parameters that are compatible with the parameters of the telemetry consumer, and once found, the telemetry producer IDs are sent to the telemetry consumer. When the telemetry consumer receives the telemetry producer ID, the telemetry consumer can request telemetry data from the compatible telemetry producer through the centralized telemetry message broker.

[0039] When a telemetry producer registers with a telemetry registration controller, the telemetry producer sends a list of all parameters of all types that the telemetry producer can use to produce and publish telemetry data. The main parameters that the telemetry producer provides for registration include the type of collection protocol (e.g., Simple Network Management Protocol (SNMP), Model Driven Telemetry (MDT), Command Line Interface (CLI), Google Network Management Interface (gNMI), YANG, or any other available collection protocol, including custom protocols), the number of keys or the number of types of data that can be collected, the serialization or messaging format (e.g., Javascript Object Notation (JSON), Key-Value Google Protocol Buffers (KVGPB), Protobuf, Avro encoding, Crosswork encoding, or any other applicable messaging format, including custom formats), available sensor paths, and hashing mechanisms. In some examples, secondary parameters such as the type of operating system, security of the collection (credentials, TLS, mutual TLS, etc.), and device vendors may also be included. Each telemetry producer can support one or more of each of the different parameters discussed above. Thus, each telemetry producer is made compatible with multiple telemetry consumers with multiple capabilities.

[0040] Similarly, when a telemetry consumer registers with the telemetry registration framework, the telemetry consumer communicates with the telemetry registration controller through the telemetry registration interface. The telemetry registration controller assigns a unique telemetry consumer identifier (ID) to the telemetry consumer. The telemetry consumer then sends a telemetry consumer request packet to the telemetry registration controller through the telemetry registration interface, which has a list of all telemetry consumer parameters that the telemetry consumer can use to consume telemetry data. The telemetry consumer ID is stored in the telemetry registration database along with the telemetry consumer parameters, effectively registering the telemetry consumer with the telemetry registration framework. The telemetry registration controller then queries the database for a telemetry producer ID associated with a telemetry producer having telemetry producer parameters that are compatible with the telemetry consumer parameters. When a compatible telemetry producer is found, the telemetry registration controller sends the telemetry producer ID of the compatible telemetry producer to the telemetry consumer through the telemetry registration interface. Once the telemetry consumer receives the telemetry producer ID of the compatible telemetry producer, the telemetry consumer can send a telemetry data request to the compatible telemetry producer through the telemetry message broker.

[0041] The telemetry consumer request packet has a list of all telemetry consumer parameters of all types that the telemetry consumer can utilize to consume telemetry data, similar to the list of telemetry producer parameters that the telemetry producer uses to register with the telemetry controller. The main parameters that the telemetry consumer uses to register with the telemetry registration controller include the type of collection protocol, the number of keys or the number of types of data that can be collected, the serialization or messaging format, the available sensor paths, and the hashing mechanism. Each telemetry consumer can support one or more of each of the different parameters.

[0042] Certain implementations and embodiments of the present disclosure will be described more fully below with reference to the accompanying drawings, in which various aspects are shown. However, various aspects can be implemented in many different forms and should not be construed as being limited to the implementations described herein. The present disclosure includes variants of the embodiments described herein. The same numbers throughout the text represent the same elements.

[0043] Figure 1 A system architecture diagram of an example implementation of a telemetry registration framework for dynamically synchronizing telemetry producers and telemetry consumers is shown. The system architecture 100 includes a telemetry registration framework 102 (hereinafter referred to as a telemetry registration framework 102) for registering telemetry producers 104 and telemetry consumers 106. Figure 2 100). The system architecture 100 also includes a telemetry message broker 108, such as Kafka, for facilitating messaging and communication between telemetry producers 104 and telemetry consumers 106. The system architecture 100 also shows telemetry sources 110 from which telemetry producers collect telemetry data for publication.

[0044] The telemetry producer 104 registers with the telemetry registration framework 102, which will be referred to below. Figure 3 The telemetry consumer 106 also registers with the telemetry registration framework, which will be referenced below. Figure 4 Detailed description. Once the telemetry producer 104 is registered, the telemetry producer 104 collects telemetry data from the telemetry source 110, such as network resources (e.g., various hardware devices such as routers, switches, gateways, smart NICs, NICs, ASICs, FPGAs, servers, and / or any other type of device), and publishes the telemetry data to the telemetry message broker 108 (e.g., Apache Kafka, Amazon SNS, Azure Service Bus, Google Cloud Publish / Subscribe Platform, or any other appropriate publish / subscribe platform). Once the telemetry consumer 106 is registered, the telemetry consumer 106 receives the telemetry producer ID of the telemetry producer 104 with compatible parameters. The telemetry consumer 106 can then subscribe to the telemetry data published by the telemetry producer 104 from the telemetry message broker 108.

[0045] Figure 2 An example 200 of a telemetry registration framework 102 is shown for registering telemetry producers and telemetry consumers to facilitate dynamic runtime synchronization between compatible telemetry producers and telemetry consumers. The illustrated telemetry registration framework includes a telemetry registration interface 202. The telemetry registration interface 202 is a multi-protocol interface that can facilitate communication between a telemetry registration controller 204 and multiple telemetry producers and multiple telemetry consumers having different protocol capabilities. Thus, regardless of the protocol used by the telemetry producer or telemetry consumer, the telemetry registration interface 202 can facilitate communication with the telemetry registration controller 204. The example 200 of the telemetry registration framework also includes a telemetry registration controller 204. The telemetry registration controller 204 is a centralized controller with a horizontally scaled architecture. The telemetry registration controller 204 is capable of registering multiple telemetry producers and multiple telemetry consumers simultaneously. Additionally, the telemetry registration controller 204 can register telemetry producers and telemetry consumers in any order. The telemetry registration framework 102 also includes a telemetry registration database 206. The telemetry registration database 206 is a strongly consistent database with raft consensus (e.g., etcd, Redis, or any other suitable database). The telemetry registration database 206 stores each telemetry producer and telemetry consumer registration, including a unique ID assigned by the telemetry registration controller 204 and parameters that each telemetry producer and telemetry consumer can utilize to produce and consume telemetry data, respectively.

[0046] The dynamic synchronization achieved by adopting the telemetry registration framework 102 significantly increases the flexibility of injecting runtime telemetry consumers into the network management controller and is applicable to different consumer deployments and data models. This enables the development of optimizations for telemetry function packages and the use of hashing frameworks for dynamic insertion to quickly process messages. In addition, dynamic consensus allows runtime changes to telemetry producers without affecting telemetry consumers. However, in the case of traditional static synchronization, telemetry producers cannot be changed because of strong coupling, and all telemetry producers and telemetry consumers must be changed at the same time, which brings a huge bottleneck to upgrading producers. However, by utilizing the telemetry registration framework 102, the telemetry producer is compatible with multiple telemetry consumers with different functions. In addition, the telemetry registration framework 102 allows seamless horizontal and vertical scaling to handle increased throughput and availability.

[0047] Figure 3 As shown above reference Figure 2 Detailed example 300 of registering a telemetry producer 104 with a telemetry registration framework. The telemetry producer 104 sends a hello message to the telemetry registration interface 202. The telemetry registration interface 202 returns a hello message to the telemetry producer 104. The telemetry producer 104 sends a message including a telemetry producer protocol group to the telemetry registration interface 202. The telemetry producer protocol group includes a list of all parameters of all types that the telemetry producer 104 can utilize to produce telemetry data, as described above with reference to Figure 1 As discussed. The telemetry registration interface 202 forwards the message with the telemetry producer protocol group to the telemetry registration controller 204, and sends a message back to the telemetry producer 104 including acceptance of the telemetry producer protocol group and an instruction to forward the telemetry producer protocol group to the telemetry registration controller 204. The telemetry producer 104 sends a hello message to the telemetry registration controller 204 via the telemetry registration interface 202. The telemetry registration controller 204 sends a message back to the telemetry producer 104 via the telemetry registration interface 202, the message including the unique telemetry producer ID confirmed and assigned by the telemetry registration controller. The telemetry producer 104 sends another hello message with the assigned telemetry producer ID to the telemetry registration controller 204 via the telemetry registration interface. When the telemetry registration controller receives the message, the telemetry producer 104 is effectively registered to the telemetry registration controller 204, and the telemetry producer ID is stored in the telemetry registration database together with the telemetry producer protocol group. The telemetry registration controller 204 sends another telemetry controller confirmation message with the telemetry producer ID to the telemetry producer 104 through the telemetry registration interface 202. At this point, the telemetry producer 104 has been registered with the telemetry registration framework and is ready to start sending messages to the telemetry message broker (as described above and as shown in the example below). Figure 1 ) to publish telemetry data.

[0048] Figure 4As shown above reference Figure 2 Detailed example 400 of registering a telemetry consumer 106 with a telemetry registration framework is described. The telemetry consumer 106 sends a hello message to the telemetry registration controller 204 via the telemetry registration interface 202. The telemetry registration controller 204 returns an acknowledgement message with an assigned unique telemetry consumer ID. The telemetry consumer 106 then sends a telemetry consumer request packet to the telemetry registration controller 204 via the telemetry registration interface 202, the telemetry consumer request packet including a list of all parameters of all types that the telemetry consumer can utilize to consume telemetry data and the telemetry consumer ID. At this point, the telemetry consumer is effectively registered with the telemetry registration controller 204, and the telemetry consumer ID and telemetry consumer parameters are stored in the telemetry registration database. The telemetry registration database is then queried to find the telemetry producer ID of a telemetry producer that has parameters that are compatible with the parameters of the telemetry consumer 106. Once found, the telemetry registration controller 204 sends the telemetry producer ID of the telemetry producer that has compatible parameters to the telemetry consumer 106. When a telemetry consumer has been registered and has received the telemetry producer ID of a compatible telemetry producer, the telemetry consumer 106 can subscribe to the telemetry message broker (as described above in reference to Figure 1 described) receives telemetry data produced by a compatible telemetry producer.

[0049] Figure 5a-5b A process 500 is shown for registering telemetry producers and telemetry consumers with a telemetry registration framework using a registration interface protocol. The process 500 may be described at least in part as described above with reference to Figure 1 In the network environment described above and using Figure 2 The telemetry registration framework is used to perform the above operations.

[0050] A first message including a telemetry producer hello is sent from a telemetry producer to a telemetry registration interface in operation 502. The telemetry producer initiates communication with the telemetry registration interface to begin a registration process with the telemetry registration framework.

[0051] In operation 504, a second message including a telemetry registration interface hello is sent from the telemetry registration interface back to the telemetry producer. Once the telemetry registration interface successfully receives the telemetry producer hello message, the telemetry registration interface returns a hello message to the telemetry producer. At this point, the telemetry producer and the telemetry registration interface have successfully established communication and the telemetry producer registration process can continue. If the telemetry registration interface does not return a hello message to the telemetry producer, the telemetry producer registration process fails.

[0052] In operation 506, a third message including a telemetry producer protocol group is sent from the telemetry producer to the telemetry registration interface and forwarded to the telemetry registration controller. The telemetry producer protocol group includes a list of all parameters of all types that the telemetry producer can utilize to produce telemetry data. For example, the main parameters included in the telemetry producer protocol group include the type of collection protocol, the number of keys or the number of types of data that can be collected, the serialization or messaging format, the available sensor paths, and the hashing mechanism. In some examples, the producer protocol group also includes secondary parameters such as the type of operating system, the security of the collection, and the device vendor.

[0053] In operation 508, a fourth message is sent from the telemetry registration interface to the telemetry producer, the fourth message including acceptance of the protocol group and an indication that the protocol group has been forwarded to the telemetry registration controller.

[0054] In operation 510, a fifth message including a second telemetry producer hello message is sent from the telemetry producer to the telemetry registration interface and forwarded to the telemetry registration controller. The telemetry producer initiates communication with the telemetry registration controller through the telemetry registration interface.

[0055] In operation 512, a sixth message including a telemetry registration controller acknowledgement and a unique telemetry producer ID assignment is sent from the telemetry registration controller to the telemetry registration interface and forwarded to the telemetry producer. When the telemetry registration controller successfully receives the hello message sent from the telemetry producer, the telemetry registration controller acknowledges receipt of the hello message by sending a unique ID assignment to the telemetry producer, thereby effectively establishing communication with the telemetry producer via the telemetry registration interface. If the telemetry registration controller does not acknowledge the telemetry producer hello message, the telemetry producer registration process cannot continue.

[0056] In operation 514, a seventh message including the second telemetry producer hello message and the unique telemetry producer ID is sent from the telemetry producer to the telemetry registration interface and forwarded to the telemetry registration controller. When the telemetry registration controller receives the message, the telemetry registration controller effectively registers the telemetry producer as ready to collect and publish telemetry data and stores the registration in a telemetry registration database (e.g., as described above and in Figure 2 In the telemetry registration database 206 shown in .

[0057] In operation 516, an eighth message including the second telemetry registration controller confirmation and the unique telemetry producer ID and indicating the telemetry producer registration is sent from the telemetry registration controller to the telemetry registration interface and forwarded to the telemetry producer.

[0058] In operation 518, a ninth message including a telemetry consumer hello is sent from the telemetry consumer to the telemetry registration interface and forwarded to the telemetry registration controller. The telemetry consumer initiates communication with the telemetry registration controller through the telemetry registration interface to begin the registration process.

[0059] In operation 520, a tenth message including a telemetry registration controller acknowledgment with a unique telemetry consumer ID assignment is sent from the telemetry registration controller to the telemetry registration interface and forwarded to the telemetry consumer. The telemetry registration controller acknowledges successful communication with the telemetry consumer through the telemetry registration interface and sends the telemetry consumer its unique telemetry consumer ID assignment. If the telemetry registration controller does not acknowledge the hello message sent by the telemetry consumer, the telemetry consumer registration process will fail.

[0060] In operation 522, an eleventh message including a telemetry consumer request packet with a list of telemetry consumer parameters is sent from the telemetry consumer to the telemetry registration interface and forwarded to the telemetry registration controller. The telemetry consumer request packet includes a list of all parameters of all types that the telemetry consumer can utilize to consume telemetry data. The main parameters include the collection protocol type, the number of keys or the number of types of data that can be collected, the serialization or messaging format, the available sensor paths, and the hashing mechanism. When the telemetry registration controller receives the message, the telemetry registration controller effectively registers the telemetry consumer and stores the registration in the telemetry database.

[0061] In operation 524, a twelfth message including a unique telemetry producer ID and indicating that the telemetry consumer has been registered with the telemetry registration controller is sent from the telemetry registration controller to the telemetry registration interface and forwarded to the telemetry consumer. Once the telemetry consumer receives the telemetry producer ID of a compatible telemetry producer, the telemetry consumer can communicate with the telemetry consumer through a telemetry message broker (e.g., as described above with reference to Figure 1 A telemetry message broker as described and illustrated) subscribes to telemetry data published by compatible telemetry producers.

[0062] Figure 6 An example computer architecture diagram illustrating a computer hardware architecture of device 600 for implementing the functionality described herein. The telemetry registration interface 202 , telemetry registration controller 204 , and telemetry registration database 206 described above may include some or all of the components discussed below with reference to device 600 .

[0063] The device 600 includes a substrate 602 or "motherboard," which is a printed circuit board to which multiple components or devices may be connected via a system bus or other electrical communication paths. In one exemplary configuration, one or more central processing units (CPUs) 604 work together with a chipset 606. The CPU 604 may be a standard programmable processor that performs the arithmetic and logic operations required for the operation of the device 600.

[0064] The CPU 604 performs operations by manipulating switch elements that distinguish discrete physical states and change these states to convert from one discrete physical state to the next discrete physical state. Switch elements typically include electronic circuits that maintain one of two binary states, such as flip-flops, and electronic circuits that provide output states based on logical combinations of the states of one or more other switch elements, such as logic gates. These basic switch elements can be combined to create more complex logic circuits, including registers, adders-subtractors, arithmetic logic units, floating point units, etc.

[0065] Chipset 606 provides an interface between CPU 604 and the rest of the components and devices on baseboard 602. Chipset 606 may provide an interface to random access memory (RAM) 608, which is used as main memory in device 600. Chipset 606 may also provide an interface to a computer-readable storage medium such as read-only memory (ROM) 610 or non-volatile RAM (NVRAM) for storing basic routines that help boot device 600 and transfer information between various components and devices. ROM 610 or NVRAM may also store other software components required for operation of device 600 according to the configuration described herein.

[0066] Device 600 can operate in a networked environment using logical connections to remote computing devices and computer systems through a network, such as local area network 624. Chipset 606 may include functionality for providing network connectivity through a network interface card (NIC) 612, such as a Gigabit Ethernet adapter. NIC 612 is capable of connecting device 600 to other computing devices through a network. It should be understood that multiple NICs 612 may be present in device 600 for connecting a computer to other types of networks and remote computer systems.

[0067] The device 600 can be connected to a storage device 618 that provides non-volatile storage for the computer. The storage device 618 can store an operating system 620, programs 622, and data, which have been described in more detail herein. The storage device 618 can be connected to the device 600 via a storage controller 614 connected to the chipset 606. The storage device 618 may include one or more physical storage units. The storage controller 614 may be connected to the physical storage unit via a serial attached SCSI (SAS) interface, a serial advanced technology connection (SATA) interface, an FC interface, or other types of interfaces for providing physical connections and transferring data between a computer and a physical storage unit.

[0068] Device 600 can store data on storage device 618 by transforming the physical state of the physical storage unit to reflect the information being stored. In different embodiments of the present specification, the specific transformation of the physical state can depend on various factors. Examples of these factors may include, but are not limited to, the technology used to implement the physical storage unit, whether storage device 618 is marked as a primary storage device or a secondary storage device, etc.

[0069] For example, the device 600 can store information to the storage device 618 by issuing instructions to the storage controller 614 to change the magnetic properties of a specific location in the disk drive unit, the reflective or refractive properties of a specific location in the optical storage unit, or the electrical properties of a specific capacitor, transistor or other discrete component in the solid-state storage unit. Other transformations of the physical medium are also possible without departing from the scope and spirit of the present specification, and the foregoing examples are provided only for ease of illustration. The device 600 can also read information from the storage device 618 by detecting the physical state or properties of one or more specific locations in the physical storage unit.

[0070] In addition to the storage device 618 described above, the device 600 may also access other computer-readable storage media to store and retrieve information, such as program modules, data structures, or other data. It should be appreciated by those skilled in the art that computer-readable storage media may be any available media that provides non-temporary storage of data and is accessible by the device 600.

[0071] By way of example and not limitation, computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology. Computer-readable storage media include, but are not limited to, RAM, ROM, erasable programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), flash memory or other solid-state memory technology, compact disk ROM (CD-ROM), digital versatile disk (DVD), high-definition DVD (HD-DVD), BLU-RAY or other optical storage, magnetic cassettes, magnetic tapes, disk storage or other magnetic storage devices, or any other medium that can be used to store the desired information in a non-transitory manner.

[0072] As briefly mentioned above, the storage device 618 may store an operating system 620 for controlling the operation of the device 600. According to one embodiment, the operating system comprises LINUX TM According to another embodiment, the operating system includes WINDOWS from Microsoft Corporation in Redmond, Washington. TM SERVER operating system. According to another embodiment, the operating system may include UNIX TMAn operating system or one of its variants. It should be understood that other operating systems may also be used. Storage device 618 may store other system or application programs and data used by device 600.

[0073] In one embodiment, the storage device 618 or other computer-readable storage medium is encoded with computer-executable instructions that, when loaded into the device 600, convert the computer from a general-purpose computing system to a special-purpose computer capable of implementing the embodiments described herein. As described above, these computer-executable instructions convert the device 600 by specifying how the CPU 604 transitions between states. According to one embodiment, the device 600 has access to a computer-readable storage medium storing computer-executable instructions that, when executed by the device 600, implement the embodiments described above with reference to Figure 1-5b The device 600 may also include a computer-readable storage medium having stored thereon instructions for performing any other computer-implemented operations described herein.

[0074] The device 600 may also include one or more input / output controllers 616 for receiving and processing input from a plurality of input devices such as a keyboard, a mouse, a touch pad, a touch screen, an electronic pen, or other types of input devices. Similarly, the input / output controller 616 may provide output to a display such as a computer monitor, a flat panel display, a digital projector, a printer, or other types of output devices. It should be understood that the device 600 may not include Figure 6 All components shown may include Figure 6 Other components not explicitly shown in the figure or the like may be used Figure 6 Completely different architecture shown.

[0075] In summary, the telemetry producer sends a hello message to the telemetry registration interface. The interface returns a hello message. The producer sends a producer protocol group to the interface. A message including acceptance of the protocol group and an indication that the protocol group has been forwarded to the telemetry registration controller is returned. The producer sends a hello message to the controller. The controller returns an acknowledgment and a producer identifier (ID). A second hello message and the producer ID are sent from the producer to the controller. The controller returns a second acknowledgment and the producer ID indicating the producer registration. The telemetry consumer sends a hello message to the controller. An acknowledgment with a consumer identifier (ID) is returned to the consumer. The consumer sends a consumer request packet to the controller. The controller sends the producer ID and an indication of the consumer registration to the consumer.

[0076] In some examples, one or more components may be described herein as "configured to...", "configurable to...", "operable / capable to...", "adapted / adaptable to...", "capable of...", "conformable / conformable to...", etc. One skilled in the art will recognize that such terms (e.g., "configured to") may generally encompass active state components and / or inactive state components and / or standby state components unless the context requires otherwise.

[0077] As used herein, the term "based on" may be used synonymously with "based at least in part on" and "based at least in part on". As used herein, the terms "comprising / including / comprising" and their equivalents may be used interchangeably. An apparatus, system, or method "comprising A, B, and C" includes A, B, and C, but may also include other components (e.g., D). That is, the apparatus, system, or method is not limited to components A, B, and C.

[0078] Although the present invention has been described with respect to specific embodiments, it should be understood that the scope of the present invention is not limited to these specific embodiments. Since other modifications and variations that may be adapted to specific operating requirements and environments are apparent to those skilled in the art, the present invention should not be considered to be limited to the examples selected for the purpose of disclosure, but rather encompasses all changes and modifications that do not constitute a departure from the true spirit and scope of the present invention.

[0079] Although the present application describes embodiments with specific structural features and / or methodological actions, it should be understood that the claims are not necessarily limited to the specific features or actions described. Instead, the specific features and actions are merely illustrations of embodiments within the scope of the claims of the present application.

Claims

1. A system comprising: one or more processors; as well as One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform actions comprising: The telemetry producer is assigned a unique telemetry producer identifier (ID) by the telemetry registration controller; registering parameters associated with the telemetry producer to the telemetry registration controller; storing the telemetry producer ID and parameters associated with the telemetry producer in a telemetry registration database; Allocating a unique telemetry consumer ID to the telemetry consumer by the telemetry registration controller; registering parameters associated with the telemetry consumer with the telemetry registration controller; storing the telemetry consumer ID and parameters associated with the telemetry consumer in the telemetry registration database; determining that parameters associated with the telemetry producer are compatible with parameters associated with the telemetry consumer; and A message is sent to the telemetry consumer, where the message includes the telemetry producer ID and indicates that the telemetry consumer can subscribe to telemetry data published by the telemetry producer from a telemetry message broker.

2. The system according to claim 1, wherein: The telemetry registration controller is capable of registering multiple telemetry producers and multiple telemetry consumers simultaneously.

3. The system according to claim 1 or 2, wherein: The telemetry registration controller is a centralized controller with a horizontally scalable architecture.

4. The system according to any one of claims 1 to 3, wherein: The telemetry registration database is a strong consistency key-value database.

5. A system comprising: one or more processors; as well as One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform actions comprising: receiving, by the telemetry registration interface, a first message from a telemetry producer, the first message comprising a telemetry producer hello message; The telemetry registration interface sends a second message to the telemetry producer, wherein the second message includes a telemetry registration interface hello message; receiving, by the telemetry registration interface, a third message from the telemetry producer, the third message including a telemetry producer protocol group; Sending the third message to the telemetry registration controller by the telemetry registration interface; sending, by the telemetry registration interface, a fourth message to the telemetry producer, the fourth message including acceptance of the telemetry producer protocol group and indicating that the telemetry producer protocol group has been forwarded to the telemetry registration controller; receiving, by the telemetry registration interface, a fifth message from the telemetry producer, the fifth message comprising a second telemetry producer hello message; Sending the fifth message to the telemetry registration controller by the telemetry registration interface; receiving, by the telemetry registration interface, a sixth message from the telemetry registration controller, the sixth message including a unique telemetry producer identifier (ID) confirmed and assigned by the telemetry registration controller; Sending the sixth message to the telemetry producer by the telemetry registration interface; receiving, by the telemetry registration interface, a seventh message from the telemetry producer, the seventh message comprising a third telemetry producer hello message having a unique telemetry producer ID; Sending the seventh message to the telemetry registration controller by the telemetry registration interface; sending, by the telemetry registration controller, an eighth message to a telemetry registration database, the eighth message comprising instructions for storing a telemetry producer registration for the telemetry producer, the telemetry producer registration comprising the telemetry producer protocol group and the unique telemetry producer ID; storing, by the telemetry registration database, the telemetry producer registration including the telemetry producer protocol group and the unique telemetry producer ID for the telemetry producer; receiving, by the telemetry registration interface, a ninth message from the telemetry registration controller, the ninth message including a second telemetry registration controller confirmation and the unique telemetry producer ID, indicating that registration of the telemetry producer with the telemetry registration controller has been accepted; and The eighth message is sent by the telemetry registration interface to the telemetry producer.

6. The system according to claim 5, wherein: The computer readable medium is further configured to cause the one or more processors to perform actions including: receiving, by the telemetry registration interface, a first message from a telemetry consumer, the first message comprising a telemetry consumer hello message; The telemetry registration interface sends the first message to the telemetry registration controller; receiving, by the telemetry registration interface, a second message from the telemetry registration controller, the second message including a telemetry registration controller acknowledgment having a unique telemetry consumer identifier (ID) assigned to the telemetry consumer; The telemetry registration interface sends the second message to the telemetry consumer; receiving, by the telemetry registration interface, a third message from the telemetry consumer, the third message comprising a telemetry consumer request packet, the telemetry consumer request packet having a list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data; The telemetry registration interface sends the third message to the telemetry registration controller; sending, by the telemetry registration controller, a fourth message to the telemetry registration database, the fourth message comprising instructions for storing a telemetry consumer registration for the telemetry consumer, the telemetry consumer registration comprising a list of the telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data and the unique telemetry consumer ID; storing, by the telemetry registration database, for the telemetry consumer, the telemetry consumer registration including a list of the telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data and the unique telemetry consumer ID; querying the telemetry registration database for telemetry producers capable of producing telemetry data that is compatible with the list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data; receiving, by the telemetry registration controller from the telemetry registration database, a fifth message including a telemetry producer ID associated with a telemetry producer having a telemetry producer protocol set compatible with the list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data; receiving, by the telemetry registration interface, the fifth message from the telemetry registration controller; as well as The fifth message is sent by the telemetry registration interface to the telemetry consumer.

7. The system according to claim 6, further comprising: A sixth message is sent by the telemetry consumer to the telemetry message broker, the sixth message requesting telemetry data published by the telemetry producer associated with the telemetry producer ID.

8. The system according to claim 6 or 7, wherein: The list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data includes: A list of types of collection protocols that the telemetry consumer can support; The number of unique keys in the telemetry message; A list of available serialization formats that the telemetry consumer can support; a list of available sensor paths; and A list of available hashing mechanisms that this telemetry consumer is compatible with.

9. A system according to any one of claims 6 to 8, wherein: Registering a telemetry consumer as a first telemetry consumer to the telemetry registration controller, wherein the list of telemetry consumer parameters is a first telemetry consumer parameter list, and also including registering a second telemetry consumer to the telemetry registration controller, wherein the second telemetry consumer parameter list that can be used by the second telemetry consumer is different from the first telemetry consumer parameter list that can be used by the first telemetry consumer.

10. The system according to claim 9, wherein: The telemetry producer ID associated with a telemetry producer capable of producing telemetry data compatible with the second telemetry consumer parameter list that the second telemetry consumer can utilize is the same telemetry producer ID associated with the same telemetry producer capable of producing telemetry data compatible with the first telemetry consumer parameter list that the first telemetry consumer can utilize.

11. A system according to any one of claims 5 to 10, wherein: The telemetry registration controller is capable of registering multiple telemetry producers simultaneously.

12. A system according to any one of claims 5 to 11, wherein: The telemetry registration interface is a multi-protocol registration interface.

13. A system according to any one of claims 5 to 12, wherein: The telemetry producer protocol suite includes: A list of collection protocol types that the telemetry producer can support; The number of keys that can be collected; A list of available serialization formats that the telemetry producer can support; a list of available sensor paths; and A list of available hashing mechanisms that this telemetry producer is compatible with.

14. A method for registering a telemetry producer and a telemetry consumer with a telemetry registration controller, the method being implemented at least in part by a telemetry registration interface, the method comprising: receiving a first message including a telemetry producer hello message from the telemetry producer; sending a second message including a telemetry registration interface hello message to the telemetry producer; receiving a third message including a telemetry producer protocol suite from the telemetry producer; sending the third message to the telemetry registration controller; sending a fourth message to the telemetry producer, the fourth message including acceptance of the telemetry producer protocol set and indicating that the telemetry producer protocol set has been forwarded to the telemetry registration controller; receiving a fifth message including a second telemetry producer hello message from the telemetry producer; sending the fifth message to the telemetry registration controller; receiving a sixth message from the telemetry registration controller, the sixth message including a telemetry registration controller confirmation and a unique telemetry producer identifier (ID) assignment; sending the sixth message to the telemetry producer; receiving a seventh message from the telemetry producer, the seventh message comprising a second telemetry producer hello message and the unique telemetry producer ID; sending the seventh message to the telemetry registration controller; receiving an eighth message from the telemetry registration controller, the eighth message including a second telemetry registration controller confirmation and the unique telemetry producer ID, indicating that the telemetry producer has been registered with the telemetry registration controller; as well as The eighth message is sent to the telemetry producer.

15. The method according to claim 14, further comprising: receiving a ninth message including a telemetry consumer hello message from the telemetry consumer; sending the ninth message to the telemetry registration controller; receiving a tenth message from the telemetry registration controller, the tenth message including a telemetry registration controller acknowledgment with a unique telemetry consumer identifier (ID) assignment; sending the tenth message to the telemetry consumer; receiving an eleventh message from the telemetry consumer, the eleventh message comprising a telemetry consumer request packet having a list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data; sending the eleventh message to the telemetry registration controller; receiving a twelfth message from the telemetry registration controller, the twelfth message including the unique telemetry producer ID and indicating that the telemetry consumer has been registered with the telemetry registration controller; as well as The twelfth message is sent to the telemetry consumer.

16. The method according to claim 15, wherein: A telemetry consumer request packet having a list of telemetry consumer parameters that the telemetry consumer can utilize to consume telemetry data includes: A list of collection protocol types that the telemetry consumer can support; The number of keys that can be collected; A list of available serialization formats that the telemetry consumer can support; a list of available sensor paths; and a list of available sensor paths; and a list of available hashing mechanisms that the telemetry consumer is compatible with.

17. The method according to any one of claims 14 to 16, wherein: The telemetry producer protocol suite includes: A list of collection protocol types that the telemetry producer can support; The number of keys that can be collected; A list of available serialization formats that the telemetry producer can support; a list of available sensor paths; and A list of available hashing mechanisms that this telemetry producer is compatible with.

18. The method according to any one of claims 14 to 17, wherein: The method is initiated at runtime.

19. The method according to any one of claims 14 to 18, wherein: The telemetry registration controller is capable of registering multiple telemetry producers and multiple telemetry consumers simultaneously.

20. The method according to any one of claims 14 to 19, wherein: The telemetry producer is compatible with multiple telemetry consumers having various telemetry consumer parameters.

21. A system comprising: means for receiving, by the telemetry registration interface, a first message from a telemetry producer including a telemetry producer hello message; means for sending, by the telemetry registration interface, a second message comprising a telemetry registration interface hello message to the telemetry producer; means for receiving, by the telemetry registration interface, from the telemetry producer a third message including a telemetry producer protocol suite; means for sending, by the telemetry registration interface, the third message to the telemetry registration controller; means for sending, by the telemetry registration interface, a fourth message to the telemetry producer, the fourth message including acceptance of the telemetry producer protocol suite and indicating that the telemetry producer protocol suite has been forwarded to the telemetry registration controller; means for receiving, by the telemetry registration interface, from the telemetry producer a fifth message comprising a second telemetry producer hello message; means for sending, by the telemetry registration interface, the fifth message to the telemetry registration controller; means for receiving, by the telemetry registration interface, a sixth message from the telemetry registration controller, the sixth message comprising a unique telemetry producer identifier (ID) confirmed and assigned by the telemetry registration controller; means for sending, by the telemetry registration interface, the sixth message to the telemetry producer; means for receiving, by the telemetry registration interface, a seventh message from the telemetry producer, the seventh message comprising a third telemetry producer hello message having the unique telemetry producer ID; means for sending, by the telemetry registration interface, the seventh message to the telemetry registration controller; means for sending, by the telemetry registration controller, an eighth message to a telemetry registration database, the eighth message comprising instructions for storing a telemetry producer registration for the telemetry producer, the telemetry producer registration comprising the telemetry producer protocol group and the unique telemetry producer ID; means for storing, by said telemetry registration database, said telemetry producer registration for said telemetry producer including said telemetry producer protocol set and said unique telemetry producer ID; means for receiving, by the telemetry registration interface, a ninth message from the telemetry registration controller, the ninth message including a second telemetry registration controller acknowledgment and the unique telemetry producer ID and indicating that registration of the telemetry producer with the telemetry registration controller has been accepted; as well as Means for sending, by the telemetry registration interface, the eighth message to the telemetry producer.

22. The apparatus of claim 21, further comprising means for implementing the method of any one of claims 15 to 20.

23. A computer program, a computer program product or a computer readable medium comprising instructions which, when executed by a computer, cause the computer to carry out the steps of the method according to any one of claims 14 to 20.