Data transmission method and device and storage medium

Abstract

The invention discloses a data transmission method and device and a storage medium, relates to the technical field of communication, and can reduce the situation of wireless link failure caused by misjudgment of new transmission and retransmission, improve the communication reliability, shorten the service interruption time and improve the user experience. The method comprises the following steps: receiving first scheduling information of an HARQ process; and when the first scheduling information satisfies a retransmission scheduling condition and the time for receiving the first scheduling information or the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, performing data retransmission by using the HARQ process.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a data transmission method, device, and storage medium. Background Art

[0002] Hybrid automatic repeat request (HARQ) improves the reliability of data transmission by using two technologies: automatic repeat request (ARQ) and forward error correction (FEC). During the transmission process, if the data receiving end detects that the data packet is erroneous, it uses FEC technology to correct the error; for errors that cannot be corrected by FEC technology, a retransmission request will be sent to the data sending end to enable the sending end to retransmit the data packet.

[0003] In related technologies, in order to distinguish between newly transmitted data and retransmitted data, when sending data, the data transmitter defines whether the value of the new data indicator (NDI) is flipped to indicate whether the data transmission is new data to the data receiver. However, in the scenario of continuous DCI missed detection, relying solely on NDI flipping to indicate whether it is new data is prone to misjudgment, resulting in wireless link failure. Summary of the invention

[0004] The embodiments of the present application provide a data transmission method, device and storage medium, which can reduce the wireless link failure caused by new transmission and retransmission misjudgment, improve communication reliability, shorten service interruption time, and improve user experience.

[0005] In a first aspect, a data transmission method is provided, the method comprising: receiving first scheduling information of a HARQ process; using the HARQ process to retransmit data when the first scheduling information meets a retransmission scheduling condition and the time of receiving the first scheduling information is within the life cycle of the HARQ process.

[0006] Based on the first aspect method, the embodiment of the present application defines the life cycle of HARQ. When the received first scheduling information meets the retransmission scheduling condition, it is determined whether the time of receiving the first scheduling information is within the life cycle of HARQ; if so, the HARQ process is used to retransmit the data; in this way, in the scenario of continuous DCI missed detection, the wireless link failure caused by new transmission and retransmission misjudgment can be reduced, the communication reliability can be improved, the service interruption time can be shortened, and the user experience can be improved.

[0007] In a possible design, the method further includes: if the first scheduling information satisfies the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, refusing to execute the first scheduling information. It can be understood that if the time when the terminal receives the first scheduling information exceeds the life cycle of the HARQ process, it means that the HARQ process has been revoked and the HARQ process cannot be used for data retransmission, then the terminal can choose to refuse to execute the first scheduling information.

[0008] In a possible design, the method further includes: when the first scheduling information satisfies the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, using the HARQ process for new data transmission. It can be understood that if the time when the terminal receives the first scheduling information exceeds the life cycle of the HARQ process, it means that the HARQ process has been revoked and the HARQ process cannot be used for data retransmission, then the terminal can choose to use the HARQ process for new data transmission.

[0009] In one possible design, the first scheduling information satisfies the retransmission scheduling condition, including: determining that the new transmission identifier carried by the first scheduling information has not flipped. It can be understood that in order to distinguish between new transmission data and retransmission data, the terminal / access network device indicates whether the transmitted data is new data by defining whether the value of NDI is flipped. Therefore, if the NDI carried by the first scheduling information has not flipped, the terminal determines that the first scheduling information meets the retransmission scheduling condition.

[0010] In one possible design, the first scheduling information satisfying the retransmission scheduling condition further includes at least one of the following:

[0011] The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transport block size calculated based on the MCS index value is the same as the transport block size of the last new data transmitted by the HARQ process;

[0012] The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transport block size calculated based on the MCS index value is larger than the transport block size of the last newly transmitted data of the HARQ process;

[0013] The modulation and coding scheme MCS index value indicated by the first scheduling information is not within the preset interval.

[0014] It can be understood that the data retransmitted each time in the HARQ process can be the same as the newly transmitted data, or padding information can be added to the newly transmitted data; and the RV version of each retransmission can be the same or different. Therefore, regardless of whether the amount of data changes, the transmission block size calculated according to the MCS index value indicated by the first scheduling information should not be less than the transmission block size of the last newly transmitted data of the HARQ process. Therefore, in an embodiment of the present application, when the transmission block size calculated according to the MCS index value indicated by the first scheduling information is greater than or equal to the transmission block size of the last newly transmitted data of the HARQ process, it is determined that the first scheduling information meets the retransmission condition.

[0015] Among them, when the MCS index value indicated by the first scheduling information is not within the preset interval, the target code rate (Target code Rate) corresponding to the MCS index is invalid. Therefore, the size of the transmission block cannot be determined, and the first scheduling information meets the retransmission condition.

[0016] In one possible design, the above-mentioned preset interval is the MCS index value interval required to calculate the transmission block size.

[0017] In one possible design, the time for receiving the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for receiving the first scheduling information and the time for last receiving the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time for receiving the first scheduling information and the time for last receiving the scheduling information indicating new transmission data of the HARQ process is less than the life cycle of the HARQ process.

[0018] It can be understood that if the time interval between the time when the first scheduling information received by the terminal and the time of the second scheduling information of the HARQ process is greater than the life cycle of the HARQ process, it means that the retransmission indicated by the first scheduling information and the new transmission / retransmission indicated by the second scheduling information are too long apart, which may be due to the misjudgment of the new transmission and retransmission caused by DCI missed detection; similarly, if the time interval between the time when the first scheduling information received by the terminal and the time when the scheduling information indicating the new transmission data of the HARQ process was last received is greater than the life cycle of the HARQ process, it means that the scheduling information indicating the new transmission data and the retransmission indicated by the first scheduling information are too long apart, which may be due to the misjudgment of the new transmission and retransmission caused by DCI missed detection. Therefore, corresponding measures can be taken for the first scheduling information (for example, refusing to execute the first scheduling information or sending the first scheduling information as a new transmission) to avoid wireless link failure and improve communication reliability.

[0019] In one possible design, the time when the first scheduling information is received is within the life cycle of the HARQ process, including: the time interval between the time when the first scheduling information is received and the time when data is transmitted based on the last receipt of the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time when the first scheduling information is received and the last time the HARQ process transmitted new data is less than the life cycle of the HARQ process.

[0020] It is understandable that the time when the terminal receives the second scheduling information may be different from the time when the terminal transmits data based on the second scheduling information. Therefore, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal receives the first scheduling information and the time when the terminal transmits data based on the last time it received the second scheduling information of the HARQ process.

[0021] Similarly, the time when the terminal last received scheduling information indicating new data transmission of the HARQ process may be different from the time when the terminal's HARQ process last transmitted new data. Therefore, the embodiment of the present application can also determine whether the time when the terminal receives the first scheduling information is within the life cycle of the HARQ process based on the time when the HARQ process last transmitted new data and the time when the terminal received the first scheduling information.

[0022] In one possible design, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time when the second scheduling information of the HARQ process was last received is less than the life cycle of the HARQ process; or, the time interval between the time for transmitting data based on the first scheduling information and the time when the scheduling information indicating new transmission data of the HARQ process was last received is less than the life cycle of the HARQ process.

[0023] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the terminal last received the second scheduling information of the HARQ process, or the time when the terminal last received the scheduling information indicating new transmission data of the HARQ process.

[0024] In one possible design, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time for transmitting data based on the last receipt of the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time for transmitting data based on the first scheduling information and the last time the HARQ process transmitted new data is less than the life cycle of the HARQ process.

[0025] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the terminal transmits data based on the last received second scheduling information of the HARQ process, or the last time the HARQ process transmitted new data.

[0026] In one possible design, the method further includes: sending first information, the first information being used to indicate the maximum duration of the supported life cycle. It is understandable that the terminal can send the maximum duration of the life cycle supported by the terminal to the access device, and then the access network device determines the actual duration of the life cycle based on the maximum duration of the life cycle supported by the terminal.

[0027] In one possible design, the method also includes: receiving second information, where the second information is used to configure the actual duration of the life cycle.

[0028] It is understandable that the terminal can interact with the access network equipment to negotiate the actual duration of the life cycle. In this way, it can reduce the probability of new transmission and retransmission misjudgment in continuous DCI missed detection scenarios, reduce wireless link failures caused by erroneous data transmission, improve communication reliability, shorten service interruption time, and improve user experience.

[0029] In one possible design, the method further includes: determining different life cycles based on different business scenarios; wherein different business scenarios correspond to different signal-to-noise ratios; and different business scenarios include at least one of the following: non-high-speed rail scenarios and high-speed rail scenarios. It can be understood that in the data transmission method provided in the embodiment of the present application, the terminal can customize the life cycle of the HARQ process without negotiating with the access network device. In addition, due to different signal-to-noise ratios, the corresponding signal quality is different, and therefore the length of the corresponding HARQ process life cycle is also different. Therefore, in the embodiment of the present application, the terminal can determine the length of the life cycle of the HARQ process based on the signal-to-noise ratio corresponding to the business scenario of the HARQ process application.

[0030] In a possible design, the units of the life cycle include: symbols or time slots.

[0031] In a second aspect, a communication device is provided for implementing the above-mentioned various methods. The communication device includes a module, unit, or means corresponding to the above-mentioned method, and the module, unit, or means can be implemented by hardware, software, or by hardware executing the corresponding software. The hardware or software includes one or more modules or units corresponding to the above-mentioned functions.

[0032] In some possible designs, the communication device may include a transceiver module and a processing module. The transceiver module, which may also be referred to as a transceiver unit, is used to implement the sending and / or receiving functions in the above-mentioned first aspect and any possible implementation thereof. The transceiver module may be composed of a transceiver circuit, a transceiver, a transceiver or a communication interface. The processing module may be used to implement the processing functions in the above-mentioned first aspect and any possible implementation thereof.

[0033] In some possible designs, the transceiver module includes a sending module and a receiving module, which are respectively used to implement the sending and receiving functions in the above-mentioned first aspect and any possible implementation methods thereof.

[0034] Among them, the communication device provided in the third aspect is used to execute the above-mentioned first aspect or any possible implementation method of the first aspect. The specific details can be found in the above-mentioned first aspect or any possible implementation method of the first aspect, and will not be repeated here.

[0035] In a third aspect, a communication device is provided for implementing the above-mentioned various methods. The communication device comprises: a processor and a memory; the memory is used to store computer instructions, and when the processor executes the instructions, the communication device executes the above-mentioned method in the first aspect.

[0036] In some possible designs, the communication device may include: a processor and a communication interface; the communication interface is used to communicate with a module outside the communication device; the processor is used to execute a computer program or instructions so that the communication device performs the method described in the first aspect above.

[0037] In a fourth aspect, the present application provides a computer-readable storage medium storing computer instructions, which, when the computer instructions are executed on a computer, enable the computer to execute the cell switching method in the first aspect or any possible design of the first aspect, or enable the computer to execute the data transmission method in the second aspect or any possible design of the second aspect.

[0038] In a fifth aspect, the present application provides a computer program product, which includes computer instructions. When the computer instructions are executed on a computer, the computer executes the cell switching method in the first aspect or any possible design of the first aspect, or the computer executes the data transmission method in the second aspect or any possible design of the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0039] Figure 1 This is a schematic diagram of the order in which redundant versions are used;

[0040] Figure 2 A schematic diagram of data transmission;

[0041] Figure 3 A schematic diagram of the time interval between two data transmissions;

[0042] Figure 4 A schematic diagram of DCI missed detection is shown;

[0043] Figure 5 A schematic diagram of the architecture of a communication system provided for this application;

[0044] Figure 6 A schematic diagram of the structure of an access network device and a terminal provided for this application;

[0045] Figure 7 A flowchart of a data transmission method provided by this application;

[0046] Figure 8 A flowchart of a data transmission method provided by this application;

[0047] Fig. 9 A flowchart of a data transmission method provided by this application;

[0048] Fig.10 A schematic diagram of the life cycle of a HARQ process provided by the present application;

[0049] Fig.11 A schematic diagram of the life cycle of a HARQ process provided by the present application;

[0050] Fig.12 A schematic diagram of the life cycle of a HARQ process provided by the present application;

[0051] Fig.13 A schematic diagram of the life cycle of a HARQ process provided by the present application;

[0052] Fig.14 A flowchart of a data transmission method provided by this application;

[0053] Fig.15 A schematic diagram of the structure of a communication device provided in this application. DETAILED DESCRIPTION

[0054] Before introducing the embodiments of the present application, some technical terms involved in the embodiments of the present application are explained. It should be noted that the following explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection required by the embodiments of the present application.

[0055] HARQ is a technology that combines ARQ and FEC, which can effectively combat the impact of wireless channel fading and ensure the reliability and efficiency of data transmission. Specifically, during the transmission process, if the data receiving end detects that the data packet is incorrect, it can use FEC technology to correct the error to ensure the correctness of the data, thereby reducing the number of retransmissions. For errors that cannot be corrected by FEC technology, the data receiving end can use ARQ technology to send a retransmission request to the data sending end so that the data sending end resends the data packet.

[0056] NR's HARQ supports an incremental retransmission mechanism, that is, each retransmission does not need to be the same as the initial transmission, only the lost data packets need to be retransmitted. The data receiving end will save the received erroneous data packets in a HARQ buffer and merge them with the subsequently received retransmitted data packets to obtain a more reliable data packet than decoding alone.

[0057] At the same time, the data transmitter generates multiple sets of coded bits each time it retransmits, and each set carries the same information (the coded bit set generated for each retransmission is different). The coded bit set generated for each retransmission is called a redundancy version (RV). The data transmitter can skip the initial retransmission in the order of RV=0 / 2 / 3 / 1. For example, Figure 1As shown, when RV is used, there is a set of available RVs, such as {0, 2, 3, 1}, and different redundant versions are represented by using the elements in the set in sequence. For a data packet, the first transmission is called "new transmission data", and the "new transmission data" uses the redundant version of RV=0. If this data packet is not correctly received by the data receiving end and needs to be retransmitted, we call it "retransmitted data". During the first retransmission, the redundant information value is increased, and the redundant version value RV=2 used by the "retransmitted data" is increased; if it has not been correctly received by the data receiving end and needs to be retransmitted, then during the second retransmission, the redundant information value is continued to be increased, and the redundant version value RV=3 used by the "retransmitted data" is used; similarly, if retransmission is still required, during the third retransmission, the redundant information value is continued to be increased, and the redundant version value RV=1 used by the "retransmitted data" is used; thereafter, during the fourth and subsequent retransmissions, the redundant version value RV=1 used by the "retransmitted data". In addition, in the prior art, the same HARQ process may also use RV=0 for data of the same content multiple times. In summary, from the first transmission to each retransmission, the order of using RVs may be: 0, 2, 3, 1, 0, 2, 3, 1, ...

[0058] In order to distinguish between new data and retransmitted data, the data sender indicates to the data receiver whether the data transmission is new data by defining whether the value of NDI is flipped when sending data. NDI has only 1 bit, so it has only 2 values: 0 and 1. The value of NDI is changed when new data is transmitted, and the value of NDI is not changed when data is retransmitted. For example, when the data sender transmits the first new data, NDI is 0; when the second new data is transmitted, NDI is 1; when the third new data is transmitted, NDI is 0; and NDI is used in this order. When retransmitting data, the NDI remains unchanged, that is, when the first new data is retransmitted (i.e., the retransmitted data of the first new data), whether it is the first retransmission or the subsequent retransmission, the NDI remains unchanged, and the value is 0, the same as the first new data; when the second new data is retransmitted (i.e., the retransmitted data of the second new data), whether it is the first retransmission or the subsequent retransmission, the NDI remains unchanged, and the value is 1, the same as the second new data; when the third new data is retransmitted (i.e., the retransmitted data of the third new data), whether it is the first retransmission or the subsequent retransmission, the NDI remains unchanged, and the value is 0, the same as the third new data. That is, the NDI of the first transmission data and the retransmitted data of the same data remains unchanged.

[0059] In some embodiments, when receiving data, the data receiving end decodes and verifies the data, and sends an acknowledgment (ACK) signal to the data sending end after the verification is successful; if the verification fails, a negative acknowledgement (NACK) signal is sent to the data sending end. Exemplarily, the data receiving end can use a cyclic redundancy check (CRC) technology to verify the received data.

[0060] For example, Figure 2 As shown, assuming that the initial value of NDI is 0, when the data sending end sends a new data transmission block (Transport Block, TB) 1 (new transmission of TB1), the value of NDI is 0. If the data receiving end receives successfully, it determines that TB1 is new data according to the value of NDI, and sends an ACK signal to the data sending end; accordingly, after receiving the ACK signal, the data sending end starts to send new data TB2 (new transmission of TB2) and changes the value of NDI to 1. If the data receiving end fails to receive (that is, TB2 is not received), no feedback is given to the data sending end; accordingly, if the data sending end does not receive feedback within the preset time period, TB2 is retransmitted without changing the value of NDI (that is, NDI The value of NDI is still 1); accordingly, when the data receiving end receives TB2, it determines that TB2 is new data according to the value of NDI (because the value of NDI received by the data receiving end last time is 0, so the value of NDI is flipped, thereby confirming that TB2 is new data), and then sends an ACK signal to the data sending end; accordingly, after receiving the ACK signal, the data sending end starts to send new data TB3 (new transmission of TB3) and changes the value of NDI to 0. If the data receiving end receives successfully, it determines that TB3 is new data according to the value of NDI, and sends an ACK signal to the data sending end.

[0061] New data: refers to data with new original content. Different new data carry different original content. For example, the original content carried by the first new data and the second new data is different.

[0062] Newly transmitted data and retransmitted data: When new data is sent for the first time, it is called newly transmitted data (or first transmitted data, initial transmitted data, etc.); when it is sent for the second time and subsequently, it is called retransmitted data; the original content carried by the newly transmitted data and the retransmitted data is the same. For example, when the first new data is sent for the first time, it is called newly transmitted data; when the first new data is sent for the second time, it is called retransmitted data; the original content carried by the newly transmitted data and the retransmitted data is the same, both of which are the original content of the first new data.

[0063] Data retransmission: refers to data that is not transmitted for the first time, and the transmitted data is historical data that has been transmitted before the HARQ process. It should be noted that the definition of data retransmission is different in the uplink node and the downlink node. For example, for the uplink node, data retransmission refers to sending retransmission data, that is, sending historical data that has been transmitted before the HARQ process; for the downlink node, data retransmission refers to receiving retransmission data, and combining and decoding the received retransmission data with the transmission block that has been received before the HARQ process.

[0064] New data transmission: refers to the first transmission of data, and the transmitted data is data that has not been transmitted before the HARQ process. It should be noted that the definition of new data transmission is different in the uplink node and the downlink node. For example, for the uplink node, new data transmission refers to the sending of new data, that is, the sending of new data that has not been transmitted before the HARQ process; for the downlink node, new data transmission refers to the reception of new data, and the combination and decoding of the received new data with the transmission block received before the HARQ process.

[0065] Downlink control information (DCI) is used to carry the control scheduling information of the physical uplink control channel (PUSCH) and the physical downlink shared channel (PDSCH). The DCI information includes resource block (RB) resource allocation information, modulation and coding scheme (MCS), HARQ session identification (ID) and other information.

[0066] In some embodiments, when the DCI includes the values ​​of the HARQ ID and the DNI, after receiving the DCI sent by the DCI sending end, the DCI receiving end may retransmit the data according to the instruction of the DCI.

[0067] It should be noted that the data transmitter and the data receiver mentioned in the embodiments of the present application are two communication nodes that send and receive data. The DCI transmitter and the DCI receiver are two communication nodes that send and receive DCI. Among them, the data transmitter is not necessarily a DCI transmitter; the data receiver is not necessarily a DCI receiver. Exemplarily, taking the two communication nodes as an access network device and a terminal or user equipment (UE), the UE can be a data transmitter, the access network device can be a data receiver, the access network device is a DCI transmitter, and the UE is a DCI receiver.

[0068] In some embodiments, taking the DCI transmitter as an access network device and the receiver as a UE as an example, in actual data transmission, the UE may miss detecting the DCI sent by the access network device through the PDCCH. For example, the access network device sends a certain DCI to the UE, but the UE does not receive the DCI, resulting in missed detection of the DCI.

[0069] like Figure 3 As shown, if the DCI indicating retransmission is missed, the time difference between the new transmission and retransmission of the same HARQ may be large. In the acknowledged mode (AM) of the Radio Link Control (RLC) layer, the data receiving end (e.g., access network equipment) will reply the sequence number (SN) of the data to the data sending end (e.g., UE) after decoding correctly. However, due to the large time difference between the new transmission and the retransmission, the SN may no longer be in the SN valid window of the RLC of the data sending end (e.g., UE). Therefore, the data sending end (e.g., UE) may determine that an abnormality has occurred, resulting in a failure of the wireless link.

[0070] Exemplary scenarios in which missed detection of a DCI indicating retransmission results in a large time difference between a new transmission and a retransmission of the same HARQ include:

[0071] Scenario 1: Dual cards occupy the RF path, resulting in DCI missed detection.

[0072] Specifically, Figure 4 As shown in the figure, when a UE includes two cards, one of the cards occupies the radio frequency path resources, resulting in the other card's downlink path continuously not receiving DCI. After stopping the occupancy of the radio frequency path resources, the UE receives DCI, which indicates that a certain HARQ is sent by PUSCH. According to the HARQ ID and NDI, the HARQ is a retransmission, and the time difference between the retransmission and the new transmission is large. However, in fact, the NDI continuously flipped between the two schedulings due to the continuous missed detection of DCI, and in fact, the two schedulings were new transmissions.

[0073] Scenario 2: DCI is missed due to wireless channel issues.

[0074] Specifically, due to a period of continuous DCI missed detection caused by the wireless channel, the NDI is continuously flipped (1→0→1), and the UE mistakenly takes the second new transmission as the first retransmission and sends historical data.

[0075] Exemplarily, the process of initial retransmission identification failure due to DCI missed detection may include the following steps:

[0076] Step a1: The base station sends DCI1 to the UE, wherein the DCI1 includes: the HARQ ID is HARQ7; and the value of NDI is 1. Accordingly, the UE receives the DCI1 sent by the access network device.

[0077] Step a2: The UE uses the HARQ7 process to send new data 602 / 1 to the access network device according to the instruction of DCI1, and sets the value of NDI to 1.

[0078] Step a3: The base station sends DCI2 to the UE, wherein DCI2 includes: HARQ ID is HARQ7; and NDI value is 0. However, the UE does not receive DCI2 because card 1 occupies radio frequency path resources or because of wireless channel reasons.

[0079] It can be understood that if the base station does not receive the HARQ7 data corresponding to DCI2, or the base station receives the HARQ7 data corresponding to DCI2 but the decoding is incorrect, the base station can schedule the retransmission of HARQ7. If after multiple retransmissions, the base station still does not receive the HARQ7 data corresponding to DCI2, or the decoding is still incorrect, the base station abandons scheduling the HARQ7 data corresponding to DCI2 and instead schedules the sending of the next new data.

[0080] Step a4: The base station sends DCI3 to the UE, wherein the DCI3 includes: the HARQ ID is HARQ7; and the value of NDI is 1. Accordingly, the UE receives the DCI3 sent by the access network device.

[0081] Step a5: According to the instruction of DCI3, the UE believes that this scheduling should be retransmission using HARQ7, so the UE retransmits data 602 / 1 to the access network device using HARQ7 and keeps the value of NDI as 1.

[0082] It is understandable that since the UE missed detecting DCI2, the UE misjudged DCI3 as a retransmission of data transmitted by DCI1 by comparing DCI1 and DCI3 (HARQ ID is HARQ7; NDI value is 1), and this misjudgment may cause the wireless link to fail.

[0083] Therefore, it can be seen that relying solely on the NDI flip in the current protocol to indicate whether it is new data cannot solve the misjudgment problem in the above scenario. Once an initial retransmission misjudgment occurs, the wireless link will fail, affecting the user experience.

[0084] In order to solve the problem of misjudgment of new transmission and retransmission, the present application provides a data transmission method, which includes: a receiving end of a DCI receives first scheduling information of a HARQ process, and uses the HARQ process to retransmit data when the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information is within the life cycle of the HARQ process.

[0085] In this way, the embodiment of the present application defines the life cycle of HARQ. When the received first scheduling information meets the retransmission scheduling condition, it is determined whether the time of receiving the first scheduling information is within the life cycle of HARQ; if so, the HARQ process is used to retransmit the data; if not, the first scheduling information is refused to be executed or HARQ is used for new data transmission. In this way, in the scenario of continuous DCI missed detection, the wireless link failure caused by new transmission and retransmission misjudgment can be reduced, the communication reliability can be improved, the service interruption time can be shortened, and the user experience can be improved.

[0086] The data transmission method provided in the embodiment of the present application is described below in conjunction with the accompanying drawings.

[0087] The technical solutions of the embodiments of the present application can be used in various communication systems, which may be a third generation partnership project (3GPP) communication system, such as a long term evolution (LTE) system, or a fifth generation (5G) mobile communication system, a new radio (NR) system, a new radio vehicle to everything (NR V2X) system, and may also be applied to a system of LTE and 5G hybrid networking, or a device-to-device (D2D) communication system, a machine-to-machine (M2M) communication system, an Internet of Things (IoT), and other next generation communication systems, and may also be a non-3GPP communication system without limitation.

[0088] The technical solutions of the embodiments of the present application can be applied to various communication scenarios, for example, one or more of the following communication scenarios: enhanced mobile broadband (eMBB), ultra-reliable low latency communication (URLLC), machine type communication (MTC), massive machine type communications (mMTC), D2D, V2X, and IoT and other communication scenarios.

[0089] The technical solution of the embodiment of the present application can also be applied to long-distance communication scenarios, such as satellite communication scenarios where the distance between the terminal device and the network device is constantly changing, or other long-distance communication scenarios, etc., without limitation.

[0090] The system architecture of the communication system of the embodiment of the present application may include at least a first communication node and a second communication node. It should be understood that in this example, in the downlink, the first communication node may be a network side device (for example, including but not limited to an access network device), and the second communication node may be a terminal side device (for example, including but not limited to a terminal). Of course, in the uplink, the first communication node may also be a terminal side device, and the second communication node may also be a network side device. In the device-to-device communication between the two communication nodes, the first communication node and the second communication node may both be a base station or a terminal. The first communication node and the second communication node may be referred to as the first node and the second node, respectively.

[0091] Exemplarily, taking the first communication node as an access network device and the second communication node as a terminal as an example, Figure 5 A schematic diagram of a network architecture of a communication system provided in an embodiment of the present application is shown. Figure 5 As shown, the communication system includes an access network device 20 and a terminal 30 connected to the access network device. The access network device 20 may cover one or more cells, and the terminal 30 may move within the cell covered by the access network device 20 or between cells to receive network services provided by the access network device 20.

[0092] The access network device 20 involved in the present application is a device in a radio access network (RAN) that connects a terminal to a wireless network. The RAN can be connected to a core network (for example, it can be an LTE core network or a 5G core network, etc.). The access network device 20 can be a satellite base station (or flying platform) in an NTN scenario, an evolutionary Node B (eNB or eNodeB) in LTE, or a base station in a 5G network or a future evolved public land mobile network (PLMN), a broadband network gateway (BNG), a convergence switch or a non-3GPP access device; or the access network device 20 in the embodiment of the present application can also be a wireless controller in a cloud radio access network (CRAN); or a transmission and reception point (TRP), or a device including a TRP, etc., which is not specifically limited in the embodiment of the present application. Optionally, the base station in the embodiment of the present application may include various forms of base stations, such as: macro base stations, micro base stations (also called small stations), relay stations, access points, etc., and the embodiment of the present application does not specifically limit this.

[0093] In some embodiments, the access network device 20 and the terminal 30 may also be referred to as a communication device, which may be a general device or a dedicated device, and the embodiments of the present application do not specifically limit this.

[0094] In some embodiments, the terminal 30 may be a device with wireless transceiver function, which may be deployed on land, including indoors or outdoors, handheld, wearable or vehicle-mounted; it may also be deployed on the water surface (such as a ship, etc.); it may also be deployed in the air (such as an airplane, a balloon, and a satellite, etc.). The terminal may be a mobile phone, a tablet computer (Pad), a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in smart grid, a wireless terminal in transportation safety, a wireless terminal in smart city, a wireless terminal in smart home, etc. The embodiments of the present application do not limit the application scenarios. Terminal 30 may sometimes also be referred to as user, UE, access terminal, UE unit, UE station, mobile station, mobile station, remote station, remote terminal, mobile device, UE terminal, wireless communication equipment, UE agent or UE device, etc., which is not limited to the embodiments of the present application.

[0095] like Figure 6 As shown, it is a schematic diagram of the structure of the access network device 20 and the terminal 30 provided in the embodiment of the present application.

[0096] The terminal 30 includes at least one processor ( Figure 6 The exemplary embodiment includes a processor 301 as an example) and at least one transceiver ( Figure 6 In the example, the terminal 30 includes a transceiver 303 as an example for explanation). Further, the terminal 30 may also include at least one memory ( Figure 6 In the example, a memory 302 is used as an example to illustrate), at least one output device ( Figure 6 The exemplary embodiment includes an output device 304 as an example) and at least one input device ( Figure 6 The example is described by taking an input device 305 as an example).

[0097] The processor 301, the memory 302 and the transceiver 303 are connected via a communication line. The communication line may include a path to transmit information between the above components.

[0098] Processor 301 may be a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits for controlling the execution of the program of the present application. In a specific implementation, as an embodiment, processor 301 may also include multiple CPUs, and processor 301 may be a single-core (single-CPU) processor or a multi-core (multi-CPU) processor. The processor here may refer to one or more devices, circuits, or processing cores for processing data (such as computer program instructions).

[0099] The memory 302 may be a device with a storage function. For example, it may be a read-only memory (ROM) or other types of static storage devices that can store static information and instructions, a random access memory (RAM) or other types of dynamic storage devices that can store information and instructions, or an electrically erasable programmable read-only memory (EEPROM), a compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical disc, laser disc, optical disc, digital versatile disc, Blu-ray disc, etc.), a magnetic disk storage medium or other magnetic storage device, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and can be accessed by a computer, but is not limited thereto. The memory 302 may exist independently and be connected to the processor 301 via a communication line. The memory 302 may also be integrated with the processor 301.

[0100] The memory 302 is used to store computer-executable instructions for executing the solution of the present application, and the execution is controlled by the processor 301. Specifically, the processor 301 is used to execute the computer-executable instructions stored in the memory 302, thereby implementing the method described in the embodiment of the present application.

[0101] Alternatively, in the present application, the processor 301 may also perform processing-related functions in the signal sending and receiving method provided in the present application, and the transceiver 303 may be responsible for communicating with other devices or communication networks, and the embodiments of the present application do not specifically limit this.

[0102] The computer executable instructions involved in this application may also be referred to as application code or computer program code, which is not specifically limited in the embodiments of this application.

[0103] The transceiver 303 may be any transceiver-like device for communicating with other devices or communication networks, such as Ethernet, radio access network (RAN), or wireless local area networks (WLAN). The transceiver 303 includes a transmitter (Tx) and a receiver (Rx).

[0104] The output device 304 communicates with the processor 301 and can display information in a variety of ways. For example, the output device 304 can be a liquid crystal display (LCD), a light emitting diode (LED) display device, a cathode ray tube (CRT) display device, or a projector.

[0105] The input device 305 communicates with the processor 301 and can accept user input in a variety of ways. For example, the input device 305 can be a mouse, a keyboard, a touch screen device, or a sensor device.

[0106] The access network device 20 includes at least one processor ( Figure 6 The exemplary embodiment includes a processor 201 as an example) and at least one transceiver ( Figure 6 In the example, a transceiver 203 is used as an example for explanation). Further, the access network device 20 may also include at least one memory ( Figure 6 In the example, a memory 202 is used as an example for explanation) and at least one network interface ( Figure 6 The exemplary embodiment of the present invention is described by taking a network interface 204 as an example). The processor 201, the memory 202, the transceiver 203 and the network interface 204 are connected via a communication line. The network interface 204 is used to connect to the core network device via a link (such as an S1 interface), or to connect to the network interface of other network devices via a wired or wireless link (such as an X2 interface). Figure 6 In addition, the description of the processor 201, the memory 202 and the transceiver 203 can refer to the description of the processor 301, the memory 302 and the transceiver 303 in the terminal 30, which will not be repeated here.

[0107] Understandably, Figure 6The structure shown does not constitute a specific limitation on the terminal 30 and the access network device 20. For example, in other embodiments of the present application, the terminal 30 and the access network device 20 may include more or fewer components than shown in the figure, or combine some components, or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0108] It is understandable that in the embodiment of the present application, the terminal 30 and / or the access network device 20 can perform some or all of the steps in the embodiment of the present application, and these steps or operations are only examples. The embodiment of the present application can also perform other operations or variations of various operations. In addition, the various steps can be performed in different orders presented in the embodiment of the present application, and it is possible that not all operations in the embodiment of the present application need to be performed.

[0109] It is understandable that the interaction mechanism between the access network device 20 and the terminal 30 in each embodiment of the present application can be appropriately modified to apply to the interaction between the CU or DU and the terminal. It should be noted that the message name between the various devices or the name of each parameter in the message in the following embodiments of the present application is only an example, and other names may also be used in the specific implementation, and the embodiments of the present application do not specifically limit this.

[0110] It should be noted that the execution subject of the data transmission method provided in the embodiment of the present application is not limited. For example, the method can be applied to Figure 4 In the communication system shown in FIG. 1 , the method is executed by the terminal 30; or, the method can also be applied to an end-to-end system architecture and executed by one of the terminals. Figure 4 In the communication system shown, the terminal 30 is used as an example for explanation.

[0111] like Figure 7 As shown, the data transmission method provided in the embodiment of the present application includes the following steps:

[0112] S501. A terminal receives first scheduling information of a HARQ process.

[0113] The first scheduling information is used to schedule the transmission of a data packet or a TB block. Exemplarily, the first scheduling information may be carried in a DCI or other information that may indicate scheduling information, which is not limited in the embodiment of the present application.

[0114] Exemplarily, the above HARQ process may correspond to one or more TB blocks. For example, in NR mode, when uplink and downlink space division multiplexing is not enabled, one scheduling transmission may transmit one TB block, and one HARQ process may correspond to one TB block; when uplink and downlink space division multiplexing is enabled, one scheduling transmission may transmit one or two TB blocks, and one HARQ process may correspond to one or two TB blocks.

[0115] It should be noted that in the implementation steps of the data transmission method provided in the embodiment of the present application, the access network device is the sender of the first scheduling information, and the terminal is the receiver of the first scheduling information; and, the terminal is the sender of the data, and the access network device is the receiver of the data.

[0116] S502: When the first scheduling information satisfies the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information is within the life cycle of the HARQ process, the terminal uses the HARQ process to retransmit data.

[0117] The above-mentioned use of the HARQ process for data retransmission refers to the use of the HARQ process to transmit historical data.

[0118] The life cycle of the HARQ process refers to the maximum duration of the HARQ process, that is, the longest time interval from the creation to the cancellation of the HARQ process. If the time of receiving the first scheduling information is within the life cycle of the HARQ process, it means that the HARQ process is in execution state and the HARQ process can be used for data retransmission.

[0119] In some embodiments, the unit of the above life cycle may be a symbol or a time slot, wherein the symbol may be an orthogonal frequency division multiplexing (OFDM) symbol; the time slot may include: a mini-slot, a basic timeslot, a combined timeslot, an extended timeslot, etc.

[0120] Exemplarily, when the unit of the life cycle is an OFDM symbol, the time when the first scheduling information is received may be the start symbol or the end symbol of the OFDM symbol, etc., and this embodiment of the present application is not limited to this.

[0121] Exemplarily, when the unit of the life cycle is a time slot, the time when the first scheduling information is received may be the time slot where the first scheduling information is located; or, the time when the first scheduling information is received may be the next time slot of the time slot where the first scheduling information is located.

[0122] It should be noted that the embodiments of the present application do not limit the reception status of the retransmitted data by the data receiving end (for example, the access network device). For example, the data receiving end can receive the retransmitted data sent by the data sending end using the HARQ process, and feedback ACK information to the data sending end after successful decoding; or, the data receiving end can receive the retransmitted data sent by the data sending end using the HARQ process, and feedback NACK information to the data sending end after decoding fails; or, the data receiving end does not receive the retransmitted data sent by the data sending end using the HARQ process.

[0123] In some embodiments, Figure 8 As shown, the above method may further include the following step S503a.

[0124] S503a: When the first scheduling information satisfies the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, the terminal refuses to execute the first scheduling information.

[0125] It can be understood that if the time when the terminal receives the first scheduling information or the time to transmit data based on the first scheduling information exceeds the life cycle of the HARQ process, it means that the HARQ process has been revoked and the HARQ process cannot be used for data retransmission, then the terminal can choose to refuse to execute the first scheduling information.

[0126] In some embodiments, Fig. 9 As shown, the above method may further include the following step S503b.

[0127] S503b: When the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, the terminal uses the HARQ process to retransmit data.

[0128] The above-mentioned use of HARQ for new data transmission refers to using the HARQ process to transmit new data.

[0129] It can be understood that if the time when the terminal receives the first scheduling information or the time to transmit data based on the first scheduling information exceeds the life cycle of the HARQ process, it means that the HARQ process has been revoked and the HARQ process cannot be used for data retransmission. The terminal can choose to use the HARQ process for new data transmission.

[0130] To summarize, in the scenario of continuous DCI missed detection, relying solely on NDI flipping to judge new transmission and retransmission is prone to misjudgment. In this regard, the embodiment of the present application defines the life cycle of HARQ. When the received first scheduling information meets the retransmission scheduling condition, it is determined whether the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information is within the life cycle of HARQ; if so, the HARQ process is used to retransmit the data; if not, the first scheduling information is refused to be executed or HARQ is used for new data transmission. In this way, the wireless link failure caused by new transmission and retransmission misjudgment can be reduced, the communication reliability can be improved, the service interruption time can be shortened, and the user experience can be improved.

[0131] The following describes the situation where the first scheduling information meets the retransmission scheduling condition.

[0132] In some embodiments, the first scheduling information meeting the retransmission scheduling condition includes: determining that a new transmission identifier (NDI) carried by the first scheduling information has not flipped.

[0133] Exemplarily, assuming that the NDI carried by the first scheduling information is 1, and the NDI carried by the previous scheduling information of the first scheduling information is also 1, that is, the NDI has not flipped, it is determined that the first scheduling information meets the retransmission condition.

[0134] It is understandable that in order to distinguish between new transmission data and retransmission data, the terminal / access network device indicates whether the transmitted data is new data by defining whether the value of NDI is flipped. Therefore, if the NDI carried by the first scheduling information does not flip, the terminal determines that the first scheduling information meets the retransmission scheduling condition.

[0135] In some embodiments, the first scheduling information satisfies the retransmission scheduling condition and also includes: the modulation and coding scheme (MCS) index value indicated by the first scheduling information is within a preset interval, and the transmission block size calculated based on the MCS index value is the same as the transmission block size of the last new data transmitted by the HARQ process.

[0136] Among them, the above-mentioned preset interval is the MCS index value interval that needs to calculate the transmission block size. It should be noted that when the UE is configured with different modulation modes, the MCS index value interval that needs to calculate the transmission block size may be different. Exemplarily, when the UE is configured with 64-phase quadrature amplitude modulation (Quadrature Amplitude Modulation, QAM), the following Table 1 can be determined according to configuration parameters (such as scheduling parameters or network configuration parameters, etc., which are not limited in the embodiments of the present application), and then the MCS index value interval that needs to calculate the transmission block size is determined to be 0-27 according to the following Table 1.

[0137] Exemplarily, the first scheduling information is DCI. After receiving the DCI, the terminal reads the MCS field of the DCI to obtain the MCS index value (Index), and then determines that the MCS index value is within a preset interval, and calculates the transport block size based on the MCS index value.

[0138] Exemplarily, calculating the transport block size based on the MCS index value may be implemented as follows:

[0139] Step b1: Determine the modulation order (Modulation Order) and target code rate (Target code Rate) used by PUSCH by looking up the table according to the MCS index value.

[0140] Exemplarily, when the UE is configured for 64QAM, the UE MCS )I MCS The following Table 1 is consulted to determine the modulation order (which may be expressed as Qm) and the target code rate (which may be expressed as R) used by the PUSCH.

[0141] Table 1

[0142]

[0143]

[0144] Step b2: Determine the number of resource elements (RE) in the time slot (N RE ).

[0145] First, the number of REs (N′) allocated to PUSCH in a physical resource block (PRB) is determined by the following formula (1): RE ).

[0146]

[0147] in, is the number of subcarriers in a PRB; is the number of symbols allocated to PUSCH in the time slot; is the number of REs of DM-RS in each PRB during the scheduling period; It is the overhead configured by the parameter xOverhead in the serving cell configuration (serving cellconfig) of PUSCH.

[0148] Furthermore, according to the above formula (1), N′ is obtained RE According to the following formula (2), the number of REs in the time slot (NRE ).

[0149] N RE =min(156,N′ RE )*n PRB Formula (2)

[0150] Among them, n PRB is the total number of PRBs.

[0151] Step b3: Determine the median number of information bits based on the number of resource elements in the time slot, the target code rate, the modulation order, and the number of transmission layers.

[0152] Exemplarily, the median number of information bits is determined according to the following formula (3).

[0153] N info =N RE *R*Q m *v Formula (3)

[0154] Where v is the number of transmission layers.

[0155] In some embodiments, if N info ≤3824, then determine the size of the transport block according to the following step b4; if N info >3824, determine the size of the transmission block according to the following step b5.

[0156] Step b4: If N info When ≤3824, determining the size of the transport block includes the following:

[0157] First, determine N′ according to the following formula (4): info :

[0158]

[0159] in,

[0160] Then, by looking up the following table 2, select a value greater than or equal to N′ info (When greater than N′ info In the case of info The value closest to ( ) is used as the transport block size (TB size, TBS).

[0161] Table 2

[0162]

[0163]

[0164] Step b5: In N info>3824, the size of the transport block is determined by:

[0165] First, determine N′ according to the following formula (5): info :

[0166] N′ info =max(3824,2 n *round[(N info -24) / 2 n ]) Formula (5)

[0167] in, And the round function refers to rounding to the nearest integer.

[0168] Furthermore, according to N′ info Determine TBS:

[0169] If the target bitrate R≤1 / 4, TBS satisfies the following formula (6):

[0170]

[0171] in,

[0172] If the target code stream R>1 / 4, determine N′ info Is it greater than 8424? info When >8424, TBS satisfies the following formula (7):

[0173]

[0174] in,

[0175] In N info When ≤8424, TBS satisfies the following formula (8):

[0176]

[0177] In some embodiments, the first scheduling information satisfies the retransmission scheduling condition and further includes: the MCS index value indicated by the first scheduling information is within a preset interval, and the transmission block size calculated based on the MCS index value is larger than the transmission block size of the last new data transmitted by the HARQ process.

[0178] It can be understood that the data retransmitted each time in the HARQ process can be the same as the newly transmitted data, or padding information can be added to the newly transmitted data; and the RV version of each retransmission can be the same or different. Therefore, regardless of whether the amount of data changes, the transmission block size calculated according to the MCS index value indicated by the first scheduling information should not be less than the transmission block size of the last newly transmitted data of the HARQ process. Therefore, in an embodiment of the present application, when the transmission block size calculated according to the MCS index value indicated by the first scheduling information is greater than or equal to the transmission block size of the last newly transmitted data of the HARQ process, it is determined that the first scheduling information meets the retransmission condition.

[0179] In some embodiments, the first scheduling information satisfying the retransmission scheduling condition also includes: the MCS index value indicated by the first scheduling information is not within a preset interval.

[0180] Among them, when the MCS index value indicated by the first scheduling information is not in the MCS index value interval that needs to calculate the transport block size, the target code rate (Target code Rate) corresponding to the MCS index is invalid, and therefore, the size of the transport block cannot be determined, then the first scheduling information satisfies the retransmission condition. Exemplarily, when the UE is configured for 64QAM, the MCS index value interval that does not need to calculate the transport block size is 28-31. It can be seen from Table 1 above that this interval does not give a valid target code rate.

[0181] The following describes a method for determining whether the time when the terminal receives the first scheduling information or the time when data is transmitted based on the first scheduling information is within the life cycle of the HARQ process.

[0182] In some embodiments, the time of receiving the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time of receiving the first scheduling information and the time of last receiving the second scheduling information of the HARQ process is less than the life cycle of the HARQ process.

[0183] The second scheduling information of the HARQ process may be scheduling information for indicating new transmission data; or, the second scheduling information of the HARQ process may be scheduling information for indicating retransmission.

[0184] For example, Fig.10 As shown, it is assumed that the time when the first scheduling information is received is moment t2; the time when the second scheduling information of the HARQ process is last received is moment t1. If the time interval between moment t1 and moment t2 is less than the life cycle of the HARQ process, it is determined that the time when the first scheduling information is received (moment t2) is within the life cycle of the HARQ process, and then the terminal uses the HARQ process indicated by the first scheduling information to retransmit data.

[0185] Example type, such as Fig.11 As shown, it is assumed that the time when the first scheduling information is received is moment t3; the time when the second scheduling information of the HARQ process is last received is moment t2, if the time interval between moment t2 and moment t3 is greater than the life cycle of the HARQ process, it is determined that the time when the first scheduling information is received (moment t3) exceeds the life cycle of the HARQ process, and then the terminal uses the HARQ process indicated by the first scheduling information to transmit new data.

[0186] It can be understood that if the time interval between the time when the first scheduling information is received by the terminal and the time of the second scheduling information of the HARQ process is greater than the life cycle of the HARQ process, it means that the retransmission indicated by the first scheduling information and the new transmission / retransmission indicated by the second scheduling information are too long apart, which may be due to the misjudgment of the new transmission and retransmission caused by DCI missed detection. Therefore, corresponding measures can be taken for the first scheduling information (for example, refusing to execute the first scheduling information or sending the first scheduling information as a new transmission) to avoid wireless link failure and improve communication reliability.

[0187] In some embodiments, the time when the first scheduling information is received is within the life cycle of the HARQ process, including: the time interval between the time when the first scheduling information is received and the time when data is transmitted based on the last received second scheduling information of the HARQ process is less than the life cycle of the HARQ process.

[0188] It is understandable that the time when the terminal receives the second scheduling information may not be the same as the time when the terminal transmits data based on the second scheduling information. Therefore, if the time interval between the time when the terminal receives the first scheduling information and the time when the terminal transmits data based on the second scheduling information of the HARQ process is greater than the life cycle of the HARQ process, it means that the retransmission indicated by the first scheduling information and the new transmission / retransmission indicated by the second scheduling information are too long apart, which may be due to the misjudgment of the new transmission and retransmission caused by DCI missed detection. Therefore, corresponding measures can be taken for the first scheduling information (for example, refusing to execute the first scheduling information or sending the first scheduling information as a new transmission) to avoid wireless link failure and improve communication reliability.

[0189] In some embodiments, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time when the second scheduling information of the HARQ process was last received is less than the life cycle of the HARQ process.

[0190] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the terminal last received the second scheduling information of the HARQ process.

[0191] In some embodiments, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time for transmitting data based on the last received second scheduling information of the HARQ process is less than the life cycle of the HARQ process.

[0192] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the terminal transmits data based on the last received second scheduling information of the HARQ process.

[0193] In some embodiments, the time of receiving the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time of receiving the first scheduling information and the time when the HARQ process last transmitted new data is less than the life cycle of the HARQ process.

[0194] Example type, such as Fig.12 As shown, it is assumed that the time when the first scheduling information is received is moment t2; the time when the HARQ process last transmitted new data is moment t1. If the time interval between moment t1 and moment t2 is less than the life cycle of the HARQ process, it is determined that the time when the first scheduling information is received (moment t2) is within the life cycle of the HARQ process, and then the terminal uses the HARQ process indicated by the first scheduling information to retransmit data.

[0195] Example type, such as Fig.13 As shown, it is assumed that the time when the first scheduling information is received is moment t3; the time when the HARQ process last transmitted new data is moment t1. If the time interval between moment t1 and moment t3 is greater than the life cycle of the HARQ process, it is determined that the time when the first scheduling information is received (moment t3) exceeds the life cycle of the HARQ process, and then the terminal uses the HARQ process indicated by the first scheduling information to transmit new data.

[0196] It can be understood that if the time interval between the time when the first scheduling information is received by the terminal and the time when the HARQ process last transmitted new data is greater than the life cycle of the HARQ process, it means that the new transmission of the HARQ process is too long apart from the retransmission indicated by the first scheduling information, which may be due to the misjudgment of the new transmission and retransmission caused by DCI missed detection. Therefore, corresponding measures can be taken for the first scheduling information (for example, refusing to execute the first scheduling information or sending the first scheduling information as a new transmission) to avoid wireless link failure and improve communication reliability.

[0197] In some embodiments, the time when the first scheduling information is received is within the life cycle of the HARQ process, including: the time interval between the time when the first scheduling information is received and the time when the last scheduling information indicating new transmission data of the HARQ process was received is less than the life cycle of the HARQ process.

[0198] It is understandable that the time when the terminal last received the scheduling information indicating new transmission data of the HARQ process may be different from the time when the terminal's HARQ process last transmitted new data. Therefore, the embodiment of the present application can also determine whether the time when the terminal receives the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal last received the scheduling information indicating new transmission data of the HARQ process and the time when the terminal received the first scheduling information.

[0199] In some embodiments, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time when the HARQ process last transmitted new data is less than the life cycle of the HARQ process.

[0200] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the HARQ process last transmitted new data.

[0201] In some embodiments, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time when the last scheduling information indicating new transmission data of the HARQ process was received is less than the life cycle of the HARQ process.

[0202] It can be understood that since the time when the terminal receives the first scheduling information may be different from the time when the terminal transmits data based on the first scheduling information, the embodiment of the present application can also determine whether the time when the terminal transmits data based on the first scheduling information is within the life cycle of the HARQ process based on the time when the terminal transmits data based on the first scheduling information and the time when the terminal last received scheduling information indicating new data transmission of the HARQ process.

[0203] In some embodiments, before the above step S502, the above method further includes determining the life cycle of the HARQ process. Exemplarily, determining the life cycle of the HARQ process can be implemented in the following two ways:

[0204] 1. The life cycle of the HARQ process is negotiated between the base station and the terminal. For example, Fig.14 As shown, the process of negotiating the life cycle of the HARQ process can be implemented as the following steps:

[0205] S401. A terminal sends first information, where the first information is used to indicate a maximum duration of a supported life cycle.

[0206] Exemplarily, the terminal may report the capability information of the terminal to the access network device; the capability information is used to represent the capabilities supported by the terminal. The capability information of the terminal may include the first information.

[0207] Accordingly, after receiving the first information sent by the terminal, the access network device determines the actual duration of the life cycle of the HARQ process based on the first information. Exemplarily, the access network device may determine the actual duration of the life cycle of the HARQ process based on the service scenario of the HARQ process and / or the historical statistical characteristics of the HARQ process (i.e., the scheduling interval of the HARQ process counted in the historical time period).

[0208] In some embodiments, Fig.14 As shown, before the above step S502, the above method further includes:

[0209] S402: The terminal receives second information, where the second information is used to configure an actual duration of a life cycle.

[0210] Exemplarily, the terminal receives the second information via air interface signaling.

[0211] In some embodiments, the actual duration of the life cycle of the HARQ process is less than or equal to the maximum duration of the life cycle of the HARQ process supported by the terminal. Exemplarily, assuming that the maximum duration of the HARQ life cycle supported by the terminal is 500 slots, the actual duration of the life cycle of the HARQ process may be 400 slots. It is understandable that if the actual duration of the life cycle of the HARQ process exceeds the maximum duration of the life cycle of the HARQ process supported by the terminal, it may cause the terminal to make an incorrect judgment on the new transmission and retransmission of the HARQ process, thereby causing the wireless link to fail.

[0212] It should be noted that Fig.14 The execution order shown is only an example and does not limit the data transmission method provided in the embodiment of the present application. The embodiment of the present application does not limit the execution order between the above step S501 and steps S401-S402. Exemplarily, the above step S501 may be executed first and then the above steps S401-S402; or, the above steps S401-S402 may be executed first and then the above step S501; or, the above steps S501 and steps S401-S402 may be executed simultaneously.

[0213] 2. The terminal statically configures the life cycle of the HARQ process.

[0214] Exemplarily, the terminal may determine the life cycle of the HARQ process based on different service scenarios applied by the HARQ process and / or historical statistical characteristics of the HARQ process, without the need to negotiate with the access network device.

[0215] Among them, different service scenarios correspond to different signal-to-noise ratios. It can be understood that different signal-to-noise ratios correspond to different signal qualities, and therefore the length of the corresponding HARQ process life cycle is also different. Therefore, in the embodiment of the present application, the terminal can determine the length of the HARQ process life cycle according to the signal-to-noise ratio corresponding to the service scenario of the HARQ process application.

[0216] Exemplarily, different business scenarios include at least one of the following: non-high-speed rail scenario and high-speed rail scenario.

[0217] It can be understood that in the data transmission method provided in the embodiment of the present application, by defining the life cycle of the HARQ process, it is possible to reduce the probability of new transmission and retransmission misjudgment in a continuous DCI missed detection scenario, reduce wireless link failures caused by erroneous data transmission, improve communication reliability, shorten service interruption time, and improve user experience.

[0218] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of interaction between each node. It is understandable that each node, such as a terminal, an access network device, etc., includes a hardware structure and / or software module corresponding to each function in order to realize the above functions. It should be easily appreciated by those skilled in the art that, in combination with the algorithm steps of each example described in the embodiments disclosed herein, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present application.

[0219] The embodiment of the present application can group the functional modules of the terminal, access network equipment, etc. according to the above method example. For example, each functional module can be grouped according to each function, or two or more functions can be integrated into one processing module. The above integrated module can be implemented in the form of hardware or in the form of software functional modules. It should be noted that the grouping of modules in the embodiment of the present application is schematic and is only a logical functional grouping. There may be other grouping methods in actual implementation.

[0220] Fig.15 The structure diagram of a communication device 100 is shown. The communication device 100 may be a terminal, or a chip in a terminal, or a system on a chip. The communication device 100 may be used to perform the functions of the terminal involved in the above embodiments. As an implementation method, Fig.15 The communication device 100 shown includes: a receiving unit 1001 and a processing unit 1002. As another possible implementation, Fig.15 The communication device 100 shown further includes: a sending unit 1003 .

[0221] The receiving unit 1001 is configured to receive first scheduling information of a HARQ process. For example, the receiving unit 1001 may support the communication device 100 to execute S501.

[0222] The processing unit 1002 is configured to use the HARQ process to retransmit data when the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information is within the life cycle of the HARQ process. For example, the processing unit 1002 may support the communication device 100 to execute S502.

[0223] In one possible design, the processing unit 1002 is further configured to refuse to execute the first scheduling information when the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information exceeds the life cycle of the HARQ process. For example, the processing unit 1002 can support the communication device 100 to execute S503a.

[0224] In one possible design, the processing unit 1002 is further configured to use the HARQ process to perform new data transmission when the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information exceeds the life cycle of the HARQ process. For example, the processing unit 1002 can support the communication device 100 to execute S503b.

[0225] In one possible design, the first scheduling information satisfies the retransmission scheduling conditions, including: determining that the new transmission identifier carried by the first scheduling information has not been flipped.

[0226] In a possible design, the first scheduling information satisfying the retransmission scheduling condition further includes at least one of the following:

[0227] The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transport block size calculated based on the MCS index value is the same as the transport block size of the last new data transmitted by the HARQ process;

[0228] The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transport block size calculated based on the MCS index value is larger than the transport block size of the last new data transmitted by the HARQ process;

[0229] The modulation and coding scheme MCS index value indicated by the first scheduling information is not within the preset interval.

[0230] In one possible design, the above-mentioned preset interval is the MCS index value interval required to calculate the transmission block size.

[0231] In one possible design, the time for receiving the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for receiving the first scheduling information and the time for last receiving the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time for receiving the first scheduling information and the time for last receiving the scheduling information indicating new transmission data of the HARQ process is less than the life cycle of the HARQ process.

[0232] In one possible design, the time when the first scheduling information is received is within the life cycle of the HARQ process, including: the time interval between the time when the first scheduling information is received and the time when data is transmitted based on the last receipt of the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time when the first scheduling information is received and the last time the HARQ process transmitted new data is less than the life cycle of the HARQ process.

[0233] In one possible design, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time when the second scheduling information of the HARQ process was last received is less than the life cycle of the HARQ process; or, the time interval between the time for transmitting data based on the first scheduling information and the time when the scheduling information indicating new transmission data of the HARQ process was last received is less than the life cycle of the HARQ process.

[0234] In one possible design, the time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: the time interval between the time for transmitting data based on the first scheduling information and the time for transmitting data based on the last receipt of the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, the time interval between the time for transmitting data based on the first scheduling information and the last time the HARQ process transmitted new data is less than the life cycle of the HARQ process.

[0235] In a possible design, the sending unit 1003 is used to send the first information, where the first information is used to indicate the maximum duration of the supported life cycle. For example, the sending unit 1003 can support the communication device 100 to execute S401.

[0236] In a possible design, the receiving unit 1001 is further used to receive second information, where the second information is used to configure the actual duration of the life cycle. For example, the receiving unit 1001 can support the communication device 100 to execute S402.

[0237] In one possible design, the processing unit 1002 is also used to determine different life cycles based on different business scenarios; wherein different business scenarios correspond to different signal-to-noise ratios; and different business scenarios include at least one of the following: non-high-speed rail scenarios and high-speed rail scenarios.

[0238] In a possible design, the units of the life cycle include: symbols or time slots.

[0239] Specifically, the above Figure 7All relevant contents of each step involved in the illustrated method embodiment can be referred to the functional description of the corresponding functional module, and will not be repeated here. The communication device 100 is used to execute Figure 7 The method shown has the function of the terminal in the data transmission method shown, so it can achieve the same effect as the above-mentioned data transmission method.

[0240] As another possible way to achieve this, Fig.15 The communication device 100 shown includes: a processing module and a communication module. The processing module is used to control and manage the actions of the communication device 100. For example, the processing module can integrate the functions of the processing unit 1002, and can be used to support the communication device 100 to execute S502, S503a, S503b and other processes of the technology described in this article. The communication module can integrate the functions of the receiving unit 1001 and the sending unit 1003, and can be used to support the communication device 100 to execute S501, S401, S402 and communicate with other network entities. The communication device 100 may also include a storage module for storing program codes and data of the communication device 100.

[0241] The processing module may be a processor or a controller. It may implement or execute various exemplary logic blocks, modules and circuits described in conjunction with the contents disclosed in this application. The processor may also be a combination that implements computing functions, such as a combination of one or more microprocessors, a combination of a DSP and a microprocessor, etc. The communication module may be a transceiver circuit or a communication interface, etc. The storage module may be a memory. When the processing module is a processor, the communication module is a communication interface, and the storage module is a memory, the communication device 100 involved in the embodiment of the present application may be Figure 5 Terminal 30 is shown.

[0242] In the technical solution of this application, the collection, storage, use, processing, transmission, provision and disclosure of user personal information involved are in compliance with relevant laws and regulations and do not violate public order and good morals. For example, in the technical solution of this application, the processing of user personal information is carried out with the authorization of the user, which is explained here uniformly and will not be repeated here.

[0243] It should be noted that the terms "first" and "second" in the specification, claims and drawings of the present application are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units that are not listed, or may optionally include other steps or units that are inherent to these processes, methods, products or devices.

[0244] It should be understood that in the present application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three and more than three, and "and / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

[0245] It should be understood that in the embodiments of the present application, "B corresponding to A" means that B is associated with A. For example, B can be determined based on A. It should also be understood that determining B based on A does not mean determining B only based on A, but B can also be determined based on A and / or other information. In addition, the "connection" that appears in the embodiments of the present application refers to various connection methods such as direct connection or indirect connection to achieve communication between devices, and the embodiments of the present application do not impose any limitation on this.

[0246] Unless otherwise specified, the "transmission" (transmit / transmission) appearing in the embodiments of the present application refers to bidirectional transmission, including sending and / or receiving actions. Specifically, the "transmission" in the embodiments of the present application includes the sending of data, the receiving of data, or the sending of data and the receiving of data. In other words, the data transmission here includes uplink and / or downlink data transmission. Data may include channels and / or signals, uplink data transmission is uplink channel and / or uplink signal transmission, and downlink data transmission is downlink channel and / or downlink signal transmission. The "network" and "system" appearing in the embodiments of the present application express the same concept, and the communication system is the communication network.

[0247] Through the description of the above implementation methods, technical personnel in the relevant field can clearly understand that for the convenience and simplicity of description, only the grouping of the above-mentioned functional modules is used as an example. In actual applications, the above-mentioned functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be grouped into different functional modules to complete all or part of the functions described above.

[0248] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the grouping of the modules or units is only a logical function grouping. There may be other grouping methods in actual implementation. For example, multiple units or components can be combined or integrated into another device, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0249] The units described as separate components may or may not be physically separated, and the components shown as units may be one physical unit or multiple physical units, that is, they may be located in one place or distributed in multiple different places. Some or all of the units may be selected according to actual needs to achieve the purpose of the present embodiment.

[0250] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0251] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a readable storage medium. Based on this understanding, the technical solution of the embodiment of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium, including several instructions to enable a device, such as a single-chip microcomputer, a chip, etc., or a processor (processor) to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media for storing program codes such as USB flash drives, mobile hard drives, ROM, RAM, magnetic disks or optical disks.

[0252] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any changes or substitutions that can be easily thought of by any technician familiar with the technical field within the technical scope disclosed in the present application should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A data transmission method, characterized in that: The method comprises: Receiving first scheduling information of a HARQ process; When the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information is within the life cycle of the HARQ process, the HARQ process is used to retransmit data.

2. The method according to claim 1, characterized in that The method further comprises: When the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, the first scheduling information is refused to be executed.

3. The method according to claim 1, characterized in that The method further comprises: When the first scheduling information meets the retransmission scheduling condition and the time of receiving the first scheduling information or the time of transmitting data based on the first scheduling information exceeds the life cycle of the HARQ process, the HARQ process is used to retransmit data.

4. The method according to any one of claims 1 to 3, characterized in that: The first scheduling information satisfies the retransmission scheduling condition, including: determining that the new transmission flag carried by the first scheduling information has not been flipped.

5. The method according to claim 4, characterized in that The first scheduling information satisfies the retransmission scheduling condition and further includes at least one of the following: The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transport block size calculated based on the MCS index value is the same as the transport block size of the last new data transmitted by the HARQ process; The modulation and coding scheme MCS index value indicated by the first scheduling information is within a preset interval, and the transmission block size calculated based on the MCS index value is larger than the transmission block size of the last new transmission data of the HARQ process; The modulation and coding scheme MCS index value indicated by the first scheduling information is not within a preset interval.

6. The method according to claim 5, characterized in that The preset interval is an interval of MCS index values ​​for which the transport block size needs to be calculated.

7. The method according to any one of claims 1 to 6, characterized in that: The time of receiving the first scheduling information is within the life cycle of the HARQ process, including: The time interval between the time when the first scheduling information is received and the time when the second scheduling information of the HARQ process is last received is less than the life cycle of the HARQ process; or, The time interval between the time when the first scheduling information is received and the time when the scheduling information indicating new transmission data of the HARQ process was last received is less than the life cycle of the HARQ process.

8. The method according to any one of claims 1 to 6, characterized in that: The time of receiving the first scheduling information is within the life cycle of the HARQ process, including: The time interval between the time when the first scheduling information is received and the time when data is transmitted based on the last received second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, The time interval between the time when the first scheduling information is received and the time when the HARQ process last transmitted new data is less than the life cycle of the HARQ process.

9. The method according to any one of claims 1 to 6, characterized in that: The time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: The time interval between the time of transmitting data based on the first scheduling information and the time of last receiving the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, The time interval between the time of transmitting data based on the first scheduling information and the time of last receiving the scheduling information indicating new data transmission of the HARQ process is less than the life cycle of the HARQ process.

10. The method according to any one of claims 1 to 6, characterized in that: The time for transmitting data based on the first scheduling information is within the life cycle of the HARQ process, including: The time interval between the time of transmitting data based on the first scheduling information and the time of transmitting data based on the last reception of the second scheduling information of the HARQ process is less than the life cycle of the HARQ process; or, The time interval between the time of transmitting data based on the first scheduling information and the time of last new data transmission of the HARQ process is less than the life cycle of the HARQ process.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: Sending first information, where the first information is used to indicate a maximum duration of the life cycle supported.

12. The method according to any one of claims 1 to 11, characterized in that: The method further comprises: Second information is received, where the second information is used to configure an actual duration of the life cycle.

13. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: Different life cycles are determined based on different business scenarios; wherein the signal-to-noise ratios corresponding to the different business scenarios are different; and the different business scenarios include at least one of the following: a non-high-speed rail scenario and a high-speed rail scenario.

14. The method according to any one of claims 1 to 10, characterized in that: The unit of the life cycle includes: symbol or time slot.

15. A communication device, characterized in that: The communication device comprises a processor and a communication interface, and the processor and the communication interface are used to support the communication device to execute the method according to any one of claims 1-14.

16. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and when the computer instructions are executed on a computer, the computer is caused to execute the method according to any one of claims 1 to 14.

17. A computer program product, characterized in that The computer program product comprises computer instructions, and when the computer instructions are executed on a computer, the computer is caused to perform the method according to any one of claims 1 to 14.

Images