Communication method and terminal

Abstract

The embodiment of the invention discloses a communication method and a terminal, relates to the technical field of communication, and enables the terminal to recover wireless communication when communication interruption occurs to the terminal. The scheme specifically comprises the following steps: sending a first data packet; a first status report is received. The first status report is used for indicating that the access network equipment has confirmed to receive the first segment. The first segment is included in the first data packet. A second status report is received. The second status report is used for indicating that the access network equipment does not receive the second segment. The second segment and the first segment include at least partial data coincidence. And triggering a radio link failure (RLF).

Description

Technical Field

[0001] The embodiments of the present application relate to the field of communication technology, and in particular, to a communication method and a terminal. Background Art

[0002] Currently, the UE can implement data transmission by sending a data packet to the base station. The data packet includes data to be sent by the UE.

[0003] Exemplarily, the UE may send a data packet 1 to the base station. After the UE sends the data packet 1, the base station may send a status report 1 to the UE. The status report 1 is used to indicate the reception status of the data packet 1 by the base station.

[0004] For example, the status report 1 is used to indicate that segment A has been received. Segment A is included in data packet 1. After receiving the status report 1, the UE may delete segment A in data packet 1.

[0005] In some implementations, after sending status report 1, the base station continues to send status report 2 to the UE. Status report 2 is used to indicate that segment B has not been received. Segment B and segment A contain at least some overlapping data. After receiving status report 2, the UE has deleted segment A, which results in the UE being unable to query segment B or data in segment B that overlaps with segment A, and unable to completely retransmit segment B. This affects the transmission of subsequent data, thereby causing communication interruption of the UE. Summary of the invention

[0006] The embodiments of the present application provide a communication method and a terminal, so that the terminal can restore wireless communication when communication is interrupted.

[0007] To achieve the above objectives, the embodiments of the present application adopt the following technical solutions:

[0008] In a first aspect, a communication method is applied to a terminal, the method comprising: sending a first data packet. Receive a first status report. The first status report is used to indicate that an access network device has confirmed receipt of a first segment. The first segment is included in the first data packet. Receive a second status report. The second status report is used to indicate that the access network device has not received a second segment. The second segment and the first segment include at least part of data overlap. Trigger a radio link failure RLF.

[0009] Based on the above solution, the first status report also indicates that the access network device has received the data that overlaps with the second segment and the first segment, and the second status report also indicates that the access network device has not received the data that overlaps with the second segment and the first segment. After receiving the above-mentioned first status report and second status report, the terminal triggers RLF. Therefore, when the terminal subsequently fails to retransmit the data that overlaps with the second segment and the first segment, resulting in a communication interruption problem, the terminal can restore wireless communication by triggering RLF.

[0010] Optionally, a first radio resource control (RRC) connection is established between the terminal and the access network device. The sending of the first data packet includes: sending the first data packet through the first RRC connection. Based on the above solution, the terminal can send the first data packet to the access network device through the first RRC connection.

[0011] Optionally, after triggering the radio link failure RLF, the method further includes: establishing a second RRC connection with the access network device. Thus, the terminal can subsequently continue to transmit data based on the second RRC connection.

[0012] Optionally, the terminal is configured with a sending window. The sending of the first data packet includes: sending the first data packet with a sequence number SN ranging from a first SN to a second SN. The first SN corresponds to a lower boundary of the first sending window, and the second SN corresponds to an upper boundary of the sending window.

[0013] Optionally, the sending window is configured with a first state variable and a second state variable. The first state variable corresponds to the lower boundary of the sending window, and the second state variable corresponds to the upper boundary of the sending window. Before sending the first data packet, the first state variable corresponds to the first SN, and the second state variable corresponds to the second SN.

[0014] Optionally, before triggering the RLF, the method further includes: detecting that the second segment and the first segment include at least partial data overlap. Recording the time of receiving the second status report as the first time. Recording the time of sending the first data packet of the second SN as the second time. Triggering the RLF includes: triggering the RLF according to the time difference between the first time and the second time being greater than a preset first duration.

[0015] Based on the above scheme, after detecting that the second segment and the first segment include at least part of the data overlap, the terminal records the time of receiving the second data report as the first time, and records the second time of sending the first data packet of the second SN. The terminal triggers RLF after the difference between the first time and the second time is a preset first time length. In this way, the terminal can realize communication recovery only for the communication interruption caused by receiving the first data report and the second data report.

[0016] Optionally, after establishing the second RRC connection with the access network device, the method further includes: configuring the lower boundary and the upper boundary of the sending window. The configuring the lower boundary and the upper boundary of the sending window includes: configuring the first state variable as the third SN. Configuring the second state variable as the fourth SN. Based on the above scheme, after the terminal re-establishes the RRC connection with the access network device, the upper and lower boundaries of the sending window are reconfigured. So that the terminal can continue to send data packets with SNs within the corresponding range according to the upper and lower boundaries of the sending window.

[0017] Optionally, the terminal stores a second data packet. The second data packet is a data packet that the terminal has not sent. After configuring the lower boundary and the upper boundary of the sending window, the method further includes: sending the second data packet. The second data packet carries a fifth SN. The fifth SN is less than or equal to the third SN, and the fifth SN is less than the fourth SN. Based on the above scheme, the terminal can continue to transmit data based on the currently configured sending window after triggering RLF.

[0018] Optionally, after sending the second data packet, the method further includes: receiving a fourth status report. The fourth status report is used to indicate that the access network device has confirmed receipt of the third segment. The third segment is included in the second data packet. Receiving a fifth status report. The fifth status report is used to indicate that the access network device has not received the fourth segment. The fourth segment and the third segment include at least some overlapping data. According to the fifth status report, resending the fourth segment.

[0019] Based on the above solution, after receiving the fourth status report and the fifth status report, the terminal can retransmit the data not received by the access network device according to the fifth status report, so that the terminal can transmit subsequent data.

[0020] Optionally, after resending the fourth segment, the method further includes: receiving a third status report. The third status report is used to indicate that the access network device has confirmed receipt of the second data packet.

[0021] Optionally, the fourth status report and the fifth status report are received at the same time. Before receiving the third status report, the method further includes: upon receiving the fourth status report or the fifth status report, deleting the third segment and the data in the second data packet except the fourth segment after a delay of a second time length.

[0022] In the above solution, after receiving the fourth status report, the terminal still stores the third segment. Therefore, when the terminal receives the fifth status report, it can retransmit the fourth segment that the base station has not received. In addition, when the terminal subsequently receives an indication message that the third segment or data other than the fourth segment in the second data packet is not received, it can retransmit the third segment or data other than the fourth segment in the second data packet. Thus, the terminal can always maintain the function of wireless data transmission.

[0023] Optionally, the fifth status report is received later than the fourth status report within a third time period. Before receiving the third status report, the method further includes: upon receiving the fifth status report, deleting the data in the second data packet except the fourth segment after a delay of the third time period. Alternatively, upon receiving the fifth status report, deleting the third segment and the data in the second data packet except the fourth segment after a delay of the third time period.

[0024] Based on the above solution, when the terminal receives the fourth status report, the third segment is still stored. Therefore, when the terminal receives the fifth status report, the fourth segment can be retransmitted. In addition, when the terminal subsequently receives an indication message indicating that data other than the fourth segment in the second data packet is not received, the data other than the fourth segment in the second data packet can be retransmitted. Thus, the terminal can always maintain the function of wireless data transmission.

[0025] Optionally, after receiving the third status report, the method further comprises: deleting the remaining data in the second data packet according to the third status report. Thus, the maintenance of the data stored in the memory by the terminal can be reduced.

[0026] Optionally, after receiving the fourth status report or the fifth status report, the method further includes: continuing to store the at least one second data packet. Sending a third data packet. The SN of the third data packet is the sixth SN. The sixth SN is greater than the fifth SN. Receive a sixth status report. The sixth status report is used to indicate that the access network device has confirmed receipt of the third data packet. According to the sixth status report, the second data packet is deleted. Based on the above scheme, the terminal can delete a data packet whose SN is less than the third data packet when receiving the sixth status report. Thus, the terminal can retransmit the fourth data segment when receiving the fifth status report. Further, the terminal can always maintain the function of wireless data transmission.

[0027] Optionally, after receiving the third status report, the method further includes: modifying the first state variable from the third SN to the fifth SN plus 1. Modifying the second state variable from the fourth SN to the fifth SN plus 1 and a first length. The first length is equal to the difference between the fourth SN and the third SN. Thus, the terminal can update the upper and lower boundaries of the sending window. It is convenient for the terminal to continue subsequent data transmission based on the updated upper and lower boundaries of the sending window.

[0028] Optionally, after receiving the sixth status report, the method further includes: modifying the first state variable from the third SN to the sixth SN plus 1. Modifying the second state variable from the fourth SN to the sixth SN plus 1 and a first length. The first length is equal to the difference between the fourth SN and the third SN. Thus, the terminal can update the upper and lower boundaries of the sending window. It is convenient for the terminal to continue subsequent data transmission based on the updated upper and lower boundaries of the sending window.

[0029] Optionally, the first segment is included in the first data packet, including: the first segment is the first data packet, or the first segment is part of the data in the first data packet.

[0030] Optionally, when the first segment is part of the data in the first data packet, the first status report is further used to indicate that the first access network device has not received the fifth segment. The fifth segment is data in the first data packet other than the first segment. After receiving the first status report, the method further includes: resending the fifth segment. Deleting the first segment.

[0031] Optionally, before configuring the lower boundary and the upper boundary of the sending window, the method further includes: receiving an RRC connection reconfiguration message. The RRC connection reconfiguration message carries a first indication. The first indication is used to indicate that the sending window is to be configured. In this way, it is convenient for a subsequent terminal to perform subsequent processing according to the first indication.

[0032] Optionally, re-accessing the first access network device includes: sending a first RRC connection re-establishment request; the first RRC connection re-establishment request is used to request establishment of a second RRC connection; receiving a first RRC re-establishment message; the first RRC re-establishment message carries the configuration of the second RRC connection; sending a first RRC connection completion message; the first RRC connection completion message is used to indicate that the establishment of the second RRC connection is complete.

[0033] In a second aspect, a communication method is applied to a terminal, the method comprising: sending a second data packet. Receive a fourth status report. The fourth status report is used to indicate that the access network device has confirmed receipt of the third segment. The third segment is included in the fourth data packet. Receive a fifth status report. The fifth status report is used to indicate that the access network device has not received the fourth segment. The fourth segment and the third segment include at least part of the data overlap. According to the fifth status report, resend the fourth segment.

[0034] Optionally, the fourth status report and the fifth status report are received at the same time. When the fourth status report or the fifth status report is received, the third segment and the data in the fourth data packet other than the fourth segment are deleted after a delay of the second time period. Alternatively, the fifth status report is received later than the fourth status report within a third time period. When the fifth status report is received, the data in the fourth data packet other than the fourth segment are deleted after a delay of the third time period. After resending the fourth segment, the method further includes: receiving a third status report. The third status report is used to indicate that the access network device has confirmed receipt of the fourth data packet. According to the third status report, the remaining data in the fourth data packet is deleted, and the upper and lower boundaries of the sending window are configured.

[0035] Optionally, when receiving the fourth status report or the fifth status report, continue to store the fourth data packet. After resending the fourth segment, the method further includes: sending a fifth data packet, the SN of the fifth data packet being greater than the SN of the fourth data packet. Receiving a sixth status report. The sixth status report is used to indicate that the access network device has confirmed receipt of the fifth data packet. According to the sixth status report, delete the remaining data in the fourth data packet, and configure the upper and lower boundaries of the sending window.

[0036] In a third aspect, a terminal includes: a memory and one or more processors. The memory is coupled to the processor. The memory is used to store computer program code, and the computer program code includes computer instructions. When the processor executes the computer instructions, the terminal executes the communication method provided in the first aspect and any possible design thereof or the communication method provided in the second aspect and any possible design thereof.

[0037] In a fourth aspect, a chip system includes a processor and a communication interface. The processor is used to call and run a computer program stored in a storage medium from a storage medium to execute a communication method as provided in the first aspect and any possible design thereof or a communication method as provided in the second aspect and any possible design thereof.

[0038] In a fifth aspect, a computer-readable storage medium stores computer instructions thereon, which, when executed by a processor, implement the communication method provided in the first aspect and any possible design thereof, or the communication method provided in the second aspect and any possible design thereof.

[0039] In a sixth aspect, a computer program product comprises computer instructions, which, when executed by a processor, implement the communication method provided in the first aspect and any possible design thereof or the communication method provided in the second aspect and any possible design thereof.

[0040] It can be understood that the technical solutions provided in the third to sixth aspects above can respectively correspond to the communication processing methods provided in the aforementioned designs, and the beneficial effects that can be obtained are similar and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] Figure 1 is an interactive schematic diagram of a communication method;

[0042] Figure 2 A schematic diagram of an update sending window;

[0043] Figure 3 is an interactive diagram of another communication method;

[0044] Figure 4 is an interactive diagram of another communication method;

[0045] Figure 5 A schematic diagram of the composition of a chip module in a terminal provided in an embodiment of the present application;

[0046] Figure 6 An interactive schematic diagram of a communication method provided in an embodiment of the present application;

[0047] Figure 7 An interactive schematic diagram of another communication method provided in an embodiment of the present application;

[0048] Figure 8 An interactive schematic diagram of another communication method provided in an embodiment of the present application;

[0049] Fig. 9 An interactive schematic diagram of another communication method provided in an embodiment of the present application;

[0050] Fig.10 An interactive schematic diagram of another communication method provided in an embodiment of the present application;

[0051] Fig.11 A schematic diagram of the composition of a terminal provided in an embodiment of the present application;

[0052] Fig.12 A schematic diagram of the composition of a chip system provided in an embodiment of the present application. DETAILED DESCRIPTION

[0053] In the following, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of this embodiment, unless otherwise specified, "plurality" means two or more.

[0054] The technical solution provided in the embodiments of the present application can be applied to various wireless communication networks, such as: global system for mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, universal mobile telecommunication system (UMTS) system, general packet radio service (GPRS) system, long term evolution (LTE) system, long term evolution advanced (LTE-A) system, world wide interoperability for microwave access (WiMAX) system, fifth generation mobile communication technology (5th Generation Mobile Communication Technology) system. The terms "network" and "system" are interchangeable.

[0055] In the embodiment of the present application, a base station (BS) may be a device for communicating with a user equipment (UE) or other communication sites such as a relay site, and the base station may provide communication coverage for a specific physical area. For example, the base station may be a base transceiver station (BTS) or a base station controller (BSC) in GSM or CDMA; it may also be a node B (NB) in UMTS or a radio network controller (RNC) in UMTS; it may also be an evolved Node B (eNB or eNodeB) in LTE; it may also be a next generation NodeB (gNB) in 5G NR; or it may be other access network devices that provide access services in a wireless communication network, which is not limited by the present invention.

[0056] The following description is made by taking the access network device as a base station as an example.

[0057] Currently, the UE can transmit data by sending a data packet to the base station. The data packet may include a protocol data unit (PDU) / service data unit (SDU). The data packet carries the data to be sent by the UE. Due to interference in the transmission link, one or more data packets sent by the UE to the base station may be lost or fail to be sent during the transmission process.

[0058] In order to ensure the performance of data transmission between the UE and the base station, the base station can generate a status report based on the reception status of the data packet and send the status report to the UE, so that the UE can obtain the data packet reception status of the base station based on the received status report.

[0059] Exemplary, reference Figure 1 , Figure 1 The diagram shows the interactive process of data packet transmission between the UE and the base station.

[0060] like Figure 1 As shown, the program includes:

[0061] S101. An RRC connection is established between a UE and a base station.

[0062] Exemplarily, the UE sends an RRC connection establishment request to the base station. The RRC connection establishment request may be RRCConnectionRequest.

[0063] Correspondingly, after receiving the RRC connection establishment request, the base station sends an RRC connection establishment message (such as RRCConnectionsetup) to the UE.

[0064] Then, the UE may perform RRC connection establishment according to the RRC connection establishment message. In this example, after completing the RRC connection establishment, the UE feeds back an RRC connection establishment completion message to the base station. For example, the RRC connection establishment completion message may be RRCConnectionComplete.

[0065] Thus, an RRC connection is established between the UE and the base station. For example, the RRC connection may be a first RRC connection.

[0066] S102. The UE sends data packet 1 with SN=n1 to the base station.

[0067] It should be noted that, in this embodiment, when the UE transmits data to the base station, the data to be sent can be sent to the base station through a data packet (such as PDU / SDU) according to the transmission capacity of the network and the size of the data to be sent, so as to send the entire segment of the data to be sent to the base station. Alternatively, the data to be sent can be sent to the base station through multiple data packets. The multiple data packets may include different segments of the data to be sent, thereby sending the segments of the data to be sent to the base station.

[0068] In some embodiments, the UE may send a data packet 1 to the base station. The data packet 1 is configured with a sequence number (SN). The SN is used to identify the data packet 1. The SN of the data packet 1 corresponds to SN=n1.

[0069] As an implementation method, the UE may send data packet 1 to the base station in segments. That is, the UE may split data packet 1 into at least two sub-data packets, and transmit the at least two sub-data packets to the base station in sequence. The at least two sub-data packets include different segments of data packet 1.

[0070] For example, the at least two sub-data packets are data packet 11, data packet 12, and data packet 13, where data packet 11, data packet 12, and data packet 13 sequentially include the first segment, the last segment, and the middle segment of data packet 1. Data packet 11, data packet 12, and data packet 13 all include SN=n1. The UE can send data packet 1 to the base station in segments by sequentially sending data packet 11, data packet 12, and data packet 13 to the base station.

[0071] It should be noted that, in some implementations, a segment indication (SI) is also configured in the data packet. Generally, the SI may include one of a first value, a second value, a third value, and a fourth value. Among them, the first value is used to indicate that the data packet includes complete data to be sent, and the first value may include 0. The second value is used to indicate that the data packet includes the first segment of data to be sent, and the second value may include 1. The third value is used to indicate that the data packet includes the last segment of data to be sent, and the third value may include 2. The fourth value is used to indicate that the data packet includes an intermediate segment of data to be sent, and the fourth value may be 3. The intermediate segment is between the first segment and the last segment of the data to be sent.

[0072] In combination with the above description, in this example, data packet 11 may further include SI=1. The SI=1 is used to indicate that data packet 11 includes the first segment of data packet 1. Similarly, data packet 12 may further include SI=2. The SI=2 is used to indicate that data packet 12 includes the last segment of data packet 1. Data packet 13 may further include SI=3. The SI=3 is used to indicate that data packet 13 includes the middle segment of data packet 1.

[0073] In this way, after receiving data packets 11, data packet 12 and data packet 13, the base station determines the positions of data packets 11, data packet 12 and data packet 13 in data packet 1 based on the SI carried in data packets 11, data packet 12 and data packet 13, and then can reassemble data packets 11, data packet 12 and data packet 13 into a complete data packet 1.

[0074] It should be noted that the above description of the data packets 11, 12 and 13 is only an example. In the present application, there is no limitation on the division method of the data packet 1.

[0075] As another implementation, the UE may send the entire data packet 1 to the base station, that is, the UE does not divide the data packet 1, and directly sends the data packet 1 to the base station at one time.

[0076] In this implementation, the data packet 1 may also be configured with an SI, and the SI corresponds to SI = 0. The SI is used to indicate that the data packet 1 includes complete data.

[0077] S103. The base station sends an ACK message 11 to the UE.

[0078] Exemplarily, the ACK message 11 corresponds to the base station's confirmation of the data packet 1 with SN=n1. That is, the base station has received the data packet 1 with SN=n1.

[0079] For example, the ACK message 11 may be ACK_SN=n1+1.

[0080] In some other implementations, before sending the data packet 1 with SN=n1, the UE also sends a data packet with SN less than n1 to the base station. In this implementation, the ACK message 11 also corresponds to the base station's confirmation of the data packet with SN less than n1. That is, the base station has received the data packet with SN less than or equal to n1.

[0081] S104. After receiving the ACK message 11, the UE deletes the data packet 1 from the cache.

[0082] It should be noted that the UE always stores the data packet 1 in the cache in the UE before receiving the ACK message 11 from the base station. In this embodiment, after receiving the ACK message 11, the UE can delete the data packet 1 from the cache.

[0083] S105. The UE updates state variables 1 and 2 of the sending window.

[0084] In the examples of this application, reference is made to Figure 2 , a sending window is also configured in the UE. The sending window is configured with state variable 1 and state variable 2. The sending window is used to limit the range of SNs of data packets that the UE can send. Specifically, the SN of the data packet needs to be greater than or equal to state variable 1 and less than state variable 2. In this way, the UE can send the data packet corresponding to the SN to the base station. Otherwise, the UE will not send the data packet to the base station.

[0085] For example, taking the size of the sending window as L1 and the state variable 1 as a, the state variable 2 is a+L1.

[0086] In addition, in combination with the description in S102 above, n1 needs to be greater than or equal to a and less than a+L1. In this way, the UE can send the data packet 1 to the base station.

[0087] In this embodiment, after receiving the ACK message 11, the UE needs to update the state variable 1 and the state variable 2 of the sending window.

[0088] Specifically, taking the ACK message 11 as ACK_SN=n1+1 as an example, the UE modifies the state variable 1 from a to n1+1 according to the ACK message 11. Correspondingly, the state variable 2 is modified from a+L1 to n1+1+L1.

[0089] In this way, the range of SNs to which the UE can subsequently send data packets is from n1+1 to n1+L1.

[0090] In some other embodiments of the present application, the state variable 1 may also be referred to as a first state variable, and the state variable 2 may also be referred to as a second state variable.

[0091] Exemplary, reference Figure 3 , Figure 3 Another interactive process of data packet transmission between UE and base station is shown.

[0092] S301. An RRC connection is established between a UE and a base station.

[0093] S302. The UE sends data packet 1 with SN=n1 to the base station.

[0094] In this embodiment, the implementation of S301 and S302 corresponds to S101 and S102. For the specific content, please refer to the description in S301 and S302, which will not be repeated here.

[0095] S303: The base station sends a NACK message 31 to the UE.

[0096] In some embodiments, after the UE sends the data packet 1, the base station may send a status report to feedback the reception status of the data packet 1 to the UE, so that the UE can perform subsequent data transmission processing according to the status report.

[0097] Exemplarily, the status report may include a NACK message 31. The NACK message 31 includes an SN and a location identifier. The SN corresponds to the SN of the data not received by the base station, and the location identifier is used to indicate the location of the data not received by the base station.

[0098] For example, after the UE sends data packet 1, the base station may send a NACK message 31 to the UE. The NACK message 31 is used to indicate that segment 1 is not received. Segment 1 is part of the data in data packet 1. The NACK message 31 includes SN=n1 and position identifier 1 of segment 1. Position identifier 1 is used to indicate the position of segment 1 in data packet 1, and the position identifier 1 may include identifier 1 and identifier 2. Identifier 1 is used to indicate the offset of the first byte in segment 1 in data packet 1, and identifier 2 is used to indicate the offset of the last byte in segment 1 in data packet 1.

[0099] Taking segment 1 corresponding to the data of the mth to nth bytes in data packet 1 as an example, the identifier 1 may be SOstart=m-1, and SOstart=m-1 corresponds to the offset of the first byte in segment 1 in data packet 1 being m-1 bytes. The identifier 2 may be SOend=n-1, and SOend=n-1 corresponds to the offset of the last byte in segment 1 in data packet 1 being n-1 bytes.

[0100] Correspondingly, the NACK message 31 may be NACK_SN=n1, SOstart=m-1, SOend=n-1.

[0101] In the embodiment of the present application, the NACK message may also carry a retransmission indication 1. The retransmission indication 1 is used to instruct the UE to retransmit the segment 1 that the base station has not received.

[0102] In some other embodiments of the present application, the NACK message 31 may also be referred to as a first status report. Data packet 1 may also be referred to as a first data packet. Segment 1 may also be referred to as a fifth segment. Data in data packet 1 other than segment 1 may also be referred to as a first segment.

[0103] S304. The UE deletes the data except segment 1 in data packet 1.

[0104] Exemplarily, after receiving the NACK message 31 in S303 , the UE may delete the data except the segment 1 in the data packet 1 .

[0105] In this embodiment, after receiving the NACK message 31, the UE may also perform the process in S305.

[0106] S305. The UE retransmits segment 1 to the base station.

[0107] Exemplarily, after receiving the NACK message 31 , the UE may retransmit the data that is not received by the base station according to the NACK message 31 .

[0108] For example, taking the location identifier 1 of segment 1 carried in the NACK message 31 as an example, after receiving the NACK message 31 , the UE may retransmit segment 1 to the base station according to the NACK message 31 .

[0109] S306. The base station sends a NACK message 32 to the UE.

[0110] In some embodiments, after receiving the NACK message 31, the UE also receives a NACK message 32. Similar to the NACK message 31, the NACK message 32 carries the SN and location identifier corresponding to the data not received by the base station.

[0111] For example, if the base station does not receive segment 2 in data packet 1, segment 2 is different from segment 1. Then the NACK message 32 carries SN=n1 and the location identifier 2 of segment 2.

[0112] Among them, the implementation method of location identifier 2 is similar to that of location identifier 1. The specific content can be referred to the above description and will not be repeated here.

[0113] In some implementations, segment 2 and segment 1 are two different parts of data in data packet 1.

[0114] In some other implementations, segment 2 includes segment 1 and segment 3. Segment 3 is also included in data packet 1, and segment 3 is different from segment 1.

[0115] In this embodiment, the NACK message 32 also carries a retransmission indication 2. The retransmission indication 2 is used to instruct the UE to retransmit the segment 2 that the base station has not received.

[0116] The above example is described by taking the case where the UE first receives the NACK message 31 and then receives the NACK message 32. In other embodiments, the UE may receive the NACK message 31 and the NACK message 32 at the same time. In this embodiment, after receiving the NACK message 31 and the NACK message 32, the UE may continue to perform the processing in S304 and S305.

[0117] It should be noted that, taking segment 2 being different from segment 1 as an example, after receiving NACK message 31, UE will perform the processing in S304, so that only the part of segment 1 in data packet 1 is stored in UE. As a result, after receiving NACK message 32, UE cannot find segment 2 in the cache, resulting in UE being unable to retransmit segment 2 according to NACK message 32.

[0118] Similarly, when segment 2 includes segment 1 and segment 3 in data packet 1 except segment 1, the UE cannot find segment 3 in the cache after receiving NACK message 32, which also causes the UE to be unable to retransmit segment 3 in segment 2 according to NACK message 32.

[0119] In some other embodiments of the present application, the NACK message 32 may also be referred to as a second status report. Segment 2 may also be referred to as a second segment.

[0120] S307. The UE sends data packet 2 with SN=n2 to the base station.

[0121] In some embodiments, after the UE fails to retransmit segment 2, it can continue to send other data packets to be sent to the base station.

[0122] It should be noted that, since the UE cannot retransmit segment 2, the UE will not receive the acknowledgment of the data packet 1 with SN=n1 from the base station in the future. At this time, the state variable 1 of the sending window will always remain at n1, and the state variable 2 will always remain at n1+L1. In other words, the UE can continue to send data packets with SN greater than or equal to n1 and SN less than n1+L1 in the future.

[0123] For example, the UE may send data packet 2 with SN=n2 to the base station. Data packet 2 is a data packet that the UE has not sent yet. Wherein, n2 is greater than n1 and less than n1+L1. That is, in this example, n2 may include one of n1+1, n1+2, ..., n1+L1-1.

[0124] In S307, the implementation manner of the UE sending the data packet 2 to the base station is similar to the implementation manner of sending the data packet 1. For details, please refer to the description in S102, which will not be repeated here.

[0125] In some other embodiments of the present application, SN=n1 is included in the first SN, and SN=n1+L1-1 is included in the second SN.

[0126] In such Figure 3 In the example, after the UE sends the data packet 1, the UE first receives the NACK message 31 and then receives the NACK message 32. In other embodiments, the UE may receive the NACK message 31 and the NACK message 32 at the same time.

[0127] In this embodiment, when the UE receives NACK message 31 and NACK message 32 simultaneously, it can perform the processing in S304 and S305 according to NACK message 31. At this time, the UE still cannot retransmit segment 2 according to NACK message 32.

[0128] In another implementation, when the UE receives NACK message 31 and NACK message 32 simultaneously, it can delete data except segment 2 in data packet 1 according to NACK message 32. This will also cause the UE to be unable to retransmit segment 1 according to NACK message 31.

[0129] Exemplary, reference Figure 4 , Figure 4 Another interactive process of data packet transmission between a UE and a base station is shown.

[0130] S401. An RRC connection is established between a UE and a base station.

[0131] S402. The UE sends data packet 1 with SN=n1 to the base station.

[0132] In this embodiment, the implementation of S401 and S402 corresponds to S101 and S102. For the specific content, please refer to the description in S301 and S302, which will not be repeated here.

[0133] S403: The base station sends an ACK message 41 to the UE.

[0134] Exemplarily, after the UE sends data packet 1 to the base station, the base station may send an ACK message 41 to the UE. Similar to the ACK message 11, the ACK message 11 corresponds to the base station's confirmation of the data packet 1 with SN=n1.

[0135] In some other implementations, the UE sends a data packet with SN less than n1 to the base station before sending the data packet 1 with SN=n1. In this implementation, the ACK message 41 may also correspond to the base station's confirmation of the data packet with SN less than n1.

[0136] In some other embodiments of the present application, the ACK message 41 may also be referred to as a first status report. The data packet 1 may also be referred to as a first segment.

[0137] S404. UE deletes data packet 1.

[0138] In combination with the above description, before receiving the acknowledgment message of the base station for the data packet 1, the UE will store the data packet 1 in the UE's buffer. After receiving the ACK message 41, the UE can delete the data packet 1 stored in the buffer.

[0139] S405. The base station sends a NACK message 42 to the UE.

[0140] In some embodiments, after sending the ACK message 41, the base station also sends a NACK message 42 to the UE. The NACK message 42 corresponds to the base station not receiving the data packet 1.

[0141] Specifically, NACK message 42 corresponds to the base station not receiving part of the data in data packet 1. For example, NACK message 42 may be NACK message 31 or NACK message 32. For detailed description of NACK message 31 and NACK message 32, reference may be made to the description in S303 and S306, which will not be repeated here.

[0142] In some other embodiments, the NACK message 42 corresponds to the base station not receiving the data packet 1. In this implementation, the NACK message 42 may include SN=n1 and the location identifier 3 corresponding to the data packet 1.

[0143] In the above two implementations, the NACK message 42 may also carry a retransmission indication 3. The retransmission indication 3 is used to instruct the UE to retransmit the data packet 1 (such as segment 1 in data packet 1 or data packet 1, etc.) not received by the base station.

[0144] In the description of S405, the example is taken that the UE first receives the ACK message 41 and then receives the NACK message 42. In other implementations, the UE may simultaneously receive the ACK message 41 and the NACK message 42 sent by the base station. In this implementation, the UE still performs the processing in S404.

[0145] In S403 to S405, after receiving ACK message 41, UE will perform the process in S404, so that data packet 1 with SN=n1 is no longer stored in the UE cache. Therefore, after receiving NACK message 42, UE cannot retransmit segment 1 or data packet 1 in data packet 1 according to NACK message 42.

[0146] In other embodiments of the present application, the NACK message 42 may also be referred to as a second status report.

[0147] S406. The UE sends data packet 2 with SN=n2 to the base station.

[0148] In this embodiment, the implementation of S406 corresponds to S307. For the specific content, please refer to the description in S307, which will not be repeated here.

[0149] In such Figure 3 and Figure 4 In the example, since the UE cannot retransmit the data that the base station has not received, and thus cannot receive the base station's confirmation for data packet 1, the UE does not update the lower boundary (state variable 1) and upper boundary (state variable 2 minus 1) of the sending window. As a result, when the SN of the data packet sent by the UE reaches the upper boundary of the sending window, the UE cannot continue to transmit data with the base station, causing the UE's communication to be interrupted.

[0150] To solve the above problems, an embodiment of the present application provides a communication method and a terminal. Based on this method, after the UE detects that the data to be retransmitted has been confirmed to have been received by the base station, the radio link failure (Radio Link Failure, RLF) is triggered, and the RRC connection is re-established with the base station. After the UE re-establishes the RRC connection with the base station, the lower and upper boundaries of the sending window are reset. As a result, the UE can subsequently configure the SN of the data packets that have not been sent in the UE according to the upper and lower boundaries of the sending window. This allows the UE to continue to send data packets whose SN is between the lower and upper boundaries of the sending window to the base station, thereby restoring the wireless communication of the UE.

[0151] It should be noted that in the following description, UE is taken as an example as a device used by a user.

[0152] In other embodiments of the present application, the UE may also be replaced by any other electronic device with a communication function. The electronic device may also be referred to as a terminal device or a terminal.

[0153] Exemplarily, the electronic device in the embodiment of the present application may include at least one of a mobile phone, a foldable electronic device, a tablet computer, a desktop computer, a laptop computer, a handheld computer, a notebook computer, an ultra-mobile personal computer (UMPC), a netbook, a cellular phone, a personal digital assistant (PDA), an augmented reality (AR) device, a virtual reality (VR) device, an artificial intelligence (AI) device, a wearable device, an in-vehicle device, a smart home device, or a smart city device. The embodiment of the present application does not impose any special restrictions on the specific type of the electronic device.

[0154] As an example, Figure 5 A schematic diagram of the composition of an electronic device provided in an embodiment of the present application.

[0155] like Figure 5 As shown, the terminal may include a multi-layer structure. In this example, the terminal may include a NAS layer 501, an RRC layer 502, a PDCP layer 503, an RLC layer 504, a MAC layer 505, and a PHY layer 506.

[0156] NAS is the abbreviation of Non Access Stratum, and NAS layer 501 is also the non-access layer. NAS layer 501 is mainly responsible for providing control and management of the non-access layer. For example, EPS bearer management, authentication, mobility management in the idle state (i.e., ECM-IDLE state) of EPS connection management mode, responsible for generating paging messages for UEs in ECM-IDLE state, security control and other functions.

[0157] The RRC layer 502 is a high-level layer of the control plane, which is mainly responsible for controlling L1 / L2 to complete air interface resource transmission and providing information transmission services for the NAS layer 501. Exemplarily, the RRC layer 502 can be used to manage functions such as system message broadcasting, RRC connection control, mobility management, and measurement configuration reporting. Among them, RRC connection control management includes paging, establishing / modifying / suspending / resuming / releasing RRC connection, initial security activation, establishing / modifying / activating SRB / DRB, cell management in DC and CA modes, and radio link failure recovery.

[0158] PDCP is the abbreviation of Packet Data Convergence Protocol, and the PDCP layer 503 is also the packet data convergence protocol layer. The PDCP layer 503 is used to process RRC messages on the control plane and Internet Protocol (IP) packets on the user plane. Exemplarily, on the user plane, after the PDCP layer 503 obtains the IP data packet from the upper layer, it can perform header compression and encryption on the IP data packet, and then submit it to the RLC layer 504. The PDCP layer 503 also provides the upper layer with in-order submission and duplicate packet detection functions. On the control plane, the PDCP layer 503 provides signaling transmission services for the upper layer RRC, implements encryption and consistency protection of RRC signaling, and implements decryption and consistency checking of RRC signaling in the reverse direction.

[0159] RLC is the abbreviation of Radio Link Control, and RLC layer 504 is the radio link control layer. RLC layer 504 mainly provides radio link control functions, and provides services such as segmentation, retransmission control, and on-demand transmission for the upper layer. RLC layer 504 includes three transmission modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledged Mode (AM), and mainly provides functions such as error correction, segmentation, and reassembly.

[0160] MAC is the abbreviation of Media Access Control, and the MAC layer 505 is the media access control layer. The MAC layer 505 is used to provide mapping between logical channels and transport channels; multiplex MAC SDUs from one or more logical channels into a transport block and pass it to the PHY layer 506; demultiplex the transport block from the PHY layer 506 into multiple MAC SDUs and pass them to one or more logical channels; report scheduling information; perform error correction through HARQ; manage the priority between users through dynamic scheduling; and manage the priority of logical channels.

[0161] The PHY layer 506 is the physical layer. The PHY layer 506 provides mechanical, electronic, functional and regulatory characteristics for creating, maintaining and removing the physical link required for data transmission. The physical layer can be used to ensure that the original data can be transmitted on various physical media.

[0162] like Figure 5As shown, in the embodiment of the present application, the above NAS layer 501, RRC layer 502, PDCP layer 503, RLC layer 504, MAC layer 505, and PHY layer 506 can be integrated in the first chip module of the terminal. For example, the first chip module can be a modem of the terminal.

[0163] In addition, in some embodiments, an application layer 507 may be provided in the terminal. The application layer 507 may be provided on the upper layer of the NAS layer 501. The application layer may be used to process and judge the signaling from the NAS layer, and send communication signaling and data to the NAS layer.

[0164] In such Figure 5 In the example of , the application layer 507 can be set in the second chip module of the terminal. For example, the second chip module can be an application processor (Application Processor Unit, referred to as APU or AP) of the terminal.

[0165] In other embodiments, the application 507, and the NAS layer 501, the RRC layer 502, the PDCP layer 503, the RLC layer 504, the MAC layer 505, and the PHY layer 506 may also be in the same chip module. The embodiment of the present application does not specifically limit the division and setting of each protocol layer in the terminal.

[0166] The solution provided in the embodiments of the present application is described in detail below with reference to the accompanying drawings.

[0167] An embodiment of the present application provides a communication method and a terminal, which enable a UE to reconfigure the lower and upper boundaries of a sending window when the UE cannot query data that needs to be retransmitted and the SN of a subsequently sent data packet reaches the upper boundary of the sending window, thereby allowing the UE to continue to transmit data with the base station subsequently.

[0168] Exemplary, reference Figure 6 ,by Figure 3 The scenario shown is taken as an example. Solution A provided in the embodiment of the present application is illustrated by way of example.

[0169] like Figure 6 As shown, the program may include:

[0170] S601: An RRC connection is established between a UE and a base station.

[0171] S602. The UE sends data packet 1 with SN=n1 to the base station.

[0172] S603: The base station sends a NACK message 31 to the UE.

[0173] S604. The UE deletes the data except segment 1 in data packet 1.

[0174] S605. The UE retransmits segment 1 to the base station.

[0175] S606. The base station sends a NACK message 32 to the UE.

[0176] In the embodiment of the present application, the implementation of S601 to S606 corresponds to S301 to S306. For the specific content, please refer to the description in S301 to S306, which will not be repeated here.

[0177] S607 . When the UE detects that segment 2 has been confirmed to be received by the base station, the UE records the time T1 at which the NACK message 32 is received.

[0178] In some embodiments of the present application, in combination with the above description, NACK message 31 corresponds to the base station confirming receipt of data other than segment 1 in data packet 1. At this time, when the UE receives NACK message 32, it detects that the base station has received segment 2 according to the previously received NACK message 31. At this time, the UE can record the time T1 when the NACK message 32 is received.

[0179] In some other embodiments, time T1 may also be referred to as the first time.

[0180] Specifically, the UE may record the time T1 at which the NACK message 32 is received when detecting that the data in segment 2 and data packet 1 other than segment 1 include at least a portion of data overlap.

[0181] As another implementation, after receiving the NACK message 32, the UE needs to retransmit the segment 2 that the base station has not received according to the NACK message 32. Before the UE retransmits the segment 2 to the base station, it needs to query the segment 2 in the cache.

[0182] According to the description in S306, segment 2 is different from segment 1. After receiving NACK message 32, UE deletes data except segment 1 in data packet 1. Therefore, UE cannot query segment 2. At this time, UE can record time T1 when NACK message 32 is received.

[0183] In some other embodiments of the present application, the UE may trigger a radio link failure RLF when detecting that at least part of the data in segment 2 and data packet 1 other than segment 1 overlap. After triggering the RLF, the UE may continue to perform the processing in S612 to S617.

[0184] The following will take the first embodiment as an example to further explain the solution provided by the present application.

[0185] S608. The UE sends data packet 2 with SN=n2 to the base station.

[0186] In the embodiment of the present application, after the UE fails to retransmit segment 2, it can continue to send data packet 2 to the base station. The data packet 2 is a data packet that the UE has not yet sent to the base station.

[0187] The SN of data packet 2 is SN=n2. n2 may include one of n1+1, n1+2, ..., n1+L1-1.

[0188] In this embodiment, the implementation of S608 corresponds to S307. For the specific content, please refer to the description in S307, which will not be repeated here.

[0189] S609. When the UE detects that n2+1 is equal to the state variable 2, the UE records the current time as time T2.

[0190] Combined with the above description, since the UE cannot retransmit segment 2, the UE will not receive the base station's confirmation of data packet 1, which causes the state variable 1 of the sending window to always remain at n1, and the state variable 2 of the sending window to always remain at n1+L1.

[0191] In an embodiment of the present application, when the UE detects that SN=n2 plus 1 corresponding to the currently transmitted data packet 2 is equal to the state variable 2 of the transmitting window, the UE records the current time as time T2.

[0192] In other embodiments of the present application, time T2 may also be referred to as the second time.

[0193] S610. The base station sends a NACK message 61 to the UE.

[0194] In some embodiments of the present application, after the UE sends data packet 2 with SN=n2 to the base station, a NACK message 61 may be received. In this example, the NACK message 61 may be a NACK message 32. That is, except for segment 2 in data packet 1, the base station has received all data before SN=n2.

[0195] The above embodiment takes the example that segment 2 and segment 1 are two different parts in data packet 1 to illustrate the NACK message 61. In other embodiments of the present application, taking the example that segment 2 includes segment 1 and segment 3, the NACK message 61 may correspond to the base station not receiving segment 3. The NACK message 61 may include SN=n1 and the location identifier 4 corresponding to segment 3.

[0196] In this embodiment, after receiving the NACK message 61, the UE still cannot retransmit the data not received by the base station. At this time, the UE can continue to perform the process in S608.

[0197] S611. The UE triggers RLF and accesses cell A based on the time difference between time T1 and time T2 being greater than time T3.

[0198] In an embodiment of the present application, after the UE completes the operations in S607 and S609, RLF may be triggered when the time difference between the time T1 recorded in S607 and the time T2 recorded in S609 is greater than the duration T3.

[0199] In this embodiment, after triggering RLF, the UE may preferentially access a currently known cell according to a configured policy.

[0200] For example, the UE may camp on cell A. The cell A may be a cell where the UE has camped before, or the cell A may be a cell where other UEs in the base station have not camped.

[0201] In other embodiments of the present application, the duration T3 may also be referred to as the first duration.

[0202] It is understandable that, in the process of data transmission between the UE and the base station, in addition to the problem that the upper and lower boundaries of the sending window remain unchanged due to the UE receiving abnormal status reports such as NACK message 31 and NACK message 32, there are other reasons that cause the upper and lower boundaries of the sending window to remain unchanged, such as network congestion or poor channel quality in the uplink.

[0203] In this example, the UE executes the process in S611 so that the UE can trigger RLF and access cell A in response to the situation where the upper and lower boundaries of the sending window remain unchanged due to the reception of an abnormal status report.

[0204] S612: The UE initiates an RRC connection re-establishment procedure to the base station.

[0205] In an embodiment of the present application, when the UE resides in cell A, it can continue to initiate an RRC connection re-establishment process to the base station where cell A is located.

[0206] Exemplarily, the UE may send an RRC connection re-establishment request to the base station.

[0207] Correspondingly, after receiving the RRC reestablishment request, the base station sends an RRC reestablishment message to the UE. The RRC reestablishment message may include RRCConnectionReestablishment.

[0208] After receiving the RRC reestablishment message, the UE may perform RRC connection configuration according to the RRC reestablishment message, and send an RRC connection completion message to the base station in an uplink channel. The RRC connection completion message may include RRCConnectionReestablishmentComplete.

[0209] In this way, a second RRC connection can be established between the UE and the base station.

[0210] S613: The base station sends an RRC connection reconfiguration message 62 to the UE.

[0211] In an embodiment of the present application, after the UE establishes a second RRC connection with the base station, the base station may send an RRC connection reconfiguration message 62 to the UE. The RRC connection reconfiguration message 62 may carry an indication 1. The indication 1 is used to instruct the UE to configure a sending window.

[0212] For example, the RRC connection reconfiguration message 62 may include RRCConnectionReconfiguration.

[0213] In other embodiments of the present application, indication 1 may also be referred to as the first indication.

[0214] S614. The UE resets the state variable 1 of the sending window to n0, and resets the state variable 2 to n0+L1.

[0215] Exemplarily, after receiving indication 1 in the RRC connection reconfiguration message 62, the UE may reset the state variable 1 of the sending window to n0 and reset the state variable 2 to n0+L2.

[0216] For example, n0 may be 0. Correspondingly, the state variable 1 of the sending window is 0, and the state variable 2 of the sending window is L2.

[0217] In some other embodiments of the present application, SN=n0 is included in the third SN, and SN=n0+L2 is included in the fourth SN.

[0218] S615. The UE sends an RRC connection reconfiguration complete message 63 to the base station.

[0219] In an embodiment of the present application, after completing the operation of S614, the UE may send an RRC connection reconfiguration completion message 63 to the base station.

[0220] For example, the RRC connection reconfiguration complete message 63 may be RRCReconfigurationComplete.

[0221] Thus, the RRC connection reconfiguration is completed between the UE and the base station.

[0222] It can be understood that after the UE and the base station complete the RRC connection reconfiguration, the UE can continue to transmit data with the base station based on the current sending window.

[0223] As a specific example, the UE can continue to transmit data with the base station by executing the operations in S616 and S617.

[0224] S616. The UE configures the SN of data packet 3 as SN=n0.

[0225] In some embodiments of the present application, a data packet 3 is stored in the UE, and the data packet 3 is a data packet not sent in the UE. The data packet 3 may carry user service data of the application layer in the UE, etc.

[0226] In this example, the UE may configure the SN of the data packet 3 to be SN=n0 according to the state variable 1 of the current sending window.

[0227] In some other embodiments of the present application, data packet 3 may become the second data packet. SN=n0 to SN=n0+L2-1 are included in the fifth SN.

[0228] S617. The UE sends data packet 3 with SN=n0 to the base station.

[0229] Exemplarily, after configuring the SN of data packet 3 as SN=n0, the UE can send data packet 3 to the base station. The implementation method of the UE sending data packet 3 to the base station is similar to the implementation method of sending data packet 1. For details, please refer to Figure 1 The description in S102 will not be repeated here.

[0230] In some embodiments of the present application, after the UE sends the data packet 3 to the base station, the base station may send an ACK message 64 to the UE. The ACK message corresponds to the base station's confirmation of the data packet 3 with SN=n0. That is, the base station has received the data packet 3 with SN=n0.

[0231] In this embodiment, after receiving the ACK message 64, the UE may perform the processing from S104 to S105 to update the sending window.

[0232] For example, the UE may modify the state variable 1 of the sending window from n0 to n0+1. Correspondingly, the state variable 2 of the sending window may be modified from n0+L2 to n0+1+L2.

[0233] It should be noted that in Figure 6In the example shown, the UE is explained by taking the example that the UE first receives the NACK message 31 and then receives the NACK message 32. In other embodiments of the present application, the UE may receive the NACK message 31 and the NACK message 32 at the same time.

[0234] As an implementation, when the UE receives the NACK message 31 and the NACK message 32 at the same time, the UE performs the process in S604 according to the NACK message 31. In this implementation, the UE and the base station may continue to perform the processes in and after S605.

[0235] As another implementation manner, when the UE receives the NACK message 31 and the NACK message 32 at the same time, the UE deletes the data except the segment 2 in the data packet 1 according to the NACK message 32, and retransmits the segment 2 to the base station.

[0236] Next, similar to the process in S607, when the UE receives the NACK message 31, it detects that the segment 1 has been confirmed to be received by the base station according to the NACK message 32 received at the same time. At this time, the UE can record the time when the NACK message 31 or the NACK message 32 is received. In this implementation, the UE and the base station can continue to perform the processes such as S608 and thereafter.

[0237] In addition, Figure 6 In Figure 3 S603 to S607 are described by taking the scenario of FIG. 4 as an example. In some other embodiments of the present application, after the UE sends the data packet 1 with SN=n1, it can receive the ACK message 41 in S403. Figure 4 According to the description in, the UE and the base station can continue to perform operations as in S404 and S405.

[0238] Taking the NACK message 42 in S405 corresponding to the base station not receiving segment 1 in data packet 1 as an example, in this embodiment, when the UE receives the NACK message 42, it detects that segment 1 has been confirmed to be received by the base station according to the ACK message 41, and can record the time T0 when the NACK message 42 is received. Then, the UE can continue to perform the processing in S608 to S617 with the base station. Among them, when the UE performs the operation in S611, when the time difference between time T0 and time T2 is greater than T3, RLF is triggered and accesses cell A. The specific implementation method of this step can refer to the description in S611, which will not be repeated here.

[0239] In such Figure 6In the scheme A shown, when the UE detects that the data to be retransmitted has been confirmed to have been received by the base station, and the SN of the subsequently sent data packet reaches the upper boundary of the sending window, the UE triggers RLF to reconfigure the state variables 1 and 2 of the sending window. The UE can subsequently configure the SN of the data packet according to the reconfigured state variable 1 (such as n0), and can transmit the data packet to the base station based on the current sending window. In addition, the UE can continue to maintain wireless communication with the base station to achieve subsequent data transmission.

[0240] In other embodiments of the present application, a scheme B is provided to solve the problem of communication interruption in UE. Based on scheme B, when the UE receives confirmation from the base station for a data packet or a segment in a data packet, it will continue to cache the data packet or the segment in the data packet. So that when the UE subsequently receives a NACK message from the base station for the data packet or the segment in the data packet, it can retransmit the data packet or the segment in the data packet to the base station. It is ensured that the UE can subsequently trigger the UE to update the upper and lower boundaries of the sending window. This prevents the SN of the data packet subsequently sent by the UE from reaching the upper boundary of the sending window, so that the UE can always maintain communication with the base station.

[0241] Exemplary, reference Figure 7 , still Figure 3 The scenario shown is taken as an example. Scheme B1 in Scheme B provided in the embodiment of the present application is illustrated by way of example.

[0242] like Figure 7 As shown, the scheme B1 may include:

[0243] S701: An RRC connection is established between a UE and a base station.

[0244] S702. The UE sends data packet 1 with SN=n1 to the base station.

[0245] S703: The base station sends a NACK message 31 to the UE.

[0246] In some other embodiments of the present application, the NACK message 31 is included in the fourth status report. The data in the data packet 1 except the segment 1 can also be called the third segment.

[0247] In the embodiment of the present application, the implementation method of S701 to S703 corresponds to S301 to S303. For the specific content, please refer to the description in S301 to S303, which will not be repeated here.

[0248] S704. The base station sends a NACK message 32 to the UE.

[0249] In some embodiments of the present application, the base station sends a NACK message 32 to the UE while sending a NACK message 31 to the UE. The NACK message 32 is used to indicate that segment 2 is not received. For detailed description of the NACK message 32, reference can be made to the description in S306, which will not be repeated here.

[0250] In some other embodiments of the present application, the NACK message 32 is included in the fifth status report. Segment 2 may also be referred to as the fourth segment.

[0251] It should be noted that, in the embodiment of the present application, the base station simultaneously sends NACK message 31 and NACK message 32 to the UE, corresponding to indicating that the base station has received data other than segment 1 and segment 2 in data packet 1.

[0252] In this implementation, the UE may simultaneously receive the NACK message 31 and the NACK message 32. In this case, the UE may continue to perform the process in S707 or S710.

[0253] S705. The UE retransmits segment 1 to the base station.

[0254] In the present application, after receiving the NACK message 31 , the UE may retransmit segment 1 to the base station according to the NACK message 31 .

[0255] S706. The UE retransmits segment 2 to the base station.

[0256] In the embodiment of the present application, before executing the operation of S707 or S710, the UE receives NACK message 32. At this time, the UE still stores segment 2. Therefore, after receiving NACK message 32, the UE can retransmit segment 2 to the base station according to NACK message 32.

[0257] The specific implementation of S707 and S710 will be described in detail in the subsequent content.

[0258] S707 : After waiting for a time period of T4 , the UE deletes the data in data packet 1 except for segment 1 and segment 2 .

[0259] In the embodiment of the present application, when the UE receives NACK message 31 and NACK message 32 at the same time, it will continue to store data packet 1 in the cache. After waiting for a time period of T4, the UE deletes data in data packet 1 except segment 1 and segment 2 from the cache.

[0260] In other embodiments of the present application, the duration T4 may also be referred to as the second duration.

[0261] In this way, after receiving the NACK message 32 in S704, the UE can query the segment 2 from the cache and execute the process in S706, thereby implementing the retransmission process for the segment 2 that the base station has not received.

[0262] Through the processing in S707, the UE always stores the data except segment 1 and segment 2 in data packet 1 within the T4 duration after receiving NACK message 31 or NACK message 32. When the UE receives a NACK message for data except segment 1 and segment 2 in data packet 1, it can implement retransmission processing of data except segment 1 and segment 2 in data packet 1. Thus, it is avoided that the UE cannot receive the confirmation of data packet 1 from the base station, so that the UE can update the upper and lower boundaries of the sending window later. In addition, the UE can maintain data transmission with the base station.

[0263] S708. The base station sends an ACK message 71 to the UE.

[0264] In some embodiments of the present application, after the UE retransmits segment 1 and segment 2 to the base station, the base station may send an ACK message 71 to the UE. The ACK message 71 corresponds to the base station's confirmation of data packet 1 with SN=n1. That is, the base station has received data packet 1 with SN=n1.

[0265] For example, the ACK message 71 may be ACK_SN=n1+1.

[0266] In this embodiment, the ACK message 71 may be the ACK message 11. For detailed description of the ACK message 71, reference may be made to the description in S103.

[0267] In addition, after receiving the ACK message 71, the UE may continue to execute the processes in S709 and S714.

[0268] In other embodiments of the present application, the ACK message 71 may also be referred to as a third status report.

[0269] S709: The UE deletes the remaining data in data packet 1.

[0270] Exemplarily, after receiving the ACK message 71, the UE may delete the remaining data of the data packet 1 stored in the cache.

[0271] As another implementation, after receiving the ACK message 71, the UE may continue to perform the processing in S710 to S714. The specific implementation of S711 to S714 will be described in detail later.

[0272] In the present application, when the UE receives NACK message 31 and NACK message 32 at the same time, it can correspondingly perform the processes in S707 to S709 and S714. In other embodiments of the present application, when the UE receives NACK message 31 and NACK message 32 at the same time, it can correspondingly perform the processes in S710 to S714.

[0273] S710 : UE continues to store data packet 1 .

[0274] In some other embodiments of the present application, when the UE receives the NACK message 31 and the NACK message 32 at the same time, the UE may continue to store the data packet 1.

[0275] Therefore, when the UE subsequently receives a NACK message from the base station for the data in data packet 1, it can retransmit the data in data packet 1. This avoids the situation where the UE cannot receive the confirmation of the base station for data packet 1, and ensures that the UE can trigger the update of the upper and lower boundaries of the sending window. In turn, the UE can maintain data transmission with the base station.

[0276] S711. UE sends data packet 4 with SN=n3 to the base station.

[0277] In some embodiments of the present application, after retransmitting segment 1 and segment 2, the UE may continue to send data packet 4 with SN=n3 to the base station, where n3 is greater than n1 and less than n1+L1.

[0278] In this embodiment, the implementation manner of the UE sending the data packet 4 to the base station is similar to the implementation manner of sending the data packet 1 to the base station. For details, please refer to the description in S102 and will not be repeated here.

[0279] In some other embodiments of the present application, data packet 4 may also be referred to as a third data packet. SN=n3 may also be referred to as a sixth SN.

[0280] S712. The base station sends an ACK message 72 to the UE.

[0281] In some embodiments of the present application, after the UE sends the data packet 4 with SN=n3 to the base station, the base station may send an ACK message 72 to the UE. The ACK message 72 corresponds to the base station's confirmation of the data packet with SN less than or equal to n3. In other words, the base station has received the data packet with SN less than or equal to n3.

[0282] For example, the ACK message 72 may be ACK_SN=n3+1.

[0283] In addition, after receiving the ACK message 72, the UE may continue to perform the processes in S713 and S714.

[0284] In other embodiments of the present application, the ACK message 72 may also be referred to as a sixth status report.

[0285] S713. UE deletes data packet 1.

[0286] Exemplarily, after receiving the ACK message 72, the UE may delete the data packets with SN less than n3 stored in the cache.

[0287] For example, after receiving the ACK message 72, the UE may delete the data packet 1 stored in the cache.

[0288] S714. The UE updates state variables 1 and 2 of the sending window.

[0289] In this embodiment, the implementation of S714 is similar to that of S105, and the specific content can refer to the description in S105.

[0290] For example, taking ACK message 71 as ACK_SN=n1+1, after receiving ACK_SN=n1+1, the UE can modify state variable 1 to n1+1. Correspondingly, the state variable 2 is modified to n1+1+L1. In this way, the SN range of the UE that can subsequently send data packets is from n1+1 to n1+L1.

[0291] Similarly, taking ACK message 72 as ACK_SN=n3+1 as an example, after receiving ACK_SN=n3+1, the UE can modify state variable 1 to n3+1. Correspondingly, the state variable 2 is modified to n3+1+L1. In this way, the SN range of the UE that can subsequently send data packets is from n3+1 to n3+L1.

[0292] In such Figure 7 In the example, the scheme B1 is described by taking the case where the UE simultaneously receives the NACK message 31 and the NACK message 32 as an example. In other embodiments of the present application, the UE may first receive the NACK message 31 and then receive the NACK message 32.

[0293] The following combination Figure 8 Taking the example that the UE may first receive the NACK message 31 and then receive the NACK message 32, the scheme B2 in the scheme B provided in the embodiment of the present application will be further described.

[0294] like Figure 8 As shown, the scheme B2 may include:

[0295] S801. An RRC connection is established between a UE and a base station.

[0296] S802. The UE sends data packet 1 with SN=n1 to the base station.

[0297] S803. The base station sends a NACK message 31 to the UE.

[0298] In an embodiment of the present application, when the UE receives the NACK message 31, it can jump to execute the operation in S807 or S811.

[0299] S804. The UE retransmits segment 1 to the base station.

[0300] S805. The base station sends a NACK message 32 to the UE.

[0301] In some embodiments of the present application, after sending NACK message 31 to the UE, the base station also sends NACK message 32 to the UE. The NACK message 32 is used to indicate that segment 2 is not received. That is, at this time, the base station has received data in data packet 1 except segment 2.

[0302] For the detailed description of NACK message 32, please refer to the description in S306, which will not be repeated here.

[0303] In addition, in the present application, after receiving the NACK message 32, the UE may continue to execute the processing in S808 or S811.

[0304] In this embodiment, the implementation of S801 to S803 corresponds to S301 to S303, and the specific content can refer to the description of S301 to S303. The implementation of S804 and S805 corresponds to S305 and S306, and the specific content can refer to the description of S305 and S306, which will not be repeated here.

[0305] S806. The UE retransmits segment 2 to the base station.

[0306] In the embodiment of the present application, before executing the operation of S807 or S811, the UE receives NACK message 32. At this time, the UE still stores segment 2. Therefore, after receiving NACK message 32, the UE can retransmit segment 2 to the base station according to NACK message 32.

[0307] The specific implementation of S807 and S811 will be described in detail in the subsequent content.

[0308] S807 : After waiting for a period of time T5 , the UE deletes the data except segment 1 in data packet 1 .

[0309] In the embodiment of the present application, when the UE receives the NACK message 31, it will continue to store the data packet 1 in the buffer. After waiting for a time period of T5, the UE deletes the data except the segment 1 in the data packet 1.

[0310] For example, the duration of T5 may be the duration of T4 in S707.

[0311] Therefore, after receiving the NACK message 32 in S805, the UE can query the segment 2 from the cache and execute the process in S806, thereby implementing the retransmission process for the segment 2 that the base station has not received.

[0312] In other embodiments of the present application, the duration T5 may also be referred to as the third duration.

[0313] S808, covering S807, after waiting for T5 time, the UE deletes the data except segment 2 in data packet 1.

[0314] In some embodiments of the present application, taking the time window between the UE executing step S803 and executing step S807 as time window 1, the time point when the UE executes step S805 falls within time window 1. That is, before the UE executes to delete the data except segment 1 in data packet 1, the base station sends a NACK message 32 to the UE.

[0315] In this embodiment, when the UE receives the NACK message 32, it can overwrite the processing in S807. That is, the UE will not continue to perform the operation in S807, and can continue to store the data packet 1 in the cache. After waiting for T5 time, the UE deletes the data except the segment 2 in the data packet 1.

[0316] In another implementation, when the UE receives the NACK message 32, it may delete the data except the segment 1 and the segment 2 in the data packet 1 after a delay of T5 according to the received NACK messages 31 and 32.

[0317] Through the processing in S807 and S808, after receiving the NACK message 31, the UE always stores the data in the data packet 1 except the segment 1. When the UE subsequently receives the NACK message for the data in the data packet 1 except the segment 1, the data in the data packet 1 except the segment 1 can be retransmitted. Thus, it is avoided that the UE cannot receive the confirmation of the base station for the data packet 1, and it is ensured that the UE can trigger the update processing of the upper and lower boundaries of the sending window. In addition, the UE can maintain the data transmission between the UE and the base station.

[0318] S809. The base station sends an ACK message 81 to the UE.

[0319] For example, the ACK message 81 may be the ACK message 71 .

[0320] As an implementation manner, after receiving the ACK message 81, the UE may continue to perform the processes in S810 and S815.

[0321] As another processing manner, after receiving the ACK message 81, the UE may continue to perform the processing in S811 to S815.

[0322] S810. UE deletes the remaining data in data packet 1.

[0323] S811. UE continues to store data packet 1.

[0324] In an embodiment of the present application, when the UE receives the NACK message 31 or the NACK message 32, the UE may continue to store the data packet 1.

[0325] S812. The UE sends data packet 4 with SN=n3 to the base station.

[0326] S813. The base station sends an ACK message 82 to the UE.

[0327] For example, the ACK message 82 is considered to be the ACK message 72 .

[0328] S814. UE deletes data packet 1.

[0329] S815. The UE updates state variables 1 and 2 of the sending window.

[0330] In this embodiment, the implementation of S809 to S815 is similar to that of S708 to S714. For the specific contents, reference may be made to the descriptions of S708 to S714, which will not be repeated here.

[0331] exist Figures 6 to 8 In the description of Figure 3 The following example uses the scenario in Figure 4 Taking the scenario in as an example, the scheme B provided in the embodiment of the present application is further illustrated.

[0332] The following combination Fig. 9 Taking the example that the UE receives an ACK message 41 and a NACK message 42 after sending a data packet 1, scheme B3 in scheme B provided in an embodiment of the present application will be further described.

[0333] like Fig. 9 As shown, the scheme B3 may include:

[0334] S901. An RRC connection is established between a UE and a base station.

[0335] S902. The UE sends data packet 1 with SN=n1 to the base station.

[0336] S903. The base station sends an ACK message 41 to the UE.

[0337] S904. The base station sends a NACK message 42 to the UE.

[0338] In some embodiments of the present application, the base station sends a NACK message 42 to the UE while sending an ACK message 41 to the UE. For detailed description of the NACK message 42, reference may be made to the description in S405, which will not be repeated here.

[0339] It should be noted that, in the embodiment of the present application, taking the NACK message 42 used to indicate that segment 1 has not been received as an example, the base station simultaneously sends an ACK message 41 and a NACK message 42 to the UE, corresponding to indicating that the base station has received the data in data packet 1 except segment 1.

[0340] In this implementation, the UE may simultaneously receive the ACK message 41 and the NACK message 42. In this case, the UE may continue to perform the process in S906 or S909.

[0341] In this embodiment, the implementation of S901 to S903 corresponds to S401 to S403, and the specific content can refer to the description of S401 to S403. The implementation of S904 corresponds to S405, and the specific content can refer to the description of S405, which will not be repeated here.

[0342] In the following examples, the method is further described by taking the NACK message 42 used to indicate that segment 1 is not received as an example.

[0343] S905. The UE retransmits segment 1 to the base station.

[0344] In the embodiment of the present application, through the processing in scheme 5 or scheme 6, when the UE receives the NACK message 42, the UE still stores segment 1. Therefore, after receiving the NACK message 42, the UE can retransmit segment 1 to the base station according to the NACK message 42.

[0345] The specific implementation of Scheme 5 and Scheme 6 will be described in detail in the subsequent content.

[0346] S906 , after waiting for a period of time T6 , the UE deletes the data except segment 1 in data packet 1 .

[0347] In the embodiment of the present application, when the UE receives the ACK message 41 and the NACK message 42, it will continue to store the data packet 1 in the buffer. After waiting for a time period of T4, the UE deletes the data except the segment 1 in the data packet 1 according to the ACK message 41 and the NACK message 42.

[0348] For example, the duration of T6 may be the duration of T4.

[0349] In this way, after receiving the NACK message 42 in S904, the UE can query the segment 1 from the cache and execute the process in S905, thereby implementing the retransmission process for the segment 1 that the base station has not received.

[0350] Through the processing in S906, the UE always stores the data except segment 1 in data packet 1 within the duration T6 after receiving the ACK message 41 or the NACK message 42. When the UE subsequently receives a NACK message for the data except segment 1 in data packet 1, the data except segment 1 in data packet 1 can be retransmitted. Thus, it is avoided that the UE cannot receive the confirmation of data packet 1 from the base station, so that the UE can update the upper and lower boundaries of the sending window later. In addition, the UE can maintain data transmission with the base station.

[0351] S907. The base station sends an ACK message 91 to the UE.

[0352] In some embodiments of the present application, after the UE retransmits segment 1 to the base station, the base station may send an ACK message 91 to the UE. The ACK message 91 corresponds to the base station's confirmation of data packet 1 with SN=n1. That is, the base station has received data packet 1 with SN=n1.

[0353] For example, the ACK message 91 may be the ACK message 71 .

[0354] S908. The UE deletes the remaining data in data packet 1.

[0355] S909. UE continues to store data packet 1.

[0356] In an embodiment of the present application, when the UE receives the ACK message 41 and the NACK message 42 at the same time, the UE may continue to store the data packet 1 .

[0357] S910. The UE sends data packet 4 with SN=n3 to the base station.

[0358] S911. The base station sends an ACK message 92 to the UE.

[0359] For example, the ACK message 92 may be the ACK message 72 .

[0360] S912. UE deletes data packet 1.

[0361] S913. The UE updates state variables 1 and 2 of the sending window.

[0362] In this embodiment, the implementation of S908 to S913 is similar to the implementation of S709 to S714. For the specific content, please refer to the description of S709 to S714, which will not be repeated here.

[0363] In such Fig. 9 In the example, scheme B3 is described by taking the case where the UE simultaneously receives the ACK message 41 and the NACK message 42 as an example. In other embodiments of the present application, the UE may first receive the ACK message 41 and then receive the NACK message 42.

[0364] The following combination Fig.10 Taking the example that the UE can first receive the ACK message 41 and then receive the NACK message 42, the scheme B4 in the scheme B provided in the embodiment of the present application is further described.

[0365] like Fig.10 As shown, the scheme B4 may include:

[0366] S1001. Establish an RRC connection between UE and base station.

[0367] S1002. UE sends data packet 1 with SN=n1 to the base station.

[0368] S1003. The base station sends an ACK message 41 to the UE.

[0369] In an embodiment of the present application, when the UE receives the ACK message 41, it can jump to execute the operation in S1006 or S1010.

[0370] S1004. The base station sends a NACK message 42 to the UE.

[0371] In some embodiments of the present application, after sending the ACK message 41 to the UE, the base station also sends a NACK message 42 to the UE. For the detailed description of the NACK message 42, please refer to the description in S405, which will not be repeated here.

[0372] In addition, after receiving the NACK message 42, the UE may continue to execute the processing in S1007 or S1010.

[0373] In this embodiment, the implementation of S1001 to S1003 corresponds to S401 to S403, and the specific content can refer to the description of S401 to S403. The implementation of S1004 corresponds to S405, and the specific content can refer to the description of S405, which will not be repeated here.

[0374] In the following examples, the method is further described by taking the NACK message 42 used to indicate that segment 1 is not received as an example.

[0375] S1005. UE retransmits segment 1 to the base station.

[0376] In the embodiment of the present application, before the UE performs the operation in S1006 or S1010, it receives NACK message 42. At this time, the UE still stores segment 1. Therefore, after receiving NACK message 42, the UE can retransmit segment 1 to the base station according to NACK message 42.

[0377] The specific implementation of S1006 and S1010 will be described in detail in the subsequent content.

[0378] S1006 , after waiting for a period of time T7 , the UE deletes data packet 1 .

[0379] In the embodiment of the present application, when the UE receives the ACK message 41, it will continue to store the data packet 1 in the buffer. After waiting for a time period of T7, the UE deletes the data packet 1.

[0380] For example, the duration of T7 may be the duration of T4 in S707.

[0381] Therefore, after receiving the NACK message 42 in S1004, the UE can query the segment 1 from the cache and execute the process in S1005, thereby implementing the retransmission process for the segment 1 that the base station has not received.

[0382] S1007, covering S1006, after waiting for T7 time, the UE deletes the data except segment 1 in data packet 1.

[0383] In the embodiment of the present application, the UE receives a NACK message 42 before executing the operation in S1006 .

[0384] In this embodiment, when the UE receives the NACK message 42, it can overwrite the processing in S1006. That is, the UE will not continue to perform the operation in S1006, and can continue to store the data packet 1 in the cache. After waiting for T7, the UE deletes the data except the segment 1 in the data packet 1.

[0385] S1008. The base station sends an ACK message 1001 to the UE.

[0386] For example, the ACK message 1001 may be the ACK message 71 .

[0387] S1009. UE deletes the remaining data in data packet 1.

[0388] S1010. UE continues to store data packet 1.

[0389] In an embodiment of the present application, when the UE receives the ACK message 41 or the NACK message 42 , it can continue to store the data packet 1 .

[0390] S1011. UE sends data packet 4 with SN=n3 to the base station.

[0391] S1012. The base station sends an ACK message 1002 to the UE.

[0392] For example, the ACK message 1002 may be the ACK message 72 .

[0393] S1013. UE deletes data packet 1.

[0394] S1014. The UE updates state variables 1 and 2 of the sending window.

[0395] In this embodiment, the implementation of S1008 to S1014 is similar to the implementation of S708 to S714. For the specific content, please refer to the description of S708 to S714, which will not be repeated here.

[0396] In some other embodiments of the present application, after the UE performs the operation of S617 according to solution A, it can receive a confirmation from the base station for data packet 3 or a segment in data packet 3. At this time, the UE can continue to store the data packet 3 or the segment in data packet 3. So that when the UE subsequently receives a NACK message from the base station for the data packet 3 or the segment of the data packet 3, it can retransmit the data packet 3 or the segment of the data packet 3 to the base station. Further, the UE can always maintain communication with the base station.

[0397] Exemplarily, after sending data packet 3, the UE may receive status report A and status report B. Status report A is used to indicate that the base station has received the third segment. The third segment is included in data packet 3. Status report B is used to indicate that the base station has not received the fourth segment. The fourth segment and the third segment include at least part of the data overlap. After receiving status report A and status report B, the UE may delay deleting the data in the third segment and data packet 3 except the fourth segment.

[0398] Among them, the specific implementation method of the UE delaying deletion of the third segment and the data in the data packet 3 except the fourth segment is the same as Figures 7 to 10 Similar to any of the methods in, for details, please refer to Figures 7 to 10 The instructions in the article are not repeated here.

[0399] In this example, the UE can Figures 7 to 10 Any of the methods provided in the embodiment of the present invention is used to perform the same processing on data packet 3 as on data packet 1.

[0400] In some other embodiments of the present application, status report A may also be referred to as a fourth status report, and status report B may also be referred to as a fifth status report.

[0401] The above mainly introduces the solution provided by the embodiment of the present application from the perspective of the terminal (such as UE). Those skilled in the art should easily realize that, in combination with the units and 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 this application.

[0402] refer to Fig.11 , is a schematic diagram of another terminal 1100 provided in an embodiment of the present application. Fig.11 As shown, the terminal 1100 may include: a processor 1101 and a memory 1102. The memory 1102 is used to store computer-executable instructions. Exemplarily, in some embodiments, when the processor 1101 executes the instructions stored in the memory 1102, the terminal 1100 may execute any of the methods shown in the above embodiments.

[0403] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0404] Fig.12 A schematic diagram of the composition of a chip system 1200 is shown. The chip system 1200 may include: a processor 1201 and a communication interface 1202, which are used for the UE to implement the functions involved in the above embodiments. In a possible design, the chip system also includes a memory for storing program instructions and data necessary for the terminal. The chip system may be composed of chips, or may include chips and other discrete devices. It should be noted that in some implementations of the present application, the communication interface 1202 may also be referred to as an interface circuit. As a possible implementation, the chip system 1200 may correspond to the following: Figure 5 The first chip module shown is such as a modem.

[0405] It should be noted that all relevant contents of each step involved in the above method embodiment can be referred to the functional description of the corresponding functional module and will not be repeated here.

[0406] The functions or actions or operations or steps in the above embodiments, etc., can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using a software program, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loading and executing computer program instructions on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The computer instructions can be stored in a computer-readable storage medium, or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that includes one or more servers that can be integrated with a medium. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (eg, a solid state drive (SSD)).

[0407] Although the present application has been described in conjunction with specific features and embodiments thereof, it is obvious that various modifications and combinations may be made thereto without departing from the spirit and scope of the present application. Accordingly, this specification and the drawings are merely exemplary illustrations of the present application as defined by the appended claims, and are deemed to have covered any and all modifications, variations, combinations or equivalents within the scope of the present application. Obviously, those skilled in the art may make various modifications and variations to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: The method is applied to a terminal, and the method includes: Sending a first data packet; receiving a first status report; the first status report is used to indicate that the access network device has confirmed receipt of the first segment; the first segment is included in the first data packet; receiving a second status report; wherein the second status report is used to indicate that the access network device has not received the second segment; and the second segment and the first segment include at least part of overlapping data; Triggering radio link failure RLF.

2. The method according to claim 1, characterized in that: A first radio resource control RRC connection is established between the terminal and the access network device; The sending of the first data packet comprises: The first data packet is sent through the first RRC connection.

3. The method according to claim 1 or 2, characterized in that: After triggering the radio link failure RLF, the method further includes: Establish a second RRC connection with the access network device.

4. The method according to any one of claims 1 to 3, characterized in that The terminal is configured with a sending window; and sending the first data packet comprises: The first data packet whose sending sequence number SN is from a first SN to a second SN; the first SN corresponds to the lower boundary of the sending window, and the second SN corresponds to the upper boundary of the sending window.

5. The method according to claim 4, characterized in that The sending window is configured with a first state variable and a second state variable; the first state variable corresponds to the lower boundary of the sending window, and the second state variable corresponds to the upper boundary of the sending window; before sending the first data packet, the first state variable corresponds to the first SN, and the second state variable corresponds to the second SN.

6. The method according to claim 5, characterized in that Before triggering the RLF, the method further includes: detecting that the second segment and the first segment include at least a portion of data overlap; Recording the time when the second status report is received as the first time; Recording the time when the first data packet of the second SN is sent as the second time; The triggering of RLF includes: According to the time difference between the first time and the second time being greater than a preset first duration, RLF is triggered.

7. The method according to claim 5 or 6, characterized in that: After establishing a second RRC connection with the access network device, the method further includes: Configuring the lower and upper boundaries of the sending window; The configuring the lower boundary and the upper boundary of the sending window includes: configuring the first state variable as a third SN; The second state variable is configured as a fourth SN.

8. The method according to claim 7, characterized in that The terminal stores a second data packet; the second data packet is a data packet not sent by the terminal; After configuring the lower boundary and the upper boundary of the sending window, the method further includes: Send the second data packet; the second data packet carries a fifth SN; the fifth SN is less than or equal to the third SN, and the fifth SN is less than the fourth SN.

9. The method according to claim 8, characterized in that After sending the second data packet, the method further includes: receiving a fourth status report; the fourth status report is used to indicate that the access network device has confirmed receipt of the third segment; the third segment is included in the second data packet; receiving a fifth status report; the fifth status report is used to indicate that the access network device has not received the fourth segment; the fourth segment and the third segment include at least part of the data overlap; Resending the fourth segment according to the fifth status report.

10. The method according to claim 9, characterized in that After resending the fourth segment, the method further comprises: Receive a third status report; the third status report is used to indicate that the access network device has confirmed receipt of the second data packet.

11. The method according to claim 10, characterized in that The fourth status report and the fifth status report are received simultaneously; before receiving the third status report, the method further includes: When the fourth status report or the fifth status report is received, the third segment and the data in the second data packet except the fourth segment are deleted after a second delay.

12. The method according to claim 10, characterized in that The fifth status report is received within a third time period later than the fourth status report; Before receiving the third status report, the method further includes: Upon receiving the fifth status report, deleting data other than the fourth segment in the second data packet after delaying the third time period; Alternatively, when the fifth status report is received, the third segment and the data in the second data packet except the fourth segment are deleted after delaying the third time length.

13. The method according to claim 11 or 12, characterized in that: After receiving the third status report, the method further includes: According to the third status report, the remaining data in the second data packet is deleted.

14. The method according to claim 9, characterized in that After receiving the fourth status report or the fifth status report, the method further includes: Continue to store the second data packet; Sending a third data packet; the SN of the third data packet is the sixth SN; the sixth SN is greater than the fifth SN; receiving a sixth status report; the sixth status report is used to indicate that the access network device has confirmed receipt of the third data packet; According to the sixth status report, the second data packet is deleted.

15. The method according to any one of claims 10 to 13, characterized in that: After receiving the third status report, the method further includes: Modify the first state variable from the third SN to the fifth SN plus 1; The second state variable is modified from the fourth SN to the fifth SN plus 1 and a first length; the first length is equal to the difference between the fourth SN and the third SN.

16. The method according to claim 14, characterized in that After receiving the sixth status report, the method further includes: Modify the first state variable from the third SN to the sixth SN plus 1; The second state variable is modified from the fourth SN to the sixth SN plus 1 and a first length; the first length is equal to the difference between the fourth SN and the third SN.

17. The method according to claim 1, characterized in that The first segment is included in the first data packet, including: the first segment is the first data packet; or the first segment is part of data in the first data packet.

18. The method according to claim 17, characterized in that When the first segment is part of the data in the first data packet, the first status report is further used to indicate that the access network device has not received the fifth segment; The fifth segment is data in the first data packet except the first segment; After receiving the first status report, the method further includes: resending the fifth segment; Delete the first segment.

19. The method according to claim 7, characterized in that Before configuring the lower boundary and the upper boundary of the sending window, the method further includes: An RRC connection reconfiguration message is received; the RRC connection reconfiguration message carries a first indication; the first indication is used to indicate configuration of the sending window.

20. A terminal, characterized in that: The terminal comprises: a memory and one or more processors; the memory and the processor are coupled; The memory is used to store computer program codes, and the computer program codes include computer instructions. When the processor executes the computer instructions, the terminal executes the method as described in any one of claims 1 to 19.

Images