Computer-implemented method, computer program product, and communication system for transmitting data

The method improves message transmission in publish-subscribe systems by using intelligent reduction units to analyze and transform messages, addressing scalability and cost issues in message queues.

DE102023209404B3Active Publication Date: 2024-12-05SIEMENS AG
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
DE102023209404
Authority / Receiving Office
DE · DE
Patent Type
Patents
Current Assignee / Owner
Filing Date
2023-09-26
Publication Date
2024-12-05
Estimated Expiration
2043-09-26

AI Technical Summary

Technical Problem

Message queues face limitations in message size, persistent memory, maximum throughput, and high operational costs, particularly in cloud-based systems, leading to performance issues and scalability challenges when handling large data packets and multiple messages simultaneously.

Method used

A computer-implemented method involving intelligent reduction units that analyze and transform messages based on specific properties, applying reshaping actions to optimize transmission, reconstruct the original message, and manage message traffic intelligently, thereby reducing load and costs in publish-subscribe systems.

Benefits of technology

This approach enhances the robustness and efficiency of message transmission by intelligently managing message traffic, decoupling publishers and subscribers, and optimizing operational costs in public clouds.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 00000000_0000_ABST
    Figure 00000000_0000_ABST
Patent Text Reader

Abstract

A computer-implemented method for transferring data in a communication system is proposed, which includes the following steps: a) Receiving a message from a first communication unit, wherein the message is assigned to a topic, b) Analyzing the received message with respect to a message property to obtain a first specific transformation type for the received message, c) Applying a first type of specific transformation action to the analyzed message depending on the obtained first specific transformation type to obtain a transformed message, wherein the transformed message is associated with the subject or a modified subject corresponding to the obtained first specific transformation type, d) Reconstructing the transformed message using the theme or modified theme of the transformed message determined by the second reduction unit to obtain the message or a modified message, and e) Transmitting the received message or the received modified message to the second communication unit.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] The present invention relates to a computer-implemented method and a computer program product for transmitting data. Furthermore, the invention relates to a communication system for transmitting data.

[0002] Message queues with various protocols such as Message Queuing Telemetry Transport (MQTT) are often used for communication in distributed systems (see [1]). A message queue has publishers, which submit messages with a specific topic to the message queue, and subscribers, which, for example, subscribe to the specific topic and thereby receive messages on this topic. Such message queues are used as a communication channel in many technical systems, particularly in the context of the Internet of Things (IoT). This is referred to as a publish-subscribe system.

[0003] However, message queues have various limitations regarding message size, the persistent storage used internally, and / or the maximum message throughput. Consequently, transporting large amounts of data can be challenging, and sending (too) many messages simultaneously can lead to performance and scalability degradation. In the case of persistence, storage problems can also arise if large data packets are not retrieved by a subscriber.

[0004] In the case of cloud-based message queues, such as Amazon Web Service (AWS) IoT Core [2], the cost aspect also comes into play. Public clouds offer various cost models, e.g., based on message size and / or number of messages, which can sometimes result in very high operational costs. State-of-the-art approaches to this include data compression during message transmission.

[0005] In addition, Lambda and Kappa architectural patterns for message queues are known from the state of the art (see [3], Fig. ).

[0006] DE 10 2020 214 358 A1 discloses a computer-implemented method for transmitting individual messages using the MQTT protocol. It involves collecting relevant messages for a receiving device, creating a collective message, transmitting it to the receiving device, receiving the collective message, unpacking it into individual messages, and publishing these messages.

[0007] DE 10 2021 114 282 A1 relates to a method for runtime-based configuration of internal signal transmission in a control unit, in which, during startup, publisher components provide at least one publisher list of the signals they provide, and subscriber components provide at least one subscriber list of the signals they require. The method provides for determining the signal path from a publisher component to a subscriber component for each required signal and grouping signals with identical signal paths into a signal group, for which a common transmission command is then stored in the runtime environment.

[0008] KR 10-2022-0027711 A concerns a routing service system for a data distribution service (DOS) that uses intelligent topic compression to implement low latency. The system connects two local area networks (LANs) via a wide area network (WAN) and enables efficient data management through intelligent topic compression. This approach uses payload and data size information to selectively compress data to optimize transmission.

[0009] CN 1 16 546 046 A provides a method and apparatus for data transmission processing, a control device, and a storage medium aimed at improving data processing efficiency. The method involves collecting data from field devices via sensors, determining the data type, and applying preconfigured transmission strategies based on the respective data type. The data is then transmitted to the edge IoT for processing. This approach helps reduce network bandwidth and delays caused by large data transmissions, thus increasing data processing efficiency.

[0010] DE 10 2020 214 357 A1 relates to a method for transmitting messages in a communication network based on the MQTT protocol. A publisher sends messages to a broker, which forwards them to subscribers. Messages from a subscribed topic are aggregated by the broker while maintaining a maximum latency and transmitted collectively to the subscriber.

[0011] Against this background, an object of the present invention is to improve the transmission of messages between a first communication unit and a second communication unit.

[0012] According to a first aspect, a computer-implemented method for transmitting data in a communication system, in particular in a publish-subscribe system, comprising a first communication unit, a second communication unit, a first reduction unit, and a second reduction unit is proposed. The computer-implemented method comprises: a) receiving, by the first reduction unit, at least one original message from the first communication unit, wherein the at least one original message is associated with a topic, b) analyzing, by the first reduction unit, the at least one received original message with respect to at least one message property to obtain a first or a second specific transformation type from a plurality of different transformation types for the received original message, wherein the obtained first or second specific transformation type respectively indicates how the received original message is to be transformed and / or further processed, c) applying at least a first type of specific transformation action to the analyzed message depending on the obtained first specific transformation type to obtain at least one transformed message, wherein the at least one transformed message is associated with the topic or a modified topic corresponding to the obtained first specific transformation type, d) reconstructing, by the second reduction unit, the at least one transformed message based on the topic or modified topic of the at least one transformed message determined by the second reduction unit to obtain the original message or a modified original message, and e) transmitting the received original message or the received modified original message to the second communication unit.

[0013] With the computer-implemented method according to the first aspect, the transmission of messages between a first communication unit and a second communication unit is improved by the first and second reduction units interacting with each other to intelligently analyze the incoming original messages according to one or more message properties, to transform them according to a type of specific transformation action, and to reconstruct the original message from the transformed message on the receiver side in the second reduction unit, thus automatically reducing the load and optimizing the message transmission in the publish-subscribe system.

[0014] This has the technical effect of increasing the robustness of the message queue, as message traffic in the publish-subscribe system is handled more specifically, intelligently, and with less load. Since the first and second reduction units are designed as reusable, intelligent software libraries, they can easily contribute to the decoupling of publisher and subscriber. If parts of the publish-subscribe system are implemented in a cloud, this also advantageously reduces operating costs in public clouds.

[0015] Thus, the computer-implemented method according to the first aspect advantageously provides automatic and intelligent load and cost optimization of message transmission in a publish-subscribe system.

[0016] A computer-implemented method is a method that uses a computer, a computer network, or other programmable device, one or more features of which are implemented in whole or in part by means of a computer program.

[0017] The publish-subscribe system specifically comprises one or more publishers (corresponding to the first communication unit) that publish messages containing data, and one or more subscribers (corresponding to the second communication unit) that can subscribe to and receive the messages. The publishing and subscribing of messages is topic-based, with each published message being assigned to a specific topic or covering a specific topic. Therefore, the publish-subscribe system can also be referred to as a topic-based publish-subscribe system.

[0018] The first communication unit can also be referred to as a publisher-client or a publisher. The second communication unit can also be referred to as a subscriber-client or a subscriber.

[0019] In embodiments, the communication system may comprise a plurality of subscribers and thus a plurality of second communication units. The various subscribers may have different needs regarding their communication in the communication system, such as granularity, for example, including frequency and accuracy, or access paths.

[0020] If there are several subscribers in the communication system, these can be treated in particular according to one of the following options a) to c): Option a)

[0021] Each communication relationship is treated individually according to a given rule or recipe. Option b)

[0022] All subscribers are treated equally under the following conditions b1) to b3): b1) (Exceeding) all data requirements, for example including the required minimum throughput, the highest required minimum precision and the like. b2) Balancing the resulting costs, for example, including fragmentation and aggregation. It's possible that messages might become larger, and not every subscriber needs everything. However, these messages can be used by all subscribers. Thus, there are fewer messages / load / costs. b3) Use of dynamic scalability or adaptability. In some embodiments, a time series database can be used as the number of subscribers increases. In such a case, the remaining subscribers can perform aggregation themselves (see also point c) below). Option c)

[0023] Grouping of subscribers into equally treatable subsets. In extreme cases, i) only groups of 1 or ii) only one group can be used. For example, group 1 receives an average per minute, while group 2 only receives an average per 15 minutes.

[0024] In some embodiments, the subscribers can also change dynamically. In this case, the selected strategy can also be changed (see, for example, option b2) above). However, a basic configuration is preferably used that defines minimum requirements, for example, regarding persistence and later availability of historical data. This defines, for example, how long which data is retained and at what granularity. This can also influence or limit the optimizations a) to c) above.

[0025] Preferably, the publish-subscribe system can be implemented within an automation system. The automation system can be a system from the process industry, the chemical industry, the pharmaceutical industry, the petrochemical industry, or a system from the food and beverage industry. This also includes all systems from the manufacturing and production industry and systems in which, for example, cars or goods of all kinds are produced. Furthermore, the automation system can also be designed as an energy generation system, such as a wind turbine, a solar system, or a power plant, and / or as an energy distribution system. The publish-subscribe system can also be implemented, for example, within a micrologistics system.

[0026] According to a further embodiment, step a) comprises, before receiving: Transmit, by the second communication unit, a subscribe request to subscribe to the topic to receive messages concerning the topic.

[0027] According to a further embodiment, step e) comprises: Receiving, in response to the subscribe request transmitted in step a), by the second communication unit, the received original message associated with the topic or the received modified original message associated with the modified topic.

[0028] The publish-subscribe system according to the first aspect, for example, uses the MQTT protocol, which is why the topics that can be subscribed to are called "topics." Specifically, a topic refers to a specific content of a message, in particular the original message. Preferably, a topic is a specific topic or service of the publish-subscribe system to which a participant, e.g., the second communication unit, can subscribe. Subscribers in a topic-based publish-subscribe system receive all (cryptographically secured) messages published in the topics to which they are subscribed.

[0029] In particular, the publish-subscribe system comprises several different topics, e.g., the topic, a second topic, a third topic, and so on. An example of a topic is "measured sensor values ​​from a first communication unit" or "measured actuator movements from a third communication unit," which acts as an actuator in the publish-subscribe system. For example, once a communication unit has received sensor values, these sensor values ​​can be published in the form of a message related to the topic.

[0030] The first reduction unit is embodied, in particular, as an intelligent software library or as an intelligent publisher software library. The second reduction unit is preferably embodied as an intelligent software library or as an intelligent subscriber software library. The second reduction unit is thus the counterpart to the first reduction unit and receives the transformed messages. Depending on the type of specific transformation action—recognizable from the (modified) topic—it reacts to transformed messages and performs a counter-operation to the specific transformation action performed by the first reduction unit to restore the original message or a modified original message.

[0031] In particular, the first reduction unit, the second reduction unit, the first communication unit and / or the second communication unit are each dedicated units that are arranged spatially separated from one another.

[0032] Furthermore, a corresponding communication unit, e.g., the first communication unit or the second communication unit, can be designed as a field device. The field device can, for example, be a field device in an automation system or an automation installation. The field device can be an IoT device. In particular, a field device is a hardware and / or software-implemented unit that has or provides a specific functionality. Examples of field devices are sensors, actuators, robots, measuring devices, computers, and the like. Sensors can also be connected to field devices. Such field devices include, in particular, control computers or microcontrollers, such as a field-programmable gate array (FPGA). A field device can also be a single control device or a single device. However, a field device can also have a plurality of control devices or functional units, e.g.,are structurally interconnected and / or can interact functionally with each other. In this case, each control unit or functional unit included in the field device can be considered a field device connected to and / or dependent on the other control units or functional units.

[0033] Preferably, the subscribe request is a request transmitted by a communication unit, e.g., the second communication unit, to subscribe to messages and / or data relating to a specific topic published in the publish-subscribe system.

[0034] In particular, the received at least one converted message is transmitted indirectly from the first reduction unit to the second reduction unit. Indirect transmission occurs by transmitting the received at least one converted message depending on a database of the communication system, depending on a broker unit of the communication system, or depending on a first broker part and a second broker part.

[0035] Preferably, the topic remains the same when the message is transmitted through the publish-subscribe system if the second specific transformation type is performed, since in this case the message is not transformed, and thus the original message and thus also the original topic are retained. The topic is particularly changed when the first specific transformation type is performed, since in this case the original message is transformed, and thus the original message and its topic change and then refer to the transformed message. The specific transformation type, the original topic, and thus the transformation action can be derived from the topic. Thus, regardless of the first specific transformation type, it is recognizable from the transformed message and its changed topic that a modification or transformation of the original message has taken place.

[0036] If the analysis in step b) shows that the second specific transformation type was received, the original message is not transformed and is further processed without transformation and transmitted to the second reduction unit. However, if the analysis in step b) shows that the first specific transformation type was received, the original message is transformed and further processed according to one of the first types of specific transformation action and then transmitted to the second reduction unit.

[0037] In particular, specific transformation actions applied can be tracked and stored in a history database of the communication system. Artificial intelligence algorithms, such as deep learning or machine learning, can then be applied to the stored specific transformation actions to automatically derive future predictions about message traffic and / or the number of messages, the size of the messages, and / or the time of message transmission. This also reduces the burden on message transmission in the publish-subscribe system.

[0038] Preferably, an additional peer-to-peer communication can be implemented to coordinate the procedure between the first communication unit and the second communication unit.

[0039] Metadata regarding the selected specific transformation type and its transformation action type can also be transmitted in a form understandable to the first and / or second communication unit or stored at a specified location in the communication system. This opens up the possibility, in particular, of incorporating the behavior of the first and / or second communication unit (the clients) into the selection of the specific transformation action.

[0040] The respective unit, for example, the first or second communication unit, can be implemented in hardware and / or software. In a hardware implementation, the respective unit can be embodied as a device or as part of a device, for example, as a computer or a microprocessor. In a software implementation, the respective unit can be embodied as a computer program product, as a function, as a routine, as part of a program code, or as an executable object.

[0041] In particular, the first type of specific transformation action describes how the analyzed message is transformed depending on the obtained first transformation type in order to obtain the at least one transformed message.

[0042] Preferably, in step d) a counter-operation to step c) is carried out by means of reconstruction in order to at least partially undo the specific transformation action carried out in step c) in order to obtain the original message or the modified original message.

[0043] The received modified original message contains at least parts of the data or content of the original message. These parts of the data or content may be present in a reduced or modified form in the modified original message.

[0044] In particular, step c) is carried out by the first reduction unit.

[0045] According to one embodiment, the method comprises: f) Executing, by the second communication unit, an application on the second communication unit depending on the transmitted original message or the transmitted modified original message, wherein the execution of the application comprises at least controlling a machine of the communication system by means of the application.

[0046] An application is, in particular, a program or service, especially a microservice, that is run on the second communication unit or to which the second communication unit has access. The same applies analogously to the further application and the first communication unit.

[0047] A machine or physical machine in the communication system is a technical structure with parts moved by a drive system. For example, the machine is designed as a turbine or an engine.

[0048] According to a further embodiment, step a) comprises, before receiving: Acquisition of data, in particular sensor data of a technical system in the communication system, by the first communication unit by means of a further application, and Transfer the captured data as part of the original message with the associated topic to the first reduction unit.

[0049] A technical system can be a robot, an automation system with various sensors and actuators and / or a power generation system.

[0050] According to a further embodiment, step a) further comprises, prior to receiving: Incorporating relevance and / or a reference into the original message, and Transferring the original message with the associated topic and memorized relevance and / or cue to the first reduction unit.

[0051] A hint and / or relevance can specify a specific maximum size for the messages to be transmitted. For example, the first communication unit provides a hint that only messages with a maximum size of 0.1 megabytes may be transmitted, as larger messages are more costly.

[0052] A note may also include configuration parameters of the message queue or publish-subscribe system, such as the maximum message size, throughput metrics, and / or cloud cost models.

[0053] In addition, a notice may contain current message queue metrics or metrics of the publish-subscribe system, such as an online query of the queue length and / or the size of an internal persistence store used.

[0054] Preferably, memorizing the hint and / or the relevance serves to improve the message transmission between the first reduction unit and the second reduction unit in order to further improve the relief of the message transmission.

[0055] According to a further embodiment, step a) further comprises, prior to receiving: Publishing, by the first communication unit, the original message associated with the topic in the publish-subscribe system.

[0056] According to a further embodiment, the message property is configured as the size, as a frequency of arrival, as a content and / or as information in a header of the at least one received original message, wherein the message property further comprises specific configuration properties and / or specific cost-benefit models.

[0057] Preferably, the message property is configured as the size of the at least one received original message, as a frequency of arrival of the at least one received original message and / or as a content of the at least one received original message.

[0058] Specific configuration properties are exchanged, in particular, as a configuration file between the first communication unit (and its further application) and the first reduction unit, and are preferably stored in the first reduction unit. Furthermore, it is possible to exchange such specific configuration properties in the form of at least one configuration file between the first and second reduction units, for example via a side channel or via further messages with further topics, so that both reduction units have information about the respective specific configuration properties. These specific configuration properties can then be used in step b) for determining and configuring the first or second specific conversion types.An example of such a specific configuration property is that an average value of sensor data from the further application should be transmitted every 5 minutes.

[0059] Specific cost-benefit models are known, in particular, to the first and second reduction units and can also be used as message properties in step b). Examples include IoT Core Pricing [4], per-message costs, message size costs, region-based costs, and / or persistence costs.

[0060] According to a further embodiment, the first type of specific transformation action is designed as a splitting action, wherein the application of the splitting action designed as a first type of specific transformation action according to step c) comprises splitting the analyzed message into individual packets to obtain the at least one transformed message comprising a plurality of individual packets, wherein the reconstruction according to step d) comprises merging the plurality of individual packets from the transformed message to obtain the original message.

[0061] In particular, during this splitting action, the analyzed message is split into individual packets, for example, for cost reasons in public clouds or in the case of very large messages. Subsequently, in step d), the multiple individual packets are recombined in the second reduction unit and transmitted to the second communication unit as a single packet in the form of the original message.

[0062] According to a further embodiment, the first type of specific transformation action is designed as a partial transformation action, wherein the application of the partial transformation action designed as a first type of specific transformation action according to step c) comprises a partial transformation of the analyzed message to obtain the at least one transformed message, wherein the reconstruction according to step d) comprises a reconstruction of a part of the transformed message to obtain the modified original message.

[0063] In this embodiment, the content of the message is modified during the partial transformation action so that a modified original message is obtained.

[0064] The partial transformation takes place in particular depending on the specific configuration properties and / or the specific cost-benefit models, so that both the sender-side first reduction unit and the receiver-side second reduction unit have information about the specific configuration properties and / or specific cost-benefit models according to which steps c) and d) are carried out.

[0065] According to a further embodiment, the partial transformation of the analyzed message comprises splitting the analyzed message into a plurality of individual packets, wherein during the reconstruction according to step d) only a part of the plurality of individual packets is reconstructed and incorporated into the modified original message in order to obtain the modified original message.

[0066] For example, it is no longer necessary to transmit each individual packet. Therefore, only a portion of the majority of individual packets is reconstructed and incorporated into the modified original message, which is then transmitted to the second communication unit via the second reduction unit.

[0067] According to a further embodiment, the partial transformation of the analyzed message comprises determining a time-dependent average over a certain number of data points of the analyzed message to obtain a time-dependent average of the analyzed message, wherein in the reconstruction according to step d), the obtained time-dependent average is incorporated into the modified original message to obtain the modified original message.

[0068] In particular, a minute-by-minute or hourly average is determined over the specific number of data points of the analyzed message (or an aggregation is determined over the specific number of data points) in order to avoid transmitting all individual data points of the analyzed message and thus reduce the load in the message communication between the first and second communication units. Thus, the original message is also changed to a modified original message containing the obtained time-dependent average, for example, a minute-by-minute average.

[0069] According to a further embodiment, the first type of specific transformation action is designed as a bundling action, wherein the application of the bundling action designed as a first type of specific transformation action according to step c) comprises bundling a plurality of analyzed messages depending on a bundling property to obtain the at least one transformed message, wherein the reconstruction according to step d) comprises splitting the plurality of analyzed messages from the transformed message to obtain the original message.

[0070] The original message is then transmitted to the second communication unit.

[0071] The bundling property specifies, in particular, when the at least one converted message is bundled and then transmitted to the second reduction unit. The bundling property is, in particular, embodied as a specific number of messages, a volume, or a time interval.

[0072] In other words, the bundling property specifies a specific number of messages, for example, 100 messages. The system waits until this specific number of messages is reached, or until they have arrived at the first reduction unit. Once this specific number of messages is reached, they are bundled and transformed and transferred to the second reduction unit. The same procedure applies analogously to further implementations of the bundling property.

[0073] If the time interval between two incoming analyzed messages is too large, a current message bundle is transmitted and the mechanism starts again.

[0074] According to a further embodiment, the first type of specific transformation action is designed as a database action, wherein the application of the database action designed as a first type of specific transformation action according to step c) comprises an indirect transformation of the analyzed message via a database of the communication system to obtain the at least one transformed message, wherein the transformed message has information about a storage location of the database or information about further configuration properties, wherein the database is designed in particular as a time series database, wherein the reconstruction according to step d) comprises at least one accessing of the storage location of the database to retrieve the transformed message from the storage location of the database to obtain the original message.

[0075] The database is designed specifically as an AWS S3 bucket or as a time series database.

[0076] The additional configuration properties include the specific configuration properties.

[0077] In this embodiment, the original message is modified to indicate the storage location of the now transformed message. The stored transformed message is then retrieved from the transmitted storage location and forwarded to the second communication unit by the second reduction unit.

[0078] The storage location of the database is located in particular in the communication system.

[0079] If the transformed message comprises information about further configuration properties, the reconstruction according to step d) may comprise accessing a configuration file comprising at least some of the further configuration properties in order to retrieve the transformed message by means of the configuration file to obtain the original message.

[0080] According to a further embodiment, the first type of specific transformation action is designed as a change action, wherein the application of the change action designed as a first type of specific transformation action according to step c) comprises converting a format of the at least one analyzed message depending on a change property to obtain the at least one transformed message, wherein the reconstruction according to step d) comprises re-formatting the transformed message to obtain the original message.

[0081] A modification property is, for example, the type of compression method used to change the format of at least one analyzed message. Examples of compression method types are ZIP or LZW.

[0082] A modification property can also be a specific protocol into which the format of at least one analyzed message is changed. An example of this is the "Protocol Buffers" protocol.

[0083] In particular, the format conversion has an opposite operation to the change action in order to get the original message back.

[0084] According to a further embodiment, step c) further comprises: Performing a second type of specific transformation action of the analyzed message depending on the obtained second specific transformation type to obtain the at least one original message, wherein performing the second type of specific transformation action according to step c) does not involve any change to the at least one analyzed message, wherein step e) further comprises: Transmitting the received at least one original message to the second communication unit.

[0085] In this embodiment, no transformation of the original message is performed and the original message is transmitted as it is via the second reduction unit to the second communication unit.

[0086] According to a further embodiment, the communication system further comprises a broker unit, wherein step c) further comprises: Transferring the at least one transformed or original message to a transmitting unit of the communication system, Sending, by the sending unit, at least one transferred transformed or original message to the broker unit, Processing, by the broker unit, at least one transmitted transformed or original message, Transmitted, by the broker unit, at least one processed transformed or original message to a receiving unit of the communication system, Passing, by the receiving unit, the at least one transmitted transformed or original message to the second reduction unit.

[0087] A broker unit is, in particular, a message broker unit. In particular, the broker unit is an MQTT broker unit. When using the broker unit in the publish-subscribe system, the providers of information / messages (publisher, first communication unit) do not have a direct connection to specific consumers of this information / message (subscriber, second communication unit). Instead, the interactions between publishers and subscribers are controlled by the broker unit. This means that within the publish-subscribe system with a broker unit, the respective communication units, for example, the first and / or second communication units, are loosely coupled and communicate only via the broker unit and not directly with each other.In detail, publications (messages) are sent from the publishers to the broker unit and subscribe requests are sent from the subscribers to the broker unit, and the broker unit forwards the published messages to the subscribers.

[0088] According to a further embodiment, step a) comprises: Transmit a subscribe request to the broker unit.

[0089] According to a further embodiment, step c) comprises: Receiving, in response to the transmitted subscribe request, by the receiving unit, at least one processed transformed or original message from the broker unit.

[0090] According to a further embodiment, the broker unit is divided into at least a first broker part and a second broker part, wherein the first broker part is implemented in the first communication unit and the second broker part is implemented in the second communication unit.

[0091] If the publish-subscribe system is implemented without the (central) broker unit (brokerless publish-subscribe architecture) or using the first broker part and the second broker part, all communication units participating in the publish-subscribe system can implement a distributed database to exchange messages among themselves via point-to-point connections. This is implemented, in particular, using the "Data Distribution Service (DDS)" or "ZeroMQ."

[0092] Then, the published messages, as well as information concerning the first and second communication units, the first and second reduction units, and the first and second broker parts, can be synchronized between all communication units, reduction units, and broker parts of the publish-subscribe system using the consensus procedure. In particular, in this case, the information providers (publishers, first communication units) have a direct communication connection to specific consumers of this information (subscribers, second communication units). This means that within the publish-subscribe system without a broker unit, the respective communication units, e.g., the first and / or second communication units, are directly coupled and can communicate directly with each other.

[0093] Any embodiment of the first aspect may be combined with any embodiment of the first aspect to obtain another embodiment of the first aspect.

[0094] According to a second aspect, a computer program product is proposed which comprises instructions which, when the program is executed by a computer, cause the computer to carry out the above-described computer-implemented method according to the first aspect or embodiments of the first aspect.

[0095] A computer program product, such as a computer program means, can be provided or delivered, for example, as a storage medium, such as a memory card, USB stick, CD-ROM, DVD, or in the form of a downloadable file from a server in a network. This can be done, for example, in a wireless communications network by transmitting a corresponding file with the computer program product or the computer program means.

[0096] According to a third aspect, a communication system, in particular a publish-subscribe system, for transmitting data comprising a first communication unit, a second communication unit, a first reduction unit, and a second reduction unit is proposed. The first reduction unit is configured to to receive at least one original message from the first communication unit, wherein the at least one original message is associated with a topic, to analyze the at least one received original message with respect to at least one message property to obtain a first or a second specific transformation type from a plurality of different transformation types for the received original message, wherein the obtained first or second specific transformation type respectively indicates how the received original message is to be transformed and / or further processed, and to apply a first type of specific transformation action to the analyzed message depending on the obtained first specific transformation type to obtain at least one transformed message, wherein the at least one transformed message is associated with the topic or a modified topic corresponding to the obtained first specific transformation type, wherein the second reduction unit is configured to to reconstruct the at least one transformed message based on the topic or modified topic of the at least one transformed message determined by the second reduction unit to obtain the original message or a modified original message, and to transmit the received original message or the received modified original message to the second communication unit.

[0097] According to an embodiment of the third aspect, the first communication unit is further configured to acquire data, in particular sensor data of a technical installation in the communication system, by means of a further application and to transmit the acquired data as part of the original message with the associated topic to the first reduction unit, wherein the second communication unit is further configured to execute an application on the second communication unit depending on the transmitted original message or the transmitted modified original message, wherein the execution of the application comprises at least controlling a machine of the communication system by means of the application.

[0098] The technical effects and advantages described for the computer-implemented method according to the first aspect apply equally to the communication system according to the third aspect.

[0099] Furthermore, the embodiments and features described for the computer-implemented method according to the first aspect also apply mutatis mutandis to the communication system according to the third aspect.

[0100] Further possible implementations of the invention also include combinations of features or embodiments described above or below with regard to the exemplary embodiments not explicitly mentioned. In this case, the person skilled in the art will also add individual aspects as improvements or additions to the respective basic form of the invention. Regardless of the grammatical gender of a particular term, persons with male, female, or other gender identities are included.

[0101] Further advantageous embodiments and aspects of the invention are the subject of the dependent claims and the exemplary embodiments of the invention described below. The invention will be explained in more detail below using preferred embodiments with reference to the accompanying figures. Fig. 1 shows a schematic block diagram of a communication system for transmitting data according to one embodiment; Fig. 2 shows a schematic flow diagram of a computer-implemented method for transmitting data; and Fig. 3 shows a schematic block diagram of a communication system for transmitting data according to another embodiment.

[0102] In the figures, identical or functionally equivalent elements have been given the same reference numerals unless otherwise stated.

[0103] Fig. 1 shows a schematic block diagram of a communication system 100 for transmitting data according to one embodiment. The communication system 100 is shown in Fig. 1 is designed as a publish-subscribe system. In addition, references to the process steps of the Fig. 2, which describes a computer-implemented method for transmitting data, in parentheses in the following explanations to Fig. 1 is specified.

[0104] The communication system 100 comprises a first communication unit 10, a second communication unit 20, a first reduction unit 11 and a second reduction unit 21.

[0105] The transmission of an original message N1 from the first communication unit 10 to the second communication unit 20 via various paths is described below.

[0106] First, the first communication unit 10 is configured to acquire data, in particular sensor data of a technical installation (not shown) in the communication system 100, by means of a further application and to transmit the acquired data as part of at least the original message N1 with an associated topic to the first reduction unit 11 (see also method step S10 in Fig. 2) (cf. Fig. 1, the original message N1 formed as an arrow from the first communication unit 10 to the first reduction unit 11).

[0107] Subsequently, the first reduction unit 11 is configured to receive the at least one original message N1 from the first communication unit 10, wherein the at least one original message N1 is assigned to the topic (see also method step S10 in Fig. 2).

[0108] In addition, the first reduction unit 11 is configured to analyze the at least one received original message N1 with respect to at least one message property in order to obtain a first or a second specific transformation type from a plurality of different transformation types for the received original message N1 (see also method step S20 in Fig. 2). The received first or second specific transformation type indicates how the received original message N1 is to be transformed and / or further processed.

[0109] The message property in Fig. 1 is formed as the size, as a frequency of arrival, as a content or as information in a header of the at least one received original message N1, wherein the message property further comprises specific configuration properties or specific cost-benefit models.

[0110] Thereafter, the first reduction unit 11 is configured to apply a first type of specific transformation action to the analyzed message N1 depending on the obtained first specific transformation type to obtain at least one transformed message N2. The at least one transformed message N2 is assigned to the topic or a modified topic that corresponds to the obtained first specific transformation type (see also method step S30 in Fig. 2).

[0111] Furthermore, the communication system 100 further comprises a broker unit 30. Accordingly, based on the Fig. 1 below shows the path of the transformed or original message N1, N2 via the broker unit 30 (see also process step S30 in Fig. 2).

[0112] As in Fig. 1, the first reduction unit 11 is configured to transfer the at least one converted or original message N1, N2 to a transmitting unit 12 of the communication system 100. The transmitting unit 12 is then configured to transmit the at least one transferred converted or original message N1, N2 to the broker unit 30 (see FIG. Fig. 1, the original message N1, N2 formed as an arrow from the first reduction unit 11 via the transmitting unit 12 to the broker unit 30).

[0113] Now, the broker unit 30 is configured to process the at least one transmitted transformed or original message N1, N2 and subsequently to transmit it to a receiving unit 22 of the communication system 100 (cf. Fig. 1, the original message N1, N2 formed as an arrow from the broker unit 30 to the receiving unit 22).

[0114] The receiving unit 22 is then configured to transfer the at least one transmitted transformed or original message N1, N2 to the second reduction unit 21 (cf. Fig. 1, the original message N1, N2 formed as an arrow from the receiving unit 22 to the second reduction unit 21).

[0115] Alternatively, the original message N1 can be transmitted via a database 40 of the communication system 100 to the second reduction unit 21 as follows: The first type of specific transformation action is designed as a database action. The application of the database action designed as a first type of specific transformation action according to step c) (cf. method step S30 in Fig. 2) comprises an indirect transformation of the analyzed message N1 via the database 40 to obtain the at least one transformed message N2 (cf. Fig. 1, the original message N1, formed as an arrow, from the first reduction unit 11 to the database 40). The transformed message N2 has information about a storage location of the database 40 or information about further configuration properties, wherein the database 40 is in Fig. 1 is designed as a time series database.

[0116] The reconstruction according to step d) (see process step S40 in Fig. 2) comprises at least one access to the storage location of the database 40 for retrieving the transformed message N2 from the storage location of the database 40 for obtaining the original message N1 (cf. Fig. 1, the transformed message N2 formed as an arrow with two ends between the database 40 and the second reduction unit 21).

[0117] Subsequently, the second reduction unit 21 is configured to reconstruct the at least one transformed message N2 based on the topic or modified topic of the at least one transformed message N2 determined by the second reduction unit 21 in order to obtain the original message N1 or a modified original message N3 (cf. also method step S40 in Fig. 2).

[0118] Then, the second reduction unit 21 is further configured to transmit the received original message N1 or the received modified original message N3 to the second communication unit 20 (see also method step S50 in Fig. 2) (cf. Fig. 1, the original message N1 formed as an arrow or the received modified original message N3 from the second reduction unit 21 to the second communication unit 20).

[0119] The second communication unit 20 is then further configured to execute an application on the second communication unit 20 depending on the transmitted original message N1 or the transmitted modified original message N3 (see also method step S60 in Fig. 2). Executing the application involves controlling a machine of the communication system 100 using the application.

[0120] Both the first communication unit 10 (Publisher) and the second communication unit 20 (Subscriber) use Fig. 1 a respective intelligent software library (first reduction unit 11 and second reduction unit 21) instead of directly using the Pub / Sub library of the message queue or the broker unit 30.

[0121] The first and second reduction units 11, 21 internally use a Pub / Sub middleware (software), such as MQTT, via a corresponding Publisher / Subscriber library, both to exchange information between the intelligent software libraries and to transfer application data. Fig. 1, this corresponding publisher library is integrated in the transmitting unit 12, while the corresponding subscriber library is integrated in the receiving unit 22.

[0122] Several possibilities for specific transformation actions are explained below: First option

[0123] Here, the first type of specific transformation action is designed as a splitting action. The application of the splitting action designed as a first type of specific transformation action according to step c) (see also method step S30 in Fig. 2) splitting the analyzed message N1 into individual packets to obtain the at least one transformed message N2 comprising several individual packets, wherein the reconstruction according to step d) (see also method step S40 in Fig. 2) merging the multiple individual packets from the transformed message N2 to obtain the original message N1. Second option

[0124] In this case, the first type of a specific forming action is designed as a partial forming action. In this case, the application of the partial forming action designed as a first type of a specific forming action according to step c) (cf. also method step S30 in Fig. 2) a partial transformation of the analyzed message N1 to obtain the at least one transformed message N2, wherein the reconstruction according to step d) (see also method step S40 in Fig. 2) reconstructing a part of the transformed message N2 to obtain the modified original message N3.

[0125] The partial transformation of the analyzed message N1 comprises splitting the analyzed message N1 into a plurality of individual packets, wherein during the reconstruction according to step d) (see also method step S40 in Fig. 2) only a part of the plurality of individual packets is reconstructed and incorporated into the modified original message N3 in order to obtain the modified original message N3.

[0126] In addition, the partial transformation of the analyzed message N1 comprises determining a time-dependent average over a certain number of data points of the analyzed message N1 to obtain a time-dependent average of the analyzed message N1, wherein in the reconstruction according to step d) (cf. also method step S40 in Fig. 2) the obtained time-dependent mean value is incorporated into the modified original message N3 to obtain the modified original message N3.

[0127] As in Fig. 1, the modified original message N3 can also be transmitted via the transmitting unit 12, via the broker unit 30, via the receiving unit 22 to the second reduction unit 21. Third option

[0128] In this case, the first type of specific transformation action is designed as a bundling action. In this case, the application of the bundling action designed as a first type of specific transformation action according to step c) (cf. also method step S30 in Fig. 2) bundling several analyzed messages N1 depending on a bundling property to obtain the at least one transformed message N2, wherein the reconstruction according to step d) (see also method step S40 in Fig. 2) splitting the plurality of analyzed messages N1 from the transformed message N2 to obtain the original message N1. Fourth option

[0129] Furthermore, the first type of specific transformation action is designed as a change action in this case. The application of the change action designed as a first type of specific transformation action according to step c) (see also method step S30 in Fig. 2) converting a format of the at least one analyzed message N1 depending on a change property to obtain the at least one transformed message N2, wherein the reconstruction according to step d) (cf. also method step S40 in Fig. 2) a format reconversion of the transformed message N2 to obtain the original message N1. Fifth option

[0130] Also, sometimes a transformation of the original message N1 is not necessary. For example, method step S30 (see Fig. 2) furthermore the step on: Carrying out a second type of specific transformation action of the analyzed message N1 as a function of the obtained second specific transformation type in order to obtain the at least one original message N1, wherein carrying out the second type of specific transformation action according to step c) does not involve any change to the at least one analyzed message N1, wherein step e) S50 (cf. Fig. 2) further comprises: Transmitting the received at least one original message N1 to the second communication unit 20.

[0131] As in Fig. 1, the original message N1 can thus also be transmitted via the transmitting unit 12, via the broker unit 30, via the receiving unit 22 to the second reduction unit 21.

[0132] Fig. 2 shows a schematic flow diagram of a computer-implemented method for transmitting data in a communication system 100 (cf. Fig. 1) comprising a first communication unit 10 (cf. Fig. 1), a second communication unit 20 (cf. Fig. 1), a first reduction unit 11 (cf. Fig. 1) and a second reduction unit 21 (cf. Fig. 1). The respective process steps S10 - S50 of the computer-implemented process have already been described above with reference to Fig. 1, which is why, to avoid repetition, the method steps S10 - S50 are not explained again here. This also applies to method step S60, which forms an embodiment of the method steps S10 - S50 of the computer-implemented method and is therefore Fig. 2 is connected to the process steps S10 - S50 via a dashed line.

[0133] Fig. 3 shows a schematic block diagram of a communication system 100 (see also Fig. 1) for transmitting data according to another embodiment. Fig. 3 shows an application case of the communication system 100 in an industrial environment.

[0134] Fig. 3 has all components of the Fig. 1, which is why they will not be explained in detail again. Fig. 3 in the frontend FE a frontend subscriber client 28 with a software program 27, which is designed as an Angular JS client program. The frontend subscriber client 28 obtains its data via a Pub / Sub client library (receiving unit 22 in Fig. 3) or via a broker unit 30 from the backend BE, for example, current values ​​of a system, which are displayed in a diagram and updated regularly (e.g. every 5 s (seconds)). Alternatively, the respective broker unit 30 can be Fig. 3 can also be implemented as a websocket or an S3 client (Simple Storage Service). Furthermore, there can be many instances of this frontend subscriber client 28 that require the data simultaneously (for example, 10,000 users (not shown)).

[0135] In addition, the frontend FE is Fig. 3, a frontend publisher client 19 is arranged, which has a first communication unit 10 and a transmitting unit 12. The frontend publisher client 19 sends its generated data via a Pub / Sub client library (transmitting unit 12 in Fig. 3) to the backend BE, in particular again to a further broker unit 30, which can be designed according to one of the embodiments of the broker unit 30, which transmits the data to the frontend subscriber client 28.

[0136] The values ​​of this generated data are provided by the frontend publisher client 19 in a higher resolution, for example, a measurement value every 100 ms (milliseconds). The frontend FE in Fig. 3 is arranged in particular in a cloud cld (public cloud) or locally in a data center or a computer of the communication system 100.

[0137] The backend BE has Fig. 3 comprises a data acquisition unit 50, a database 40, several broker units 30, a first backend subscriber client 15 and a second backend subscriber client 16. The backend in Fig. 3 is located in the cloud cld.

[0138] The multiple broker units 30 in Fig. 3 can, but do not have to, use the same technologies and be the same broker instances (e.g. S3, AWS IoT Core, Websocket).

[0139] The data acquisition unit 50 has Fig. 3 comprises a transmitting unit 12, a data acquisition program 50a and the first reduction unit 11. The first backend subscriber client 15 has Fig. 3, the second communication unit 20, the second reduction unit 21 and a first subscriber program 23. Furthermore, the second backend subscriber client 16 in Fig. 3 comprises a third communication unit 24, a third reduction unit 25, and a second subscriber program 26. The third reduction unit 25, like the second reduction unit 21, is configured as an intelligent subscriber library. The third communication unit 24 is also configured as a subscriber or subscriber client.

[0140] In Fig. Figure 3 illustrates a case in which additional subscribers, such as the first backend subscriber client 15, require the data from the frontend publisher client 19 in this higher resolution (one measurement value every 100 ms), with the first backend subscriber client 15 executing a batch job on the high-resolution data once a day. Therefore, the data should not be reduced to 5 seconds (one measurement value every 5 seconds) at the frontend publisher client 19. Furthermore, in this case, the data must be persisted accordingly, in addition to the event stream, for example, in a database 40, for example, a time series database such as Influx or in a cloud data store such as AWS S3 (see the arrows representing the messages N1, N2 between the data ingestion unit 50, the database 40, and the first backend subscriber client 15 and / or the second backend subscriber client 16).

[0141] For this case, there is the data ingestion unit 50, also referred to as an “ingester,” which subscribes to the measured values ​​of the frontend publisher client 19 or receives them in another way from the frontend publisher client 19 (e.g., via a REST API, S3 upload (which are embodiments of the broker unit 30)).

[0142] The data ingestion unit 50 uses the first reduction unit 11 to further distribute the data received from the front-end publisher client 19 via the broker unit 30, optimizing load and costs. In the simplest case, the data ingestion unit 50 simply forwards the events (messages). The first reduction unit 11 can also process the data or the original message N1 according to one of the Fig. 1 to obtain the transformed message N2. This can then be forwarded via the broker unit 30 to the first backend subscriber client 15 and / or the second backend subscriber client 16 (cf. Fig. 3, the transmission of the messages N1, N2 from the data acquisition unit 50 via the broker unit 30 to the first backend subscriber client 15 and to the second backend subscriber client 16).

[0143] Subsequently, the second reduction unit 21 and / or the third reduction unit 25 carries out step d) (cf. step S40 in Fig. 2) depending on the respective in step c) (see step S30 in Fig. 2) specific transformation action is carried out again to obtain the original message N1 (see also Fig. 1) or the modified original message N3 (see also Fig. 1). The original message N1 and the modified original message N3 are then each sent via the broker unit 30 to the frontend subscriber client 28 (cf. Fig. 3, the arrows representing the messages N1, N3, respectively starting from the second reduction unit 21 or the third reduction unit 25 to the frontend subscriber client 28).

[0144] If necessary, the data ingestion unit 50 writes the data to the time series database. In this case, the data ingestion unit 50 could publish one or more events (e.g., only one message or part of a message) instead of the full event stream (e.g., multiple messages) to notify the first backend subscriber client 15 and the second backend subscriber client 16 that new data is available. The database 40 could, for example, also filter for 5s events itself.

[0145] In this example in Fig. 2 there are two intelligent subscribers, namely the first backend subscriber client 15 (designed as a “data processor”) and the second backend subscriber client 16 (designed as a “non-direct speed processor”).

[0146] The second backend subscriber client 16 is satisfied with one aggregated data point every 5 seconds.

[0147] The first backend subscriber client 15, on the other hand, wants the full data, but retrieves it directly from the database 40, possibly once in a batch.

[0148] Therefore, depending on the cloud costs, a possible best solution of the intelligent Pub / Sub layer would be to write the data completely into the time series database 40 on the data ingestion unit 50 side and additionally to forward a current data point every 5 seconds via a broker unit 30 to the respective backend subscriber client 15, 16.

[0149] The third reduction unit 25 would initially execute a query on the database 40 upon loading the frontend page to retrieve the data for the area to be displayed and then continuously forward the latest data points to the running frontend clients, for example, the frontend subscriber client 28. In the first backend subscriber client 15, the second reduction unit 21 would simply perform a database query for the relevant time period.

[0150] The frontend publisher client 19 and the frontend subscriber client 28 can also have a respective reduction unit (intelligent software library). Fig. 3 is an example scenario that is particularly applicable if these components (frontend publisher client 19 and the frontend subscriber client 28) cannot or should not use the reduction units 11, 21 and 25 in the respective intelligent clients 15, 16 and 50 for whatever reason, for example in the case of legacy components.

[0151] Compared to the state of the art [3], the following differences and advantages arise: In the Lambda architecture according to Fig. the [3] the data acquisition unit 50 would be Fig. 3 from the top of the “Data Ingestion Layer” Fig. of [3], but without the intelligent reduction units 11, 21 and 25 of the Fig. 3 no automatically adjusted load to the “Speed ​​Layer” and the “Service Layer” of the Fig. the [3] (together see second backend subscriber client 16 of the Fig. 3) and to the “batch layer” of the Fig. of [3] (cf. “first backend subscriber client 15 of Fig. 3”) and no automatic use of a “master dataset” of the Fig. of [3] (cf. database 40, especially time series database, of Fig. 3) for load optimization.

[0152] In the Kappa architecture according to Fig. the [3] all data would always be included in the master dataset (cf. Fig. the [3]) and then completely transferred to the Speed ​​Layer (cf. Fig. of [3]) and then passed to the serving layer (cf. Fig. [3]) if this were not filtered by appropriate manual programming. The computer-implemented method according to the first aspect with the intelligent first and second reduction units 11, 21 provides a cost- and load-optimizing abstraction that solves this automatically.

[0153] Although the present invention has been described using exemplary embodiments, it can be modified in many ways. List of reference symbols 10 first communication unit 11 first reduction unit 12 Transmitter unit 15 first backend subscriber client 16 second backend subscriber client 19 Frontend Publisher Client 20 second communication unit 21 second reduction unit 22 Receiving unit 23 first subscriber program 24 third communication unit 25 third reduction unit 26 second subscriber program 27 software program 28 Frontend Subscriber Client 30 broker units 40 database 50 data acquisition unit 50a Data acquisition program 100 communication system cld Cloud BE Backend FE Frontend N1 original (analyzed) message N2 transformed message N3 modified original message S10 - S60 Process steps Reference list [1] https: / / en.wikipedia.org / wiki / Message_queue [2] https: / / aws.amazon.com / de / iot-core / [3] https: / / entwickler.de / software-architektur / lambda-vskappa / [4] https: / / aws.amazon.com / de / iot-core / pricing /

Claims

[1] Computer-implemented method for transmitting data in a communication system (100), in particular in a publish-subscribe system, comprising a first communication unit (10), a second communication unit (20), a first reduction unit (11) and a second reduction unit (21), the computer-implemented method comprising: a) receiving (S10), by the first reduction unit (11), at least one original message (N1) from the first communication unit (10), wherein the at least one original message (N1) is associated with a topic, b) analyzing (S20), by the first reduction unit (11), the at least one received original message (N1) with respect to at least one message property to obtain a first or a second specific transformation type from a plurality of different transformation types for the received original message (N1), wherein the obtained first or second specific transformation type each indicates how the received original message (N1) is to be transformed and / or further processed, c) applying (S30) at least a first type of specific transformation action to the analyzed message (N1) depending on the obtained first specific transformation type to obtain at least one transformed message (N2), wherein the at least one transformed message (N2) is associated with the topic or a modified topic corresponding to the obtained first specific transformation type, d) reconstructing (S40), by the second reduction unit (21), the at least one transformed message (N2) based on the topic or modified topic of the at least one transformed message (N2) determined by the second reduction unit (21) to obtain the original message (N1) or a modified original message (N3), and e) transmitting (S50) the received original message (N1) or the received modified original message (N3) to the second communication unit (20), wherein the communication system (100) further comprises a broker unit (30), wherein step c) (S30) further comprises: Transferring the at least one transformed or original message (N1, N2) to a transmitting unit (12) of the communication system (100), Sending, by the transmitting unit (12), the at least one transferred transformed or original message (N1, N2) to the broker unit (30), Processing, by the broker unit (30), the at least one transmitted transformed or original message (N1, N2), Transmitted by the broker unit (30) of the at least one processed transformed or original message (N1, N2) to a receiving unit (22) of the communication system (100), Transferring, by the receiving unit (22), the at least one transmitted transformed or original message (N1, N2) to the second reduction unit (21). [2] Method according to claim 1, characterized by : f) executing (S60), by the second communication unit (20), an application on the second communication unit (20) depending on the transmitted original message (N1) or the transmitted modified original message (N3), wherein the execution of the application comprises at least controlling a machine of the communication system (100) by means of the application. [3] Method according to claim 1 or 2, characterized by that step a) (S10) comprises, before receiving: Acquisition of data, in particular sensor data of a technical installation in the communication system (100), by the first communication unit (10) by means of a further application, and Transferring the captured data as part of the original message (N1) with the associated topic to the first reduction unit (11). [4] Method according to one of claims 1-3, characterized by in that the message property is formed as the size, as a frequency of arrival, as a content and / or as information in a header of the at least one received original message (N1), wherein the message property further comprises specific configuration properties and / or specific cost-benefit models. [5] Method according to one of claims 1-4, characterized bythat the first type of specific transformation action is designed as a splitting action, wherein the application of the splitting action designed as a first type of specific transformation action according to step c) (S30) comprises splitting the analyzed message (N1) into individual packets to obtain the at least one transformed message (N2) comprising a plurality of individual packets, wherein the reconstruction according to step d) (S40) comprises merging the plurality of individual packets from the transformed message (N2) to obtain the original message (N1). [6] Method according to one of claims 1-4, characterized bythat the first type of specific transformation action is designed as a partial transformation action, wherein the application of the partial transformation action designed as a first type of specific transformation action according to step c) (S30) comprises a partial transformation of the analyzed message (N1) to obtain the at least one transformed message (N2), wherein the reconstruction according to step d) (S40) comprises a reconstruction of a part of the transformed message (N2) to obtain the modified original message (N3). [7] Method according to claim 6, characterized by that the partial transformation of the analyzed message (N1) comprises splitting the analyzed message (N1) into a plurality of individual packets, wherein during the reconstruction according to step d) (S40) only a part of the plurality of individual packets is reconstructed and incorporated into the modified original message (N3) in order to obtain the modified original message (N3). [8] Method according to claim 6 or 7, characterized by that the partial transformation of the analyzed message (N1) comprises determining a time-dependent mean value over a certain number of data points of the analyzed message (N1) to obtain a time-dependent mean value of the analyzed message (N1), wherein in the reconstruction according to step d) (S40) the obtained time-dependent mean value is incorporated into the modified original message (N3) in order to obtain the modified original message (N3). [9] Method according to one of claims 1-4, characterized byin that the first type of specific transformation action is designed as a bundling action, wherein the application of the bundling action designed as a first type of specific transformation action according to step c) (S30) comprises bundling a plurality of analyzed messages (N1) depending on a bundling property to obtain the at least one transformed message (N2), wherein the reconstruction according to step d) (S40) comprises splitting the plurality of analyzed messages (N1) from the transformed message (N2) to obtain the original message (N1). [10] Method according to claim 8 or 9, characterized byin that the first type of specific transformation action is designed as a database action, wherein the application of the database action designed as a first type of specific transformation action according to step c) (S30) comprises an indirect transformation of the analyzed message (N1) via a database (40) of the communication system (100) to obtain the at least one transformed message (N2), wherein the transformed message (N2) comprises information about a storage location of the database (40) or information about further configuration properties, wherein the database (40) is designed in particular as a time series database, wherein the reconstruction according to step d) (S40) comprises at least one accessing of the storage location of the database (40) to retrieve the transformed message (N2) from the storage location of the database (40) to obtain the original message (N1). [11] Method according to one of claims 1-10, characterized byin that the first type of specific transformation action is designed as a change action, wherein the application of the change action designed as a first type of specific transformation action according to step c) (S30) comprises converting a format of the at least one analyzed message (N1) depending on a change property to obtain the at least one transformed message (N2), wherein the reconstruction according to step d) (S40) comprises a format re-conversion of the transformed message (N2) to obtain the original message (N1). [12] Method according to one of claims 1-11, characterized by that step c) (S30) further comprises: Performing a second type of specific transformation action of the analyzed message (N1) depending on the obtained second specific transformation type to obtain the at least one original message (N1), wherein performing the second type of specific transformation action according to step c) (S30) does not involve any change to the at least one analyzed message (N1), wherein step e) (S50) further comprises: Transmitting the received at least one original message (N1) to the second communication unit (20). [13] A computer program product comprising instructions which, when executed by a computer, cause the computer to carry out the computer-implemented method according to any one of claims 1-12. [14] Communication system (100), in particular publish-subscribe system, for transmitting data comprising a first communication unit (10), a second communication unit (20), a first reduction unit (11) and a second reduction unit (21), wherein the first reduction unit (11) is configured to to receive at least one original message (N1) from the first communication unit (10), wherein the at least one original message (N1) is associated with a topic, to analyze the at least one received original message (N1) with respect to at least one message property to obtain a first or a second specific transformation type from a plurality of different transformation types for the received original message (N1), wherein the obtained first or second specific transformation type respectively indicates how the received original message (N1) is to be transformed and / or further processed, and to apply a first type of specific transformation action to the analyzed message (N1) depending on the obtained first specific transformation type to obtain at least one transformed message (N2), wherein the at least one transformed message (N2) is associated with the topic or a modified topic corresponding to the obtained first specific transformation type, wherein the second reduction unit (21) is configured to to reconstruct the at least one transformed message (N2) based on the topic or modified topic of the at least one transformed message (N2) determined by the second reduction unit (21) to obtain the original message (N1) or a modified original message (N3), and transmitting the received original message (N1) or the received modified original message (N3) to the second communication unit (20), wherein the communication system (100) further comprises a broker unit (30), wherein step c) (S30) further comprises: Transferring the at least one transformed or original message (N1, N2) to a transmitting unit (12) of the communication system (100), Sending, by the transmitting unit (12), the at least one transferred transformed or original message (N1, N2) to the broker unit (30), Processing, by the broker unit (30), the at least one transmitted transformed or original message (N1, N2), Transmitted by the broker unit (30) of the at least one processed transformed or original message (N1, N2) to a receiving unit (22) of the communication system (100), Transferring, by the receiving unit (22), the at least one transmitted transformed or original message (N1, N2) to the second reduction unit (21). [15] Communication system according to claim 14, characterized byin that the first communication unit (10) is further configured to acquire data, in particular sensor data of a technical installation in the communication system (100), by means of a further application and to transmit the acquired data as part of the original message (N1) with the associated topic to the first reduction unit (11), wherein the second communication unit (20) is further configured to execute an application on the second communication unit (20) depending on the transmitted original message (N1) or the transmitted modified original message (N3), wherein the execution of the application comprises at least controlling a machine of the communication system (100) by means of the application.

Citation Information

Patent Citations

  • Data transmission processing method and device, control equipment and storage medium

    CN116546046A

  • Computer-implemented method for transmitting messages in a communication network based on an MQTT protocol

    DE102020214357A1

  • Computer-implemented method for transmitting individual messages using an MQTT protocol

    DE102020214358A1

  • Method for time-based configuration of an internal signal transmission in a control unit, as well as a correspondingly operable control unit and motor vehicle

    DE102021114282A1

  • Micro-sized metamaterial absorbers

    KR1020220125700A