Disclosure of Invention
The present invention is directed to a method for reporting an uplink status report, a method and an apparatus for transmitting radio link control data, so as to at least solve the above problems.
According to an aspect of the present invention, a method for reporting an uplink status report is provided, which includes the following steps: receiving Radio Link Control (RLC) data through an evolved high speed downlink packet access media access control (MAC-ehs) entity, wherein the RLC data carries an initial sequence number of an expected sequence number range of the RLC data which are expected to be continuously sent by the MAC-ehs entity; and determining whether to send an uplink state report and a state report of the RLC data needing to be reported according to the current sequence number of the received RLC data, the initial sequence number in the expected sequence number range and the received polling information POLL or polling protocol data unit POLL PDU.
Preferably, the method further comprises the following steps: receiving RLC data with a current sequence number corresponding to an end sequence number in the expected sequence number range, wherein the RLC data corresponding to the end sequence number carries a POLL; or receiving a POLL PDU, where the POLL PDU carries the starting sequence number and a second ending sequence number, where the second ending sequence number is a sequence number of the last RLC data that has been sent in an expected sequence number range of RLC data that is expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
Preferably, after receiving RLC data carrying POLL or the POLL PDU, detecting whether RLC data between the starting sequence number and the ending sequence number or between the starting sequence number and the second ending sequence number is completely received; if the detection result is negative, reporting an uplink state report to the sending end of the RLC data to request retransmission of the RLC data which are not received, and/or if the detection result is positive, reporting the uplink state report to the sending end of the RLC data to inform the sending end of correct receiving of the RLC data.
Preferably, when the RLC data is an RLC PDU, the starting sequence number is indicated by a special length indication of the RLC PDU; or, when the RLC data is a POLL PDU, the starting sequence number is carried in the POLL PDU.
Preferably, the POLL PDU is a predetermined type of RLC status PDU for flexible RLC PDU size and/or fixed RLC PDU size configuration.
According to an aspect of the present invention, there is provided a radio link control data transmission method, including the steps of: determining an expected sequence number range in which continuous transmission of radio link control, RLC, data is expected in the MAC-ehs entity; and sending RLC data through the MAC-ehs entity, wherein the RLC data carries a starting sequence number in the expected sequence number range.
Preferably, the transmitting the RLC data includes: sending RLC data corresponding to an ending sequence number in the expected sequence number range, wherein the RLC data corresponding to the ending sequence number carries alternate detection information POLL; alternatively, the method further comprises: and sending a POLL PDU (protocol data unit), wherein the POLL PDU carries the starting sequence number and a second ending sequence number, and the second ending sequence number is the sequence number of the last RLC data which is sent in the expected sequence number range of the RLC data which are expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
Preferably, when sending the RLC data corresponding to the starting sequence number, starting a first timer; before the first timer expires, if the RLC data corresponding to the ending sequence number is sent, ending the first timer; otherwise, under the condition that the first timer is overtime, the POLL PDU is sent.
Preferably, when the RLC data is an RLC PDU, the starting sequence number is indicated by a special length indication of the RLC PDU; or, when the RLC data is a POLL PDU, the starting sequence number is carried in the POLL PDU.
Preferably, the POLL PDU is a predetermined type of RLC status PDU for flexible RLC PDU size and/or fixed RLC PDU size configuration.
Preferably, the method further comprises the following steps: and receiving an uplink state report, wherein the uplink state report is determined and reported by a receiving end according to the current sequence number of the received RLC data, the initial sequence number in the expected sequence number range, and alternate detection information POLL or alternate detection protocol data unit POLL PDU.
Preferably, when the uplink status report indicates that the receiving end has RLC data that is not received, the RLC data or the POLL PDU corresponding to the end sequence number is retransmitted until the uplink status report indicates that the receiving end receives all RLC data from the start sequence number to the end sequence number or from the start sequence number to the second end sequence number.
Preferably, after sending the RLC data or the POLL PDU corresponding to the end sequence number, setting a second timer, if the received uplink status report indicates that the receiving end has RLC data that is not received before the second timer expires, when the second timer expires, resending the RLC data or the POLL PDU corresponding to the end sequence number, and resetting the second timer until the uplink status report indicates that the receiving end receives all RLC data from the starting sequence number to the end sequence number or from the starting sequence number to the second end sequence number, and then stopping the second timer.
According to another aspect of the present invention, an uplink status report reporting apparatus is provided, including: a receiving module, configured to receive RLC data via an MAC-ehs entity, where the RLC data carries an initial sequence number of an expected sequence number range of RLC data that the MAC-ehs entity expects to continuously send; and the reporting module is used for determining whether to send an uplink state report and a state report of the RLC data needing to be reported according to the current sequence number of the received RLC data, the initial sequence number in the expected sequence number range and the POLL or POLL PDU.
Preferably, the receiving module is configured to receive RLC data corresponding to an end sequence number in the expected sequence number range, where the RLC data corresponding to the end sequence number carries POLL; or, the receiving module is further configured to receive a POLL PDU for polling protocol data unit, where the POLL PDU carries the starting sequence number and a second ending sequence number, and the second ending sequence number is a sequence number of the last RLC data that has been sent in a sequence number range of RLC data that is expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
According to still another aspect of the present invention, there is also provided a radio link control data transmission apparatus including: a determining module for determining an expected sequence number range in which continuous transmission of radio link control, RLC, data is expected in the MAC-ehs entity; and a sending module, configured to send RLC data through the MAC-ehs entity, where the RLC data carries an initial sequence number in the expected sequence number range.
Preferably, the sending module is further configured to send RLC data corresponding to an end sequence number in the expected sequence number range, where the RLC data corresponding to the end sequence number carries POLL; or, the sending module is further configured to send a POLL PDU, where the POLL PDU carries the starting sequence number and a second ending sequence number, where the second ending sequence number is a sequence number of the last RLC data that has been sent in an expected sequence number range of RLC data that is expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
Preferably, the method further comprises the following steps: and the receiving module is used for receiving an uplink state report, wherein the uplink state report is determined and reported by a receiving end according to the current sequence number of the received RLC data, the initial sequence number in the expected sequence number range, and alternate detection information POLL or alternate detection protocol data unit POLL PDU.
Preferably, when the uplink status report indicates that the receiving end has RLC data that is not received, the sending module is further configured to resend the RLC data or the POLL PDU corresponding to the end sequence number until the uplink status report indicates that the receiving end receives all RLC data between the starting sequence number and the end sequence number or between the starting sequence number and the second end sequence number.
The invention solves the problem that the receiving party can not judge whether the RLC data is lost normally under the Inter-NodeB scene in the related technology, thereby enabling the receiving party to judge whether the RLC data is lost correctly.
Detailed Description
The invention will be described in detail hereinafter with reference to the accompanying drawings in conjunction with embodiments. It should be noted that the embodiments and features of the embodiments in the present application may be combined with each other without conflict.
In this embodiment, a method for reporting an uplink status report is provided, and fig. 1 is a flowchart of a method for reporting an uplink status report according to an embodiment of the present invention, as shown in fig. 1, the method includes the following steps:
step S102, receiving RLC data (e.g., RLC PDU) via a MAC-ehs entity, where the RLC data carries a starting sequence number of an expected sequence number range (abbreviated as sequence number range) of RLC data that the MAC-ehs entity expects to continuously transmit; for example, in order to have a small modification to the existing RLC data, the starting sequence number may be indicated by a special length indication of the RLC PDU, or, in case the RLC data is a POLL PDU, the starting sequence number may be carried in the POLL PDU. Preferably, the poll PDU may be a predetermined type (e.g., new type) of RLC status PDU for flexible RLC PDU size (RLC PDU size) and/or fixed RLC PDU size (RLC PDU size) configuration.
Step S104, determining whether to send an uplink status report and which status reports of RLC data need to be reported according to the current sequence number of the received RLC data, the initial sequence number in the sequence number range, and POLL (or POLL PDU).
Through the steps, a receiving end (for example, a UE) can know the sequence number range of RLC data sent by an MAC-ehs entity (which may also be a base station), so that the receiving end can determine whether the RLC data is normally received according to the sequence number and the initial sequence number of the received RLC data, thereby solving the problem that the receiving end cannot determine whether the RLC data is normally lost in an Inter-NodeB scenario. It should be noted that, in the receiving end, if data from a plurality of different base stations is received, there is one MAC-ehs entity corresponding to each base station, so that, hereinafter, the relevant processing for the base station involved in the transmitting end and/or the receiving end may be regarded as processing for the MAC-ehs entity corresponding to the base station.
Fig. 2 is a flowchart of a radio link control data transmission method according to an embodiment of the present invention, as shown in fig. 2, the flowchart includes the steps of:
in step S202, a sequence number range in which radio link control RLC data is expected to be continuously transmitted in the base station is determined.
Step S204, RLC data are sent through the base station, wherein the RLC data carry a starting sequence number in the expected sequence number range.
The above steps S202 to S204 determine the sequence number range of the RLC data transmitted by each base station for the transmitting end (e.g., RNC) and carry the starting sequence number in the sequence number range in the RLC data, so that the receiving end receiving the RLC data can obtain the RLC data starting sequence number in the expected sequence number range transmitted by the base station.
Preferably, in implementation, in order to trigger the receiving end to report the uplink status report, and/or in order to ensure that the receiving end receives the relevant RLC data in the expected sequence number range, in the RLC data corresponding to the end sequence number in the expected sequence number range, the POLL may carry the alternate detection information POLL, and at this time, the POLL carries the end sequence number in the expected sequence number range; or sending a POLL PDU (protocol data unit), wherein the POLL PDU carries a starting sequence number and a second ending sequence number. It should be noted that the second ending sequence number at this time is the sequence number of the last RLC data that has been transmitted in the sequence number range of the RLC data that is expected to be continuously transmitted by the MAC-ehs entity from the starting sequence number, and therefore, the second ending sequence number may or may not be equal to the ending sequence number of the sequence number range in step S202. Correspondingly, when the preferred embodiment is adopted, the receiving end can receive the RLC data corresponding to the end sequence number, wherein the RLC data corresponding to the end sequence number carries the alternate detection information POLL; or, the receiving end may also receive a POLL PDU, where the POLL PDU carries a start sequence number and a second end sequence number.
Preferably, how to send the RLC data or POLL PDU carrying POLL corresponding to the ending sequence number may be determined by using a timer, for example, when the RLC data corresponding to the starting sequence number is sent, the first timer is started; before the first timer is up, if RLC data corresponding to the ending sequence number are sent, ending the first timer; otherwise, under the condition that the first timer is overtime, sending the POLL PDU.
For the receiving end, the method of triggering the uplink status report may adopt an existing method, in this embodiment, after receiving RLC data or POLL PDU carrying POLL, the receiving end may detect whether the RLC data between the starting sequence number and the ending sequence number or between the starting sequence number and the second ending sequence number is completely received, if the detection result is negative, report the uplink status report to the transmitting end of the RLC data, request retransmission of the RLC data that is not received, and if the RLC data is completely received, also report the uplink status report to the transmitting end, and notify the transmitting end that all data are normally received. For the sending end, an uplink status report may be received, where the uplink status report is reported by the receiving end according to the sequence number of the received RLC data, and the starting sequence number and the ending sequence number in the sequence number range. Preferably, the transmitting end may determine, according to the uplink status report, information related to the retransmission operation, for example, whether retransmission is required and which RLC data or RLC data needs to be retransmitted. A preferred embodiment will be described as an example.
In the preferred embodiment, when the uplink status report indicates that the receiving end has RLC data that is not received, the RLC data or POLL PDU corresponding to the end sequence number is retransmitted until the uplink status report indicates that the receiving end receives all RLC data from the start sequence number to the end sequence number or from the start sequence number to the second end sequence number.
More preferably, a second timer may be added in the preferred embodiment, for example: and after the RLC data or the POLL PDU corresponding to the ending sequence number is sent, setting a second timer, if the received uplink state report indicates that the receiving end has the RLC data which is not received before the second timer expires, resending the RLC data or the POLL PDU corresponding to the ending sequence number when the second timer expires, and resetting the second timer until the uplink state report indicates that the receiving end receives all the RLC data from the starting sequence number to the ending sequence number or from the starting sequence number to the second ending sequence number, and stopping the second timer.
Corresponding to the foregoing embodiment and the preferred embodiments thereof, the present embodiment further provides an uplink status report reporting apparatus, which has been described above and is not described herein again, and a description is provided below for a module related to the apparatus. Fig. 3 is a block diagram of a structure of an uplink status report reporting apparatus according to an embodiment of the present invention, and as shown in fig. 3, the structure includes a receiving module 32 and a reporting module 34, which will be described below.
A receiving module 32, configured to receive RLC data via a base station, where the RLC data carries a starting sequence number of an expected sequence number range of the RLC data continuously sent by the base station; a reporting module 34, connected to the receiving module 32, for determining (or determining) whether to send an uplink status report and status reports of which RLC data need to be reported according to the current sequence number of the received RLC data, the starting sequence number in the sequence number range, and the POLL or POLL PDU.
Preferably, the receiving module 32 is configured to receive RLC data corresponding to an end sequence number in an expected sequence number range, where the RLC data corresponding to the end sequence number carries POLL; or, the receiving module 32 is further configured to receive a POLL PDU, where the POLL PDU carries a starting sequence number and a second ending sequence number, where the second ending sequence number is a sequence number of the last RLC data that has been sent in a sequence number range of RLC data expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
Corresponding to the foregoing embodiment and the preferred embodiments thereof, the present embodiment further provides a radio link control data transmission apparatus, which has already been described above and is not described herein again, and the following describes modules related to the apparatus. Fig. 4 is a block diagram of a configuration of a radio link control data transmission apparatus according to an embodiment of the present invention, and as shown in fig. 4, the configuration includes a determination module 42 and a transmission module 44, and the configuration will be explained below.
A determining module 42 for determining a range of sequence numbers for which continuous transmission of radio link control, RLC, data is desired in the base station; a sending module 44, connected to the determining module 42, is configured to send RLC data through the base station, where the RLC data carries a starting sequence number in the sequence number range.
Preferably, the sending module 44 is further configured to send RLC data corresponding to an end sequence number in the expected sequence number range, where the RLC data corresponding to the end sequence number carries POLL; or, the sending module 44 is further configured to send a POLL PDU, where the POLL PDU carries a starting sequence number and a second ending sequence number, where the second ending sequence number is a sequence number of the last RLC data that has been sent in a sequence number range of RLC data expected to be continuously sent by the MAC-ehs entity from the starting sequence number.
Fig. 5 is a block diagram of a preferred structure of a radio link control data transmission apparatus according to an embodiment of the present invention, as shown in fig. 5, the structure further includes: a receiving module 52, configured to receive an uplink status report, where the uplink status report is determined to be reported by the receiving end according to a current sequence number of received RLC data, a starting sequence number in an expected sequence number range, and POLL (or POLL pdu).
Preferably, in the case that the uplink status report indicates that the receiving end has RLC data that is not received, the sending module 44 is further configured to resend the RLC data or POLL PDU corresponding to the end sequence number until the uplink status report indicates that the receiving end receives all RLC data from the starting sequence number to the end sequence number or from the starting sequence number to the second end sequence number.
The following preferred embodiment takes an acknowledged mode radio link control (AM RLC for short) entity in the RNC as a transmitting side and a UE as a receiving side as an example.
In the preferred embodiment, an RLC PDU sequence number setting and status report triggering method of an AM RLC entity is provided. In the method, when a sending end confirms the mode radio link control entity to send RLC data (for example, RLC PDUs), the sending end carries the starting sequence number (SNfirst for short) and the ending sequence number (SNlast for short) of the RLC data which the sending end plans to continuously send in the corresponding NodeB along with the path; carrying the POLL along with the path when the sending end sends the RLC PDU with the ending sequence number; the receiving end confirms the mode radio link control entity and decides whether to send the uplink state report and detects the state report of which RLC data (RLC PDUs) are reported according to the sequence number and the initial sequence number in the received RLC data and the POLL. The method comprises the following steps:
step S1, the sending end carries the starting sequence number when confirming that the mode radio link control entity sends the RLC data.
Preferably, the start sequence number and the end sequence number are the start sequence number and the end sequence number of the RLC data that the RLC entity needs to continuously transmit in a certain NodeB.
Preferably, in order to guarantee forward compatibility of the RLC PDU, the Length Indicator (Length Indicator) of the RLC data may be extended as shown in the following table, or the UE may be informed of the RLC PDU format change using other methods (e.g., other in-band and/or out-of-band negotiation methods may be included).
Watch 1
Preferably, the data amount of the RLC data that the sending-end acknowledged mode radio link control entity needs to continuously send in a certain NodeB may be related to the air interface capability of the service in the NodeB.
Step S2, when the sending end confirms that the mode radio link control entity sends RLC data with sequence number SNlast, it carries POLL along with the path or sends POLL PDU, which needs to carry the starting sequence number and the second ending sequence number.
Preferably, the sending end starts a timer SNLastlDelayTimer when the sending end confirms the RLC data of the mode radio link control entity sending SNfirst, the sending end confirms the RLC data (RLC PDU) with sequence number SNlast in the timer snlastdelaytimer by the mode radio link control entity, and carries Poll along with the path; simultaneously clearing the timer SNLastlDelayTimer; when the timer SNLastlDelayTimer times out (indicating that the sending end does not send RLC data with sequence number SNlast), the sending end acknowledged mode radio link control entity sends a single POLL PDU, and the POLL PDU needs to carry a starting sequence number (SNfirst) and a second ending sequence number.
Preferably, the POLL PDU may be a new type of RLC status PDU for flexible RLC PDU size (RLC PDU size) and/or fixed RLC PDU size (RLC PDU size) configuration.
Step S3, the receiving end determines whether to send an uplink status report and detects which RLC data (RLC PDUs) status reports are reported according to the Sequence Number (SN), the initial sequence number and the POLL in the received RLC data.
Preferably, the receiving end confirms that the mode radio link control entity receives RLC data with POLL and/or POLL PDU(s); the receiving end may transmit an RLC status report to the transmitting end.
Preferably, the receiving-end acknowledged mode radio link control entity receives a plurality of RLC data, and there may be one or even more sequence number intervals (referring to the starting sequence number and the ending sequence number of the first part) of the received data.
Preferably, the receiving end acknowledged mode radio link control entity processes RLC data for each sequence number interval: recording the maximum sequence number SNlarget in RLC data successfully received in the sequence number interval; checking whether the RLC data between the starting sequence number SNfirst and the maximum sequence number SNlarget are completely received, and if so, considering that the RLC data of the received sequence number are not discarded. The receiving end confirms the mode radio link control entity and sends RLC status report to the sending end, including discarding the sequence number tabulation of RLC data and sequence number tabulation of RLC data received successfully.
In step S4, the sending-end acknowledged mode radio link control entity retransmits POLL PDU of a certain sequence number interval, where the POLL PDU may be RLC data with POLL of sequence number SNlast or a single POLL PDU.
Preferably, if the transmission sequence number interval is not completely received within a period of time polirrendeddelaytimer after the sending end acknowledged mode radio link control entity sends the POLL PDU (refer to the starting sequence number and the ending sequence number in step S1), the POLL PDU is retransmitted according to the receiving status report of the RLC data. For example, the retransmitted POLL PDU may be sequence number SNlast RLC data carrying POLL or a single POLL PDU; and the sending end stops the timer if the successful receiving state report of the RLC data in the sending sequence number interval is received within a period of time PollResendDelayTimer after the sending end confirms the mode radio link control entity to send the POLL PDU.
Through this preferred embodiment, the following effect has been reached: the problem that normal or abnormal PDU loss cannot be judged according to a sequential sending principle when a wireless link control entity at a receiving end of a confirmation mode receives data PDUs and SN gaps exist after DF-DC-HSDPA or SF-DC-HSDPA technology is introduced is solved; the main functions of the wireless link control entity in the existing protocol confirmation mode, such as loss monitoring, are furthest used, and backward compatibility is ensured. Preferably, to avoid that the receiver acknowledged mode radio link control, AM, RLC entity responds too much RLC POLL, the preferred embodiment may be used with a Status Prohibit Timer (Timer _ Status _ Prohibit).
The preferred embodiments will be described below with reference to the accompanying drawings.
Fig. 6 is a flowchart of an AM RLC entity at a transmitting end transmitting AM RLC PDUs according to the preferred embodiment, where in the flowchart, multiple RLC data (RLC PDUs) at the transmitting end are transmitted to a receiving end through two nodebs, each RLC data carries a starting sequence number, and the RLC data may carry POLL, or the transmitting end transmits POLL PDU, as shown in fig. 6, the flowchart includes the following steps:
step S610, the sending end may pre-allocate a desired sequence number range to each NodeB according to factors such as air interface sending capability of each NodeB, and record the desired sequence number range pre-allocated to each NodeB as [ SNfirst, SNlast ], where SNfirst is an initial sequence number, SNlast is an end sequence number, and the RLC PDU format may refer to fig. 8, and of course, the RLC PDU in fig. 8 is a preferred format; the POLL PDU may refer to fig. 9, wherein a SUFI (stb-field) type POLL _ EXT is added, although the POLL PDU in fig. 9 is a preferred format and is not limited thereto.
Step S620, the sending end sends RLC data, which carries SNfirst along with the path;
step S630, the sending end sends the RLC data of SNfirst and sets a timer SNLastlDelayTimer at the same time;
step S640, the sending end sends RLC data with sequence number SNlast in the timer SNLastlDelayTimer, and then carries POLL along with the path, and simultaneously clears the timer SNLastlDelayTimer;
step S650, the sending end sends a single POLL PDU when the timer SNLastlDelayTimer is over, and simultaneously carries SNfirst and the sequence number of the RLC data which is sent last in the expected sequence number range;
step S660, after step S640 or step S650, a timer pollresendedelaytimer is set;
step S670, if the sending end collects the successful receiving status report of all RLC data in the sending sequence number interval in the timer PollResendDelayTimer, the timer is cleared;
in step 8680, if the sending end does not receive the successful receiving status report of all RLC data in the sending sequence number interval in the timer pollresentdelaytimer, the RLC PDU or POLL PDU carrying POLL in step S640 or step S650 is retransmitted.
Fig. 7 is a flowchart of the receiving-end AM RLC entity triggering according to the RLC PDU status report according to the preferred embodiment, as shown in fig. 7, the flowchart includes:
step S710, when receiving end AM RLC entity receives RLC data with POLL or POLL PDU, the receiving end may send RLC status report to the sending end;
step 8720, the receiving end AM RLC entity receives RLC data, and there may be one or more expected sequence number intervals (referring to the starting sequence number (SNfirst) and the ending sequence number (SNlast));
step S730, the receiving end AM RLC entity processes the RLC data of each expected sequence number interval; referring to steps S730-10/20 for the processing procedure of the RLC data of each sequence number interval;
step S730-10, recording the maximum sequence number SNlarget in the successfully received RLC data in the sequence number interval;
step S730-20, checking whether RLC data between the initial sequence number SNfirst and the maximum sequence number SNlarget in the sequence number interval are completely received, if so, determining that the RLC data of the received sequence number are not discarded, and if not, determining that the RLC data are discarded;
in step S740, the receiving end AM RLC entity returns a status report, which includes a sequence number list of discarded RLC data and a sequence number list of successfully received RLC data.
By the embodiment, the problem that the receiving party cannot judge whether the RLC data are normally lost in an Inter-NodeB scene is solved.
It will be apparent to those skilled in the art that the modules or steps of the present invention described above may be implemented by a general purpose computing device, they may be centralized on a single computing device or distributed across a network of multiple computing devices, and alternatively, they may be implemented by program code executable by a computing device, such that they may be stored in a storage device and executed by a computing device, or they may be separately fabricated into various integrated circuit modules, or multiple modules or steps thereof may be fabricated into a single integrated circuit module. Thus, the present invention is not limited to any specific combination of hardware and software.
The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention, and various modifications and changes may be made by those skilled in the art. Any modification, equivalent replacement, or improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.