WO2019192425A1 - 确认模式rlc实体及其发送/重传方法、通信设备 - Google Patents

确认模式rlc实体及其发送/重传方法、通信设备 Download PDF

Info

Publication number
WO2019192425A1
WO2019192425A1 PCT/CN2019/080807 CN2019080807W WO2019192425A1 WO 2019192425 A1 WO2019192425 A1 WO 2019192425A1 CN 2019080807 W CN2019080807 W CN 2019080807W WO 2019192425 A1 WO2019192425 A1 WO 2019192425A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc sdu
rlc
ack
state variable
sequence number
Prior art date
Application number
PCT/CN2019/080807
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 WO2019192425A1 publication Critical patent/WO2019192425A1/zh

Links

Images

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
    • 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
    • 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
    • H04L1/1621—Group acknowledgement, i.e. the acknowledgement message defining a range of identifiers, e.g. of sequence numbers
    • 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
    • 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/1809—Selective-repeat protocols

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and more particularly, to an acknowledgement mode (AM) RLC entity and a transmission method thereof, a retransmission method, and a communication device.
  • AM acknowledgement mode
  • NR New Radio
  • the radio state control RLC entity sender maintains the transmission state variable TX_Next for storing the acknowledgment mode data AMD protocol data unit PDU to be allocated to the next new generation.
  • the sequence number, TX_Next is initialized to 0 and is updated when the AM RLC entity constructs the sequence number TX_Next and contains the last segment of an RLC SDU or RLC SDU.
  • the transmission state variable TX_Next defines a different transmission state variable VT(S) than that defined in the existing LTE system (see 3GPP TS 36.322 for details), so that it is currently defined in the 3GPP TS 38.322 protocol in accordance with the inquiry process in the LTE system.
  • the inquiry process has a problem of inquiring that the transmission state variable POLL_SN does not match.
  • Solution 1 The query will send the state variable.
  • POLL_SN is set to the maximum sequence number of all AMD PDUs that have been queried in the AMD PDUs that have been submitted to the lower layer;
  • Solution 2 Set the polling state variable POLL_SN to TX_Next-1 and redefine the transmission state variable TX_Next only when the RLC PDU is delivered to Updated only when the lower layer.
  • Solution 2 conflicts with the definition of TX_Next that has been reached by 3GPP RAN2 and is therefore not adopted. If solution one is employed, the inquiry transmission state variable POLL_SN is set to the maximum sequence number of all AMD PDUs containing the inquiry that has been submitted to the lower layer, which may result in a retransmission delay of the partial RLC service data unit SDU.
  • the present disclosure is directed to solving the problems in the first solution.
  • the present disclosure provides an acknowledgement mode (AM) RLC entity capable of solving the above problem, a transmitting method thereof, a retransmission method, and a communication device.
  • AM acknowledgement mode
  • a method for transmitting an acknowledge mode RLC entity comprising: the acknowledge mode RLC entity transmitting an acknowledge mode data PDU including a query to a lower layer; the acknowledge mode RLC entity update querying a transmit state variable POLL_SN, the inquiry transmission state variable POLL_SN is set to a sequence number SN of an arbitrary acknowledgment mode data PDU that satisfies a predetermined condition, the predetermined condition is that the acknowledgment mode data PDU is an acknowledgment mode that has been sent to the lower layer
  • the acknowledgment mode data PDU containing the inquiry and having the largest sequence number in the data PDU is transmitted together to the acknowledgment mode data PDU of the lower layer.
  • the acknowledge mode data PDU sent together to the lower layer is specifically: simultaneously sent to the lower layer, or sent together to the lower layer, or multiplexed to a media access control PDU, or from The acknowledge mode data PDU transmitted in the same transmission opportunity indicated by the lower layer.
  • the acknowledgment mode data PDU of the segment is updated.
  • a retransmission method for an acknowledgment mode RLC entity comprising: the acknowledgment mode RLC entity receiving a status report or status PDU from a peer acknowledgment mode RLC entity; The status PDU, the acknowledge mode RLC entity performs the following operations: retransmitting the RLC SDU or RLC SDU segment that received the negative acknowledgement; or retransmitting the RLC SDU or RLC SDU segment that satisfies the predetermined condition.
  • the negative acknowledged RLC SDU or RLC SDU segment is received by: a status PDU from the peer to peer acknowledgement mode RLC entity; or a certain RLC SDU or RLC SDU segment
  • the sequence number SN satisfies between the acknowledgment sequence number ACK_SN and the transmission state variable TX_Next, and the certain RLC SDU or RLC SDU segment has been sent before the most recent or newly transmitted acknowledgment mode data PDU or RLC SDU containing the query
  • the sequence number SN of the certain RLC SDU or RLC SDU segment satisfies between the interrogation transmission state variable POLL_SN and the transmission state variable TX_Next, and the certain RLC SDU or RLC SDU segment is in the nearest or
  • the newly transmitted acknowledgment mode data PDU or RLC SDU containing the inquiry has been previously transmitted; or the sequence number SN of the certain RLC SDU or RLC SDU segment satisfies between the acknowledgment state variable TX_Next_Ack and the transmission state variable T
  • the RLC SDU or RLC SDU segment of the predetermined condition is specifically: the status PDU of the peer-to-peer acknowledgment mode RLC entity or the status report negative acknowledgment, and the corresponding RLC SDU
  • the PDU or the status report does not include a positive acknowledgment and/or negative acknowledgment of the RLC SDU or RLC SDU segment that was sent before the most recent or most recently sent acknowledgment mode data PDU or RLC SDU containing the challenge; or Or the most recently sent acknowledgment mode data PDU containing the query or the RLC SDU or RLC SDU segment that was previously transmitted by the RLC SDU, and the sequence number SN of the RLC SDU or RLC S
  • an acknowledge mode RLC entity comprising: a transmitting end and a receiving end, the transmitting end performing the transmitting method according to the above first aspect and/or the retransmission method according to the second aspect described above .
  • a communication device comprising: a processor; and a memory storing instructions; wherein the instructions, when executed by the processor, perform a transmitting method according to the above first aspect and / or the retransmission method according to the second aspect above.
  • the acknowledgement mode (AM) RLC entity and its transmission method, retransmission method, and communication device solve the problem of setting the inquiry transmission state variable POLL_SN to the maximum sequence of all AMD PDUs containing the query that have been submitted to the lower layer.
  • the number may cause a problem of retransmission delay of some RLC service data unit SDUs, which improves transmission efficiency and improves user experience.
  • FIG. 1 is a schematic flow chart showing a method of transmitting an AM RLC entity according to an embodiment of the present disclosure.
  • FIG. 2 is a schematic flow chart showing a retransmission method of an AM RLC entity according to an embodiment of the present disclosure.
  • FIG. 3 schematically shows a schematic block diagram of an AM RLC entity involved in an embodiment of the present disclosure.
  • FIG. 4 is a block diagram schematically showing a schematic configuration of a communication device according to an embodiment of the present disclosure.
  • PDCP Packet Data Convergence Protocol, Packet Data Convergence Protocol.
  • RLC Radio Link Control, radio link control.
  • the RLC entity may be an Unacknowledged Mode UM RLC entity or an Acknowledged Mode AM RLC entity.
  • the segment of the RLC SDU or the RLC SDU adds an RLC header to obtain an AM Data PDU (AMD PDU).
  • AMD PDU AM Data PDU
  • UM RLC a segment of the RLC SDU or RLC SDU adds a RMC header to obtain a UM Data PDU (UMD PDU).
  • the RLC Data PDU may be an AMD PDU or a UMD PDU, but does not include an RLC Control PDU.
  • MAC Medium Access Control, media access control.
  • PDU Protocol Data Unit, protocol data unit.
  • SDU Service Data Unit, service data unit.
  • data received from the upper layer or sent to the upper layer is referred to as an SDU
  • data to be delivered to or received from the lower layer is referred to as a PDU
  • the data received by the RLC entity from the upper layer (ie, the PDCP entity) or the data sent to the upper layer is called the RLC SDU
  • the data received by the RLC entity from the lower layer (ie, the MAC entity) or the data submitted to the lower layer is called the RLC PDU.
  • Segmentation Segment, part of the RLC SDU.
  • STATUS PDU A status PDU, which is used by the AM RLC entity receiving end to notify the peer AM RLC entity about the successful reception of the RLC data PDU and the AM RLC entity receiving end detecting the lost RLC data PDU.
  • TX_Next is used to hold the sequence number that will be assigned to the next newly generated AMD PDU.
  • the inquiry transmission state variable POLL_SN:POLL_SN can be used to hold the maximum sequence number of the AMD PDU in which the poll bit is set to "1" in the AMD PDU that has been submitted to the lower layer; POLL_SN is initialized to 0.
  • ACK_SN The definition is the same as defined in the latest version of 3GPP TS 38.322, that is, the ACK_SN field is used to indicate the next unreceived RLC SDU, which is not in the STATUS PDU. Reported as a missing RLC SDU.
  • the NACK_SN field is used to indicate that the AM RLC entity receiving end detects the missing sequence number SN of the RLC SDU (or RLC SDU segment), and the SOstart field (together with the SOend field) is used to indicate that the AM RLC entity receiving end detects the loss.
  • the SOstart field indicates the location of the first byte of a part of the RLC SDU in the original RLC SDU, the first of the original RLC SDU
  • the SOend field indicates the location of the last byte of a part of the RLC SDU in the original RLC SDU, and the first byte of the original RLC SDU uses the SOend field.
  • the NACK range field is the number of consecutive RLC SDUs that are lost from the NACK_SN (including NACK_SN) (This NACK range field is the number of consecutively lost RLC S
  • TX_Next_Ack is used to hold the next RLC SDU for which a positive acknowledgment is to be received in-sequence The lower edge of the send window.
  • TX_Next_Ack is initialized to 0 and the value of TX_Next_Ack is updated when the AM RLC entity receives a positive acknowledgment of the RLC SDU with sequence number TX_Next_Ack.
  • the acknowledge mode radio link control AM RLC entity submits an acknowledge mode data protocol data unit AMD PDU to the lower layer, the AMD PDU including a poll or inquiry bit set to "1" ".
  • the acknowledgment mode radio link control AM RLC entity submits an acknowledgment mode data protocol data unit AMD PDU containing the challenge to the lower layer.
  • step S111 and step S112 enclosed by a broken line frame are optional steps, that is, unnecessary steps.
  • step S111 the process proceeds to step S112.
  • step S112 the transmission state variable TX_Next is updated.
  • the Transmit State Variable TX_Next holds the sequence number that will be assigned to the next newly generated AMD PDU.
  • step S111 the transmission state variable TX_Next is updated.
  • the transmit state variable TX_Next holds the sequence number that will be assigned to the next newly generated AMD PDU.
  • the TX_Next is updated when the AMD PDU of the segment).
  • step S111 if it is not necessary (NO in step S111), the process proceeds to step S120.
  • the AM RLC entity updates the value of the transmit status variable POLL_SN, and the POLL_SN is initialized to zero.
  • the POLL_SN is set to the maximum sequence number of the AMD PDU containing the inquiry that has been submitted to the underlying AMD PDU.
  • the POLL_SN is set to a sequence number of any AMD PDU that satisfies the following conditions: the AMD PDU is submitted to the lower layer (or simultaneously with the AMD PDU that has been submitted to the underlying AMD PDU and contains the largest sequence number) The lower layer or together are sent or multiplexed into one MAC PDU or transmitted in the same transmission opportunity indicated from the lower layer or transmitted in one transport block).
  • POLL_SN is set to TX_Next-1 (or TX_Next).
  • step S210 the acknowledgment mode radio link control AM RLC entity sender receives a status report (or status PDU) from its peer AM RLC entity (ie, the AM RLC entity receiver).
  • step S220 the AM RLC entity sender performs one of the following two operations:
  • Operation 1 The RLC SDU or RLC SDU segment that receives the negative acknowledgement is used for retransmission. In other words, it is considered that the RLC SDU or RLC SDU segment that received the negative acknowledgment needs to be retransmitted.
  • the transmitting end of the AM RLC entity may receive a negative acknowledgement of the RLC SDU or RLC SDU segment by at least one of the following ways:
  • Manner 1 Status PDU from its peer AM RLC entity.
  • the AM RLC entity sender considers that the negative acknowledgment of the RLC SDU or RLC SDU segment is received or the RLC SDU or RLC SDU segment is negatively acknowledged.
  • the condition of the third mode further includes: a positive acknowledgment and/or a negative acknowledgment of the RLC SDU or RLC SDU segment not included in the status PDU or the status report received by the transmitting
  • Manner 5 RLC SDUs that have been sent (or submitted to the lower layer) before (or before being submitted to the lower layer) the most recent (or latest) sent (or submitted to the lower layer) AMD PDU (or RLC SDU) containing the query
  • the RLC SDU segment if the received status PDU (or status report) does not include a positive acknowledgment and/or a negative acknowledgment of the RLC SDU or RLC SDU segment, the AM RLC entity sender considers that the RLC SDU is received. Or a negative acknowledgement of the RLC SDU segment or the RLC SDU or RLC SDU segment is negatively acknowledged.
  • the TX_Next involved in the second to fourth modes may be as defined in step 110, and the POLL_SN may be updated according to the embodiment defined in step 120.
  • Operation 2 The RLC SDU or RLC SDU segment that the sender of the AM RLC entity considers to satisfy one of the following conditions needs to be retransmitted (in other words, the AM RLC entity sender uses the RLC SDU or RLC SDU segment that satisfies one of the following conditions for heavy pass):
  • Condition 3 When receiving a status PDU (or status report) from its peer AM RLC entity, it does not include an AMD PDU (or RLC SDU) containing the query that was sent (or submitted to the lower layer) in the most recent (or latest) state.
  • the negative acknowledgement and/or positive acknowledgment of the RLC SDU or RLC SDU segment that was sent (or before the lower layer) has been sent (or submitted to the lower layer) then the AM RLC entity sender segments the RLC SDU or RLC SDU (or the positive acknowledgement and/or negative acknowledgement RLC SDU or RLC SDU segment is not received) for retransmission; in other words, the AM RLC entity sender considers the RLC SDU or RLC SDU segment (or the unreceived Re-transmission is required to positively acknowledge and/or negatively acknowledge RLC SDU or RLC SDU segments.
  • Condition 4 When receiving a status PDU (or status report) from its peer AM RLC entity, it does not include a recent (or latest) transmission in the retransmission buffer (or waiting for acknowledgment) (or delivery to the lower layer) A negative acknowledgment and/or positive acknowledgment of the RLC SDU or RLC SDU segment that has been sent (or submitted to the lower layer) before (or before the lower layer) the AMD PDU (or RLC SDU) of the inquiry is sent by the AM RLC entity Ending the RLC SDU or RLC SDU segment (or the unacknowledged positive acknowledgement and/or negative acknowledgement RLC SDU or RLC SDU segment) for retransmission; in other words, the AM RLC entity sender considers the RLC SDU Or RLC SDU segmentation (or the failure to receive a positive acknowledgment and/or negative acknowledgment RLC SDU or RLC SDU segment) requires retransmission.
  • Condition 5 When receiving a status PDU (or status report) from its peer AM RLC entity, it does not include an AMD PDU (or RLC SDU) containing the query that was recently (or latest) transmitted (or submitted to the lower layer). a positive acknowledgment and/or negative acknowledgment of the RLC SDU or RLC SDU segment that was sent (or before the lower layer) has been sent (or to the lower layer) if the RLC SDU or RLC SDU segment (or not received affirmative)
  • the TX_Next involved in the conditions 2 to 5 may be as defined in step 110, and the POLL_SN may be updated according to the embodiment defined in step 120.
  • condition two to five is determined when a status PDU (or status report) from its peer AM RLC entity is received.
  • the calculation of the state variable can be performed in the following manner: If the sequence number is identified by, for example, 12 bits, the sequence number ranges from 0 to 4095. Then, the state variable takes a value equal to the remainder of the calculated value and the modulo operation of 4096. In addition, if the serial number is identified by 18 bits, the state variable ranges from 0 to 262143. Then, the state variable takes a value equal to the remainder of the calculated value and the modulo operation of 262144.
  • setting the state variable to the value of the serial number or the serial number described in the present disclosure means setting the value of the state variable to the value of the serial number or the serial number.
  • FIG. 3 shows a schematic block diagram of an AM RLC entity in accordance with an embodiment of the present disclosure.
  • the AM RLC entity 400 includes at least a receiving end 401 and a transmitting end 402. Moreover, the AM RLC entity 400 can be included, for example, in both the client device and the base station device, and can be controlled by the processor to receive the terminal 401 to perform the AM RLC described in the above-described FIG. 1 and/or FIG. 2 of the present disclosure. The method of sending and/or retransmission of the entity.
  • FIG. 4 shows a block diagram of a schematic structure of a communication device according to an embodiment of the present disclosure.
  • the communication device 500 includes at least a processor 501 and a memory 502.
  • Processor 501 can include, for example, a microprocessor, a microcontroller, an embedded processor, and the like.
  • Memory 502 can include, for example, volatile memory (such as random access memory RAM), hard disk drive (HDD), non-volatile memory (such as flash memory), or other memory systems, and the like.
  • Program instructions are stored on the memory 502. The instructions, when executed by the processor 501, may perform the transmission method and/or retransmission method of the AM RLC entity described above with respect to FIG. 1 and/or FIG. 2 of the present disclosure.
  • the embodiments of the present disclosure may be performed at the user equipment UE or at the base station. If the transmitting end of the AM RLC entity is in the UE, its peer AM RLC entity (ie, the AM RLC entity receiving end) is in the base station; correspondingly, if the transmitting end of the AM RLC entity is in the base station, its peer AM RLC entity ( That is, the AM RLC entity receiving end) is in the UE.
  • the program running on the device may be a program that causes a computer to implement the functions of the embodiments of the present disclosure by controlling a central processing unit (CPU).
  • the program or information processed by the program may be temporarily stored in a volatile memory (such as a random access memory RAM), a hard disk drive (HDD), a non-volatile memory (such as a flash memory), or other memory system.
  • a volatile memory such as a random access memory RAM
  • HDD hard disk drive
  • non-volatile memory such as a flash memory
  • a program for realizing the functions of the embodiments of the present disclosure may be recorded on a computer readable recording medium.
  • the corresponding functions can be realized by causing a computer system to read programs recorded on the recording medium and execute the programs.
  • the so-called "computer system” herein may be a computer system embedded in the device, and may include an operating system or hardware (such as a peripheral device).
  • the "computer readable recording medium” may be a semiconductor recording medium, an optical recording medium, a magnetic recording medium, a recording medium of a short-term dynamic storage program, or any other recording medium readable by a computer.
  • circuitry e.g., monolithic or multi-chip integrated circuits.
  • Circuitry designed to perform the functions described in this specification can include general purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field programmable gate arrays (FPGAs), or other programmable logic devices, discrete Gate or transistor logic, discrete hardware components, or any combination of the above.
  • DSPs digital signal processors
  • ASICs application specific integrated circuits
  • FPGAs field programmable gate arrays
  • a general purpose processor may be a microprocessor or any existing processor, controller, microcontroller, or state machine.
  • the above circuit may be a digital circuit or an analog circuit.
  • One or more embodiments of the present disclosure may also be implemented using these new integrated circuit technologies in the context of new integrated circuit technologies that replace existing integrated circuits due to advances in semiconductor technology.
  • present disclosure is not limited to the above embodiment. Although various examples of the embodiments have been described, the present disclosure is not limited thereto.
  • Fixed or non-mobile electronic devices installed indoors or outdoors can be used as terminal devices or communication devices such as AV devices, kitchen devices, cleaning devices, air conditioners, office equipment, vending machines, and other home appliances.

Landscapes

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

Abstract

本公开提供一种确认模式RLC实体及其发送/重传方法、及通信设备。所述确认模式RLC实体的发送方法包括：所述确认模式RLC实体向下层发送包含询问的确认模式数据PDU；所述确认模式RLC实体更新询问发送状态变量POLL_SN，将所述询问发送状态变量POLL_SN设置为满足预定条件的任意确认模式数据PDU的序列号SN，所述预定条件为：所述任意确认模式数据PDU是与已发送给所述下层的确认模式数据PDU中包含询问且序列号最大的确认模式数据PDU一起发送给所述下层的确认模式数据PDU。

Description

确认模式RLC实体及其发送/重传方法、通信设备 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及一种确认模式(AM)RLC实体及其发送方法、重传方法、以及通信设备。
背景技术
2016年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#71次全会上，提出了一个关于5G技术标准的新的研究项目(参见非专利文献：RP-160671：New SID Proposal：Study on New Radio Access Technology)。该研究项目的目的是开发一个新的无线(New Radio：NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景：增强的移动宽带通信、大规模机器类通信和超可靠低延迟通信。
在3GPP RAN2#100次会议上，达成NR中的确认模式AM无线链路控制RLC实体发送端维护的发送状态变量TX_Next用于保存将分配给下一个新产生的确认模式数据AMD协议数据单元PDU的序列号，TX_Next初始化为0且在AM RLC实体构建序列号为TX_Next且包含一个RLC SDU或RLC SDU的最后一个分段时更新。所述发送状态变量TX_Next定义不同于现有LTE系统中定义的发送状态变量VT(S)(具体见3GPP TS36.322)，使得目前在3GPP TS38.322协议中仿照LTE系统中的询问过程所定义的询问过程存在询问发送状态变量POLL_SN不匹配的问题，具体问题描述可参见3GPP提案R2-1800563和R2-1803004。在2018年2月召开的3GPP RAN2#101次会议上，讨论了所述问题的解决方案，目前主要有两种解决方案(具体参见3GPP提案RAN2-1803870)：解决方案一、将询问发送状态变量POLL_SN设置为所有已递交给下层的AMD PDU中包含询问的AMD PDU的最大序列号；解决方案二：将询问发送状态变量POLL_SN设置TX_Next-1且重新定义发送状态变量TX_Next只有在将RLC PDU递交给下层时才更新。解决方案二与3GPP RAN2已达成的TX_Next的定义存在冲突，故不 被采纳。如果采用解决方案一，将询问发送状态变量POLL_SN设置为所有已递交给下层的包含询问的AMD PDU的最大序列号，这将可能导致部分RLC服务数据单元SDU发生重传延迟。本公开致力于解决所述解决方案一中存在的问题。
发明内容
本公开提供能够解决上述问题的确认模式(AM)RLC实体及其发送方法、重传方法、以及通信设备。
根据本发明的第一方面，提供了一种确认模式RLC实体的发送方法，包括：所述确认模式RLC实体向下层发送包含询问的确认模式数据PDU；所述确认模式RLC实体更新询问发送状态变量POLL_SN，将所述询问发送状态变量POLL_SN设置为满足预定条件的任意确认模式数据PDU的序列号SN，所述预定条件为：所述任意确认模式数据PDU是与已发送给所述下层的确认模式数据PDU中包含询问且序列号最大的确认模式数据PDU一起发送给所述下层的确认模式数据PDU。
在上述发送方法中，所述一起发送给所述下层的确认模式数据PDU具体为：同时发送给所述下层、或一起发送给所述下层、或复用到一个媒体访问控制PDU、或在来自下层指示的同一传输时机中传输的确认模式数据PDU。
在上述发送方法中，还包括：在必要情况下更新发送状态变量TX_Next，所述必要情况具体为：所述确认模式RLC实体构建一个序列号SN＝TX_Next、且其中包含一个RLC SDU或RLC SDU的最后一个分段的确认模式数据PDU的情况；或者所述确认模式RLC实体发送或传输或者向所述下层发送或传输一个序列号SN＝TX_Next、且其中包含一个RLC SDU或RLC SDU的最后一个分段的确认模式数据PDU的情况。
根据本公开的第二方面，提供了一种确认模式RLC实体的重传方法，包括：所述确认模式RLC实体接收来自对等确认模式RLC实体的状态报告或状态PDU；根据所述状态报告或所述状态PDU，所述确认模式RLC实体执行下列操作：将接收到否定确认的RLC SDU或RLC SDU分段进行重传；或者将满足预定条件的RLC SDU或RLC SDU分段进行重传。
在上述重传方法中，所述否定确认的RLC SDU或RLC SDU分段是通 过如下方式接收到的：来自所述对等确认模式RLC实体的状态PDU；或者某个RLC SDU或RLC SDU分段的序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送；或者所述某个RLC SDU或RLC SDU分段的所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送；或者所述某个RLC SDU或RLC SDU分段的所述序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送且所述状态报告或所述状态PDU中不包含肯定确认和/或其否定确认。
在上述重传方法中，所述序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间具体为：ACK_SN＜SN＜TX_Next；或ACK_SN＜SN＜＝TX_Next-1；或ACK_SN＜＝SN＜TX_Next；或ACK_SN＜＝SN＜＝TX_Next-1，所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间具体为：POLL_SN＜SN＜TX_Next；或POLL_SN＜SN＜＝TX_Next-1；或POLL_SN＜＝SN＜TX_Next；或POLL_SN＜＝SN＜＝TX_Next-1，所述序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间具体为：TX_Next_Ack＜＝SN＜TX_Next；或TX_Next_Ack＜SN＜＝TX_Next-1；或TX_Next_Ack＜＝SN＜＝TX_Next-1；或TX_Next_Ack＜SN＜TX_Next。
在上述重传方法中，所述预定条件的RLC SDU或RLC SDU分段具体为：被所述对等确认模式RLC实体的所述状态PDU或所述状态报告否定确认、并且所对应的RLC SDU的序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间即TX_Next_Ack＜＝SN＜TX_Next的RLC SDU或RLC SDU分段；或者接收到来自所述对等确认模式RLC实体的所述状态PDU或所述状态报告中不包括某个在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送的RLC SDU或RLC SDU分段的肯定确认和/或否定确认；或者在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送的RLC SDU或RLC  SDU分段、并且该RLC SDU或RLC SDU分段的序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间、或者满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间。
在上述重传方法中，所述序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间具体为：ACK_SN＜SN＜TX_Next；或ACK_SN＜SN＜＝TX_Next-1；或ACK_SN＜＝SN＜TX_Next；或ACK_SN＜＝SN＜＝TX_Next-1，所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间具体为：POLL_SN＜SN＜＝TX_Next-1；或POLL_SN＜SN＜TX_Next；或POLL_SN＜＝SN＜TX_Next；或POLL_SN＜＝SN＜＝TX_Next-1。
根据本公开的第三方面，提供了一种确认模式RLC实体，包括：发送端和接收端，所述发送端执行根据上述第一方面的发送方法和/或根据上述第二方面的重传方法。
根据本公开的第四方面，提供了一种通信设备，包括：处理器；以及存储器，存储有指令；其中，所述指令在由所述处理器运行时执行根据上述第一方面的发送方法和/或根据上述第二方面的重传方法。
根据本发明所涉及的确认模式(AM)RLC实体及其发送方法、重传方法、以及通信设备，解决了将询问发送状态变量POLL_SN设置为所有已递交给下层的包含询问的AMD PDU的最大序列号时可能导致部分RLC服务数据单元SDU发生重传延迟的问题，提高了传输效率，从而提高了用户体验。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示意性示出了本公开的实施例涉及的AM RLC实体的发送方法的简要流程图。
图2示意性示出了本公开的实施例涉及的AM RLC实体的重传方法的简要流程图。
图3示意性示出了本公开的实施例涉及的AM RLC实体的简要结构框图。
图4示意性示出了本公开的实施例涉及的通信设备的简要结构框图。
需要注意的是，附图不一定按比例绘制，重点在于示出本文公开的技术的原理。另外，为了清楚起见，贯穿附图中的相似的附图标记指代相似的元素。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。
首先介绍本公开涉及的部分术语、变量和域(filed)。如未特别说明，本公开涉及的术语或变量或域均采用此处定义。此外，在本公开中未定义的术语或变量或域，其定义与3GPP TS38.322最新版本中的定义相同。
PDCP：Packet Data Convergence Protocol，分组数据汇聚协议。
RLC：Radio Link Control，无线链路控制。RLC实体可以是非确认模式(Unacknowledged Mode)UM RLC实体或确认模式(Acknowledged Mode)AM RLC实体。
在AM RLC实体中，RLC SDU或RLC SDU的分段增加RLC头部后得到AM数据PDU(AMD PDU)。在UM RLC实体中，RLC SDU或RLC SDU的分段增加RLC头部后得到UM数据PDU(UMD PDU)。RLC数据PDU可以是AMD PDU或UMD PDU，但不包括RLC控制PDU。
MAC：Medium Access Control，媒体访问控制。
PDU：Protocol Data Unit，协议数据单元。
SDU：Service Data Unit，服务数据单元。
在本公开中，将从上层接收或发往上层的数据称为SDU，将递交给下层或从下层接收的数据称为PDU。例如，RLC实体从上层(即PDCP实体)接收的数据或发往上层的数据称为RLC SDU，RLC实体从下层(即MAC实体)接收到的数据或递交给下层的数据称为RLC PDU。
分段：Segment，RLC SDU的一部分。
SN：Sequence Number，序列号。
STATUS PDU：状态PDU，是AM RLC实体接收端用于通知对等(peer)AM RLC实体关于成功接收的RLC数据PDU和AM RLC实体接收端检测到丢失的RLC数据PDU。
发送状态变量TX_Next：TX_Next用于保存(holds)将为下一个新产生的AMD PDU分配的序列号。TX_Next初始化为0，且当AM RLC实体构建一个序列号SN＝TX_Next且其中包含一个RLC SDU或RLC SDU的最后一个分段的AMD PDU时更新所述TX_Next。
询问发送状态变量POLL_SN：POLL_SN可以用于保存已递交给下层的AMD PDU中询问(poll)比特设置为“1”的AMD PDU的最大序列号；POLL_SN初始化为0。
确认SN(Acknowledgement SN)ACK_SN：其定义与3GPP TS38.322最新版本中的定义相同，即ACK_SN域用于指示下一个未接收到的RLC SDU，所述RLC SDU是未在状态(STATUS)PDU中报告为丢失的RLC SDU。
当AM RLC实体发送端接收到一个STATUS PDU时，其认为序列号小于ACK_SN的所有RLC SDU已被其对等(peer)AMRLC实体接收，但不包括在状态PDU中由NACK_SN中指示的RLC SDU、在状态PDU中由NACK_SN、SOstart和SOend指示的RLC SDU的一部分、在状态PDU中由NACK_SN和NACK_range指示的RLC SDU和在状态PDU中由NACK_SN、NACK range、SOstart和SOend指示的RLC SDU的一部分(it interprets that all RLC SDUs up to but not including the RLC SDU with SN＝ACK_SN have been received by its peer AM RLC entity，excluding those RLC SDUs indicated in the S TATUS PDU with NACK_SN，portions of RLC SDUs indicated in the STATUS PDU with NACK_SN，SOstart and SOend，RLC SDUs indicated in the STATUS PDU with NACK_SN and NACK_range，and portions of RLC SDUs indicated in the STATUS PDU with NACK_SN，NACK range，SOstart and SOend)。其中，NACK_SN域用于指示AM RLC实体接收端检测到丢失的RLC SDU(或RLC SDU分段)的序列号SN，SOstart域(和SOend域一起)用于指示AM RLC实体接收端检测到丢失的且序列号SN＝NACK_SN(SOstart对应的NACK_SN)的RLC SDU的一部分；进一步的，SOstart域指示所述RLC SDU的一部分的第一字节在原RLC SDU中的位置， 所述原RLC SDU的第一字节用SOstart域取值为″0000000000000000″表示，即从0开始计数；当E3为0时，SOend域(和SOstart域一起)用于指示AM RLC实体接收端检测到丢失的且序列号SN＝NACK_SN(SOend对应的NACK_SN)的RLC SDU的一部分，进一步的，SOend域指示所述RLC SDU的一部分的最后一个字节在原RLC SDU中的位置，所述原RLC SDU的第一字节用SOend域取值为″0000000000000000″表示；当E3为1时，SOend域用于指示AM RLC实体接收端检测到丢失的且序列号SN＝NACK_SN+NACK范围-1(SOend对应的NACK_SN)的RLC SDU的一部分，更进一步的，SOend域指示所述RLC SDU的一部分的最后一个字节在原RLC SDU中的位置；E3域指示是否有连续未收到的RLC SDU的信息(whether or not information about a continous sequence of RLC SDUs that have not been received follows)。NACK范围(range)域是从NACK_SN开始(包括NACK_SN)丢失的连续RLC SDU的数量(This NACK range field is the number of consecutively lost RLC SDUs starting from and including NACK_SN)。
确认状态变量TX_Next_Ack：TX_Next_Ack用于保存下一个应该按序接收到肯定确认的RLC SDU的序列号(holds the value ofthe SN ofthe next RLC SDU for which a positive acknowledgment is to be received in-sequence)，其作为发送窗的下界(lower edge)。TX_Next_Ack初始化为0且当AM RLC实体接收到序列号为TX_Next_Ack的RLC SDU的肯定确认时更新TX_Next_Ack的值。
下面，参照附图1来描述AM RLC实体发送端发送包含询问的AMD PDU的操作的实施例。
如图1所示，在步骤S110中，确认模式无线链路控制AM RLC实体向下层递交一个确认模式数据协议数据单元AMD PDU，该AMD PDU包括一个询问(poll)或询问比特被置为“1”。换言之，确认模式无线链路控制AM RLC实体向下层递交一个包含询问的确认模式数据协议数据单元AMD PDU。
这里，应注意：以虚线框围起的步骤S111和步骤S112是可选步骤，即并非必须的步骤。
可选的，如有必要(步骤S111为“是”)，则进入步骤S112。在步骤S112中，更新发送状态变量TX_Next。所述发送状态变量TX_Next保存将 为下一个新产生的AMD PDU分配的序列号。TX_Next初始化为0，且当AM RLC实体构建一个序列号SN＝TX_Next且其中包含一个RLC SDU或RLC SDU的最后一个分段(segment)的AMD PDU时更新所述TX_Next。
可选的，如有必要(步骤S111为“是”)，则进入步骤S112。在步骤S112中，更新发送状态变量TX_Next。所述发送状态变量TX_Next保存将为下一个新产生的AMD PDU分配的序列号。TX_Next初始化为0，且当AM RLC实体发送或传输或向下层发送或向下层传输一个序列号SN＝TX_Next且其中包含一个RLC SDU或RLC SDU的最后一个分段(segment)(或第一个分段)的AMD PDU时更新所述TX_Next。
可选的，如无必要(步骤S111为“否”)，则进入步骤S120。
在步骤S120中，AM RLC实体更新询问发送状态变量POLL_SN的值，POLL_SN初始化为0。优选的，将POLL_SN设置为已递交给下层的AMD PDU中的包含询问的AMD PDU的最大序列号。备选的，将POLL_SN设置为满足以下条件的任意AMD PDU的序列号：所述AMD PDU是与已递交给下层AMD PDU中包含询问且序列号最大的AMD PDU一起递交给下层的(或同时递交给下层或一起发送的或复用到一个MAC PDU中或在来自下层指示的同一传输机会中传输的或在一个传输块中传输)。备选的，POLL_SN设置为TX_Next-1(或TX_Next)。
下面，参照附图2来描述AM RLC实体发送端接收到状态报告或状态PDU时执行的操作的实施例。
如图2所示，在步骤S210中，确认模式无线链路控制AM RLC实体发送端接收来自其对等AM RLC实体(即AM RLC实体接收端)的状态报告(或状态PDU)。
在步骤S220中，AM RLC实体发送端执行以下两种操作之一：
操作一：将接收到否定确认(negative acknowledgement)的RLC SDU或RLC SDU分段用于重传。换言之，认为接收到否定确认的RLC SDU或RLC SDU分段需要重传。AM RLC实体的发送端可以通过以下几种方式中的至少一种来接收到RLC SDU或RLC SDU分段的否定确认：
方式一：来自其对等AM RLC实体的状态PDU。
方式二：如果某个RLC SDU或RLC SDU分段的序列号SN满足ACK_SN＜SN＜TX_Next(备选的，ACK_SN＜SN＜＝TX_Next；备选的， ACK_SN＜＝SN＜TX_Next；备选的，ACK_SN＜SN＜＝TX_Next-1；备选的，ACK_SN＜＝SN＜＝TX_Next-1)且所述RLC SDU或RLC SDU分段在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或已递交给下层)，则AM RLC实体发送端认为接收到了所述RLC SDU或RLC SDU分段的否定确认或所述RLC SDU或RLC SDU分段被否定确认。
方式三，如果某个RLC SDU或RLC SDU分段的序列号SN满足POLL_SN＜SN＜TX_Next(备选的，POLL_SN＜SN＜＝TX_Next-1；备选的，POLL_SN＜＝SN＜TX_Next；备选的，POLL_SN＜＝SN＜＝TX_Next-1)且所述RLC SDU或RLC SDU分段在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)，则AM RLC实体发送端认为接收到了所述RLC SDU或RLC SDU分段的否定确认或所述RLC SDU或RLC SDU分段被否定确认。可选的，方式三的条件还包括：AM RLC实体发送端接收到的状态PDU或状态报告中不包括所述RLC SDU或RLC SDU分段的肯定确认和/或否定确认。
方式四，如果某个RLC SDU或RLC SDU分段的序列号SN满足TX_Next_Ack＜＝SN＜TX_Next(备选的，TX_Next_Ack＜SN＜＝TX_Next-1；备选的，TX_Next_Ack＜＝SN＜＝TX_Next-1；备选的，TX_Next_Ack＜SN＜TX_Next)且所述RLC SDU或RLC SDU分段在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)且AM RLC实体发送端接收到的状态PDU或状态报告中不包括所述RLC SDU或RLC SDU分段的肯定确认和/或否定确认，则AM RLC实体发送端认为接收到了所述RLC SDU或RLC SDU分段的否定确认或所述RLC SDU或RLC SDU分段被否定确认。
方式五：对于在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或已递交给下层)的RLC SDU或RLC SDU分段，如果接收到的状态PDU(或状态报告)中不包括所述RLC SDU或RLC SDU分段的肯定确认和/或否定确认，则AM RLC实体发送端认为接收到了所述RLC SDU或RLC SDU分段的否定确认或所述RLC SDU或RLC SDU分段被否定确认。
可选的，方式二～四中所涉及的TX_Next可以按照步骤110中的定义， POLL_SN可以按照步骤120中定义的实施例进行更新。
操作二：AM RLC实体发送端认为满足以下条件之一的RLC SDU或RLC SDU分段需要重传(换言之，AM RLC实体发送端将满足以下条件之一的RLC SDU或RLC SDU分段用于重传)：
条件一：当一个RLC SDU或RLC SDU分段被来自对等AM RLC实体的状态PDU(或状态报告)否定确认时，如果其对应的RLC SDU序列号SN满足TX_Next_Ack＜＝SN＜TX_Next，则AM RLC实体发送端将所述RLC SDU或RLC SDU分段(或所述接收到否定确认RLC SDU或RLC SDU分段)用于重传；换言之，AM RLC实体发送端认为所述RLC SDU或RLC SDU分段(或所述接收到否定确认RLC SDU或RLC SDU分段)需要重传。
条件二：在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)的RLC SDU或RLC SDU分段，如果所述RLC SDU或RLC SDU分段(或者未收到肯定确认和/或否定确认的RLC SDU或RLC SDU分段)的序列号SN满足ACK_SN＜SN＜TX_Next(备选的，ACK_SN＜SN＜＝TX_Next-1；备选的，ACK_SN＜＝SN＜TX_Next；备选的，ACK_SN＜＝SN＜＝TX_Next-1；备选的，POLL_SN＜SN＜＝TX_Next-1；备选的，POLL_SN＜SN＜TX_Next；备选的，POLL_SN＜＝SN＜TX_Next；备选的，POLL_SN＜SN＜＝TX_Next；备选的，POLL_SN＜＝SN＜＝Tx_Next-1)，则AM RLC实体发送端将所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)用于重传；换言之，AM RLC实体发送端认为所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)需要重传。
条件三：当接收到来自其对等AM RLC实体的状态PDU(或状态报告)中不包括某个在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)的RLC SDU或RLC SDU分段的否定确认和/或肯定确认，则AM RLC实体发送端将所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)用于重传；换言之，AM RLC实体发送端认为所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)需要重传。
条件四：当接收到来自其对等AM RLC实体的状态PDU(或状态报告)中不包括重传缓存区中(或等待确认的)某个在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)的RLC SDU或RLC SDU分段的否定确认和/或肯定确认，则AM RLC实体发送端将所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)用于重传；换言之，AM RLC实体发送端认为所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)需要重传。
条件五：当接收到来自其对等AM RLC实体的状态PDU(或状态报告)中不包括某个在最近(或最新)发送(或递交给下层的)的包含询问的AMD PDU(或RLC SDU)之前(或递交给下层之前)已发送(或递交给下层)的RLC SDU或RLC SDU分段的肯定确认和/或否定确认，如果所述RLC SDU或RLC SDU分段(或者未收到肯定确认和/或否定确认的RLC SDU或RLC SDU分段)的序列号SN满足POLL_SN＜SN＜＝TX_Next-1(备选的，POLL_SN＜SN＜TX_Next；备选的，POLL_SN＜＝SN＜TX_Next；备选的，POLL_SN＜SN＜＝TX_Next；备选的，POLL_SN＜＝SN＜＝TX_Next-1；备选的，TX_Next_Ack＜＝SN＜TX_Next；备选的，TX_Next_Ack＜＝SN＜＝TX_Next-1；备选的，TX_Next_Ack＜SN＜TX_Next；备选的，TX_Next_Ack＜SN＜＝TX_Next-1)，则AM RLC实体发送端将所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)用于重传；换言之，AM RLC实体发送端认为所述RLC SDU或RLC SDU分段(或所述未接收到肯定确认和/或否定确认RLC SDU或RLC SDU分段)需要重传。
可选的，条件二～五中涉及的TX_Next可以按照步骤110中的定义，POLL_SN可以按照步骤120中定义的实施例进行更新。
可选的，当接收到来自其对等AM RLC实体的状态PDU(或状态报告)时才判断条件二～五。
在本公开中，关于状态变量的计算可以按照以下方式来进行：如果序列号用例如12比特标识，则序列号取值范围为0到4095。那么，状态变量取值等于计算得到的值与4096进行模(modulo)运算的余数。另外，如果 序列号用18比特标识，则状态变量取值范围为0到262143。那么，状态变量取值等于计算得到的值与262144进行模运算的余数。
另外，本公开中描述的将状态变量设置为序列号或序列号的值是指将该状态变量的值设置为序列号或序列号的值。
图3示出了根据本公开实施例的AM RLC实体的简要结构框图。
如图3所示，该AM RLC实体400至少包括接收端401和发送端402。而且，该AM RLC实体400例如既可以包含于客户端设备，也可以包含于基站设备，且可以由处理器控制接收端401来执行本公开的上述图1和/或图2所描述的AM RLC实体的发送方法和/或重传方法。
图4示出了根据本公开实施例的通信设备的简要结构框图。
如图4所示，该通信设备500至少包括处理器501和存储器502。处理器501例如可以包括微处理器、微控制器、嵌入式处理器等。存储器502例如可以包括易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统等。存储器502上存储有程序指令。该指令在由处理器501运行时，可以执行本公开的上述图1和/或图2所描述的AM RLC实体的发送方法和/或重传方法。
需要说明的是，本公开实施例中所述“包含询问”、“询问比特被置为1”是等价描述，可互换使用；所述“已传输”、“已发送”、“已递交给下层”是等价描述，可互换使用；所述“AM RLC发送实体”和“AM RLC实体发送端”是等价描述，可互换使用；所述“RLC SDU的第一个分段”和“RLC SDU的第一个字节”是等价描述，可互换使用。将所述实施例中的术语替换其等价描述，所述实施例仍然成立。在本公开实施例中，可将RLC SDU或RLC SDU分段用RLC PDU代替。
需要说明的是本公开所述实施例可以在用户设备UE处执行，也可以在基站处执行。如果AM RLC实体发送端在UE中，则其对等AM RLC实体(即AM RLC实体接收端)在基站中；相应的，如果AM RLC实体发送端在基站中，则其对等AM RLC实体(即AM RLC实体接收端)在UE中。
运行在根据本公开的设备上的程序可以是通过控制中央处理单元(CPU)来使计算机实现本公开的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、或其他存储器系统 中。
用于实现本公开各实施例功能的程序可以记录在计算机可读记录介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读记录介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本公开的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本公开并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本公开并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本公开的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本公开也包括不偏离本公开主旨的任何设计改动。另外，可以在权利要求的范围内对本公开进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本公开的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种确认模式RLC实体的发送方法，包括：
    所述确认模式RLC实体向下层发送包含询问的确认模式数据PDU；
    所述确认模式RLC实体更新询问发送状态变量POLL_SN，将所述询问发送状态变量POLL_SN设置为满足预定条件的任意确认模式数据PDU的序列号SN，
    所述预定条件为：所述任意确认模式数据PDU是与已发送给所述下层的确认模式数据PDU中包含询问且序列号最大的确认模式数据PDU一起发送给所述下层的确认模式数据PDU。
  2. 根据权利要求1所述的方法，其中，
    所述一起发送给所述下层的确认模式数据PDU具体为：
    同时发送给所述下层、或一起发送给所述下层、或复用到一个媒体访问控制PDU、或在来自下层指示的同一传输时机中传输的确认模式数据PDU。
  3. 根据权利要求1所述的方法，其中，
    还包括：在必要情况下更新发送状态变量TX_Next，
    所述必要情况具体为：
    所述确认模式RLC实体构建一个序列号SN＝TX_Next、且其中包含一个RLC SDU或RLC SDU的最后一个分段的确认模式数据PDU的情况；或者
    所述确认模式RLC实体发送或传输或者向所述下层发送或传输一个序列号SN＝TX_Next、且其中包含一个RLC SDU或RLC SDU的最后一个分段的确认模式数据PDU的情况。
  4. 一种确认模式RLC实体的重传方法，包括：
    所述确认模式RLC实体接收来自对等确认模式RLC实体的状态报告或状态PDU；
    根据所述状态报告或所述状态PDU，所述确认模式RLC实体执行下列操作：
    将接收到否定确认的RLC SDU或RLC SDU分段进行重传；或者
    将满足预定条件的RLC SDU或RLC SDU分段进行重传。
  5. 根据权利要求4所述的确认模式RLC实体的重传方法，其中，
    所述否定确认的RLC SDU或RLC SDU分段是通过如下方式接收到的：
    来自所述对等确认模式RLC实体的状态PDU；或者
    某个RLC SDU或RLC SDU分段的序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送；或者
    所述某个RLC SDU或RLC SDU分段的所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送；或者
    所述某个RLC SDU或RLC SDU分段的所述序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间、并且所述某个RLC SDU或RLC SDU分段在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送且所述状态报告或所述状态PDU中不包含其肯定确认和/或否定确认。
  6. 根据权利要求5所述的确认模式RLC实体的重传方法，其中，
    所述序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间具体为：
    ACK_SN＜SN＜TX_Next；或
    ACK_SN＜SN＜＝TX_Next-1；或
    ACK_SN＜＝SN＜TX_Next；或
    ACK_SN＜＝SN＜＝TX_Next-1，
    所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间具体为：
    POLL_SN＜SN＜TX_Next；或
    POLL_SN＜SN＜＝TX_Next-1；或
    POLL_SN＜＝SN＜TX_Next；或
    POLL_SN＜＝SN＜＝TX_Next-1，
    所述序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间具体为：
    TX_Next_Ack＜＝SN＜TX_Next；或
    TX_Next_Ack＜SN＜＝TX_Next-1；或
    TX_Next_Ack＜＝SN＜＝TX_Next-1；或
    TX_Next_Ack＜SN＜TX_Next。
  7. 根据权利要求4所述的确认模式RLC实体的重传方法，其中，
    所述预定条件的RLC SDU或RLC SDU分段具体为：
    被所述对等确认模式RLC实体的所述状态PDU或所述状态报告否定确认、并且所对应的RLC SDU的序列号SN满足介于确认状态变量TX_Next_Ack与发送状态变量TX_Next之间即TX_Next_Ack＜＝SN＜TX_Next的RLC SDU或RLC SDU分段；或者
    接收到来自所述对等确认模式RLC实体的所述状态PDU或所述状态报告中不包括某个在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送的RLC SDU或RLC SDU分段的肯定确认和/或否定确认；或者
    在最近或最新发送的包含询问的确认模式数据PDU或RLC SDU之前已发送的RLC SDU或RLC SDU分段、并且该RLC SDU或RLC SDU分段的序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间、或者满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间。
  8. 根据权利要求7所述的确认模式RLC实体的重传方法，其中，
    所述序列号SN满足介于确认序列号ACK_SN与发送状态变量TX_Next之间具体为：
    ACK_SN＜SN＜TX_Next；或
    ACK_SN＜SN＜＝TX_Next-1；或
    ACK_SN＜＝SN＜TX_Next；或
    ACK_SN＜＝SN＜＝TX_Next-1，
    所述序列号SN满足介于询问发送状态变量POLL_SN与发送状态变量TX_Next之间具体为：
    POLL_SN＜SN＜＝TX_Next-1；或
    POLL_SN＜SN＜TX_Next；或
    POLL_SN＜＝SN＜TX_Next；或
    POLL_SN＜＝SN＜＝TX_Next-1。
  9. 一种确认模式RLC实体，包括：
    发送端和接收端，
    所述发送端执行根据权利要求1至3中任一项所述的发送方法和/或根据权利要求4至8中任一项所述的重传方法。
  10. 一种通信设备，是具有确认模式RLC实体的通信设备，包括：
    处理器；以及
    存储器，存储有指令；
    其中，所述指令在由所述处理器运行时执行根据权利要求1至3中任一项所述的发送方法和/或根据权利要求4至8中任一项所述的重传方法。
PCT/CN2019/080807 2018-04-03 2019-04-01 确认模式rlc实体及其发送/重传方法、通信设备 WO2019192425A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201810293512.X 2018-04-03
CN201810293512.XA CN110351021A (zh) 2018-04-03 2018-04-03 确认模式rlc实体及其发送/重传方法、通信设备

Publications (1)

Publication Number Publication Date
WO2019192425A1 true WO2019192425A1 (zh) 2019-10-10

Family

ID=68099945

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/080807 WO2019192425A1 (zh) 2018-04-03 2019-04-01 确认模式rlc实体及其发送/重传方法、通信设备

Country Status (2)

Country Link
CN (1) CN110351021A (zh)
WO (1) WO2019192425A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111132232B (zh) * 2020-01-02 2022-10-25 重庆邮电大学 一种智能接收5g nr rlc umd pdu的方法和装置

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101030839A (zh) * 2007-02-13 2007-09-05 华为技术有限公司 一种数据重传的方法
WO2017194326A1 (en) * 2016-05-13 2017-11-16 Sony Corporation Apparatuses and methods for using arq processes in a relay device

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101030839A (zh) * 2007-02-13 2007-09-05 华为技术有限公司 一种数据重传的方法
WO2017194326A1 (en) * 2016-05-13 2017-11-16 Sony Corporation Apparatuses and methods for using arq processes in a relay device

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
3GPP: "3 rd Generation Partnership Project; Technical Specification Group Ra- dio Access Network; NR; Radio Link Control (RLC) protocol specification (Re- lease 15", 3GPP TS 38. 322, vol. RAN WG2, no. V15.1.0, 30 March 2018 (2018-03-30) - 2 April 2018 (2018-04-02), pages 1 - 33, XP051450733 *
LG ELECTRONICS INC: "Summary of POLL_SN related issue", 3GPP TSG-RAN WG2 MEETING #101, R2-1803870, vol. RAN WG2, 2 March 2018 (2018-03-02), XP051400945 *

Also Published As

Publication number Publication date
CN110351021A (zh) 2019-10-18

Similar Documents

Publication Publication Date Title
US9565007B2 (en) Method of receiving a point-to-multipoint service in a wireless communication system
JP5431526B2 (ja) ワイヤレス通信システムにおけるハンドオーバの間に順序が狂っているパケットを取り扱うための方法および装置
US20060245430A1 (en) Method and Apparatus of a Procedure for Receiving Window Size Reconfiguration in a Communication System
US20070291695A1 (en) Method and apparatus for facilitating lossless handover in 3gpp long term evolution systems
JP2010536271A (ja) 無線通信システムにおけるハンドオーバー中のデータのレイヤ２トンネリング
CN109076475B (zh) 一种用于保持无连接传输中同步的方法和系统
US8738984B2 (en) Apparatus for processing retransmission failure in radio link control (RLC) layer
TW200935812A (en) Status reporting for retransmission protocol
WO2020156569A1 (zh) 发送rlc状态报告的方法、设备和存储介质
US20180302830A1 (en) Data transmission method and network device
KR101578047B1 (ko) 통신 시스템에서 데이터 패킷 재정렬 장치 및 방법
US20080192671A1 (en) Mobile Telecommunication
JP2018509037A (ja) データパケットの再送信方法及び装置
WO2010128636A1 (ja) 通信システム、通信装置、通信方法及びプログラム
WO2019192425A1 (zh) 确认模式rlc实体及其发送/重传方法、通信设备
US11258721B2 (en) Radio link control (RLC) acknowledged mode (AM) data reception
US10849160B2 (en) Reinstating poll retransmission timer
WO2019110003A1 (zh) 无线通信方法和设备
WO2019062760A1 (zh) 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质
US20150071273A1 (en) Efficient transfer of tcp traffic over wlan
WO2019096215A1 (zh) 无线通信方法和设备
JP2009044694A (ja) データユニットの送信回数のカウント方法、カウント装置、送信装置、およびコンピュータプログラム
JP2009044695A (ja) 通信制御方法、送信装置、およびコンピュータプログラム
WO2019193448A1 (en) Method and apparatus for multi‑hop arq
KR101374261B1 (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: 19780788

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

Country of ref document: EP

Kind code of ref document: A1