Communication method, computer readable storage medium and electronic device
Through the RLC entity, the SDU identification is determined based on the first negative feedback information in the status report and send signaling, the problem of low status report processing efficiency and large signaling overhead in NB-IoT communication is solved, and more efficient inter-layer interaction is achieved and data processing.
Patent Information
- Application Number
- CN202210878721.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2022-07-25
- Publication Date
- 2024-11-12
- Estimated Expiration
- 2042-07-25
AI Technical Summary
In NB-IoT communication technology, when multiple negative feedback information is received in the status report, the RLC entity needs to send multiple signaling to the upper layer, resulting in low processing efficiency, time delay and signaling overhead, affecting the inter-layer interaction process.
The RLC entity determines the first SDU identifier based on the first negative feedback information in the status report, sends signaling to the PDCP entity, deletes the corresponding PDCP protocol packet PDU, and only sends one signaling when multiple negative feedback information is repeated, optimizes Inter-layer interaction process.
Improves the efficiency of status reporting processing, reduces signaling overhead, optimizes inter-layer interaction processes, and improves the efficiency and accuracy of data processing.
Smart Images

Figure CN115297504B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of communication technology, and in particular to a communication method, a computer-readable storage medium and an electronic device. Background Art
[0002] In NB-IoT (Narrow Band-Internet Of Things) communication technology, two EPS optimization modes are defined for CIoT (Cellular Internet of Things) under the EPS (Evolved Packet System) framework based on the demand characteristics of IoT services: control plane CIoT EPS optimization (CP-CIoT for short) and user plane CIoT EPS optimization (UP-CIoT for short).
[0003] In the prior art, when the CP-CIoT optimization scheme or the UP-CIoT optimization scheme is used to send data, the sending end determines the reception status of the sent data based on the status report fed back by the receiving end. Specifically, after the RLC entity at the sending end receives the status report, it is necessary to determine the data that was not correctly received by the receiving end based on the PDU sequence number corresponding to each negative feedback information in the status report. For any incorrectly received data determined by the PDU sequence number corresponding to the negative feedback information, the RLC entity needs to send a signal to the upper layer, and each signal includes at least a start identifier and an end identifier, and then the upper layer performs corresponding processing according to the signal. The upper layer can be a higher-layer data protocol layer of the RLC layer, such as the PDCP layer, the RRC layer, etc.
[0004] However, when the status report includes multiple negative feedback information, the RLC entity needs to determine multiple segments of incorrectly received data based on the PDU sequence numbers corresponding to the multiple negative feedback information, resulting in low status report processing efficiency and long latency, which is not conducive to the RLC entity's maintenance and update of the RLC cache. At the same time, the RLC entity needs to send multiple signaling to the upper layer, resulting in large signaling overhead. Summary of the invention
[0005] In view of this, an object of an embodiment of the present invention is to provide a communication method, a computer-readable storage medium and an electronic device to improve the status report processing efficiency, reduce signaling overhead, and optimize the inter-layer interaction process.
[0006] In a first aspect, an embodiment of the present invention provides a communication method, the method comprising:
[0007] A radio link control layer RLC entity receives a status report, and in response to the status report including at least one negative feedback information, the RLC entity determines a first service data packet SDU identifier according to first negative feedback information in the status report, wherein the negative feedback information is used to represent data that is not correctly received by the receiving end;
[0008] The RLC entity sends a first signaling to a Packet Data Convergence Protocol layer PDCP entity, where the first signaling includes the first SDU identifier; and
[0009] According to the first signaling, the PDCP protocol data packet PDU corresponding to the first SDU identifier and before the first SDU identifier is deleted from the PDCP cache.
[0010] In some embodiments, the RLC entity determines the first service data packet SDU identifier according to the first negative feedback information in the status report, including:
[0011] Determine a first confirmation status value according to the PDU sequence number corresponding to the first negative feedback information in the status report; and
[0012] The first SDU identifier is determined according to the identifier of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value.
[0013] In some embodiments, the method further comprises:
[0014] The RLC entity determines an initial confirmation status value according to a PDU sequence number corresponding to the confirmation status value of the sending window when receiving the status report; and
[0015] The initial SDU identifier is determined according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value.
[0016] In some embodiments, the method further comprises:
[0017] In response to the SDU corresponding to the first SDU identifier representing a complete SDU, the RLC entity sends the first signaling to the PDCP entity; or
[0018] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being different from the first SDU identifier, the RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value, and the RLC entity sends the first signaling to the PDCP entity; and
[0019] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being the same as the first SDU identifier, the RLC entity waits to receive a subsequent status report.
[0020] In some embodiments, the method further comprises:
[0021] In response to the RLC entity receiving the status report, marking a PDU other than the third status PDU as a first status PDU in a first buffer, the first buffer being used to buffer data sent to the receiving end, the first status PDU representing a PDU that the RLC entity has confirmed to be correctly received, and the third status PDU representing a PDU that the RLC entity has confirmed to be correctly received and to be confirmed and processed;
[0022] Marking the incorrectly received data in the first status PDU as a second status PDU according to the negative feedback information in the status report; and
[0023] The PDU whose sequence number is greater than or equal to the first confirmation status value and is not the second status PDU is marked as the third status PDU.
[0024] In some embodiments, the method further comprises:
[0025] Cache the information of the second status PDU in a second cache, where the second cache is used to cache information of data that needs to be retransmitted; and
[0026] The information of the first status PDU and the information of the third status PDU are deleted in the second buffer.
[0027] In some embodiments, the method further comprises:
[0028] In response to link failure reconnection and the first buffer including at least one of the third status PDUs, the RLC entity determines an identifier of an SDU included in at least one of the third status PDUs;
[0029] The RLC entity sends at least one signaling to the PDCP entity, where the signaling includes an identifier of the SDU; and
[0030] The PDCP PDU corresponding to the identifier of the SDU is deleted from the PDCP buffer according to the signaling.
[0031] In some embodiments, the method further comprises:
[0032] In response to the memory status indicating insufficient memory or multiple data packets having been sent and waiting to be confirmed, the RLC entity sets a polling bit in the sent data, wherein the polling bit is used to request a reply status report from the receiving end.
[0033] In a second aspect, an embodiment of the present invention provides a computer-readable storage medium storing computer program instructions, wherein the computer program instructions implement the method described in the first aspect when executed by a processor.
[0034] In a third aspect, an embodiment of the present invention provides an electronic device, comprising a memory and a processor, wherein the memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method described in the first aspect.
[0035] The technical solution of the embodiment of the present invention is that the RLC entity receives a status report, and in response to at least one negative feedback information included in the status report, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process. BRIEF DESCRIPTION OF THE DRAWINGS
[0036] The above and other objects, features and advantages of the present invention will become more apparent through the following description of the embodiments of the present invention with reference to the accompanying drawings, in which:
[0037] Figure 1 is a schematic diagram of a communication system according to an embodiment of the present invention;
[0038] Figure 2 is a schematic diagram of the protocol layer of an embodiment of the present invention;
[0039] Figure 3 is a flow chart of a prior art sending end request and processing status report;
[0040] Figure 4 is a flow chart of a method for an RLC entity at a transmitting end to process a status report according to an embodiment of the present invention;
[0041] Figure 5 It is a flowchart of a specific method for an RLC entity at a transmitting end to process a status report according to an embodiment of the present invention;
[0042] Figure 6 is a schematic diagram of a status report according to an embodiment of the present invention;
[0043] Figure 7 It is a flow chart of a method for an RLC entity at a transmitting end to determine a first SDU identifier according to first negative feedback information in a status report according to an embodiment of the present invention;
[0044] Figure 8 is a flow chart of a method in which a sending end requests a receiving end to reply to a status report according to an embodiment of the present invention;
[0045] Fig. 9 It is a flow chart of communication between an RLC entity at a transmitting end and a PDCP entity at a transmitting end during a link failure reconnection process according to an embodiment of the present invention;
[0046] Fig.10 is a flow chart of a communication device according to an embodiment of the present invention;
[0047] Fig.11 is a schematic diagram of an electronic device according to an embodiment of the present invention. DETAILED DESCRIPTION
[0048] The present invention is described below based on embodiments, but the present invention is not limited to these embodiments. In the detailed description of the present invention below, some specific details are described in detail. It is possible for a person skilled in the art to fully understand the present invention without the description of these details. In order to avoid confusing the essence of the present invention, known methods, processes, flows, components and circuits are not described in detail.
[0049] In addition, persons of ordinary skill in the art will appreciate that the drawings provided herein are for illustration purposes and are not necessarily drawn to scale.
[0050] Unless the context clearly requires otherwise, words such as “comprise”, “include” and the like in the specification should be interpreted as including rather than being exclusive or exhaustive; that is, as “including but not limited to”.
[0051] In the description of the present invention, it is to be understood that the terms "first", "second", etc. are only configured for descriptive purposes and cannot be understood as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, "plurality" means two or more.
[0052] In the following description, the scenario in which a smart phone, a smart bicycle and a base station communicate with each other is taken as an example. It should be understood that the communication method of the embodiment of the present invention can also be applied to various other types of scenarios that can communicate based on NB-IoT, such as smart traffic control, smart fire control, smart home appliance control, shared bicycle control, GPS positioning, smart buildings, smart parking lots and other scenarios.
[0053] Figure 1 Schematic diagram of a communication system according to an embodiment of the present invention. Figure 1 In the embodiment shown, the communication system includes a base station 2 and a plurality of terminals. Figure 1 In the figure, there are multiple terminals, which are 1 and 3 shown in the figure. In the embodiment of the present invention, terminals 1 and 3 communicate through base station 2 to realize data transmission and reception. Among them, terminals 1 and 3 can send data to the base station as a sending end, and can also receive data from the base station as a receiving end to realize the communication function.
[0054] In this embodiment, terminals 1 and 3 can be devices with wireless communication and data transmission functions, such as smart phones, smart bicycles, smart street lights, smart electricity meters, smart manhole covers, smart locks, smart fire hydrants, etc., and the wireless communication can be achieved through NB-IoT.
[0055] In this embodiment, multiple terminals and base station 2 in the communication system have communication functions based on NB-IoT (Narrow Band-Internet of Things). In this embodiment, the communication system adopts the UP-CIoT optimization solution as an example for explanation, but the embodiment of the present invention does not limit the optimization solution adopted by the communication system, such as the CP-CIoT optimization solution.
[0056] In this embodiment, multiple terminals communicating with base station 2 are taken as an example for explanation, but the embodiment of the present invention does not limit the number of terminals and base stations communicating. It can be one base station and one terminal communicating, or multiple base stations and multiple terminals communicating, or multiple base stations and one terminal communicating, etc.
[0057] The technical solution of the embodiment of the present invention is that the RLC entity receives a status report, and in response to at least one negative feedback information included in the status report, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process.
[0058] At the protocol level, the method of the embodiment of the present invention is applicable to the RLC entity of the transmitting end requesting the receiving end to reply to the status report and process the status report. In the following description, the transmitting end and the receiving end are used to describe the method of requesting and processing the status report of the embodiment of the present invention.
[0059] Furthermore, the sending end and the receiving end communicate and transmit data based on the protocol layer. Specifically, Figure 2 It is a schematic diagram of the protocol layer of an embodiment of the present invention.
[0060] like Figure 2 As shown, the protocol layers of the transmitting end of the embodiment of the present invention include NAS layer (Non-Access Stratum), PDCP layer (Packet Data Convergence Protocol), RLC layer (Radio Link Control), MAC layer (Media Access Control) and PHY layer (Physical layer). The protocol layers of the receiving end include NAS layer, PDCP layer, RLC layer, MAC layer and PHY layer.
[0061] In this embodiment, when sending data, the data is sent to the receiving end via the NAS layer, PDCP layer, RLC layer, MAC layer and PHY layer of the sending end.
[0062] In this embodiment, when receiving data, the data is received by the receiving end via the receiving end PHY layer, MAC layer, RLC layer, PDCP layer and NAS layer, thereby realizing data transmission between the sending end and the receiving end.
[0063] Furthermore, during the data transmission process, the transmitting end determines the reception status of the transmitted data according to the status report fed back by the receiving end. Figure 3is a flow chart of the prior art sending end request and processing status report. Figure 3 As shown, the sending end request and processing status report of the prior art includes the following steps:
[0064] Step S100: In response to the fact that there are no new data packets and retransmission data packets in the RLC buffer that need to be sent or the sending window reaches the maximum and the data packet cannot be sent, the polling bit is set to 1 in the sending data.
[0065] In the prior art, during the process of sending data from a transmitting end to a receiving end, the transmitting end RLC entity responds that there are no new data packets and retransmission data packets to be sent after the RLC PDU to be sent in the RLC cache or the sending window has reached the maximum and data packets cannot be sent, and sets the polling bit in the RLC header of the RLC PDU to 1. The polling bit is used to request a reply status report from the receiving end.
[0066] Step S110: Send data.
[0067] In the prior art, a transmitting end sends data with a polling bit set to 1 to a receiving end.
[0068] Step S120: The RLC entity parses the data packet and determines that the polling bit is 1.
[0069] In the prior art, in response to receiving a data packet, the receiving end RLC entity parses the data packet and determines that the polling bit is 1.
[0070] Step S130: In response to determining that the polling bit is 1 or data is not correctly received, feeding back a status report.
[0071] In the prior art, the receiving end responds to determining that the polling bit is 1 or that the data is not received correctly, and feeds back a status report to the sending end. The receiving end does not receive the data correctly in a way such as the received data packet loss, data error, etc. In the NB-IoT communication technology, the sending end does not have the function of setting the polling bit to 1 in the subsequent data sent after sending a predetermined byte or a predetermined data packet in the LTE architecture (Long Term Evolution) so that the receiving end can feed back a status report. Therefore, when continuously sending data, the sending end in the prior art cannot promptly request the receiving end to reply to the status report, resulting in a large amount of data being accumulated in the RLC cache of the sending end, and the RLC layer of the sending end cannot release the memory in time, which leads to problems such as memory exhaustion at the sending end.
[0072] Step S140: The RLC entity determines the data correctly received and the data incorrectly received by the receiving end according to the PDU sequence numbers of the positive feedback information and the negative feedback information in the status report.
[0073] In the prior art, for any negative feedback information in the status report, the RLC entity at the sending end will determine the data that has not been correctly received by the receiving end based on the PDU sequence number corresponding to the feedback information. At the same time, the RLC entity at the sending end will determine the data that has been correctly received by the receiving end based on the PDU sequence number corresponding to the positive feedback information in the status report. Therefore, for each negative feedback information in the status report, the RLC entity at the sending end needs to determine the reception status of the two PDUs.
[0074] Furthermore, when the status report includes multiple negative feedback information, the RLC entity at the transmitting end determines multiple segments of data that were not correctly received by the receiving end based on the multiple PDU sequence numbers corresponding to the multiple negative feedback information in the status report, resulting in low status report processing efficiency and long delay, which is not conducive to the RLC entity's maintenance and update of the RLC cache.
[0075] Step S150: The RLC entity sends multiple signalings to the upper layer, and the upper layer performs corresponding processing according to the signalings.
[0076] In the prior art, the RLC entity at the transmitting end sends multiple signalings to the upper layer, and the signaling overhead is large, and each signaling includes at least a start SDU identifier and an end SDU identifier. The upper layer may be a higher layer data protocol layer of the RLC layer, such as a PDCP layer, an RRC layer, etc. In the embodiment of the present invention, the upper layer of the RLC layer is taken as an example for description.
[0077] In the embodiment of the present invention, the RLC entity responds to the memory status characterization that the memory is insufficient or multiple data packets have been sent to be confirmed or there are no new data packets and retransmission data packets in the RLC cache that need to be sent or the sending window has reached the maximum and data packets cannot be sent, and sets the polling bit in the sending data so that the receiving end can feedback the status report. Then the RLC entity receives the status report, and in response to the status report including at least one negative feedback information, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process.
[0078] In the following description, the NAS entity is the NAS layer, the PDCP entity is the PDCP layer, the RLC entity is the RLC layer, the PHY entity is the PHY layer, and the MAC entity is the MAC layer. Among them, the NAS entity, the PDCP entity, the RLC entity, the PHY entity, and the MAC entity can receive data and send data, and can also receive signaling, send signaling, and process signaling.
[0079] In the following description, by Figure 4-Figure 10 The method for requesting and processing a status report at the sending end according to the embodiment of the present invention is described respectively.
[0080] Figure 4 FIG. 4 is a flow chart of a method for processing a status report by an RLC entity at a transmitting end according to an embodiment of the present invention. Figure 4 As shown, the method for processing status report by the RLC entity of the transmitting end in the embodiment of the present invention includes the following steps:
[0081] Step S210: A radio link control layer RLC entity receives a status report, and in response to the status report including at least one negative feedback information, the RLC entity determines a first service data packet SDU identifier according to the first negative feedback information in the status report.
[0082] Step S220: The RLC entity sends a first signaling to a packet data convergence protocol layer PDCP entity, where the first signaling includes a first SDU identifier.
[0083] Step S230: Delete the PDCP protocol data packet PDU corresponding to the first SDU identifier and before the first SDU identifier from the PDCP cache according to the first signaling.
[0084] In some embodiments, the RLC entity determines the first service data packet SDU identifier according to the first negative feedback information in the status report, including:
[0085] Determine a first confirmation status value according to the PDU sequence number corresponding to the first negative feedback information in the status report; and
[0086] The first SDU identifier is determined according to the identifier of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value.
[0087] In some embodiments, the method further comprises:
[0088] The RLC entity determines an initial confirmation status value according to a PDU sequence number corresponding to the confirmation status value of the sending window when receiving the status report; and
[0089] The initial SDU identifier is determined according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value.
[0090] In some embodiments, the method further comprises:
[0091] In response to the SDU corresponding to the first SDU identifier representing a complete SDU, the RLC entity sends the first signaling to the PDCP entity; or
[0092] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being different from the first SDU identifier, the RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value, and the RLC entity sends the first signaling to the PDCP entity; and
[0093] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being the same as the first SDU identifier, the RLC entity waits to receive a subsequent status report.
[0094] In some embodiments, the method further comprises:
[0095] In response to the RLC entity receiving the status report, marking a PDU other than the third status PDU as a first status PDU in a first buffer, the first buffer being used to buffer data sent to the receiving end, the first status PDU representing a PDU that the RLC entity has confirmed to be correctly received, and the third status PDU representing a PDU that the RLC entity has confirmed to be correctly received and to be confirmed and processed;
[0096] Marking the incorrectly received data in the first status PDU as a second status PDU according to the negative feedback information in the status report; and
[0097] The PDU whose sequence number is greater than or equal to the first confirmation status value and is not the second status PDU is marked as the third status PDU.
[0098] In some embodiments, the method further comprises:
[0099] Cache the information of the second status PDU in a second cache, where the second cache is used to cache information of data that needs to be retransmitted; and
[0100] The information of the first status PDU and the information of the third status PDU are deleted in the second buffer.
[0101] In some embodiments, the method further comprises:
[0102] In response to link failure reconnection and the first buffer including at least one of the third status PDUs, the RLC entity determines an identifier of an SDU included in at least one of the third status PDUs;
[0103] The RLC entity sends at least one signaling to the PDCP entity, where the signaling includes an identifier of the SDU; and
[0104] The PDCP PDU corresponding to the identifier of the SDU is deleted from the PDCP cache according to the signaling.
[0105] In some embodiments, the method further comprises:
[0106] In response to the memory status indicating insufficient memory or multiple data packets having been sent and waiting to be confirmed, the RLC entity sets a polling bit in the sent data, wherein the polling bit is used to request a reply status report from the receiving end.
[0107] Further, Figure 5 FIG. 1 is a flowchart of a specific method for the RLC entity at the transmitting end to process a status report according to an embodiment of the present invention. Figure 5 As shown, the specific method for the RLC entity processing status report at the transmitting end of the embodiment of the present invention includes the following steps:
[0108] Step S301: The RLC entity receives a status report and determines an initial confirmation status value according to a PDU sequence number corresponding to the confirmation status value of the sending window when the status report is received.
[0109] In this embodiment, the schematic diagram of the status report is as follows: Figure 6 As shown. Figure 6 In the status report, there are multiple Oct (octet, byte), which are Figure 6 Oct1-Oct9 shown in FIG.
[0110] In this embodiment, the status report is described by taking the control message in the AM message (Acknowledged Mode) as an example, but the embodiment of the present invention does not limit the category of the status report.
[0111] Specifically, Oct1 includes a D / C indicator bit (Data / Control), a CPT indicator bit (ControlPDU Type) and an ACK_SN (Acknowledgement_Serial Number). In this embodiment, the D / C indicator bit is used to indicate whether the message category is a data message or a control message, the CPT indicator bit is used to indicate the type of the RLC entity control PDU, and the ACK_SN is positive feedback information, indicating that the PDU preceding the PDU corresponding to the ACK_SN and not the PDU corresponding to the NACK_SN has been correctly received by the receiving end.
[0112] Oct2 includes ACK_SN and E1 (Extension bit 1). In this embodiment, E1=1 indicates that there is NACK_SN in the following byte.
[0113] Oct3 includes NACK_SN (Negative Acknowledgement_Serial Number, error confirmation sequence number), NACK_SN is negative feedback information, indicating that the receiving end has not correctly received the data.
[0114] Oct4 includes E1, E2 (Extension bit 2) and NACK_SN. In this embodiment, E2=1 indicates that SO_START and SO_END are after NACK SN.
[0115] Oct5 includes NACK_SN, E1 and E2.
[0116] Oct6 includes SOstart (Segment Offset start), which is used to indicate the offset position of the first byte of the incorrectly received data portion in the PDU corresponding to the NACK_SN in the original PDU.
[0117] Oct7 includes SOstart and SOend (Segment Offset end), and SOend is used to indicate the offset position of the last byte of the incorrectly received data part in the PDU corresponding to NACK_SN in the original PDU.
[0118] Oct8 includes SOend.
[0119] Oct9 includes NACK_SN.
[0120] It should be understood that the embodiments of the present invention are described by taking the status report including 4 negative feedback information NACK_SN as an example. However, the embodiments of the present invention do not limit the number of negative feedback information NACK_SN included in the status report. The status report may not include the negative feedback information NACK_SN and only include the positive feedback information ACK_SN, or may include one NACK_SN, or may also include multiple NACK_SN.
[0121] Furthermore, the embodiments of the present invention do not limit the number of NACK_SN, SOstart, and SOend included in the status report either. The number of NACK_SN, SOstart, and SOend can be determined by the receiving end according to the data reception situation.
[0122] Thus, the sending end can determine the data correctly received by the receiving end among the sent data according to the positive feedback information ACK_SN in the status report fed back by the receiving end, and determine the data not correctly received by the receiving end among the sent data according to the negative feedback information NACK_SN in the status report.
[0123] In this embodiment, the RLC entity at the sending end maintains a sending window through the acknowledged status value VT(A) and the maximum sendable status value VT(MS).
[0124] Specifically, the acknowledged status value VT(A) represents the sequence number of the first RLC PDU to be acknowledged and received in sequence. The first RLC PDU to be acknowledged and received is expected to be acknowledged according to the status report replied by the receiving end next time, and the sequence number of the RLC PDU corresponding to VT(A) is the lower edge of the sending window.
[0125] The maximum sendable status value VT(MS) represents the sequence number of the last RLC PDU to be acknowledged and received in sequence, and the sequence number of the RLC PDU corresponding to VT(MS) is the upper edge of the sending window.
[0126] Furthermore, for the RLC PDU whose sequence number falls within the sending window, that is, VT(A)<=SN<VT(MS), the RLC entity at the sending end sends the RLC PDU corresponding to this sequence number to the receiving end. For the RLC PDU whose sequence number falls outside the sending window, the RLC entity at the sending end does not send the RLC PDU corresponding to this sequence number temporarily.
[0127] In this embodiment, the RLC entity at the transmitting end determines the PDU sequence number corresponding to the confirmation status value VT(A) of the sending window when the status report is received as the initial confirmation status value preVta in response to receiving the status report. Specifically, the RLC entity records the sequence number of the first RLC PDU to be confirmed received corresponding to the VT(A) of the sending window when the status report is received as the initial confirmation status value preVta.
[0128] Step S302: The RLC entity determines the initial SDU identifier according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value.
[0129] In this embodiment, the RLC entity at the transmitting end determines the initial SDU identifier First SDU Id according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value preVta.
[0130] Step S303: In response to the status report including at least one negative feedback information, the RLC entity determines the first service data packet SDU identifier according to the first negative feedback information in the status report.
[0131] In this embodiment, step S303 also includes step S3031 and step S3032. Specifically, Figure 7 1 is a flow chart of a method for determining a first SDU identifier according to the first negative feedback information in a status report by an RLC entity at a transmitting end according to an embodiment of the present invention. Figure 7 As shown, the method for the RLC entity at the transmitting end of the embodiment of the present invention to determine the first SDU identifier according to the first negative feedback information in the status report includes the following steps:
[0132] Step S3031: The RLC entity determines a first confirmation status value according to a PDU sequence number corresponding to the first negative feedback information in the status report.
[0133] In this embodiment, the RLC entity at the transmitting end receives a status report, and in response to the status report including at least one negative feedback information NACK_SN, the RLC entity at the transmitting end determines, based on the first NACK_SN in the status report, that the first confirmation status value is the sequence number of the RLC PDU corresponding to the first NACK_SN, and at the same time, the RLC entity updates the confirmation status value VT(A) to the first confirmation status value.
[0134] Step S3032: Determine a first SDU identifier according to the identifier of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value.
[0135] In this embodiment, the RLC entity at the transmitting end records the sequence number of the last PDU before the PDU corresponding to the first confirmation status value VT(A) as VT(A)-1.
[0136] Further, the RLC entity determines the first SDU identifier Last SDU ID according to the identifier of the last SDU included in the PDU corresponding to VT(A)-1.
[0137] In this embodiment, an RLC PDU including a combination of multiple incomplete SDUs and multiple complete SDUs is used for illustration, but the embodiment of the present invention does not limit the number of RLC SDUs included in the RLC PDU and the completeness of the RLC SDUs included in the RLC PDU. For example, the RLC PDU includes one or more complete RLC SDUs, or another example is that the RLC PDU includes one incomplete RLC SDU, or another example is that the RLC PDU includes a combination of an incomplete SDU and multiple complete SDUs, etc.
[0138] In this embodiment, step S303 and step S301 can be executed simultaneously, or step S303 and step S301 can be executed in the current step sequence, or step S303 can be executed before step S301.
[0139] In an optional embodiment, the RLC entity at the transmitting end receives a status report, and in response to the status report including positive feedback information ACK_SN and excluding negative feedback information NACK_SN, the RLC entity at the transmitting end determines the first confirmation status value as the sequence number of the RLC PDU corresponding to ACK_SN according to the positive feedback information ACK_SN in the status report, and at the same time, the RLC entity updates the confirmation status value VT(A) to the first confirmation status value. Further, the RLC entity at the transmitting end records the sequence number of the last PDU before the PDU corresponding to the first confirmation status value VT(A) as VT(A)-1, and the RLC entity at the transmitting end determines the first SDU identifier Last SDU ID according to the identifier of the last SDU included in the PDU corresponding to VT(A)-1.
[0140] Step S304: The RLC entity marks the PDUs other than the third state PDUs as first state PDUs in the first buffer.
[0141] In this embodiment, in order to improve the status report processing efficiency of the RLC entity at the transmitting end, the present invention implements dividing the RLC PDU into a first status PDU, a second status PDU, a third status PDU and a fourth status PDU.
[0142] Specifically, the first state is ACK, indicating that the receiving end has correctly received the data.
[0143] The second state is NACK, which indicates that the receiving end has not received the data correctly.
[0144] The third state is ACKED, indicating that the RLC entity has confirmed the data correctly received by the receiving end and to be confirmed and processed.
[0145] The fourth state is NULL, indicating new data when the sender sends new data to the receiver.
[0146] In this embodiment, in response to the RLC entity at the transmitting end receiving the status report, the RLC entity at the transmitting end marks the PDU other than the ACKED status PDU as the ACK status in the first buffer. The first buffer is used to buffer the data sent by the transmitting end to the receiving end, and the ACKED status PDU is the data that the RLC entity has previously received the status report and has confirmed that the receiving end has correctly received and is to be confirmed.
[0147] In an optional embodiment, the RLC entity at the transmitting end, in response to receiving a status report and the PDUs other than the ACKED status PDU in the first cache include the NULL status PDU, marks the PDUs other than the ACKED status PDU as ACK status in the first cache. Further, if the first cache includes other status PDUs other than the ACKED status PDU, marks the PDUs other than the ACKED status PDU as ACK status in the first cache.
[0148] In this embodiment, step S304 and step S301 may be executed simultaneously, step S304 and step S301 may also be executed in the current step sequence, and step S304 may also be executed before step S301.
[0149] Step S305: Mark the incorrectly received data in the first state PDU as a second state PDU according to the negative feedback information in the status report.
[0150] In an optional embodiment, the RLC entity at the transmitting end marks the incorrectly received data in the ACK state PDU in the first buffer as NACK state according to all NACK_SNs in the status report. Specifically, the RLC entity at the transmitting end obtains all NACK_SNs in the status report, and marks the incorrectly received data other than the ACKED state PDU in the first buffer as NACK state according to all NACK_SNs.
[0151] Step S306: Mark the PDU whose sequence number is greater than or equal to the first confirmation status value and is not the second status PDU as a third status PDU.
[0152] In this embodiment, the RLC entity at the transmitting end marks the PDU in the first buffer whose sequence number is greater than or equal to the first confirmation status value VT(A) and is not a NACK status PDU as an ACKED status.
[0153] Step S307: Cache the information of the second status PDU into the second cache.
[0154] In this embodiment, the RLC entity at the transmitting end caches the information of the NACK state PDU in the first cache to the second cache, waiting for scheduling for retransmission, and the second cache is used to cache the information of the data to be retransmitted.
[0155] In an optional embodiment, the information of the PDU includes a PDU identifier, a PDU memory pointer, and the length of the RLC SDU protocol header included in the PDU.
[0156] It should be understood that the embodiment of the present invention is explained by taking the information of the PDU including the PDU identifier, the PDU memory pointer and the length of the SDU protocol header included in the PDU as an example, but the embodiment of the present invention does not limit the information of the PDU. For example, the information of the PDU also includes an encryption count value, the RLC SDU protocol header content included in the PDU, the compression header length, etc.
[0157] Step S308: The SDU corresponding to the first SDU identifier represents an incomplete SDU.
[0158] In this embodiment, if the SDU corresponding to the first SDU identifier Last SDU ID represents an incomplete SDU, step S309 is executed. If the SDU corresponding to the first SDU identifier Last SDU ID represents a complete SDU, step S311 is executed.
[0159] Step S309: The initial SDU identifier is different from the first SDU identifier.
[0160] In this embodiment, if the initial SDU identifier First SDU Id is different from the first SDU identifier Last SDU ID, step S310 is executed. If the initial SDU identifier is the same as the first SDU identifier, step S317 is executed.
[0161] Step S310: The RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value.
[0162] In this embodiment, the RLC entity updates the first SDU identifier Last SDU ID to the identifier of the SDU before the last SDU included in the PDU corresponding to VT(A)-1.
[0163] Step S311: The RLC entity sends a first signaling to a packet data convergence protocol layer PDCP entity.
[0164] In this embodiment, the RLC entity at the transmitting end sends a first signaling to the PDCP entity at the transmitting end, wherein the first signaling includes a first SDU identifier, and the first SDU identifier is the Last SDU ID or the identifier of the previous SDU of the last SDU included in the PDU corresponding to VT(A)-1.
[0165] Step S312: Delete the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP protocol data packet PDU corresponding before the first SDU identifier from the PDCP cache according to the first signaling.
[0166] In this embodiment, the PDCP entity at the transmitting end responds to receiving the first signaling, traverses the PDCP PDU linked list header to the PDCP PDU corresponding to the first SDU identifier, deletes the PDCP PDU data memory and linked list corresponding to the first SDU identifier and before the first SDU identifier in the PDCP cache, and executes steps S313 and S314 after executing this step.
[0167] Step S313: Delete the information of the first state PDU and the information of the third state PDU in the second cache.
[0168] In an optional embodiment, the RLC entity at the transmitting end deletes the information of the PDUs corresponding to the ACK status PDU and the ACKED status PDU in the second cache in the second cache, that is, the RLC entity at the transmitting end deletes the information that the receiving end has confirmed that the data has been correctly received in the second cache, and the second cache is used to cache information of data that needs to be retransmitted, and the current step ends.
[0169] Step S314: The RLC PDU sequence number is less than the first confirmation status value.
[0170] In this embodiment, if the RLC PDU sequence number is less than the RLC PDU sequence number corresponding to the first confirmation status value VT(A), step S315 is executed. If the RLC PDU sequence number is greater than the RLC PDU sequence number corresponding to the first confirmation status value VT(A), step S316 is executed.
[0171] Step S315: Delete the PDU linked list and data memory corresponding to the sequence number less than the first confirmation status value in the first cache.
[0172] In this embodiment, the RLC entity at the transmitting end deletes the RLC PDU linked list and data memory corresponding to the sequence number less than the first confirmation status value VT(A) in the first cache, and the first cache is used to cache the data sent to the receiving end, and the current step ends.
[0173] Step S316: Delete the PDU data memory whose sequence number is greater than the first confirmation status value and is not the second status PDU in the first cache, and retain the PDU information.
[0174] In this embodiment, the RLC entity at the transmitting end deletes the PDU data memory whose sequence number is greater than the first confirmation status value VT(A) and is not a NACK status PDU in the first cache, and retains the PDU information whose sequence number is greater than the first confirmation status value VT(A) and is not a NACK status PDU.
[0175] In an optional embodiment, the RLC entity at the transmitting end retains NACK status PDU data memory and information in a first buffer.
[0176] After executing this step, execute step S317
[0177] Step S317: The RLC entity waits for receiving a subsequent status report.
[0178] In this embodiment, the RLC entity at the transmitting end waits for receiving a subsequent new status report and then continues to process the subsequently received new status report. In response to receiving a new status report, the process returns to step S301.
[0179] The technical solution of the embodiment of the present invention is that the RLC entity receives a status report, and in response to at least one negative feedback information included in the status report, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process.
[0180] Further, Figure 8 FIG. 1 is a flow chart of a method in which a transmitting end requests a receiving end to reply to a status report according to an embodiment of the present invention. Figure 8 As shown, the method for a transmitting end to request a receiving end to reply a status report in an embodiment of the present invention includes the following steps:
[0181] Step S400: The RLC entity queries the current memory status.
[0182] In this embodiment, during the process of sending data, the RLC entity at the sending end queries the current memory status in response to receiving a data packet sent by the PDCP entity at the sending end. The memory status includes a sufficient memory status and an insufficient memory status. The sufficient memory status and the insufficient memory status can be determined by the memory usage rate being lower or higher than a set threshold. The threshold can be one or more.
[0183] In an optional implementation, the threshold is set by the user. For example, the user sets the threshold to 70%. When the memory usage is lower than 70%, the RLC entity memory state is a sufficient memory state; when the memory usage is higher than 70%, the RLC entity memory state is an insufficient memory state.
[0184] In another optional implementation, the threshold is automatically set by the sending end. For example, the sending end automatically sets the threshold to 70%.
[0185] In an optional embodiment, the insufficient memory state also includes a memory not full state and a memory full state. Specifically, the thresholds are set to 50% and 70%. When the memory usage rate is lower than 50%, the memory state is a memory sufficient state; when the memory usage rate is higher than 50% and the memory usage rate is lower than 70%, the RLC entity memory state is a memory not full state; when the memory usage rate is higher than 70%, the RLC entity memory state is a memory full state.
[0186] In this embodiment, the PDCP entity at the transmitting end compresses, encrypts, and appends a PDCP header to generate a PDCP PDU (Protocol Data Unit), and then the PDCP entity allocates memory to store the PDCP PDU in the PDCP PDU cache, and sends the PDCP PDU to the RLC entity at the transmitting end.
[0187] Furthermore, the RLC entity at the transmitting end stores the data sent by the PDCP entity into an RLC SDU linked list (Service Data Unit).
[0188] The PHY entity at the transmitting end detects the uplink scheduling sent by the receiving end, and instructs the MAC entity at the transmitting end to read data through the RLC SDU cache. The MAC entity at the transmitting end divides / concatenates the RLC SDU into RLC PDU according to the uplink scheduling. The RLC PDU may include one or more complete RLC SDUs, or only one incomplete RLC SDU, or a combination of an incomplete SDU and a complete SDU.
[0189] Furthermore, the MAC entity at the sending end adds a MAC header to the RLC PDU or adds a MAC header through a MAC CE (MAC Control Element), and then forms a TB (Transport Block) which is sent by the PHY entity at the sending end to the receiving end, thereby realizing data transmission between the sending end and the receiving end.
[0190] Step S410: In response to the memory status indicating that the memory is insufficient or multiple data packets have been sent and are waiting to be confirmed, the RLC entity sets the polling bit to 1 in the sent data.
[0191] In an optional embodiment, in response to receiving data sent by the PDCP entity of the transmitting end, the RLC entity of the transmitting end queries the current memory status, and simultaneously queries the RLC SDU linked list and the RLC retransmission cache status. In response to the memory status indicating insufficient memory or multiple data packets have been sent to be confirmed or there are no new data packets in the RLC cache and no retransmission data packets need to be sent or the sending window has reached the maximum and data packets cannot be sent, the RLC entity of the transmitting end sets the polling bit in the sending data to 1, and the polling bit is the POLL Bit, which is used to request a reply status report from the receiving end.
[0192] In another optional embodiment, in response to the memory status indicating that the memory is insufficient or multiple data packets have been sent and are awaiting confirmation, the RLC entity at the transmitting end sets the POLL Bit to 1 in the transmitted data.
[0193] In an optional implementation, the RLC entity at the transmitting end sets POLL_SN in the RLC header of the first RLC PDU to be sent in the RLC sending buffer, where the POLL_SN (POLL Serial Number) represents the sequence number of the RLC PDU with the POLL Bit set to 1 in the RLC header.
[0194] In this embodiment, the multiple data packets that have been sent and are awaiting confirmation can be determined by a set threshold. For example, the number of sent and unconfirmed data packets is set to 10. The RLC entity at the transmitting end sets the polling bit to 1 in the transmitted data in response to 10 data packets being sent and awaiting confirmation.
[0195] In an optional implementation, the number of sent but unacknowledged data packets is set by the user.
[0196] In another optional implementation, the sending end automatically sets the number of sent but unacknowledged data packets.
[0197] Step S420: Send data.
[0198] In this embodiment, the transmitting end sends the RLC PDU with the POLL_SN to the receiving end, so that the receiving end replies with a status report.
[0199] In an optional embodiment, the transmitting end is further configured with a timing module for recording the time when the transmitting end has sent the RLC PDU with POLL_SN. In response to the fact that the time of sending the RLC PDU with POLL_SN exceeds the predetermined time without receiving the reply status report from the receiving end, the RLC entity of the transmitting end sets the polling bit to 1 again in the transmitted data. The specific implementation method is similar to step S410, and the invention will not be repeated here.
[0200] Step S430: The RLC entity parses the data packet and determines that the polling bit is 1.
[0201] In this embodiment, the RLC entity at the receiving end receives a data packet, and determines the RLC PDU sequence number with the polling bit set to 1 according to the RLC PDU with POLL_SN set in the data packet.
[0202] Step S440: In response to determining that the polling bit is 1 or data is not correctly received, feeding back a status report.
[0203] In this embodiment, in response to determining that the polling bit is 1 or that the data is not correctly received, the receiving end feeds back a status report to the sending end.
[0204] The technical solution of the embodiment of the present invention is that the RLC entity responds to the memory status characterization that the memory is insufficient or multiple data packets have been sent to be confirmed or there are no new data packets and retransmission data packets in the RLC cache that need to be sent or the sending window reaches the maximum and the data packet cannot be sent, and sets the polling bit in the sending data so that the receiving end can feedback the status report. Then the RLC entity receives the status report, and in response to the status report including at least one negative feedback information, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, improves the status report processing efficiency, reduces the signaling overhead, and optimizes the inter-layer interaction process.
[0205] Fig. 9FIG. 1 is a flow chart of communication between an RLC entity at a transmitting end and a PDCP entity at a transmitting end during a link failure reconnection process according to an embodiment of the present invention. Fig. 9 As shown, the communication between the RLC entity at the transmitting end and the PDCP entity at the transmitting end during the link failure reconnection process of the embodiment of the present invention includes the following steps:
[0206] Step S510: In response to link failure reconnection and the first buffer including at least one third status PDU, the RLC entity determines an identifier of an SDU included in the at least one third status PDU.
[0207] In this embodiment, in response to link failure reconnection and the first buffer including at least one ACKED status PDU, the RLC entity at the transmitting end determines the identifier of the SDU included in the at least one ACKED status PDU.
[0208] In an optional embodiment, in response to link failure reconnection and the first buffer including multiple ACKED status PDUs, the RLC entity at the transmitting end determines the identifiers of the SDUs included in the multiple ACKED status PDUs according to the sequence numbers of the multiple ACKED status PDUs.
[0209] In another optional embodiment, in response to link failure reconnection and when any ACKED status PDU included in the first cache includes multiple SDUs, the RLC entity at the transmitting end determines multiple SDU identifiers according to the identifiers of the multiple SDUs included in the ACKED status PDU.
[0210] Step S520: The RLC entity sends at least one signaling to the PDCP entity, where the signaling includes an identifier of the SDU.
[0211] In this embodiment, the RLC entity at the transmitting end sends at least one signaling to the PDCP entity at the transmitting end, where the signaling includes the identifier of the SDU.
[0212] In an optional embodiment, after the RLC entity at the transmitting end sends at least one signaling to the PDCP entity at the transmitting end, the RLC entity at the transmitting end deletes the data cache corresponding to the identifier of the SDU in the first cache.
[0213] In another optional embodiment, in response to link failure reconnection and the first buffer not including an ACKED status PDU, the RLC entity at the transmitting end does not send signaling to the PDCP entity at the transmitting end.
[0214] In another optional embodiment, in response to link failure reconnection and the first cache including multiple ACKED status PDUs, the RLC entity sends multiple signalings to the PDCP entity in sequence according to the sequence numbers of the multiple ACKED status PDUs, and each signaling includes an identifier of an SDU included in an ACKED status PDU.
[0215] In another optional embodiment, in response to link failure reconnection and any ACKED status PDU included in the first cache includes multiple SDUs, the RLC entity at the transmitting end sends multiple signalings to the PDCP entity in sequence according to the sequence numbers of the multiple SDUs included in the ACKED status PDU, and each signaling includes an identifier of an SDU included in the ACKED status PDU.
[0216] Step S530: Delete the PDCP PDU corresponding to the SDU identifier from the PDCP buffer according to the signaling.
[0217] In this embodiment, in response to receiving at least one signaling, the PDCP entity at the transmitting end deletes the PDCP PDU corresponding to the SDU identifier in the signaling from the PDCP buffer.
[0218] The technical solution of the embodiment of the present invention is that the RLC entity receives a status report, and in response to at least one negative feedback information included in the status report, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process.
[0219] Fig.10 is a flow chart of a communication device according to an embodiment of the present invention. Fig.10In the illustrated embodiment, the communication device is applicable to a transmitting end and a receiving end, and the communication device includes a receiving unit 411, an identification determination unit 412, a signaling sending unit 413 and a data control unit 414. Among them, the receiving unit 411 is used for the radio link control layer RLC entity to receive a status report. The identification determination unit 412 is used for the RLC entity to determine the first service data packet SDU identifier according to the first negative feedback information in the status report in response to at least one negative feedback information included in the status report. The signaling sending unit 413 is used for the RLC entity to send a first signaling to a packet data convergence protocol layer PDCP entity, and the first signaling includes the first SDU identifier. The data control unit 414 is used to delete the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP protocol data packet PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling.
[0220] In some embodiments, the communication device further comprises:
[0221] The confirmation status value unit is used to determine a first confirmation status value according to a PDU sequence number corresponding to the first negative feedback information in the status report.
[0222] In some embodiments, the identification determination unit 412 is further configured to:
[0223] The first SDU identifier is determined according to the identifier of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value.
[0224] In some embodiments, the confirmation status value unit is further used to:
[0225] The RLC entity determines the initial confirmation status value according to the PDU sequence number corresponding to the confirmation status value of the sending window when receiving the status report.
[0226] In some embodiments, the identification determination unit 412 is further configured to:
[0227] The initial SDU identifier is determined according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value.
[0228] In some embodiments, the identification determination unit 412 is further configured to:
[0229] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being different from the first SDU identifier, the RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU contained in the last PDU before the PDU corresponding to the first confirmation status value.
[0230] In some embodiments, the signaling sending unit 413 is further configured to:
[0231] In response to the SDU corresponding to the first SDU identifier representing a complete SDU, the RLC entity sends the first signaling to the PDCP entity; or
[0232] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being different from the first SDU identifier, the RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU contained in the last PDU before the PDU corresponding to the first confirmation status value, and the RLC entity sends the first signaling to the PDCP entity.
[0233] In some embodiments, the receiving unit 411 is further configured to:
[0234] In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being the same as the first SDU identifier, the RLC entity waits to receive a subsequent status report.
[0235] In some embodiments, the communication device further comprises:
[0236] The first cache is used to cache data sent to the receiving end.
[0237] In some embodiments, the communication device further comprises:
[0238] A data status marking unit is used to mark PDUs other than the third-state PDU as first-state PDUs in a first cache in response to the RLC entity receiving the status report, wherein the first-state PDU represents a PDU that the RLC entity has confirmed to be correctly received, and the third-state PDU represents a PDU that the RLC entity has confirmed to be correctly received and is to be confirmed and processed.
[0239] In some embodiments, the data status marking unit is further used to:
[0240] According to the negative feedback information in the status report, the data that is not correctly received in the first status PDU is marked as a second status PDU.
[0241] In some embodiments, the data status marking unit is further used to:
[0242] The PDU whose sequence number is greater than or equal to the first confirmation status value and is not the second status PDU is marked as the third status PDU.
[0243] In some embodiments, the communication device further comprises:
[0244] The second buffer is used to buffer information of data that needs to be retransmitted.
[0245] In some embodiments, the data control unit 414 is further configured to:
[0246] The information of the second status PDU is cached in a second cache.
[0247] In some embodiments, the data control unit 414 is further configured to:
[0248] The information of the first status PDU and the information of the third status PDU are deleted in the second buffer.
[0249] In some embodiments, the communication device further comprises:
[0250] Link failure reconnection unit, used for link failure reconnection.
[0251] In some embodiments, the identification determination unit 412 is further configured to:
[0252] In response to link failure reconnection and the first buffer including at least one of the third status PDUs, the RLC entity determines an identifier of an SDU included in the at least one of the third status PDUs.
[0253] In some embodiments, the signaling sending unit 413 is further configured to:
[0254] The RLC entity sends at least one signaling to the PDCP entity, where the signaling includes an identifier of the SDU.
[0255] In some embodiments, the data control unit 414 is further configured to:
[0256] The PDCP PDU corresponding to the identifier of the SDU is deleted from the PDCP buffer according to the signaling.
[0257] In some embodiments, the communication device further comprises:
[0258] Memory status unit, used to indicate low memory.
[0259] The data packet sending unit is used to determine that a plurality of data packets have been sent and are to be confirmed.
[0260] A polling bit unit is used to respond to the memory status characterizing insufficient memory or multiple data packets have been sent and are waiting to be confirmed. The RLC entity sets a polling bit in the sent data, and the polling bit is used to request a reply status report from the receiving end.
[0261] The technical solution of the embodiment of the present invention is that the RLC entity receives a status report, and in response to at least one negative feedback information included in the status report, the RLC entity determines the first SDU identifier according to the first negative feedback information in the status report, and then the RLC entity sends a first signaling to the PDCP entity, and the first signaling includes the first SDU identifier, so that the PDCP entity deletes the PDCP protocol data packet PDU corresponding to the first SDU identifier and the PDCP PDU corresponding to the first SDU identifier in the PDCP cache according to the first signaling. Therefore, when the status report includes multiple negative feedback information, the RLC entity only sends one signaling to the PDCP entity, so that the PDCP entity deletes the correctly received data according to the signaling, thereby improving the status report processing efficiency, reducing the signaling overhead, and optimizing the inter-layer interaction process.
[0262] Fig.11 is a schematic diagram of an electronic device according to an embodiment of the present invention. Fig.11 The electronic device shown can be a general-purpose data processing chip or device. The data processing chip or device includes a general-purpose computer hardware structure, which includes at least a processor 421 and a memory 422. The processor 421 and the memory 422 are connected via a bus 423. The memory 422 is suitable for storing instructions or programs executable by the processor 421. The processor 421 can be an independent microprocessor or a collection of one or more microprocessors. Thus, the processor 421 executes the instructions stored in the memory 422, thereby executing the method flow of the embodiment of the present invention as described above to realize the processing of data and the control of other devices. The bus 423 connects the above-mentioned multiple components together, and at the same time connects the above-mentioned components to the display controller 424 and the display device and the input / output (I / O) device 425. The input / output (I / O) device 425 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a somatosensory input device, a printer, and other devices known in the art. Typically, the input / output device 425 is connected to the system via an input / output (I / O) controller 426.
[0263] It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as methods, electronic devices or computer program products. Therefore, the present invention may take the form of a complete hardware embodiment, a complete software embodiment or an embodiment combining software and hardware. Moreover, the present invention may take the form of a computer program product implemented on one or more computer-readable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.
[0264] The present invention is described with reference to flowcharts of methods, electronic devices and computer program products according to embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.
[0265] These computer program instructions may be stored in a computer-readable memory that can direct a computer or other programmable data processing chip or device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture including an instruction device that implements the process Figure 1 A function specified in a process or multiple processes.
[0266] These computer program instructions may also be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing chip or device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing chip or device generate a machine configured to implement the process Figure 1 A device that specifies functions in a process or multiple processes.
[0267] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included in the protection scope of the present invention.
Claims
1. A communication method, characterized in that: The method comprises: A radio link control layer RLC entity receives a status report, and in response to the status report including at least one negative feedback information, the RLC entity determines a first service data packet SDU identifier according to first negative feedback information in the status report, wherein the negative feedback information is used to represent data that is not correctly received by the receiving end; The RLC entity sends a first signaling to a Packet Data Convergence Protocol layer PDCP entity, where the first signaling includes the first SDU identifier; and Deleting the PDCP protocol data packet PDU corresponding to the first SDU identifier and corresponding before the first SDU identifier from the PDCP cache according to the first signaling; The RLC entity determining the first service data packet SDU identifier according to the first negative feedback information in the status report includes: Determine a first confirmation status value according to the PDU sequence number corresponding to the first negative feedback information in the status report; and Determine the first SDU identifier according to the identifier of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value; Wherein, the method further comprises: The RLC entity determines an initial confirmation status value according to a PDU sequence number corresponding to the confirmation status value of the sending window when receiving the status report; Determine the initial SDU identifier according to the identifier of the first SDU included in the PDU corresponding to the initial confirmation status value; In response to the SDU corresponding to the first SDU identifier representing a complete SDU, the RLC entity sends the first signaling to the PDCP entity; In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being different from the first SDU identifier, the RLC entity updates the first SDU identifier to the identifier of the previous SDU of the last SDU included in the last PDU before the PDU corresponding to the first confirmation status value, and the RLC entity sends the first signaling to the PDCP entity; and In response to the SDU corresponding to the first SDU identifier representing an incomplete SDU and the initial SDU identifier being the same as the first SDU identifier, the RLC entity waits to receive a subsequent status report.
2. The method according to claim 1, characterized in that The method further comprises: In response to the RLC entity receiving the status report, marking a PDU other than the third status PDU as a first status PDU in a first buffer, the first buffer being used to buffer data sent to the receiving end, the first status PDU representing a PDU that the RLC entity has confirmed to be correctly received, and the third status PDU representing a PDU that the RLC entity has confirmed to be correctly received and to be confirmed and processed; Marking the incorrectly received data in the first status PDU as a second status PDU according to the negative feedback information in the status report; and A PDU whose sequence number is greater than or equal to the first confirmation status value and is not a second-state PDU is marked as the third-state PDU.
3. The method according to claim 2, characterized in that The method further comprises: Cache the information of the second status PDU in a second cache, where the second cache is used to cache information of data that needs to be retransmitted; and The information of the first status PDU and the information of the third status PDU are deleted in the second buffer.
4. The method according to claim 2, characterized in that: The method further comprises: In response to link failure reconnection and the first buffer including at least one of the third status PDUs, the RLC entity determines an identifier of an SDU included in at least one of the third status PDUs; The RLC entity sends at least one signaling to the PDCP entity, where the signaling includes an identifier of the SDU; and The PDCP PDU corresponding to the identifier of the SDU is deleted from the PDCP buffer according to the signaling.
5. The method according to claim 1, characterized in that The method further comprises: In response to the memory status indicating insufficient memory or multiple data packets having been sent and waiting to be confirmed, the RLC entity sets a polling bit in the transmitted data, wherein the polling bit is used to request a reply status report from the receiving end.
6. A computer-readable storage medium having computer program instructions stored thereon, characterized in that: The computer program instructions implement the method according to any one of claims 1 to 5 when executed by a processor.
7. An electronic device comprising a memory and a processor, characterized in that: The memory is used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the method according to any one of claims 1 to 5.
