An information transmission method and apparatus, a communication device, and a storage medium

Abstract

This invention discloses an information transmission method, apparatus, communication device, and storage medium. The method includes: when a first device determines that first data received using a first process has not been successfully received and / or has not been successfully decoded, sending a NACK message for the first data to a second device; when the first device receives second data sent by the second device using the first process, sending a first message to the second device, the first message indicating that the second device has incorrectly acknowledged the NACK message for the first data, and the first message being used to trigger the second device to retransmit the first data.

Description

Technical Field

[0001] This invention relates to the field of communication technology, and more specifically to an information transmission method, apparatus, communication device, and storage medium. Background Technology

[0002] Currently, communication systems control the transmission quality of data packets through Automatic Repeat Request (ARQ) at the Radio Link Control (RLC) layer and Hybrid Automatic Repeat Request (HARQ) at the Media Access Control (MAC) layer. In the HARQ mechanism, the HARQ process sends out Acknowledgement (ACK) or Negative Acknowledgement (NACK) responses to handle new transmissions and retransmissions. However, because the ACK / NACK detection mechanism has a probability of false detection and missed detection, the sending HARQ process may receive incorrect ACK / NACK responses from the receiving HARQ process. This means that the sending HARQ process cannot accurately determine whether a retransmission is necessary, leading to situations where a Transport Block (TB) is not successfully transmitted, and the sending HARQ process stops retransmission due to misjudgment. In addition, if ARQ is used, ARQ is the Acknowledgment Mode (AM) at the RLC layer. Since the RLC layer is above the MAC layer, although the error rate is guaranteed, the response time is too long, which makes it difficult to meet the needs of high reliability and low latency services. Summary of the Invention

[0003] To address the existing technical problems, embodiments of the present invention provide an information transmission method, apparatus, communication device, and storage medium.

[0004] To achieve the above objectives, the technical solution of this invention is implemented as follows:

[0005] In a first aspect, embodiments of the present invention provide an information transmission method, the method being applied to a first device, the method comprising:

[0006] When the first device determines that the first data received using the first process has not been successfully received and / or has not been successfully decoded, it sends a NACK message for the first data to the second device.

[0007] When the first device receives the second data sent by the second device using the first process, it sends a first message to the second device. The first message indicates that the second device has made an incorrect confirmation of the feedback information regarding the first data. The first message is used to trigger the second device to retransmit the first data.

[0008] In the above scheme, the method further includes: caching the first data in a first cache corresponding to the first process; and / or,

[0009] If the second data is not successfully received and / or not successfully decoded, the second cache corresponding to the first process is requested, and the second data is cached in the second cache.

[0010] In the above scheme, when the first device determines that the first data received using the first process was not successfully received and / or not successfully decoded, the method further includes:

[0011] The first device starts the timer;

[0012] When the first device receives the second data sent by the second device using the first process, it sends a first message to the second device, including:

[0013] Within the timer's timing range, if the first device receives the second data sent by the second device using the first process, it sends a first message to the second device.

[0014] In the above scheme, the method further includes: when the timer times out, if the first device does not receive the first data retransmitted by the second device, sending a NACK message for the first data to the second device.

[0015] In the above scheme, sending the first message to the second device includes:

[0016] The first device sends the first message to the second device via resources indicated by downlink control information (DCI); or,

[0017] The first device sends the first message to the second device via the resources indicated by the authorized configuration (CG).

[0018] Secondly, embodiments of the present invention also provide an information transmission method, the method being applied to a second device, the method comprising:

[0019] When the second device receives a second message sent by the first device and determines that the second message is an ACK message for the first data, it does not release the cached first data; the first data is data sent by the first device using the second process.

[0020] The second device sends second data to the first device using the second process, and upon receiving a feedback message regarding the second data, determines to release the first data.

[0021] In the above scheme, the method further includes: the second device receiving a first message for the first data and retransmitting the first data, wherein the first message indicates that the second device has incorrectly confirmed the feedback information for the first data.

[0022] In the above scheme, before the second device receives the second message sent by the first device, the method further includes: the second device using a second process to send the first data to the first device, and caching the first data in a first cache corresponding to the second process.

[0023] In the above scheme, after the second device receives the second message sent by the first device and determines that the second message is an ACK message for the first data, the method further includes:

[0024] The second device requests the second cache corresponding to the second process and migrates the first data from the first cache to the second cache.

[0025] In the above scheme, after the second device receives the first message for the first data, the method further includes: the second device moving the first data from the second cache to the first cache.

[0026] In the above scheme, after the second device retransmits the first data, the method further includes: the second device receives an ACK message for the first data and determines to release the first data.

[0027] In the above scheme, the second device receives a first message regarding the first data, including:

[0028] The second device receives a first message for the first data via resources indicated by downlink control information (DCI); or,

[0029] The second device receives a first message for the first data via the resources indicated by the authorized configuration (CG).

[0030] Thirdly, embodiments of the present invention also provide an information transmission device, which is applied to a first device, and the device includes: a first processing unit and a first communication unit; wherein,

[0031] The first processing unit is used to determine whether the first data received by the first process was successfully received and / or successfully decoded;

[0032] The first communication unit is configured to send a NACK message for the first data to the second device when the first processing unit determines that the first data received by the first process was not successfully received and / or was not successfully decoded; and is further configured to send a first message to the second device when the first process receives the second data sent by the second device, the first message indicating that the second device has made an incorrect acknowledgment of the NACK message for the first data, and the first message is used to trigger the second device to retransmit the first data.

[0033] Fourthly, embodiments of the present invention also provide an information transmission device, which is applied to a second device, and the device includes: a second communication unit and a second processing unit; wherein,

[0034] The second communication unit is used to receive a second message sent by the first device;

[0035] The second processing unit is configured to, when determining that the second message is an ACK message for the first data, not release the cached first data; the first data is data sent by the first device using the second process;

[0036] The second communication unit is further configured to send second data to the first device using the second process, and receive feedback messages for the second data;

[0037] The second processing unit is further configured to determine to release the first data when the second communication unit receives a feedback message for the second data.

[0038] Fifthly, embodiments of the present invention also provide a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the steps of the information transmission method described in the first or second aspect of the embodiments of the present invention.

[0039] In a sixth aspect, embodiments of the present invention also provide a communication device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the information transmission method described in the first or second aspect of the embodiments of the present invention.

[0040] In a seventh aspect, embodiments of the present invention also provide a computer program product, including computer program instructions that cause a computer to perform the steps of the information transmission method described in the first or second aspect of the embodiments of the present invention.

[0041] The information transmission method, apparatus, communication device, and storage medium provided in this invention, for a first device (i.e., the receiving device), after sending a corresponding NACK message for received first data, receiving new data (second data) indicates that the second device has misjudged the NACK message fed back by the first device. The first device sends a first message to the second device to indicate that the second device has incorrectly acknowledged the NACK message for the first data. For the second device (the sending device), after receiving the ACK message for the first data, it does not immediately release the buffer of the first data. Instead, after sending new data (second data), it receives a feedback message for the second data, thereby determining that the first data was successfully received by the first device, that is, determining that the received ACK message for the first data was correctly understood. Based on the results of multiple verifications, it decides whether to release the buffer of the first data. On the one hand, this reduces the probability of the sending end "stopping retransmission" due to misjudgment, reduces data transmission latency, and improves data transmission reliability. On the other hand, it achieves error-free transmission over the air interface, improving the robustness of the air interface. Attached Figure Description

[0042] Figure 1 This is a flowchart illustrating the information transmission method according to an embodiment of the present invention. Figure 1 ;

[0043] Figure 2 This is a flowchart illustrating the information transmission method according to an embodiment of the present invention. Figure 2 ;

[0044] Figure 3 This is an interactive schematic diagram of the information transmission method according to an embodiment of the present invention;

[0045] Figure 4 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of the present invention. Figure 1 ;

[0046] Figure 5 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of the present invention. Figure 2 ;

[0047] Figure 6 This is a schematic diagram of the hardware composition structure of a communication device according to an embodiment of the present invention. Detailed Implementation

[0048] The present invention will now be described in further detail with reference to the accompanying drawings and specific embodiments.

[0049] The technical solutions of this invention can be applied to various communication systems, such as GSM (Global System of Mobile communication), LTE (Long Term Evolution), or 5G systems. Optionally, a 5G system or 5G network can also be referred to as a New Radio (NR) system or NR network.

[0050] For example, the communication system used in this embodiment of the invention may include network devices and terminal devices (also referred to as terminals, communication terminals, etc.); the network device may be a device that communicates with the terminal device. The network device can provide communication coverage within a certain area and can communicate with terminals located within that area. Optionally, the network device may be a base station in various communication systems, such as an evolved Node B (eNB) in an LTE system, or a gNB in ​​a 5G or NR system.

[0051] It should be understood that devices with communication functions in the network / system of this application embodiment can be referred to as communication devices. Communication devices may include network devices and terminals with communication functions. Network devices and terminal devices can be the specific devices described above, which will not be repeated here. Communication devices may also include other devices in the communication system, such as network controllers, mobility management entities, and other network entities. This embodiment of the present invention does not limit these.

[0052] It should be understood that the terms "system" and "network" are often used interchangeably in this document. The term "and / or" in this document merely describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. Furthermore, the character " / " in this document generally indicates that the preceding and following related objects have an "or" relationship.

[0053] The terms “first,” “second,” etc., used in the specification and claims of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented, for example, in orders other than those illustrated or described herein. Furthermore, the terms “comprising” and “having,” and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0054] Before providing a detailed description of the technical solutions of the embodiments of the present invention, a brief explanation of the current ARQ and HARQ technologies will be given first.

[0055] ARQ is one of the basic functions of the RLC layer. Through the RLC layer's acknowledgment mode, it accumulates and monitors the sequence numbers of received and sent packets to retransmit lost or erroneous RLC Protocol Data Units (PDUs). In other words, it's a retransmission mechanism within the RLC layer. When an RLC PDU transmission fails, it sends an instruction to the lower layer (MAC layer). Based on the transmission resources indicated by the MAC instruction, a new MAC Service Data Unit (SDU) is constructed and sent to the lower layer for retransmission.

[0056] HARQ is a crucial and fundamental function of the MAC layer, reducing the average number of retransmissions by correcting frequently occurring errors. However, when lower-frequency errors are detected, the receiver requests retransmissions, each carrying the same or some redundant information to aid in packet detection. HARQ uses Forward Error Correction (FEC) to correct some errors at the receiver and relies on error detection to detect the remaining errors. Typically, Cyclic Redundancy Check (CRC) codes are used for error detection, and some form of FEC is used to correct transmission errors.

[0057] Typically, through multiple retransmissions using HARQ, the block error rate (BLER) can reach 10%. -3 The current level is sufficient to meet some business needs. However, some services, such as Voice over Internet Protocol (VoIP), have higher reliability requirements. By combining ARQ and HARQ at the RLC layer, 10000 RARQ can be achieved. -6 The above reliability ensures that business needs are met.

[0058] On the one hand, further improving the BLER of HARQ becomes more difficult. Referring to Table 1, if the ACK / NACK received by the sending HARQ process from the receiving HARQ process is incorrect, such as the receiving HARQ process returning NACK, the sending HARQ might mistakenly believe it has received an ACK and thus stop retransmission. When ARQ and HARQ coexist, ARQ can identify and complete retransmissions through data sorting and retransmission.

[0059] Table 1

[0060]

[0061]

[0062] However, since the RLC layer is above the MAC layer, and ARQ itself needs to wait for the RLC timer to complete before determining that the peer transmission has failed, the latency for the ARQ layer to determine packet mistransmission is often more than 10 times that of the MAC layer. Although the error rate is guaranteed, the response time is too long, making it difficult to meet the requirements of high-reliability, low-latency services. Therefore, existing technical solutions are insufficient to meet the requirements of high-reliability, low-latency services.

[0063] Based on this, embodiments of the present invention provide an information transmission method. Figure 1 This is a flowchart illustrating the information transmission method according to an embodiment of the present invention. Figure 1 ;like Figure 1 As shown, the method includes:

[0064] Step 101: When the first device determines that the first data received using the first process has not been successfully received and / or has not been successfully decoded, it sends a NACK message for the first data to the second device;

[0065] Step 102: When the first device receives the second data sent by the second device using the first process, it sends a first message to the second device. The first message indicates that the second device has made an incorrect acknowledgment of the NACK message for the first data. The first message is used to trigger the second device to retransmit the first data.

[0066] In this embodiment, the second device is a transmitting device, and the first device is a receiving device. In specific implementations, the second device can be a network device, and the first device can be a terminal device. In this case, the data sent from the second device to the first device (such as first data and second data) can be downlink data. Alternatively, the second device can be a terminal device, and the first device can be a network device. In this case, the data sent from the second device to the first device (such as first data and second data) can be uplink data. The network device can be an access network device, such as a base station. In other embodiments, the first device and the second device can also be any two devices using the HARQ mechanism for data transmission.

[0067] In this embodiment, the second device sends first data to the first device. The second device sends feedback messages to the first device based on the reception and / or decoding status. For example, if the first data is successfully received and / or successfully decoded, the first device sends an ACK message to the second device; if the first data is not successfully received and / or at least partially undecoded, the first device sends a NACK message to the second device. In conventional solutions, when the second device receives an ACK message for the first data, it releases the buffer used to cache the first data to allow for the transmission of new data. However, the second device may misjudge the situation, meaning it cannot accurately determine whether the first data needs to be retransmitted. There may be cases where data is not successfully received and / or at least partially undecoded, but is judged as successfully received (e.g., it is considered that an ACK message for the first data has been received). In such cases, the second device will consider the reception successful and release the buffer used to cache the first data. Therefore, using conventional solutions requires stopping and retransmitting, which significantly increases latency.

[0068] In this embodiment, if the first device (receiving device) receives new data (second data) after sending a corresponding NACK message for the received first data, it indicates that the second device has misinterpreted the NACK message from the first device; that is, the second device thought the first device had sent an ACK message. The first device then sends a first message to the second device, indicating that the second device has incorrectly acknowledged the NACK message for the first data. This first message triggers the second device to retransmit the first data. Upon receiving the first message, the second device can determine that the ACK message for the first data has been misinterpreted and needs to retransmit the first data.

[0069] In this embodiment, the first message may be another status feedback information that is different from the existing ACK message and NACK message. For example, it may be referred to as NNACK message, which indicates that the second device has made an incorrect acknowledgment of the ACK message for the first data, so as to prompt the second device to make an incorrect reception of the ACK for the first data.

[0070] By employing the technical solution of this invention, for the first device (i.e., the receiving device), after sending a corresponding NACK message for the received first data, receiving new data (second data) indicates that the second device has misjudged the NACK message fed back by the first device. The first device sends a first message to the second device to indicate the second device's incorrect acknowledgment of the NACK message for the first data. For the second device (the sending device), after receiving the ACK message for the first data, it does not immediately release the buffer of the first data. Instead, it sends new data (second data) and receives a feedback message for the second data, thereby determining that the first data was successfully received by the first device, that is, determining that the received ACK message for the first data was correctly understood. Based on the results of multiple verifications, it decides whether to release the buffer of the first data. On the one hand, this reduces the probability of the sending end "stopping retransmission" due to misjudgment, reduces data transmission latency, and improves data transmission reliability. On the other hand, it achieves error-free transmission over the air interface, improving the robustness of the air interface.

[0071] In some alternative embodiments, sending the first message to the second device includes: the first device sending the first message to the second device through resources indicated by Downlink Control Information (DCI); or, the first device sending the first message to the second device through resources indicated by License Configuration (CG).

[0072] In this embodiment, when the first device is a network device and the second device is a terminal device, and the first data and second data are uplink data, the first device can send the first message to the second device through the resources indicated by the DCI, or through the resources indicated by the CG. The second device receives the first message according to the indication of the DCI or CG. When the first device is a terminal device and the second device is a network device, and the first data and second data are downlink data, the first device can send the first message to the second device through the resources indicated by the DCI, or through the resources indicated by the CG. The second device receives the first message according to the configuration.

[0073] In some optional embodiments of the present invention, the method further includes: caching the first data in a first cache corresponding to the first process; and / or, if the second data is not successfully received and / or not successfully decoded, requesting a second cache corresponding to the first process and caching the second data in the second cache.

[0074] In this embodiment, when the first device receives the first data using the first process, and the first data is not successfully received and / or not successfully decoded, the first data can be cached in the first cache corresponding to the first process. If the first device receives the second data using the first process, the first device can request a new cache corresponding to the first process, denoted as the second cache, and cache the second data in the second cache.

[0075] In various embodiments of the present invention, a process (such as a first process, a second process, etc.) may refer to a HARQ process.

[0076] In conventional technical solutions, each process corresponds to a buffer; that is, one sending process corresponds to one sending buffer, and one receiving process corresponds to one receiving buffer. After the sending process finishes sending a TB, it receives the corresponding ACK and releases the buffer corresponding to that sending process. When a new TB needs to be sent, it sends the new TB based on the sending process, and the corresponding sending buffer holds the new TB. This approach has the following problem: if the ACK received by the sending HARQ process is a misjudgment, it indicates that the receiving end has not successfully received the TB or has not successfully decoded the TB, and the TB needs to be retransmitted. However, at this time, the sending buffer corresponding to the sending process has been released, and the corresponding TB no longer exists, so retransmission must be stopped, which greatly increases the data transmission latency. The receiving process at the receiving end works similarly.

[0077] In the technical solution of this invention, the sending and receiving processes can use more than one buffer simultaneously. The sending end (second device) buffers data through one sending buffer (such as the first buffer) of the second process. Even if an ACK corresponding to the data is received, the sending buffer (such as the first buffer) is not immediately released. When new data is transmitted, the new data is buffered by requesting another sending buffer (such as the second buffer) corresponding to the second process. Similarly, the receiving end (first device) buffers data through one receiving buffer of the first process. When new data is received, if there is data in the receiving buffer that was not successfully transmitted and / or at least partially undecoded, the new data is buffered by requesting another receiving buffer corresponding to the first process. In this way, for the sending end, a buffer can be used to cache the transmitted data, and a new buffer can be requested to cache the newly transmitted data. This avoids the "stop retransmission" situation caused by the release of the buffer due to misjudgment. New data can still be transmitted even when the transmission of the already transmitted data is not yet determined to be successful, which greatly reduces the data transmission latency. For the receiving end, multiple buffers can be used to cache the received data. This allows for the judgment of misjudgment of feedback messages (for example, if new data is received even after a NACK has been sent, it can be determined that the sending end has made a misjudgment). Furthermore, by using the method of requesting new buffers to cache new data, error-free transmission over the air interface is achieved, which improves the robustness of the air interface.

[0078] In some alternative embodiments, when the first device determines that the first data received using the first process has not been successfully received and / or has not been successfully decoded, the method further includes: the first device starting a timer;

[0079] Accordingly, when the first device receives the second data sent by the second device using the first process, it sends a first message to the second device, including: within the timer's timing range, if the first device receives the second data sent by the second device using the first process, it sends a first message to the second device.

[0080] In this embodiment, when the first device determines that the first data has not been successfully received and / or has not been successfully decoded, it may start a timer. Within the timer's time range, since the first device sends a NACK message for the first data to the second device, the first device may receive the first data retransmitted by the second device, or receive the second data, or still not receive the first data or the second data when the timer expires. Within the timer's timing range, if the first device receives the retransmitted first data using the first process, it indicates that the second device has successfully received the NACK message for the first data and retransmitted the first data based on the NACK message. If, within the timer's timing range, the first device does not receive the retransmitted first data from the second device, it indicates that the second device has not received the NACK message for the first data, or has misjudged the NACK message for the first data, mistaking it for an ACK message and believing that the first data has been successfully received. If, within the timer's timing range, the first device receives the second data sent by the second device, it indicates that the second device has misjudged the NACK message for the first data, mistaking it for an ACK message and believing that the first data has been successfully received, and there is currently a new data scheduling task, i.e., new data (i.e., the second data) being transmitted. In the last case, the first device receives the new data (i.e., the second data) and therefore sends the first message to the second device indicating the second device's erroneous acknowledgment of the NACK message for the first data, thereby triggering the second device to retransmit the first data.

[0081] Optionally, when the first device sends a first message to the second device, the method may further include: restarting the timer to trigger the timer to start counting again, so as to determine whether the retransmitted first data is received within the timer's counting range.

[0082] In some optional embodiments, after the first device receives the second data sent by the second device using the first process, the method further includes: the first device sending an ACK message or a NACK message to the second device for the second data based on the reception result and / or decoding result of the second data.

[0083] In this embodiment, if the second data is successfully received and / or successfully decoded, an ACK message is sent to the second device; if the second data is not successfully received and / or not successfully decoded, a NACK message is sent to the second device.

[0084] In some optional embodiments of the present invention, the method further includes: when the timer times out, if the first device does not receive the first data retransmitted by the second device, sending a NACK message to the second device for the first data.

[0085] In this embodiment, if the first device does not receive the first data resent by the second device when the timer expires, it indicates that the second device has not received the NACK message for the first data, and the first device resends the NACK message for the first data to the second device.

[0086] Based on the above embodiments, this invention also provides an information transmission method. Figure 2 This is a flowchart illustrating the information transmission method according to an embodiment of the present invention. Figure 2 ;like Figure 2 As shown, the method includes:

[0087] Step 201: When the second device receives the second message sent by the first device and determines that the second message is an ACK message for the first data, it does not release the cached first data; the first data is the data sent by the first device using the second process.

[0088] Step 202: The second device sends second data to the first device using the second process, and upon receiving a feedback message for the second data, determines to release the first data.

[0089] In this embodiment, the second device is a transmitting device, and the first device is a receiving device. In specific implementations, the second device can be a network device, and the first device can be a terminal device. In this case, the data sent from the second device to the first device (such as the first data) can be downlink data; or, conversely, the second device can be a terminal device, and the first device can be a network device. In this case, the data sent from the second device to the first device (such as the first data) can be uplink data. The network device can be an access network device, such as a base station. In other embodiments, the first device and the second device can also be any two devices using the HARQ mechanism for data transmission.

[0090] In this embodiment, the second device sends first data to the first device. The second device sends feedback messages to the first device based on the reception and / or decoding status. For example, if the first data is successfully received and / or successfully decoded, the first device sends an ACK message to the second device. If the first data is not successfully received and / or at least partially undecoded, the second device sends a NACK message to the first device. In conventional solutions, when the second device receives an ACK message for the first data, it releases the buffer used to cache the first data to allow for the transmission of new data. However, the second device may misinterpret a NACK as an ACK, meaning it cannot accurately determine whether the first data needs to be retransmitted. There may be cases where data is not successfully received and / or undecoded, but is judged as successfully received (e.g., it is considered that an ACK message for the first data has been received). In such cases, the second device will consider the reception successful and release the buffer used to cache the first data. Therefore, using conventional solutions, the untransmitted and / or undecoded data blocks (TBs) are deleted, requiring retransmission to stop, which significantly increases latency.

[0091] In the technical solution of this invention, after receiving the ACK message for the first data, the second device (sending device) does not immediately release the buffer of the first data. Instead, it sends new data (second data) and then receives a feedback message for the second data. This confirms that the first data was successfully received by the first device, that is, that the received ACK message for the first data was correctly understood. Based on the results of multiple verifications, it decides whether to release the buffer of the first data. On the one hand, this reduces the probability of the sending end "stopping retransmission" due to misjudgment, reduces the latency of data transmission, and improves the reliability of data transmission. On the other hand, it achieves error-free transmission over the air interface, improving the robustness of the air interface.

[0092] In this embodiment, the second message is the initial feedback message for the first data. As an example, if the first device successfully receives and / or decodes the first data, it sends an ACK message for the first data; correspondingly, the second device receives an ACK message. As another example, if the first device fails to receive and / or decode the first data, it sends a NACK message for the first data; the second device receives a NACK message that is correctly understood, or it may receive an ACK message that is misinterpreted as a NACK message. This embodiment mainly addresses the situation of misinterpretation of the NACK message in the second scenario.

[0093] In some alternative embodiments, before the second device receives the second message sent by the first device, the method further includes: the second device sending the first data to the first device using a second process, and caching the first data in a first cache corresponding to the second process.

[0094] In this embodiment, the second device uses a second process to send the first data and caches the first data in a first cache corresponding to the second process. Even if the second device receives an ACK message for the first data, the second device does not release the first data in the second cache.

[0095] Regarding the first scenario, since the second message is a genuine ACK message, meaning the first device successfully received the first data and / or successfully decoded it, and the second device also received the ACK message for the first data, after sending the second data using the second process and receiving the feedback message for the second data, it can be determined that the first data has been successfully received and / or successfully decoded by the first device. In other words, it can be determined that the ACK message for the first data received by the second device is correctly understood. At this point, the cache of the first data can be released, i.e., the first data can be deleted.

[0096] In the second scenario described above, since the second device assumes that the first data has been successfully received and / or decoded, it will not perform any operation on the first data (e.g., retransmission). When there is a scheduling task with new data, the second process will be used to send the new data (e.g., the second data). At this time, the first device waits for the retransmission of the first data. After a period of time without receiving the retransmitted first data and receiving the second data, the first device sends a first message. The first message indicates that the second device has made an incorrect acknowledgment of the NACK message for the first data.

[0097] In this embodiment, after the second device completes the first data transmission using the second process, it caches the first data in the first cache corresponding to the second process.

[0098] In some optional embodiments of the present invention, the method further includes: the second device receiving a first message for the first data and retransmitting the first data, wherein the first message indicates that the second device has made an erroneous acknowledgment of feedback information for the first data.

[0099] In this embodiment, after the second device sends the second data to the first device using the second process, it receives the first message sent by the first device. The first message indicates that the second device has made an incorrect confirmation of the feedback information for the first data, that is, it indicates that the second device has made an incorrect confirmation of the ACK message received in step 201. Then the second device resends the first data.

[0100] In some alternative embodiments, after the second device retransmits the first data, the method further includes: the second device receiving an ACK message for the first data and determining to release the first data.

[0101] In this embodiment, after the second device retransmits the first data, it receives an ACK message for the first data. The second device can then determine that the first data was successfully received by the first device based on the two received ACK messages, and the second device can then determine to release the first data.

[0102] In some alternative embodiments, the second device receiving the first message of the first data includes: the second device receiving the first message of the first data through a resource indicated by the DCI; or, the second device receiving the first message of the first data through a resource indicated by the authorization configuration (CG).

[0103] In this embodiment, when the first device is a network device and the second device is a terminal device, and the first data and second data are uplink data, the first device can send the first message to the second device through the resources indicated by the DCI, or through the resources indicated by the CG. The second device receives the first message according to the indication of the DCI or CG. When the first device is a terminal device and the second device is a network device, and the first data and second data are downlink data, the first device can send the first message to the second device through the resources indicated by the DCI, or through the resources indicated by the CG. The second device receives the first message according to the configuration.

[0104] In some optional embodiments of the present invention, after the second device receives a second message sent by the first device and determines that the second message is an ACK message for the first data, the method further includes: the second device requesting a second cache corresponding to the second process and migrating the first data from the first cache to the second cache.

[0105] In this embodiment, after the second device receives the ACK message for the first data, it retains the first data and requests the second cache corresponding to the second process, and migrates the data in the first cache to the second cache, that is, the first data is migrated from the first cache to the second cache.

[0106] In some alternative embodiments, after the second device receives the first message for the first data, the method further includes: the second device migrating the first data from the second cache to the first cache.

[0107] In this embodiment, after the second device receives the first message regarding the first data, indicating an ACK misunderstanding of the first message, the second device migrates the data from the second cache to the first cache, that is, the first data is moved from the second cache to the first cache, and the original data in the first cache is placed into the data queue to be sent. Thus, by first migrating the first data from the first cache to the second cache, and then, after determining that retransmission is needed, migrating it from the second cache back to the first cache, the accuracy of transmission can be improved.

[0108] The information transmission method of this invention will be described below with reference to specific examples. Taking the second device as the sending device and the first device as the receiving device as an example, the information transmission method may include:

[0109] Step 1: The receiving device receives the first data packet sent by the sending device through the first HARQ process. After verifying that the first data packet was received correctly according to the CRC check mechanism, it sends an ACK. If it is determined that the first data packet was not received correctly, it sends a NACK. If other data packets have been buffered in the first HARQ process, it indicates that the receiving device has received other data packets (e.g., the second data packet) before receiving the first data packet through the first HARQ process and has not received them successfully. In this case, the receiving device sends an NNACK (equivalent to the first message).

[0110] Step 2: The sending device receives feedback information, including the following situations:

[0111] Upon receiving an ACK, it indicates that the first data packet was successfully received, and the system is ready to send the next data packet or wait.

[0112] Upon receiving a NACK, it indicates that the first data packet was not successfully received, and preparations are made to resend the first data packet.

[0113] If NNACK is received, it indicates that the second data packet was not received successfully. The system will then prepare to resend the second data packet, and the first data packet will be discarded (or deleted) and needs to be resent.

[0114] Step 3: The receiving device receives the data packets sent by the sending device through the first HARQ process, and performs the following processing based on the feedback from Step 1:

[0115] Step 1 sends an ACK. If a new third data packet is received, it is received normally and feedback is sent, then return to step 1.

[0116] Step 1: Send ACK. If the received data is the first data packet, ignore this reception; return to Step 1.

[0117] Step 1 sends NACK; if the received data is a new third data packet, then sends NNACK in response; return to Step 1.

[0118] Step 1 sends NACK. If the received data is the first data packet, it is received normally and feedback is sent; return to step 1.

[0119] Step 1 sends NNACK. If the received data is the first data packet, it is received normally and feedback is sent; return to step 1.

[0120] Step 1 sends NNACK. If the received data is a new third data packet, then send NNACK back; return to step 1.

[0121] Figure 3 This is an interactive schematic diagram of the information transmission method according to an embodiment of the present invention; as shown below. Figure 3 As shown, the example uses a first device as the sending end and a second device as the receiving end. The first and second devices may include n HARQ processes, for example, P#0, ..., P#n. Each HARQ process may have a pre-defined buffer, for example, denoted as buffer #0. In this embodiment, both the first and second devices have a dynamic buffer function for HARQ processes, meaning that a new buffer can be dynamically requested when needed, and this dynamically requested buffer can be denoted as buffer #1. After buffer #1 is used up, it can also be dynamically released.

[0122] Specifically, the first device sends TB1 to the second device via HARQ process P#0, and TB1 is buffered in Buffer#0; the second device receives TB1 via HARQ process P#0, and TB1 is buffered in Buffer#0. However, if the second device finds that TB1 was not successfully received and / or decoded, it sends a NACK to the first device and starts a timer, waiting for the first device to retransmit TB1.

[0123] The following situations may exist for the message received by the first device:

[0124] 1. If a NACK is received, TB1 is resent and buffered in Buffer #0;

[0125] 2. Upon receiving an ACK, the first device may mistakenly assume that it has received the ACK corresponding to TB1 due to possible misjudgment or decoding / decoding errors. At this time, the first device does not release Buffer #0, but retains TB1 in Buffer #0; it moves the data TB1 in Buffer #0 to Buffer #1, and waits for the next TB to be sent.

[0126] Within the timing range of the second device's timer, the following situations may occur:

[0127] When the HARQ process P#0 of the first device needs to send TB2, it requests dynamic buffer Buffer#1, sends TB2 to the second device through HARQ process P#0, moves the data TB1 in Buffer#0 to Buffer#1, and caches TB2 through Buffer#0.

[0128] In the above situation, the second device had already sent the NACK corresponding to TB1, but still received new data (i.e. TB2) within the timer's timing range. The second device can determine that the first device has made a misjudgment, so it requests dynamic buffer #1, caches the received TB2 through buffer #1, and sends NNACK to the first device to indicate the incorrect acknowledgment of the NACK message for TB1; at the same time, it restarts the timer.

[0129] In this case, the first device receives NNACK and can know that there was a misjudgment of the previously received ACK for TB1, so it needs to retransmit TB1; move the data in Buffer #1 to Buffer #0, and set the data to be sent as a retransmission packet; put the original data TB2 in Buffer #0 into the data queue to be sent; and retransmit TB1 through the HARQ process P #0.

[0130] In addition, the second device may send feedback information to the first device based on the reception status and / or decoding status of TB2; for example, if reception is successful and / or decoding is successful, it sends an ACK for TB2 to the first device; if reception is unsuccessful and / or at least partial decoding is unsuccessful, it sends a NACK for TB2 to the first device.

[0131] If the first device's HARQ process P#0 has no new data to send, and the second device does not receive the retransmission data of TB1 when the timer expires, it will resend a NACK for TB1. After waiting for the retransmission of TB1, the timer will be restarted until the first device receives the NACK for TB1 and then resends TB1 to the second device through the HARQ process P#0.

[0132] The second device receives the retransmitted TB1, buffers TB1 in Buffer #0, replaces the first received TB1, and sends feedback information to the first device based on the reception status and / or decoding status. For example, if reception and / or decoding are successful, it sends an ACK for TB1 to the first device; if reception is unsuccessful and / or at least partial decoding is unsuccessful, it sends a NACK for TB1 to the first device. The first device performs corresponding processing based on the second feedback message for TB1. For example, if the second feedback message is ACK, it releases Buffer #0; if the second feedback message is NACK, it sends TB1 to the second device again through the HARQ process P #0.

[0133] Based on the above embodiments, this invention also provides an information transmission device, which is applied to a first device. Figure 4 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of the present invention. Figure 1 ;like Figure 4 As shown, the device includes: a first processing unit 31 and a first communication unit 32; wherein,

[0134] The first processing unit 31 is used to determine whether the first data received by the first process was successfully received and / or successfully decoded;

[0135] The first communication unit 32 is configured to send a NACK message for the first data to the second device when the first processing unit 31 determines that the first data received by the first process was not successfully received and / or not successfully decoded; and is further configured to send a first message to the second device when the first process receives the second data sent by the second device, the first message indicating that the second device has made an incorrect acknowledgment of the NACK message for the first data, and the first message is used to trigger the second device to retransmit the first data.

[0136] In some optional embodiments of the present invention, the first processing unit 31 is further configured to cache the first data in a first cache corresponding to the first process; and / or, further configured to request a second cache corresponding to the first process and cache the second data in the second cache if the second data is not successfully received and / or not successfully decoded.

[0137] In some optional embodiments of the present invention, the first processing unit 31 is further configured to start a timer when it is determined that the first data received by the first process has not been successfully received and / or has not been successfully decoded;

[0138] The first communication unit 32 is used to send a first message to the second device when the first process receives the second data sent by the second device within the timing range of the timer.

[0139] In some optional embodiments of the present invention, the first communication unit 32 is further configured to send a NACK message to the second device for the first data if the first data retransmitted by the second device is not received when the timer times out.

[0140] In some alternative embodiments of the present invention, the first communication unit 32 is configured to send the first message to the second device via a resource indicated by the DCI; or, to send the first message to the second device via a resource indicated by the authorization configuration (CG).

[0141] In this embodiment of the invention, the first processing unit 31 in the device can be implemented by a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU), or a field-programmable gate array (FPGA) in practical applications; the first communication unit 32 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and a transceiver antenna in practical applications.

[0142] This invention also provides an information transmission device, which is applied to a second device. Figure 5 This is a schematic diagram of the composition structure of the information transmission device according to an embodiment of the present invention. Figure 2 ;like Figure 5 As shown, the device includes: a second communication unit 41 and a second processing unit 42; wherein,

[0143] The second communication unit 41 is used to receive a second message sent by the first device;

[0144] The second processing unit 42 is configured to, when determining that the second message is an ACK message for the first data, not release the cached first data; the first data is data sent by the first device using the second process;

[0145] The second communication unit 41 is further configured to send second data to the first device using the second process, and receive feedback messages for the second data;

[0146] The second processing unit 42 is further configured to determine to release the first data when the second communication unit receives a feedback message for the second data.

[0147] In some optional embodiments of the present invention, the second communication unit 41 is further configured to receive a first message for the first data and resend the first data, wherein the first message indicates that the second device has made an erroneous confirmation of the feedback information for the first data.

[0148] In some optional embodiments of the present invention, the second communication unit 41 is further configured to send the first data to the first device using a second process before receiving the second message sent by the first device;

[0149] The second processing unit 42 is further configured to cache the first data in the first cache corresponding to the second process.

[0150] In some optional embodiments of the present invention, the second processing unit 42 is further configured to receive a second message sent by the first device through the second communication unit 41, and after determining that the second message is an ACK message for the first data, apply for a second cache corresponding to the second process and migrate the first data from the first cache to the second cache.

[0151] In some optional embodiments of the present invention, the second communication unit 41 is further configured to receive a feedback message for the first data after retransmitting the first data;

[0152] The second processing unit 42 is further configured to, upon receiving an ACK message for the first data from the second communication unit 41, determine to release the first data.

[0153] In some optional embodiments of the present invention, the second communication unit 41 is configured to receive the third message sent by the first device through a resource indicated by DCI; or, to receive the third message sent by the first device through a resource indicated by authorization configuration (CG).

[0154] In this embodiment of the invention, the second processing unit 42 in the device can be implemented by a CPU, DSP, MCU or FPGA in practical applications; the second communication unit 41 in the device can be implemented by a communication module (including: basic communication kit, operating system, communication module, standardized interface and protocol, etc.) and transceiver antenna in practical applications.

[0155] It should be noted that the information transmission device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the information transmission device and the information transmission method embodiments provided in the above embodiments belong to the same concept, and their specific implementation process can be found in the method embodiments, which will not be repeated here.

[0156] This invention also provides a communication device, which is either the first device or the second device described in the foregoing embodiments. Figure 6 This is a schematic diagram of the hardware composition structure of the communication device according to an embodiment of the present invention, such as... Figure 6 As shown, the communication device includes a memory 52, a processor 51, and a computer program stored in the memory 52 and executable on the processor 51. When the processor 51 executes the program, it implements the steps of the information transmission method of the present invention applied to the first device or the second device.

[0157] Optionally, the communication device also includes at least one network interface 53. The various components of the communication device are coupled together via a bus system 54. It is understood that the bus system 54 is used to implement communication between these components. In addition to a data bus, the bus system 54 also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 6 The general labeled all buses as Bus System 54.

[0158] It is understood that memory 52 can be volatile memory or non-volatile memory, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), magnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memory 52 described in this embodiment of the invention is intended to include, but is not limited to, these and any other suitable types of memory.

[0159] The methods disclosed in the above embodiments of the present invention can be applied to processor 51, or implemented by processor 51. Processor 51 may be an integrated circuit chip with signal processing capabilities. In the implementation process, each step of the above method can be completed by the integrated logic circuit of the hardware in processor 51 or by instructions in the form of software. The processor 51 may be a general-purpose processor, DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Processor 51 can implement or execute the methods, steps and logic block diagrams disclosed in the embodiments of the present invention. The general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of the present invention can be directly manifested as being executed by a hardware decoding processor, or being executed by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory 52. ​​Processor 51 reads the information in memory 52 and completes the steps of the aforementioned method in combination with its hardware.

[0160] In an exemplary embodiment, the communication device may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), FPGAs, general-purpose processors, controllers, MCUs, microprocessors, or other electronic components to perform the aforementioned method.

[0161] In an exemplary embodiment, the present invention also provides a computer-readable storage medium, such as a memory 52 including a computer program, which can be executed by a processor 51 of a communication device to perform the steps described in the foregoing method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM; or it may be various devices including one or any combination of the above-mentioned memories.

[0162] The computer-readable storage medium provided in the embodiments of the present invention stores a computer program thereon, which, when executed by a processor, implements the steps of the information transmission method of the embodiments of the present invention applied to a first device or a second device.

[0163] This application also provides a computer program product, including a computer program that can be executed by a communication node (such as the processor 51 of a communication device) to complete the steps of any of the aforementioned information transmission methods.

[0164] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0165] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0166] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0167] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0168] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0169] In addition, in the various embodiments of the present invention, each functional unit can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0170] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0171] Alternatively, if the integrated units of this invention are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this invention, or the parts that contribute to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the methods described in the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0172] The above description is merely a specific embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. An information transmission method, characterized in that, The method is applied to a first device, and the method includes: When the first device determines that the first data received using the first process has not been successfully received and / or has not been successfully decoded, it sends a NACK message for the first data to the second device. When the first device receives the second data sent by the second device using the first process, it sends a first message to the second device. The first message indicates that the second device has made an incorrect confirmation of the feedback information regarding the first data. The first message is used to trigger the second device to retransmit the first data. The method further includes: The first data is cached in the first cache corresponding to the first process; and / or, If the second data is not successfully received and / or not successfully decoded, the second cache corresponding to the first process is requested, and the second data is cached in the second cache.

2. The method according to claim 1, characterized in that, When the first device determines that the first data received using the first process was not successfully received and / or not successfully decoded, the method further includes: The first device starts the timer; When the first device receives the second data sent by the second device using the first process, it sends a first message to the second device, including: Within the timer's timing range, if the first device receives the second data sent by the second device using the first process, it sends a first message to the second device.

3. The method according to claim 2, characterized in that, The method further includes: When the timer expires, if the first device does not receive the first data retransmitted by the second device, it sends a NACK message to the second device regarding the first data.

4. The method according to claim 1, characterized in that, Sending the first message to the second device includes: The first device sends the first message to the second device via the resources indicated by the downlink control information (DCI); or... The first device sends the first message to the second device by authorizing the resources indicated by the configuration CG.

5. An information transmission method, characterized in that, The method is applied to a second device, and the method includes: When the second device receives a second message sent by the first device and determines that the second message is an ACK message for the first data, it does not release the cached first data; the first data is data sent by the first device using the second process. The second device sends second data to the first device using the second process, and upon receiving a feedback message regarding the second data, determines to release the first data.

6. The method according to claim 5, characterized in that, The method further includes: The second device receives a first message regarding the first data and retransmits the first data. The first message indicates that the second device has incorrectly acknowledged the feedback information regarding the first data.

7. The method according to claim 5 or 6, characterized in that, Before the second device receives the second message sent by the first device, the method further includes: The second device uses a second process to send the first data to the first device and caches the first data in the first cache corresponding to the second process.

8. The method according to claim 7, characterized in that, After the second device receives a second message sent by the first device and determines that the second message is an ACK message for the first data, the method further includes: The second device requests the second cache corresponding to the second process and migrates the first data from the first cache to the second cache.

9. The method according to claim 8, characterized in that, After the second device receives the first message regarding the first data, the method further includes: The second device migrates the first data from the second cache to the first cache.

10. The method according to claim 6, characterized in that, After the second device retransmits the first data, the method further includes: The second device receives an ACK message for the first data and determines to release the first data.

11. The method according to claim 6, characterized in that, The second device receives a first message regarding the first data, including: The second device receives a first message for the first data via resources indicated by downlink control information (DCI); or, The second device receives a first message for the first data through the resources indicated by the authorized configuration CG.

12. An information transmission device, characterized in that, The device is applied to a first equipment, and the device includes: a first processing unit and a first communication unit; wherein... The first processing unit is used to determine whether the first data received by the first process was successfully received and / or successfully decoded; The first communication unit is configured to send a NACK message for the first data to the second device when the first processing unit determines that the first data received by the first process has not been successfully received and / or has not been successfully decoded; and is further configured to send a first message to the second device when the first process receives the second data sent by the second device, the first message indicating that the second device has made an incorrect acknowledgment of the NACK message for the first data, and the first message is used to trigger the second device to retransmit the first data. The first processing unit is further configured to cache the first data in a first cache corresponding to the first process; and / or, further configured to request a second cache corresponding to the first process and cache the second data in the second cache if the second data is not successfully received and / or not successfully decoded.

13. An information transmission device, characterized in that, The device is applied to a second equipment, and the device includes: a second communication unit and a second processing unit; wherein... The second communication unit is used to receive a second message sent by the first device; The second processing unit is configured to, when determining that the second message is an ACK message for the first data, not release the cached first data; the first data is data sent by the first device using the second process; The second communication unit is further configured to send second data to the first device using the second process, and receive feedback messages for the second data; The second processing unit is further configured to determine to release the first data when the second communication unit receives a feedback message for the second data.

14. A computer-readable storage medium having a computer program stored thereon, characterized in that, When executed by a processor, the program implements the steps of the method according to any one of claims 1 to 4; or, when executed by a processor, the program implements the steps of the method according to any one of claims 5 to 11.

15. A communication device, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the method according to any one of claims 1 to 4; or, when the processor executes the program, it implements the steps of the method according to any one of claims 5 to 11.

16. A computer program product, characterized in that, It includes computer program instructions that cause a computer to perform the steps of the method according to any one of claims 1 to 4; or, the computer program instructions cause a computer to perform the steps of the method according to any one of claims 5 to 11.

Images