Interleaving for the transmission of variable telegrams Subpacket number and successive decoding 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 interleaving for the transmission of messages with variable sub-packet number and successive decoding. DE100 201 1 082 098 B4 describes a method for battery-operated transmitters, in which the data packet is subdivided into transmission packets (or sub-data packets) which are smaller than the actual information that is to be transmitted (so-called telegram splitting) )). Telegrams are divided into several subpackets (or subdata packages). 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. Since several radio transmissions share a medium for transmission, it can happen at any time that one sub-packet (or sub-data packet) is disturbed by another transmission so that it can not be decoded at the receiver. To counteract this problem, a channel coding of the data to be transmitted is performed, for example by a convolutional encoder, which provides redundancy in the signal in order to correctly decode it even with corrupted parts, Often the performance of this channel coding depends on how many consecutive symbols are disturbed. Since an interferer frequently disturbs successive symbols, the symbols are interlaced after the channel coding in such a way that symbols in the transmitted telegram, in the channel-coded codeword, have the greatest possible distance from one another. However, the interlaced) of the symbols (also called interleaving) has the consequence that the information of the telegram can only be recovered as a whole, since the information is scattered over the entire telegram. This makes it impossible to analyze a length field that would allow one to receive a variable number of subpackets. If, for example, the length field is preceded alone, it is not part of the channel coding and a non-receipt of the subpacket with the length information results in the total loss of the dgramm. In DE 10 201 1 082 100 A1 a base station with a bidirectional data transmission to a node is described. The base station has means for receiving a data packet transmitted by the node at a node transmission frequency, the node transmission frequency being derived from a frequency generator of the node. Furthermore, the base station has a device for determining the node transmission frequency based on the received data packet and for determining a deviation of the frequency generator of the node based on a frequency deviation between the determined node transmission frequency and a nominal node transmission frequency assigned to the node. Furthermore, the base station comprises means for sending a data packet to the node with a base station transmission frequency, 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 Teiegram splitting method, wherein a sub-packet to be transmitted is either sent, buffered and later transmitted, or discarded, in response to an amount of electrical energy that can be distributed by the power supply device. In the publication [G. Kilian, H. Petkov, R. Psiuk, H. Ueske, J., J. Robert, and A. Heuberger, "Improved Coverage for Low-Power Telemetry Systems Using Teygram Splitting," in Proceedings of 2013 European Conference on Smart Objects, Systems and Technologies (SmartSysTech), 2013.] describes an improved range for low-energy telemetry systems using the Teiegram splitting method. In the publication [G. Kilian,. Breiling, H. H, Petkov, H. üeske, F, Beer, J., Robert, and A. Heuberger, "Increasing Transmission Reliability for Telemetry Systems Using Telegram Splitting," IEEE Transactions on Communications, vol. 83, no. 3, pp. 949-961 Mar, 2015,] describes improved transmission security for low power telemetry systems using the gram splitting method. In the publication [Sam Dolinar, Dariush Divsalar, and Fabrizio Pollara, "Turbo Code Performance as a Function of Code Block Size," 1998 IEEE International Symposium on Information Theory], the performance of Turbo Codes is described in terms of a block size. The object of the present invention is therefore to increase transmission reliability in the transmission of data of variable length, This object is solved by the independent claims. Advantageous developments can be found in the dependent claims. Embodiments provide a data transmitter configured to encode and nested kernel data onto a plurality of core sub-data packets, the data transmitter configured to encode extension data and nested among a plurality of extension sub-data packets, wherein at least a portion of the data contained in the core sub-data packets Core data is required to receive the extension data or extension data packets. Further embodiments provide a data receiver configured to receive core sub-data packets and extension sub-data packets, the core sub-data packets containing core data interleaved over the core sub-data packets, and wherein the expansion sub-data packets include extension data that is nested over the expansion sub-data packets, the data receiver being configured in order to decode at least part of the coded core data to obtain information regarding the enhancement data packets, and wherein the data receiver is adapted to receive the enhancement data packets using the information. According to the concept of the present invention, core sub-data packets and sub-sub data packets are used to transmit variable-length data, interleaved coded core data of the variable-length data to the core sub-data packets to increase the transmission security of the coded core data, and coded extension data of the variable-length data Extension sub-data packets and, optionally, interleaved onto the core sub-data packets to enhance the transmission security of the encoded extension data, the encoded core data containing information about the encoded extension data or extension sub-data packets. Further embodiments provide a method of transmitting core data and extension data. The method includes a step of encoding core data to obtain encoded core data. Further, the method includes a step of interleaving and dividing the coded core data into a plurality of core sub-data packets. Further, the method includes a step of encoding by extension data to encoded extendibility ' to obtain ungsdaten. Further, the method includes a step of interleaving and dividing the encoded extension data into a plurality of extension data packets. Furthermore, the method comprises a step of sending the core sub-data packets and extension data packets. Further embodiments provide a method for receiving core data and extension data. The method comprises a step of receiving core sub-data packets and extension sub-data packets, the core sub-data packets containing core data interleaved over the core sub-data packets, and wherein the expansion sub-data packets include extension data interleaved over the extension sub-data packets. Further, the method includes a step of decoding at least part of the coded core data to obtain information regarding the enhancement data packets, wherein the enhancement data packets are received using the information. Further embodiments provide a transmission method for the wireless transmission of data in a communication system (eg a sensor network or telemetry system). The data comprises core data and extension data, the core data being encoded and interleaved among a plurality of core sub-data packets, the extension data being encoded and interleaved among a plurality of extension sub-data packets, at least a portion of which are incorporated in the Core data packages containing core data for a Empfa ' extension data or extension data packets is required. In the following, preferred embodiments of the data transmitter will be described In embodiments, the data transmitter is configured to not split coded core data onto the extension sub-data packets. In other words, the extension sub-data packets do not contain encoded core data. In embodiments, the data transmitter can be designed to divide the coded core data onto the core sub-data packets in such a way that even if one or more of the core sub-data packets are lost, a receiver-side decoding of the core data based on the other core sub-data packets is possible. For example, the coded core data may be successively divided among the core sub-data packets so that the loss of one of the core sub-data packets will not result in the total loss of the decoding capability. For this purpose, for example, immediately successive symbols of the core data can be divided into immediately successive core sub-data packets. In embodiments of the can ' data transmitter be configured in such a way to divide the encoded core data to the Kernsubdatenpakete that a time interval of the encoded Kemdaten with respect to a constraint length of the code used for coding the core information (channel codes) increases (or even maximized). For example, the data transmitter can be designed to divide symbols of the coded core data into the core sub-data packets such that a time interval of the symbols with respect to an influence length of a code used for coding the core data (Kana code) is increased (or even maximized). The performance of the channel coding may depend on how many consecutive symbols are disturbed. Since a disturber frequently disturbs successive symbols, the symbols can be interleaved after the channel coding in such a way that they have the greatest possible distance from one another in the transmitted core sub-data packets. In embodiments, the data transmitter may be configured to, if one of the core data is insufficient to fill the core sub-data packets, nested the extension data (or a portion of the extension data) to the core sub-data packets to populate the core sub-data packets. In embodiments, the data transmitter may be configured to divide the extension data (or a portion of the extension data) into the core sub-data packets and extension sub-data packets such that a distance of the encoded extension data with respect to an influence length of a code used for coding the extension data when filling the core sub-data packets (Channel codes) is increased (or even maximized). For example, the data transmitter may be configured to divide symbols of the encoded extension data onto the core sub-data packets such that a time interval of the symbols relative to an influence length of a code (channel code) used for encoding the core data is increased (or even maximized). In embodiments, the data transmitter may be configured to divide the extension data into the core sub-data packets and expansion sub-data packets such that the core sub-data packets and extension sub-data packets are equally filled when the core sub-data packets are filled. In embodiments, the data transmitter may be configured to divide the extension data into the core sub-data packets and expansion sub-data packets such that the core sub-data packets and extension sub-data packets are unequally populated when filling the core sub-data packets. In embodiments, the data transmitter may be configured to split the coded core data into a fixed or predetermined number of core sub-data packets. In embodiments, the data transmitter may be configured to adjust a number of expansion sub-data packets depending on a length of the extension data. In embodiments, the data transmitter may be configured to co-encode the core data and the extension data. In this case, the core data and the extension data can be coded together in such a way that a decoding of the coded core data supplies at least part of the core data. For example, with some channel codes, performance may be increased as the input length of the data increases, so the core data and extension data may be coded together. It should be noted, however, that the core data and the extension data are coded together so that e encoding of the core data or at least a portion of the core data is possible even without the extension data. In embodiments, the data transmitter may be configured to independently code the core data and the extension data. In embodiments, the data transmitter may be configured to fill the uncoded core data with enhancement data so that the enhancement data is timed ahead of the core data and security in decoding the core data is increased. In embodiments, the data transmitter may be configured to provide at least a portion of the core sub-data packets with synchronization data. In this case, the data transmitter can be designed to arrange the core data temporally adjacent to the synchronization data in the respective core sub-data packets. Furthermore, the data transmitter can be designed to arrange the core data alternately before and after the synchronization data in temporally (immediately) successive core sub-data packets. Furthermore, the data transmitter can be designed to arrange the synchronization data in the respective core sub-data packets in such a way that they are arranged immediately adjacent to the extension data and immediately adjacent to the core data. In embodiments, the data transmitter may be configured to transmit pure synchronization sub-packets. In this case, the data transmitter can be designed to transmit the core sub-data packets and the synchronization sub-data packets in such a way that the core sub-data packets and the synchronization sub-data packets are arranged adjacent to one another in terms of time. For example, the synchronization sub-packets may be sent out between the core sub-packets. In the following, preferred embodiments of the data receiver will be described In embodiments, the data receiver may know the number of core sub-data packets. In embodiments, the information regarding the extension data packets contained in the core sub-data packets may be a number of extension sub-data packets. In embodiments, the coded core data may be distributed to the core sub-data packets such that even if one or more of the core sub-data packets are lost, receiver-side decoding of the core data based on the other core sub-data packets is possible. The data receiver may be configured to receive and decode at least a portion of the core sub-data packets to obtain the core data. For example, the coded core data may be successively divided among the core sub-data packets so that the loss of one of the core sub-data packets will not result in the total loss of the decoding capability. For this purpose, for example, immediately successive symbols of the core data can be divided into immediately successive core sub-data packets. In embodiments, at least a portion of the core sub-data packets may be provided with synchronization data, wherein the data receiver may be configured to detect the core sub-data packets based on at least a portion of the synchronization data in a receive data stream. In embodiments, the data receiver may be configured to receive pure synchronization sub-packets and to detect the core sub-data packets based on at least a portion of the synchronization sub-packets in a receive data stream. In embodiments, the data receiver may be configured to recode at least a portion of the decoded core data. to obtain reencoded core data and to decode at least part of the encoded extension data using the core reencoded data. In embodiments, the data receiver may be configured to decode and reencode a first portion of the encoded enhancement data to obtain a first portion of reencoded enhancement data and to decode a second portion of the coded enhancement data using the first portion of reencoded enhancement data. Embodiments of the present invention will be explained with reference to the accompanying 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 schematic view of a channel coding and symbol assignment of Dates; Fig. 3 is a diagram showing a division of the core data and extension data in Core sub-data packets and extension sub-data packets; Fig. 4 is a diagram of a division of the nuclear symbols and Extension symbols in core sub-data packets and extension sub-data packets; Fig. 5 is a diagram of a division of the nuclear symbols and Extension symbols in core sub-data packets and extension sub-data packets after a first padding intermediate result; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and extension sub-data packets after a second filling intermediate result; in a diagram e division of the core symbols Extension symbols Core sub-data packages Extension sub-packets after one Filling intermediate result; Fig. 8 is a diagram of a division of the nuclear symbols and Extension symbols in core sub-data packages and Extension sub-packets after a fourth Filling intermediate result; 9 is a schematic view of a cyclic shift of the overall word after the channel coding, so that symbols of the extension word are arranged in front of the core word; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and Extension sub-data packets, synchronization symbols being preceded in the sub-data packets by the respective core symbols or extension symbols; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and Extension sub-data packets, wherein synchronization symbols are present in the middle of the respective sub-data packets between the respective core symbols or extension symbols; in a diagram a division of the core symbols and Extension symbols in core sub-data packages and Expansion sub-data packets, wherein synchronization sub-packets with synchronization symbols are arranged between the core sub-data packets; Fig. 13 is a diagram showing a division of the core symbols and Extension symbols in core sub-data packages and Extension sub-data packets, wherein there are two spaced apart (sub) synchronization symbol sequences in the respective sub-data packets; in a diagram a division of the core symbols and Extension symbols in core sub-data packages and Extension sub-data packets, wherein in the respective sub-data packets there are two spaced differently long (partial) sync symbol sequences; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and Expansion sub-data packets, with sub-synchronization (synchronization) sequences in the respective sub-data packets; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and Expansion sub-data packets, with sub-synchronization (synchronization) sequences in the respective sub-data packets; in a diagram, a division of the core symbols and extension symbols into core sub-data packets and Expansion sub-data packets, with sub-synchronization (symbol) sequences arranged in the respective sub-data packets; shows a diagram of a division of the core symbols into core sub-data packets, wherein in the respective core sub-data packets in the middle arranged (partial) synchronization symbol sequences are present: in a diagram, a division of the core symbols into core sub-data packets, wherein in the respective core sub-data packets in the middle arranged (partial) Synchronisatlonssymbolsequenzen are present, the core symbols are divided in successive Kernsubdaten packets alternately before and after the (sub-) synchronization symbol sequences; a flowchart of a method for transmitting core data and extension data 21 is a flowchart of a method for receiving core data and Extension data, 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. 1 shows a schematic block diagram of a system having a data transmitter 100 for transmitting data 120 and a data receiver 110 for receiving data 120, according to an embodiment of the present invention. The data 120 may include core data and extension data. The data transmitter 100 is configured to encode and interleave the core data to a plurality of core sub-packets 140_1 to 140_n, and to encode and interleave the extension data to a plurality of extension sub-packets 142_1 to 142_m, wherein at least a portion of the data in the sub-packet data 140_1 up to 140_n contained core data for receiving the expansion data packets is required. The data receiver 110 is configured to receive the core sub-data packets 140_1 to 140_n and the extension sub-data packets 142_1 to 142_m, the core sub-data packets 140_1 to 140_n containing the core data interleaved over the core sub-data packets 140_1 to 140_n, and the extension sub-data packets 142_1 to 142_m include expansion data that is nested over the extension sub-packets 142_1 through 142_m. The data receiver 110 is further configured to decode at least a portion of the coded core data to obtain information regarding the enhancement data packets 142_1 to 42__m, and wherein the data receiver 110 is adapted to use the enhancement data packets 142_1 to 142_m using the information receive. In embodiments, the core data may be divided into n core sub-data packets 140_1 through 140_n, where n is a natural number greater than or equal to two. n> 2. The extension data can be divided into sub-sub-packets 142_1 to 142_m. The data 120 can thus be transmitted using s = n + m sub-data packets (core sub-data packets + extension sub-data packets), the Minimum number (= number n of core sub-packets 140_1 b to be transmitted Subdata packages is. In embodiments, the extension data may be nested between both the core sub-data packets 14Q_1 to 140_n and the extension sub-data packets 142_1 to 1 2_m. The core sub-data packets 140_1 to 1: may thus contain both core data and a portion of the extension data. In embodiments, the core data is not divided among the extension sub-data packets 142_1 through 142_m. The extension sub-data packets 142_1 to 142_m thus contain no core data. In embodiments, the sub-data packets (core sub-data packets + extension sub-data packets) may be transmitted at a time interval, so that transmission pauses exist between the sub-data packets. In embodiments, the sub-data packets (core sub-data packets and / or expansion sub-data packets) may be transmitted using a time-hopping pattern and / or frequency hopping pattern. In embodiments, the frequency hopping pattern may indicate a sequence of transmission frequencies or transmission frequency jumps with which to transmit the sub-data packets. For example, a first sub-data packet having a first transmission frequency (or in a first frequency channel) and a second sub-data packet 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 hopping) between the first transmission frequency and the second transmission frequency. Of course, the frequency hopping pattern may also indicate only the frequency separation (transmission frequency hopping) 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 with which the sub-data packets are to be transmitted. For example, a first sub-data packet can be sent at a first transmission time (or in a first transmission time slot) and a second sub-data packet at a second transmission time (or in a second transmission time slot), 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 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 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 are transmitted, with transmission frequencies (or transmission frequency jumps) being associated with the transmission times (or transmission time intervals). In embodiments, the core sub-data packets 140_1 through 140_n and the extension sub-data packets 142_J through 142_m may be transmitted with separate time-hopping patterns and / or frequency-hopping patterns. In embodiments, the data transmitter 100 may include a transmitter (transmitter) 102 configured to transmit the data 120. 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 16 which is adapted to receive the data 120. The receiving means may be connected to an antenna 14 of the data receiver. Furthermore, the Data receiver 1 10 a transmitter (transmitter) 1 12, which is adapted to transmit data. The transmitting device 1 12 may be connected to the antenna 1 14 or another (separate) antenna of the data receiver 1 10. The data receiver may also have 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 110 is a sensor node. Further, it is possible that both the data transmitter 00 and the data receiver 1 are serial nodes. Furthermore, it is possible for both the data transmitter 100 and the data receiver 1 to be isisstations. In embodiments, the data to be sent can be divided into two parts, the so-called core information, which can be processed even before receipt of the entire package and the extension information. If the information is channel coded and assigned (or mapped), they yield the core word, respectively the extension word, as shown in FIG. 2 shows a schematic view of channel coding and symbol assignment of data. As can be seen in FIG. 2, the data 120 may include core information (core data) 122 and extension information (extension data) 124. The channel coding and symbol mapping of the core information 122 may yield a kernel 130 with the symbols k0 through kK (kernel symbols 136). The kana coding and symbol mapping of extension information 124 may yield an extension word 132 with symbols eO to eE (extension symbols 138). The core word 130 and the extension word 132 may form a total word 134. In other words, FIG. 2 shows the formation of the total word 134 from core information 122 and extension information 124. The targeted nesting of the core words 130 as described herein is particularly important when disturbances occur in the channel. In this case, it is advantageous if the overall data packet to be transmitted is subdivided into smaller subpackets, so-called subpackets (see DE 10 201 1 082 098 B4). If the time interval between subpackets is long enough in comparison to the interferers occurring in the channel, then the probability is high that only a single subpacket will be disturbed. If the data is now properly nested, the loss of information in a subpacket does not result in the loss of information. To achieve this, channel coding can be applied to the information before it is divided into subpackets. After the channel coding, the symbols can be switched to the broadcasting alphabet of the Be mapped (or assigned). The resulting words are referred to as the core word or extension word. These words then form a total word 134, which is then subdivided into sub-packages. The core word can now be nested in the transmission word so that it can be evaluated as early as possible at the receiver, as shown in FIG. 3, 3 shows in a diagram a division of the core data 122 and extension data 124 into core sub-data packets 140_1 to 140_4 and extension sub-data packets 142_1 to 142_5. In this case, the abscissa describes a temporal arrangement of the sub-data packets (core sub-data packets 140_1 to 140_4 + extension sub-data packets 142_1 to 142_5) the ordinate describes a temporal arrangement of the symbols (core symbols + extension symbols) in the respective sub-data packets. As can be seen in FIG. 3, the core word 130 may be divided into the core data packets 140_1 to 140_4, in detail the symbols 136 of the core word 130 may be nested among the core sub-data packets 140_1 to 140_4. Likewise, the extension word 132 may be divided into the extension sub-packets 142_1 to 142_5. In detail, the symbols 138 of the extension word 132 may be interleaved among the extension sub-data packets 42_1 to 142_5. As further seen in FIG. 3, extension word 132 (or extension symbols 138 in detail) may be distributed to both core data packets 140_1 to 140_4 and extension sub-data packets 142_1 to. This is especially possible if the Kernsubdatenpak ' ete140_1 to 140_4 by the core word 130 (or in detail the core symbols 136) are not completely filled. In this case, the extension word 132 may be divided into both the core data packets 140_1 to 140_4 and the extension sub-data packets 142_1 to 142_5. In other words, FIG. 3 shows that core subpackets 140_1 to 140_4 contain kernel symbols 136, extension subpackets 142_1 to 142_5 do not contain kernel symbols 136. The subpackets can therefore be divided into two different categories. First. Core subpackets 140_1 to 140_4. These are subpackets 140_1 to 140_4. contain ribole 138 of the core word 130. Second, expansion sub-packets 142_1 to 142_5. These are subpackets 142_1 to 142_5 that do not contain symbols of the core word 130. A Traditional transmission (ie without subpackets) can be achieved if the subpackets are transmitted without time delay. In the following, detailed exemplary embodiments of the transmission method presented above, which can be carried out by the data transmitter 100 and the data receiver 110, will be explained in more detail. First Detailed Embodiment: Interleaving the Core Data on Kernel Subpackets The core word 132, which may contain, for example, important side information for reception, can hereby be completely nested into the so-called core sub-data packets 140_1 to 140_n, which can be evaluated by the receiver 1 10 before the completed submission of the extension sub-packets 142_1 to 142_1 to 142_m. The Number n of the core sub-packets 140_1 to 40_n must be known to the receiver 110. In this case, it is important that the loss of one or more of the core subpackets 140_1 to 140_n can also be compensated, for example by a fault. For this, the symbols of the core data 122 may be evenly distributed across the kernel subpacket, as the loss of a larger contiguous block in the data for many channel coding techniques results in rapid failure. The simplest procedure for this is to interleave the symbols one after the other into the subpackets of the core sequence (core sub-data packets 140_1 to 140_n). If the number n of the core sub-packets 140_1 to 10_n has been reached, the allocation starts again from the beginning. The number of subpackets in the core sequence is identical and given for all telegrams of variable length, ie fixed. Fig. 4 is a diagram showing a division of the core symbols k0 to k15 and extension symbols e0 to e19 into core sub-data packets 140_1 to 140_4 and er submission data packets to 142_5. The abscissa describes a temporal Arrangement of the sub-data packets (core sub-data packets 140_1 to + extension sub-data packets 142_1 to 142_5), while the ordinate describes a temporal arrangement of the symbols (core symbols + extension symbols) in the respective sub-data packets. As can be seen in FIG. 4, the kernel symbols k0 to k5 can be split successively into the kernel data packets 140_1 to 140_4, while the extension symbols eO b,>, Γ mf, the extension sub-data packets 142_1 to 142_m are successively nested. In detail, first the For example, the first kernel sub-packet 140_1 may be the kernel symbols k0, k4, k8 and ki2, the second one. The first kernel sub-packet 140_1 may be the kernel symbols k0, k4, k8 and ki2 Core sub-packet 140_2 the kernel symbols k1, k5, k9, k13, the third kernel sub-packet 140_3 the kernel symbols k2, k6, k10 and k14, and the third kernel data packet 40_4 containing the kernel symbols k3, k7, k1 and k15, In other words, FIG. 4 shows an exemplary division of the core and extension symbols with core subpackets, extension subpackets 142_1 to 142_m with a symbol number per subpacket of Ns = 4. In the example shown in FIG. 4, for example, N K = 16 core symbols k 0 to k 15 are nested on n = S min = 4 core sub-data packets 140_ 1 to 140_ 4. For example, the symbols can be nested as follows: 0. Symbol in 0. Kernsubpack 1. Symbol in 1. Kernsubpaket 3. Symbol in 3. Kernsubpaket 4. Symbol in 0. Kernsubpackage 5. Symbol in 1, Kernsubpaket 15. Symbol in 4. Kernsubpack This is just an example, in principle it can be interleaved in any way, but some ways of interleaving will result in worse performance if subpackages are lost. In embodiments, the information may be interleaved into subpackets so that the core word can be separated and received before the extension word. In embodiments, the symbols within the kernel extension sub-packets may be interleaved such that the loss of one or more core sequence sub-packets does not result in the total loss of the decode capability. Second detailed Ausführungsbeispiej filling the Kemsub akete with Expansion poles for vara Usually, the number of symbols that can be sent in the core sub-packets 140_1 to 140_n is greater than the number of symbols in the core word 130, so that the core sub-packets 140_1 to 140_n can be padded with symbols from the extension word 132. For this to happen as evenly as possible, the ratio of core symbols in Kernsubpaket () and expansion symbols in Kernsubpaket {N can s - N K ) prior to be set nest. This ratio V = - , can be a N $ -N K integer divisor of the number of core sub-packets {S min ), and the number of core symbols in a sub-packet can be greater than or equal to the number of extension symbols in a sub-packet, ie ~> 1. If the core word 130 and the extension word 132 are now divided into the telegram, the kernel word is split into the first free data symbols of the kernel subpackets. The first symbols of the extension word 132 are then written to the kernel subpackets 140_1 to 140_n distributed. This mapping can happen evenly so that two of these symbols are not placed in the same subpacket. There are various possibilities for this, First, the symbols can be placed at a distance V in the kernel subpackets. On the first pass, this process starts at subpacket 0 and advances in V steps. Thus, the second symbol can be placed in subpacket V, etc. Second, the symbols can be placed in V blocks in the core subpackets. The ^ ψ symbols occupy ^ - successive core subpackets, if the kernel subpack index S min exceeds , then kernsubpaket 0 is started again. The next S - S min extension symbols can then be distributed to the subpackets of the extension sequence, without additional spacing. Start with Subpackage S min and end with Subpackage S. If S - S min + ^ 2 expansion symbols have been distributed, you start by placing the next ^ 1 extension symbols in Subpackage 1 and proceed again in V steps. So the next symbol will be placed in subpackage V + 1 etc, until the ^ 11 Symbols are placed. The placement of the extension icons within the extension sequence remains the same as in the first step. If an extension symbol has been assigned to each subpacket of the core sequence, the next round of allocations begins again at subpackage 0 (140_1) and the method is continued until the end of the extension symbols, 5 shows a diagram of a division of the core symbols k0 to k15 and extension symbols e0 to e39 into core sub-data packets 140_1 to 140_4 and extension sub-data packets 142_1 to 142_3 after a first one Filling intermediate result. In this case, the abscissa describes a temporal arrangement of the sub-data packets (core sub-packets 140_1 to 140_4 + extension sub-data packets 142_1 to 142_3), while the ordinate describes a temporal arrangement of the symbols (core symbols + extension symbols) in the respective sub-data packets. As can be seen in FIG. 5, firstly the kernel symbols k0 to kl5 can be nested to the kernel subpackets 140_1 to 140_4, so that the loss of one or more of the kernel subpackets 140_1 to 140_3 does not lead to the total loss of the decoding capability, in detail, ' For example, the first core sub-packet 140_1 may include the core symbols k0, k4, k8 and kl2, the second core sub-packet 140_2, the kernel symbols k1, k5, k9, k13, the third kernel sub-packet 140_3, the kernel symbols k2, k6, ki0 and k14, and the third core data packet 140_4 the core symbols k3, k7. k1 contains 1 and k15. Subsequently, the extension symbols e0 to e39 can be distributed to both the core sub-data packets 140_1 to 140_4 and the extension sub-data packets, so that the core sub-data packets 140_1 to 140_4 and the extension sub-packets 142_1 to 142_3 are filled up evenly, and so that the loss of one of the sub-data packets does not Total loss of the decoding possibility leads. The goal is that the first kernel data packet 140_1 the extension symbols and e30, the second core sub-packet 140_2, the extension symbols e5, e15. e25 and e35, the third core sub-packet 140_3 the extension symbols H,; I! e21 and e31, the fourth core sub-packet 140_4 the extension symbols e6, e16. e26 and e36, the first extension sub-packet 142_1 the extension icons e2, 22, e27. e32, and e37, the second extension sub-packet includes extension symbols e3, e23, e28, e33 and e38, and the third extension sub-packet 142_3 the extension symbols e4. e9, e14, e19, e24, e29. e34 and e39 included. For this purpose, first the extension symbol eO can be applied to the first core sub-packet 140_1, the extension symbol e1 to the third core sub-packet 140_3, the extension symbol e2 to the first extension sub-packet 142_1, the extension symbol e3 to the second extension sub-packet and the Extension symbol e3 to the third extension sub-packet 142_3. In other words, Fig. 5 shows placing the expansion symbols e0 and ei with Distance V = 2 in the core sub-cells starting at core sub-packet 0, symbols e2, e3 and e4 are interleaved into the extension sub-packets. Fig. 6 is a diagram showing a division of the core symbols k0 to k15 and extension symbols e0 to e39 into core sub-data packets 140_1 to 140_4 and extension sub-data packets 142_1 to 142_3 after a second intermediate threading result. In this case, the abscissa describes a temporal arrangement of the sub-data packets (core sub-packets 140_1 to 140_4 + extension sub-data packets 142_1 to 142_3), while the ordinate describes a temporal arrangement of the symbols (core symbols + extension symbols) in the respective sub-data packets. As can be seen in FIG. 8, the extension symbol e5 can now be applied to the second core sub-packet 140_2, the extension symbol e6 to the fourth core sub-packet 140_4, the extension symbol e7 to the first extension sub-packet 142_1, the extension symbol e8 to the second extension sub-packet 142_2, and the Extension symbol e9 to the third extension sub-packet 142_3. In other words, Fig. 6 shows placement of the extension symbols e5 and e6 at a distance V = 2 in the core sub-cells starting at the core sub-packet 1, symbols e7. e8 and e9 are nested in the extension subpackets, 7 shows a diagram of a division of the core symbols k0 to k15 and extension symbols e0 to e39 into core sub-data packets 140_1 to 140_4 and extension sub-data packets 142_1 to 1 to a third one Auffüilungszwischenergebnis. In this case, the abscissa describes a temporal arrangement of the sub-data packets (core sub-packets 140_1 to 140_4 + extension sub-data packets 142_1 to 142_3), while the ordinate describes a temporal arrangement of the symbols (core symbols + extension symbols) in the respective sub-data packets. As can be seen in Fig. 7. Now the Erweitungssymboi mf the first Kernsubdata package 140_1, the extension symbol e1 1 on the third Kernsubdatenpaket as extension symbol Ί 4θ_ the π " coded enhancement data (132) in such a way on the Kernsubdatenpakete (140_1: 1 0_n) and extension sub-packets Core sub-data packets (140_1: 140_n) and extension sub-data packets are padded with data. The data transmitter (100) of any one of claims 4 to 5, wherein the data transmitter (100) is adapted to, upon padding the core sub-data packets (140_1: 40_n), encode the encoded extension data (124) to the core sub-data packets (140_1: 140_n) and extension sub-data packets (140). 142_1: 142_m), that the core sub-data packets (140_1: 140_n) and extension sub-data packets (142_1: 142_m) are padded unevenly. The data transmitter (100) of any one of claims 1 to 7, wherein the data transmitter (00) is adapted to split the coded core data (130) to a fixed or predetermined number of core sub-data packets (140_1: 140_n). The data transmitter (100) of any one of claims 1 to 8, wherein the data transmitter (00) is adapted to adjust a number of expansion sub-data packets (142_1: 142_m) in dependence on a length of the extension data. The data transmitter (100) of any one of claims 1 to 9, wherein the data transmitter (100) is adapted to code the core data (122) and the extension data (124) together. The data transmitter (100) of claim 10, wherein the core data (122) and the enhancement data (124) are coded together such that decoding the coded core data (130) provides at least a portion of the core data. The data transmitter (100) of any one of claims 1 to 9, wherein the data transmitter (100) is adapted to independently code the core data (122) and the extension data (124). The data transmitter (100) of any one of claims 1 to 12, wherein the data transmitter (100) is adapted to fill the uncoded core data (122) with enhancement data (124) such that the enhancement data is timed ahead of the core data and the security is increased in the decoding of the core data, The data transmitter (100) of any one of claims 1 to 13, wherein the data transmitter is configured to further split the encoded extension data (132) into at least a portion of the core sub-data packets (140_1: 140__n) such that in the respective subpacket data packets (140_1: 1 0_n ) a part of the coded extension data is arranged in time before the coded core data (130), so that a security in the decoding of the coded core data (130) is increased, The data transmitter (100) of any one of claims 1 to 14, wherein the data transmitter (100) is adapted to provide at least a portion of the core sub-data packets (140_1: 140_n) with synchronization data (150). The data transmitter (100) of claim 15, wherein the data transmitter (100) is adapted to place the encoded core data (130) in the respective subpacket packets (140_1: 140_n) temporally adjacent to the synchronization data (150). Data transmitter (00) according to claim 5, wherein the data transmitter (00) is designed to arrange the core data (130) alternately before and after the synchronization data (150) in chronologically successive Kemsubdatenpaketen (140_1: 140_n). Data transmission ι ' > Π) according to any one of claims 15 to 17, wherein the data transmitter (100) is adapted to arrange in the respective Kemsubdatenpaketen (140_1: 140_n) the synchronization data (150) in time so that these immediately adjacent to the encoded extension data (132) and immediately adjacent to the coded core data (130). The data transmitter (100) of any one of claims 1 to 18, wherein the data transmitter (100) is further adapted to transmit pure synchronization sub-packets (152_1, 152_2). The data transmitter (100) of claim 19, wherein the data transmitter (100) is adapted to transmit the core sub-data packets (140_1: 140_n) and the synchronization sub-packets (152_1, 152_2) such that the core sub-data packets (1 0_1: 1 Q_n) and the synchronization sub-packets are adjacent are arranged to each other. A data receiver (110) adapted to receive core sub-data packets (140_1: 140_n) and expansion sub-data packets (142_1: 142_m), the core sub-data packets containing J-core data (130) transmitted via the Core sub-data packets (140_1: 140_n) are interleaved distributed, and wherein the enhancement sub-data packets (142_1: 142_m) contain coded enhancement data (132) interleaved over the enhancement sub-data packets (142_1: 142_m): wherein the data receiver (110) is adapted to decode at least a portion of the encoded core data (130) to obtain information regarding the encoded enhancement data (132) or enhancement sub-data packets (42_1: 42_m); wherein the data receiver (110) is adapted to receive the extension data packets (142_1: 142_m) using the information. Data receiver (1 10) according to claim 21, wherein the data receiver (1 10) a number of core sub-data packets (40_1: 1 0_n) is known. The data receiver (1 10) of any one of claims 21 to 22, wherein the information regarding the extension sub-data packets comprises a number of the sub-extension data packets (142_1: 142_m). Data receiver (1 10) according to any one of claims 21 to 23 wherein the coded core data (130) to the core sub-data packets (140_1: 140_n) are divided such that even with loss of transmission of one or more of the core sub-data packets (140_1: 140_n) a receiver-side decoding of the encoded core data (130) based on the other core sub-data packets (140_1: 140_n) is possible; wherein the data receiver (110) is adapted to receive and decode at least a portion of the core sub-data packets (140_1: 140_n) to obtain the core data (122). Data receiver (1 10) according to one of claims 21 to 24, wherein at least a portion of the core sub-data packets: synchronization data (150) is provided; wherein the data receiver (110) is adapted to detect the core sub-data packets (140_1; 140_n) based on at least a portion of the synchronization data (150) in a receive data stream. The data receiver (1 10) of any one of claims 21 to 25, wherein the data receiver (110) is adapted to receive pure synchronization sub-packets (152_1, 152_2) and the core sub-data packets (140_1: 140_n) based on at least a portion of the synchronization sub-packets (152_1, 152_2) in a receive data stream. A data receiver (10) according to any of claims 21 to 26, wherein the data receiver (110) is adapted to reencode at least a portion of the decoded core data to obtain reencoded core data; wherein the data receiver (10) is adapted to decode at least a portion of the encoded extension data using the reencoded core data. The data receiver (1 10) of any one of claims 21 to 27, wherein the data receiver (110) is adapted to decode and reencode a first portion of the encoded extension data to obtain a first portion of encoded extension data; wherein the data receiver (110) is adapted to decode a second portion of the encoded extension data using the first portion of reencoded extension data. System, with the following features a data transmitter (100) according to any one of claims 1 to 20; and a data receiver zh any one of claims 21 to 28. 30. Method (200), with the following steps Encoding (202) core data to obtain coded core data; Interleaving (204) and dividing the coded core data into a plurality of core sub-data packets; Encoding (206) extension data to obtain encoded extension data: Interleaving (208) and dividing the encoded extension data into a plurality of extension data packets; Transmitting (210) the core sub-data packets and extension data packets. 31. Method (220), comprising the following steps: Receiving (222) core sub-data packets and extension sub-data packets, the core sub-data packets containing core data passing over the Core sub-data packets are nested, and wherein the Expansion sub-data packets containing extension data nested over the extension sub-data packets; Decoding (224) at least a portion of the encoded core data to be a To obtain information regarding the extension data packets; wherein the extension data packets are received using the information. 32. Computer program for carrying out the method according to claim 30 or 31, A data transmitter (100) adapted to encode fixed-length data and to nestedly divide it into at least a subset of a plurality of sub-data packets, the data transmitter (100) being further adapted. to encode variable-length data and nested to divide at least a subset of the plurality of sub-data packets so that at least one of the plurality of sub-data packets comprises a portion of the fixed-length data and a portion of the variable-length data.