WO2018028697A1 - State report generating method and system and state report receiving method and device - Google Patents

Abstract

The embodiments of the present invention provide a state report generating method and system, and a state report receiving method and device. The state report generating method comprises: generating a state report by a receiving-end device, the state report carrying indication information for indicating one or more lost data packages; and sending the state report to a sending-end device by the receiving-end device. The present invention using the described technical solution solves the problem that a state report sent by a receiving-end device occupies a large space when a transmission error of a data occurs in the related technologies, thus greatly reducing the transmission occupation space of the state report.

Description

Status report generation method and system, and status report receiving method and device Technical field

The embodiments of the present invention relate to the field of communications, and in particular, to a method and system for generating a status report, and a method and a device for receiving a status report.

Background technique

In the related art, the user plane status reporting mechanism is applied to the case of some radio bearers that need to receive and confirm the receiving end, the receiving end feeds back the data receiving state, and the receiving end feedbacks to notify the user side related entity of the sending end. The data packet information received by the receiving end when the reconstruction is completed, so as to reduce the unnecessary duplicate data packet transmission after the completion of the reconstruction of the user plane related entity on the transmitting end.

In the 4G communication network in the related art, the feedback status report of the user plane entity, such as the Packet Data Convergence Protocol (PDCP), is in the form of a bitmap file bitmap, in the future 5G communication network, along with the traffic volume. As the data transmission rate increases, the sequence number SN length of the data packet also increases. For example, the SN length is 18 bits or longer, and the transmission and reception window of the user plane entity is expanded accordingly, so that the user plane entity such as the bitmap in the PDCP status report is expanded. The bit length of the NS is also increased. In a scenario where the bearer is separated, when a branch data transmission link is unstable, a continuous SN number may occur, and the SN number spans. In a large case, when a PDCP status report is generated according to the format of the current PDCP status report, a sufficiently large bitmap field is required to indicate the PDCP PDU transmission status of a certain time segment, and even the status PDU size exceeds the upper limit of the PDCP Control PDU.

For example, in the case of high frequency, low frequency bear split or high frequency, WLAN bear split, if the PDCP packet of the slow rate is lost, according to the definition of the current bitmap, the Protocol Data Unit (referred to as the Protocol Data Unit) The size of the PDU) may exceed the upper limit of the PDCP PDU. Specifically, if the SN=X packet and the SN=Y packet are lost in the data transmission, the number of bits that the status PDU needs to carry is Y-X, considering that the SN can be 18 bits, Even if only 2 packets are lost, this value may be very large, which will occupy a large block field, and may even exceed the upper limit of the PDU size, which makes the generation and parsing of the status PDU low and the bit overhead is large.

In the related art, when there is a transmission error in the data, the status report sent by the receiving device consumes a large space, and there is currently no effective solution.

Summary of the invention

The embodiment of the invention provides a method and a system for generating a status report, and a method and a device for receiving a status report, so as to solve at least the problem that the status report sent by the receiving device has a large space when there is a transmission error in the related art.

According to an embodiment of the present invention, a method for generating a status report is provided, including:

The receiving device generates a status report, where the status report carries indication information for indicating one or more lost data packets;

The receiving end device sends the status report to the sending end device.

Optionally, the receiving device generates a status report, including:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated according to the bitmap segmentation.

Optionally, determining, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

The starting position information of each segment, the length information of each segment.

Optionally, the starting location information is used to indicate the first lost packet sequence number SN of each segment.

Optionally, the length information is used to indicate a bit length of a segmented bitmap field, where a bit length of the bitmap field is equal to a first lost data packet of the segment to a last lost data of the segment. The length of the package.

Optionally, the status report carries a data packet indicating one or more missing packets. Instructions, including:

In the case that the receiving device does not segment the lost data packet, the status report carries the sequence number of each lost data packet.

According to another embodiment of the present invention, a method for receiving a status report is provided, including:

The sending end device receives the status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets;

The sending end device sends the lost data packet to the receiving end device according to the indication information.

Optionally, before the sending end device receives the status report sent by the receiving end device, the receiving end device generates the status report by:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated according to the bitmap segmentation.

Optionally, the receiving end device determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

According to another embodiment of the present invention, a status report generating system is further provided, including: a receiving end device, a transmitting end device, wherein the receiving end device includes a first processor and a first communication module, and the sending The end device includes a second processor and a second communication module;

The first processor generates a status report, where the status report carries indication information for indicating one or more lost data packets;

The first communication module sends the status report to the second communication module;

The second processor passes the second communication module to the first according to the indication information A communication module transmits the lost data packet.

Optionally, the first processor generates a status report, including:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated according to the bitmap segmentation.

Optionally, the first processor determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

According to another embodiment of the present invention, a receiving end device is further provided, including: a first processor and a first communication module;

The first processor generates a status report, where the status report carries indication information for indicating one or more lost data packets;

The first communication module sends the status report to the sender device.

Optionally, the first processor generates a status report, including:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated according to the bitmap segmentation.

Optionally, the first processor determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

Optionally, the status report carries indication information for indicating one or more lost data packets, including:

In the case that the receiving device does not segment the lost data packet, the status report carries the sequence number of each lost data packet.

According to another embodiment of the present invention, a transmitting device is further provided, including: a second processor and a second communication module;

The second communication module receives a status report sent by the receiving device, where the status report carries indication information for indicating one or more lost data packets;

The second processor sends the lost data packet to the receiving end device according to the indication information.

Optionally, before the second communication module receives the status report sent by the receiving end device, the receiving end device generates the status report by:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated according to the bitmap segmentation.

Optionally, the receiving end device determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

According to still another embodiment of the present invention, a storage medium is also provided. The storage medium is arranged to store program code for performing the following steps:

The receiving device generates a status report, where the status report carries indication information for indicating one or more lost data packets;

The receiving end device sends the status report to the sending end device.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

The sending end device receives the status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets;

Sending, by the sending end device, the lost data packet to the receiving end device according to the indication information

According to the present invention, after the transmitting device transmits data to the receiving device, the receiving device generates a status report carrying indication information indicating the lost data packet when detecting that there is a transmission error in the data packet. That is, the indication information carries only the information indicating the lost data packet as much as possible, does not contain the data packet with the correct transmission, occupies a small transmission space, and transmits the status report to the transmitting end device, and the transmitting end device can transmit the information. The wrong packet was resent. The problem that the status report sent by the receiving end device takes up a large space when the data has a transmission error is solved in the related art, and the transmission space of the status report is greatly reduced.

DRAWINGS

The drawings described herein are intended to provide a further understanding of the invention, and are intended to be a part of the invention. In the drawing:

1 is a flowchart of a method for generating a status report according to an embodiment of the present invention;

2 is a schematic diagram of a bear split bearer separation architecture according to an embodiment of the present invention;

3 is a schematic diagram of a PDCP (Serial Number 15bit) status report format according to the related art;

4 is a schematic diagram of a PDCP (Serial Number 15bit) status report format based on a segmented bitmap according to Embodiment 1;

5 is a schematic diagram of a PDCP (Serial Number 15bit) status report format without using a bitmap according to Embodiment 2;

6 is a block diagram showing the hardware structure of a receiving end device according to an embodiment of the present invention;

FIG. 7 is a block diagram showing the hardware structure of a transmitting device according to an embodiment of the present invention.

detailed description

The invention will be described in detail below with reference to the drawings in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments may be combined with each other without conflict.

It is to be understood that the terms "first", "second" and the like in the specification and claims of the present invention are used to distinguish similar objects, and are not necessarily used to describe a particular order or order.

Example 1

The embodiment described in the present application can be operated in a 5G system, and the receiving device can be a terminal or a network device, and the device corresponding to the transmitting device can be a network device or a terminal device, that is, the terminal receives the network device. The status report described in this application file may be generated after the data packet is sent, or the network side device may also generate a status report after receiving the data packet uploaded by the terminal. The embodiments described in this application file have the above two scenarios.

FIG. 1 is a flowchart of a method for generating a status report according to an embodiment of the present invention. As shown in FIG. 1 , the process includes the following steps:

S102. The receiving end device generates a status report, where the status report carries indication information for indicating one or more lost data packets.

S104. The receiving end device sends the status report to the sending end device.

After the sending end device sends the data to the receiving end device, the receiving end device generates a status report carrying the indication information for indicating the lost data packet, if the receiving end device detects that there is a transmission error in the data packet. That is, the indication information carries only the information indicating the lost data packet as much as possible, does not contain the data packet with the correct transmission, occupies a small transmission space, and transmits the status report to the transmitting end device, and the transmitting end device can transmit the information. The wrong packet was resent. The problem that the status report sent by the receiving end device takes up a large space when the data has a transmission error is solved in the related art, and the transmission space of the status report is greatly reduced.

Optionally, the receiving end device generates a status report, including: determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs; generating the status report according to the bitmap segment.

Optionally, the bitmap segment to which the bitmap bitmap information of the data packet belongs is determined according to the following information: start position information of each segment, length information of each segment.

Optionally, the starting location information is used to indicate the first lost packet sequence number SN of each segment.

Optionally, the length information is used to indicate a bit length of the segmented bitmap field, where the bit length of the bitmap field is equal to the first lost packet of the segment to the last lost packet of the segment. length.

Optionally, in a case that the receiving end device does not segment the lost data packet, the status report carries a sequence number of each lost data packet.

According to another embodiment of the present invention, a method for receiving a status report is provided, which is an embodiment written by a sender side, and the steps are as follows:

The sending end device receives the status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets;

The sending end device sends the lost data packet to the receiving end device according to the indication information.

Optionally, before the sending end device receives the status report sent by the receiving end device, the receiving end device generates the status report by:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated based on the bitmap segmentation.

Optionally, the receiving end device determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate the first lost packet sequence number SN of each segment, the length information is used to indicate segmentation The bit length of the bitmap field, where the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

The following is a detailed description in conjunction with a preferred embodiment of the invention:

Compared with related technologies, in future wireless communication networks, with traffic and data transmission As the rate increases, the serial number SN of the data packet and the size of the transceiver window of the user plane entity expand, and the user plane incorrectly receives the length of the bitmap in the packet format, which is long, especially in the scenario of carrying the bear split. When there is a problem with a certain branch, there may be a problem with a continuous SN number, and the span between the SN numbers is large. It is necessary to use a sufficiently large bitmap field to indicate the abnormal reception of the user plane data. The bit overhead is large, and the efficiency of generating and parsing the feedback packet is also low. Based on this problem, in the future 5G wireless communication user plane protocol design, this application file solves the problem of large feedback bit overhead by adopting a segmented bitmap.

The main idea of using the segmented bitmap method in the user plane data receiving state feedback format is that the feedback end does not need to carry the bitmap information of all out-of-order packets in the generated status report. Specific features of the segmented bitmap method include adding start position information, length information, and bitmap information of one and/or multiple lost data packets in the feedback status report, and generating a new user plane status report for indicating one and/or Or multiple lost packets.

The detailed flow of a preferred embodiment of the present invention includes the following:

Before the description of the preferred embodiment, it should be noted that both the terminal and the network user plane entity can be used as the receiving end device in the foregoing embodiment, that is, in the case of data transmission between the two, a status report can be generated. The other party can receive status reports accordingly.

The high-level (such as RRC) configuration terminal and/or network user plane entity sends a status report, and the terminal and/or network user plane entity adopts a segmented bitmap method when generating the status report.

The segmentation bitmap method described in this application file includes the following two methods:

In the mode 1, a new field is added in the status report format, where the new field includes start position information, length information, and bitmap information of one and/or multiple lost data packets. Specifically, mode 1 is segment transmission. Way, adding a new field, that is, the sequence number of the first lost data packet containing the segment, and the segment contains N data packets, that is, length information, starting from the first lost data packet, Packets within N (including the Nth) are the contents of the segment.

Mode 2, adding a new field in the status report format, the new field includes the next one Missing packet sequence number, no length information and bitmap information. Mode 2 is the ultimate thinking of segmented transmission, that is, each lost data packet is a segment. Of course, in the case of more lost data packets, too many segmentation will also occupy additional transmission space. Find an optimal approach between the number of segments and each segment containing as much of the missing packets as possible.

The starting location information of the lost packet is used to indicate the sequence number of the first lost packet of a certain and/or a segment. The number of bits it occupies is related to the length of the data packet SN.

The length information is used to indicate the bit length of the bitmap field, and the number of bits occupied is related to the length of the data packet SN.

The bit length of the bitmap field is variable, and the length thereof is equal to the length of the bitmap field from the next PDCP SDU of the first lost PDCP SDU of each segment to the last out-of-order PDCP SDU of each segment. Round up to an integer multiple of 8.

The status report is used to indicate the receiving status of the user plane data packet and send it to the peer end to indicate whether the data packet needs to be retransmitted by the peer end.

It should be added that the user plane entity processes the received data packet according to the protocol process, and encapsulates the data packet in a format understandable by the peer end.

The following description will be made in conjunction with specific embodiments.

FIG. 2 is a schematic diagram of a bear split bearer separation architecture according to an embodiment of the present invention. As shown in FIG. 2, all user plane data is routed and buffered through the primary base station MeNB, and the secondary base station SeNB user plane data is derived from the MeNB. Downstream: The PDCP entity in the MeNB has a routing function, which is the RLC entity to which eNB; and the uplink: the PDCP entity reorders the received data. Referring to FIG. 2, the above-mentioned scenario of bearer separation bear split mentioned above can be better understood.

FIG. 3 is a schematic diagram of a PDCP (Serial Number 15bit) status report format according to the related art, and FIG. 3 is compiled with reference to the 36323-c00 protocol. A simple example is given to show that the bit length of the Bitmap field will be long as the SN length increases. In the case where a few PDCP SDUs are lost, but the SN number span is large, for example, there are nearly 10,000 out-of-order PDCP SDUs spanned between the two lost packets in Figure 3, then it needs to be large enough. Bitmap domain It can feedback the status of PDCP PDU transmission, which will result in low generation and parsing efficiency of the PDCP status report.

As mentioned above, since the feedback status PDU of the PDCP is in the form of a bitmap, a higher data transmission rate, a shorter transmission delay, and a better user experience are required in the future 5G wireless network, driving the innovation of the entire network architecture design. The user plane protocol architecture also needs to be designed to meet the needs of future business diversity. As the PDCP SN number increases, the PDCP transceiver window will expand, the bit length of the bitmap field will be long, and the PDCP status report generation and parsing efficiency will be improved. The bear split architecture is shown in Figure 2. When a branch data transmission link is unstable, a certain SN number may occur, and the span between SN numbers is very large. In a large case, when a PDCP status report is generated according to the format of the current PDCP status PDU, a sufficiently large bitmap field is required to indicate the PDCP PDU transmission status of a certain time segment, and the PDCP status report size may exceed the upper limit of the PDCP control PDU. Therefore, the PDCP status report format needs to be enhanced, and a segmentation bitmap method is introduced to adapt to the case where the SN number is getting longer and longer. Reduce the bit overhead bitmap field, the PDCP status report generation and improve resolution efficiency is low.

Specific embodiment 1

The specific embodiment 1 corresponds to the mode 1 in the above preferred embodiment.

4 is a schematic diagram of a segmented bitmap based PDCP (Serial Number 15bit) status report format according to Embodiment 1. 4 is based on the assumption that the length of the PDCP sequence number is 15. Therefore, the maximum PDCP sequence number Maximum_PDCP_SN is 32767, that is, the sequence number SN ranges from 0 to 32767, and the reorder window length is the PDCP sequence number. Half the length of the 15-bit space, which is 16384. When the received data packet is the data packet submitted by the RLC in the out-of-order manner when the PDCP is reconstructed, and the data packet is stored in the cache due to the out-of-order condition that is not satisfied to be submitted to the upper layer, the data packet is not submitted to the upper layer temporarily, and the incorrectly received data packet is not received. The generation of the status report will be based on this.

In the PDCP status report format of FIG. 4, the segment bitmap does not include the indication information corresponding to the sequence number of the PDCP SDU that is continuously received by the receiving end and does not need to be retransmitted by the peer end. The current method is to add start point location information, length information, bitmap information, and extension bits of one and/or multiple lost PDUs in the PDCP status report. Since the bitmap information does not need to carry the corresponding serial number indication information of multiple correctly received PDCP SDUs, the bitmap overhead is reduced, and the PDCP status report is prevented from being too large or even exceeds the maximum number of bytes allowed by the PDCP status PDU. The above bitmap segmentation method is applicable to a scenario in which a lost data packet has a large span between SN numbers. The description of each field in Figure 4 is as follows:

The NMS field occupies 15 bits long and is an optional field. It defines the starting position of the PDCP SDU that is lost in the next segment. Whether the field is used or not depends on whether the bitmap domain is segmented. The NMS is used to segment a bitmap field that has a long bit length and has a continuous area that does not need to be retransmitted, and is used for base adjustment of the bitmap bit map, so that the next segment bitmap is based on the NMS. Perform the shift calculation of the SN number of the SDU. The value of the NMS is decremented by the first PDCP SDU sequence number indicated by the next Bitmap. As shown in Figure 4, the first segment bitmap starts with the FMS, assuming FMS = 100, and the first bit of the Bitmap field corresponds. SN=101 of the PDCP SDU to the PN=200 of the PDCP SDU corresponding to the last bit of the Bitmap field, but the PDCP SDU SN=201-5000 data packet does not need to be retransmitted by the peer end, and the subsequent PDCP SDU needs to be retransmitted. The next segment bitmap will skip the PDCP SDU that does not need to be retransmitted from SN=201 to 5000, and only carries the PDCP SDU sequence number indication information that needs to be retransmitted. Therefore, the NMS here takes 5001, and the NMS corresponds to the Bitmap domain. The SN of the PDCP SDU indicated by one bit is 5002, and the SN of the PDCP SDU indicated by the last bit of the Bitmap field is 5100. In this way, the bitmap field is segmented, and the bitmap does not carry the indication information corresponding to the PDCP SDU sequence number that does not need to be retransmitted by the peer end, and the bit overhead of the bitmap is reduced. The calculation formula of the serial number SN of the PDCP SDU received out of order in the segmented bitmap domain is: PDCP SDU sequence number SN=(FMS+bit position)%(Maximum_PDCP_SN+1), or SN=(NMS+ Bit position)%(Maximum_PDCP_SN+1), in the formula, bit position represents the first bit to the Nth bit in the bitmap, the bit position of the first bit is 1, and the bit position of the Nth bit is N.

If the data packets of SN=X, X+2, X+5, X+5000, X+5001, X+5002, and X+5010 need to be retransmitted, the segmentation bitmap method of the specific embodiment 1 may be adopted. ,jump over SN=X+5 and SN=X+5000 packets that do not need to be retransmitted, use two segment bitmaps to carry X and X+5 respectively, and X+5001, X+5002, X+ Packet information between 5010. Specifically, set FMS=X, then use 5 valid bitmaps to carry the packet status of the interval, and set NMS=X+5000, and then use 10 valid bitmaps to carry the packet status of the interval.

Optionally, set the bitmap domain segmentation threshold. During the PDCP status report generation process, the terminal and/or the network calculates the length of the bitmap field and compares it with the bitmap domain segmentation threshold. If the calculated bit field length exceeds the bitmap domain segmentation threshold, according to the figure The PDCP status report format of 4 performs segmentation bitmap generation of the PDCP status report. If the calculated bit field length does not exceed the bitmap domain segmentation threshold, the PDCP status report is generated according to the PDCP status report format of FIG. The segmentation threshold is configurable.

In the status report format shown in FIG. 4, D/C occupies 1 bit, denoted by "0" or "1", "0" indicates that the PDU is a control PDU, and "1" indicates that the PDU is a data PDU. The PDU type occupies 3 bits. For example, "000" indicates that the PDU type is a PDCP status report. 5 reserved bits R, for subsequent use, set to "0", which is ignored by the receiving end when parsing. The extended bit E occupies 1 bit, which is used to indicate whether the next field of E is an L field, and E=1, indicating that the next field of E is an L field. The length indication L is 15 bits, which is an optional field, determined by whether or not the bitmap domain is segmented. The length indication L is used to indicate the bit length of the segmented bitmap field immediately following it. The FMS field occupies 15 bits and is used to indicate the PDCP sequence number of the first PDCP SDU that has not been received.

The Bitmap field has a variable bit length equal to the last PDCP SDU from the next PDCP SDU of the first lost PDCP SDU of each segment to the last out-of-order PDCP SDU of each segment (ie the last lost packet) So far, it should be noted that the length of the bitmap field is rounded up to an integral multiple of 8. Taking the first byte as an example, the MSB (Most Significant Bit) is used to indicate the most significant bit of the first byte of the bitmap field, and is used to indicate the PDCP SDU of SN=(FMS/NMS+1)%(Maximum_PDCP_SN+1). Whether it has been successfully received. If header compression is configured, it also indicates whether the PDCP SDU header compression corresponding to the SN is correct. Use LSB (Least Significant Bit) to represent the least significant bit of the first byte of the bitmap field, used to refer to Whether the PDCP SDU of SN=(FMS/NMS+8)%(Maximum_PDCP_SN+1) has been received, it needs to be added that, in this embodiment (FMS/NMS), the meaning of FMS or NMS is expressed in the formula. When calculating, one of them is used. If the FMS/NMS is configured with header compression, it also indicates whether the PDCP SDU header compression corresponding to the SN is correct. For each segmented bitmap field, the receiving end fills in the corresponding bit of the PDCP SDU that is not received in the bitmap field with “0”. For the case where the header compression is configured, the received but uncompressed header fails. The PDCP SDU is also padded with a "0" in the corresponding bit in the bitmap field. Fill in the other bits in the bitmap field with a "1". In general, the PDCP SDU sequence number SN=(FMS/NMS+bit position)%(Maximum_PDCP_SN+1) is 0, indicating that the data packet needs to be retransmitted; the PDCP SDU sequence number SN=(FMS/NMS+bit position) %(Maximum_PDCP_SN+1) is 1, indicating that the packet does not need to be retransmitted. Where bit position represents the first bit to the Nth bit in the bitmap, the bit position of the first bit is 1, and the bit position of the Nth bit is N.

The specific embodiment 1 generates the status report with SN=15, which is only a better explanation of the main idea of the segmentation bitmap, and does not limit the specific field, the position of the field and the segmentation mode. The SN can be other values, and other corresponding fields can be added, deleted, or modified.

Specific embodiment 2

The specific embodiment 2 corresponds to the mode 2 in the above preferred embodiment.

FIG. 5 is a schematic diagram of a PDCP (Serial Number 15bit) status report format without using a bitmap according to Embodiment 2. When the SN number of the data packet that needs to be retransmitted by the peer end is large, and the data packets that need to be retransmitted are sparsely distributed, the PDCP status report format in the prior art needs to be enhanced to reduce the bit overhead, that is, no bitmap is needed. The out-of-order packet is carried, and only the sequence number SN of the single packet is indicated by the NMS. For example, if a packet with SN=100, 300, 500, 1000 is lost, each lost packet has a large span and is sparsely distributed. It is not suitable for segment report generation. . For this scenario, the sequence number SN corresponding to the PDCP SDU is directly indicated. As shown in FIG. 5, each lost data packet is represented by FMS and NMS, and the data packet that does not need to be retransmitted is skipped.

The NMS indicates the next lost PDCP sequence number, which is an optional field and increases as the number of data packets that need to be retransmitted increases. The extended bit E is used to indicate whether there is NMS following after the FMS and/or NMS. Other D/C, PDU type, reserved bit R are consistent with the description in the specific embodiment 1. The specific embodiment 2 is only for better explanation of the idea of generating a status report, and is not limited by the various fields in the illustration.

The technical solution described in the present application file introduces a segmented bitmap method in the process of generating a user plane status report, which does not need to carry the bitmap information of all the data packets, reduces the bit overhead of the bitmap, and improves the generation of the user plane status report. Analyze efficiency to avoid the size of the user face status report exceeding the upper limit.

Table 1 is a list of technical terms according to an embodiment of the present invention. As shown in Table 1, the full name of the technical terms used in the present embodiment is described.

Table 1

abbreviation	Full name in English	Chinese interpretation
4G/5G	Fourth/Fifth Generation	Fourth/fifth generation mobile communication
WLAN	Wireless Local Area Networks	Wireless LAN
PDCP	Packet Data Convergence Protocol	Packet data convergence protocol
SN	Sequence Number	serial number
FMS	First Missing PDCP SN	The first lost PDCP serial number
NMS	Next Missing PDCP SN	Next missing PDCP serial number
SDU	Service Data Unit	Business data unit
PDU	Protocol Data Unit	Protocol data unit
RRC	Radio Resource Control	Radio resource control
D/C	Data/Control PDU	Data/control PDU
R	Reserved	Reserved
L	Length	Length indication
MSB	Most significant Bit	Most significant bit
LSB	Least significant Bit	Least significant bit
MeNB	Master evolved Node B	Primary evolved Node B
SeNB	Secondary evolved Node B	Secondary evolved Node B

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course, by hardware, but in many cases, the former is A better implementation. Based on such understanding, the technical solution of the present invention may be soft in nature or in part contributing to the prior art. The form of the product is stored in a storage medium (such as ROM / RAM, disk, CD), including a number of instructions to make a terminal device (can be a mobile phone, computer, server, or network) Apparatus, etc.) The method of the various embodiments of the present invention is performed.

Example 2

According to another embodiment of the present invention, a status report generating system is further provided, including: a receiving end device, a transmitting end device, wherein the receiving end device comprises a first processor and a first communication module, and the transmitting end device The second processor and the second communication module are included;

The first processor generates a status report, where the status report carries indication information indicating one or more lost data packets;

The first communication module sends the status report to the second communication module;

The second processor sends the lost data packet to the first communication module by using the second communication module according to the indication information.

Optionally, the first processor generates a status report, including the following steps: determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs; generating the status report according to the bitmap segment.

Optionally, the first processor determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate the first lost packet sequence number SN of each segment, the length information is used to indicate segmentation The bit length of the bitmap field, where the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

Example 3

FIG. 6 is a block diagram showing the hardware structure of a receiving end device according to an embodiment of the present invention. As shown in FIG. 6, the receiving end device 60 includes: a first processor 62 and a first communication module 64;

The first processor 62 generates a status report, where the status report carries a reference An indication indicating one or more lost data packets;

The first communication module 64 sends the status report to the sender device.

Optionally, the first processor 62 generates a status report, including:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated based on the bitmap segmentation.

Optionally, the first processor 62 determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate the first lost packet sequence number SN of each segment, the length information is used to indicate segmentation The bit length of the bitmap field, where the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

Optionally, in the case that the receiving end device 60 does not segment the lost data packet, the status report carries a sequence number of each lost data packet.

FIG. 7 is a block diagram showing the hardware structure of a transmitting device according to an embodiment of the present invention. As shown in FIG. 7, the transmitting device 70 includes: a second processor 72 and a second communication module 74;

The second communication module 74 receives a status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets;

The second processor 72 sends the lost data packet to the receiving end device according to the indication information.

Optionally, before the second communication module 74 receives the status report sent by the receiving device, the receiving device generates the status report by:

Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

The status report is generated based on the bitmap segmentation.

Optionally, the receiving end device 60 determines, according to the following information, a bitmap segment to which the bitmap bitmap information of the data packet belongs:

Start position information of each segment, length information of each segment, wherein the start position information is used to indicate the first lost packet sequence number SN of each segment, the length information is used to indicate segmentation The bit length of the bitmap field, where the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

Example 4

Embodiments of the present invention also provide a storage medium. Optionally, in the embodiment, the foregoing storage medium may be configured to store program code for performing the following steps:

S1. The receiving end device generates a status report, where the status report carries indication information for indicating one or more lost data packets.

S2. The receiving end device sends the status report to the sending end device.

Optionally, the storage medium is further arranged to store program code for performing the following steps:

S3. The sending end device receives a status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets.

S4. The sending end device sends the lost data packet to the receiving end device according to the indication information.

Optionally, in this embodiment, the foregoing storage medium may include, but not limited to, a USB flash drive, a Read-Only Memory (ROM), a Random Access Memory (RAM), a mobile hard disk, and a magnetic memory. A variety of media that can store program code, such as a disc or a disc.

Optionally, in this embodiment, the processor performs the method steps in the foregoing embodiments according to the stored program code in the storage medium.

For example, the specific examples in this embodiment may refer to the examples described in the foregoing embodiments and the optional embodiments, and details are not described herein again.

It will be apparent to those skilled in the art that the various modules or steps of the present invention described above can be implemented by a general-purpose computing device that can be centralized on a single computing device or distributed across a network of multiple computing devices. Alternatively, they can be executed by computing devices The program code of the lines is implemented so that they can be stored in the storage device by the computing device, and in some cases, the steps shown or described can be performed in a different order than here, or they can be Each of the integrated circuit modules is fabricated separately, or a plurality of modules or steps thereof are fabricated into a single integrated circuit module. Thus, the invention is not limited to any specific combination of hardware and software.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Industrial applicability

As described above, the method and system for generating a status report and the method and device for receiving a status report provided by the embodiment have the following beneficial effects: after the transmitting device sends data to the receiving device, the receiving device detects the data. In the case that there is a transmission error in the packet, the receiving device generates a status report carrying indication information indicating the lost data packet, that is, the indication information carries only the information indicating the lost data packet as much as possible, and the transmission is correct. The data packet occupies a small transmission space, and the status report is transmitted to the transmitting device, and the transmitting device can resend the data packet with the wrong transmission. The problem that the status report sent by the receiving end device takes up a large space when the data has a transmission error is solved in the related art, and the transmission space of the status report is greatly reduced.

Claims (19)

1. A method for generating a status report, comprising:

   The receiving device generates a status report, where the status report carries indication information for indicating one or more lost data packets;

   The receiving end device sends the status report to the sending end device.
2. The method of claim 1, wherein the receiving device generates a status report, comprising:

   Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

   The status report is generated according to the bitmap segmentation.
3. The method according to claim 2, wherein the bitmap segment to which the bitmap bitmap information of the data packet belongs is determined according to the following information:

   The starting position information of each segment, the length information of each segment.
4. The method of claim 3, comprising:

   The starting location information is used to indicate the first lost packet sequence number SN for each segment.
5. The method of claim 3, comprising:

   The length information is used to indicate a bit length of a segmented bitmap field, wherein a bit length of the bitmap field is equal to a length of a first lost packet of the segment to a last lost packet of the segment.
6. The method of claim 1, wherein the status report carries indication information for indicating one or more lost data packets, including:

   In the case that the receiving device does not segment the lost data packet, the status report carries the sequence number of each lost data packet.
7. A method for receiving a status report, comprising:

   The sending end device receives the status report sent by the receiving end device, where the status report carries indication information for indicating one or more lost data packets;

   The sending end device sends the lost data packet to the receiving end device according to the indication information.
8. The method according to claim 7, wherein the receiving end device generates the status report by: before the transmitting end device receives the status report sent by the receiving end device:

   Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

   The status report is generated according to the bitmap segmentation.
9. The method according to claim 8, wherein the receiving end device determines a bitmap segment to which the bitmap bitmap information of the data packet belongs according to the following information:

   Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.
10. A status report generating system includes: a receiving end device, a transmitting end device, wherein the receiving end device includes a first processor and a first communication module, and the transmitting end device includes a second processor and a second communication module ;

    The first processor generates a status report, where the status report carries indication information for indicating one or more lost data packets;

    The first communication module sends the status report to the second communication module;

    The second processor sends the lost data packet to the first communication module by using the second communication module according to the indication information.
11. The system of claim 10 wherein said first processor generates a status report comprising:

    Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

    The status report is generated according to the bitmap segmentation.
12. The system of claim 10, wherein the first processor determines a bitmap segment to which the bitmap bitmap information of the data packet belongs according to the following information:

    Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.
13. A receiving end device, comprising: a first processor and a first communication module;

    The first processor generates a status report, where the status report carries indication information for indicating one or more lost data packets;

    The first communication module sends the status report to the sender device.
14. The receiving end device according to claim 13, wherein the first processor generates a status report, including:

    Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

    The status report is generated according to the bitmap segmentation.
15. The receiving end device according to claim 13, wherein the first processor determines a bitmap segment to which the bitmap bitmap information of the data packet belongs according to the following information:

    Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.
16. The receiving end device according to claim 13, wherein the status report carries indication information for indicating one or more lost data packets, including:

    In the case that the receiving device does not segment the lost data packet, the status report carries the sequence number of each lost data packet.
17. A transmitting device includes: a second processor and a second communication module;

    The second communication module receives a status report sent by the receiving device, where the status report carries indication information for indicating one or more lost data packets;

    The second processor sends the lost data packet to the receiving end device according to the indication information.
18. The transmitting end device according to claim 17, wherein the receiving end device generates the status report by: before the second communication module receives the status report sent by the receiving end device:

    Determining a bitmap segment to which the bitmap file bitmap information of the data packet belongs;

    The status report is generated according to the bitmap segmentation.
19. The transmitting end device according to claim 18, wherein the receiving end device determines a bitmap segment to which the bitmap bitmap information of the data packet belongs according to the following information:

    Start position information of each segment, length information of each segment, wherein the start position information is used to indicate a first lost packet sequence number SN of each segment, and the length information is used to indicate a segment The bit length of the bitmap field of the segment, wherein the bit length of the bitmap field is equal to the length of the first lost packet of the segment to the last lost packet of the segment.

Images