Abstract: Exemplary embodiments provide a transmission method for transmitting data of variable length using a fixedly predefined number of data sub-packets into which the data of variable length is split.
Variable partial packet lengths for telegram splitting in low-traffic networks
power consumption
description
Embodiments of the present invention relate to a data transmitter for transmitting data. Further embodiments relate to a data receiver for receiving data. Some embodiments relate to variable sub-packet lengths for telegram splitting in low-power networks.
DE 10 201 1 082 098 B4 describes a method for battery-operated transmitters in which the data packet is subdivided into transmission packets which are smaller than the actual information that is to be transmitted (so-called telegram splitting). Telegrams are divided into several subpackages. Such a subpackage is called a hop. In a hop several information symbols are transmitted. The hops are distributed on one frequency or over several frequencies, so-called frequency hopping. There are pauses between the hops where there is no transmission.
In a typical sensor network, several 100,000 sensor nodes are covered with only one base station. Since the sensor nodes have only very small batteries, coordination of the transmissions is hardly possible in most cases. The telegram splitting method achieves a very high transmission reliability for this purpose.
WO 2015/128385 A1 describes a data transmission arrangement which has an energy harvesting element as energy source. The data transmission device is configured to transmit data using the telegram splitting method, wherein a partial packet pending transmission is either sent, buffered and later transmitted, or discarded, depending on an amount of electrical energy that can be supplied by the power supply device.
In the publication [G. Kilian, H. Petkov, R. Psiuk, H. Lieske, F. Beer, J. Robert, and A. Heuberger, "Improved coverage for low-power telemetry systems using telegram splitting," in Proceedings of 2013 European Conference on Smart Objects , Systems and Technologies (SmartSysTech), 2013] will provide improved coverage for
Low-power emulation systems using the telegram splitting method are described.
In the publication [G. Kilian, M. Breiling, HH Petkov, H. Lieske, F. Beer, J. Robert, and A. Heuberger, "Increasing Transmission Reliability for Telemetry Systems Using Telegram Splitting," IEEE Transactions on Communications, vol. 63, no. 3, pp. 949-961, Mar. 2015] describes improved transmission security for low power telemetry systems using the telegram splitting method.
US2016 / 0094269 A1 describes a wireless communication system having a plurality of base stations and a plurality of endpoints. The communication system uses telegrams with a CSS modulated preamble (CSS = Chirp Spread Spectrum), followed by data, with the data modulated with a narrow bandwidth than the preamble.
The object of the present invention is therefore to provide a concept for the transmission of data of variable length, which requires a low overhead and / or provides a high transmission reliability.
This object is solved by the independent claims.
Advantageous developments can be found in the dependent claims.
Embodiments provide a data transmitter for transmitting variable length data, wherein the data transmitter is adapted to divide the variable length data into a predetermined number of sub-data packets and to transmit the sub-data packets.
Embodiments provide data receivers for receiving variable length data, wherein the data receiver is adapted to receive a predetermined number of sub-data packets to which the variable-length data is divided. By always dividing the variable-length data into the same number of sub-data packets regardless of the length thereof, a required overhead can be kept low because, for example, no additional synchronization sequences have to be transmitted in additional data packets. Furthermore, a transmission time
be kept low, so that the probability of a disruption of the transmission can be kept low.
In embodiments, the variable length data (regardless of a length thereof) is divided into a predetermined number of sub-data packets. Accordingly, the lengths of the individual sub-data packets are dependent on the length of the variable-length data.
Further embodiments provide a method for transmitting variable length data, the method comprising a step of dividing the variable length data into a predetermined number of sub data packets and a step of transmitting the sub data packets.
Further embodiments provide a method for receiving variable-length data, the method comprising a step of receiving a predetermined number of sub-data packets to which the variable-length data is divided, and a step of combining the predetermined number of sub-data packets with the variable-length data to obtain.
Further embodiments provide a transmission method for transmitting variable-length data using a fixed predetermined number of sub-data packets to which the variable-length data is divided.
In the following, preferred embodiments of the data transmitter for transmitting variable length data will be described.
In embodiments, the predetermined number of sub-data packets may be a fixed (or non-variable) number of sub-data packets. The data transmitter may thus be designed to always divide the variable length data (regardless of a length thereof) into the same number of sub-data packets. Accordingly, the lengths of the individual sub-data packets may be dependent on the length of the variable-length data.
In embodiments, the data transmitter may be configured to transmit the sub-data packets within a predetermined time interval.
For example, the variable-length data may be sent out independently of a length of variable-length data (always) within the predetermined time interval using the predetermined number of sub-data packets.
In embodiments, the data transmitter may be configured to transmit the sub-data packets spaced apart in time so that transmission pauses are present between the sub-data packets.
In embodiments, the data transmitter may be configured to transmit the sub-data packets at a predetermined time interval such that the time interval between the sub-data packets is constant independent of a length of the variable-length data.
For example, the pauses (transmission pauses) between the sub-data packets may remain constant as the lengths of the sub-data packets (sub-packet lengths) change (depending on the length of the variable-length data). For example, three sub-data packets may each be 24 symbols in length, the pauses being 10 ms and 15 ms. If the lengths of the sub-data packets are increased due to a length of the variable-length data and, for example, result in 34 symbols per sub-data packet, then the pauses are still 10 ms and 15 ms.
In embodiments, the data transmitter may be configured to transmit the sub-data packets with a length dependent on the length of the variable length data interval, so that a time interval between predetermined areas (eg Subdatenpaketanfang, Subdatenpaketmitte, Subdatenpaketende or a (partial) synchronization sequence) of the sub-data packets regardless of a length of variable length data is constant.
For example, the sub-data packets can be transmitted so that a distance between the assigned areas (eg sub-packet start, sub-packet center, sub-packet end or a (partial) synchronization sequence) is constant. For example, three sub-data packets may each be 24 symbols in length, the pauses being 10 ms and 15 ms. If the lengths of the sub-data packets are increased due to a length of the variable-length data and, for example, result in 34 symbols per sub-data packet, then the pauses are shorter, eg 5 ms and 10 ms.
In embodiments, the data transmitter may be configured to provide at least a portion of the sub-data packets with synchronization sequences.
In embodiments, the data transmitter may be configured to provide at least a portion of the sub-data packets with sub-sync sequences. In this case, the data transmitter can be designed to divide a synchronization sequence into the sub-synchronization sequences.
The synchronization sequences or sub-synchronization sequences can be located anywhere in the sub-data packet. For a possible subsequent iterative decoding, it is advantageous that the synchronization sequences or sub-synchronization sequences are sent together with the data in a sub-data packet. Of course, it is also possible to distribute the synchronization sequences or sub-synchronization sequences and the data to separate sub-data packets (hops). In this case, it is advantageous to ensure that coherence is not lost between the data shops and sync hops.
For example, the sub-data packets may be provided with synchronization sequences or partial synchronization sequences. If the sub-data packets are provided with synchronization sequences, then a complete synchronization of the respective sub-data packet or detection or localization thereof in a receive data stream is possible on the receiver side based on the respective synchronization sequence. If the sub-data packets are provided with partial synchronization sequences, then a complete synchronization of the sub-data packets or detection of the same is possible in the receiver data stream (only) over several or all partial synchronization sequences into which the synchronization sequence is divided.
In embodiments, the data transmitter may be configured to transmit the sub-data packets at a time interval dependent on the length of the variable-length data such that a time interval between the synchronization sequences or sub-sync sequences of the sub-data packets is constant regardless of a length of the variable-length data.
For example, the sub-data packets can always be transmitted so that a time interval between the synchronization sequences or sub-synchronization sequences is constant.
In embodiments, the data may include core data and extension data, the core data having a fixed length and the extension data having a variable length. The data transmitter may be configured to provide the core data with signaling information for signaling the length of the extension data.
The data transmitter may be configured to split the core data and the extension data onto the sub-data packets.
For example, the data transmitter may be configured to divide the core such data to the Subdatenpakete that in the ' Subdatenpaketen the respective part of the core data adjacent to the (sub-) synchronization sequences is arranged. The data transmitter can be designed to divide the core data into the sub-data packets such that in the sub-data packets the respective part of the core data is arranged uniformly before and after the respective (sub-) synchronization sequences.
For example, the data transmitter can be designed to divide the extension data into the sub-data packets in such a way that, in the sub-data packets, the respective part of the extension data is arranged adjacent to the respective part of the core data. The data transmitter can be designed to divide the extension data into the sub-data packets in such a way that, in the sub-data packets, the respective part of the extension data is arranged uniformly before and after the respective part of the core data.
For example, the data transmitter can be designed to divide the core data into sub-data packets as a function of lengths of the synchronization sequences or sub-synchronization sequences, as follows :that sub-data packets with longer synchronization sequences or sub-synchronization sequences contain a larger part of core data than sub-data packets with shorter synchronization sequences or sub-synchronization sequences. In other words, the core data is distributed according to the length of the respective preamble length, i. If more preamble symbols are contained in a sub-data packet, then more core data symbols can also be attached there than in a sub-data package in which fewer preamble symbols are contained. The data transmitter can be designed to divide the extension data depending on lengths of the synchronization sequences or sub-synchronization sequences on the sub-data packets, so that sub-data packets.
Subdata packages with shorter synchronization sequences or
Subsynchronisationssequenzen.
In embodiments, the data transmitter may be configured to divide the number of sub-data packets into at least two independent blocks of sub-data packets, wherein the data transmitter is configured to divide the sub-data packets into the at least two blocks of sub-data packets such that a first block of the at least two blocks of Sub-data packets can be detected by themselves on the receiver side.
In this case, the data transmitter can be designed to provide at least one of the two blocks of sub-data packets with a synchronization sequence for the synchronization of the sub-data packets in a data receiver. Furthermore, the data transmitter can be designed to provide the first block of sub-data packets with information about a second block of sub-data packets of the at least two blocks of sub-data packets. For example, the information may signal at least one of a length, a number of sub-data packets and a hopping pattern with which the sub-data packets are transmitted. For example, the location of the other blocks may be known or signaled in the first block. Thus, the other blocks need not necessarily be detectable.
In embodiments, the data transmitter can be configured to, if a length of variable length data is so large that would be below a minimum value of the transmission pauses between the sub-packets in a given transmission of the sub-packets within the predetermined time interval, the variable-length data to at least one additional Split subdata package. In this case, the data transmitter can be designed to provide the data contained in the sub-data packets of fixed number with information about the at least one additional sub-data packet.
In the following, preferred embodiments of the data receiver for receiving variable length data will be described.
In embodiments, the predetermined number of sub-data packets may be a fixed (or non-variable) number of sub-data packets. The variable-length data can thus always be divided into the same number of sub-data packets (irrespective of their length). Accordingly, the lengths of the individual sub-data packets may be dependent on the length of the variable-length data.
In embodiments, the data receiver may be configured to receive the sub-data packets within a predetermined time interval.
In embodiments, the sub-data packets may be spaced in time so that there are pauses between the sub-data packets.
In embodiments, the transmission pauses between the sub-data packets may be constant irrespective of a length of the variable-length data.
For example, the pauses (transmission pauses) between the sub-data packets may remain constant as the lengths of the sub-data packets (sub-packet lengths) change (depending on the length of the variable-length data). For example, three sub-data packets may each be 24 symbols in length, the pauses being 10 ms and 15 ms. If the lengths of the sub-data packets are increased due to a length of the variable-length data and, for example, result in 34 symbols per sub-data packet, then the pauses are still 10 ms and 15 ms.
In exemplary embodiments, the transmission pauses between the sub-data packets may be dependent on the length of the variable-length data such that a time interval between predetermined areas (eg sub-packet start, sub-packet center, sub-packet end or (sub) synchronization sequence) of the sub-data packets is independent of a variable length of data Length is constant.
For example, the sub-data packets can be sent out so that a distance between the predefined areas (eg sub-packet start, sub-packet center, sub-packet end or a (sub) synchronization sequence) is constant. For example, three sub-data packets may each be 24 symbols in length, the pauses being 10 ms and 15 ms. If the lengths of the sub-data packets are increased due to a length of the variable-length data and, for example, result in 34 symbols per sub-data packet, then the pauses are shorter, eg 5 ms and 10 ms.
In embodiments, at least a portion of the sub-data packets may be provided with synchronization sequences, wherein the data receiver may be configured to detect the sub-data packets based on the synchronization sequences.
In embodiments, at least a portion of the sub-data packets may be provided with sub-synchronization sequences, wherein the data receiver may be configured to detect the sub-data packets based on the sub-synchronization sequences.
For example, the sub-data packets may be provided with synchronization sequences or partial synchronization sequences. If the sub-data packets are provided with synchronization sequences, then a complete synchronization of the respective sub-data packet or detection thereof in a receive data stream is possible on the receiver side based on the respective synchronization sequence. If the sub-data packets are provided with partial synchronization sequences, then a complete synchronization of the sub-data packets or detection or localization thereof in a receive data stream (only) over several or all partial synchronization sequences into which the synchronization sequence is divided is possible on the receiver side.
In embodiments of the can ' time interval between the synchronization sequences or Subsynchronisationssequenzen be independent of a length of the variable length data is constant and / or be known to the data receiver.
In embodiments, the variable length data may include core data and extension data, the core data having a fixed length and the extension data having a variable length.
The core data may be provided with signaling information for signaling the length of the extension data, wherein the data receiver may be configured to receive the extension data using the signaling information or to extract it from the sub-data packets.
The core data and the extension data may be divided among the sub-data packets.
For example, the core data may be distributed to the sub-data packets such that in the sub-data packets the respective part of the core data is arranged adjacent to the sub-synchronization sequences. For example, the core data may be distributed to the sub-data packets such that in the sub-data packets the respective part of the core data is evenly arranged before and after the respective synchronization sequence or sub-synchronization sequence.
For example, the extension data may be distributed to the sub-data packets such that in the sub-data packets the respective part of the extension data is arranged adjacent to the respective part of the core data. For example, the extension data may be distributed to the sub-data packets such that in the sub-data packets the respective part of the extension data is evenly arranged before and after the respective part of the core data.
The core data can be divided into sub-data packets depending on lengths of the synchronization sequence or sub-synchronization sequence, such that sub-data packets with a longer synchronization sequence or sub-synchronization sequence contain a larger amount of core data than sub-data packets with a shorter synchronization sequence or sub-synchronization sequence. In this case, the data receiver can be designed to determine lengths of the parts of core data contained in the respective sub-data packets, based on the lengths of the synchronization sequence or sub-synchronization sequence contained in the respective sub-data packets.
The extension data can be divided into sub-data packets depending on lengths of the synchronization sequence or sub-synchronization sequence, so that sub-data packets with a longer synchronization sequence or sub-synchronization sequence contain a larger portion of extension data than sub-data packets with a shorter synchronization sequence or sub-synchronization sequence. In this case, the data receiver can be designed to determine lengths of the parts of extension data contained in the respective sub-data packets, based on the lengths of the (sub-synchronization sequence) contained in the respective sub-data packets.
In embodiments, the data receiver may be configured to decode and reencode a first portion of the respective portion of the variable length data using the synchronization sequence or sub-synchronization sequence to obtain a first portion of reencoded data; to decode a second portion of the respective portion of variable length data using the first portion of reencoded data to obtain a second portion of reencoded data; and to decode a third portion of the respective portion of the variable length data using the second portion of the reencoded data.
In this case, in the respective sub-data packets, the first area may be arranged immediately adjacent to the synchronization sequence or sub-synchronization sequence, and
wherein the second region may be disposed immediately adjacent to the first region.
In embodiments, the number of sub-data packets may be divided into at least two independent blocks of sub-data packets such that a first block of the at least two blocks of sub-data packets is detectable by itself. The data receiver can be designed to detect the first block of the at least two blocks of sub-data packets for itself.
At least one of the at least two blocks of sub-data packets (eg the first block of the at least two blocks) may be provided with a synchronization sequence for the synchronization of the sub-data packets in a data receiver. The data receiver can be designed to detect the at least one of the at least two blocks of sub-data packets using the respective synchronization sequence.
The first block of sub-data packets of the at least two blocks of sub-data packets may be provided with information about a second block of the at least two blocks of sub-data packets. The data receiver may be configured to receive the second block of the at least two blocks of sub-data packets using the information. For example, the information may include at least one of a length, a number of sub-data packets, and a hopping pattern with which the sub-data packets are sent.
In embodiments, the data receiver may be configured to receive at least one further sub-data packet appended to the number of sub-data packets.
In embodiments, the data contained in the sub-data packets of fixed number may be provided with information about the at least one additional sub-data packet, wherein the data receiver may be configured to receive the at least one additional sub-data packet using the information.
Exemplary embodiments of the present invention will be explained in more detail with reference to the attached figures. Show it:
1 is a schematic block diagram of a system having a data transmitter and a data receiver, according to one embodiment of the present invention;
Fig. 2 is a diagram of an occupancy of a transmission channel in the
Transmitting the variable length data using a fixed predetermined number of sub-data packets within a predetermined time interval;
Fig. 3 is a diagram of an occupancy of a transmission channel in the
Transmission of data using a plurality of sub-data packets with transmission pauses, which specify the time intervals between the sub-data packets;
Fig. 4 is a diagram of an occupancy of a transmission channel in the
Transmission of the variable length data using a fixed number of sub-data packets within a fixed predetermined time interval, intervals between the synchronization sequences and partial synchronization sequences being constant;
5 shows a schematic view of a structure of the sub-data packets, each having a synchronization sequence, a core sequence and an extension sequence;
6 shows a schematic view of a structure of the sub-data packets each having a synchronization sequence, a core sequence and an extension sequence together with a decoder-side distribution of the respective sub-data packet corresponding to the sequences for an iterative decoding;
7 shows a schematic view of a structure of the sub-data packets each having a synchronization sequence, a core sequence and an extension sequence, wherein the data corresponding to the core sequence and the extension sequence are arranged in the respective sub-data packets such that a distance of the encoded data with respect to an influence length of a code used to encode the data is increased;
Fig. 8 is a diagram of an occupancy of a transmission channel in the
Transmitting data using a plurality of sub-data packets grouped in blocks;
9 is a diagram of an occupancy of a transmission channel in the
Transmitting the variable length data using a predetermined number of sub-data packets, wherein the predetermined number of sub-data packets are appended with additional sub-data packets;
10 is a flowchart of a method of transmitting variable length data in accordance with one embodiment; and
1 1 is a flowchart of a method for receiving variable data
Length, according to an embodiment.
In the following description of the embodiments of the present invention, the same or equivalent elements are provided with the same reference numerals in the figures, so that their descriptions in the different embodiments with each other is interchangeable.
Fig. 1 shows a system with a data transmitter 100 and a data receiver 1 10, according to an embodiment of the present invention.
The data transmitter 100 is configured to divide variable length data 120 to a predetermined number of sub-data packets 142_1 to 142_n and to send out the predetermined number of sub-data packets 142_1 to 42_n.
The data receiver 110 is configured to receive the predetermined number of sub-data packets 142_1 to 142_n to which the variable-length data 120 is divided. The data receiver 110 may further be configured to combine the received sub-data packets 42_1 to 142_n or, depending on a used channel coding, at least a part of the received sub-data packets 142_1 to 142_n in order to obtain the data 120 of variable length.
In embodiments, the predetermined number of sub-data packets 142_1 through 142_n may be a fixed (or non-variable) number of sub-data packets, that is, where n is a natural number greater than or equal to two, where n is not variable. The data transmitter can thus be designed to always divide the variable-length data (irrespective of a length thereof) to the same number n of sub-data packets 142_1 to 142_n. Accordingly, the lengths of the individual sub-data packets 142_1 to 142_n may depend on the length of the variable-length data 120.
As can be seen by way of example in FIG. 1, the variable-length data 120 can be divided independently of a length thereof into n = 5 sub-data packets 142_1 to 142_5.
In embodiments, the sub-data packets 142_1 to 142_n may be transmitted within a fixed (or non-variable) time interval 143. Furthermore, the sub-data packets 142_1 to 142_n can be transmitted at a time interval, so that there are transmission pauses between the sub-data packets 142_1 to 142_n. Since the lengths of the individual sub-data packets 142_1 to 142_n depend on the length of the variable-length data 120, and the data is transmitted within the fixed time interval 143, the transmission pauses between the sub-data packets 142_1 to 142_n are also the length of the variable-length data 120 dependent.
In embodiments, the sub-data packets may be transmitted using a time-hopping pattern and / or frequency hopping pattern 140.
In embodiments, the frequency hopping pattern 140 may indicate a sequence of transmission frequencies or transmission frequency jumps with which to transmit the sub-data packets 142_1 to 142_n.
For example, a first sub-packet 142_1 having a first transmission frequency (or in a first frequency channel) and a second sub-packet 142_2 having a second transmission frequency (or in a second frequency channel) may be transmitted, wherein the first transmission frequency and the second transmission frequency are different. The frequency hopping pattern can define (or specify, or specify) the first transmission frequency and the second transmission frequency. Alternatively, the frequency hopping pattern may indicate the first transmission frequency and a frequency spacing (transmission frequency jump) between the first transmission frequency and the second transmission frequency. Of course, the frequency hopping pattern may also indicate only the frequency spacing (transmission frequency hop) between the first transmission frequency and the second transmission frequency.
In embodiments, the time hopping pattern may indicate a sequence of transmission times or transmission time intervals, , which are Subdatenpakete 142_1 to 142_n to send.
For example, a first sub-data packet 142_1 at a first transmission time (or in a first transmission time slot) and a second sub-data packet 142_2 at a second transmission time (or in a second transmission time contactor) are sent, wherein the first transmission time and the second transmission time are different. The time jump pattern can define (or specify, or specify) the first transmission time and the second transmission time. Alternatively, the time-jump pattern may indicate the first transmission time and a time interval between the first transmission time and the second transmission time. Of course, the time jump pattern may also indicate only the time interval between the first time and the second transmission time.
A time and frequency hopping pattern 140 may be the combination of a frequency hopping pattern and a time hopping pattern, ie a sequence of transmission times or transmission time intervals with which the sub-data packets 142_1 to 142_n are transmitted, wherein transmission times (or transmission frequency jumps) are assigned to the transmission times (or transmission time intervals).
In other words, the data transmitter 100 may be configured to transmit the variable length data 120 using the telegram splitting method. In this case, the variable length data 120 may be a telegram, wherein the data transmitter 100 is designed to divide the telegram into the fixed predetermined number of sub-data packets 142_1 to 142_n (or data subpackets or sub-data packets), wherein each of the plurality of sub-data packets is shorter than the telegram , The plurality of sub-data packets may be transmitted using the frequency hopping pattern and / or time-hopping pattern. For example, each of the plurality of sub-data packets by the frequency hopping pattern and / or time jump pattern, a transmission frequency (or a transmission frequency jump with respect to a previous data packet) and / or a transmission time (or' Transmission time interval, or transmission time slot, transmission time jump relative to a previous sub-data packet assigned). Furthermore, the plurality of sub-data packets 142_1 to 142_n can be transmitted at a time interval, so that there are transmission pauses between the sub-data packets 142_1 to 142_n.
In embodiments, the data transmitter 100 may include a transmitter (transmitter) 102 configured to transmit the data 20. The transmitting device 102 may be connected to an antenna 104 of the data transmitter 100. The data transmitter 100 may further include a receiving device (receiver) 106 configured to receive data. The receiving device may be connected to the antenna 104 or to another (separate) antenna of the data transmitter 100. The data transmitter 100 may also include a combined transceiver.
The data receiver 110 may include a receiver 116 that is configured to receive the data 120. The receiving device 116 may be connected to an antenna 114 of the data receiver 110. Further, the data receiver 110 may include a transmitter 12 configured to transmit data. The transmitting device 112 may be connected to the antenna 114 or to another (separate) antenna of the data receiver 110. The data receiver 110 may also include a combined transceiver.
In embodiments, the data transmitter 100 may be a sensor node, while the data receiver 110 may be a base station. Of course, it is also possible that the data transmitter 100 is a base station while the data receiver 10 is a sensor node. Furthermore, it is possible that both the data transmitter 100 and the data receiver 1 are 10 sensor nodes. Furthermore, it is possible that both the data transmitter 100 and the data receiver 110 are base stations.
In the following, detailed exemplary embodiments of the transmission method presented with reference to FIG. 1, which can be carried out by the data transmitter 100 and the data receiver 0, are explained in greater detail.
Embodiments allow a transmission of different length data packets with a telemetry system.
Instead of adapting the hop number (number of sub-data packets) to the data volume, in embodiments the length of the hops (length of the sub-data packets) is adapted to the data volume.
An adaptation of the hop number to the data volume has the disadvantage that additional signaling information (eg in the form of preambles) in the expansion sequence
must be inserted. This increases the transmission time of the telegram in the channel and thus offers a higher susceptibility to interference. Furthermore, additional hops require a preamble. Another disadvantage arises from the variable number of sub-packages. If subpackets are added to the telegram, the transmission duration and thus also the latency during transmission increases. This is a problem, especially for time-critical applications.
In contrast, in embodiments, the telegram splitting method is used and the lengths of the subpackets (sub data packets) 142_1 to 142_n are varied without overlapping the subpackets 142_1 to 142_n. If the lengths of the subpackets in classical systems with frequency hopping were varied, there would be a temporal superimposition of the individual subpackets.
First detailed Ausführunqsbeispiel
The data 120 of a telegram can be transmitted to several hops (sub-data packets) 142_1 to 142_n (see also DE 10 201 1 082 098 B4). In traditional hopping systems, the subpackets are transmitted directly to each other, but in the telegram splitting method there is still room for further data before and after the respective subpackets 142_1 to 142_n.
Instead of varying the number of subpackets, in embodiments the length of the subpackets 142_1 to 142_n is varied. This means that if there are only a few data 120, the number of symbols (also referred to as length) in the subpackets 142_1 to 142_n is less than when there is more data. ''
2 shows a diagram of an occupancy of a transmission channel during the transmission of the variable length data 120 using a fixed number of sub-data packets 142_1 to 142_7 within a fixed time interval 143. The ordinate describes the frequency and the abscissa the time.
As can be seen in FIG. 2, the variable length data 120 (regardless of a length thereof) can always be divided into n = 7 sub-data packets 142_1 to 142_7. The sub-data packets 142_1 to 142_7 are distributed within the fixed time interval 143 both in time and in frequency (ie, using a time and frequency hopping pattern), so that transmission pauses between the sub-data packets 142_1 to 142_7 are present.
The sub-data packets 142_1 to 1 2_7 can be provided with synchronization sequences or partial synchronization sequences. If the sub-data packets 142_1 to 142_7 are provided with synchronization sequences, then a complete synchronization of the respective sub-data packet or detection or localization thereof in a receive data stream is possible on the receiver side based on the respective synchronization sequence. If the sub-data packets 142_1 to 142_7 are provided with partial synchronization sequences, then a complete synchronization of the sub-data packets or detection of the same in a receive data stream (only) over several or all partial synchronization sequences into which the synchronization sequence is divided is possible on the receiver side.
In other words, Fig. 2 shows a structure of a telegram with variable partial packet lengths. There, a midamble (a synchronization sequence or partial synchronization sequence located in the middle of the sub-data packet) 144 is inserted for synchronization and the data 146 is applied to the right (or before) and left (or after) thereof. The length of the data blocks varies according to the number of data to be transmitted.
Instead of a midamble, the synchronization sequence can be inserted anywhere in the subpackage 142_1 to 142_n and even split into several sequences.
In current systems, the distances between the subpackets are determined by the pauses (no transmission) between the subpackets. This scheme can be seen in Fig. 3. In detail, FIG. 3 shows in a diagram an allocation of a transmission channel in the transmission of data using a plurality of sub-data packets 142_1 to 142_7 with transmission pauses which specify the time intervals to, ti and t2 between the sub-data packets 142_1 to 142_7. The ordinate describes the frequency and the abscissa the time. In other words, Fig. 3 shows a definition of the jump pattern by the pauses between the sub-packets 142_1 to 142 _7. It can be seen that the distances between the sub-packets 142_1 to 142_7 are defined by the end of the previous sub-packet at the beginning of the next sub-packet. If these pauses are now constant for different lengths, the intervals between the synchronization sequences change with each other. In order for the receiver to be able to correctly detect the data, it first requires the information as to which length the subpackets 142_1 to 142_7 possess, or all possibilities in the receiver are tried until the correct length or the distance between the synchronization sequences is found.
In embodiments, the number n of the sub-packets 142_1 to 142_n may be the same (on the transmitter side or on the waveform side) for several lengths of data to be transmitted. The length of the subpackets 142_1 to 142_n changes with the amount of data to be transmitted.
In embodiments, the number of received symbols in the decoder can vary (receiver side or decoder side) according to the telegram length. If this is unknown, the decoder can examine all possible lengths for their likelihood of being transmitted.
Second detailed embodiment
In the previous detailed embodiment, it is possible to keep the pauses between the subpackets constant (see Fig. 3). This means that the pauses are set independently of the subpacket lengths since, by definition, the end of the previous one was specified at the beginning of the next subpacket. However, this can have the disadvantage that the distances between the synchronization sequences for different telegram lengths are no longer constant, as a result of which several detections for the different distances must be carried out.
If the distances between the synchronization sequences are kept constant over the different telegram lengths, it is possible to carry out all lengths with only a single synchronization. This shortens the pauses between the subpackages accordingly if the length of the user data per message increases.
This offers the advantage that existing receivers can continue to use the same detection algorithms and only the decoder must be adapted to the variable telegram lengths.
Fig. 4 is a diagram showing an assignment of a transmission channel in the transmission of data 120 variable length using a fixed number of Subdatenpaketen 142_1 to 142 _7 within a predetermined time interval 143, wherein distances t3, t 4 and i 5 between the synchronization sequences or partial synchronization sequences are constant. The ordinate describes the frequency and the abscissa the time.
In other words, Fig. 4 shows a definition of the jump pattern by the distances of the synchronization sequences between the sub-packets.
In embodiments, the number n of subpackets 142_1 to 142_n may be the same for different lengths of data to be transmitted (transmitter side or waveform side). The pauses between the subpackets can thereby change with the telegram length, with the intervals of the synchronization sequences (of the subpackets 142_1 to 142_n) remaining the same.
In embodiments, the synchronization for all telegram lengths can be done together (receiver side or decoder side). It is for the detection of no knowledge of the transmitted telegram length necessary.
Third detailed embodiment
In embodiments, the message can be subdivided into a core sequence and an extension sequence. Here, the core sequence represents the minimum length of the telegram, which must therefore always be transmitted.
By dividing the telegram into a core sequence and an extension sequence, it is possible for the receiver to already decode part of the information in advance before the complete telegram has been transmitted.
5 shows a schematic view of a structure of the sub-data packets 142_1 to 142_n, each having a synchronization sequence, a core sequence and an extension sequence. As can be seen in FIG. 5, the core sequence 147 may be arranged (directly) adjacent to the synchronization sequence 144 in the respective sub-data packets 142_1 to 142_n. Furthermore, in the respective sub-data packets 142_1 to 142_n, the extension sequence 148 may be arranged (directly) adjacent to the core sequence 147. For example, a first part of the core sequence may be arranged before the synchronization sequence, while a second part of the core sequence may be arranged after the synchronization sequence. The first part of the core sequence and the second part of the core sequence can be the same length. A first part of the extension sequence may be arranged before the first part of the core sequence, while a second part of the extension sequence may be arranged after the second part of the core sequence. The first part of the extension sequence and the second part of the extension sequence can be the same length. The synchronization sequence can be arranged in the middle of the respective sub-data packet 142_1 to 142_n.
In other words, Fig. 5 shows a construction of a sub-packet (or sub-packet) 142_1 to 142_n having a core sequence and an extension sequence. It will be appreciated that the symbols of the kernel are located closest to the synchronization symbols. This makes it possible to decode the core independently of the extension, so it is not necessary to know the length of the extension.
This also offers the great advantage that the size of the core can be set to an already existing length of an existing system. Thus, the synchronization and decoding of the existing system can continue to be used and only one more decoder for the extension needs to be added.
In embodiments, a telegram can be divided into a core and an extension (transmitter side or waveform side). In contrast to DE 10 201 1 082 098 B4, however, this is carried out with a constant number of subpackets by the variation of their lengths.
In embodiments, the decoding can take place in two separate steps (detection side or decoder side) after the detection. For example, the synchronization sequence can be used to decode the core sequence, while a reencoded core sequence can be used to decode the extension sequence.
Fourth Detailed Embodiment
The subdivision of the telegram into a core and the extension results in the possibility of separate decoding of the core from the extension. Thus, for example, the length of the entire telegram can no longer be signaled in advance, but directly in the core of the transmitted telegram.
In this case, the necessary information for recovering the length information is deliberately introduced into the core in the transmitter. The receiver first decodes the core and can deduce the length of the entire telegram. If this length is known, the correspondingly necessary data can be loaded from a buffer, for example, and the extension can be decoded.
If an error correction (eg FEC = Forward Error Correction) is used for the transmission of symbols, these can either be split into two independent parts or an entire coding of the message is carried out the premature partial decoding of the length information exist.
If the telegram length is already known in advance to the receiver or this is achieved by trying all the possibilities, it is also possible to introduce any useful data in the core. Also possible is a combination of length information and other data.
The length of the core symbols can be chosen arbitrarily large, but they should not be much larger than the minimum expected telegram length to avoid the transmission of unnecessary additional data. This is necessary if there is less data than needed for the core.
In addition to the signaling of the length information, further parameters can be inserted in the core, which the receiver can use for the decoding.
In embodiments, a length information and / or further signaling information can be introduced into the core (on the transmitter side or on the waveform side).
In embodiments, (decoder side) after detection, the decoding in two separate steps, wherein for the decoding of the extension, a part of the information obtained from the core is used.
Fifth Detailed Embodiment
As already shown in the previous detailed embodiments, the data may be appended outwardly from the synchronization sequence 144. The more data that is available, the longer will be the lengths of the sub-packets (sub-data packets) 142_1 to 142_n. This may result in the disadvantage that the error probability of the symbols increases linearly with increasing distance from the synchronization sequence 144 due to estimation errors. This means that symbols which are farther away from the synchronization sequence 14 are generally incorrect more often by estimation errors in the receiver than symbols which (in the respective sub-data packet 142_1 to 42_n) are closer to the synchronization sequence 144.
To avoid this problem, an iterative decoding can be used, in which case the symbols are close to each other. at the synchronization sequence 144 decoded. These are recalculated with the help of reencoding and can thus also be used for the estimation in the receiver. As a result, a longer synchronization sequence is available, with the help of which the parameters can be better estimated. This step can be repeated until the complete telegram has been received.
6 shows a schematic view of a structure of the sub-data packets 142_1 to 142_n, each having a synchronization sequence 144, a core sequence 147 and an extension sequence 148 together with a decoder-side distribution of the respective sub-data packet corresponding to the sequences for an iterative decoding. The structure of the sub-data packet shown in FIG. 6 corresponds to the structure of the sub-data packet shown in FIG.
As indicated in FIG. 6, in a zeroth step 150, the core sequence 147 may be decoded using the synchronization sequence 144. In a first step 152, the decoded core sequence (or at least a portion of the decoded core sequence) may be reencoded to obtain a reencoded core sequence, and a first portion of the extension sequence 148 may be decoded using the reencoded core sequence. In a second step 154, the decoded first portion of the extension sequence (or at least a portion thereof) may be reencoded to obtain a reencoded first portion of the extension sequence, and a second portion of the extension sequence 148 may be decoded using the reencoded first portion of the extension sequence. "
In other words, FIG. 6 shows an iterative decoding on the example of a sub-packet (sub-data packet). In this case, first the core 147 can be decoded in step 0. If its data are present, reencoding can be performed and for the estimation the synchronization sequence 144 is thus extended by the two parts from step 0. Thereafter, the estimation can be carried out again and the data from step 1 decoded. Similarly, this can also be done for step 2.
For this kind of iterative decoding to be possible, the inter eaverver can fulfill this requirement. There are also different possibilities of design here. It should be noted that the data for each decoding step further outward (ie away from the synchronization sequence 144) are attached. An example of such an interleaver is shown in FIG. 7.
7 shows a schematic view of a structure of the sub-data packets 142_1 to 142_n, each having a synchronization sequence 144, a core sequence 147 and an extension sequence 148, the data corresponding to the core sequence 147 and the extension sequence 148 being arranged in the respective sub-data packets 142_1 to 142_n are that a distance of the coded data in relation to an influence length of a code used for the coding of the data is increased (or maximized).
In other words, Fig. 7 shows an example of an interleaver for iterative decoding. Here, the decoding is done iteratively in two steps, first the core is decoded and then the extension.
In embodiments, the interleaver design can be selected (transmitter side or waveform side) such that an iterative decoding is possible. The encoding of the telegram can be done so that a premature partial decoding with only a part of the data is possible.
In embodiments, the decoder may decode part of the message (or the sub-data packet) and use the obtained information to re-estimate frequency, phase, and / or time.
Sixth detailed embodiment
Due to a predetermined latency request to the system, the pauses between the subpackets (sub-data packets) 142_1 to 142_n must not exceed a maximum length in order to be able to transmit all subpackets 142_1 to 142_n within the request (within the fixed time interval 143). This means that the distances between the subpackets 142_1 to 142_n can not become arbitrarily large.
Through the use of quartz, which always have a tolerance, the entire telegram must be transmitted within a certain period of time, since otherwise the symbol times relative to the detection time can no longer be met. This time span in which the entire telegram must be transmitted is called the coherence time. By this effect, it is also necessary to limit the duration of pauses between the sub-pacts.
With a minimally defined distance between two synchronization sequences of successive subpackets 142_1 to 142_n, there is a maximum size which is the
Sub-packets 142_1 to 142_n must not exceed, which is exactly reached when the break is completely filled with symbols of the two sub-packages.
In practice, however, it is better to define the maximum size smaller so that a break is still maintained between the subpackets 142_1 to 142_n in order to become more robust against disturbances and, under certain circumstances, to be able to recharge the energy stores.
In order not to limit the maximum size of the telegram by limiting the duration of the pauses, the telegram can be subdivided into so-called blocks. This means that once the maximum length of the subpackages mentioned above has been reached, the signal is split into at least two blocks. This scheme can be seen in FIG.
In detail, Fig. 8 is a diagram showing an occupancy of a transmission channel in the transmission of data using a plurality of sub-data packets 142_1 to 142_n, which are combined in blocks 160_1 to 180_m. The ordinate describes the frequency and the abscissa the time.
The Subdatenpakete 142_1 to 142 can _n ' in this case be divided into m blocks 160_1 to 160_m (uniformly) so that each of the m blocks to 160_m at least two Subdatenpakete 160_1.
As can be seen by way of example in FIG. 8, the sub-data packets 142_1 to 142_n can be combined into blocks 160_1 to 160_m of three sub-data packets, so that a first block 160_1 the sub-data packets 142_1 to 142_3, a second block 160_2 the sub-data packets 142_4 to 142_6 , and an m-th block 160_m having sub-data packets 142_n-2 to 142_n.
In other words, Fig. 8 shows a subdivision of a telegram into a plurality of blocks 160_1 to 180_m. Here, the number, the length, the synchronization sequences and also the hopping pattern in each block 160_1 to 160_m can be arbitrarily and independently selected from the previous, as long as it is known to the receiver.
A big advantage of dividing the telegram into blocks 160_1 to 160_m is the increased coherence time since the blocks 160_1 to 160_m are detectable by themselves.
This allows the synchronization time, which runs away through quartz offsets, to be recalculated after each block and retraced accordingly.
If an error correction is used, it is possible either to calculate the coding over the entire telegram or to view the coding separately for each block 160_1 to 160_m. The latter has the advantage that a part of the telegram can be prematurely decoded. If an error has occurred during this premature decoding and the transmitted data can not be reconstructed, the reception of the further blocks 160_1 to 160_m can be aborted and thus the power consumption can be reduced.
In embodiments, (at the transmitter side or waveform side) a telegram can be divided into at least two independent blocks 160_1 to 160_m, which are detectable for themselves. Here, the number of sub-packets 142_1 to 142_n of the blocks 160_1 to 160_m may be different, the length between the blocks 160_1 to 160_m may vary and also the hopping pattern may be independent of each other.
In embodiments (receptions and seminars can ' gerseitig or decoder side) further blocks are decoded and the reception data are merged from both blocks according to the detection of a first block. The receiver may have the ability to resynchronize each block for itself.
Seventh detailed Ausführunqsbeispiel
It is also possible to signal the number and size of the coming blocks in the first or previous block, thus a flexible telegram length is also possible here. Also, the distances and the hopping pattern can be signaled to the following blocks. If a pseudo-random pattern to be generated, z. B. a portion of the transmitted data (eg CRC (CRC = Cyclic Redundancy Check) or unknown user data) are derived from the previous block to generate the distances, hopping pattern, synchronization sequence and other transmission parameters. '
In embodiments, signaling of a number, a size, a jump pattern, etc. in the first or previous block can take place (transmitter side or waveform side).
In embodiments, the decoding of the entire telegram can be done stepwise (on the receiver side or on the decoder side), after a part of the already decoded information is used for the signaling of the following blocks.
Eighth detailed Ausführunqsbeispiel
Instead of subdividing into blocks 160_1 to 160_m, it is also possible to add individual subpackets (sub data packets) to the telegram in order to further increase the maximum length of the telegram. This process is described in detail in DE 10 201 1 082 098 B4.
However, the method described there has the disadvantage that the lengths of the subpackets could not be changed. With the method herein, a combination of variable sub-packet lengths and their number can now be realized.
It is also a combination of the blocks described in the sixth detailed embodiment and the insertion of individual sub-packages possible. This results in a high degree of flexibility. If, for example, only a few data are required above the maximum size of a block, it makes sense to add individual subpackages to the telegram. However, if more data is added it is better to create a new block as the coherence time is extended.
Similar to the seventh detailed embodiment, it is also possible here to signal incoming subpackets in previous data. Be it the number, the length, the jump pattern or other transmission parameters.
9 shows a diagram of an occupancy of a transmission channel during the transmission of the variable length data 120 using a predetermined number of sub-data packets 142_1 to 142_7, wherein the predetermined number of sub-data packets 142_1 to 142_7 are appended with additional sub-data packets 162_1 and 162_2.
When the maximum length of the data 120 has been exceeded, the data 120 of variable length can fall short of a time-defined minimum distance between the sub-data packets 142_1 to 142_7 or even one during the transmission of the variable length data 120 within the predetermined time interval
Overlapping the sub-data packets 142_1 to 142_7 would have to be divided into further sub-data packets 162_1 and 162_2.
In other words, Fig. 9 shows a structure of a telegram with a variable number of subpackets.
In embodiments, the number of sub-packets used may not be constant (transmitter side or waveform side) and in addition, the lengths of the sub-packets may vary.
In embodiments, further subpackets can be received after the detection of a first block (receiver side or decoder side), which can not be independently decoded. The hopping pattern of these subpackets can be defined or transmitted.
Further embodiments
10 shows a flow chart of a method 200 for transmitting variable length data. The method 200 comprises a step 202 of dividing the variable-length data into a predetermined number of sub-data packets and a step 204 of transmitting the sub-data packets.
FIG. 1 shows a flowchart of a method 210 for receiving variable length data. The method 210 includes a step 212 of receiving a predetermined number of sub-data packets to which the variable-length data is divided.
In embodiments, subpacket lengths may vary with a constant number of subpackets.
In embodiments, iterative decoding can be done to obtain the length information.
In embodiments, a subdivision of a telegram into blocks with possibly separate decoding can take place.
Embodiments provide a system for transferring data from many sensor nodes to a base station. However, the concepts described herein may be used for any arbitrary transmission if the channel is not coordinated (ALOHA or Slotted-ALOHA access method) and thus the receiver does not know when a packet is being transmitted. In addition, this can lead to overlapping with other participants, causing interference during transmission.
The used radio transmission band may, but need not be reserved exclusively for this transmission. The frequency resource can be shared with many other systems, making reliable information transmission difficult.
In embodiments, different lengths of utzdaten can be transmitted in a telegram. In this case, the telegram splitting method can be used by which it is possible to vary the lengths of the subpackets, whereby no additional signaling information is needed.
In embodiments, the estimation accuracy can be increased by iterative decoding for longer subpackets.
In embodiments, a telegram can be divided into several independent blocks. As a result, the maximum number of data to be transmitted can be further increased.
Although some aspects have been described in the context of a device, it will be understood that these aspects also constitute a description of the corresponding method such that a block or device of a device may also be described as a corresponding method step or method .is to be understood as a feature of a process step. Similarly, aspects described in connection with or as a method step also represent a description of a corresponding block or detail or feature of a corresponding device. Some or all of the method steps may be performed by a hardware device (or using a hardware device). Apparatus), such as a microprocessor, a programmable computer or an electronic circuit. In some embodiments, some or more of the most important method steps may be performed by such an apparatus.
Depending on particular implementation requirements, embodiments of the invention may be implemented in hardware or in software. The implementation may be performed using a digital storage medium, such as a floppy disk, a DVD, a bi-ray disc, a CD, a ROM, a PROM, an EPROM, an EEPROM or FLASH memory, a hard disk or other magnetic disk or optical memory are stored on the electronically readable control signals that can cooperate with a programmable computer system or cooperate such that the respective method is performed. Therefore, the digital storage medium can be computer readable.
Thus, some embodiments of the invention include a data carrier having electronically readable control signals capable of interacting with a programmable computer system such that one of the methods described herein is performed.
In general, embodiments of the present invention may be implemented as a computer program product having a program code, wherein the program code is operative to perform one of the methods when the computer program product runs on a computer.
The program code can also be stored, for example, on a machine-readable carrier.
Other embodiments include the computer program for performing any of the methods described herein, wherein the computer program is stored on a machine-readable medium.
In other words, an embodiment of the method according to the invention is thus a computer program which has a program code for performing one of the methods described herein when the computer program runs on a computer.
A further embodiment of the inventive method is thus a data carrier (or a digital storage medium or a computer-readable medium) on which the computer program is recorded for carrying out one of the methods described herein. The data carrier, the digital storage medium or the computer-readable medium are typically representational and / or non-transient or non-transient.
A further embodiment of the method according to the invention is thus a data stream or a sequence of signals, which represent the computer program for performing one of the methods described herein. The data stream or the sequence of signals may be configured, for example, to be transferred via a data communication connection, for example via the Internet.
Another embodiment includes a processing device, such as a computer or a programmable logic device, that is configured or adapted to perform one of the methods described herein.
Another embodiment includes a computer on which the computer program is installed to perform one of the methods described herein.
Another embodiment according to the invention comprises a device or system adapted to transmit a computer program for performing at least one of the methods described herein to a receiver. The transmission can be done for example electronically or optically. The receiver may be, for example, a computer, a mobile device, a storage device or a similar device. For example, the device or system may include a file server for transmitting the computer program to the recipient.
In some embodiments, a programmable logic device (eg, a field programmable gate array, an FPGA) may be used to perform some or all of the functionality of the methods described herein. In some embodiments, a field programmable gate array may cooperate with a microprocessor to perform one of the methods described herein. In general, in some embodiments, the methods are performed by any hardware device. This may be a universal hardware such as a computer processor (CPU) or a graphics card (GPU) or hardware specific to the method, such as an ASIC.
The devices described herein may be implemented, for example, using a hardware device, or using a computer, or using a combination of a hardware device and a computer.
The devices described herein, or any components of the devices described herein, may be implemented at least in part in hardware and / or software (computer program).
For example, the methods described herein may be implemented using a hardware device, or using a computer, or using a combination of a hardware device and a computer.
The methods described herein, or any components of the methods described herein, may be performed at least in part by hardware and / or by software.
The embodiments described above are merely illustrative of the principles of the present invention. It will be understood that modifications and variations of the arrangements and details described herein will be apparent to others of ordinary skill in the art. Therefore, it is intended that the invention be limited only by the scope of the appended claims and not by the specific details presented in the description and explanation of the embodiments herein.
claims
1 . A data transmitter (100) for transmitting variable length data (120), the data transmitter (100) adapted to split the variable length data (120) to a predetermined number of sub-data packets (142_1: 142_n) and the sub-data packets (142_1 : 42_n).
The data transmitter (100) of claim 1, wherein the data transmitter (100) is adapted to transmit the sub-data packets (142_1: 142_n) within a predetermined time interval (143).
The data transmitter (100) according to any one of claims 1 to 2, wherein the data transmitter (100) is adapted to transmit the sub-data packets (142_1: 142_n) spaced apart in time such that transmission pauses exist between the sub-data packets (142_1: 142_n).
4. Data transmitter (100) according to any one of claims 1 to 3, wherein the data transmitter (100) is adapted to transmit the sub-data packets (1 2_1: 142_n) with a predetermined time interval, so that the time interval between the sub-data packets (142_1: 142_n) is constant regardless of a length of the variable length data (120).
The data transmitter (100) of any one of claims 1 to 3, wherein the data transmitter (100) is adapted to transmit the sub-data packets (142_1: 142_n) at a time interval dependent on the length of the variable-length data (120) such that a time interval between predetermined areas of the sub-data packets (142_1: 142_n) is constant independently of a length of the variable-length data (120).
The data transmitter (100) of any one of claims 1 to 5, wherein the data transmitter (100) is adapted to provide at least a portion of the sub-data packets (142_1: 42_n) with synchronization sequences (144).
The data transmitter (100) according to any one of claims 1 to 5, wherein the data transmitter (100) is anhenohilH p t to yi iminrtafit pinpn part ripr Subdatenoakete C 142 1: 142 n) with
The data transmitter (100) of claim 7, wherein the data transmitter (100) is adapted to transmit the sub-data packets (142_1: 142_n) at a time interval dependent on the length of the variable-length data (120), such that a time interval between (to, ti, t 2 ) is constant to the sub-synchronization sequences (144) of the sub-data packets (142_1: 142_n) irrespective of a length of the variable-length data (120).
The data transmitter (100) of any one of claims 7 to 8, wherein the data transmitter (100) is adapted to divide a synchronization sequence into the sub-sync sequences.
The data transmitter (100) of any one of claims 1 to 9, wherein the data (120) comprises core data and extension data, the core data having a fixed length and the extension data having a variable length.
1 1. The data transmitter (100) of claim 10, wherein the data transmitter (100) is adapted to provide the core data with signaling information for signaling the length of the extension data.
The data transmitter (100) of any one of claims 10 to 11, wherein the data transmitter (100) is adapted to split the core data and the extension data onto the sub-data packets (142_1: 142_n).
The data transmitter (100) according to any one of claims 10 to 12, wherein the data transmitter (100) is adapted to divide the core data onto the sub-data packets (142_1: 142_n) such that the respective part of the sub-data packets (142_1: 142_n) Core data is arranged adjacent to the (sub-) synchronization sequences.
14. The data transmitter (100) according to claim 13, wherein the data transmitter (100) is designed to divide the core data onto the sub-data packets (142_1: 142_n) such that in the sub-data packets the respective part of the core data evenly before and after the respective (Sub -) synchronization sequences (144) is arranged.
The data transmitter (100) of any of claims 12 to 13, wherein the data transmitter
Ι ΠΠ ai icnohilHot ict ι im Hie »Pru / oitori inncHaton rloror if the» Qi i tann lio *.! respective part of the extension data is arranged adjacent to the respective part of the core data.
16. The data transmitter (100) according to claim 15, wherein the data transmitter (100) is designed to divide the extension data onto the sub-data packets (142_1: 142_n) in such a way that the respective part of the extension data in the sub-data packets (142_1: 1 2_n) is uniform and arranged according to the respective part of the core data.
17. Data transmitter (100) according to one of claims 1 to 16, wherein the data transmitter (100) is designed to divide the core data into sub-data packets (142_1; 142_n) depending on lengths of the (sub) synchronization sequences, such that sub-data packets have longer (sub-) synchronization sequences contain a larger amount of core data than sub-data packets (142_1: 1 2_n) with shorter (sub-) synchronization sequences.
The data transmitter (100) according to one of claims 1 to 17, wherein the data transmitter (100) is designed to divide the extension data into sub-data packets (142_1: 142_n) depending on lengths of the (sub-) synchronization sequences, such that sub-data packets ( 142_1: 142_n) with longer (sub-) synchronization sequences contain a larger amount of extension data than sub-data packets (142_1: 142_n) with shorter (sub-) synchronization sequences.
The data transmitter (100) of any one of claims 1 to 18, wherein the data transmitter (100) is adapted to divide the number of sub-data packets (142_1: 142_n) into at least two independent blocks (160_1: 60_m) of sub-data packets (142_1: 142_n). divide;
wherein the data transmitter (100) is adapted to divide the sub-data packets (142_1: 142_n) into at least two blocks (160_1: 60_m) of sub-data packets (142_1: 142_n) such that a first block of the at least two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) can be detected by itself on the receiver side.
The data transmitter (100) of claim 19, wherein the data transmitter (100) is adapted to provide the first block of sub-data packets with information about a second block of sub-data packets. (142_1: 142_n) of the at least two blocks (160_1: 160_m) of sub-data packets.
The data transmitter (100) of claim 20, wherein the information signals at least one of a length, a number of sub-data packets (142_1: 142_n) and a hopping pattern with which the sub-data packets are transmitted.
22. A data transmitter (100) according to any one of claims 19 to 21, wherein the data transmitter (100) is adapted to at least one of the two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) with a synchronization sequence for the synchronization of the sub-data packets (142_1 : 142_n) in a data receiver.
The data transmitter (100) according to any one of claims 1 to 22, wherein the data transmitter (100) is adapted to attach further sub-data packets (162_1, 162_2) to the sub-data packets (142_1: 142_n).
The data transmitter (100) according to any one of claims 1 to 23, wherein the data transmitter (100) is adapted to, if a length of the variable length data (120) is so large that when transmitting the sub-data packets (142_1: 142_n). within the predetermined time interval (143), a minimum value of the transmission pauses between the sub-data packets (142_1: 142_n) would be undershot, to divide the variable-length data (120) into at least one additional sub-data packet (162_1, 162_2).
25. The data transmitter (100) according to claim 24, wherein the data transmitter (100) is designed to provide the data contained in the sub-data packets (142_1: 142_n) of fixed numbers with information about the at least one additional sub-data packet (162_1, 162_2).
A data receiver (110) for receiving variable length data (120), the data receiver (110) being adapted to receive a predetermined number of sub-data packets (142_1: 142_n) to which the variable length data (120) are divided.
The data receiver (10) of claim 26, wherein the data receiver (110) is adapted to receive the sub-data packets (142_1: 142_n) within a predetermined time interval.
The data receiver (1 10) according to any one of claims 26 to 27, wherein the sub-data packets (42_1: 142_n) are temporally spaced apart so that there are pauses between the sub-data packets (142_1: 142_n).
The data receiver (1 10) of claim 28, wherein the transmission pauses between the sub-data packets (142_1: 142_n) are constant regardless of a length of the variable-length data (120).
The data receiver (1 10) according to claim 28, wherein the transmission pauses between the sub-data packets (142_1: 142_n) are dependent on the length of the variable-length data (120) such that a time interval between predetermined areas of the sub-data packets (142_1: 142_n) regardless of a length of the variable length data (120) is constant.
31. Data receiver (1 10) according to one of claims 26 to 30, wherein at least a part of the sub-data packets (142_1: 142_n) is provided with synchronization sequences (144);
wherein the data receiver (110) is adapted to detect the sub-data packets (142_1: 142_n) based on the synchronization sequences (144).
32. Data receiver (1 10) according to any one of claims 26 to 30, wherein at least a part of the sub-data packets (142_1: 142_n) is provided with sub-synchronization sequences (144);
wherein the data receiver (110) is configured to detect the sub-data packets (142_1: 142_n) based on the sub-synchronization sequences (144).
33. Data receiver (1 10) according to claim 32, wherein the time interval between the sub-synchronization sequences (144) is constant and / or the data receiver (1 10) is known.
The data receiver (1 10) of any one of claims 26 to 33, wherein the variable length data (20) comprises core data and extension data, the core data having a fixed length and the extension data having a variable length.
35. The data receiver (1 10) according to claim 34, wherein the core data is provided with signaling information for signaling the length of the extension data;
wherein the data receiver (110) is adapted to receive the extension data using the signaling information or to extract it from the sub-data packets.
The data receiver (1 10) according to any one of claims 34 to 35, wherein the core data and the extension data are divided among the sub-data packets.
37. Data receiver (1 10) according to one of claims 34 to 36, wherein the core data are subdivided in such a way onto the sub-data packets (142_1: 42_n) that in the sub-data packets (142_1: 142_n) the respective part of the core data adjacent to the (sub) ) Synchronization sequences is arranged.
38. The data receiver (1 10) as claimed in claim 37, wherein the core data are subdivided into the sub-data packets (142_1: 142_n) such that in the sub-data packets (142_1: 142_n) the respective part of the core data is distributed uniformly before and after the respective (sub-) Synchronization sequence is arranged.
39. Data receiver (1 10) according to any one of claims 34 to 38, wherein the extension data is divided among the sub-data packets (142_1: 142_n) such that in the sub-data packets (142_1: 142_n) the respective part of the extension data adjacent to the respective part of Core data is arranged.
40. The data receiver (1 10) according to claim 39, wherein the extension data are subdivided into the sub-data packets (142_1: 142_n) such that in the sub-data packets (142_1: 142_n) the respective part of the extension data is arranged uniformly before and after the respective part of the core data is.
41. Data receiver (1 10) according to one of claims 34 to 40, wherein the core data are divided into the sub-data packets (142_1: 142_n) as a function of lengths of the (sub) synchronization sequence, so that sub-data packets (142_1: 142_n) with longer (sub) ) Synchronization sequence contain a larger part of core data than sub-data packets (142_1: 142_n) with a shorter (sub-) synchronization sequence;
wherein the data receiver (110) is adapted to determine lengths of the pieces of core data contained in the respective sub-data packets (142_1: 142_n) based on the lengths of the (sub-) synchronization sequence included in the respective sub-data packets (42_1 : 1 2_n) are included.
42. The data transmitter (100) according to any one of claims 1 to 17, wherein the extension data depending on lengths of the (sub-) synchronization sequence to the sub-data packets (142_1: 142_n) are divided, so that sub-data packets (142_1: 142_n) with longer (Sub -) synchronization sequence contain a larger part of extension data than sub-data packets (1 2_1: 142_n) with a shorter (sub-) synchronization sequence;
wherein the data receiver (110) is adapted to determine lengths of the parts of extension data contained in the respective sub-data packets (142_1: 142_n) based on the lengths of the (sub-) synchronization sequence included in the respective sub-data packets (142_1 : 142_n) are included.
43. Data receiver (1 10) according to one of claims 37 to 42
wherein the data receiver (110) is adapted to decode and reencode a first portion of the respective portion of the variable length data (120) using the (sub) synchronization sequences to obtain a first portion of reencoded data;
wherein the data receiver (110) is adapted to decode a second portion of the respective portion of the variable length data (120) using the first portion of reencoded data.
The data receiver (1 10) of claim 43, wherein the data receiver (110) is adapted to decode the second portion of the respective portion of the variable length data (120) using the first portion of reencoded data by a second portion to obtain from reencoded data;
wherein the data receiver (110) is adapted to decode a third portion of the respective portion of the variable length data (120) using the second portion of reen coded data.
45. Data receiver (1 10) of any ' of claims 43 to 44, wherein in the Subdatenpaketen (142_1: 142_n) of the first region to the (sub-) synchronization sequence is located immediately adjacent, and wherein the second region immediately adjacent to the first area is arranged.
46. Data receiver (1 10) according to one of claims 26 to 45, wherein the number of sub-data packets is divided into at least two independent blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) such that a first block of the at least two blocks of sub-data packets (142_1: 142_n) is detectable for itself;
wherein the data receiver (110) is adapted to detect for itself the first block of the at least two blocks of sub-data packets (142_1: 142_n).
The data receiver (1 10) of claim 46, wherein the first block of sub-data packets of the at least two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) includes information about a second block of the at least two blocks (160_1: 160_m) of Sub-data packets (142_1: 142_n) is provided;
wherein the data receiver (110) is adapted to receive the second block of the at least two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) using the information.
48. The data receiver (1 10) according to claim 47, wherein the information comprises at least one of a length, a number of sub-data packets (142_1: 142_n) and a hopping pattern with which the sub-data packets (142_1: 142_n) are sent.
49. Data receiver (1 10) according to one of claims 46 to 48, wherein at least one of the at least two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) having a synchronization sequence for the synchronization of the sub-data packets (142_1: 142_n) in a data receiver ( 1 10) is provided;
wherein the data receiver (110) is adapted to detect the at least one of the at least two blocks (160_1: 160_m) of sub-data packets (142_1: 142_n) using the respective synchronization sequence.
The data receiver (1 10) of any one of claims 26 to 49, wherein the data receiver (110) is adapted to receive at least one further sub-data packet (162_1, 162_2) appended to the number of sub-data packets (142_1: 142_n) ,
51. Data receiver (1 10) according to claim 50, wherein the data contained in the sub-data packets (42_1: 142_n) of fixed numbers is provided with information about the at least one additional sub-data packet (62_1, 162_2);
wherein the data receiver (110) is adapted to receive the at least one additional sub-data packet (142_1: 142_n) using the information.
52. System, having the following features:
a data transmitter (100) according to any one of claims 1 to 25; and
a data receiver (1 10) according to any one of claims 26 to 49.
53. Method (200) for transmitting variable length data, comprising the steps of:
Dividing (202) the variable-length data into a predetermined number of sub-data packets; and
Transmitting (204) the sub-data packets within a predetermined time interval.
54. Method (210) for receiving variable length data, comprising the steps of:
Receiving (212) a predetermined number of sub-data packets within a predetermined time interval to which the variable-length data is divided.
55. Computer program for carrying out the method according to claim 53 or 54.
56. A data transmitter (100) for transmitting variable length data to a data receiver (110), the data transmitter (100) being adapted to split the variable length data (120) to a fixed number of sub data packets (142_1: 142_n) send out the sub-data packets (142_1: 142_n) within a predetermined time interval (143) so that transmission pauses between the sub-data packets (142_1: 142_n) do not fall below a minimum value;
wherein the data transmitter (100) is adapted to, if a length of the variable length data (120) is so large that at a transmission of the sub-data packets (142_1: 142_n) within the predetermined time period (143), the minimum value of the transmission pauses between the sub-data packets (142_1: 142_n) would be subdivided to divide the variable-length data (120) into additional sub-data packets (162_1, 162_2).
| # | Name | Date |
|---|---|---|
| 1 | 201937015586-FORM 3 [18-03-2024(online)].pdf | 2024-03-18 |
| 1 | 201937015586.pdf | 2019-04-18 |
| 2 | 201937015586-FORM 13 [12-03-2024(online)].pdf | 2024-03-12 |
| 2 | 201937015586-STATEMENT OF UNDERTAKING (FORM 3) [18-04-2019(online)].pdf | 2019-04-18 |
| 3 | 201937015586-Written submissions and relevant documents [12-03-2024(online)].pdf | 2024-03-12 |
| 3 | 201937015586-FORM 1 [18-04-2019(online)].pdf | 2019-04-18 |
| 4 | 201937015586-FIGURE OF ABSTRACT [18-04-2019(online)].pdf | 2019-04-18 |
| 4 | 201937015586-Correspondence to notify the Controller [23-02-2024(online)].pdf | 2024-02-23 |
| 5 | 201937015586-FORM-26 [19-01-2024(online)].pdf | 2024-01-19 |
| 5 | 201937015586-DRAWINGS [18-04-2019(online)].pdf | 2019-04-18 |
| 6 | 201937015586-US(14)-HearingNotice-(HearingDate-26-02-2024).pdf | 2024-01-09 |
| 6 | 201937015586-DECLARATION OF INVENTORSHIP (FORM 5) [18-04-2019(online)].pdf | 2019-04-18 |
| 7 | 201937015586-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [04-01-2024(online)].pdf | 2024-01-04 |
| 7 | 201937015586-COMPLETE SPECIFICATION [18-04-2019(online)].pdf | 2019-04-18 |
| 8 | 201937015586-US(14)-HearingNotice-(HearingDate-09-01-2024).pdf | 2023-12-18 |
| 8 | 201937015586-Information under section 8(2) (MANDATORY) [25-04-2019(online)].pdf | 2019-04-25 |
| 9 | 201937015586-FORM 18 [02-05-2019(online)].pdf | 2019-05-02 |
| 9 | 201937015586-FORM 3 [20-09-2023(online)].pdf | 2023-09-20 |
| 10 | 201937015586-FORM 3 [10-03-2023(online)].pdf | 2023-03-10 |
| 10 | 201937015586-Information under section 8(2) (MANDATORY) [09-05-2019(online)].pdf | 2019-05-09 |
| 11 | 201937015586-Information under section 8(2) (MANDATORY) [20-06-2019(online)].pdf | 2019-06-20 |
| 11 | 201937015586-Information under section 8(2) [10-03-2023(online)].pdf | 2023-03-10 |
| 12 | 201937015586-FORM-26 [02-07-2019(online)].pdf | 2019-07-02 |
| 12 | 201937015586-Information under section 8(2) [05-09-2022(online)].pdf | 2022-09-05 |
| 13 | 201937015586-Information under section 8(2) [11-03-2022(online)].pdf | 2022-03-11 |
| 13 | 201937015586-MARKED COPIES OF AMENDEMENTS [04-07-2019(online)].pdf | 2019-07-04 |
| 14 | 201937015586-FORM 13 [04-07-2019(online)].pdf | 2019-07-04 |
| 14 | 201937015586-Information under section 8(2) [17-01-2022(online)].pdf | 2022-01-17 |
| 15 | 201937015586-AMMENDED DOCUMENTS [04-07-2019(online)].pdf | 2019-07-04 |
| 15 | 201937015586-Information under section 8(2) [05-11-2021(online)].pdf | 2021-11-05 |
| 16 | 201937015586-FER.pdf | 2021-10-18 |
| 16 | 201937015586-Information under section 8(2) (MANDATORY) [14-09-2019(online)].pdf | 2019-09-14 |
| 17 | 201937015586-Information under section 8(2) [19-03-2020(online)].pdf | 2020-03-19 |
| 17 | 201937015586-CLAIMS [01-10-2021(online)].pdf | 2021-10-01 |
| 18 | 201937015586-FER_SER_REPLY [01-10-2021(online)].pdf | 2021-10-01 |
| 18 | 201937015586-Information under section 8(2) [24-06-2020(online)].pdf | 2020-06-24 |
| 19 | 201937015586-Information under section 8(2) [17-09-2020(online)].pdf | 2020-09-17 |
| 19 | 201937015586-OTHERS [01-10-2021(online)].pdf | 2021-10-01 |
| 20 | 201937015586-FORM 3 [23-09-2021(online)].pdf | 2021-09-23 |
| 20 | 201937015586-Information under section 8(2) [18-09-2020(online)].pdf | 2020-09-18 |
| 21 | 201937015586-Information under section 8(2) [02-11-2020(online)].pdf | 2020-11-02 |
| 21 | 201937015586-Information under section 8(2) [15-09-2021(online)].pdf | 2021-09-15 |
| 22 | 201937015586-Information under section 8(2) [08-01-2021(online)].pdf | 2021-01-08 |
| 22 | 201937015586-Information under section 8(2) [30-07-2021(online)].pdf | 2021-07-30 |
| 23 | 201937015586-FORM 4(ii) [29-06-2021(online)].pdf | 2021-06-29 |
| 23 | 201937015586-Verified English translation [09-04-2021(online)].pdf | 2021-04-09 |
| 24 | 201937015586-FORM 3 [09-04-2021(online)].pdf | 2021-04-09 |
| 25 | 201937015586-Verified English translation [09-04-2021(online)].pdf | 2021-04-09 |
| 25 | 201937015586-FORM 4(ii) [29-06-2021(online)].pdf | 2021-06-29 |
| 26 | 201937015586-Information under section 8(2) [08-01-2021(online)].pdf | 2021-01-08 |
| 26 | 201937015586-Information under section 8(2) [30-07-2021(online)].pdf | 2021-07-30 |
| 27 | 201937015586-Information under section 8(2) [02-11-2020(online)].pdf | 2020-11-02 |
| 27 | 201937015586-Information under section 8(2) [15-09-2021(online)].pdf | 2021-09-15 |
| 28 | 201937015586-FORM 3 [23-09-2021(online)].pdf | 2021-09-23 |
| 28 | 201937015586-Information under section 8(2) [18-09-2020(online)].pdf | 2020-09-18 |
| 29 | 201937015586-Information under section 8(2) [17-09-2020(online)].pdf | 2020-09-17 |
| 29 | 201937015586-OTHERS [01-10-2021(online)].pdf | 2021-10-01 |
| 30 | 201937015586-FER_SER_REPLY [01-10-2021(online)].pdf | 2021-10-01 |
| 30 | 201937015586-Information under section 8(2) [24-06-2020(online)].pdf | 2020-06-24 |
| 31 | 201937015586-CLAIMS [01-10-2021(online)].pdf | 2021-10-01 |
| 31 | 201937015586-Information under section 8(2) [19-03-2020(online)].pdf | 2020-03-19 |
| 32 | 201937015586-FER.pdf | 2021-10-18 |
| 32 | 201937015586-Information under section 8(2) (MANDATORY) [14-09-2019(online)].pdf | 2019-09-14 |
| 33 | 201937015586-AMMENDED DOCUMENTS [04-07-2019(online)].pdf | 2019-07-04 |
| 33 | 201937015586-Information under section 8(2) [05-11-2021(online)].pdf | 2021-11-05 |
| 34 | 201937015586-FORM 13 [04-07-2019(online)].pdf | 2019-07-04 |
| 34 | 201937015586-Information under section 8(2) [17-01-2022(online)].pdf | 2022-01-17 |
| 35 | 201937015586-Information under section 8(2) [11-03-2022(online)].pdf | 2022-03-11 |
| 35 | 201937015586-MARKED COPIES OF AMENDEMENTS [04-07-2019(online)].pdf | 2019-07-04 |
| 36 | 201937015586-Information under section 8(2) [05-09-2022(online)].pdf | 2022-09-05 |
| 36 | 201937015586-FORM-26 [02-07-2019(online)].pdf | 2019-07-02 |
| 37 | 201937015586-Information under section 8(2) (MANDATORY) [20-06-2019(online)].pdf | 2019-06-20 |
| 37 | 201937015586-Information under section 8(2) [10-03-2023(online)].pdf | 2023-03-10 |
| 38 | 201937015586-FORM 3 [10-03-2023(online)].pdf | 2023-03-10 |
| 38 | 201937015586-Information under section 8(2) (MANDATORY) [09-05-2019(online)].pdf | 2019-05-09 |
| 39 | 201937015586-FORM 18 [02-05-2019(online)].pdf | 2019-05-02 |
| 39 | 201937015586-FORM 3 [20-09-2023(online)].pdf | 2023-09-20 |
| 40 | 201937015586-Information under section 8(2) (MANDATORY) [25-04-2019(online)].pdf | 2019-04-25 |
| 40 | 201937015586-US(14)-HearingNotice-(HearingDate-09-01-2024).pdf | 2023-12-18 |
| 41 | 201937015586-COMPLETE SPECIFICATION [18-04-2019(online)].pdf | 2019-04-18 |
| 41 | 201937015586-REQUEST FOR ADJOURNMENT OF HEARING UNDER RULE 129A [04-01-2024(online)].pdf | 2024-01-04 |
| 42 | 201937015586-US(14)-HearingNotice-(HearingDate-26-02-2024).pdf | 2024-01-09 |
| 42 | 201937015586-DECLARATION OF INVENTORSHIP (FORM 5) [18-04-2019(online)].pdf | 2019-04-18 |
| 43 | 201937015586-FORM-26 [19-01-2024(online)].pdf | 2024-01-19 |
| 43 | 201937015586-DRAWINGS [18-04-2019(online)].pdf | 2019-04-18 |
| 44 | 201937015586-FIGURE OF ABSTRACT [18-04-2019(online)].pdf | 2019-04-18 |
| 44 | 201937015586-Correspondence to notify the Controller [23-02-2024(online)].pdf | 2024-02-23 |
| 45 | 201937015586-Written submissions and relevant documents [12-03-2024(online)].pdf | 2024-03-12 |
| 45 | 201937015586-FORM 1 [18-04-2019(online)].pdf | 2019-04-18 |
| 46 | 201937015586-STATEMENT OF UNDERTAKING (FORM 3) [18-04-2019(online)].pdf | 2019-04-18 |
| 46 | 201937015586-FORM 13 [12-03-2024(online)].pdf | 2024-03-12 |
| 47 | 201937015586-FORM 3 [18-03-2024(online)].pdf | 2024-03-18 |
| 47 | 201937015586.pdf | 2019-04-18 |
| 48 | 201937015586-PatentCertificate21-11-2025.pdf | 2025-11-21 |
| 49 | 201937015586-IntimationOfGrant21-11-2025.pdf | 2025-11-21 |
| 1 | 2020-12-2915-47-14E_31-12-2020.pdf |