METHOD AND DEVICE FOR RADIO TRANSMISSION OF DATA

Description

[0001] The invention relates to a method for the radio transmission of data, in particular building consumption, building sensor and / or building actuator data in a local building radio network. In the method, the data is sent and received in a telegram according to a defined standard, wherein the standard provides a standard data area for transmitting data and a proprietary area for transmitting manufacturer-specific data. The data is thus exchanged via a standard-compliant telegram, whereby the standard does not provide for an error correction method, but does provide for a proprietary area in the telegram. The defined standard is understood to mean protocols for radio transmission, including the definition of the telegrams, e.g., within the framework of the OSI layer model. According to the invention, the standard does not provide for an error correction method.The method can be used especially in a standard that does not provide for an error correction method, in particular no error correction method with Forward Error Correction (FEC).

[0002] The process of reading consumption values ​​from consumption recording devices, such as heat cost allocators, water meters, heat meters, or similar measuring devices or meters, is becoming increasingly automated. For this purpose, consumption and sensor data, for example from heat cost allocators, other consumption recording devices, or general measuring devices or meters, is often transmitted to data collectors, which collect the measurement data centrally in the building and transmit it to actuators within the building and / or to billing service providers. Such a data collector can be permanently installed in a central location or, alternatively, in a so-called drive-by reading in a vehicle or during a walk-by reading, can be brought close to the consumption recording devices and / or sensors by a meter reader to receive the consumption and / or sensor data transmitted by the measuring devices.A reading using the fly-by method using a remote-controlled aircraft is also known.

[0003] Today, radio systems are typically used to transmit and, if necessary, forward this building consumption and / or building sensor data within a building sensor network, for example. To ensure compatibility between transmitters and receivers from different manufacturers, standardized telegrams are used for radio transmission. Such standards, such as the OMS standard, do not currently provide for the transmission of error correction data, for example, for forward error correction (FEC).

[0004] Known error correction methods, such as the Reed-Solomon method, can be used to correct any transmission errors that may occur in the transmitted telegram after its reception, e.g., directly in the receiver, thus obtaining error-free data. This is achieved by redundantly encoding the data to be transmitted. These methods are particularly suitable for error correction in unidirectional radio systems.

[0005] In the paper "A Flexible Error Correction Scheme for IEEE 802.15.4-based Industrial Wireless Sensor Networks," Kann Yu et al. describes a method for forward error correction (FEC). This method uses error correction in conjunction with a special final error correction when a transmission error is detected by a checksum. The error correction data (FEC bits) are part of the complete telegram to be received. In such a system, error correction can only be implemented within the standard used.

[0006] References KAN YU ET AL, “Reliable and Low Latency Transmission in Industrial Wireless Sensor Networks,” PROCEDIA COMPUTER SCIENCE, vol. 5, doi:10.1016 / J.PROCS.2011.07.120, ISSN 1877-0509; KAN YU ET AL, "Adaptive forward error correction for best effort Wireless Sensor Networks", COMMUNICATIONS (ICC), 2012 IEEE INTERNATIONAL CONFERENCE ON, IEEE, (20120610), doi:10.1109 / ICC.2012.6364798, ISBN 978-1-4577-2052-9; KANN YU, "A Flexible Error Correction Scheme for IEEE 802.15.4-based Industrial Wireless Sensor Networks" and GIRS SVETLANA ET AL, "Adopting FEC and packet combining to increase the performance of IWSNs using relaying", 2015 INTERNATIONAL CONFERENCE ON COMPUTING AND NETWORK COMMUNICATIONS (COCONET), IEEE, (20151216), each describe methods for Forward Error Correction (FEC) that enable error correction in wireless transmission according to IEEE 802.15.4 protocol when a transmission error in the transmitted protocol has been detected using a checksum. It is therefore known that error correction methods can increase the radio range. Error correction should take place in certain hardware-related layers according to the OSI layer model, particularly the MAC layer, because transmission in the physical layer is generally not possible due to a lack of access to supplement a standard. The preferred concept according to Kan Yu et al., "Reliable and Low Latency Transmission in Industrial Wireless Sensor Networks," involves dividing the entire MAC layer packet into groups and encoding each group with a systematic FEC code, with the checksum field (FCS) explicitly excluded. Without FEC encoding, the data packet would otherwise be considered faulty. On the other hand, FEC decoding is time-consuming and leads to latency.With the preferred systematic FEC code, the original data code of the payload is preserved for the different groups, and redundant FEC data is appended to the original payload for each group. The FCS checksum is then calculated across the entire data packet, i.e., the original data code and the redundant FEC data.

[0007] WO 2015 / 974666 A1 describes an error correction method for telegrams containing two telegram parts with the payload and appended error correction data. However, the error correction data is only an optional telegram part that can be received, but does not have to be. This is achieved by ensuring that the first telegram part alone conforms to a transmission standard, so that the first telegram part can also be received independently of the other telegram part.

[0008] The standards used today for transmitting consumption, sensor and / or actuator data in a building via a local building radio network do not provide for such error correction for the telegrams and can therefore only be used for error-free transmission within a limited distance between the receiver and transmitter. If a greater transmission range is to be achieved using such a method, a significantly higher transmission power would have to be used. However, this is often not possible because the transmitters are usually battery-operated units. Since their battery capacity is usually low for cost reasons, only a limited battery and therefore transmission power is available to ensure the desired service life of the measuring or consumption recording devices can be reliably achieved. The level of transmission power can also be limited by regulatory requirements, e.g.European directives may be restricted.

[0009] The object of the present invention is therefore to provide a method with which a radio transmission of data, in particular consumption, sensor and / or actuator data in a building in a local building radio network is possible by means of a standard-compliant telegram even over longer ranges without loss of information, whereby this defined standard does not necessarily provide for an error correction method, in particular no FEC error correction method, and in which the data can be reconstructed simply and as completely as possible.

[0010] The above object is achieved by a method having the features of claim 1 and a device having the features of claims 11 and / or 12. In particular, it is provided that an error correction data record with error correction data for the telegram is transmitted in the proprietary area, which error correction data permits error correction of the data and / or the manufacturer-specific data in the event of transmission errors due to redundancy. In contrast to the error correction data and / or an identifier for the error correction in the error correction data record, the data and the manufacturer-specific data (possibly including possible data information in the header) are referred to as user data or payload. It is provided that this error correction data record is arranged at a position in the telegram that is defined relative to the end of the telegram.

[0011] In addition to the data points in the telegram specified in the standard for the data to be transmitted (i.e., the payload including header data), the standard also provides for a proprietary area in the sense of a data area within the telegram that is freely available to each individual manufacturer. Such a data area is often referred to in the standard as a "manufacturer-specific data area." It is therefore possible to transmit further manufacturer-specific data and / or additionally or alternatively error correction data for the telegram in this data area, the content of which is not specified in the standard, while the telegram remains fully standard-compliant. If an error occurs during transmission of the telegram, the error-free telegram can be reconstructed using the error correction data transmitted in the proprietary area.Due to the arrangement of the error correction data in the proprietary area, the error correction data is also referred to below as "manufacturer-specific data".

[0012] Since the exact position of the individual data points in the standard-compliant telegram is usually not specified, individual data points are located based on the position and length of the preceding data point. Due to this step-by-step determination of the positions of the individual data points, even a small error in a single preceding data point can result in the subsequent or following data points no longer being able to be reliably located. However, since the error correction data set must be located before error correction is performed, such a successive approach would likely result in the error correction data not being found in the event of a transmission error, and therefore the error correction cannot be performed.

[0013] Therefore, according to the invention, the error correction data record is located at a defined position relative to the end of the telegram. Upon receipt of the telegram, the end of the telegram can be determined based on its total length, which is transmitted in a length field in the telegram header. Since the error correction data record is located at a defined position relative to the end of the telegram, the data record can be located without having to evaluate the lengths and positions of the other individual data points, because the total telegram length is already determined from the header.

[0014] By integrating error correction into a standard-compliant telegram, the advantages of error correction can be used manufacturer-specifically without having to violate or change the standard, as is the case, for example, when additional information is appended to a standard-compliant telegram. The method according to the invention thus leads to greater error robustness and thus to a greater transmission range with the same transmission power. It is therefore possible to reduce the density of the receivers used for readings, thereby saving costs at the point of consumption. Another option is to reduce the transmission power while maintaining the same range. This leads to cost savings in the production of the devices used as transmitters, since, for example, the battery capacity can be reduced.

[0015] The protocol layers defined by the standard (e.g., in the sense of the OSI layer model) are adhered to and used in a standard-compliant manner. In particular, the hardware-related layers (physical layer and data link layer) of the standard can be used, for example, to provide check values ​​(e.g., CRC values ​​as part of a standard cyclic redundancy check).

[0016] In a preferred embodiment of the invention, the error correction data record contains, in addition to the actual error correction data, an identifier. This identifier contains information for implementing the error correction, such as the type of error correction and / or parameters required to implement the error correction, and / or information regarding which components of the telegram were included in the calculation of the error correction data. This allows the error correction data record to be designed flexibly and, for example, to have different lengths depending on the correction class to be achieved.

[0017] Possible types of error correction include Bose-Chaudhuri-Hocquenghem (BCH) codes, Reed-Solomon codes, or other systematic codes for forward error correction (FEC). In systematic codes, the information bits are included in the code word generated by the error correction in an unchanged form, making it possible to read the data in an error-free transmission even without performing error correction. This is particularly important with regard to low-computing and thus power-saving decoding of the received radio telegrams.

[0018] It can be intended to transmit only one version number of the error correction in the identifier, the meaning of which is known to the recipient of the telegram. The recipient can, for example, maintain a table that contains the type of error correction for each version number, such as the polynomial used, and all the parameters required to perform the error correction. This can save several bytes in the transmission of the identifier itself, because not all information needs to be transmitted in plain text.

[0019] To locate the identifier, the identifier of the error correction data record itself can be arranged at a defined position with respect to the end of the telegram, either in addition to the position of the error correction data record or as the position of the error correction data record. This means that the identifier can be located first, in particular independently of the actual error correction data. It is also possible to determine the position of the remaining error correction data in the telegram based on information in this identifier, provided it contains corresponding information. Such information can, for example, result from the type of correction, which determines the number of bits for the error correction data and thus defines the space required in the telegram. This can also provide information about the position, for example if the error correction data is arranged immediately before or after the identifier.In this case, the position of the identifier also determines the position of the error correction data record, so that the position of the identifier is the position of the error correction data record.

[0020] If the receiver has access to the error correction data in addition to the actual data, particularly the payload data specified in the standard and, if applicable, other manufacturer-specific data, it is possible to reconstruct the error-free telegram despite transmission errors in either the payload data or the error correction data. However, this requires that the receiver knows the type of error correction and the required parameters.

[0021] Since this information is transmitted in the error correction identifier, it would not be possible to correct an error in the identifier itself. Therefore, a preferred embodiment of the invention provides for the identifier to have its own error correction. For this purpose, separate identifier error correction data is provided in the identifier. For example, if the identifier, also referred to as the FEC header, comprises 1 byte = 8 bits, 3 bits can be provided for the actual identifier and a further 3 bits for identifier error correction data. This identifier error correction data is also referred to as FEC parity bits. According to the invention, this separate error correction of the identifier is completely independent of the error correction of the rest of the telegram, in particular the payload data.It may be provided that the error correction used in the identifier is not changed during the service life of the method so that all receiving systems can assume that there is only one type of error correction in the identifier.

[0022] In one embodiment of the invention, provision can be made for the data to be transmitted in encrypted form. For this purpose, the data to be transmitted is transmitted in encrypted form in the telegram. The error correction data is preferably determined based on the already encrypted data and is no longer encrypted itself. This is not necessary because it is not possible to determine the original data from the error correction data, as this can only reconstruct the data in encrypted form. The identifier is also not encrypted according to the invention, since the identifier and error correction data must be evaluated at the receiver before decryption in order to be able to carry out error correction in advance if an error occurred during radio transmission.

[0023] The defined standard provides for the embedding of check values ​​in the telegram by inserting a check block with an assigned check value for the preceding data block after a data block with data and / or manufacturer-specific data, i.e. the previously defined payload data, whereby the error correction data record or at least the error correction data of the error correction data record are integrated into a separate data block. A separate data block in this sense is a data block that contains no further data, in particular no payload data, apart from the error correction data and, if applicable, the identifier for the error correction. A separate check block with a check value is also provided for this separate data block.

[0024] An example of embedding check values ​​in the telegram is the provision of CRC blocks in the standard telegram. After a certain number of bytes containing the actual data to be transmitted (in particular, user data or payload), a certain number of CRC bytes are provided as check values ​​in a check block to perform a so-called cyclic redundancy check. This allows the receiver to determine whether the transmission contains errors or not. This makes it possible to perform error correction with the error correction data only if a transmission error has occurred. At least the error correction data, possibly also together with the identifier, is then combined in a separate CRC block.

[0025] According to the invention, the error correction data is calculated using all data blocks of the telegram, including the associated check blocks, with the exception of the error correction data set itself and the check block associated with the error correction data set. Thus, the maximum possible portion of the telegram is protected by error correction, resulting in a particularly high probability that the receiver can reconstruct the error-free telegram from the received data.

[0026] One way to define the positioning of the error correction data record is to place it in the last data block before the end of the telegram. Many standards allow for the length of this last (separate) data block to be variable, even if this last data block is provided with its own check value and check block. This helps keep the length of the data telegram as short as possible. The identifier of the error correction data record itself can also be located at a defined position in this last data block, preferably at the beginning or end of the separate data block, whereby, if necessary, only the position of the identifier and the relative position of the error correction data record (especially the error correction data itself) are known.

[0027] Since the identifier according to a preferred embodiment of the proposed method has its own error correction, it is also possible to arrange the identifier of the error correction data record outside the separate (in particular last) data block in the proprietary area of ​​the telegram, e.g. immediately before the last check block before the separate data block. This position can also be defined relative to the end of the telegram, since the size of the error correction data, i.e. the number of bits used for it, is usually defined. This allows a receiver to specifically access the identifier of the error correction data record at this position too. This allows the length of the entire telegram to be further shortened if the data to be transmitted does not completely fill the last data block before the separate data block.

[0028] If the data to be transmitted does not completely fill the last data block before the separate data block, it can additionally or alternatively be provided according to the invention that these unused bits of the data block (which nevertheless remain after the identifier has been positioned in this area), in particular of the proprietary area, are filled with padding data so that the error correction data record and / or the error correction data of the error correction data record are arranged in the separate data block and not in this unused area of ​​the previous data block. Padding data are filler bytes and / or filler bits that fill a data area without providing any content information. It is therefore particularly useful, for example, to swap out the identifier to the unused proprietary area of ​​the telegram in order to reduce the amount of padding data and the overall telegram length. If necessary.Instead of (useless) padding data, other data can also be transmitted, e.g. about the battery status of the measuring device, value histories, other status data, error messages and / or other information available in the measuring devices.

[0029] A particularly preferred embodiment and use of the method relates to the transmission of building consumption, building sensor, and / or building actuator data within a building wireless network. Such building wireless networks are used, for example, for measuring water, heat quantities, and / or heating costs and / or for controlling building components, such as heating and / or cooling systems.

[0030] The invention also relates to a device for the radio transmission of data with a radio transmitter, with a data memory for storing the data to be transmitted and with a computing unit which is designed to compile a telegram in the manner described above and to send it by the radio transmitter.

[0031] To send data according to the described method, the telegram to be sent is compiled in the device used as the transmitter. This can proceed, for example, as follows: First, the consumption, sensor, actuator, and / or other data are provided for the data points of the telegram specified in the standard. In addition, in the proprietary area, the additional data provided by the manufacturer is provided as manufacturer-specific data, preferably in data points specified by the manufacturer. This data can then be encrypted in whole or in part if necessary. The data thus provided (encrypted and / or unencrypted) is then inserted into the data blocks of the telegram at the designated data points. Next, test values ​​are determined - preferably data block by data block - and inserted into the test blocks.

[0032] The error correction data (e.g., as additional manufacturer-specific data) is then calculated using the designated error correction method (according to the information in the identifier). The error correction data can be calculated from the entire telegram (including header and / or check blocks), with the exception of the error correction data area itself and its check block (i.e., the separate data block).

[0033] The resulting error correction data is provided in the proprietary area. The identifier, which contains information about the error correction, is provided in the proprietary area along with the error correction data. The error correction data and / or the identifier are positioned at a defined position relative to the end of the telegram. This can, for example, be the position directly before the last check block at the end of the telegram. This ensures that the position of the error correction data set relative to the end of the telegram is always known.

[0034] To ensure that potential errors in the identifier can be corrected independently of the error correction enabled by receiving the identifier, the identifier itself is preferably equipped with its own error correction. The total length of the resulting telegram, including the data points prescribed by the standard and the (particularly manufacturer-specific) data point with the error correction data, is entered in the length field in the header of the telegram. This value allows the end of the telegram to be determined and thus allows targeted access to the error correction data set positioned relative to the end of the telegram, i.e., the error correction data and / or the identifier. The telegram compiled in this way is then sent.

[0035] The invention also relates to a device for the radio transmission of data with a radio receiver, with a data memory for storing the transmitted data and with a computing unit which is set up to receive a telegram compiled and transmitted as described above and to correct transmission errors in the telegram with the aid of the error correction data set, wherein the above-described devices for transmitting and receiving can also be combined in one device according to the invention.

[0036] To receive data according to the described method, the transmitted telegram is received by a device configured as a receiver. The transmitted data of the telegram is initially buffered as usual. Using check values ​​in the check blocks (if provided), the telegram can be checked for transmission errors, for example, via a cyclic redundancy check using CRC bytes as check values. If an error occurred during transmission of the telegram, error correction is performed next to restore the original (error-free) telegram.

[0037] To do this, it is necessary to determine which error correction method was used. According to the invention, the identifier containing the error correction information is read out. The total length is read from the length field of the telegram header, and the end of the telegram is determined based on the total length, starting from the beginning of the telegram. Since the identifier is located at a defined position relative to the end of the telegram, for example, directly before the last check block, the identifier can be located directly.

[0038] If an error occurs during the transmission of the identifier, the identifier can be recovered using the identifier's own error correction. This provides the receiver with information about the type of error correction, the location of the error correction data, all parameters, and all other information necessary for error correction.

[0039] The error correction data, located at a defined position relative to the end of the telegram, can then be located at the receiver, and the error correction can be performed. In the best case scenario—for example, if the transmission errors do not exceed a specified limit for the error correction performed—the original telegram can be reconstructed error-free.

[0040] Accordingly, according to a preferred embodiment, the computing unit of the device can be configured to evaluate the error correction data set and / or the identifier of the error correction data set at the defined position relative to the end of the telegram and to perform the error correction. If necessary, an independent correction of the identifier is also performed using the identifier error correction data contained in the identifier itself. This is performed when an error has occurred in the area of ​​the identifier.

[0041] Furthermore, the computing unit can be configured to compare the test values ​​of a test block with the data of the associated data blocks of the telegram, for example with the exception of the separate data block for the correction data record, and to carry out error correction if at least one test value does not match the data of the associated data block.

[0042] The invention is explained below using exemplary embodiments and with reference to the figures. Fig. 1 shows the structure of a telegram according to the invention, as used in the method according to the invention, according to one exemplary embodiment. Fig. 2 shows a further embodiment of a telegram according to the invention, of which only the proprietary area is shown. Fig. 3 shows the proprietary area of ​​a further embodiment of a telegram according to the invention, in which the penultimate data block is filled with padding data and in which the identifier is arranged in the penultimate data block. Fig. 4 shows an embodiment of an identifier according to the invention.

[0043] Fig. 1 shows a telegram 1 as it is sent and / or received in the manner described above in the method according to the invention, according to a preferred embodiment according to the OMS standard, which is used for the transmission of consumption values ​​in a local radio network, in particular a building radio network.

[0044] This telegram 1 conforms to a standard for transmitting consumption values, e.g., the OMS standard. Each telegram 1 begins with a telegram header 2, also known as a header, which can contain information about the sender, receiver, the standard, the (total) telegram length, and / or similar information in a known manner and as defined by the standard. The telegram length contained in the telegram header 2 is the total length of the telegram 1 as it is transmitted. The total length therefore includes a standard data area 3, which follows the telegram header 2, and a proprietary area 4, which in turn follows the standard data area 3.

[0045] The standard data area 3 comprises data 7 that is specified in the OMS standard, in particular an identifier of the measuring device, the consumption value, the reading time and / or similar information. The length of the individual data 7 can already be specified in the standard. It is also possible, as provided in the example OMS standard, for the length of the individual data 7 to be specified together with the data value, so that the receiver can work through the telegram 1 from data value to data value by evaluating the data 7 with the length information contained therein. This data 7, comprising the data value and the associated length information of the data value, is also referred to as data points.

[0046] The subsequent proprietary area 4 contains manufacturer-specific data 8, which any manufacturer of a consumption metering device can transmit as additional information, i.e., information not provided for in the standard. This information can be evaluated and used by appropriately configured receivers. In principle, the equally proprietary area 4 is preferably structured in the same way as the standard data area 3, although the data content of the data 8 in the proprietary area 4 is not specified by the standard.

[0047] According to the invention, this proprietary area 4 contains, in addition to general manufacturer-specific data 8, error correction data 10 as special manufacturer-specific data 8. This error correction data 10 is located in an error correction data record 9, which differs from other data records by certain features, which are explained below. According to the invention, individual features or any combination of these features can also be combined in a telegram according to the invention.

[0048] In particular, the error correction data record 9 can be arranged as the last (separate) data block 13 before the end of the telegram, ie in particular after data blocks 12 with the data 7 from the standard data area 3 of the telegram 1 and the general manufacturer-specific data 8 from the proprietary area 4 of the telegram 1.

[0049] According to a preferred embodiment, the data blocks 12, 13 are separated from one another by test blocks 5 with the test values ​​6.

[0050] These can, for example, be so-called CRC blocks, which contain, as check value 6, a CRC sum of data 7 and 8 of the respective preceding data blocks 12. Sometimes, the actual check block 5 with check value 6 and the associated data blocks 12 and 13 are also referred to together as a CRC block. This CRC procedure is generally known and is usually integrated into the DataLink layer of the protocol defined by the standard. Therefore, the CRC procedure does not need to be described separately here.

[0051] The CRC sums (ie the check values ​​6 of the individual check blocks 5) are formed from the data 7, 8 of the data block 12 assigned to the respective check block 5 and thus associated therewith, in such a way that bit errors occurring in the data 7, 8 during transmission can be detected with a very high degree of probability.

[0052] This also applies in principle to the separate data block 13 with the error correction data, which according to the invention, however, preferably only contains the error correction data record 9 with the error correction data 10 and, if applicable, the identifier 11 for the error correction.

[0053] The length of this last separate data block 13 preferably corresponds exactly to the length of the error correction data record 9 with the identifier 11, as in the embodiments according to Fig. 1 or Fig. 2 shown, or without the identifier 11, as described later with respect to other embodiments (shown in Fig. 3 ) will be described later. The check value 6 of the check block 5 for the last separate data block 13 therefore only considers the error correction data 10 and, if applicable, the error correction identifier 11. Thus, a transmission error in the error correction data 10 can also be detected and, if applicable, localized. In this case, it is possible to correct the error correction data 10 using the other data 7, 8 if no transmission error has occurred in the associated data block 12 or the associated data blocks 12 containing the data 7 and / or the general manufacturer-specific data 8.

[0054] In telegram 1, after a fixed number of bytes containing data 7, 8, a certain number of CRC bytes are transmitted as check value 6, which are used upon reception to verify error-free transmission of the previous bytes of data 7, 8 in data block 12.

[0055] In the embodiment of the Fig. 1 The error correction data set 5 with the error correction data 10 and the identifier 11 is transmitted in the last CRC block (i.e., the separate data block 13). The identifier 11 is located directly before the last check block 5 of the entire telegram 1, thus at a defined position in telegram 1 relative to the end of the telegram. This is because the length of a check block 5 with the check value 6 is precisely known in bits.

[0056] The receiver of telegram 1 can therefore directly locate the end of telegram 1 and (taking into account the length of check block 5) the position of identifier 11 in the telegram using the length information transmitted in header 2.

[0057] Fig. 2 shows an alternative embodiment of the check block 9 in the proprietary area 4 of the telegram 1, in which the identifier 11 is arranged after the penultimate check block 5, i.e. at the beginning of the last (separate) data block 13. Since the length of the last data block 13 is determined by the error correction data record 9, the length of which in bytes is known to the receiver, the identifier 11 can also be reliably located by the receiver for this arrangement without the positions and lengths of all data points 3 having to be evaluated. The first bit or byte position after the penultimate check block 5 is also precisely known to the receiver, since the length of the data blocks 12 (with the exception of the last data block 13) is known, so that the penultimate check block 5 can also be precisely determined knowing the total length of the telegram 1.

[0058] In principle, it would also be possible, particularly if the type of error correction influences the length of the error correction data 10 and therefore determines the length of the last data block 13, to position the identifier at a specific bit length, i.e., for example, 40 bits or any other defined number of bits, before the end of the telegram, for example in the middle of the error correction data 10, which are then grouped around the identifier 11. This would have the advantage that the position of the identifier 11 is always the same for the receiver in the telegram 1 relative to the end of the telegram, so that (regardless of the actual length of the error correction data 10) it is always the same in the receiver for every type of manufacturer-specific error correction. This is advantageous because the receiver can then be configured accordingly during production. This embodiment is also the subject of the invention, even if it is not shown separately in the figures.

[0059] Fig. 3 shows a further embodiment of the manufacturer-specific area 4 of the telegram 1, in which the error correction data record 9 is divided in that it is divided across the last separate data block 13 and the one (directly or indirectly) preceding data block 12. According to the invention, the division is such that all error correction data 10 are arranged in the last separate data block 12, which depend on the content of the previous data blocks and thus vary with the data 7, 8 in the data blocks 12. According to the invention, these should always be arranged in the last data block 13, which is preferably a separate data block 13 in the sense that only data 10, 11 related to the manufacturer-specific error correction are arranged there.However, the identifier 11 is independent of the (other) data 7, 8 in the data blocks 12, so that the identifier 11 of the error correction itself can be arranged with a part of the manufacturer-specific area 4 of the telegram 1 that is not used for other manufacturer-specific data 8.

[0060] The position can, for example, be selected such that the identifier 11 is located directly before the penultimate test block 5. This can, as already described in another context, be clearly determined relative to the end of the telegram. It is of course also possible according to the invention to arrange the identifier at a specific bit or byte position in the proprietary area 4 before the penultimate test block 5, because this position is also clearly identifiable. However, the particularly easy-to-handle position of the identifier 11 immediately before the last test block in the data block 12 is preferred for this embodiment, as also in Fig. 3 shown.

[0061] Because a telegram should not or must not contain any empty (ie undefined) bits, in the last data block 12 before the penultimate check block 5, any unfilled bit fields are filled with so-called padding bits or padding bytes, or more generally with so-called padding data 14, as shown for example in Fig. 3 are shown, but can be used in the other embodiments in the same way. This filler data is marked as filler bytes and is not decoded by the application. However, it would also be conceivable according to the invention to use these unfilled bit fields of a data block 12 in the manufacturer-specific area to transmit further content information which can be used meaningfully if required, without this being absolutely necessary for evaluation. This could include, for example, values ​​from data histories. It is also conceivable, for example, to transmit the data transmitted in the standard data area 3 (i.e. the essential data) redundantly in its pure form, so that in the event of a data error in the standard data area 3, in addition to the manufacturer-specific error correction proposed according to the invention, further redundancy can be achieved by simply duplicating essential data information. In the context of consumption values, for example,a reference date value or another value that is absolutely necessary for the evaluation must be transmitted twice again in order not to fill the (technically necessary) telegram length with meaningless, i.e. empty, data.

[0062] The same reference numerals have been used for the description of all embodiments of the proprietary area 4 of the telegram because the content of the individual referenced features is the same in all embodiments and only their position in the telegram changes.

[0063] Error-free reception of identifier 11 of error correction data record 9 is a prerequisite for implementing manufacturer-specific error correction, at least if different types of error correction are generally applicable in the transmission method resulting from the identifier. The receiver must then evaluate identifier 11 so that the correct error correction method can be applied.

[0064] This can only be omitted if the receiver can identify which manufacturer-specific error correction method should be applied without evaluating an identifier 11. This would be the case, for example, if only a precisely defined error correction method is applied or if the type of error correction method can be derived from other information in the telegram, e.g., the total telegram length.

[0065] In the event that an identifier 11 is required for the application of the error correction proposed according to the invention during the radio transmission of data 7, 8, 10, it is therefore sensible for the identifier 11 to have its own identifier error correction data 15 for the independent error correction of the identifier 11. This is exemplified in Fig. 4 illustrated.

[0066] There, an identifier 11 with a total of 8 bits (i.e., one identifier byte) is shown with identifier data 16, which describes the type of identifier, can be read directly by the receiver, and contains the information for performing error correction. 3 bits are used for this purpose. Following the identifier data 16, the identifier error correction data 15 is provided, which is calculated on the basis of the identifier data 16 and, in the event of an error due to redundancy, allows the identifier data 16 to be reconstructed. A conventional FEC method can also be used for this purpose. According to the invention, this is clearly predefined and can therefore be used without further parameterization. This method should not be changed in a device generation so that all devices are compatible with one another. 3 bits are also provided for the identifier error correction data 15.

[0067] The remaining Fig. 4The unmarked bits can be used for other purposes, e.g. for a check value to detect transmission errors, analogous to the method already described for the check blocks 5. Thus, according to the invention, the identifier 11 in the telegram 1 is completely self-sufficient with regard to detecting and correcting transmission errors. List of reference symbols:

[0068] 1Telegram 2Telegram header 3Standard data area 4Proprietary area 5Test data block 6Test value 7Data 8Manufacturer-specific data 9Error correction data record 10Error correction data 11Identifier 12Data block 13Separate data block 14Padding data 15Identifier error correction data

Claims

1. Method for radio transmission of data, wherein the data is sent and received in a telegram (1) according to a defined standard, wherein the standard is predefined by protocols for the radio transmission including the definition of the telegrams, the method having the following steps: - Compilation, by a computing unit of an apparatus with a radio transmitter, of the telegram (1), wherein the defined standard in the telegram (1) provides a standard data area (3) for transmitting data (7), a proprietary area (4) for transmitting manufacturer-specific data (8) and the embedding of check values (6) in the telegram (1), in that after a data block (12) with a specific number of bytes with data (7) and / or manufacturer-specific data (8), a check block (5) with a specific number of CRC bytes is inserted with each assigned check to the value (6) for the preceding data block (12); the defined standard does not provide for an error correction procedure; an error correction data set (9) with error correction data (10) for the telegram (1) is transmitted in the proprietary area (4), which allows error correction of the data (7) and / or the manufacturer-specific data (8) in the event of transmission errors due to redundancy; this error correction data set (9) is arranged at a position of the telegram (1) defined relative to the end of the telegram (1) identified by the overall length of the telegram (1); the error correction data set (9) is integrated into a separate data block (13) with its own check block (5) with its own check value (6), and the multiple data blocks (12, 13) are delimited from one another by the check blocks (5) with the check values (6); the error correction data (10) is calculated from all data blocks (12) of the telegram (1) including the associated check blocks (5), with the exception of the error correction data set (9) itself and the check block (5) assigned to the error correction data set (9); - Transmission of the compiled telegram by the radio transmitter using the computing unit; - reception, by means of a computing unit of an apparatus with a radio receiver by the radio receiver, of the transmitted telegram, wherein a cyclic redundancy check is carried out in the received telegram according to the defined standard, and an error correction is carried out if a transmission error is detected during the cyclic redundancy check using the CRC bytes as check values (6), for which purpose the check values (6) of the check block (5) are compared with the data (7, 8, 10) of the associated data blocks (12, 13) and the error correction is carried out if at least one check value (6) does not match the data (7, 8, 10) of the associated data block (12, 13).

2. Method for radio transmission of data according to claim 1, characterized in that the error correction data set (9) contains an identifier (11) in addition to the error correction data (10), wherein the identifier (11) contains information for performing the error correction.

3. Method according to claim 2, characterized in that the identifier (11) of the error correction data set (9) is arranged at a position of the telegram (1) defined relative to the end of the telegram (1).

4. Method for radio transmission of data according to claim 2 or 3, characterized in that the identifier (11) contains its own error correction with identifier error correction data (15) for correcting the identifier (11).

5. Method for radio transmission of data according to one of the preceding claims, characterized in that the error correction data set (9) or the error correction data (10) of the error correction data set (9) are arranged in the separate data block (13) before the end of the telegram.

6. Method for radio transmission of data according to any one of the preceding claims 2 to 4, characterized in that the identifier (11) of the error correction data set (9) is arranged at the beginning or at the end of the separate data block (13).

7. Method for radio transmission of data according to one of the preceding claims 2 to 4 or 6, characterized in that the identifier (11) of the error correction data set (9) is arranged outside the separate data block (13) in the proprietary area (4) of the telegram (1).

8. Method according to one of the preceding claims, characterized in that a data block (12) in the proprietary area is padded with padding data (14) so that the error correction data set (9) and / or the error correction data (10) of the error correction data set (9) are arranged in the separate data block (13).

9. Method for radio transmission of data according to one of the preceding claims, characterized in that, in the event of a transmission error in the error correction data (10), a correction is made by the other data (7, 8) if no transmission error has occurred in the associated data block (12) containing the data (7, 8).

10. Use of the method according to any one of the preceding claims for the transmission of building consumption, building sensor and / or building actuator data within a building radio network.

11. Apparatus for the radio transmission of data, having a radio transmitter, having a data memory for storing the data to be transmitted and having a computing unit, wherein the computing unit is adapted to compile a telegram (1) defined in accordance with the method of claims 1 to 9 after the compiling step of claims 1 to 9 and to send it by the radio transmitter.

12. Apparatus for radio transmission of data comprising a radio receiver, a data memory for storing the transmitted data and a computing unit, wherein the computing unit is adapted to: Receiving a telegram (1) according to the receiving step in the method of claims 1 to 9, wherein the telegram (1) is compiled by a computing unit of an apparatus with a radio transmitter according to the compiling step in the method according to any one of claims 1 to 9.

13. Apparatus according to claim 12, characterized in that the computing unit is further adapted to evaluate the error correction data set (9) and / or the one identifier (11) of the error correction data set (9) at the defined position relative to the end of the telegram (1) identified by the total length of the telegram (1) when performing the error correction.