WO2023202566A1 - 状态报告生成方法、装置、计算机设备及可读介质 - Google Patents

状态报告生成方法、装置、计算机设备及可读介质 Download PDF

Info

Publication number
WO2023202566A1
WO2023202566A1 PCT/CN2023/088934 CN2023088934W WO2023202566A1 WO 2023202566 A1 WO2023202566 A1 WO 2023202566A1 CN 2023088934 W CN2023088934 W CN 2023088934W WO 2023202566 A1 WO2023202566 A1 WO 2023202566A1
Authority
WO
WIPO (PCT)
Prior art keywords
information
hole
status report
length
air interface
Prior art date
Application number
PCT/CN2023/088934
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 WO2023202566A1 publication Critical patent/WO2023202566A1/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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/10—Scheduling measurement reports ; Arrangements for measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0055—Transmission or use of information for re-establishing the radio link
    • H04W36/0058—Transmission of hand-off measurement information, e.g. measurement reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management

Definitions

  • the present disclosure relates to the field of communication technology, especially but not limited to the field of 5G network communication.
  • RLC Radio Link Control, Wireless Link Layer Control
  • RLC AM Acknowledged Mode Confirmation
  • the transmission process of the RLC PDU (Protocol Data Unit, Protocol Data Unit) message in the RLC AM mode is as shown in the figure 1 shown.
  • RLC AM mode requires that each packet sent by the sender can receive a status report packet fed back by the receiver to ensure that the sender's message has been successfully received by the receiver, otherwise the sender will Perform retransmission.
  • 3GPP 38322 5.3.4 RLC layer protocol provides a detailed description of the status report format and status report packaging process, which explains how to generate a complete status report message based on the receiver window information and send it to the lower protocol layer.
  • the receiving end should tailor the status report to adapt to the air interface scheduling resources to ensure that the status report can be sent out from the air interface in a timely and efficient manner, so that the sending end can quickly receive a response.
  • the present disclosure provides a status report generating method, device, computer equipment and readable medium.
  • embodiments of the present disclosure provide a status report generation method.
  • the method includes: determining reception window information, where the reception window information includes at least one hole information; responding to the air interface scheduling resource being greater than or equal to the acknowledgment sequence number ACK_SN field
  • the length in the status report, the status report is generated according to the air interface scheduling resource, the length of the ACK_SN field in the status report and the type of hole, so that the length of the status report satisfies the air interface scheduling resource and the status Report the most content carrying the receive window information.
  • an embodiment of the present disclosure also provides a status report generating device, including a receiving window information determining module, Determination module and status report generation module, wherein the reception window information determination module is configured to determine reception window information, and the reception window information includes at least one hole information; the determination module is configured to determine whether the air interface scheduling resource is greater than or Equal to the length of the ACK_SN field in the status report; the status report generation module is configured to, in response to the air interface scheduling resource being greater than or equal to the length of the ACK_SN field in the status report, according to the air interface scheduling resource, the ACK_SN domain in the status report The length of the status report and the type of the hole are used to generate a status report, so that the length of the status report satisfies the air interface scheduling resource and the status report carries the maximum content of the reception window information.
  • an embodiment of the present disclosure also provides a computer device, including: one or more processors; a storage device on which one or more programs are stored; when the one or more programs are executed by the one or more When executed by multiple processors, the one or more processors implement the status report generating method as described above.
  • embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, wherein when the program is executed, the status report generating method as described above is implemented.
  • FIG. 1 is a schematic diagram of the RLC PDU message transmission process in RLC AM mode
  • Figure 2 is a schematic flowchart of a status report generation method provided by an embodiment of the present disclosure
  • Figure 3 is a schematic diagram of a receiving window provided by an embodiment of the present disclosure.
  • Figure 4 is a schematic flowchart of generating a status report based on air interface scheduling resources, the length of the ACK_SN field in the status report, and the type of holes provided by an embodiment of the present disclosure
  • Figure 5 is a schematic flowchart of determining the first receiving window information to be carried according to an embodiment of the present disclosure
  • Figures 6-12 are schematic diagrams of status reports in seven scenarios in specific examples provided by the embodiments of the present disclosure.
  • Figure 13 is a schematic structural diagram of a status report generating device provided by an embodiment of the present disclosure.
  • Figure 14 is a schematic structural diagram of a status report generation module provided by an embodiment of the present disclosure.
  • Embodiments described herein may be described with reference to plan and/or cross-sectional illustrations, with the aid of idealized schematic illustrations of the present disclosure. Accordingly, example illustrations may be modified based on manufacturing techniques and/or tolerances. Therefore, the embodiments are not limited to those shown in the drawings but include modifications of configurations formed based on the manufacturing process. Accordingly, the regions illustrated in the figures are of a schematic nature and the shapes of the regions shown in the figures are illustrative of the specific shapes of regions of the element and are not intended to be limiting.
  • Embodiments of the present disclosure provide a status report generation method, which realizes reasonable tailoring of the complete status report and can maximize the maximum amount of receiving window information sent to the sending device.
  • An embodiment of the present disclosure provides a status report generating method, as shown in Figure 2.
  • the method includes the following steps S21 and S22.
  • step S21 the reception window information is determined, and the reception window information includes at least one hole information.
  • FIG 3 is a schematic diagram of a receiving window.
  • the receiving window information may include ACK (Acknowledge, confirmation) message information and hole information.
  • the ACK message is the RLC PDU message sent by the sender received by the receiving end.
  • the ACK message information can be represented by the SN (Sequence Number, sequence number) of the RLC PDU message.
  • the loss of messages and message fragments causes the message frames to have gaps similar to "loopholes" during reassembly. Therefore, the messages or message fragments lost during this link transmission process are vividly called Is a hole.
  • the hole information may be represented by the SN of the RLC PDU message.
  • step S22 in response to the air interface scheduling resource being greater than or equal to the length of the ACK_SN field in the status report, a status report is generated based on the air interface scheduling resource, the length of the ACK_SN field in the status report, and the type of hole, so that the length of the status report satisfies
  • the air interface schedules resources and the status report carries the most content of the receiving window information.
  • Status reports such as RLC protocol layer status reports, can only include the ACK_SN (Acknowledgement SN, confirmation sequence number) field, but not the NACK_SN (Negative Acknowledgment SN, non-confirmation sequence number) field. Therefore, the length of the ACK_SN field in the status report That is the minimum length of the status report, usually 3 bytes.
  • the NACK_SN field is used to record the SN value of the lost AMD PDU or AMD PDU fragment, that is, the SN value corresponding to the hole.
  • the air interface scheduling resources are compared with the length of the ACK_SN field in the status report. If the air interface scheduling resources are greater than or equal to the length of the ACK_SN field in the status report, it means that the current air interface scheduling resources are sufficient to ensure the minimum length of the status report.
  • a status report can be constructed.
  • a status report is generated based on the air interface scheduling resources, the length of the ACK_SN field in the status report, and the type of hole.
  • the generated status report satisfies the air interface scheduling resources, which means that the length of the status report is smaller than the air interface scheduling resources, and the generated status report carries as much receiving window information as possible. In other words, the generated status report can carry the most hole information. and ACK message information.
  • the air interface scheduling resource is less than the length of the ACK_SN field in the status report, even the minimum length status report cannot be sent from the air interface, so the status report is no longer generated.
  • the status report generation method provided by the embodiment of the present disclosure includes determining the reception window information, which includes at least one hole information; in response to the air interface scheduling resource being greater than or equal to the minimum length of the ACK message in the status report, according to the air interface
  • the scheduling resources, the length of the ACK_SN field in the status report and the type of hole are used to generate the status report, so that the length of the status report meets the air interface scheduling resources and carries the maximum content of the receive window information.
  • the status report generated by the embodiment of the present disclosure can generate a status report that can be sent from the air interface and includes the most receiving window information content when the air interface condition is poor and the status report cannot be sent completely, so as to achieve reasonable tailoring of the complete status report and provide Message sender feedback update Accurate packet collection can avoid the waste of air interface scheduling resources caused by air interface obstruction, as well as the resulting problems such as RLC stuck windows.
  • the types of holes include: a single RLC PDU message, a continuous RLC PDU message, a single RLC PDU message fragment, a continuous RLC PDU message, and each of the continuous RLC PDU messages.
  • generating a status report (ie, step S22) based on air interface scheduling resources, the length of the ACK_SN field in the status report, and the type of hole includes the following steps S221 to S226.
  • step S221 the first remaining air interface scheduling resources are determined based on the air interface scheduling resources and the length of the ACK_SN field in the status report.
  • the first remaining air interface scheduling resource the air interface scheduling resource - the length of the ACK_SN field in the status report (3 bytes).
  • step S222 it is determined whether the first remaining air interface scheduling resource is greater than or equal to the minimum length of the NACK_SN field in the status report. If so, step S223 and step S224 are executed. Otherwise, step S225 and step S226 are executed.
  • the minimum length of the NACK_SN field in the status report refers to the minimum length occupied by a hole information in the status report.
  • the four hole types occupy different lengths in the status report. Among them, in AM 18bit mode, the length of a single RLC PDU message type hole in the status report is 2 bytes; the length of a continuous RLC PDU message type hole in the status report is 3 bytes; a single The length of the RLC PDU message fragment type hole in the status report is 6 bytes; it includes a combination of consecutive RLC PDU messages and RLC PDU message fragments located at the beginning and end of the continuous RLC PDU message. The length of the hole in the status report is 7 bytes.
  • the first remaining air interface scheduling resource is greater than or equal to the minimum length of the NACK_SN field in the status report, it means that theoretically the current air interface scheduling resources are sufficient to send a status report carrying NACK_SN domain information, that is, theoretically the status report can carry ACK_SN domain information and NACK_SN Domain information, but in fact whether the status report can really carry hole information and how much hole information it can carry need to be further determined based on the order and type of holes in the receiving window, so steps S223-224 are executed; if the first remaining air interface scheduling resource is less than NACK_SN
  • the minimum length of the field in the status report indicates that the current air interface scheduling resources are not enough to send a status report carrying a minimum hole information, so the status report can only carry ACK_SN domain information and cannot carry NACK_SN domain information, so steps S225-226 are performed.
  • Step S223 Determine the first receive window information to be carried based on the first remaining air interface scheduling resources, the order of holes in the reception window, and the length of each hole in the status report; wherein, the length of each hole in the status report is based on the length of each hole in the status report. Type determined.
  • the first reception window information to be carried includes at least ACK_SN field information, and may also include NACK_SN field information.
  • ACK_SN field information ie, NACK_SN domain information
  • NACK_SN field information ie, NACK_SN domain information
  • step S224 a status report is generated according to the first reception window information to be carried.
  • step S225 the second receiving window information to be carried is determined according to the receiving window information.
  • the second receiving window to be carried is The information includes ACK_SN field information but does not include hole information.
  • step S2266 a status report is generated according to the second reception window information to be carried.
  • the status report also includes status report header information.
  • the status report header information includes data/control bits (D/C) and control message type (CPT). The data/control bit is used to indicate whether the current RLC PDU message is a data message or a control message.
  • the first receiving window information to be carried is determined based on the first remaining air interface scheduling resources, the order of holes in the receiving window and the length of each hole in the status report (ie step S223 ), including the following steps S51 and S52.
  • step S51 according to the order of the holes in the receiving window, the length of the current hole in the status report and the length of all holes before the current hole in the status report are accumulated sequentially to obtain the current first length, until the current first length. until the length is greater than the current remaining air interface scheduling resources, where the current remaining air interface scheduling resources are determined based on the first remaining air interface scheduling resources and the length of the last accumulated hole in the status report.
  • the current first length is the length of the first hole in the status report.
  • step S52 hole information is determined according to the current hole type, and ACK_SN field information is determined.
  • the hole information is determined based on the type of hole (that is, the current hole) at the status report clipping position.
  • the hole information is determined in different ways. Details will be given later. Explain the above two options.
  • the preset type refers to the type of combination of continuous RLC PDU messages and RLC PDU message fragments located at the beginning and end of the continuous RLC PDU messages, that is, the type of hole 5 in Figure 3.
  • determining the hole information according to the type of the current hole includes the following steps: when the type of the current hole is not a preset type of hole, determine the location of the previous accumulation operation to stop the accumulation.
  • the first hole information contained is hole information. That is to say, for the situation that the current hole type is not a preset type, in this step, the first hole information included in the previous accumulation operation where the accumulation is stopped is used as the first NACK_SN field information to be carried in the reception window. If the current hole type is not a preset type, after determining the first NACK_SN field information to be carried in the reception window, the ACK_SN field information is determined based on the first hole information. That is to say, the first reception window information to be carried includes ACK_SN field information and NACK_SN field information.
  • the length of hole 1 accumulated for the first time is the first length of the first time.
  • the first length of the first time is combined with the current remaining air interface scheduling resources.
  • the current remaining air interface scheduling resources at this time are the first remaining air interface scheduling resources. If the first length of the first time is ⁇ the current remaining air interface scheduling resources, then the next Continue with the second accumulation.
  • the length of hole 2 and the length of hole 1 are accumulated for the second time to obtain the first length for the second time.
  • the current remaining air interface scheduling resources the first remaining air interface scheduling resources - the length of hole 1 in the status report.
  • the second first length is compared with the current remaining air interface scheduling resources.
  • the third accumulation is continued.
  • the length of hole 3, the length of hole 2 and the length of hole 1 are accumulated for the third time to obtain the first length of the third time.
  • the current remaining air interface scheduling resources the first remaining air interface scheduling resources - hole 1 in the status report
  • the current hole is Hole 3, and its type is continuous RLC PDU messages. That is, Hole 3 is not a hole of the preset type.
  • the first hole information contained in the second accumulation operation is used as the first to-be-carried receive window.
  • the receiving window is the receiving window shown in Figure 3
  • determining the hole information according to the type of the current hole includes the following steps: when the type of the current hole is a hole of a preset type, in response to the current remaining air interface scheduling resources being greater than Or equal to the length of the holes of the continuous RLC PDU message type in the status report, and less than the length of the holes of the preset type in the status report, determine the hole information, where the hole information includes the second hole information and the previous hole information that stops accumulation.
  • the first hole information included in an accumulation operation, and the second hole information includes the information of continuous RLC PDU messages in the current hole and the information of the RLC PDU messages to which the RLC PDU message fragments in the current hole belong.
  • the type of the current hole i.e. hole 5
  • the length of the holes of the continuous RLC PDU message type in the status report (3 bytes) ⁇ the current remaining air interface scheduling resources ⁇ the hole of the preset type is in The length (7 bytes) in the status report indicates that the NACK_SN field information in the status report cannot carry complete hole 5 information.
  • the first hole information includes the first hole information contained in the fourth accumulation operation.
  • the receiving window is the receiving window shown in Figure 3
  • NackSO refers to the fragmentation offset, which is used to indicate the current fragmentation The position of the fragment in the original RLC SDU), stop accumulating; when there are consecutive RLC PDU messages in the receiving window, all of which are empty, that is, the NackSN message carries NackRange (NackRange is used to indicate that there are consecutive RLC SDUs with SN lost. , the length is customized), if the current remaining air interface scheduling resource size cannot accommodate the length required to carry the NackRange information, the status report will not carry the NackRange information and the accumulation will stop.
  • Continuous RLC PDU messages in the receiving window are empty and empty.
  • the status report does not need to carry the NackSONackRange information and only carries the NackRangeNackSo information, where the NackRange information needs to reflect the information of the packet to which the NackSO belongs.
  • Scenario 1 If the air interface scheduling resources are large enough, no tailoring is performed, and a status report is generated according to the protocol requirements.
  • the status report contains all the receiving window information shown in Figure 3, and the constructed status report message format is shown in Figure 6.
  • E1/E2/E3 are status report construction indicator flags.
  • E1 is used to indicate whether there is a NACK SN field in the status report;
  • E2 is used to indicate whether there is SOstart/SOend;
  • E3 is used to indicate whether there is a NACK SN range.
  • NACK SN range is used to indicate that RLC SDUs with SN consecutive are lost.
  • the status report will be tailored according to different strategies according to the following six scenarios (scenario 2 to scenario 7):
  • Air interface scheduling resources can only accommodate ACK_SN domain information and cannot accommodate any NACK_SN domain information.
  • clipping is performed from the position starting from the first hole, and the format of the clipped status report is shown in Figure 7.
  • Air interface scheduling resources can only accommodate the first hole information, but cannot accommodate the second hole information.
  • clipping is performed from the starting position of the second hole.
  • the clipped status report format is shown in Figure 8.
  • the status report includes both ACK_SN field information and NACK_SN field information.
  • Air interface scheduling resources can only accommodate the first hole information and the second hole information, but cannot accommodate the third hole information.
  • clipping is performed from the beginning of the third hole.
  • the clipped status report format is shown in Figure 9.
  • the status report includes both ACK_SN field information and NACK_SN field information.
  • Air interface scheduling resources can only accommodate the first hole information, the second hole information, and the third hole information, but cannot accommodate the fourth hole information.
  • clipping is performed from the position starting from the fourth hole.
  • the clipped status report format is shown in Figure 10.
  • the status report includes both ACK_SN field information and NACK_SN field information.
  • Air interface scheduling resources can only accommodate the first hole information, the second hole information, the third hole information, and the fourth hole information, but cannot accommodate the fifth hole information.
  • clipping is performed from the position starting from the fifth hole.
  • the clipped status report format is shown in Figure 11.
  • the status report includes both ACK_SN field information and NACK_SN field information.
  • the air interface scheduling resource can only accommodate the first hole information, the second hole information, the third hole information and the fourth hole information. It cannot accommodate the complete fifth hole information, but it can accommodate the first four holes. information and the fifth hole information excluding fragmentation information.
  • the generated status report format is shown in Figure 12.
  • the status report includes both ACK_SN field information and NACK_SN field information.
  • the NACK_SN field information includes the first hole information, the second hole information, the third hole information, the fourth hole information and the fifth hole information excluding fragmentation information.
  • the disclosed embodiments can be applied to scenarios where the 5G NR air interface is blocked, far-point scenarios, or scenarios with a high packet error rate.
  • the status report tailoring function can be completed in the most efficient manner when the air interface capability is insufficient.
  • the status report can contain the most receiving window information, avoiding waste of air interface resources and avoiding too many messages from the sender. invalid retransmission, which supplements the existing protocol.
  • the embodiments of this disclosure improve and optimize the content of the RLC status report protocol, with the purpose of sending the most efficient status report under the premise that there is a bottleneck in air interface scheduling resources.
  • the ability of the status report to carry receive window information is determined based on the size of the air interface scheduling resources, and the status report packet format is dynamically adjusted to ensure that the status report can carry the most content of the receive window information under the current air interface scheduling resources.
  • the size of the status report matches the allocated air interface scheduling resources, carries as much receiving window content as possible, and feeds back a more accurate packet receiving situation to the message sending end to avoid the waste of air interface scheduling resources caused by air interface obstruction. And the resulting problems such as RLC stuck windows.
  • the status report generation device includes a reception window information determination module 101, a judgment module 102, and a status report generation module 103.
  • the receiving window information determining module 101 is configured to determine receiving window information, where the receiving window information includes at least one hole information.
  • the determination module 102 is configured to determine whether the air interface scheduling resource is greater than or equal to the length of the acknowledgment sequence number ACK_SN field in the status report.
  • the status report generation module 103 is configured to, in response to the air interface scheduling resource being greater than or equal to the length of the ACK_SN field in the status report, generate a status report according to the air interface scheduling resource, the length of the ACK_SN field in the status report, and the type of the hole, So that the length of the status report satisfies the air interface scheduling resource and the status report carries the maximum content of the reception window information.
  • the types of holes include: separate wireless link layer control protocol data unit RLC PDU messages, continuous RLC PDU messages, separate RLC PDU message fragments, including continuous RLC PDU messages. A combination of the RLC PDU message fragments and the RLC PDU message fragments respectively located at the beginning and end of the continuous RLC PDU message.
  • the status report generation module 103 includes: a remaining resource determination unit 1031, a judgment unit 1032, a reception window information to be carried determination unit 1033, and a status report generation unit 1034.
  • the remaining resource determining unit 1031 is configured to determine the first remaining air interface scheduling resource according to the air interface scheduling resource and the length of the ACK_SN field in the status report.
  • the judging unit 1032 is configured to judge whether the first remaining air interface scheduling resource is greater than or equal to the minimum length of the non-acknowledged sequence number NACK_SN field in the status report.
  • the reception window information to be carried determining unit 1033 is configured to, in response to the first remaining air interface scheduling resource being greater than or equal to Based on the minimum length of the NACK_SN field in the status report, determine the first receive window information to be carried based on the first remaining air interface scheduling resources, the order of holes in the reception window, and the length of each hole in the status report; The length of each hole in the status report is determined according to the type of each hole.
  • the status report generating unit 1034 is configured to generate a status report according to the first to-be-carried reception window information.
  • the reception window information to be carried determining unit 1033 is configured to, in accordance with the order of holes in the reception window, sequentially determine the length of the current hole in the status report and the length of all holes before the current hole in the status report. Accumulation is performed to obtain the current first length until the current first length is greater than the current remaining air interface scheduling resources, wherein the current remaining air interface scheduling resources are based on the first remaining air interface scheduling resources and the previously accumulated holes.
  • the length in the status report is determined; the hole information is determined according to the current hole type, and the ACK_SN field information is determined.
  • the reception window information to be carried determining unit 1033 is configured to, when the type of the current hole is not a preset type of hole, determine that the first hole information included in the previous accumulation operation to stop accumulation is the Hole information; when the current hole type is a preset type of hole, in response to the current remaining air interface scheduling resources being greater than or equal to the length of the hole in the status report of the continuous RLC PDU message type, and less than the length of the hole in the status report.
  • the length of the hole of the preset type in the status report is determined to determine the hole information, wherein the hole information includes the second hole information and the first hole information included in the previous accumulation operation that stopped the accumulation, and the second hole information Including the information of continuous RLC PDU messages in the current hole and the information of the packets to which the RLC PDU message fragments in the current hole belong; wherein, the preset type is the information of the continuous RLC PDU messages and the information located respectively in the continuous hole.
  • the to-be-carried reception window information determining unit 1033 is configured to, after determining the hole information, determine ACK_SN domain information according to the hole information and the reception window information.
  • the receiving window information to be carried determining unit 1033 is further configured to, in response to the first remaining air interface scheduling resource being less than the minimum length of the NACK_SN field in the status report, determine the second receiving window information based on the receiving window information.
  • the second reception window information to be carried includes ACK_SN field information but does not include hole information.
  • the status report generating unit 1034 is further configured to generate a status report according to the second to-be-carried reception window information.
  • Embodiments of the present disclosure also provide a computer device.
  • the computer device includes: one or more processors and a storage device; wherein one or more programs are stored on the storage device. When the one or more programs are used by the above-mentioned one When executed by or multiple processors, the above one or more processors implement the aforementioned status report generating method.
  • Embodiments of the present disclosure also provide a computer-readable medium on which a computer program is stored, wherein when the computer program is executed, the status report generating method as described above is implemented.
  • Such software may be distributed on computer-readable media, which may include computer storage media (or non-transitory media) and communication media (or transitory media).
  • computer storage media includes volatile and nonvolatile media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. removable, removable and non-removable media.
  • Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, Digital Versatile Disk (DVD) or other optical disk storage, magnetic cassettes, tapes, disk storage or other magnetic storage device, or any other medium that can be used to store the desired information and can be accessed by a computer.
  • communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism, and may include any information delivery media .

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

本公开提供一种状态报告生成方法，所述方法包括：确定接收窗口信息，接收窗口信息至少包括一个空洞信息；响应于空口调度资源大于或等于ACK_SN域在状态报告中的长度，根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使状态报告的长度满足空口调度资源且携带接收窗口信息的最多内容。本公开还提供一种状态报告生成装置、计算机设备和可读介质。

Description

状态报告生成方法、装置、计算机设备及可读介质
相关申请的交叉引用
本申请要求于2022年4月18日提交的中国专利申请NO.202210404258.2的优先权，该中国专利申请的内容通过引用的方式整体合并于此。
技术领域
本公开涉及通信技术领域，尤其但不限于5G网络通信领域。
背景技术
根据3GPP 38322协议层关于RLC(Radio Link Control，无线链路层控制)AM(Acknowledged Mode确认)模式的描述，RLC AM模式下RLC PDU(Protocol Data Unit，协议数据单元)报文的传输流程如图1所示。RLC AM模式要求发送端发送的每一包报文均能接收到接收端反馈的一包状态报告包，以保证发送端报文已被接收端成功接收，否则发送端将会对这包报文进行重传。3GPP 38322 5.3.4RLC层协议对状态报告格式及状态报告组包流程进行了详细的描述，其中阐述了如何根据接收端窗口信息生成完整的状态报告报文并发给下层协议层的过程。
但是，如果空口条件不好，空口误包较高，对应的空口调度资源也会相应减少。由于接收窗口空洞较多，根据协议，状态报告需要包含多个NACK报文信息，导致状态报告报文较大。因为状态报告报文不支持分片，若空口调度资源不足，则状态报告报文无法及时从空口发出，发送端无法获得状态报告反馈信息，势必影响发送端发送报文的效率，出现报文大量无效重传。故此时接收端应对状态报告进行裁剪以适配空口调度资源，保证状态报告能够及时、高效地从空口发出，从而发送端能够迅速得到响应。
随着5G应用场景增多，比如远点或者环境干扰，必然存在误包增大与调度授权变小的情况，而两者有极大可能同时出现。在误包增大的情况下，根据协议描述必定需要构建包长较大的RLC状态报告报文，由于状态报告的格式内没有唯一序列标签(SN)，因此RLC的状态报告不支持分片，无法实现拆分和重组，这样，就需要对状态报告做裁剪，但是如何做到裁剪后的状态报告携带最多的有效信息，协议未描述。
发明内容
本公开提供一种状态报告生成方法、装置、计算机设备及可读介质。
第一方面，本公开实施例提供一种状态报告生成方法，所述方法包括：确定接收窗口信息，所述接收窗口信息至少包括一个空洞信息；响应于空口调度资源大于或等于确认序列号ACK_SN域在状态报告中的长度，根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使所述状态报告的长度满足所述空口调度资源且所述状态报告携带所述接收窗口信息的最多内容。
又一方面，本公开实施例还提供一种状态报告生成装置，包括接收窗口信息确定模块、 判断模块和状态报告生成模块，其中，所述接收窗口信息确定模块配置为，确定接收窗口信息，所述接收窗口信息至少包括一个空洞信息；所述判断模块配置为，判断空口调度资源是否大于或等于ACK_SN域在状态报告中的长度；所述状态报告生成模块配置为，响应于空口调度资源大于或等于ACK_SN域在状态报告中的长度，根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使所述状态报告的长度满足所述空口调度资源且所述状态报告携带所述接收窗口信息的最多内容。
又一方面，本公开实施例还提供一种计算机设备，包括：一个或多个处理器；存储装置，其上存储有一个或多个程序；当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如前所述的状态报告生成方法。
又一方面，本公开实施例还提供一种计算机可读介质，其上存储有计算机程序，其中，所述程序被执行时实现如前所述的状态报告生成方法。
附图说明
图1为RLC AM模式下RLC PDU报文传输流程示意图；
图2为本公开实施例提供的状态报告生成方法的流程示意图；
图3为本公开实施例提供的接收窗口的示意图；
图4为本公开实施例提供的根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告的流程示意图；
图5为本公开实施例提供的确定第一待携带接收窗口信息的流程示意图；
图6-图12为本公开实施例提供的具体实例中7种场景下的状态报告的示意图；
图13为本公开实施例提供的状态报告生成装置的结构示意图；
图14为本公开实施例提供的状态报告生成模块的结构示意图。
具体实施方式
在下文中将参考附图更充分地描述示例实施例，但是所述示例实施例可以以不同形式来体现且不应当被解释为限于本文阐述的实施例。反之，提供这些实施例的目的在于使本公开透彻和完整，并将使本领域技术人员充分理解本公开的范围。
如本文所使用的，术语“和/或”包括一个或多个相关列举条目的任何和所有组合。
本文所使用的术语仅用于描述特定实施例，且不意欲限制本公开。如本文所使用的，单数形式“一个”和“该”也意欲包括复数形式，除非上下文另外清楚指出。还将理解的是，当本说明书中使用术语“包括”和/或“由……制成”时，指定存在所述特征、整体、步骤、操作、元件和/或组件，但不排除存在或添加一个或多个其他特征、整体、步骤、操作、元件、组件和/或其群组。
本文所述实施例可借助本公开的理想示意图而参考平面图和/或截面图进行描述。因此，可根据制造技术和/或容限来修改示例图示。因此，实施例不限于附图中所示的实施例，而是包括基于制造工艺而形成的配置的修改。因此，附图中例示的区具有示意性属性，并且图中所示区的形状例示了元件的区的具体形状，但并不旨在是限制性的。
除非另外限定，否则本文所用的所有术语(包括技术和科学术语)的含义与本领域普通技术人员通常理解的含义相同。还将理解，诸如那些在常用字典中限定的那些术语应当被解释 为具有与其在相关技术以及本公开的背景下的含义一致的含义，且将不解释为具有理想化或过度形式上的含义，除非本文明确如此限定。
现有的5G协议未对状态报告裁剪实现细节进行阐述，为了解决空口调度资源存在瓶颈，无法发出完整的状态报告带来的大量报文无效重传，造成空口调度资源浪费的问题。本公开实施例提供一种状态报告生成方法，实现对完整的状态报告的合理裁剪，可以最大限度将接收窗口信息发送到发送端设备。
本公开实施例提供一种状态报告生成方法，如图2所示，所述方法包括以下步骤S21和S22。
在步骤S21中，确定接收窗口信息，接收窗口信息至少包括一个空洞信息。
图3为一种接收窗口的示意图，如图3所示，接收窗口信息可以包括ACK(Acknowledge，确认)报文信息和空洞信息。ACK报文即为接收端接收到的由发送端发送的RLC PDU报文，ACK报文信息可以通过RLC PDU报文的SN(Sequence Number，序列号)表示。报文及报文分片的丢失导致重组成帧时的报文帧具有类似于“漏洞”的空缺，因此，将这种链路传输过程中丢失的报文或报文分片形象地称之为空洞(hole)。在本公开实施例中，空洞信息可以通过RLC PDU报文的SN表示。
在步骤S22中，响应于空口调度资源大于或等于ACK_SN域在状态报告中的长度，根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使状态报告的长度满足空口调度资源且状态报告携带接收窗口信息的最多内容。
状态报告，例如RLC协议层状态报告，可以仅包括ACK_SN(Acknowledgement SN，确认序列号)域，而不包括NACK_SN(Negative Acknowledgement SN，非确认序列号)域,因此，ACK_SN域在状态报告中的长度即为状态报告的最小长度，通常为3字节。ACK_SN域用于记录没有在STATUS PDU中上报为丢失的下一个还未收到的RLC Data PDU。示例性的，如图3所示的接收窗口，完整的状态报告中ACK_SN域的值为17，即ACK_SN＝17。NACK_SN域用于记录丢失的AMD PDU或AMD PDU分片的SN值，即空洞对应的SN值。
在本步骤中，将空口调度资源与ACK_SN域在状态报告中的长度相比较，若空口调度资源大于或等于ACK_SN域在状态报告中的长度，说明当前的空口调度资源足以保证最小长度的状态报告从空口发出，则可以构建状态报告，相应的，根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告。
生成的状态报告满足空口调度资源是指状态报告的长度小于空口调度资源，且生成的状态报告尽可能携带更多的接收窗口信息的内容，也就是说，生成的状态报告能够携带最多的空洞信息和ACK报文信息。
需要说明的是，在空口调度资源小于ACK_SN域在状态报告中的长度的情况下，即使最小长度的状态报告也无法从空口发出，因此不再生成状态报告。
本公开实施例提供的状态报告生成方法，所述方法包括确定接收窗口信息，接收窗口信息至少包括一个空洞信息；响应于空口调度资源大于或等于ACK报文在状态报告中的最小长度，根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使状态报告的长度满足空口调度资源且携带接收窗口信息的最多内容。本公开实施例生成的状态报告能够在空口条件较差导致状态报告无法完整发出的情况下，生成能够从空口发出且包括最多接收窗口信息内容的状态报告，实现对完整状态报告的合理裁剪，给报文发送端反馈更 准确的收包情况，避免空口受阻引起的空口调度资源浪费，以及由此导致的RLC卡窗等问题。
在一些实施例中，空洞的类型包括：单独的RLC PDU报文、连续的RLC PDU报文、单独的RLC PDU报文分片、包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合。
在如图3所示的接收窗口信息中，共包括上述4种类型的5个空洞：空洞1和空洞2分别为SN＝1和SN＝4的RLC PDU报文(类型为单独的RLC PDU报文)，空洞3为SN＝6和7的RLC PDU报文(类型为连续的RLC PDU报文)，空洞4为SN＝10的RLC PDU报文分片(类型为单独的RLC PDU报文分片)、空洞5为包括SN＝12的RLC PDU报文分片+SN＝13和14的连续RLC PDU报文+SN＝15的报文分片的组合(类型为包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合)。
在一些实施例中，如图4所示，所述根据空口调度资源、ACK_SN域在状态报告中的长度和空洞的类型生成状态报告(即步骤S22)，包括以下步骤S221至S226。
在步骤S221中，根据空口调度资源和ACK_SN域在状态报告中的长度，确定第一剩余空口调度资源。
第一剩余空口调度资源＝空口调度资源-ACK_SN域在状态报告中的长度(3字节)。
在步骤S222中，判断第一剩余空口调度资源是否大于或等于NACK_SN域在状态报告中的最小长度，若是，则执行步骤S223和步骤S224，否则，执行步骤S225和步骤S226。
NACK_SN域在状态报告中的最小长度是指状态报告中一个空洞信息所占用的最小长度，4种空洞类型在状态报告中所占用的长度不同。其中，在AM 18bit模式下，单独的RLC PDU报文类型的空洞在状态报告中的长度为2字节；连续的RLC PDU报文类型的空洞在状态报告中的长度为3字节；单独的RLC PDU报文分片类型的空洞在状态报告中的长度为6字节；包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合类型的空洞在状态报告中的长度为7字节。
若第一剩余空口调度资源大于或等于NACK_SN域在状态报告中的最小长度，说明理论上当前的空口调度资源足以发送携带NACK_SN域信息的状态报告，即理论上状态报告可携带ACK_SN域信息和NACK_SN域信息，但实际上状态报告是否真正能够携带空洞信息以及能够携带多少空洞信息还需进一步根据接收窗口中空洞的顺序和类型决定，因此执行步骤S223-224；若第一剩余空口调度资源小于NACK_SN域在状态报告中的最小长度，说明当前的空口调度资源不足以发送携带一个最小空洞信息的状态报告，则状态报告只能携带ACK_SN域信息，不能携带NACK_SN域信息，因此执行步骤S225-226。
步骤S223，根据第一剩余空口调度资源、接收窗口中空洞的顺序和各空洞在状态报告中的长度，确定第一待携带接收窗口信息；其中，各空洞在状态报告中的长度根据各空洞的类型确定。
第一待携带接收窗口信息至少包括ACK_SN域信息，还可以包括NACK_SN域信息。在本步骤中，根据第一剩余空口调度资源、接收窗口中空洞的顺序和各空洞在状态报告中的长度，确定状态报告是否携带空洞信息(即NACK_SN域信息)或者携带哪些空洞信息，其具体实现过程后续结合图5和图6再详细说明。
在步骤S224中，根据第一待携带接收窗口信息生成状态报告。
在步骤S225中，根据接收窗口信息确定第二待携带接收窗口信息，第二待携带接收窗口 信息包括ACK_SN域信息但不包括空洞信息。
在本步骤中，根据接口窗口信息确定第一个空洞的SNx，状态报告在第一空洞之前的位置进行裁剪，由此得到ACK_SN域的值即为SNx，即ACK_SN＝SNx。
在步骤S226中，根据第二待携带接收窗口信息生成状态报告。
状态报告中除了第一携带接收窗口信息或第二携带接收窗口信息之外，还包括状态报告头信息，状态报告头信息包括数据/控制位(D/C)和控制报文类型(CPT)，数据/控制位用于指示当前的RLC PDU报文是数据报文还是控制报文。
在一些实施例中，如图5所示，所述根据第一剩余空口调度资源、接收窗口中空洞的顺序和各空洞在状态报告中的长度，确定第一待携带接收窗口信息(即步骤S223)，包括以下步骤S51和S52。
在步骤S51中，按照接收窗口中空洞的顺序，依次对当前空洞在状态报告中的长度和当前空洞之前的全部空洞在状态报告中的长度进行累加，得到当前的第一长度，直到当前的第一长度大于当前的剩余空口调度资源为止，其中，当前的剩余空口调度资源根据第一剩余空口调度资源和前次累加的空洞在状态报告中的长度确定。
在本步骤中，从接收窗口的RX_Next(接收窗口的下边沿，即首个待重组数据包的SN)开始查询空洞SN号，在RX_Next到RX_Highest_Status(状态报告上边沿，即状态报告中可填写的ACKSN的最大SN)的范围内查询丢失的RLC PDU报文或报文分片。
需要说明的是，在当前空洞为接收窗口中首个空洞的情况下，当前的第一长度为该首个空洞在状态报告中的长度。
在步骤S52中，根据当前空洞的类型确定空洞信息，并确定ACK_SN域信息。
在本步骤中，根据状态报告裁剪位置的空洞(即当前空洞)类型确定空洞信息，针对当前空洞为预设类型的空洞以及非预设类型的空洞，采用不同的方式确定空洞信息，后续再详细说明上述2种方案。预设类型是指连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合的类型，即图3中空洞5的类型。
在一些实施例中，所述确定ACK_SN域信息包括以下步骤：在确定出空洞信息之后，根据空洞信息和接收窗口信息确定ACK_SN域信息。也就是说，在确定出空洞信息之后，即可确定出状态报告的裁剪位置，结合接收窗口信息和状态报告的裁剪位置即可确定出ACK_SN域信息。以图3所示的接收窗口为例，若空洞信息包括空洞1和空洞2的信息，那么状态报告的裁剪位置为SN＝5之后、空洞3之前，则ACK_SN域信息为ACKSN＝6。
在一些实施例中，所述根据当前空洞的类型确定空洞信息(即步骤S52)，包括以下步骤：在当前空洞的类型不是预设类型的空洞的情况下，确定停止累加的前一次累加操作所包含的第一空洞信息为空洞信息。也就是说，针对当前空洞的类型不是预设类型的情况，在本步骤中，将停止累加的前次累加操作所包含的第一空洞信息作为第一待携带接收窗口的NACK_SN域信息。当前空洞的类型不是预设类型的情况下，在确定出第一待携带接收窗口的NACK_SN域信息之后，根据第一空洞信息确定ACK_SN域信息。也就是说，第一待携带接收窗口信息包括ACK_SN域信息和NACK_SN域信息。
以图3所示的接收窗口为例，共有5个空洞，第一次累加得到空洞1的长度即为第一次的第一长度，将第一次的第一长度与当前的剩余空口调度资源相比较，此时当前的剩余空口调度资源即为第一剩余空口调度资源，若第一次的第一长度<当前的剩余空口调度资源，则继 续进行第二次累加。第二次累加空洞2的长度和空洞1的长度，得到第二次的第一长度，此时当前的剩余空口调度资源＝第一剩余空口调度资源-空洞1在状态报告中的长度，将第二次的第一长度与当前剩余空口调度资源相比较，若第二次的第一长度<当前的剩余空口调度资源，则继续进行第三次累加。第三次累加空洞3的长度、空洞2的长度和空洞1的长度，得到第三次的第一长度，此时当前的剩余空口调度资源＝第一剩余空口调度资源-空洞1在状态报告中的长度-空洞2在状态报告中的长度，将第三次的第一长度与当前剩余空口调度资源相比较，若第三次的第一长度>＝当前的剩余空口调度资源，则停止累加空洞。当前的空洞为空洞3，其类型为连续的RLC PDU报文，即空洞3不是预设类型的空洞，因此，将第二次累加操作所包含的第一空洞信息作为第一待携带接收窗口的NACK_SN域信息，第一空洞信息包括空洞1和空洞2的信息，即SN＝1和SN＝4的单独的RLC PDU报文的信息。在接收窗口为图3所示的接收窗口的情况下，此时第一待携带接收窗口的ACK_SN域信息为ACKSN＝6。
在一些实施例中，所述根据当前空洞的类型确定空洞信息(即步骤S52)，包括以下步骤：在当前空洞的类型为预设类型的空洞的情况下，响应于当前的剩余空口调度资源大于或等于连续的RLC PDU报文类型的空洞在状态报告中的长度，且小于预设类型的空洞在状态报告中的长度，确定空洞信息，其中，空洞信息包括第二空洞信息和停止累加的前一次累加操作所包含的第一空洞信息，第二空洞信息包括当前空洞中连续的RLC PDU报文信息和当前空洞中RLC PDU报文分片所属RLC PDU报文的信息。
以图3所示的接收窗口为例，共有5个空洞，假设进行五次累加，第五次的第一长度＝空洞1的长度+空洞2的长度+空洞3的长度+空洞4的长度+空洞5的长度，第五次的第一长度>＝当前的剩余空口调度资源，则停止累加空洞。当前的空洞(即空洞5)的类型为预设类型，若连续的RLC PDU报文类型的空洞在状态报告中的长度(3字节)≤当前的剩余空口调度资源<预设类型的空洞在状态报告中的长度(7字节)，说明状态报告中的NACK_SN域信息无法携带完整的空洞5的信息，因此，只能够携带连续丢失的报文信息而不携带报文分片信息，即空洞5的信息通过连续的RLC PDU报文信息体现，因此，第一待携带接收窗口中的空洞信息包括第二空洞信息和第一空洞是的信息，其中，第二空洞信息包括SN＝13和SN＝14的RLC PDU报文信息以及SN＝12和SN＝15的报文分片所属RLC PDU报文的信息，第一空洞信息包括第四次累加操作所包含的第一空洞信息，第一空洞信息包括空洞1的信息(即SN＝1的单独的RLC PDU报文的信息)+空洞2的信息(即SN＝4的单独的RLC PDU报文的信息)+空洞3的信息(从SN＝6开始、长度为2的连续的RLC PDU报文的信息)+空洞4的信息(SN＝10的单独的RLC PDU报文分片)。在接收窗口为图3所示的接收窗口的情况下，此时第一待携带接收窗口的ACK_SN域信息为ACKSN＝17。
由此可以看出，在本公开实施例中，若当前的剩余空口调度资源大小容不下一个NackSN信息所需要的长度，则停止累加；在接收窗口存在RLC PDU报文分片未收齐的情况下，即RLC PDU报文携带NackSO的场景，若当前的剩余空口调度资源大小容不下携带NackSO信息需要的长度，则状态报告不携带NackSO信息(NackSO是指分片偏移,用于指示当前分片在原始RLC SDU中的位置)，停止累加；在接收窗口存在连续的RLC PDU报文都是空洞的情况下，即NackSN报文携带NackRange的场景(NackRange用于表示有SN连续的RLC SDUs丢失，长度为自定义)，若当前的剩余空口调度资源大小容不下携带NackRange信息需要的长度，则状态报告不携带NackRange信息，停止累加。在接收窗口存在连续的RLC PDU报文都是空洞，且空洞 中连续RLC PDU报文的首尾存在报文分片未收齐的情况下，即RLC PDU报文携带NackRange和NackSONackSo的场景，若当前的剩余空口调度资源大小容不下携带NackRange信息和NackSoNackSO信息所需要的长度但能够容下NackSO信息，则状态报告可以不携带NackSONackRange信息和，仅携带NackRangeNackSo信息，其中NackRange信息需要体现出NackSO所属报文的信息。
以下分别结合图3和图6-11，以图3所示的接收窗口为例对生成状态报告的方式进行说明。
如果空口调度资源非常小，甚至无法满足ACK要求(ACK报文是状态报告报文的最小粒度)，则空口无法发出状态报告，相应不再生成状态报告。
场景一：如果空口调度资源足够大，不做裁剪处理，按照协议要求生成状态报告，状态报告包含图3所示的全部接收窗信息，构造的状态报告报文格式如图6所示。其中，E1/E2/E3为状态报告构造指示标识，E1用于指示状态报告中是否有NACK SN域存在；E2用于指示是否有SOstart/SOend存在；E3用于指示是否有NACK SN range存在。SOstart和SOend为丢失报文片段偏移，二者一起指示了SN＝NACK_SN的AMD PDU的哪一部分丢失，NACK SN range用于表示有SN连续的RLC SDUs丢失。
如果空口调度资源至少能够满足ACK要求，则根据以下六种场景(场景二至场景七)，按照不同策略裁剪状态报告：
场景二：空口调度资源只能容纳ACK_SN域信息,无法容纳任何NACK_SN域信息。在该场景下，从第一个空洞开始的位置进行剪裁，剪裁后的状态报告格式如图7所示。状态报告仅包括ACK_SN域信息，ACK_SN域信息为ACKSN＝1。
场景三：空口调度资源只能容纳第一个空洞信息，无法容纳第二个空洞信息。在该场景下，从第二个空洞开始的位置进行剪裁，剪裁后的状态报告格式如图8所示。状态报告既包括ACK_SN域信息又包括NACK_SN域信息，NACK_SN域信息为第一个空洞信息，即NACKSN＝1，ACK_SN域信息为ACNSN＝4。
场景四：空口调度资源只能容纳第一个空洞信息和第二个空洞信息，无法容纳第三个空洞信息。在该场景下，从第三个空洞开始的位置进行剪裁，剪裁后的状态报告格式如图9所示。状态报告既包括ACK_SN域信息又包括NACK_SN域信息，NACK_SN域信息包括第一个空洞信息和第二个空洞信息，即NACKSN＝1和NACKSN＝4，ACK_SN域信息为ACNSN＝6。
场景五：空口调度资源只能容纳第一个空洞信息、第二个空洞信息和第三个空洞信息，无法容纳第四个空洞信息。在该场景下，从第四个空洞开始的位置进行剪裁，剪裁后的状态报告格式如图10所示。状态报告既包括ACK_SN域信息又包括NACK_SN域信息，NACK_SN域信息包括第一个空洞信息、第二个空洞信息和第三个空洞信息，即NACKSN＝1、NACKSN＝4、NACKSN＝6且NACKRANGE＝2，ACK_SN域信息为ACNSN＝10。
场景六：空口调度资源只能容纳第一个空洞信息、第二个空洞信息、第三个空洞信息和第四个空洞信息，无法容纳第五个空洞信息。在该场景下，从第五个空洞开始的位置进行剪裁，剪裁后的状态报告格式如图11所示。状态报告既包括ACK_SN域信息又包括NACK_SN域信息，NACK_SN域信息包括第一个空洞信息、第二个空洞信息、第三个空洞信息和第四个空洞信息，即NACKSN＝1、NACKSN＝4、NACKSN＝6且NACKRANGE＝2、NACKSN＝10且SOSTART＝PAYLOAD_LOST_START且SOEND＝PAYLOAD_LOST_END，ACK_SN域信息为ACNSN＝12。
场景七：空口调度资源只能容纳第一个空洞信息、第二个空洞信息、第三个空洞信息和第四个空洞信息，无法容纳完整的第五个空洞信息，但是能够容纳前四个空洞信息和不包括分片信息的第五个空洞信息。在该场景下，生成状态报告格式如图12所示。状态报告既包括ACK_SN域信息又包括NACK_SN域信息，NACK_SN域信息包括第一个空洞信息、第二个空洞信息、第三个空洞信息、第四个空洞信息和不包括分片信息的第五个空洞信息(包括空洞5中的SN13-14以及SN12和SN15)，即NACKSN＝1、NACKSN＝4、NACKSN＝6且NACKRANGE＝2、NACKSN＝10且SOSTART＝PAYLOAD_LOST_START且SOEND＝PAYLOAD_LOST_END、NACKSN＝12且NACKRANGE＝4，ACK_SN域信息为ACNSN＝17。
本公开实施例可以应用于5G NR空口受阻的场景、远点场景或者高误包率的场景。采用本公开实施例所述的方案，可以满足在空口能力不足情况下以最高效的方式完成状态报告剪裁功能，状态报告能够包含最多的接收窗口信息，避免浪费空口资源，避免发送端报文多次无效重传，对现有协议进行了补充。
本公开实施例对RLC状态报告协议内容完善与优化，在空口调度资源存在瓶颈的前提下，以发送最高效状态报告为目的。根据空口调度资源的大小决策状态报告携带接收窗口信息的能力，动态调整状态报告组包格式，保证在当前空口调度资源的情况下，状态报告能够携带最多的接收窗口信息的内容。在本公开实施例中，状态报告的大小匹配分配的空口调度资源，携带尽可能多的接收窗口内容，给报文发送端反馈更准确的收包情况，避免空口受阻引起的空口调度资源浪费，以及由此导致的RLC卡窗等问题。
基于相同的技术构思，本公开实施例还提供一种状态报告生成装置，如图13所示，所述状态报告生成装置包括接收窗口信息确定模块101、判断模块102和状态报告生成模块103。接收窗口信息确定模块101配置为确定接收窗口信息，所述接收窗口信息至少包括一个空洞信息。
判断模块102配置为判断空口调度资源是否大于或等于确认序列号ACK_SN域在状态报告中的长度。
状态报告生成模块103配置为，响应于空口调度资源大于或等于ACK_SN域在状态报告中的长度，根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使所述状态报告的长度满足所述空口调度资源且所述状态报告携带所述接收窗口信息的最多内容。
在一些实施例中，所述空洞的类型包括：单独的无线链路层控制协议数据单元RLC PDU报文、连续的RLC PDU报文、单独的RLC PDU报文分片、包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合。
在一些实施例中，如图14所示，状态报告生成模块103包括：剩余资源确定单元1031、判断单元1032、待携带接收窗口信息确定单元1033和状态报告生成单元1034。剩余资源确定单元1031配置为根据所述空口调度资源和所述ACK_SN域在状态报告中的长度，确定第一剩余空口调度资源。
判断单元1032配置为判断所述第一剩余空口调度资源是否大于或等于非确认序列号NACK_SN域在状态报告中的最小长度。
待携带接收窗口信息确定单元1033配置为，响应于所述第一剩余空口调度资源大于或等 于NACK_SN域在状态报告中的最小长度，根据所述第一剩余空口调度资源、所述接收窗口中空洞的顺序和各所述空洞在状态报告中的长度，确定第一待携带接收窗口信息；其中，各所述空洞在状态报告中的长度根据各所述空洞的类型确定。
状态报告生成单元1034配置为根据所述第一待携带接收窗口信息生成状态报告。
在一些实施例中，待携带接收窗口信息确定单元1033配置为，按照所述接收窗口中空洞的顺序，依次对当前空洞在状态报告中的长度和当前空洞之前的全部空洞在状态报告中的长度进行累加，得到当前的第一长度，直到所述当前的第一长度大于当前的剩余空口调度资源为止，其中，当前的剩余空口调度资源根据所述第一剩余空口调度资源和前次累加的空洞在状态报告中的长度确定；根据当前空洞的类型确定空洞信息，并确定ACK_SN域信息。
在一些实施例中，待携带接收窗口信息确定单元1033配置为，在当前空洞的类型不是预设类型的空洞的情况下，确定停止累加的前一次累加操作所包含的第一空洞信息为所述空洞信息；在当前空洞的类型为预设类型的空洞的情况下，响应于所述当前的剩余空口调度资源大于或等于连续的RLC PDU报文类型的空洞在状态报告中的长度，且小于所述预设类型的空洞在状态报告中的长度，确定空洞信息，其中，所述空洞信息包括第二空洞信息和停止累加的前一次累加操作所包含的第一空洞信息，所述第二空洞信息包括当前空洞中连续的RLC PDU报文信息和当前空洞中RLC PDU报文分片所属报文的信息；其中，所述预设类型为所述包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合。
在一些实施例中，待携带接收窗口信息确定单元1033配置为，在确定出所述空洞信息之后，根据所述空洞信息和所述接收窗口信息确定ACK_SN域信息。
在一些实施例中，待携带接收窗口信息确定单元1033还配置为，响应于所述第一剩余空口调度资源小于所述NACK_SN域在状态报告中的最小长度，根据所述接收窗口信息确定第二待携带接收窗口信息，所述第二待携带接收窗口信息包括ACK_SN域信息但不包括空洞信息。
状态报告生成单元1034还配置为，根据所述第二待携带接收窗口信息生成状态报告。
本公开实施例还提供了一种计算机设备，该计算机设备包括：一个或多个处理器以及存储装置；其中，存储装置上存储有一个或多个程序，当上述一个或多个程序被上述一个或多个处理器执行时，使得上述一个或多个处理器实现如前述的状态报告生成方法。
本公开实施例还提供了一种计算机可读介质，其上存储有计算机程序，其中，该计算机程序被执行时实现如前述的状态报告生成方法。
本领域普通技术人员可以理解，上文中所公开方法中的全部或某些步骤、装置中的功能模块/单元可以被实施为软件、固件、硬件及其适当的组合。在硬件实施方式中，在以上描述中提及的功能模块/单元之间的划分不一定对应于物理组件的划分；例如，一个物理组件可以具有多个功能，或者一个功能或步骤可以由若干物理组件合作执行。某些物理组件或所有物理组件可以被实施为由处理器，如中央处理器、数字信号处理器或微处理器执行的软件，或者被实施为硬件，或者被实施为集成电路，如专用集成电路。这样的软件可以分布在计算机可读介质上，计算机可读介质可以包括计算机存储介质(或非暂时性介质)和通信介质(或暂时性介质)。如本领域普通技术人员公知的，术语计算机存储介质包括在用于存储信息(诸如计算机可读指令、数据结构、程序模块或其他数据)的任何方法或技术中实施的易失性和非易失性、可移除和不可移除介质。计算机存储介质包括但不限于RAM、ROM、EEPROM、闪存或其他存储器技术、CD-ROM、数字多功能盘(DVD)或其他光盘存储、磁盒、磁带、磁盘存储 或其他磁存储装置、或者可以用于存储期望的信息并且可以被计算机访问的任何其他的介质。此外，本领域普通技术人员公知的是，通信介质通常包含计算机可读指令、数据结构、程序模块或者诸如载波或其他传输机制之类的调制数据信号中的其他数据，并且可包括任何信息递送介质。
本文已经公开了示例实施例，并且虽然采用了具体术语，但它们仅用于并仅应当被解释为一般说明性含义，并且不用于限制的目的。在一些实例中，对本领域技术人员显而易见的是，除非另外明确指出，否则可单独使用与特定实施例相结合描述的特征、特性和/或元素，或可与其他实施例相结合描述的特征、特性和/或元件组合使用。因此，本领域技术人员将理解，在不脱离由所附的权利要求阐明的本发明的范围的情况下，可进行各种形式和细节上的改变。

Claims (10)

  1. 一种状态报告生成方法，包括：
    确定接收窗口信息，所述接收窗口信息至少包括一个空洞信息；以及
    响应于空口调度资源大于或等于确认序列号ACK_SN域在状态报告中的长度，根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使所述状态报告的长度满足所述空口调度资源且所述状态报告携带所述接收窗口信息的最多内容。
  2. 如权利要求1所述的方法，其中，所述空洞的类型包括：单独的无线链路层控制协议数据单元RLC PDU报文、连续的RLC PDU报文、单独的RLC PDU报文分片、包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合。
  3. 如权利要求2所述的方法，其中，所述根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，包括：
    根据所述空口调度资源和所述ACK_SN域在状态报告中的长度，确定第一剩余空口调度资源；
    响应于所述第一剩余空口调度资源大于或等于非确认序列号NACK_SN域在状态报告中的最小长度，根据所述第一剩余空口调度资源、所述接收窗口中空洞的顺序和各所述空洞在状态报告中的长度，确定第一待携带接收窗口信息；其中，各所述空洞在状态报告中的长度根据各所述空洞的类型确定；以及
    根据所述第一待携带接收窗口信息生成状态报告。
  4. 如权利要求3所述的方法，其中，所述根据所述第一剩余空口调度资源、所述接收窗口中空洞的顺序和各所述空洞在状态报告中的长度，确定第一待携带接收窗口信息，包括：
    按照所述接收窗口中空洞的顺序，依次对当前空洞在状态报告中的长度和当前空洞之前的全部空洞在状态报告中的长度进行累加，得到当前的第一长度，直到所述当前的第一长度大于当前的剩余空口调度资源为止，其中，当前的剩余空口调度资源根据所述第一剩余空口调度资源和前次累加的空洞在状态报告中的长度确定；以及
    根据当前空洞的类型确定空洞信息，并确定ACK_SN域信息。
  5. 如权利要求4所述的方法，其中，所述根据当前空洞的类型确定空洞信息，包括：
    在当前空洞的类型不是预设类型的空洞的情况下，确定停止累加的前一次累加操作所包含的第一空洞信息为所述空洞信息；
    在当前空洞的类型为预设类型的空洞的情况下，响应于所述当前的剩余空口调度资源大于或等于连续的RLC PDU报文类型的空洞在状态报告中的长度，且小于所述预设类型的空洞在状态报告中的长度，确定空洞信息，其中，所述空洞信息包括第二空洞信息和停止累加的前一次累加操作所包含的第一空洞信息，所述第二空洞信息包括当前空洞中连续的RLC PDU报文信息和当前空洞中RLC PDU报文分片所属报文的信息；并且
    其中，所述预设类型为所述包括连续的RLC PDU报文和分别位于所述连续的RLC PDU报文首尾的RLC PDU报文分片的组合。
  6. 如权利要求如权利要求4或5所述的方法，其中，所述确定ACK_SN域信息包括：
    在确定出所述空洞信息之后，根据所述空洞信息和所述接收窗口信息确定ACK_SN域信息。
  7. 如权利要求3至6中任一项所述的方法，其中，在确定第一剩余空口调度资源之后，所述方法还包括：
    响应于所述第一剩余空口调度资源小于所述NACK_SN域在状态报告中的最小长度，根据所述接收窗口信息确定第二待携带接收窗口信息，所述第二待携带接收窗口信息包括ACK_SN域信息但不包括空洞信息；以及
    根据所述第二待携带接收窗口信息生成状态报告。
  8. 一种状态报告生成装置，包括接收窗口信息确定模块、判断模块和状态报告生成模块，其中，
    所述接收窗口信息确定模块配置为确定接收窗口信息，所述接收窗口信息至少包括一个空洞信息；
    所述判断模块配置为判断空口调度资源是否大于或等于确认序列号ACK_SN域在状态报告中的长度；并且
    所述状态报告生成模块配置为响应于空口调度资源大于或等于ACK_SN域在状态报告中的长度，根据所述空口调度资源、所述ACK_SN域在状态报告中的长度和空洞的类型生成状态报告，以使所述状态报告的长度满足所述空口调度资源且所述状态报告携带所述接收窗口信息的最多内容。
  9. 一种计算机设备，包括：
    一个或多个处理器；以及
    存储装置，其上存储有一个或多个程序；
    当所述一个或多个程序被所述一个或多个处理器执行时，使得所述一个或多个处理器实现如权利要求1-7任一项所述的状态报告生成方法。
  10. 一种计算机可读介质，其上存储有计算机程序，其中，所述程序被执行时实现如权利要求1-7任一项所述的状态报告生成方法。
PCT/CN2023/088934 2022-04-18 2023-04-18 状态报告生成方法、装置、计算机设备及可读介质 WO2023202566A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202210404258.2 2022-04-18
CN202210404258.2A CN116963163A (zh) 2022-04-18 2022-04-18 状态报告生成方法、装置、计算机设备及可读介质

Publications (1)

Publication Number Publication Date
WO2023202566A1 true WO2023202566A1 (zh) 2023-10-26

Family

ID=88419198

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2023/088934 WO2023202566A1 (zh) 2022-04-18 2023-04-18 状态报告生成方法、装置、计算机设备及可读介质

Country Status (2)

Country Link
CN (1) CN116963163A (zh)
WO (1) WO2023202566A1 (zh)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102957522A (zh) * 2011-08-24 2013-03-06 中兴通讯股份有限公司 一种rlc am状态报告处理的方法和系统
US20190230667A1 (en) * 2016-11-04 2019-07-25 Panasonic Intellectual Property Corporation Of America Efficient multiplexing of control information in transport block
CN112637876A (zh) * 2020-12-30 2021-04-09 京信网络系统股份有限公司 一种状态报告的发送方法、装置、电子设备及介质
US20210314810A1 (en) * 2020-04-07 2021-10-07 Qualcomm Incorporated Radio link control (rlc) status reporting

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102957522A (zh) * 2011-08-24 2013-03-06 中兴通讯股份有限公司 一种rlc am状态报告处理的方法和系统
US20190230667A1 (en) * 2016-11-04 2019-07-25 Panasonic Intellectual Property Corporation Of America Efficient multiplexing of control information in transport block
US20210314810A1 (en) * 2020-04-07 2021-10-07 Qualcomm Incorporated Radio link control (rlc) status reporting
CN112637876A (zh) * 2020-12-30 2021-04-09 京信网络系统股份有限公司 一种状态报告的发送方法、装置、电子设备及介质

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ALCATEL-LUCENT: "Clarification on RLC Status Report", 3GPP DRAFT; R2-080926 RLC STATUS, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sorrento, Italy; 20080211 - 20080215, 4 February 2008 (2008-02-04), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050603544 *
SUNPLUS MMOBILE INC.: "Length of NACK_SN in RLC STATUS PDU", 3GPP DRAFT; R2-080401, 3RD GENERATION PARTNERSHIP PROJECT (3GPP), MOBILE COMPETENCE CENTRE ; 650, ROUTE DES LUCIOLES ; F-06921 SOPHIA-ANTIPOLIS CEDEX ; FRANCE, vol. RAN WG2, no. Sevilla, Spain; 20080108, 8 January 2008 (2008-01-08), Mobile Competence Centre ; 650, route des Lucioles ; F-06921 Sophia-Antipolis Cedex ; France , XP050138251 *

Also Published As

Publication number Publication date
CN116963163A (zh) 2023-10-27

Similar Documents

Publication Publication Date Title
JP6005710B2 (ja) 無線通信システムの状態情報送信方法及び受信装置
EP2238707B1 (en) Method of detecting and handling an endless rlc retransmission
CN103138905B (zh) Rlc数据包传输的确认方法及rlc am实体发送方
US8306061B2 (en) Method for retransmitting data unit using delivery status information
US9565007B2 (en) Method of receiving a point-to-multipoint service in a wireless communication system
JP5252331B2 (ja) メッセージ再送方法及び装置
US8493861B2 (en) Method and transmitting unit for reducing a risk of transmission stalling
US20070291646A1 (en) Retransmission control method and device
US20060245430A1 (en) Method and Apparatus of a Procedure for Receiving Window Size Reconfiguration in a Communication System
JP2007089177A (ja) 無線通信システムにおける状態報告信号の伝送速度を改善する方法及び装置
WO2009051386A2 (en) Method of performing arq procedure for transmitting high rate data
JP2013503505A (ja) 重複イベントベースのポーリングされた確認応答の移動局伝送を回避する方法および装置
US11258721B2 (en) Radio link control (RLC) acknowledged mode (AM) data reception
US7327694B2 (en) Adaptive radio link protocol (RLP) to improve performance of TCP in wireless environment for CDMAone and CDMA2000 systems
WO2023202566A1 (zh) 状态报告生成方法、装置、计算机设备及可读介质
US10849160B2 (en) Reinstating poll retransmission timer
US20220158771A1 (en) Method of enabling harq, network entity and computer program
CN114584263B (zh) 重发超限及双无条件下rlc确认模式增强方法及装置
CN115348335A (zh) 异构数据流的通用传输架构
WO2012100559A1 (zh) 一种减少状态报告长度的方法、系统及接收端
WO2012045243A1 (zh) 一种无线块的传输方法及系统

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: 23791221

Country of ref document: EP

Kind code of ref document: A1