Systems, devices and methods for transmitting and receiving preambles, data and messages
By sending URLLC preamble on the client device after sending a negative confirmation in 5G cellular communication and causing the base station to retransmit URLLC data, the problem of difficulty in achieving high reliability and low latency in the prior art is solved, and the problem of high reliability and low latency is met. The high requirements of industrial applications improve the reliability and latency performance of URLLC data.
Patent Information
- Application Number
- CN201980062288.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Priority Date
- 2018-07-24
- Filing Date
- 2019-07-23
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2039-07-23
AI Technical Summary
The existing 5G cellular communication technology is difficult to achieve high reliability and low latency at the same time, especially in industrial applications, especially when the terminal is not provided with dedicated wireless resources for uplink transmission, and it cannot meet certain industrial applications. high requirements.
High reliability and low latency are achieved by causing the client device to send the URLLC preamble before sending the URLLC data when the receiver sends a negative acknowledgement (NACK) and causing another device (such as a base station) to retransmit the URLLC data, achieving high reliability and low latency . The method includes monitoring the preamble and message using a processor, determining whether the data is received successfully, and retransmitting the data if necessary, utilizing D2D communication and other communication methods on shared resources.
It realizes meeting the latency and reliability requirements in high-demand applications, reduces the latency of URLLC data, and improves the reliability of URLLC packet transmission, while avoiding the increase in delay.
Smart Images

Figure CN112753181B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a system for reliable communications.
[0002] The invention further relates to a method for reliable communication.
[0003] The invention also relates to a computer program product enabling a computer system to perform such a method. Background Art
[0004] 5G cellular communication technology aims to support industrial applications among many other vertical industries. One of the key requirements for industrial applications is to provide ultra-reliable low-latency communication (URLLC) between different sensors and actuators in the factory. However, high reliability and low latency are usually difficult to achieve simultaneously. High reliability is usually achieved by introducing redundancy in the spatial domain (e.g., antenna diversity or multiple radio links), time domain (e.g., repetition or retransmission), and code domain (e.g., source / channel coding), which brings additional latency and overhead to the wireless communication system. Low latency can be achieved by sending data as long as it is available. However, wireless systems usually use shared radio resources, so communication reliability cannot be guaranteed due to conflicts and / or interference.
[0005] “Achieving Ultra-Reliable Low Latency Communications: Challenges and Envisioned System Enhancements”, G. Pocovi et al., IEEE Network, March / April 2018, discloses the latest 3GPP improvements for low latency in 5G (NR) Release 15. These improvements include using slots shorter than 1ms (e.g., 0.125ms mini-slots), reducing HARQ round trip time for retransmissions, and preemptive resource allocation when multiplexing eMBB and URLLC data. These improvements address user plane data transmission when the UE is in connected mode and communicating with the gNB.
[0006] However, when dedicated wireless resources for uplink transmission are not provided to the terminal, the use of the above improvements cannot achieve low latency and high reliability for the high requirements of certain industrial applications. Summary of the invention
[0007] A first object of the present invention is to provide a system for receiving preambles, data and messages which can be used to provide ultra-reliable low-latency communications for demanding applications.
[0008] A second object of the present invention is to provide a device for transmitting a preamble and data, which can be used to provide ultra-reliable low-latency communications for demanding applications.
[0009] A third object of the present invention is to provide a method for receiving preambles, data and messages, which can be used to provide ultra-reliable low-latency communications for demanding applications.
[0010] A fourth object of the present invention is to provide a method for sending a preamble and data, which can be used to provide ultra-reliable low-latency communications for high-demand applications.
[0011] According to the present invention, the first purpose is achieved in that the system for receiving a preamble code includes: at least one receiver; at least one transmitter; and at least one processor, and the at least one processor is configured to: use the at least one receiver to monitor the sending of a preamble code from a sending device to a receiving party; when the preamble code is received within a first time interval, use the at least one receiver to receive data within a second time interval, and the second time interval is after the first time interval; use the at least one receiver to monitor the sending of a message by the receiving party, and the message indicates that the data sent within the second time interval was not successfully received by the receiving party; and when the message is received within a third time interval, use the at least one transmitter to retransmit the data within a fourth time interval.
[0012] Typically, if the system has successfully received the data itself, the system will only retransmit the data. One or more other time intervals may exist between the second time interval and the third time interval and / or between the third time interval and the fourth time interval. The system may include multiple devices or a single device. The system may be, for example, a base station or a mobile device. The message may be, for example, a negative acknowledgment. The message may be unicast by the receiver to the sending device and may be heard by the system when retransmitting the data, but preferably, the message is broadcast by the receiver. The receiver may be configured to send messages only about URLLC data. For example, the receiver may be configured to determine whether the data that is not (correctly) received is URLLC data based on whether the data is sent before the preamble is sent or based on an indicator included in the data.
[0013] The inventors have recognized that device-to-device (D2D) communication has the potential to address the low latency and high reliability requirements of certain applications (e.g., industrial applications). Low latency is achieved because the D2D approach allows a group of client devices (UEs) to communicate directly with each other without always going through a base station (e.g., eNB or gNB).
[0014] The latest D2D communication technology currently standardized by 3GPP is not designed to support industrial applications that require URLLC between UEs. Therefore, the inventors have proposed improvements to the currently standardized D2D communication technology. Typical time domain packet retransmissions (such as ARQ and HARQ) increase latency, thereby no longer meeting the latency requirements of high-demand applications. However, by causing the client device to send a URLLC preamble just before sending its URLLC data when the recipient sends a negative acknowledgment (NACK), and causing another device (e.g., another client device and / or base station) to retransmit the URLLC data, both the reliability requirements and latency requirements of high-demand applications can be met. The other device is typically a device that is positioned so that it can establish a communication link with the sending device and the recipient of the URLLC data. In addition to D2D communication, the present invention can also be used for other communications on shared resources.
[0015] The preamble may indicate that the data sent in the second time interval needs to be reliably received by the recipient of the data. For example, the preamble may be a URLLC flag and / or may be sent in a time slot reserved specifically for the URLLC preamble. For example, this may be standardized in the 3GPP standard.
[0016] The at least one processor may be configured to retransmit the data on frequency resources normally dedicated to transmissions from a base station to a client device. This is particularly beneficial where the system is a base station, as a base station will normally use downlink frequency resources to communicate with a client device. However, uplink frequency resources may additionally or alternatively be used.
[0017] The at least one processor may be configured to listen, using the at least one receiver, for transmission of the data (in the second time interval) and the message (in the third time interval) on frequency resources normally dedicated to transmissions from client devices to a base station. Currently, UEs in LTE only utilize uplink frequency resources for D2D communication between each other. Therefore, messages from client devices will most likely be found on uplink frequency resources. However, downlink frequency resources may additionally or alternatively be used.
[0018] The time intervals may each include a first time period for sending data or messages, a second time period after the first time period for sending the preamble, and a guard period after the second time period. Thus, the present invention may be implemented by sending the preamble using a fraction of a normal transmission time interval (e.g., TTI). The guard period helps other devices process the preamble and decide whether to send in the next transmission time interval. Preferably, the second time period consumes 15% or less of the time interval.
[0019] The preamble can identify the first frequency resource and the second frequency resource. This allows the system and other devices receiving the preamble to still send their data on different frequency resources within the second time interval. The preamble can also identify other frequency resources used by the sending device.
[0020] The at least one processor may be configured to use the at least one receiver to monitor the transmission of the data and the message on the same frequency resource as the preamble. This allows the system to determine which frequency resources to monitor for URLLC data and messages (e.g., negative acknowledgment), i.e., only monitor the frequency resources for sending the preamble. This is beneficial in the case where, for example, the preamble does not identify the first frequency resource and the second frequency resource.
[0021] According to the present invention, the second purpose is achieved in that the device for sending a preamble code includes: at least one transmitter; and at least one processor, the at least one processor being configured to: use the at least one transmitter to send a preamble code within a first time interval, the preamble code indicating that data sent within a second time interval after the first time interval needs to be reliably received by a receiver of the data; and use the at least one transmitter to send data within the second time interval.
[0022] The at least one processor may be configured to classify the data into one of a plurality of categories and send the preamble using the at least one transmitter according to the determined category of the data. Although some devices may be configured to send only URLLC data, many devices will have both URLLC data and non-URLLC data and should only send the preamble before sending the URLLC data to obtain the best results.
[0023] The at least one processor may be configured to use the at least one transmitter to send the preamble and the data on the same frequency resource. This allows the system for receiving the preamble to determine which frequency resources to monitor for URLLC data, ie, only monitor the frequency resources that send the preamble.
[0024] According to the present invention, the third object is achieved in that the method for receiving a preamble, data and a message comprises: monitoring the sending of a preamble by a sending device to a receiving party; when the preamble is received in a first time interval, receiving data in a second time interval, the second time interval being after the first time interval; monitoring the sending of a message by the receiving party, the message indicating that the data sent in the second time interval was not successfully received by the receiving party; and when the message is received in a third time interval, retransmitting the data in a fourth time interval. The method can be executed by software running on a programmable device. This software can be provided as a computer program product.
[0025] According to the present invention, the fourth object is achieved in that the method for sending a preamble and data comprises: sending a preamble in a first time interval, the preamble indicating that data sent in a second time interval after the first time interval needs to be reliably received by a receiver of the data; and sending data in the second time interval. The method can be executed by software running on a programmable device. The software can be provided as a computer program product.
[0026] Furthermore, a computer program for executing the methods described herein and a non-transitory computer-readable storage medium storing the computer program are provided.The computer program can be downloaded from or uploaded to an existing device, or stored when manufacturing these systems, for example.
[0027] A non-transitory computer-readable storage medium stores at least a first software code portion, which is configured to perform executable operations when executed or processed by a computer, the operations including: monitoring a preamble code sent by a sending device to a receiving party; when the preamble code is received within a first time interval, receiving data within a second time interval, the second time interval being after the first time interval; monitoring the sending of a message by the receiving party, the message indicating that the data sent within the second time interval was not successfully received by the receiving party; and when the message is received within a third time interval, retransmitting the data within a fourth time interval.
[0028] A non-transitory computer-readable storage medium stores at least a second software code portion, which is configured to perform executable operations when executed or processed by a computer, the operations including: sending a preamble in a first time interval, the preamble indicating that data sent in a second time interval after the first time interval needs to be reliably received by a recipient of the data; and sending data in the second time interval.
[0029] As will be appreciated by those skilled in the art, aspects of the present invention may be implemented as devices, methods, or computer program products. Thus, aspects of the present invention may take the form of a complete hardware embodiment, a complete software embodiment (including firmware, resident software, microcode, etc.), or a combination of software and hardware aspects that may be generally referred to herein as a "circuit," "module," or "system." The functions described in this disclosure may be implemented as algorithms executed by a processor / microprocessor of a computer. In addition, aspects of the present invention may take the form of a computer program product implemented in one or more computer-readable media having, for example, a stored computer-readable program code implemented thereon.
[0030] Any combination of one or more computer-readable media can be utilized. Computer-readable media can be computer-readable signal media or computer-readable storage media. Computer-readable storage media can be, for example, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the above. More specific examples of computer-readable storage media can include, but are not limited to, the following: an electrical connection device with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the context of the present invention, a computer-readable storage medium can be any tangible medium that can contain or store a program used by or in conjunction with an instruction execution system, device or device.
[0031] A computer-readable signal medium may include a propagated data signal having a computer-readable program code implemented therein (e.g., in baseband or as part of a carrier wave). Such a propagated signal may take any of a variety of forms, including, but not limited to, electromagnetic, optical, or any suitable combination thereof. A computer-readable signal medium may be any computer-readable medium that is not a computer-readable storage medium and that can communicate, propagate, or transmit a program (for use by or in conjunction with an instruction execution system, device, or apparatus).
[0032] The program code implemented on the computer-readable medium can be transmitted using any suitable medium, and this medium includes but is not limited to wireless, wired, optical fiber, cable, RF, etc., or any suitable combination mentioned above. The computer program code for performing the operation of various aspects of the present invention can be written in any combination of one or more programming languages, and the one or more programming languages include object-oriented programming languages such as Java (TM), Smalltalk, C++, etc. and conventional process programming languages such as "C" programming language or similar programming languages. The program code can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on the remote computer, or completely on the remote computer or server. In the latter case, the remote computer can be connected to the user's computer by any type of network including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computer (for example, using an Internet service provider, through the Internet).
[0033] Aspects of the present invention will be described below with reference to the flowchart and / or block diagram of the method, device (system) and computer program product according to an embodiment of the present invention. It will be understood that each frame of the flowchart and / or block diagram and the combination of frames in the flowchart and / or block diagram can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer or other programmable data processing device, specifically a microprocessor or a central processing unit (CPU) to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device or other equipment create a device for implementing the function / action specified in one or more frames of the flowchart and / or block diagram.
[0034] These computer program instructions may also be stored in a computer-readable medium, which may direct a computer, other programmable data processing apparatus, or other device to function in a particular manner, so that the instructions stored in the computer-readable medium produce a manufactured article including instructions, which implement the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0035] The computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable apparatus provide a process for implementing the functions / actions specified in one or more boxes of the flowchart and / or block diagram.
[0036] The flowcharts and block diagrams in the accompanying drawings show the architecture, functions and operations of possible implementations of the devices, methods and computer program products according to various embodiments of the present invention. In this regard, each box in the flowchart or block diagram may represent a module, fragment or part of a code including one or more executable instructions for implementing (multiple) specific logical functions. It should also be noted that in some alternative embodiments, the functions indicated in the box may not occur in the order marked in the figure. For example, depending on the functions involved, the two boxes shown in succession may actually be executed substantially simultaneously, or the boxes may sometimes be executed in the opposite order. It will also be noted that each box of the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can be implemented by a combination of a dedicated hardware-based system or dedicated hardware and computer instructions that perform specific functions or actions. BRIEF DESCRIPTION OF THE DRAWINGS
[0037] These and other aspects of the invention will become apparent and will be further elucidated by way of example with reference to the accompanying drawings, in which:
[0038] · Figure 1 Embodiments of the systems and apparatus of the present invention are described;
[0039] · Figure 2 is a flow chart of a first embodiment of a first method of the present invention;
[0040] · Figure 3 is a flow chart of a first embodiment of a second method of the present invention;
[0041] · Figure 4 is a flow chart of a second embodiment of the first method and the second method of the present invention;
[0042] · Figure 5 is a flow chart of an embodiment of a third method of the present invention;
[0043] · Figure 6 An example of a first method of transmitting in certain time intervals and on frequency resources is depicted;
[0044] · Figure 7 A first example of the method of the present invention for transmitting and receiving in certain time intervals and frequency resources is depicted;
[0045] · Figure 8 A second example of the method of the present invention is depicted in which transmission and reception are performed in certain time intervals and on frequency resources;
[0046] · Fig. 9 A third example of the method of the present invention is depicted in which transmission and reception are performed in certain time intervals and on frequency resources;
[0047] · Fig.10A fourth example of the method of the present invention is depicted in which transmission and reception are performed in certain time intervals and on frequency resources;
[0048] · Fig.11 is a block diagram of an exemplary cellular telecommunications system used in embodiments of the apparatus and system of the present invention; and
[0049] · Fig.12 is a block diagram of an exemplary data processing system for executing the method of the present invention.
[0050] Corresponding elements in the drawings are denoted by the same reference numerals. DETAILED DESCRIPTION
[0051] Figure 1 Embodiments of the system and device of the present invention are depicted. Sensor 1 (S1), sensor 9 (S2), actuator 31 (A1), actuator 39 (A2), and mobile device 21 (UE1) are located in a cell covered by a base station 11 (e.g., eNB or gNB). In most telecommunication standards and in this specification, sensors 1 and 9, actuators 31 and 39, and mobile device 21 are referred to as user equipment (UE). In an example scenario, sensor 1 sends data to actuator 31, sensor 9 sends data to actuator 39, and mobile device 21 sends data to base station 11. In this scenario, sensors 1 and 9 and actuators 31 and 39 perform device-to-device (D2D) direct communication.
[0052] In this scenario, it is assumed that all UEs that require D2D communication (including UEs that send URLLC data) indicate to the base station 11 that they intend to use D2D communication, and it is assumed that all UEs are within the coverage area and connected to the base station 11. Sensors 1 and 9 include processors 3, receivers 5, and transmitters 7. Base station 11 includes processors 13, receivers 15, and transmitters 17. Mobile device 21 includes processors 23, receivers 25, transmitters 23, and memory 29.
[0053] In order to achieve low-latency communication, the processor 3 of the sensor 1 and 9 is configured to send a preamble code in a first time interval using the transmitter 7, and send data in a second time interval after the first time interval using the transmitter 7. The preamble code indicates that the data sent in the time interval after the first time interval needs to be reliably received by the receiver of the data. In this specification, this data is also referred to as ultra-reliable low-latency communication (URLLC) data, and this preamble code is also referred to as a URLLC preamble code.
[0054] In this embodiment, the processor 3 of sensors 1 and 9 is further configured to: use the receiver 5 to monitor the sending of the preamble code, and when it is determined that the preamble code is not received within the first time interval, use the transmitter 7 to send data within a second time interval after the first time interval; and when it is determined that the preamble code is received within the first time interval, give up sending data within the second time interval.
[0055] This allows sensor 1 (S1) to send URLLC data, for example, to actuator 31 (A1). When sensor 9 detects the preamble sent by sensor 1 within the first time interval and does not have URLLC data to be sent, it abandons sending data on the frequency resource (s) used by sensor 1 (S1). This can reduce the latency of URLLC data.
[0056] In this embodiment, the processor 3 of the sensor 1 and 9 is further configured to: use the transmitter 7 to send the preamble code on the first frequency resource in the first time interval, use the transmitter 7 to send the first part or the first copy of the data on the first frequency resource in the second time interval, and use the transmitter 7 to send the second part or the second copy of the data on the second frequency resource in the second time interval. The second frequency resource is separated from the first frequency resource. In this way, more reliable communication can be achieved without increasing latency.
[0057] exist Figure 1 In the embodiment of the present invention, the mobile communication network has reserved a set of uplink (UL) resources for D2D packet transmission, as currently specified in 3GPP for autonomous D2D resource utilization. All UEs including sensors 1 and 9 and mobile device 21 are able to monitor these UL resources, and UEs with D2D functions including sensors 1 and 9 are also able to send data (URLLC packets or non-URLLC packets) on these UL resources.
[0058] For example, a downlink (DL) resource may be used as the second frequency resource. In order to achieve reliable communication with low latency, the processor 13 of the base station 11 is configured to: use the receiver 15 to monitor the transmission of the preamble code, and when it is determined that the preamble code is not received in the first time interval, use the transmitter 17 to send data in a second time interval after the first time interval, and when it is determined that the preamble code is received in the first time interval, give up sending data in the second time interval.
[0059] In other words, when the base station 11 receives the URLLC preamble on the UL resources, the DL scheduler releases the (associated) DL resources so that the URLLC transmission of the UE (sensor 1 in the above example scenario) can use these additional DL time / frequency resources for URLLC data transmission. This improves the reliability of URLLC packet transmission without increasing latency because the second copy or part of the data is not sent later, but on different frequency resources.
[0060] The mobile device 21 does not communicate directly with other devices and therefore will not typically send data on the UL resources reserved for D2D communications. The mobile device 21 will also not send data on the DL resources as these resources are reserved for communications by the base station 11 .
[0061] If it is possible that the second frequency resource or the third frequency resource is not a UL resource reserved for D2D communication, then in order to achieve low-latency communication, the processor 23 of the mobile device 21 can be configured to: use the receiver 25 to monitor the transmission of the preamble code (on the UL resource reserved for D2D communication), and when it is determined that the preamble code is not received within the first time interval, use the transmitter 27 to send data within a second time interval after the first time interval and on the UL resource not reserved for D2D communication; and when it is determined that the preamble code is received within the first time interval, abandon the transmission of data within the second time interval and on the UL resource not reserved for D2D communication.
[0062] exist Figure 1 In the embodiment of , in order to further improve reliability, the processor 13 of the base station 11 is further configured to: use the receiver 15 to monitor the transmission of the preamble code from the transmitting device (e.g., the sensor 1) to the receiving party (e.g., the actuator 31), and when the preamble code is received in the first time interval, use the receiver to receive data in the second time interval. The second time interval is after the first time interval. The processor 13 is further configured to: use the receiver 15 to monitor the transmission of the message (e.g., NACK) by the receiving party indicating that the data sent in the second time interval was not successfully received by the receiving party, and when the message is received in the third time interval, use the transmitter 17 to retransmit the data in the fourth time interval.
[0063] Note that the present invention is particularly advantageous in situations where traffic cannot be pre-scheduled, for example, when the UE has URLLC packets when an event (e.g., emergency failure, alarm, etc.) occurs. Since the arrival of URLLC packets is unpredictable, this type of traffic cannot be pre-scheduled. Even if it can be scheduled by reserving resources, this will not be efficient because most of the time, the reserved radio resources are not utilized because there is no actual URLLC traffic in the system. There are other types of URLLC applications in which devices generate periodic traffic that needs to be sent with low latency and high reliability. Preferably, such traffic is scheduled in a conventional manner (by involving a base station) or by utilizing D2D communications with periodic resource reservation.
[0064] exist Figure 1 In the illustrated embodiment, sensors 1 and 9 include a processor 3. In alternative embodiments, one or more of these sensors include multiple processors. For example, the receiver 5 and transmitter 7 of sensors 1 and 9 can use one or more cellular communication technologies, such as GPRS, CDMA, UMTS, LTE and / or 5G NR, to communicate with actuators 31 and 39 and base station 19. Receiver 5 and transmitter 7 can be combined into a transceiver. Processor 3 can be a general-purpose processor (e.g., an ARM processor) or a dedicated processor. The sensor can include other components typical for sensors, such as a battery. For example, the sensor can be a motion sensor. The device of the present invention can be another device other than a sensor, an actuator or a mobile device.
[0065] exist Figure 1 In the illustrated embodiment, the base station 11 includes a processor 13. In an alternative embodiment, the base station 11 includes multiple processors. For example, the processor 13 of the base station 11 can be a general-purpose processor, such as an Intel or AMD processor, or a dedicated processor. For example, the processor 13 can include multiple cores. For example, the processor 13 can run a Unix-based operating system or a Windows operating system.
[0066] For example, the receiver 15 and the transmitter 17 may use one or more cellular communication technologies, such as GPRS, CDMA, UMTS, LTE and / or 5G / NR, to communicate with UEs (e.g., mobile devices 21, sensors 1 and 9, and actuators 31 and 39). The receiver 15 and the transmitter 17 may be combined into a transceiver. The base station 11 may include other components typical for components in a (e.g., mobile) communication network, such as a power supply. Figure 1 In the illustrated embodiment, the base station 11 comprises one device. In an alternative embodiment, the base station 11 comprises a plurality of devices. The system of the present invention may be another system other than a base station or a mobile device.
[0067] exist Figure 1 In the illustrated embodiment, the mobile device 21 includes a processor 23. In alternative embodiments, the mobile device includes multiple processors. For example, the receiver 25 and the transmitter 27 of the mobile device 21 can use one or more cellular communication technologies, such as GPRS, CDMA, UMTS, LTE and / or 5GNR, to communicate with the base station 11. The receiver 25 and the transmitter 27 can be combined into a transceiver.
[0068] Processor 23 can be a general-purpose processor (e.g., an ARM processor) or a dedicated processor. For example, processor 23 can run Google Android or Apple iOS as an operating system. Memory 29 can include one or more memory units. For example, memory 29 can include solid-state memory. The mobile device can include other components typical for a mobile device, such as a display and a battery. For example, the mobile device can be a mobile phone. The device of the present invention can be another device other than a sensor, an actuator, or a mobile device.
[0069] Figure 2 A first embodiment of the first method of the present invention is shown in . Step 101 includes sending a preamble code on a first frequency resource in a first time interval. Step 103 includes sending a first part or a first copy of the data on the first frequency resource in a second time interval. The second time interval is after the first time interval. Step 105 includes sending a second part or a second copy of the data on a second frequency resource in the second time interval. The second frequency resource is separate from the first frequency resource. In an alternative embodiment, the first method does not include step 105, and the data is sent on a single frequency resource. Figure 2 In an embodiment of the present invention, the preamble code indicates that data sent in a second time interval after the first time interval needs to be reliably received by a receiver of the data.
[0070] Figure 3 The first embodiment of the second method of the present invention is shown in FIG. Step 111 includes monitoring the transmission of a preamble. Step 115 includes, when it is determined in step 117 that the preamble is not received in the first time interval, transmitting data in a second time interval after the first time interval. Step 113 includes, when it is determined in step 117 that the preamble is received in the first time interval, abandoning the transmission of data in the second time interval.
[0071] Figure 4 A second embodiment of the first method and the second method is shown in FIG. Typically, a URLLC device performs both the first method and the second method. Figure 4In step 121, it is determined whether the device has any data to be sent. If not, step 121 is performed again until the device has data to be sent. In other words, step 121 includes waiting until the device has data to be sent. If the device has data to be sent, step 123 is performed next.
[0072] exist Figure 4 In an embodiment of the present invention, the data has been classified into one of a plurality of categories. In step 123, the category of the data to be sent is checked. If the device has URLLC data to be sent, then step 101 is performed next. In step 101, a preamble is sent. If the device has non-URLLC data to be sent, then a URLLC preamble is not sent, but step 111 is performed next. In step 111, the device listens for the transmission of a URLLC preamble. Steps performed after step 111 are as follows: Figure 3 The steps performed after step 101 are shown in Figure 2 After data (non-URLLC data) is sent in step 115, or after data (URLLC data) is sent in steps 103 and 105, step 121 is executed again. If the device gives up sending, that is, step 113 is executed, step 111 is repeated, and the device listens to the sending of the URLLC preamble again to check whether it is now allowed to send its non-URLLC data.
[0073] Figure 5 An embodiment of the third method of the present invention is shown in . Step 151 includes monitoring the transmission of a preamble by a transmitting device to a receiving party. If it is determined in step 161 that the preamble has been received, step 153 is then performed. Step 153 includes receiving data in a second time interval when the preamble is received in a first time interval. The second time interval is after the first time interval. Step 155 includes monitoring the transmission of a message by the receiving party indicating that the data transmitted in the second time interval was not successfully received by the receiving party in a third time interval after the second time interval. If it is determined in step 163 that the message has been received, step 157 is then performed. Step 157 includes retransmitting the data received in step 153 in a fourth time interval when the message is received in the third time interval.
[0074] Figure 6 An example of the first method of transmitting in certain time intervals and frequency resources is depicted. Figure 2 In step 101, a preamble 44 is sent within a first time interval ti1. Figure 2In step 103, data 43 is sent in the second time interval ti2 on the same frequency resource as the preamble. As shown in the time interval ti3, data 43 is sent in the time period 53 for sending data. As shown in the time interval ti3, the preamble 44 is sent in the time period 54 for sending the preamble. Time period 54 is after time period 53, and the guard period 55 is after time period 54. The existence of the guard period 55 is to help the base station and other UEs process the information sent by the preamble and make decisions about possible communications planned in the next time interval. The preamble preferably consumes 15% or less of the first time interval. In other words, the period 54 preferably consumes 15% or less of these time intervals.
[0075] Figure 7 Table 61 depicts a first example of the method of the present invention for transmitting and receiving in certain time intervals and frequency resources. Figure 7 In the example, sensor S1 ( Figure 1 Sensor 1) sends a signal to actuator A1 ( Figure 1 The executor 31 of the sensor 31 sends URLLC data. The uplink resource u2 is reserved for D2D communication. Before sending the URLLC data, the sensor S1 sends a preamble 44, such as a flag, on the uplink resource u2. The base station and other UEs nearby (UEs that do not need D2D URLLC communication) detect this preamble 44. The preamble 44 indicates that the UE will attempt URLLC transmission in the next time interval. Figure 6 As shown, the guard period follows the preamble 44 directly. The guard period marks the end of the time interval. Including the preamble and the guard period in the time interval also means that the payload of the URLLC D2D data transmission in the subsequent time interval must be slightly shorter than the total time interval length to leave room for the same UE or other UEs that need URLLC transmission to send the next URLLC preamble. This is Figure 6 Shown in.
[0076] Before the expected / planned time interval starts, conventional UEs (e.g., UEs for eMMB services) and D2D UEs with non-URLLC packets must first listen for the transmission of a URLLC preamble. A D2D UE with a non-URLLC packet only transmits on the UL resources reserved for D2D communication if it does not receive a URLLC preamble. Conventional UEs (e.g., UEs for eMBB services) give up completely using the UL resources assigned by the base station scheduler in the next time interval, because some of these UL resources may also be used by URLLC transmissions. Unlike UEs with URLLC packets, UEs with non-URLLC packets will send data directly (as long as allowed) without first sending a preamble.
[0077] To improve reliability, sensor S1 sends a second copy or part of the URLLC packet on the 'associated / preconfigured' DL resource d2 in addition to the UL resource u2. Executor A1 receives / listens to the same UL resource u2 and DL resource d2. After detecting the URLLC preamble 44 sent just before the start of time interval ti2, the base station will release this DL resource d2 for URLLC transmission.
[0078] exist Figure 7 In the example of , UL frequency resource u2 is allocated to device-to-device communication, while DL frequency resource d2 is not allocated to device-to-device communication. Figure 7 In an example, a first copy or portion of a URLLC packet is sent on an UL frequency resource that is typically dedicated to transmissions from a client device to a base station, and a second copy or portion of the URLLC packet is sent on a DL frequency resource that is typically dedicated to transmissions from a base station to a client device. In an alternative embodiment, a second copy or portion of the URLLC packet is also sent on a frequency resource that is typically dedicated to transmissions from a client device to a base station.
[0079] Optionally, sensor S1 may send another copy or part of the URLLC packet on an additional 'associated / preconfigured' UL resource. This is because a conventional UE (e.g., an eMBB user) may give up completely using the UL resource allocated by the base station scheduler upon receiving the URLLC preamble. This is not Figure 7 Executor A1 will monitor both UL resource u2 and DL resource d2 in time interval ti2. Optionally, Executor A1 will also monitor additional UL resources ( Figure 7 not shown).
[0080] exist Figure 7 In the illustrated embodiment, different copies of the data are sent on different frequency resources. In an alternative embodiment, different portions of the data are sent on different frequency resources.
[0081] exist Figure 7In the illustrated embodiment, the base station also monitors UL resource u2 (i.e., the same frequency resource on which the preamble is sent) to decode the URLLC packet for (possible) future retransmission in the event that executor A1 fails to receive the packet (data1) and sends a broadcast NACK on UL resource u2. Thus, the data and NACK are sent on frequency resources that are normally dedicated to transmissions from client devices to the base station. In the present embodiment, executor A1 decides to send a broadcast NACK because it received the preamble 44 within the time interval ti1. In an alternative embodiment, executor A1 decides to send a broadcast NACK because the packet (data1) indicates that data1 is URLLC data. Figure 7 In the example of FIG. 1 , actuator A1 fails to receive a URLLC packet in time interval ti2 and sends a broadcast NACK in time interval ti3. The base station receives this NACK, and sensors S1 and S2 also receive this NACK.
[0082] After sensors S1 and S2 receive the NACK, sensors S1 and S2 retransmit the URLLC packet (data1) in time interval ti4 by using UL resource u2 because no new URLLC packet is ready to send. In this example, there are two sensors retransmitting URLLC packets. In practice, how many devices will retransmit URLLC packets may depend on how many nearby devices are willing to retransmit data for other devices. When multiple devices send the same URLLC packet, the URLLC packet may go through different paths, thereby increasing the probability that the URLLC packet is correctly received by a properly configured receiver. The retransmission of the URLLC packet will take precedence over new non-URLLC D2D packets. After the base station detects the NACK, the base station releases the previously scheduled communication on DL resource d2 for time interval ti4 and uses it to retransmit the URLLC packet (data1). Therefore, it retransmits data on a frequency resource that is usually dedicated to transmission from the base station to the client device. After actuator A1 sends the NACK, actuator A1 will start listening on UL resource u2 and DL resource d2 simultaneously to receive the URLLC packets retransmitted by sensor S1 and the base station in time interval ti4.
[0083] For non-URLLC D2D traffic, only the preconfigured UL time / frequency resource u2 is used and no preamble is sent before the non-URLLC packet is sent. In this case, the base station can continue to schedule regular traffic on the DL time / frequency resource d2 because non-URLCC traffic can withstand longer delays. The scheduling duration for regular UEs providing eMBB services can be much longer (including multiple TTIs) than the scheduling duration required for URLLC services. If a URLLC packet arrives between scheduled eMBB packets, the URLLC packet can get its required portion by using puncturing techniques.
[0084] Figure 7 It also shows that the base station sends a message to UE1 ( Figure 1 The mobile device 21) sends a non-URLLC packet, and UE1 sends an ACK (ack2) to the base station on the UL resource u4 (which is not a resource reserved for D2D communication) within the time interval ti4. Figure 7 In the example of , UE1 did not retransmit the URLLC packet sent by sensor S1 because UE1 was receiving non-URLLC packets from the base station. In another example, UE1 may have additionally or alternatively retransmitted the URLLC packet sent by sensor S1.
[0085] Figure 8 Table 81 depicts a second example of the method of the present invention for transmitting and receiving in certain time intervals and frequency resources. Figure 8 In the embodiment of , two sensors simultaneously transmit URLLC data on different frequency resources. UL frequency resource u2 and DL frequency resource d2 have been assigned to sensor S1, while UL frequency resource u4 and DL frequency resource d4 have been assigned to sensor S2.
[0086] Sensor S2 sends URLLC preamble 84 on frequency resource u4 during time interval ti1, then sends a first copy or portion of URLLC packet (data3) to actuator A2 on frequency resource u4 during time interval ti2, and sends a second copy or portion of URLLC packet to the actuator on frequency resource d4 during time interval ti2. When the base station detects that actuator A2 sends NACK on UL frequency resource u4 during time interval ti3, the base station retransmits URLLC packet (data3) to actuator A2. Figure 7 Another difference of the example of is that sensors S1 and S2 do not receive the broadcast NACK in time interval ti3, and therefore do not retransmit the URLLC packet in time interval ti4. Only the base station retransmits the URLLC packet in time interval ti4.
[0087] Fig. 9 A third example of the method of the present invention is depicted in which transmission and reception are performed in certain time intervals and on frequency resources. Fig. 9 Four D2D pairs with simultaneous URLLC transmissions are shown, namely, (S1, A1) to (S4, A4). If these D2D pairs use the same UL resources and / or DL resources, packet collisions and interference may occur, resulting in data corruption and increased latency. This problem can be alleviated by using non-overlapping separate UL (and DL) resources for (S1, A1) to (S4, A4) to prevent the D2D pairs from colliding in their URLLC packet transmissions.
[0088] The allocation of non-overlapping resource pools for the pairs (S1, A1) to (S4, A4) is done by signaling from the base station and using their radio network temporary identifiers (RNTIs). Thus, the sensors S1 to S4 receive a message assigning one or more frequency resources to the sensors S1 to S4, and if the sensor has no URLLC packet, it listens to the transmission of the preamble on at least one of the one or more assigned frequency resources and / or the anchor frequency resource (which may be the assigned frequency resource). If there are other D2D pairs in the coverage area of the base station and they do not cause severe interference to the pairs (S1, A1) to (S4, A4), their resources may be reused.
[0089] To avoid packet collision / interference between different D2D pairs, the amount of non-overlapping UL (and DL) resources should match the number of D2D pairs that are intended to perform URLLC transmissions simultaneously. The base station should monitor the traffic conditions and then allocate more resources or release some allocated resources based on the number of simultaneously active D2D URLLC pairs to abandon resource reservation overhead.
[0090] In addition, in the presence of multiple simultaneous URLLC D2D transmissions, the solution should also consider the transmission of preambles and their mapping to UL resources and DL resources. For simultaneous preamble transmissions of URLLC D2D pairs, there are two options:
[0091] · Send the preamble on the same UL resource (an anchor UL resource) in a way that the preamble can be distinguished by the receiver (base station or other terminals in the vicinity). For example, the preamble transmission can be a Zadoff-Chu sequence (see https: / / en.wikipedia.org / wiki / Zadoff-Chu_sequence) or an encoded version of the preamble index is transmitted. For example, the 8-bit preamble index is encoded so that the receiver can distinguish overlapping transmissions. In this case, up to 2 preambles can be sent simultaneously. 8 = 256 different preamble indexes.
[0092] ·like Fig. 9 As shown, the preambles are sent on non-overlapping UL frequency resources, where it is assumed that four different D2D URLLC pairs are transmitting simultaneously. In time interval ti1, each D2D pair can use its own UL resources (e.g., which UL resource to use is based on its RNTI as signaled by the base station) to send its preambles 201 to 204. Then, in the following time interval ti3, the actual D2D URLLC data transmission is performed on the associated UL resources and DL resources agreed between the terminal and the base station (i.e., this is preconfigured).
[0093] exist Fig. 9 In an embodiment, two UEs send a third copy or a third part of the URLLC data on a third frequency resource within a time interval ti3. The first frequency resource and the third frequency resource on which these UEs send their URLLC data are usually dedicated to transmission from the client device to the base station (i.e., uplink frequency resources), and the second frequency resource on which these UEs send their URLLC data is usually dedicated to transmission from the base station to the client device (i.e., downlink frequency resources).
[0094] exist Fig. 9 In the example of , the first UE sends its URLLC data on frequency / time resources 211 (D2D UL) and 231 (conventional DL), the second UE sends its URLLC data on frequency / time resources 212 (D2D UL), 222 (conventional UL) and 232 (conventional DL), the third UE sends its URLLC data on frequency / time resources 213 (D2D UL) and 233 (conventional DL), and the fourth UE sends its URLLC data on frequency / time resources 214 (D2D UL), 224 (conventional UL) and 234 (conventional DL). Preambles 201 to 204 are sent on D2D uplink frequency resources (u3 to u6).
[0095] The preamble sent in time interval ti2 also indicates which UL resources and DL resources (preconfigured as agreed with the base station) will be used for the actual URLLC data transmission in time interval ti3. Frequency resources u1 and u2 may be shared between D2D type and non-D2D type devices. In such cases, non-D2D users will listen to the mapped D2D resources (e.g., in the UL resources u1 and u2) before sending their packets on them. Fig. 9 In the examples, they are possible preamble transmissions on u4 and u6).
[0096] exist Fig. 9In an embodiment of the present invention, the preamble identifies the assigned frequency resource. It would be beneficial if other devices knew which frequency resource to listen to the preamble on, but did not know which other frequency resources would be used to send URLLC data in subsequent time intervals. Alternatively, other devices can listen to the assignment broadcast of the base station.
[0097] The base station monitors all UL resources reserved for D2D (e.g. Fig. 9 u3 to u6 in the UL resources (where a preamble may be sent on these resources within time interval ti2) in order to detect notifications (in the form of preambles) about URLLC data transmission within time interval ti3. D2D-capable UEs without URLLC data listen for preambles on the UL resources reserved for D2D, where these UEs themselves will send preambles (assigned to them by the base station) on these resources. Non-D2D UEs listen for preambles on the UL resources reserved for D2D, which are paired with the non-D2D UL resources on which these UEs will send data. The base station can broadcast information about which channels are paired.
[0098] Regarding data, within the time interval ti3, the D2D receiver (e.g., Fig. 9 A1 to A4 in the figure only monitor the mapped UL resources and DL resources (e.g., executor A2 monitors frequency resources 212, 222, and 232) on which the transmitting D2D device will send URLLC data, while the base station can monitor all possible mapped UL resources and DL resources or a portion of these frequency resources (e.g., one or more of frequency resources 211 to 234) so as to be able to correctly receive the data and retransmit it later if necessary, as explained below. The inactive surrounding UEs monitor all or part of the frequency resources on which they will send their own data or the frequency resources paired with these frequency resources so as to be able to correctly receive the data and retransmit it later if necessary, as explained below.
[0099] Fig.10 A fourth example of the method of the present invention is depicted in which transmission and reception are performed in certain time intervals and on frequency resources. Fig.10 A situation is shown in which data is retransmitted and there are multiple simultaneous URLLC data transmissions. After the data transmission in time interval ti3, and if the receiver sends a broadcast NACK (because corrupted data is received) to request a retransmission in time interval ti4, the data will be retransmitted twice:
[0100] 1. The base station retransmits the URLLC packet in time interval ti5 on the same DL resources d1 to d4 (frequency / time resources 251 to 254) as time interval ti3 (frequency / time resources 231 to 234) (if the packet is correctly received by the base station in time interval ti3); and
[0101] 2. All surrounding inactive UEs (e.g., mobile devices UE1 to UE4) that correctly received the transmitted URLLC data in time interval ti3 retransmit the URLLC data in time interval ti5 on the same UL resources u3 to u6 (frequency / time resources 241 to 244) as time interval ti3 (frequency / time resources 211 to 214). As an exception, non-D2D devices may be allowed to retransmit URLLC data on frequency resources dedicated to D2D, because this retransmission is not for the base station, but for the D2D device.
[0102] exist Fig.11 In the telecommunication system 400, for the sake of simplicity, three generations of networks are schematically depicted together. A more detailed description of the architecture and overview can be found in 3GPP Technical Specification TS 23.002 "Network Architecture", which is incorporated by reference in its entirety in this application. Other types of cellular telecommunication systems, such as 5G cellular telecommunication systems, may be used alternatively or additionally.
[0103] Fig.11 The lower branch represents the GSM / GPRS or UMTS network.
[0104] For GSM / GPRS networks, the radio access network (RAN) system 420 includes multiple nodes, including base stations (a combination of BSC and BTS), Fig.11 The core network system includes a gateway GPRS support node 422 (GGSN), a serving GPRS support node 421 (SGSN, for GPRS) or a mobile switching center (MSC, for GSM, Fig.11 ), and a home location register 423 (HLR). The HLR 423 contains subscription information of the user equipment 401 (eg, mobile station MS).
[0105] For the UMTS radio access network (UTRAN), the radio access network system 420 also includes a radio network controller (RNC) connected to multiple base stations (NodeBs). Fig.11 In the core network system, the GGSN 422 and the SGSN 421 / MSC are connected to the HLR 423 containing the subscription information of the user equipment 401 (eg, the user equipment UE).
[0106] Fig.11The upper branch of the telecommunication system in represents the 4G network, usually denoted as the Long Term Evolution (LTE) system or the Evolved Packet System (EPS).
[0107] The radio access network system 410 (E-UTRAN) of EPS includes Fig.11 The core network system includes base stations (evolved NodeB, eNodeB or eNB) not shown separately, which provide cellular radio access for user equipment 401 (e.g., user equipment UE). The core network system includes a PDN gateway (P-GW) 414 and a serving gateway 412 (S-GW). The E-UTRAN 410 of the EPS is connected to the S-GW 412 via a packet network. For signaling purposes, the S-GW 412 is connected to a home subscriber server HSS 413 and a mobility management entity MME 411. The HSS 413 includes a subscription profile repository SPR for the user equipment 401.
[0108] For GPRS, UMTS and LTE systems, the core network system is usually connected to another packet network 402, such as the Internet.
[0109] Further information on the general architecture of an EPS network can be found in 3GPP Technical Specification TS 23.401 "GPRS Enhancements for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access".
[0110] Fig.12 Describes the demonstration of executable reference Figures 2 to 5 A block diagram of an exemplary data processing system for describing the method.
[0111] like Fig.12 As shown, data processing system 500 may include at least one processor 502 coupled to memory element 504 via system bus 506. In this way, the data processing system can store program code in memory element 504. Further, processor 502 can execute program code accessed from memory element 504 via system bus 506. In one aspect, the data processing system can be implemented as a computer suitable for storing and / or executing program code. However, it should be understood that data processing system 500 can be implemented in the form of any system including a processor and a memory capable of performing the functions described in this specification.
[0112] Memory element 504 may include one or more physical memory devices, such as, for example, local memory 508 and one or more mass storage devices 510. Local memory may refer to random access memory or other (multiple) non-persistent storage devices commonly used during the actual execution of program code. Mass storage devices may be implemented as hard drives or other persistent data storage devices. Processing system 500 may also include one or more cache memories (not shown) that provide temporary storage of at least some program code to reduce the number of times program code must be retrieved from mass storage devices 510 during execution.
[0113] Input / output (I / O) devices, depicted as input device 512 and output device 514, may optionally be coupled to the data processing system. Examples of input devices may include, but are not limited to, a keyboard, a pointing device such as a mouse, etc. Examples of output devices may include, but are not limited to, a monitor or display, speakers, etc. Input devices and / or output devices may be coupled to the data processing system directly or through intervening I / O controllers.
[0114] In an embodiment, the input device and the output device may be implemented as a combined input / output device (in Fig.12 512 and output device 514). An example of such a combination device is a touch-sensitive display, sometimes also referred to as a "touch screen display" or simply a "touch screen." In such an embodiment, input to the device can be provided by movement of a physical object (such as, for example, a stylus or a user's finger) on or near the touch screen display.
[0115] Network adapter 516 may also be coupled to the data processing system to enable it to couple to other systems, computer systems, remote network devices, and / or remote storage devices through an intermediate private or public network. The network adapter may include a data receiver for receiving data sent by the system, device, and / or network to the data processing system 500, and a data transmitter for sending data from the data processing system 500 to the system, device, and / or network. Modems, cable modems, and Ethernet cards are examples of different types of network adapters that may be used with the data processing system 500.
[0116] like Fig.12 As depicted, memory element 504 may store application 518. In various embodiments, application 518 may be stored in local memory 508, one or more mass storage devices 510, or separate from local memory and mass storage devices. It should be understood that data processing system 500 may further execute an operating system (OS) capable of facilitating the execution of application 518. Fig.125. The application 518 implemented in the form of executable program code may be executed by the data processing system 500 (eg, by the processor 502). In response to executing the application, the data processing system 500 may be configured to perform one or more operations or method steps described herein.
[0117] Various embodiments of the present invention may be implemented as a program product for use with a computer system, wherein the program of the program product defines the functionality of the embodiment (including the methods described herein). In one embodiment, the program may be contained on various non-transitory computer-readable storage media, wherein, as used herein, the expression "non-transitory computer-readable storage medium" includes all computer-readable media, with the only exception of temporarily propagated signals. In another embodiment, the program may be contained on various temporary computer-readable storage media. Illustrative computer-readable storage media include, but are not limited to: (i) non-writable storage media on which information is permanently stored (e.g., a read-only storage device within a computer, such as a CD-ROM disk readable by a CD-ROM drive, a ROM chip, or any type of solid-state non-volatile semiconductor memory); and (ii) writable storage media on which variable information is stored (e.g., a flash memory, a floppy disk within a floppy disk drive or a hard disk drive, or any type of solid-state random access semiconductor memory). The computer program may run on the processor 502 described herein.
[0118] The terms used herein are used only to describe specific embodiments and are not intended to limit the present invention. As used herein, the singular forms "a", "an", and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that when the terms "comprises" and / or "comprising", when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and / or parts, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, parts, and / or groups thereof.
[0119] The corresponding structures, materials, actions, and equivalents of all means or steps plus functional elements in the following claims are intended to include any structure, material, or action for performing a function in combination with other claimed elements as specifically claimed. The description of the embodiments of the present invention has been presented for illustrative purposes, but the description is not intended to be exhaustive or to limit the implementation to the disclosed form. Many modifications and variations will be obvious to those of ordinary skill in the art without departing from the scope and spirit of the present invention. The selection and description of the embodiments are intended to best explain the principles of the present invention and some practical applications, and when suitable for the specific purpose contemplated, enable other persons of ordinary skill in the art to understand the present invention for various embodiments with various modifications.
Claims
1. A system (11, 21, 9) for receiving a preamble, data and a message, the system comprising: at least one receiver (15, 25, 5); at least one transmitter (17, 27, 7); as well as At least one processor (13, 23, 3), the at least one processor being configured to: - using the at least one receiver to monitor a preamble sent by a sending device to a receiving party, wherein the preamble indicates that data sent in a second time interval needs to be reliably received by the receiving party of the data, - receiving data in a second time interval using the at least one receiver upon receiving the preamble in a first time interval, the second time interval being after the first time interval, - using the at least one receiver to monitor the sending of a message by the recipient, the message indicating that data sent within the second time interval was not successfully received by the recipient, and - upon receipt of said message in a third time interval, retransmitting said data in a fourth time interval using said at least one transmitter.
2. The system (11, 21, 9) of claim 1, wherein: The at least one processor (13, 23, 3) is configured to use the at least one receiver (15, 25, 5) to monitor the transmission of the data and the message on the same frequency resources as the transmission of the preamble.
3. A system (11) as claimed in any one of the preceding claims, wherein: The at least one processor (13) is configured to retransmit the data on frequency resources normally dedicated for transmission from a base station to a client device.
4. A system (11, 21, 9) as claimed in any one of claims 1 to 2, wherein: The at least one processor (13, 23, 3) is configured to use the at least one receiver (15, 25, 5) to listen for transmissions of the data and the message on frequency resources normally dedicated to transmissions from a client device to a base station.
5. The system (11, 21, 9) according to any one of the preceding claims 1-2, wherein: The time intervals each include a first period for transmitting data or a message, a second period for transmitting the preamble after the first period, and a guard period after the second period.
6. The system (11, 21) according to any one of the preceding claims 1-2, wherein: The preamble code at least identifies a first frequency resource and a second frequency resource.
7. A device (1) for sending a preamble and data, at least one transmitter (7); and At least one processor (3), the at least one processor being configured to: - using the at least one transmitter (7) to transmit a preamble in a first time interval, the preamble indicating that data transmitted in a second time interval after the first time interval needs to be reliably received by a receiver of the data, and - using said at least one transmitter (7) to transmit data during said second time interval.
8. The device (1) as claimed in claim 7, wherein: The at least one processor (3) is configured to classify the data into one of a plurality of categories and transmit the preamble using the at least one transmitter (7) according to the determined category of the data.
9. The device (1) as claimed in claim 7 or 8, wherein: The at least one processor (3) is configured to transmit the preamble and the data on the same frequency resource using the at least one transmitter (7).
10. A method for receiving a preamble, data and a message, the method comprising: -Monitor (151) the preamble code sent by the sending device to the receiving party; - receiving (153) data in a second time interval upon receiving the preamble in a first time interval, the second time interval being after the first time interval, wherein the preamble indicates that the data sent in the second time interval needs to be reliably received by the receiver of the data; - monitoring (155) the sending of a message by the recipient indicating that data sent within the second time interval was not successfully received by the recipient; and - upon receipt of said message within the third time interval, retransmitting (157) said data within a fourth time interval.
11. A method for sending a preamble and data, the method comprising: - sending (101) a preamble in a first time interval, the preamble indicating that data sent in a second time interval after the first time interval needs to be reliably received by a receiver of the data; and - sending (103, 105) data during said second time interval.
12. A computer program product comprising at least one software code portion or a computer program storing at least one software code portion, which software code portion is configured to perform the method according to any one of claims 10 to 11 when run on a computer system.
