WO2012155619A1 - 一种rlcam状态报告处理的方法和系统 - Google Patents

一种rlcam状态报告处理的方法和系统 Download PDF

Info

Publication number
WO2012155619A1
WO2012155619A1 PCT/CN2012/072266 CN2012072266W WO2012155619A1 WO 2012155619 A1 WO2012155619 A1 WO 2012155619A1 CN 2012072266 W CN2012072266 W CN 2012072266W WO 2012155619 A1 WO2012155619 A1 WO 2012155619A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
status report
pdu
status
received
Prior art date
Application number
PCT/CN2012/072266
Other languages
English (en)
French (fr)
Inventor
王博
Original Assignee
中兴通讯股份有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 中兴通讯股份有限公司 filed Critical 中兴通讯股份有限公司
Publication of WO2012155619A1 publication Critical patent/WO2012155619A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management

Definitions

  • the present invention relates to a technology for processing status reports in a wireless communication technology or an LTE (Long Term Evolution) network, and particularly relates to an eNB (E-UTRAN Node B, Node B in a wireless network) and a UE (User Equipment, user equipment).
  • eNB E-UTRAN Node B, Node B in a wireless network
  • UE User Equipment, user equipment
  • the LTE air interface layer protocol includes a PDCP (Packet Data Convergence Protocol), an RLC (Radio Link Control), and a MAC (Media Access Control) protocol, where the RLC protocol is based on the current air interface.
  • the scheduling result of the logical channel is connected or segmented to the SDU (Service Data Unit) delivered by the PDCP, and is configured by the RLC PDU (Protocol Data Unit) according to the current scheduling bandwidth.
  • the RLC provides three configurable modes: Transparent Mode (TM), Unacknowledged Mode (UM), and Acknowledge Mode (AM).
  • the RLC AM receiver When the RLC is configured in the AM mode, the RLC AM receiver needs to send an RLC AM status report to the RLC AM sender according to its own reception status of the RLC PDU, which is used to confirm to the RLC AM sender that the current RLC AM receiver has correctly received the RLC.
  • the PDU, and the RLC AM receiver does not correctly receive the RLC PDU that needs to be retransmitted by the RLC AM sender.
  • the procedure is described in the following manner.
  • the RLC AM sender and the RLC AM receiver both set an RLC. Slide the window, fill in an RLC SN (Serial Number), and place it in the corresponding position in the send sliding window.
  • the sent RLC PDU cannot be deleted from the send sliding window immediately. Receive the corresponding status report confirmation.
  • the RLC AM receiver places it according to the SN of the received RLC PDU to the corresponding location of the receiving sliding window to sort the received RLC PDUs.
  • the RLC AM receiving end can easily know the missing message SN in the current receiving sliding window according to the order of the receiving sliding window.
  • the RLC AM receiver continuously constructs the RLC AM status report in accordance with the manner specified in the protocol to notify the RLC AM sender of the current reception status and the SN of the RLC PDU that needs to be retransmitted.
  • the RLC AM sender resolves the status report, and then The packet received by the RLC AM receiver is resent once.
  • the retransmitted RLC PDU packet needs to be fragmented.
  • the RLC AM receiver receives the fragmented RLC PDU and also caches it to determine if there is fragment loss. If the RLC AM receiver finds that a retransmitted fragment is lost, it also needs to describe in the RLC AM status report the SN of the specific missing fragment RLC PDU and the start and stop offset bytes of the missing fragment in the original RLC PDU. Location, so that the RLC AM sender retransmits the fragment.
  • the status report also has a very important function of notifying the RLC AM sender that the current RLC AM receiver has correctly received the last one.
  • the SN of the RLC PDU the sender can release the RLC PDU before the RLC PDU in the send sliding window, so that the free sliding window space released by the RLC AM sender can be used for sending the new RLC PDU.
  • a maximum retransmission number maxRetxThreshold is configured to control the maximum number of times an RLC PDU is retransmitted.
  • the RLC AM receiver requests the RLC AM sender to retransmit a fragment of a PDU or PDU through the status report, if the RLC AM sender retransmits the PDU after maxRetxThreshold times and the RLC AM receiver still fails to receive correctly, then If the logical channel corresponding to the current RLC AM is abnormal, the abnormality is fed back to the RRC (Radio Resource Control), and the RRC determines whether to release the bearer or release the UE.
  • RRC Radio Resource Control
  • an abnormal logical channel occurs Not corresponding to the UE SRB (Signalling Radio Bearer, signaling radio bearer) or a default DRB (Data Radio Bearer, data radio bearer), corresponding to the UE to release the RRC only exception 7
  • SRB Signaling Radio Bearer
  • DRB Data Radio Bearer, data radio bearer
  • the RLC protocol stipulates that when the RLC AM sender sends a sliding window and cannot move forward, for example, the PDCP of the transmitting end does not have new data, or the RLC sending sliding window is full, the RLC AM transmitting end must actively forward to the RLC.
  • the AM receiving end requests to reply to the status report as soon as possible, so that the RLC AM transmitting end releases the PDU that the RLC AM receiving end has correctly received in the RLC sending sliding window, so that the sending sliding window can continue to move forward.
  • the RLC AM sender actively requests the receiver to reply to the status report, which is implemented by setting the Polling bit in the RLC header.
  • the RLC PDU that is set to the Polling bit is called a Polling PDU.
  • the RLC AM receiver receives the Polling PDU, which is considered to be the RLC AM sender in the active request status report. At this time, the RLC AM receiver constructs a status report transmission according to the current situation of receiving the sliding window. After sending a Polling PDU, the sender starts a timer. If the correct status report is not obtained before the timer expires, a Polling PDU is retransmitted. If the same Polling PDU is retransmitted, the maximum number of retransmissions maxRetxThreshold is exceeded. Then, the logical channel abnormality needs to be reported to the upper layer, and the upper layer decision is triggered whether the logical channel is to be released or the UE is released.
  • the D/C and CPT fields in the RLC status report indicate the packet type. As shown in Figure 1, the packet format of the RLC status report is used to distinguish whether it is an RLC data message or an RLC status report.
  • the ACK_SN identifies the RLC PDU SN that the current RLC AM receiver does not receive completely but does not need to retransmit.
  • the NACK-SN is used to identify the RLC PDU SN that is not completely received by the RLC AM receiver and needs to be retransmitted. If the fragmentation of an RLC PDU is lost, the SOstart domain and the SOend domain need to be attached after the NACK-SN to identify The byte offset of the specific lost fragment is the starting and ending position.
  • a status report can only contain one ACK-SN field, but can contain multiple NACK-SN fields, indicating that there are multiple packets or packet fragments not received in the sorting segment of the RLC AM receiving end receiving the sliding window.
  • E1 is used to identify whether to continue following the current NACK SN field.
  • There is a NACK-SN field and E2 is used to identify the NACK--the SN field carries the SOstart field and the SOend field. If there are multiple NACK-SN domains, then all NACK-SNs need to be arranged in increasing order in the status report. It can be seen that the minimum status report requires 2 bytes, that is, only the ACK-SN field does not contain any NACK-SN domain status report.
  • the RLC AM sender After receiving the status report, the RLC AM sender needs to retransmit the RLC PDU corresponding to the NACK_SN. If the NACK-SN domain does not carry the SOstart domain and the SOend domain, retransmit the entire RLC PDU. Otherwise, you only need to retransmit the corresponding fragment. Since the ACK-SN field indicates the RLC PDU SN that the RLC AM receiver does not receive completely but does not need to retransmit, the RLC AM sender does not need to retransmit the RLC PDU according to the current protocol.
  • the RLC AM sender receives an RLC status report that only carries the ACK_SN field, that is, does not carry any NACK-SN later, it indicates that the RLC PDUs in the sequence segment before the ACK_SN are already pressed by the RLC AM receiver. The sequence is completely received, and the RLC AM sender can release the RLC PDUs in the sliding window unit before the ACK_SN in the sending sliding window. If the RLC status report received by the RLC AM receiver carries the NACK_SN field, the RLC AM sender needs to release the transmission sliding window to the smallest NACK-sliding window unit corresponding to the SN domain in addition to constructing the retransmission message. The previous unit, the smallest NACK-RL domain PDU before the SN domain, the RLC AM receiver has been correctly received in order.
  • the RLC AM status report constructed by the RLC AM receiver can be completely transmitted depends on the scheduling bandwidth of the current air interface. If the current air interface's scheduling bandwidth is smaller than the current RLC AM status report to be sent, the RLC needs to send the status report according to the scheduled bandwidth and then send it.
  • the specific cutting rule is that the status report deletes the NACK-SN domain one by one, and if the NACK-SN domain carries the SOstart domain and the SOend domain, it needs to be deleted together, and after deleting the scheduled bandwidth, it will be deleted last.
  • a NACK-SN field is filled in as ACK_SN, and the cropped status report is sent as a whole.
  • FIG. 2 and Figure 3 are an example.
  • the RLC needs to send a status report
  • the ACK_SN is 550, indicating that the SN of the first incompletely received RLC PDU after the RLC AM receiver receives the sliding window sorting segment is 550.
  • a shard As can be seen from Figure 2, such a status report requires 8 bytes. If the air interface scheduling bandwidth at this time is 7 bytes, then such a status report cannot be completely transmitted.
  • the status report is reduced to the form of Figure 3, and can be seen to become There are only two bytes, where one NACK_SN field is deleted and ACK_SN is changed to 530. There is a problem at this time.
  • the RLC AM receiver originally wants the RLC AM sender to retransmit the PDU to a fragment of 530, but because the air interface scheduling bandwidth is insufficient, the status report is cut, and the status report after clipping does not carry the NACK— The SN field, and the ACK_SN is changed from 550 to 530.
  • the RLC AM sender After receiving the status report, the RLC AM sender follows the current protocol: 1) It is not necessary to retransmit any message for the RLC AM receiver; 2) The send sliding window of the RLC AM sender can be released to the previous unit of 530.
  • the problem here is that if the scheduling bandwidth of the air interface is not enough for 8 bytes in a period of time, the RLC AM receiver can only send such a cropped status report all the time, and the RLC AM sender can never give the RLC.
  • the AM receiving end retransmits the message 530, which causes the RLC AM receiving end to fail to receive the 530 and cannot forward the receiving sliding window, which in turn causes the sending sliding window of the RLC AM transmitting end to stagnate, thus entering a deadlock state.
  • the RLC AM transmitting end actively sends a Polling PDU requesting the RLC AM receiving end according to the protocol.
  • the status report is replied, and if the air interface scheduling of the RLC AM receiver is still less than 8 bytes, the reduced status report cannot cause the RLC AM sender to forward the transmission sliding window, and finally the transmitting end retransmits the Polling PDU.
  • the Polling PDU is retransmitted beyond the set RLC maximum number of retransmissions, causing the bearer or the UE to be released.
  • An object of the present invention is to provide a method and system for RLC AM status report processing, which is used to solve the problem that a RLC exceeds a maximum number of retransmissions to cause a bearer or a UE to be released.
  • a method for RLC AM status report processing comprising the steps of:
  • the RLC AM sender receives the RLC AM status report sent by the RLC AM receiver; the RLC AM sender determines whether the RLC AM status report is a crop status report or a normal status report;
  • the retransmission process is performed according to the corresponding identifier of the RLC AM status report;
  • the RLC AM status report is a normal status report, it is processed according to the corresponding identifier of the RLC AM status report.
  • the method further includes:
  • the RLC AM sender sends an RLC PDU to the RLC AM receiver.
  • the RLC AM receiver generates an RLC AM status 4 report based on the received RLC PDU.
  • the RLC AM sender determines whether the RLC AM status report is a crop status report or a normal status report is: Determining whether the RLC AM status report includes only the identifier of the RLC PDU that is not completely received by the RLC AM receiving end but does not need to be retransmitted; determining whether the number of RLC AM status reports received by the RLC AM transmitting end is greater than or equal to the system-set weight Number of transmissions; determining whether the RLC AM sender has an RLC PDU that has been sent but not acknowledged by the receiving end;
  • the RLC AM status report includes only the identifier of the RLC PDU that the RLC AM receiver does not receive completely but does not need to retransmit, and the number of RLC AM status reports received by the RLC AM sender is greater than or equal to the number of retransmissions set by the system and The RLC AM sender has an RLC PDU that has been sent but not acknowledged by the receiver.
  • the RLC AM status report is a crop status report. Otherwise, the RLC AM status report is a normal status report.
  • the retransmission process is performed according to the corresponding identifier of the RLC AM status report to: retransmit the RLC PDU in the RLC AM status report that is not completely received but does not need to be retransmitted.
  • the processing is performed according to the corresponding identifier of the RLC AM status report:
  • the RLC is identified as not fully received but does not need to be retransmitted.
  • the serial number of the PDU, in the RLC AM sender, the RLC PDU whose sequence number is smaller than the sequence number of the RLC PDU that is not completely received but does not need to be retransmitted is deleted;
  • the RLC PDU identified in the RLC AM Status Report as not fully received and requiring retransmission is retransmitted.
  • a system for RLC AM status report processing including:
  • RLC AM receiver used to send RLC AM status report
  • the RLC AM transmitting end is configured to receive the RLC AM status report, and determine that the RLC AM status report is a crop status report or a normal status report.
  • the RLC AM status report is a crop status report, retransmitting according to the corresponding identifier of the RLC AM status report.
  • processing when the RLC AM status report is a normal status report, processing is performed according to the corresponding identifier of the RLC AM status report.
  • the RLC AM sender includes:
  • An information receiving unit configured to receive an RLC AM status report
  • a status report determining unit configured to determine that the RLC AM status report is a crop status report or a normal status report
  • the status report processing unit is configured to: when the RLC AM status report is a crop status report, perform retransmission processing according to the corresponding identifier of the RLC AM status report, and when the RLC AM status report is a normal status report, according to the corresponding status of the RLC AM status report The logo is processed.
  • the status report determining unit includes:
  • An identifier identifying unit configured to determine whether the RLC AM status report includes only an identifier of an RLC PDU that is not completely received by the RLC AM receiving end but does not need to be retransmitted;
  • the retransmission number determining unit is configured to determine whether the number of RLC AM status reports received by the RLC AM transmitting end is greater than or equal to the number of retransmissions set by the system;
  • a storage identification unit configured to determine whether the RLC AM sender has an RLC PDU that has been sent but is not acknowledged by the receiving end;
  • the status report determining unit is specifically configured to: when the RLC AM status report includes only an identifier of an RLC PDU that is not completely received by the RLC AM receiving end but does not need to be retransmitted, and an RLC AM received by the RLC AM sending end.
  • the number of status reports is greater than or equal to the number of retransmissions set by the system and the RLC AM sender has an RLC PDU that has been sent but not acknowledged by the receiving end.
  • the RLC AM status report is determined to be a crop status report. Otherwise, the RLC AM status is determined.
  • the report is a normal status report.
  • the status report processing unit comprises:
  • a cropping status report processing unit configured to retransmit the RLC PDU in the RLC AM status report that is not completely received but does not need to be retransmitted;
  • a normal status report processing unit configured to obtain, according to the RLC AM status report, a sequence number of the RLC PDU that is not completely received but does not need to be retransmitted, and then in the RLC AM sending end
  • the sequence number is smaller than the RLC PDU identified as the sequence number of the RLC PDU that is not completely received but does not need to be retransmitted, and the RLC PDU identified in the RLC AM Status Report as not fully received and requiring retransmission is retransmitted.
  • the RLC AM sender further includes:
  • the information sending unit is configured to send a radio link control data unit (RLC PDU) to the RLC AM receiving end.
  • RLC PDU radio link control data unit
  • the present invention solves the problem that the RLC exceeds the maximum number of retransmissions to cause the bearer or the UE to be released by discriminating and processing the PLC AM status report.
  • FIG. 1 is a schematic diagram of a message format of an RLC AM status report provided by the prior art
  • FIG. 2 is a schematic diagram of a status report before cutting according to the prior art
  • FIG. 3 is a schematic diagram of a state report after cropping provided by the prior art.
  • FIG. 4 is a schematic flowchart of a method for processing RLC AM status report provided by the present invention
  • FIG. 5 is a system block diagram of RLC AM status report processing provided by the present invention. detailed description
  • FIG. 4 is a schematic flowchart showing the method of RLC AM status report processing provided by the present invention, as shown in FIG. 4:
  • Step S401 The RLC AM sender receives the RLC AM status report sent by the RLC AM receiver.
  • Step S402 The RLC AM sending end determines whether the RLC AM status report is a crop status report or a normal status report.
  • the judging process is as follows: determining whether the RLC AM status report includes only the identifier of the RLC PDU that the RLC AM receiving end does not receive completely but does not need to retransmit, and determines whether the number of RLC AM status reports received by the RLC AM transmitting end is greater than or equal to the system. The number of retransmissions is determined, and it is determined whether the RLC AM sender has an RLC PDU that has been sent but not acknowledged by the receiving end; it should be understood that the three judging processes are not strictly sequential.
  • the RLC AM status report includes only the identifier of the RLC PDU that the RLC AM receiver does not receive completely but does not need to retransmit, and the number of RLC AM status reports received by the RLC AM sender is greater than or equal to the number of retransmissions set by the system and
  • the RLC AM status report has a RLC PDU that has been sent but not acknowledged by the receiving end.
  • the RLC AM status report is a crop status report. Otherwise, the RLC AM status report is a normal status report.
  • Step S403 If the RLC AM status report is a cropping status report, perform retransmission processing according to the corresponding identifier of the RLC AM status report, and retransmit the RLC PDU in the RLC AM status report that is not completely received but does not need to be retransmitted.
  • Step S404 If the RLC AM status report is a normal status report, processing is performed according to the corresponding identifier of the RLC AM status report, and the sequence number of the RLC PDU identified as not being completely received but not requiring retransmission is obtained according to the RLC AM status report, in the RLC.
  • the RLC PDU whose sequence number is smaller than the sequence number of the RLC PDU that is not completely received but does not need to be retransmitted is deleted in the AM transmitting end, and the RLC PDU in the RLC AM status report that is not completely received and needs to be retransmitted is heavily weighted. pass.
  • FIG. 5 is a system block diagram of the RLC AM status report processing provided by the present invention.
  • the system includes an RLC AM receiver and an RLC AM sender, and the RLC AM receiver receives the RLC PDU sent by the RLC AM transmitter. Generate RLC AM status report and report to RLC The AM sender sends it.
  • the RLC AM transmitting end includes an information receiving unit, a status report determining unit, a status report processing unit, and an information sending unit.
  • the information receiving unit receives the RLC AM status report sent by the RLC AM receiving end, and the status report determining unit determines that the RLC AM status report is the cropping status.
  • the report is still a normal status report and then processed by the status report processing unit.
  • the status report processing unit performs retransmission processing according to the corresponding identifier of the RLC AM status report, when the RLC AM status report is normal.
  • the information sending unit sends the RLC to the RLC AM receiving end in real time, wherein the status report determining unit includes an identifier identifying unit, a retransmission number determining unit, and a storage identifying unit, and the identifier identifying unit determines Whether the RLC AM status report includes only the identifier of the radio link control data unit RLC PDU that is not completely received by the RLC AM receiving end but does not need to be retransmitted, and the retransmission number determining unit determines the RLC AM status report received by the RLC AM transmitting end.
  • the status report determining unit includes an identifier identifying unit, a retransmission number determining unit, and a storage identifying unit
  • the identifier identifying unit determines Whether the RLC AM status report includes only the identifier of the radio link control data unit RLC PDU that is not completely received by the RLC AM receiving end but does not need to be retransmitted, and the retransmission number determining unit determines the RLC AM status report
  • the storage identification unit determines whether the RLC AM sender has an RLC PDU that has been sent but not acknowledged by the receiving end, and if the RLC AM status report only includes the RLC, the AM receiving end does not receive the complete The number of RLC PDUs that do not need to be retransmitted, the number of RLC AM status reports received by the RLC AM sender are greater than or equal to the number of retransmissions set by the system, and the RLC PDUs that have been sent but not acknowledged by the receiver are present at the RLC AM sender. Then, the RLC AM status report is the cropped status report, otherwise, the RLC AM status report is the normal status report.
  • the status report processing unit includes a crop status report processing unit and a normal status report processing unit, and the crop status report processing unit is configured to retransmit the RLC PDU that is not completely received but does not need to be retransmitted in the RLC AM status report, and the normal status report
  • the processing unit is configured to obtain, according to the RLC AM status report, a sequence number of the RLC PDU that is not completely received but does not need to be retransmitted, and then identify the sequence number less than the complete reception in the RLC AM sending end but does not need
  • the RLC PDU of the retransmitted RLC PDU sequence number is deleted, and the RLC PDU identified in the RLC AM Status Report as not fully received and requiring retransmission is retransmitted.
  • the invention optimizes the mechanism for processing status report in the RLC AM mode in the 3GPP 36.322 RLC protocol, mainly to judge the received status report, and distinguish whether a status report containing only the ACK-SN domain is a status report that is reduced. Therefore, the corresponding RLC PDUs are quickly retransmitted, so that the status report cannot be sent because the sender of the status report is unable to send a valid status report due to insufficient air interface scheduling, causing the RLC sliding window of the transmitting and receiving ends to stagnate and causing the RLC data sending end to be disconnected. Or the problem that the RLC reaches the maximum number of retransmissions.
  • the processing of the RLC status report involved in the present invention can be used as a supplement to the original mode of the 3GPP 36.322 RLC protocol processing status report, and the above-mentioned defects existing in the original protocol can be avoided.
  • the ACK_SN field should actually be the SN of the RLC PDU that is not completely received by the receiving end. Therefore, the RLC AM transmitting end retransmits the RLC PDU corresponding to the ACK-SN field, and then triggers.
  • RLC The AM receiving end receives the complete RLC PDU, so that the RLC AM receiving end receives the sliding window forward, which in turn causes the RLC AM transmitting end to send the sliding window forward, and finally ends the stagnation of the sliding window by the RLC AM transmitting end, avoiding the subsequent RLC.
  • the current is disconnected and the UE or bearer is released.
  • the present invention can be implemented as follows.
  • Step S601 determining whether the status report does not include any NACK_SN domain, if yes, proceeding to step S602, otherwise proceeding to step S606.
  • Step S606 setting RlcAckedVtaSN to OxFFFF and RlcAckedVtaCount to 0, and continuing the processing flow of the original status report.
  • the present invention improves the mechanism of the original RLC protocol processing status report, and judges at the RLC AM transmitting end through the current situation of the sending sliding window and the content of the received status report. Whether this is a status report that has been revamped, thereby extracting the information that needs to be retransmitted, and retransmitting the RLC AM receiving end, so that the receiving sliding window of the RLC AM receiving end moves forward, thereby causing the RLC AM transmitting end to send the sliding window.
  • the problem of the air interface efficiency and stability of the LTE network is improved by avoiding the problem that the RLC full flow of the RLC AM sender sliding window and the subsequent RLC exceeding the maximum number of retransmissions causes the bearer or the UE to be released.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Detection And Prevention Of Errors In Transmission (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本发明公开了一种RLCAM状态报告处理的方法和系统，其中，所述方法包括：配置为确认模式的无线链路控制RLCAM发送端接收RLCAM接收端发送的RLCAM状态报告；所述RLCAM发送端判断所述RLCAM状态报告是裁剪状态报告或者正常状态报告；当所述RLCAM状态报告是裁剪状态报告，根据所述RLCAM状态报告的相应标识进行重传处理；当所述RLCAM状态报告是正常状态报告，根据所述RLCAM状态报告的相应标识进行处理。本发明通过对PLCAM状态报告进行判别和处理解决了RLC超过最大重传次数引起承载或者UE被释放的问题。

Description

一种 RLC AM状态报告处理的方法和系统 技术领域
本发明涉及无线通信技术领或 LTE (Long Term Evolution,长期演进）网 络中处理状态报告的技术， 特别涉及 eNB (E-UTRAN Node B, 无线网络中 的节点 B)和 UE (User Equipment, 用户设备）处理 RLC AM (Radio Link Control Acknowledged Mode, 无线链路控制确认模式）状态报告处理的方法 和系统。 背景技术
LTE空口层协议包括 PDCP ( Packet Data Convergence Protocol, 分组数 据集中协议）、 RLC (Radio Link Control, 无线链路控制）和 MAC ( Media Access Control, 介质访问控制）协议， 其中 RLC协议根据当前空口对该逻 辑信道的调度结果对 PDCP下发的 SDU ( Service Data Unit,服务数据单元 ) 进行连接或者分段，按照当前的调度带宽组成 RLC PDU( Protocol Data Unit, 协议数据单元 )进行发送。 RLC提供了透明模式（ TM )、非确认模式（ UM ) 和确认模式（ AM )三种可配置模式。 当 RLC配置为 AM模式时， RLC AM 接收端需要根据自己对 RLC PDU的接收情况给 RLC AM发送端发送 RLC AM状态报告， 用来给 RLC AM发送端确认目前 RLC AM接收端已经正确 接收了 RLC PDU, 以及 RLC AM接收端没有正确接收需要 RLC AM发送 端重传的 RLC PDU, 该过程按照协议描述， 简单的可以总结为通过以下方 式进行： RLC AM发送端和 RLC AM接收端都设置一个 RLC滑窗， 按照 填写一个 RLC SN ( Serial Number, 序列号）， 然后放置在发送滑窗中的对 应位置中。发送后的 RLC PDU不能立即从发送滑窗中删除， 要一直緩存到 收到对应的状态报告确认为止。 RLC AM接收端根据接收到的 RLC PDU的 SN将其放置到接收滑窗的对应位置，以便对接收到的 RLC PDU进行排序。 RLC AM接收端根据接收滑窗的排序情况很容易获知当前接收滑窗内缺失 的报文 SN。 RLC AM接收端会不间断地按照协议中规定的方式构造 RLC AM状态报告来通知 RLC AM发送端目前的接收状况以及需要重传的 RLC PDU的 SN, RLC AM发送端通过解析该状态报告， 然后将 RLC AM接收 端未收到的报文重新发送一次。 如果 RLC AM发送端在发送重传报文的时 候，空口当前的调度带宽不能够一次容纳整个重传报文，那么该重传的 RLC PDU报文就需要被分片发送。 RLC AM接收端收到分片 RLC PDU也会緩 存并判断是否存在分片丟失。 如果 RLC AM接收端发现某个重传的分片丟 失的话， 也需要随后在 RLC AM状态报告里面描述具体缺失分片的 RLC PDU的 SN以及缺失的分片在原 RLC PDU中的起止偏移字节位置， 以便 RLC AM发送端重传该分片。 状态报告除了用于 RLC AM接收端通知 RLC AM发送端进行 RLC PDU的重传之外， 还有一个很重要的作用就是通知 RLC AM发送端当前 RLC AM接收端已经正确按序接收到的最后一个 RLC PDU的 SN,发送端可以将该 RLC PDU SN之前的 RLC PDU在发送滑窗中 释放掉了， 这样 RLC AM发送端释放出的空闲滑窗空间就可以供新的 RLC PDU发送使用。
RLC AM模式下会配置一个最大重传次数 maxRetxThreshold, 用于控 制一个 RLC PDU最多被重传的次数。 当 RLC AM接收端通过状态报告要 求 RLC AM发送端重传某个 PDU或者 PDU的一个分片， 如果 RLC AM发 送端将这个 PDU重传了 maxRetxThreshold次之后 RLC AM接收端还是未 能正确接收， 则认为当前 RLC AM对应的逻辑信道出现异常， 就要给 RRC ( Radio Resource Control, 无线资源控制协议 )反馈该异常， 由 RRC来决 策是否要释放该承载或者释放该 UE。一般情况下如果出现异常的逻辑信道 不是对应的 UE的 SRB ( Signalling Radio Bearer, 信令无线承载）或者默认 DRB ( Data Radio Bearer, 数据无线承载）， RRC只用释放 UE对应的异常 7|载即可， 否则就要释放 UE。
在 RLC协议中还规定， 当 RLC AM发送端发送滑窗不能再向前移动的 时候， 例如发送端 PDCP没有新数据下来， 或者 RLC发送滑窗满了， 这时 候 RLC AM发送端必须主动向 RLC AM接收端请求尽快回复状态报告， 以 便 RLC AM发送端释放 RLC发送滑窗中 RLC AM接收端已经正确按序接 收的 PDU, 促使发送滑窗能够继续前移。 RLC AM发送端主动请求接收端 回复状态报告， 是通过设置 RLC报头中的 Polling位来实现的， 其中， 被设 置 Polling位的 RLC PDU, 称为 Polling PDU。 RLC AM接收端收到 Polling PDU, 认为是 RLC AM发送端在主动请求状态报告， 这时候 RLC AM接收 端根据自己当前接收滑窗情况来构造状态报告发送。 发送端每发送一个 Polling PDU之后会启动一个定时器， 在定时器超时前如果没有得到正确的 状态报告， 就会重传一个 Polling PDU, 如果同一个 Polling PDU被重传超 过最大重传次数 maxRetxThreshold, 则也需要给上层上报该逻辑信道异常， 触发上层决策是否是要释放该逻辑信道或者释放该 UE。
RLC状态报告中 D/C和 CPT字段表明报文类型， 如图 1所示是 RLC 状态报告的报文格式，用于区分是 RLC数据报文还是 RLC状态报告。接下 来 ACK— SN标识当前 RLC AM接收端没有完整接收但不需要重传的 RLC PDU SN。 NACK— SN用于标识 RLC AM接收端没有完整接收且需要重传的 RLC PDU SN, 如果是一个 RLC PDU的分片存在丟失的话， 在 NACK— SN 之后还需要附上 SOstart域和 SOend域来标识具体丟失分片的字节偏移起止 位置。 一个状态报告中只能包含一个 ACK— SN 域， 但是可以包含多个 NACK— SN域， 表明在 RLC AM接收端接收滑窗的排序段内有多个报文或 者报文分片未收齐。 E1用来标识在当前 NACK SN域后面是否还继续跟随 有 NACK— SN域， E2用来标识该 NACK— SN域有没有携带 SOstart字段和 SOend字段。 如果有多个 NACK— SN域的话， 那么所有的 NACK— SN在状 态报告里面需要按照增序排列。 可以看到最小的状态报告需要 2个字节， 也就是只包含 ACK— SN域不包含任何 NACK— SN域的状态报告。
RLC AM发送端接收到一个状态报告后， 对于其中的 NACK— SN对应 的 RLC PDU需要重传。如果 NACK— SN域没有携带 SOstart域和 SOend域， 则重传整个 RLC PDU, 否则只需重传对应的分片即可。 由于 ACK— SN域指 明的是 RLC AM接收端没有完整接收但不需要重传的 RLC PDU SN, 所以 按照目前协议， RLC AM发送端无需重传该 RLC PDU。 如果 RLC AM发送 端接收到一个 RLC状态报告只携带 ACK— SN域，也就是说后面没有携带任 何 NACK— SN,则说明 RLC AM接收端在 ACK— SN之前的排序段内的 RLC PDU都已经按序完整接收了， RLC AM发送端可以把发送滑窗内 ACK— SN 之前的滑窗单元内的 RLC PDU都释放掉。 如果 RLC AM接收端接收到的 RLC状态报告携带了 NACK— SN域， 则 RLC AM发送端除了需要构造重传 报文外， 需要把发送滑窗释放到最小的 NACK— SN域对应的滑窗单元的前 一个单元 , 认为最小的 NACK— SN域之前的 RLC PDU, RLC AM接收端都 已经按序正确接收了。
RLC AM接收端构造的 RLC AM状态报告是否能够完整发送， 也需要 根据当前空口的调度带宽来决定。 如果当前空口的调度带宽小于当前要发 送的 RLC AM状态报告，这时候 RLC需要将该状态报告按照调度带宽进行 裁剪之后发送。 具体的裁剪规则是， 状态报告从后向前一个一个的删除 NACK— SN域， 如果 NACK— SN域携带 SOstart域和 SOend域的话， 需要一 并删除， 删到满足调度带宽之后， 将最后删除的一个 NACK— SN域作为 ACK_SN填写， 然后将裁剪的状态报告作为一个整体发送出去。
图 2和图 3是一个例子， 图 2 中 RLC需要发送一个状态报告， 其中 ACK— SN为 550, 指明 RLC AM接收端接收滑窗排序段后第一个未完整接 收的 RLC PDU的 SN为 550。其中携带一个 NACK— SN域，假如指明的 RLC PDU SN为 530, 这个 NACK— SN域携带了 SOstart域和 SOend域， 指明了 RLC AM接收端接收滑窗排序段中缺失 SN=530的 RLC PDU的一个分片。 通过图 2可以看到这样的一个状态报告需要 8字节。 假如这个时候的空口 调度带宽为 7个字节， 那么这样一个状态报告就无法完整发送出去， 那么 按照上面的状态报告裁剪方式， 这个状态报告就被裁减成图 3 的形式， 可 以看到变为只有两个字节， 其中将一个 NACK— SN 域删除了， 并且将 ACK_SN变为 530。这个时候存在一个问题， RLC AM接收端本来想要 RLC AM发送端重传 PDU为 530的一个分片， 但是由于空口调度带宽不够， 导 致状态报告被裁减， 裁剪之后的状态报告里面不携带 NACK— SN域， 并且 将 ACK— SN从 550变为 530。 RLC AM发送端收到这样一个状态报告后， 按照目前协议： 1 )无须为 RLC AM接收端重传任何报文； 2 ) RLC AM发 送端的发送滑窗可以释放到 530 的前一个单元。 这里存在的问题是， 假如 一段时间内空口的调度带宽都不够 8个字节， 那么 RLC AM接收端就只能 一直发送这样一个被裁剪过的状态报告， 而 RLC AM发送端则一直不能给 RLC AM接收端重传报文 530, 导致 RLC AM接收端无法收齐 530而不能 前移接收滑窗， 就会反过来造成 RLC AM发送端的发送滑窗停滞， 这样就 进入了一个死锁状态。 这样当 RLC AM发送端发送滑窗满了之后， 发送滑 窗就不能容纳新的 RLC PDU, 导致 RLC AM发送端断流， 这时候 RLC AM 发送端按照协议会主动发送 Polling PDU请求 RLC AM接收端回复状态报 告， 而如果 RLC AM接收端的空口调度仍然维持在小于 8个字节的话， 那 么被裁减的状态报告不能使 RLC AM发送端前移发送滑窗， 最终导致发送 端一直重发 Polling PDU, 导致 Polling PDU被重传超过设定的 RLC最大重 传次数， 导致承载或者 UE被释放。 通过上面的举例分析， 可以看到， 按照目前的 RLC协议设计， 是存在 一个缺陷的。 那就是当 RLC AM接收端在一段时间内调度带宽比较小， 如 果被裁减过的状态报告无法携带任何 NACK— SN域， 则 RLC AM发送端不 能给 RLC AM接收端重传任何报文， 导致 RLC AM接收端接收滑窗不能前 移， 反过来导致 RLC AM发送端发送滑窗不能前移， 使得进入一个死锁状 态。如果这种情况一段时间内保持，则最终会导致发送端 RLC滑窗满断流， 以及导致后续的 RLC超过最大重传次数引起承载或者 UE被释放的问题。 发明内容
本发明的目的在于提供一种 RLC AM状态报告处理的方法和系统， 用 于解决 RLC超过最大重传次数引起承载或者 UE被释放的问题
根据本发明的一个方面， 提供了一种 RLC AM状态报告处理的方法， 包括以下步驟：
RLC AM发送端接收 RLC AM接收端发送的 RLC AM状态报告； RLC AM发送端判断 RLC AM状态报告是裁剪状态报告或者正常状态 报告；
当 RLC AM状态报告是裁剪状态报告， 根据 RLC AM状态报告的相应 标识进行重传处理；
当 RLC AM状态报告是正常状态报告， 根据 RLC AM状态报告的相应 标识进行处理。
优选的， 在 RLC AM接收端发送 RLC AM状态报告之前， 所述方法还 包括：
RLC AM发送端向 RLC AM接收端发送 RLC PDU;
RLC AM接收端根据接收到的 RLC PDU产生 RLC AM状态 4艮告。 优选的， RLC AM发送端判断 RLC AM状态报告是裁剪状态报告或者 正常状态报告为： 判断 RLC AM状态报告中是否只包含 RLC AM接收端没有完整接收但 不需要重传的 RLC PDU的标识； 判断 RLC AM发送端接收到的 RLC AM 状态报告的次数是否大于或等于系统设定的重传次数； 判断 RLC AM发送 端是否存在已经发出但未被接收端确认的 RLC PDU;
当 RLC AM状态报告中只包含 RLC AM接收端没有完整接收但不需要 重传的 RLC PDU的标识、 RLC AM发送端接收到的 RLC AM状态报告的 次数大于或等于系统设定的重传次数并且 RLC AM发送端存在已经发出但 未被接收端确认的 RLC PDU, 所述 RLC AM状态报告是裁剪状态报告， 否 则， 所述 RLC AM状态报告是正常状态报告。
优选的， 根据 RLC AM状态报告的相应标识进行重传处理为： 把 RLC AM状态报告中标识为没有完整接收但不需要重传的 RLC PDU 进行重传。
优选的， 根据 RLC AM状态报告的相应标识进行处理为：
根据 RLC AM状态报告得到标识为没有完整接收但不需要重传的 RLC
PDU的序列号， 在 RLC AM发送端中把序列号小于标识为没有完整接收但 不需要重传的 RLC PDU的序列号的 RLC PDU删除；
把 RLC AM状态报告中标识为没有完整接收且需要重传的 RLC PDU 进行重传。
根据本发明的一个方面， 提供了一种 RLC AM状态报告处理的系统， 包括：
RLC AM接收端， 用于发送 RLC AM状态报告；
RLC AM发送端， 用于接收 RLC AM状态报告， 并判断 RLC AM状态 报告是裁剪状态报告或者正常状态报告， 当 RLC AM状态报告是裁剪状态 报告， 根据 RLC AM状态艮告的相应标识进行重传处理， 当 RLC AM状态 报告是正常状态报告， 根据 RLC AM状态报告的相应标识进行处理。 优选的， RLC AM发送端包括：
信息接收单元， 用于接收 RLC AM状态报告；
状态报告判断单元， 用于判断 RLC AM状态报告是裁剪状态报告或者 正常状态报告；
状态报告处理单元， 用于当 RLC AM状态报告是裁剪状态报告时， 根 据 RLC AM状态报告的相应标识进行重传处理， 当 RLC AM状态艮告是正 常状态报告时， 根据 RLC AM状态报告的相应标识进行处理。
优选的， 所述状态报告判断单元包括：
标识识别单元， 用于判断 RLC AM状态报告中是否只包含 RLC AM接 收端没有完整接收但不需要重传的 RLC PDU的标识；
重传次数判断单元， 用于判断 RLC AM发送端接收到的 RLC AM状态 报告的次数是否大于或等于系统设定的重传次数；
存储识别单元， 用于判断 RLC AM发送端是否存在已经发出但未被接 收端确认的 RLC PDU;
相应地， 所述状态报告判断单元， 具体用于当所述 RLC AM状态报告 中只包含 RLC AM接收端没有完整接收但不需要重传的 RLC PDU的标识、 RLC AM发送端接收到的 RLC AM状态报告的次数大于或等于系统设定的 重传次数并且 RLC AM发送端存在已经发出但未被接收端确认的 RLC PDU, 确定 RLC AM状态报告是裁剪状态报告， 否则， 确定所述 RLC AM 状态报告是正常状态报告。
优选的， 状态报告处理单元包括：
裁剪状态报告处理单元， 用于把 RLC AM状态报告中标识为没有完整 接收但不需要重传的 RLC PDU进行重传；
正常状态报告处理单元， 用于根据 RLC AM状态报告得到标识为没有 完整接收但不需要重传的 RLC PDU的序列号， 再在 RLC AM发送端中把 序列号小于标识为没有完整接收但不需要重传的 RLC PDU 的序列号的 RLC PDU删除，并把 RLC AM状态报告中标识为没有完整接收且需要重传 的 RLC PDU进行重传。
优选的， RLC AM发送端还包括：
信息发送单元， 用于向 RLC AM接收端发送无线链路控制数据单元 ( RLC PDU )。
与现有技术相比较， 本发明的有益效果在于： 本发明通过对 PLC AM 状态报告进行判别和处理解决了 RLC超过最大重传次数引起承载或者 UE 被释放的问题。 附图说明
图 1是现有技术提供的 RLC AM状态报告的报文格式示意图； 图 2是现有技术提供的裁剪前的状态报告示意图；
图 3是现有技术提供的裁剪后的状态报告示意图。
图 4是本发明提供的 RLC AM状态报告处理的方法流程示意图； 图 5是本发明提供的 RLC AM状态报告处理的系统框图。 具体实施方式
以下结合附图对本发明的优选实施例进行详细说明， 应当理解， 以下 所说明的优选实施例仅用于说明和解释本发明， 并不用于限定本发明。
图 4显示了本发明提供的 RLC AM状态报告处理的方法流程示意， 如 图 4所示：
步驟 S401 , RLC AM发送端接收 RLC AM接收端发送的 RLC AM状态 报告。
在此之前， RLC AM发送端向 RLC AM接收端发送 RLC PDU, RLC AM 接收端根据接收到的 RLC PDU产生并发送 RLC AM状态报告。 步驟 S402 , RLC AM发送端判断 RLC AM状态报告是裁剪状态报告还 是正常状态报告。
判断过程如下： 判断 RLC AM状态报告中是否只包含 RLC AM接收端 没有完整接收但不需要重传的 RLC PDU的标识， 判断 RLC AM发送端接 收到的 RLC AM状态报告的次数是否大于或等于系统设定的重传次数， 判 断 RLC AM发送端是否存在已经发出但未被接收端确认的 RLC PDU;应当 理解， 这里， 所述的三个判断过程没有严格的先后顺序。
若 RLC AM状态报告中只包含 RLC AM接收端没有完整接收但不需要 重传的 RLC PDU的标识、 RLC AM发送端接收到的 RLC AM状态报告的 次数大于或等于系统设定的重传次数并且 RLC AM发送端存在已经发出但 未被接收端确认的 RLC PDU,则 RLC AM状态报告是裁剪状态报告，否则， RLC AM状态报告是正常状态报告。
步驟 S403 , 若 RLC AM状态报告是裁剪状态报告， 则根据 RLC AM状 态报告的相应标识进行重传处理， 把 RLC AM状态报告中标识为没有完整 接收但不需要重传的 RLC PDU进行重传。
步驟 S404,若 RLC AM状态报告是正常状态报告， 则根据 RLC AM状 态报告的相应标识进行处理， 根据 RLC AM状态报告得到标识为没有完整 接收但不需要重传的 RLC PDU的序列号， 在 RLC AM发送端中把序列号 小于标识为没有完整接收但不需要重传的 RLC PDU的序列号的 RLC PDU 删除， 再把 RLC AM状态报告中标识为没有完整接收且需要重传的 RLC PDU进行重传。
应当理解， 上述步驟 S403和步驟 S404在实现上没有先后顺序。
图 5显示了本发明提供的 RLC AM状态报告处理的系统框图， 如图 5 所示 , 系统包括 RLC AM接收端和 RLC AM发送端 , RLC AM接收端当接 收到 RLC AM发送端发送的 RLC PDU时，产生 RLC AM状态艮告并向 RLC AM发送端发送。
RLC AM发送端包括信息接收单元、 状态报告判断单元、 状态报告处 理单元和信息发送单元，信息接收单元接收 RLC AM接收端发送的 RLC AM 状态报告 , 状态报告判断单元判断 RLC AM状态报告是裁剪状态报告还是 正常状态报告然后交由状态报告处理单元处理， 状态报告处理单元当 RLC AM状态报告是裁剪状态报告时， 根据 RLC AM状态报告的相应标识进行 重传处理， 当 RLC AM状态报告是正常状态报告时， 根据 RLC AM状态报 告的相应标识进行处理， 信息发送单元实时向 RLC AM接收端发送 RLC 其中， 状态报告判断单元包括标识识别单元、 重传次数判断单元和存 储识别单元， 标识识别单元判断 RLC AM状态报告中是否只包含 RLC AM 接收端没有完整接收但不需要重传的无线链路控制数据单元 RLC PDU 的 标识， 重传次数判断单元判断 RLC AM发送端接收到的 RLC AM状态报告 的次数是否大于或等于系统设定的重传次数， 存储识别单元判断 RLC AM 发送端是否存在已经发出但未被接收端确认的 RLC PDU,若 RLC AM状态 报告中只包含 RLC AM接收端没有完整接收但不需要重传的 RLC PDU的 标识、 RLC AM发送端接收到的 RLC AM状态报告的次数大于或等于系统 设定的重传次数并且 RLC AM发送端存在已经发出但未被接收端确认的 RLC PDU, 则 RLC AM状态报告是被裁剪状态报告， 否则， RLC AM状态 报告是正常状态报告。
状态报告处理单元包括裁剪状态报告处理单元和正常状态报告处理单 元， 裁剪状态报告处理单元用于把 RLC AM状态报告中标识为没有完整接 收但不需要重传的 RLC PDU进行重传， 正常状态报告处理单元用于根据 RLC AM状态报告得到标识为没有完整接收但不需要重传的 RLC PDU的序 列号， 再在 RLC AM发送端中把序列号小于标识为没有完整接收但不需要 重传的 RLC PDU的序列号的 RLC PDU删除，并把 RLC AM状态报告中标 识为没有完整接收且需要重传的 RLC PDU进行重传。
下面通过一个具体实施例， 对本发明 RLC AM状态 ^艮告处理的方法进 行评细说明。
本发明优化了 3GPP 36.322 RLC协议中 RLC AM模式下处理状态报告 的机制， 主要是对收到的状态报告进行判断， 区分出一个只包含 ACK— SN 域的状态报告是否为一个被裁减的状态报告， 从而快速重传对应的 RLC PDU, 避免由于状态报告的发送端在一定时间内空口调度不够导致的一直 不能发送有效的状态报告，造成收发两端 RLC滑窗停滞而引起 RLC数据发 送端断流或者 RLC 达到最大重传次数的问题。 对于本发明中涉及的 RLC 状态报告的处理， 可以作为 3GPP 36.322 RLC协议处理状态报告原有方式 的一个补充， 可以避免原协议中存在的上述的缺陷。
RLC AM发送端接收到一个 RLC AM状态报告， 如果只包含 ACK— SN 域， 则和自己的发送滑窗中的相关变量进行对比， 如果 ACK— SN域等于当 前发送滑窗的发送下沿 VtA, 同时发送滑窗又不为空， 具体判断条件为 VtA!=VtS, VtS为发送滑窗内下一个要发送的 RLC PDU的 SN, 这时候可 以初步认定该状态报告可能是一个被裁减过的状态报告。 但是该状态报告 也有可能是之前的某个经过底层 Harq重传迟到的状态报告。 为了区分这种 情况， 可以设一个门限标识 RH, 设置 RH大于等于底层设置的 Harq的最 大重传次数。那么如果多次接收到满足条件 (ACK— SN==VtA)&&(VtA != VtS) 的状态报告， 而相同状态报告的连续接收次数大于或等于 RH, 则认为这个 状态报告肯定不是之前的某个由于底层 Harq重传迟到的， 则可以认定它是 一个被裁剪过的状态报告。 这时候对于一个被裁减过的状态报告， 其中 ACK_SN域实际应该是一个接收端未完整接收的 RLC PDU的 SN, 所以 RLC AM发送端将 ACK— SN域对应的 RLC PDU进行重传，就可以触发 RLC AM接收端接收完整该 RLC PDU, 使得 RLC AM接收端接收滑窗前移 , 反 过来使得 RLC AM发送端发送滑窗前移， 最终快速结束 RLC AM发送端发 送滑窗的停滞， 避免后续的 RLC断流以及 UE或者承载被释放的问题。
具体本发明可以按照如下方式来实施。
首先设置一个变量 RH, 保证 RH大于或等于底层设置的 Harq最大重 传次数； 然后为对应的 RLC AM 载设置两个变量： RlcAckedVtaSN和 RlcAckedVtaCount, 用于记录最后一次符合条件的状态报告的 ACK— SN的 值， 以及连续接收到相同符合条件的状态报告的次数， RlcAckedVtaSN初 始化为 OxFFFF, RlcAckedVtaCount初始化为 0。 设当前收到的状态报告中 的 ACK— SN域的值为 AckSn,本发明中 RLC具体处理状态报告的实施步驟 如下：
步驟 S601 , 判断该状态报告是否没有包含任何 NACK— SN域， 如果为 真则继续执行步驟 S602, 否则转到步驟 S606。
步驟 S602, 判断当前是否满足 ((AckSn==VtA)&&(VtA!=VtS))， 如果为 真则继续执行步驟 S603 , 否则转到步驟 S606。
步驟 S603 , 判断是否满足 (AckSn==RlcAckedVtaSN), 如果为真则继续 执 行 步 驟 S604 , 否 则 设 置 RlcAckedVtaSN=AckSn 并 且 RlcAckedVtaCount=l , 之后退出， 结束状态报告的处理流程。
步驟 S604 , 执行 RlcAckedVtaCount=RlcAckedVtaCount+l。
步驟 S605, 判断是否满足 (RlcAckedVtaCount==RH), 如果为真， 则重 传 AckSn对应的 RLC PDU, 然后重新初始化 RlcAckedVtaSN为 OxFFFF, RlcAckedVtaCount为 0, 之后退出， 结束状态报告的处理流程； 如果为假， 则直接退出， 结束状态报告的处理流程。
步驟 S606, 设置 RlcAckedVtaSN为 OxFFFF, RlcAckedVtaCount为 0, 继续原有状态报告的处理流程。 综上所述， 本发明具有以下技术效果： 本发明改进了原有 RLC协议处 理状态报告的机制， 在 RLC AM发送端通过自己的发送滑窗的当前情况和 接收到的状态报告的内容， 判断这是否是一个被裁减过的状态报告， 从而 提取出需要重传的信息， 给 RLC AM接收端进行重传， 使得 RLC AM接收 端的接收滑窗前移， 从而促使 RLC AM发送端的发送滑窗前移， 避免由于 RLC AM发送端滑窗出现的 RLC满断流以及后续的 RLC超过最大重传次数 导致承载或者 UE被释放的问题， 提高了 LTE网络的空口效率和稳定性。
尽管上文对本发明进行了详细说明， 但是本发明不限于此， 本领域技 术人员可以根据本发明的原理进行各种修改。 因此， 凡按照本发明原理所 作的修改， 都应当理解为落入本发明的保护范围。

Claims

权利要求书
1、 一种 RLC AM状态报告处理的方法， 其特征在于， 所述方法包括： 配置为确认模式的无线链路控制 RLC AM发送端接收 RLC AM接收端 发送的 RLC AM状态 4艮告；
所述 RLC AM发送端判断所述 RLC AM状态报告是裁剪状态报告或者 正常状态报告；
当所述 RLC AM状态报告是裁剪状态报告， 根据所述 RLC AM状态报 告的相应标识进行重传处理；
当所述 RLC AM状态报告是正常状态报告， 根据所述 RLC AM状态报 告的相应标识进行处理。
2、 根据权利要求 1所述的方法， 其特征在于， 在 RLC AM接收端发送 RLC AM状态报告之前， 所述方法还包括：
所述 RLC AM发送端向所述 RLC AM接收端发送无线链路控制数据单 元 RLC PDU;
所述 RLC AM接收端根据接收到的 RLC PDU产生 RLC AM状态 4艮告。
3、 根据权利要求 1所述的方法， 其特征在于， 所述 RLC AM发送端判 断所述 RLC AM状态报告是裁剪状态报告或者正常状态报告为：
判断所述 RLC AM状态报告中是否只包含所述 RLC AM接收端没有完 整接收但不需要重传的 RLC PDU的标识； 判断所述 RLC AM发送端接收 到的 RLC AM状态报告的次数是否大于或等于系统设定的重传次数； 判断 当所述 RLC AM状态报告中只包含所述 RLC AM接收端没有完整接收 但不需要重传的 RLC PDU的标识、所述 RLC AM发送端接收到的 RLC AM 状态报告的次数大于或等于系统设定的重传次数并且所述 RLC AM发送端 存在已经发出但未被接收端确认的 RLC PDU,所述 RLC AM状态报告是裁 剪状态报告， 否则， 所述 RLC AM状态报告是正常状态报告。
4、 根据权利要求 1 至 3 任一项所述的方法， 其特征在于， 所述根据 RLC AM状态报告的相应标识进行重传处理为：
把所述 RLC AM状态报告中标识为没有完整接收但不需要重传的 RLC PDU进行重传。
5、 根据权利要求 1 至 3任一项所述的方法， 其特征在于， 所述根据 RLC AM状态 ^艮告的相应标识进行处理为：
根据所述 RLC AM状态报告得到标识为没有完整接收但不需要重传的 RLC PDU的序列号，在 RLC AM发送端中把序列号小于标识为没有完整接 收但不需要重传的 RLC PDU的序列号的 RLC PDU删除；
把所述 RLC AM状态报告中标识为没有完整接收且需要重传的 RLC PDU进行重传。
6、 一种 RLC AM状态报告处理的系统， 其特征在于， 所述系统包括： RLC AM接收端， 用于发送配置为确认模式的无线链路控制 RLC AM 状态报告；
RLC AM发送端， 用于接收所述 RLC AM状态报告， 并判断所述 RLC AM状态报告是裁剪状态报告或者正常状态报告， 当所述 RLC AM状态报 告是裁剪状态报告，根据所述 RLC AM状态报告的相应标识进行重传处理， 当所述 RLC AM状态报告是正常状态报告， 根据所述 RLC AM状态报告的 相应标识进行处理。
7、 根据权利要求 6所述的系统， 其特征在于， 所述 RLC AM发送端包 括：
信息接收单元， 用于接收所述 RLC AM状态报告；
状态报告判断单元， 用于判断所述 RLC AM状态报告是裁剪状态报告 或者正常状态报告； 状态报告处理单元，用于当所述 RLC AM状态报告是裁剪状态报告时， 根据所述 RLC AM状态艮告的相应标识进行重传处理， 当所述 RLC AM状 态报告是正常状态报告时， 根据所述 RLC AM状态报告的相应标识进行处 理。
8、 根据权利要求 6所述的系统， 其特征在于， 所述状态报告判断单元 包括：
标识识别单元， 用于判断所述 RLC AM状态报告中是否只包含所述 RLC AM接收端没有完整接收但不需要重传的无线链路控制数据单元 RLC PDU的标识；
重传次数判断单元， 用于判断所述 RLC AM发送端接收到的 RLC AM 状态报告的次数是否大于或等于系统设定的重传次数； 被接收端确认的 RLC PDU;
相应地， 所述状态报告判断单元， 具体用于当所述 RLC AM状态报告 中只包含所述 RLC AM接收端没有完整接收但不需要重传的 RLC PDU的 标识、 所述 RLC AM发送端接收到的 RLC AM状态报告的次数大于或等于 确认的 RLC PDU, 确定所述 RLC AM状态报告是裁剪状态报告， 否则， 确 定所述 RLC AM状态报告是正常状态报告。
9、 根据权利要求 6至 8任一项所述的系统， 其特征在于， 所述状态报 告处理单元包括：
裁剪状态报告处理单元， 用于把所述 RLC AM状态报告中标识为没有 完整接收但不需要重传的 RLC PDU进行重传；
正常状态报告处理单元， 用于根据所述 RLC AM状态报告得到标识为 没有完整接收但不需要重传的 RLC PDU的序列号， 在 RLC AM发送端中 把序列号小于标识为没有完整接收但不需要重传的 RLC PDU 的序列号的 RLC PDU删除，并把所述 RLC AM状态报告中标识为没有完整接收且需要 重传的 RLC PDU进行重传。
10、 根据权利要求 9所述的系统， 其特征在于， 所述 RLC AM发送端 还包括：
信息发送单元， 用于向所述 RLC AM接收端发送无线链路控制数据单 元 RLC PDU。
PCT/CN2012/072266 2011-08-24 2012-03-13 一种rlcam状态报告处理的方法和系统 WO2012155619A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201110248235.9 2011-08-24
CN201110248235.9A CN102957522B (zh) 2011-08-24 2011-08-24 一种rlc am状态报告处理的方法和系统

Publications (1)

Publication Number Publication Date
WO2012155619A1 true WO2012155619A1 (zh) 2012-11-22

Family

ID=47176231

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/072266 WO2012155619A1 (zh) 2011-08-24 2012-03-13 一种rlcam状态报告处理的方法和系统

Country Status (2)

Country Link
CN (1) CN102957522B (zh)
WO (1) WO2012155619A1 (zh)

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107659959B (zh) * 2016-07-25 2020-10-30 普天信息技术有限公司 一种专网无线通信系统中上报接收数据状态的方法
CN108282273B (zh) 2017-01-05 2024-03-08 华为技术有限公司 分段重传的方法和装置
KR102262269B1 (ko) * 2017-04-26 2021-06-08 삼성전자 주식회사 차세대 이동 통신 시스템에서 rlc 상태 보고 방법 및 장치
CN108809540B (zh) * 2017-05-05 2021-09-17 华为技术有限公司 数据处理方法及设备
CN107172649A (zh) * 2017-07-26 2017-09-15 京信通信系统（中国）有限公司 一种数据传输方法及设备
WO2020034133A1 (zh) * 2018-08-16 2020-02-20 华为技术有限公司 通信方法及装置
CN110971352B (zh) * 2018-09-30 2021-01-26 大唐移动通信设备有限公司 一种上行增强rlc分片的harq重传处理方法及装置
CN112019306B (zh) * 2019-05-28 2022-02-18 上海华为技术有限公司 一种数据重传方法以及装置
CN112637876B (zh) * 2020-12-30 2023-05-12 京信网络系统股份有限公司 一种状态报告的发送方法、装置、电子设备及介质
CN116963163A (zh) * 2022-04-18 2023-10-27 中兴通讯股份有限公司 状态报告生成方法、装置、计算机设备及可读介质
CN114826495B (zh) * 2022-06-22 2022-09-16 深圳市佳贤通信设备有限公司 一种降低nr、rlc、am分片丢失报告开销的方法

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1697556A (zh) * 2004-05-12 2005-11-16 华为技术有限公司 一种状态报告的传输方法
CN101697630A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 一种无线链路扩充缓冲区状态报告的方法及装置
CN101895372A (zh) * 2010-06-29 2010-11-24 中国科学院计算技术研究所 无线链路控制层确认模式下的数据传输方法
CN101989899A (zh) * 2009-07-31 2011-03-23 中兴通讯股份有限公司 一种无线链路控制层触发状态报告的方法及接收侧装置

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101651527A (zh) * 2008-08-11 2010-02-17 华为技术有限公司 数据处理方法、重传上报方法、设备及数据传输系统

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1697556A (zh) * 2004-05-12 2005-11-16 华为技术有限公司 一种状态报告的传输方法
CN101989899A (zh) * 2009-07-31 2011-03-23 中兴通讯股份有限公司 一种无线链路控制层触发状态报告的方法及接收侧装置
CN101697630A (zh) * 2009-10-23 2010-04-21 中兴通讯股份有限公司 一种无线链路扩充缓冲区状态报告的方法及装置
CN101895372A (zh) * 2010-06-29 2010-11-24 中国科学院计算技术研究所 无线链路控制层确认模式下的数据传输方法

Also Published As

Publication number Publication date
CN102957522A (zh) 2013-03-06
CN102957522B (zh) 2017-05-10

Similar Documents

Publication Publication Date Title
WO2012155619A1 (zh) 一种rlcam状态报告处理的方法和系统
US8958411B2 (en) Method of transmitting RLC data
US8413002B2 (en) Method of performing ARQ procedure for transmitting high rate data
EP2290866B1 (en) Method for moving a receive window in a radio access network
EP2238707B1 (en) Method of detecting and handling an endless rlc retransmission
JP5671122B2 (ja) 無線通信システムの状態情報送信方法及び受信装置
KR101187076B1 (ko) 이동 통신 시스템에 있어서 신호 전송 방법
KR101194136B1 (ko) Ｍａｃ 층 리셋 후 노드-ｂ 에서 버퍼링된 데이터의 효과적인 복구를 위한 시스템
KR101387475B1 (ko) 복수의 네트워크 엔터티를 포함하는 이동 통신시스템에서의 데이터 처리 방법
US8503436B2 (en) Method of triggering status report in wireless communication system and receiver
WO2018127238A1 (zh) 信息处理方法及装置
US8649279B2 (en) Apparatus and method for adaptive TSP setting to minimize duplicate packet transmissions
EP2420014B1 (en) Method of receiving a point-to-multipoint service in a wireless communication system
TW200830776A (en) Method and apparatus for resegmentation of packet data for retransmission on HARQ transmission failure
KR20140097610A (ko) 다중 무선 접속 기술 기반 통신 시스템에서의 무선 링크 제어 상태 보고 전송 방법 및 장치
EP2158700A2 (en) Method for enhancing of controlling radio resources and transmitting status report in mobile telecommunications system and receiver of mobile telecommunications system
WO2009102167A2 (ko) 이동 통신 시스템에서 데이터 송수신 방법 및 장치
WO2009086679A1 (zh) 无线链路控制实体的复位控制方法
CN102315915A (zh) 一种构造状态报告的方法与装置
KR20090116614A (ko) 이동 통신 시스템에서 무선 링크 제어 데이터 처리 장치 및방법
KR101595575B1 (ko) 이동 통신 시스템에서 데이터 송수신 방법 및 장치
KR101693772B1 (ko) Ｒｌｃ 계층에서의 데이터 전송을 위한 시스템 및 그 방법
CN109729554B (zh) 上行增强数据传输方法、装置及用户设备
KR101617044B1 (ko) 피어 엔티티의 전송 상태 정보를 이용한 데이터 유닛 재전송 방법
KR101368499B1 (ko) 이동 통신 시스템에서 상태 보고 메시지를 송신하기 위한 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 12785432

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 12785432

Country of ref document: EP

Kind code of ref document: A1