WO2019062760A1 - 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质 - Google Patents

服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质 Download PDF

Info

Publication number
WO2019062760A1
WO2019062760A1 PCT/CN2018/107602 CN2018107602W WO2019062760A1 WO 2019062760 A1 WO2019062760 A1 WO 2019062760A1 CN 2018107602 W CN2018107602 W CN 2018107602W WO 2019062760 A1 WO2019062760 A1 WO 2019062760A1
Authority
WO
WIPO (PCT)
Prior art keywords
rlc
entity
sdu
data
pdu
Prior art date
Application number
PCT/CN2018/107602
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 WO2019062760A1 publication Critical patent/WO2019062760A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0231—Traffic management, e.g. flow control or congestion control based on communication conditions
    • H04W28/0242—Determining whether packet losses are due to overload or to deterioration of radio communication conditions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0278—Traffic management, e.g. flow control or congestion control using buffer status reports
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/06—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information
    • H04W28/065—Optimizing the usage of the radio link, e.g. header compression, information sizing, discarding information using assembly or disassembly of packets
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/10—Flow control between communication endpoints
    • H04W28/14—Flow control between communication endpoints using intermediate storage

Definitions

  • the present disclosure relates to the field of wireless communication technologies, and more particularly, to a method for processing a service data unit, a method for dropping a service data unit, and a corresponding user equipment, performed at a user equipment.
  • NTT DOCOMO proposed a new research project on 5G technology standards (see Non-patent literature: RP-160671) :New SID Proposal: Study on New Radio Access Technology), and approved.
  • the goal of the research project is to develop a new wireless (New Radio: NR) access technology to meet all 5G application scenarios, requirements and deployment environments.
  • NR mainly has three application scenarios: Enhanced Mobile Broadband (eMBB), Massive Machine Type Communication (mMTC) and Ultra reliable and low latency communications (URLLC).
  • eMBB Enhanced Mobile Broadband
  • mMTC Massive Machine Type Communication
  • URLLC Ultra reliable and low latency communications
  • the cascading operation was not supported in the NR Radio Link Control (RLC) entity at the 3GPP RAN2 #96 meeting held in October 2016.
  • RLC Radio Link Control
  • a split bearer at the RAN2 NR Adhoc #2 meeting in June 2017 can use data preprocessing similar to a single carrier.
  • the NR User Equipment (UE) can perform data pre-processing on the uplink split bearer before receiving the lower layer request (or data transmission request), and receives the request from the lower layer.
  • the data (that is, the preprocessed data) is submitted to the lower layer.
  • the conclusions reached in the previous meetings will affect the processing flow of the sender of the NR RLC entity.
  • the present disclosure is directed to solving related problems involved in the processing flow of an acknowledge mode AM RLC entity sender or a non-acknowledgement mode UM RLC transmission entity, including the processing of an RLC service data unit SDU from an upper layer by an AM RLC entity sender or a UM RLC transmitting entity.
  • the process, the AM RLC entity sender or the UM RLC sending entity receives an operation that should be performed when the specific RLC SDU is discarded from the upper layer.
  • the purpose of the present disclosure is to solve the above technical problem. Specifically, the present disclosure is directed to solving related problems involved in an AM RLC entity sender or a UM RLC sending entity processing flow, including an AM RLC entity sender or a UM RLC sending entity pair.
  • the processing flow of the upper layer RLC service data unit SDU, the AM RLC entity sender or the UM RLC sending entity receives an operation that should be performed when the specific RLC SDU is discarded from the upper layer.
  • a first aspect of the present disclosure provides a method performed at a UE, including: at an RLC entity of a UE,
  • the generated RLC data PDU is stored in a transmission buffer.
  • the method further includes: when the RLC entity receives the data transmission indication from the lower layer entity, transmitting the RLC data PDU stored in the transmission buffer to the lower layer entity.
  • the RLC data PDU stored in the transmission buffer exceeds the transmittable data size indicated in the data transmission indication, segmenting the RLC data PDU and modifying the RLC header Send to the underlying entity.
  • the RLC entity comprises: an AM RLC entity and/or a UM RLC transmitting entity.
  • the method further includes:
  • the AM RLC entity increments the value of TX_Next by one after associating the value of the current transmit state variable TX_Next to an RLC SDU received from the upper layer.
  • a second aspect of the present disclosure provides a method performed at a UE, comprising: at an RLC entity of a UE,
  • the RLC data PDU is discarded in a case where it is determined that at least one segment of the specific RLC SDU or the specific RLC SDU has generated a corresponding RLC data PDU, but the RLC data PDU has not been transmitted to a lower layer entity.
  • the method further comprises: if the discarded RLC SDU or a segment thereof has been associated with a sequence number, or the corresponding RLC data PDU is discarded, the discarded RLC SDU Or the sequence number corresponding to the segment or the corresponding RLC data PDU is reassigned to the other RLC SDU or its segment or the corresponding RLC data PDU, or the serial number is less than the discarded RLC SDU or its segment or corresponding
  • the RLC SDU with a large sequence number of the RLC data PDU and/or its segment and/or the corresponding RLC data PDU reallocate the sequence number.
  • the RLC entity comprises: an AM RLC entity and/or a non-acknowledgment mode UM RLC transmitting entity.
  • a third aspect of the disclosure provides a UE, including:
  • Communication interface configured for communication
  • the memory is stored with computer executable instructions that, when executed by the processor, cause the UE to perform any of the methods described above.
  • a fourth aspect of the present disclosure provides a computer readable medium having stored thereon instructions that, when executed by a processor, cause the processor to perform any of the methods described above.
  • an RLC data PDU is generated by adding an RLC header to an RLC SDU from an upper layer entity and the generated RLC data PDU is stored in a transmission buffer such that an RLC entity (eg, AM RLC)
  • the entity sending end or the UM RLC sending entity may directly send the RLC data PDU stored in the sending buffer to the lower layer when receiving the data sending indication from the lower layer, thereby reducing the data sending delay.
  • the RLC data PDU is discarded in the case of the lower layer transmission, so that the RLC entity can avoid transmitting the data that has expired, thereby saving radio resources.
  • Figure 1 shows a schematic diagram of an RLC AM entity model in an existing protocol
  • FIG. 2 illustrates a schematic flowchart of a method for processing an RLC SDU performed at a UE according to an exemplary embodiment of the present disclosure
  • FIG. 3(a) shows a schematic diagram of an RLC AM entity model according to an exemplary embodiment of the present disclosure
  • FIG. 3(b) shows a schematic diagram of an RLC AM entity model according to another exemplary embodiment of the present disclosure
  • FIG. 4 shows a schematic diagram of two RLC UM peer entity models in accordance with an exemplary embodiment of the present disclosure
  • FIG. 5 illustrates a schematic structural block diagram of a UE for processing an RLC SDU according to an exemplary embodiment of the present disclosure
  • FIG. 6 illustrates a schematic flowchart of a method for discarding an RLC SDU performed at a UE according to an exemplary embodiment of the present disclosure
  • FIG. 7 illustrates a schematic structural block diagram of a UE for discarding an RLC SDU according to an exemplary embodiment of the present disclosure.
  • PDCP Packet Data Convergence Protocol
  • Packet Data Convergence Protocol Packet Data Convergence Protocol
  • RLC Radio Link Control
  • the RLC entity may be an Unacknowledged Mode UM RLC entity or an Acknowledged Mode AM RLC entity.
  • AM RLC acknowledge mode data
  • UM RLC the segment of the RLC SDU or the RLC SDU adds the RLC header to obtain the UMD PDU.
  • the RLC Data PDU may be an AMD PDU or a UMD PDU.
  • Protocol Data Unit Protocol data unit
  • SDU Service Data Unit
  • 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 transmitted to the lower layer or received from the lower layer is referred to as a PDU
  • the data received by the PDCP entity from the upper layer or the data sent to the upper layer is called a PDCP SDU
  • the data received by the PDCP entity from the RLC entity or the data sent to the RLC entity is called a PDCP PDU (ie, an RLC SDU).
  • the data received by the RLC entity from the PDCP entity is referred to as the RLC SDU, and the data that the RLC entity submits to the lower layer (ie, the Medium Access Control (MAC) layer) is referred to as the RLC PDU, including the RLC Data PDU and the RLC Control PDU.
  • the RLC Data PDU is generated by an RLC SDU from an upper layer, and the RLC Control PDU is a Status PDU, which is used to provide a positive acknowledgment ACK or a negative acknowledgment NACK to the RLC SDU or its segment.
  • the current RLC AM entity model is shown in Figure 4.2.3.3.11 of the latest 3GPP TS 38.322 version 1.0.0 (see 3GPP proposal R2-1709752, which is referred to as version 0.3.0 in this proposal). This is shown in Figure 1 herein.
  • the AM RLC entity sender generates an RLC header for the RLC SDU from the PDCP entity and stores the generated RLC header in the transmission buffer.
  • the RLC header is added to the RLC SDU and then delivered to the lower layer.
  • the RLC SDU adds the RLC header and exceeds the transmittable data size indicated by the lower layer, the RLC SDU is segmented and the corresponding header is modified, and then the RLC header is added to the RLC SDU segment and submitted to the lower layer.
  • the transmission buffer area of the AM RLC entity stores the RLC SDU.
  • the processing method of storing the RLC SDU and its associated RLC header in the transmission buffer area when the RLC entity receives the data transmission indication of the lower layer, adds a header to the RLC SDU and then sends the header to the lower layer, adding data. Send delay.
  • FIG. 2 illustrates a flow diagram of a method 200 for processing an RLC SDU performed at a UE, in accordance with an exemplary embodiment of the present invention.
  • method 200 is performed at an RLC entity in the UE.
  • method 200 can include steps S201, S202, and S203.
  • the RLC entity may generate an RLC data PDU by adding an RLC header to an RLC SDU from an upper layer entity (eg, a PDCP entity), and may also be described as an RLC entity to be from an upper layer entity (eg, a PDCP entity)
  • the RLC SDU is mapped to an RLC data PDU.
  • step S202 the generated RLC data PDU is stored in a transmission buffer.
  • step S203 when receiving a data transmission indication from a lower layer entity (for example, a MAC entity), the RLC data PDU stored in the transmission buffer area is transmitted to the lower layer entity.
  • a lower layer entity for example, a MAC entity
  • the RLC data PDU stored in the transmission buffer exceeds the transmittable data size indicated in the data transmission indication, the RLC data PDU is segmented and the RLC header is modified and sent (may also be described as “submitted” ", the same below) to the lower entity.
  • the RLC data PDU that is delivered to the lower layer includes the segment of the RLC SDU, the RLC data PDU stored in the transmission buffer or its corresponding RLC SDU is segmented and the RLC header is modified and sent to the lower layer entity.
  • the RLC entity may be an AM RLC entity.
  • method 200 is specifically performed at the transmitting end of an AM RLC entity. This exemplary embodiment will be described later with reference to FIGS. 3(a) and 3(b).
  • the method 200 may further include maintaining, at the AM RLC entity, a transmission state variable TX_Next, the transmission state variable for storing a sequence number to be allocated to the next RLC SDU received from the upper layer entity; And the AM RLC entity increments the value of TX_Next by one after associating the value of the current transmit state variable TX_Next to an RLC SDU received from the upper entity.
  • the RLC entity may be a UM RLC transmitting entity.
  • method 200 is specifically performed at a UM RLC transmitting entity. This exemplary embodiment will be described later with reference to FIG.
  • the technical solution of the present disclosure proposes to modify the RLC AM physical model shown in FIG. 1 as shown in FIG. 3(a) or 3(b).
  • 3(a) and 3(b) respectively show schematic diagrams of an RLC AM solid model according to an exemplary embodiment of the present disclosure.
  • the transmitting end of the AM RLC entity may add an RLC header to the RLC SDU from, for example, the PDCP entity in step S201 to generate an AMD PDU, which may also be described as coming from For example, the RLC SDU of the PDCP entity is mapped to an AMD PDU.
  • step S202 the transmitting end of the AM RLC entity may store the AMD PDU in the transmission buffer.
  • step S203 when the transmitting end of the AM RLC entity receives the data transmission indication from, for example, the MAC entity, the AMD PDU stored in the transmission buffer area is delivered to the MAC entity.
  • the RLC data PDU is segmented and the RLC header is modified and then sent to the lower layer entity.
  • the AMD PDU that is delivered to the lower layer includes the segment of the RLC SDU
  • the AMD PDU stored in the transmission buffer or its corresponding RLC SDU is segmented and the RLC header is modified and sent to the lower layer entity.
  • the modified RLC AM entity model shown in Figure 3(a) or 3(b) includes at least the following modules (also referred to as functions): a transmit buffer module, a retransmission cache module, a segmentation, and a modified RLC header module. , RLC control module, add RLC head module.
  • the transmit buffer module is configured to map an RLC SDU from, for example, a PDCP entity to an AMD PDU, that is, associate a sequence number TX_Next with the RLC SDU and construct an AMD PDU by setting the sequence number of the AMD PDU to a value of TX_Next, the AMD PDU. Stored in the send buffer.
  • the retransmission buffer module is configured to store AMD PDUs that are waiting to be retransmitted or AMD PDUs that have been submitted to the lower layer but have not been confirmed to be successfully transmitted.
  • the AMD PDU is simultaneously stored in the retransmission buffer when it is delivered to the lower layer.
  • the AMD PDU is taken out from the retransmission buffer and submitted to the next layer. If the AMD PDU exceeds the size of the transmittable data indicated by the lower layer, the AMD PDU is delivered to the segment and the modified RLC header module to segment the AMD PDU.
  • the segmentation and modification RLC header module segments or re-segments the AMD PDU stored in the transmission buffer or the retransmission buffer according to the size of the transmittable data indicated by the lower layer and modifies the RLC header to deliver to the lower layer entity.
  • the RLC control module generates a load of the status PDU according to the RLC PDU received by the receiver of the AM RLC entity.
  • the RLC header module is added to add header generation RLC control PDUs or status PDUs for data from the RLC control module (ie, the load of the status PDU).
  • the process of processing the RLC SDU from the upper layer by the AM RLC entity in section 5.1.3.1.1 of the 3GPP TS 38.322 version 1.0.0 may be modified as follows:
  • the AM RLC entity is the sequence number SN of the RLC SDU associated value TX_Next
  • the AMD PDU is constructed by setting the SN of the AMD PDU to the value of TX_Next.
  • the AMD PDU is stored in a transmit buffer. Set the value of TX_Next to TX_Next+1.
  • the AM RLC entity modifies the RLC header of the AMD PDU (or the header associated with the RLC SDU).
  • the sequence number of the segmented AMD PDU is the same as the segmented AMD PDU, or the sequence number of the segmented AMD PDU is the same as the sequence number of the corresponding RLC SDU.
  • the modified RLC header and the corresponding RLC SDU segment are stored in a transmit buffer.
  • an AMD PDU or RLC SDU
  • one RLC SDU is divided into two segments, which are respectively referred to as a first segment and a second segment, and a segment offset SO is generated for each segment of the RLC SDU.
  • the RLC header, and the sequence number included in the RLC header of the segment is the same as the original RCL SDU. It should be noted that the segmentation operation is also applicable to a UMD PDU or a UM RLC transmitting entity.
  • the AM RLC entity maintains a transmission state variable TX_Next for storing the sequence number of the next newly generated AMD PDU or the next or next sequence number to be assigned or the assigned sequence number.
  • the TX_Next value ranges from 0 to 4095
  • the TX_Next value the modulo 4096 of the arithmetic operation
  • the serial number is identified by 18 bits
  • TX_Next value modulo modulo 262144 obtained by arithmetic operation.
  • the initial value of the transmit state variable TX_Next is 0, and the variable can be updated in one of two ways:
  • TX_Next is updated or incremented by 1 when the AM RLC entity associates the current TX_Next to an RLC SDU received from the upper layer.
  • this operation is performed when the AM RLC entity sender supports data preprocessing.
  • TX_Next is updated or incremented by 1 when the AM RLC entity sends the AMD PDU with the sequence number TX_Next.
  • this operation is performed when the AM RLC entity sender does not support data preprocessing.
  • whether the AM RLC entity sender supports data preprocessing is configured through RRC signaling.
  • the data pre-processing is dynamically activated and/or deactivated by the media access MAC Control Element CE, or the data pre-processing is dynamically activated and/or deactivated by the RLC Control PDU.
  • the technical solution of the present disclosure proposes two UM pairs as shown in FIG. 4.2.1.2.1-1 in 3GPP TS 38.322 version 1.0.0.
  • the entity model is modified to the two UM peer entity models shown in Figure 4.
  • the UM RLC transmitting entity includes at least the following two modules (which may also be referred to as functions): a transmit buffer module and a segment and a modified RLC header module.
  • the transmit buffer module maps the RLC SDUs from, for example, the PDCP entity into UMD PDUs and stores them in the transmit buffer.
  • the segmentation and modification RLC header module directs the UMD PDU in the transmission buffer to the size of the transmittable data indicated by the data transmission indication from the lower layer entity.
  • the lower layer sends or segments the UMD PDU or its corresponding RLC SDU and modifies the RLC header and sends it to the lower layer.
  • the implementation mechanism of storing the RLC data PDU in the transmission buffer as described in the foregoing exemplary embodiments of the present disclosure such that the AM RLC entity sender or the UM RLC transmitting entity may directly store the data transmission indication from the lower layer.
  • the RLC data PDU in the transmission buffer is sent to the lower layer, which reduces the data transmission delay.
  • the RLC entity of the UE may store the RLC SDU and the associated RLC header in a transmit buffer.
  • the technical solution of the present disclosure proposes to modify the processing flow of the RLC sender in section 5.1.3.1.1 of 3GPP TS 38.322 version 1.0.0 as follows.
  • the AM RLC entity receives an RLC SDU from an upper layer entity (eg, a PDCP entity), and generates an RLC header for the RLC SDU with a sequence number of TX_Next (or a sequence number SN for the RLC SDU association value TX_Next, generating an RLC) head).
  • the RLC header and/or RLC SDU are stored in a transmit buffer. Set the value of TX_Next to TX_Next+1 (ie, increase the value of TX_Next by 1).
  • the AM RLC entity modifies the header corresponding to the RLC SDU, and stores the modified header together with the RLC SDU segment in the transmit buffer.
  • the AM RLC entity sender adds an RLC header for the RLC SDU or RLC SDU segment.
  • the transmitting end of the AM RLC entity sets the sequence number of the AM PDU to the sequence number associated with the RLC SDU.
  • the AM RLC entity sender adds an RLC header to the RLC SDU or RLC SDU segment to construct the AMD PDU.
  • the sequence number of the AMD PDU is set to the sequence number of the corresponding RLC SDU.
  • FIG. 5 schematically shows a structural block diagram of a UE that performs a method for processing an RLC SDU, according to an exemplary embodiment of the present invention.
  • the UE 500 can be used to perform the method 200 described with reference to FIG.
  • FIG. 5 For the sake of brevity, only the schematic structure of the UE according to an exemplary embodiment of the present disclosure will be described herein, and the details already detailed in the method 200 as previously described with reference to FIG. 2 are omitted.
  • the UE 500 includes a communication interface 501 for external communication; a processing unit or processor 502, which may be a single unit or a combination of a plurality of units for performing different steps of the method; the memory 503 Where computer executable instructions are stored, which, when executed by processor 502, may cause the RLC entity of UE 500 to perform the following process:
  • the generated RLC data PDU is stored in a transmission buffer.
  • the instructions when executed by the processor 502, may also cause the RLC entity of the UE 500 to perform the following process:
  • the RLC entity When the RLC entity receives the data transmission indication from the lower layer entity, the RLC data PDU stored in the transmission buffer area is sent to the lower layer entity.
  • the RLC data PDU stored in the transmission buffer exceeds the transmittable data size indicated in the data transmission indication, segmenting the RLC data PDU and modifying the RLC header Send to the underlying entity.
  • the RLC entity may be an AM RLC entity or a UM RLC sending entity.
  • the above process is specifically performed at the transmitting end of the AM RLC entity; and in an exemplary embodiment where the RLC entity is a UM RLC entity, the above process is specifically in the UM RLC sending entity. Execution.
  • the instructions when executed by the processor 502, may also cause the RLC entity of the UE 500 to perform the following process:
  • the AM RLC entity increments the value of TX_Next by one after associating the value of the current transmit state variable TX_Next to an RLC SDU received from the upper layer entity.
  • a split bearer can be achieved at the RAN2 NR Adhoc# 2 meeting.
  • Data preprocessing similar to a single carrier can be used; at the RAN2#99 meeting, the NR UE can receive the lower layer request (or data transmission request) before receiving the lower layer request (or data transmission request).
  • Data pre-processing is performed on the uplink split bearer, and the data (ie, the pre-processed data) is delivered to the underlying entity before receiving the request from the underlying entity (eg, the MAC entity).
  • the RLC entity receives a data RLC SDU from, for example, a PDCP entity and generates an RLC header (or associates a sequence number for the RLC SDU).
  • the buffer area of the RLC entity there may be an RLC SDU (or an RLC SDU that has not yet been associated with a sequence number) that has not yet generated an RLC header, and an RLC SDU or RLC that has generated an RLC header.
  • RLC SDU or an RLC SDU that has not yet been associated with a sequence number
  • RLC SDU or RLC that has generated an RLC header.
  • the present disclosure proposes a scheme for discarding RLC SDUs performed at the UE.
  • FIG. 6 illustrates a flow diagram of a method 600 for dropping an RLC SDU performed at a UE, in accordance with an exemplary embodiment of the present invention.
  • method 600 is performed at an RLC entity in the UE.
  • the RLC entity may be an AM RLC entity or a UM RLC sending entity.
  • the method 600 is performed specifically at the transmitting end of the AM RLC entity; and in an exemplary embodiment where the RLC entity is a UM RLC entity, the method 600 specifically transmits the entity in the UM RLC Execution.
  • method 600 can include steps S601 through S606.
  • the RLC entity may receive an indication from an upper layer entity (eg, a PDCP entity) to discard a particular RLC SDU.
  • an upper layer entity eg, a PDCP entity
  • the RLC entity may stop assigning or associating the sequence number to the RLC SDU from the upper layer.
  • the RLC entity may stop assigning or associating the sequence number to the RLC SDU from the upper layer.
  • the RLC entity may determine whether any segment of the specific RLC SDU or the specific RLC SDU has generated a corresponding RLC data PDU, and may also be described as determining the specific RLC SDU or the specific RLC. Whether any segment of the SDU is mapped to the corresponding RLC data PDU.
  • step S603 is performed, wherein the RLC entity may discard the specific RLC SDU.
  • step S604 is performed, wherein the RLC entity may determine an arbitrary score of the specific RLC SDU or the specific RLC SDU Whether the corresponding RLC data PDU generated by the segment has been sent to the lower layer.
  • step S605 is performed, in which the RLC entity discards the RLC SDU and/or the corresponding RLC data PDU.
  • the RLC SDU and/or the corresponding RLC data PDU are discarded.
  • the UM RLC transmitting entity discards the RLC data PDU and/or the RLC SDU.
  • the RLC SDU is already mapped to the RLC data PDU, and the header of the RLC data PDU or the RLC data PDU includes a sequence number, but the RLC data PDU to which any segment of the RLC SDU is mapped has not been submitted to the lower layer or the The RLC data PDU corresponding to the first segment of the RLC SDU (or the corresponding RLC data PDU) has not been sent to the lower layer, and the UM RLC transmitting entity discards the RLC data PDU and/or corresponding to all segments or segments of the RLC SDU. Or RLC SDU.
  • the method 600 may further include: if the discarded RLC SDU or a segment thereof has been associated with a sequence number, or the corresponding RLC data PDU is discarded, the discarded RLC SDU or a segment thereof or The sequence number corresponding to the corresponding RLC data PDU is reassigned to the other RLC SDU or its segment or the corresponding RLC data PDU; or, the sequence number is smaller than the discarded RLC SDU or its segment or the corresponding RLC data PDU.
  • the RLC SDU with a large sequence number and/or its segment and/or the corresponding RLC data PDU reallocate the sequence number to avoid the sequence number interval (SN gap) at the receiving end.
  • the method 600 may further include: setting the value of TX_Next to TX_Next-1, that is, reducing the value of TX_Next by one.
  • method 600 can also include continuing to assign or associate a sequence number to an RLC SDU from an upper entity.
  • step S603 if the discarded RLC SDU has been associated with the sequence number, the step of re-allocating the sequence number or the step of reallocating the sequence number and setting the value of TX_Next to TX_Next-1 may be performed.
  • step S606 is performed, where the RLC entity does not discard the corresponding RLC of the specific RLC SDU Data PDU.
  • FIG. 7 schematically shows a structural block diagram of a UE that performs a method for discarding an RLC SDU, according to an exemplary embodiment of the present invention.
  • the UE 700 can be used to perform the method 600 described with reference to FIG.
  • FIG. 7 For the sake of brevity, only the schematic structure of the UE according to an exemplary embodiment of the present disclosure will be described herein, and the details already detailed in the method 600 as previously described with reference to FIG. 6 are omitted. As shown in FIG.
  • the UE 700 includes a communication interface 701 for external communication; a processing unit or processor 702, which may be a single unit or a combination of multiple units for performing different steps of the method; Where computer executable instructions are stored, which, when executed by processor 702, may cause the RLC entity of UE 700 to perform the following process:
  • the RLC data PDU is discarded in a case where it is determined that at least one segment of the specific RLC SDU or the specific RLC SDU has generated a corresponding RLC data PDU, but the RLC data PDU has not been transmitted to the lower layer.
  • the instructions when executed by the processor 702, may also cause the RLC entity of the UE 700 to perform the following process:
  • the serial number corresponding to the discarded RLC SDU or its segment or the corresponding RLC data PDU is Reassignment to other RLC SDUs or their segments or corresponding RLC data PDUs;
  • the sequence number is reassigned for an RLC SDU having a sequence number greater than the sequence number of the discarded RLC SDU or its segment or corresponding RLC data PDU and/or its segment and/or corresponding RLC data PDU.
  • the RLC entity may be an AM RLC entity or a UM RLC sending entity.
  • the above process is specifically performed at the transmitting end of the AM RLC entity; and in an exemplary embodiment where the RLC entity is a UM RLC entity, the above process is specifically in the UM RLC sending entity. Execution.
  • the method for processing the RLC SDU and the procedure for discarding the RLC SDU performed at the UE in the present disclosure may also be applied to the RLC entity of the base station.
  • Computer executable instructions or programs running on a device in accordance with the present invention may be a program that causes a computer to implement the functions of an embodiment of the present invention 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.
  • Computer-executable instructions or programs for implementing the functions of various embodiments of the present invention may be recorded on a computer readable storage 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 storage 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 invention 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.
  • the present invention is not limited to the above embodiment. Although various examples of the embodiments have been described, the invention 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.

Abstract

公开了一种在UE处执行的用于处理RLC SDU的方法，包括：在UE的RLC实体处，通过向来自上层实体的RLC SDU增加RLC头部来生成RLC数据PDU；以及将所生成的RLC数据PDU存储在发送缓存区中。还公开了一种在UE处执行的用于丢弃RLC SDU的方法，包括：在UE的RLC实体处，接收来自上层实体的丢弃特定RLC SDU的指示；以及在确定所述特定RLC SDU或所述特定RLC SDU的至少一个分段已经生成相应的RLC数据PDU、但是所述RLC数据PDU尚未向下层实体发送的情况下，丢弃所述RLC数据PDU。还公开了相应的UE和计算机可读介质。

Description

服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质 技术领域
本公开涉及无线通信技术领域，更具体地，本公开涉及在用户设备处执行的用于处理服务数据单元的方法、用于丢弃服务数据单元的方法和相应的用户设备。
背景技术
2016年3月，在第三代合作伙伴计划(3rd Generation Partnership Project：3GPP)RAN#71次全会上，NTT DOCOMO提出了一个关于5G技术标准的新的研究项目(参见非专利文献：RP-160671：New SID Proposal：Study on New Radio Access Technology)，并获批准。该研究项目的目的是开发一个新的无线(New Radio：NR)接入技术以满足5G的所有应用场景、需求和部署环境。NR主要有三个应用场景：增强的移动宽带通信(Enhanced mobile broadband：eMBB)、大规模机器类通信(massive Machine type communication：mMTC)和超可靠低延迟通信(Ultra reliable and low latency communications：URLLC)。
在2016年10月召开的3GPP RAN2#96次会议上达成在NR无线链路控制(RLC)实体中不支持级联操作。在2017年6月召开的RAN2 NR Adhoc#2次会议上达成分离承载(split bearer)可以采用与单载波类似的数据预处理。在2017年8月召开的RAN2#99次会议上达成NR用户设备(UE)可在接收到下层请求(或数据发送请求)前对上行分离承载进行数据预处理，且在接收到来自下层的请求前将数据(即预处理后的数据)递交给下层。所述历次会议达成的结论，将影响NR RLC实体发送端的处理流程。
本公开致力于解决确认模式AM RLC实体发送端或非确认模式UM RLC发送实体处理流程所涉及的相关问题，包括AM RLC实体发送端或UM RLC发送实体对来自上层的RLC服务数据单元SDU的处理流程、AM RLC实体发送端或UM RLC发送实体接收到来自上层的丢弃特定RLC SDU时应执行的操作。
发明内容
本公开的目的旨在解决上述技术问题，具体地，本公开旨在解决AM RLC实体发送端或UM RLC发送实体处理流程所涉及的相关问题，包括AM RLC实体发送端或UM RLC发送实体对来自上层的RLC服务数据单元SDU的处理流程、AM RLC实体发送端或UM RLC发送实体接收到来自上层的丢弃特定RLC SDU时应执行的操作。
为了实现上述目的，本公开的第一方面提供了一种在UE处执行的方法，包括：在UE的RLC实体处，
通过向来自上层实体的RLC SDU增加RLC头部来生成RLC数据PDU；以及
将所生成的RLC数据PDU存储在发送缓存区中。
在一示例性实施例中，所述方法还包括：当RLC实体接收到来自下层实体的数据发送指示时，将在发送缓存区中存储的RLC数据PDU发送给下层实体。
在一示例性实施例中，如果在发送缓存区中存储的RLC数据PDU超过所述数据发送指示中所指示的可发送数据大小，则对所述RLC数据PDU进行分段并修改RLC头部后发送给下层实体。
在一示例性实施例中，所述RLC实体包括：AM RLC实体和/或UM RLC发送实体。
在一示例性实施例中，所述方法还包括：
在AM RLC实体处维护发送状态变量TX_Next，所述发送状态变量用于存储将分配给下一个从上层实体接收到的RLC SDU的序列号；以及
AM RLC实体在将当前发送状态变量TX_Next的值关联到一个从上层接收到的RLC SDU之后将TX_Next的值增加1。
本公开的第二方面提供了一种在UE处执行的方法，包括：在UE的RLC实体处，
接收来自上层实体的丢弃特定RLC服务数据单元SDU的指示；以及
在确定所述特定RLC SDU或所述特定RLC SDU的至少一个分段已经生成相应的RLC数据PDU、但是所述RLC数据PDU尚未向下层实体发送 的情况下，丢弃所述RLC数据PDU。
在一示例性实施例中，所述方法还包括：在被丢弃的RLC SDU或其分段已经关联了序列号、或相应的RLC数据PDU被丢弃的情况下，将所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU对应的序列号重新分配给其他RLC SDU或其分段或相应的RLC数据PDU，或为序列号比所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU的序列号大的RLC SDU和/或其分段和/或相应的RLC数据PDU重新分配序列号。
在一示例性实施例中，所述RLC实体包括：AM RLC实体和/或非确认模式UM RLC发送实体。
本公开的第三方面提供了一种UE，包括：
通信接口，配置用于通信；
处理器；以及
存储器，存储有计算机可执行指令，所述指令在被处理器执行时，使所述UE执行前述任一方法。
本公开的第四方面提供了一种计算机可读介质，在其上存储有指令，所述指令在由处理器执行时，使所述处理器执行前述任一方法。
在本公开的示例性实施例中，通过向来自上层实体的RLC SDU增加RLC头部来生成RLC数据PDU并将所生成的RLC数据PDU存储在发送缓存区中，使得RLC实体(如，AM RLC实体发送端或UM RLC发送实体)可以在接收到来自下层的数据发送指示时直接将存储在发送缓存区中的RLC数据PDU发送给下层，降低了数据发送时延。
此外，通过在接收来自上层实体的丢弃特定RLC SDU的指示之后在确定所述特定RLC SDU或所述特定RLC SDU的至少一个分段已经生成相应的RLC数据PDU、但是所述RLC数据PDU尚未向下层发送的情况下丢弃所述RLC数据PDU，使得RLC实体可以避免发送已经失效的数据，节省了无线资源。
本公开附加的方面和优点将在下面的描述中部分给出，这些将从下面的描述中变得明显，或通过本公开的实践了解到。
附图说明
通过下文结合附图的详细描述，本公开的上述和其它特征将会变得更加明显，其中：
图1示出了现有协议中的RLC AM实体模型的示意图；
图2示出了根据本公开示例性实施例的在UE处执行的用于处理RLC SDU的方法的示意性流程图；
图3(a)示出了根据本公开一示例性实施例的RLC AM实体模型的示意图；
图3(b)示出了根据本公开另一示例性实施例的RLC AM实体模型的示意图；
图4示出了根据本公开示例性实施例的两个RLC UM对等实体模型的示意图；
图5示出了根据本公开示例性实施例的用于处理RLC SDU的UE的示意性结构框图；
图6示出了根据本公开示例性实施例的在UE处执行的用于丢弃RLC SDU的方法的示意性流程图；以及
图7示出了根据本公开示例性实施例的用于丢弃RLC SDU的UE的示意性结构框图。
具体实施方式
下面结合附图和具体实施方式对本公开进行详细阐述。应当注意，本公开不应局限于下文所述的具体实施方式。另外，为了简便起见，省略了对与本公开没有直接关联的公知技术的详细描述，以防止对本公开的理解造成混淆。本公开所述实施例不限于NR，也可以应用其他的无线通信系统，例如6G。
下面描述本公开涉及的部分术语，如未特别说明，本公开涉及的术语采用此处定义。
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头部后得到确认模式数据(AMD)PDU。在UM RLC实体中，RLC SDU或RLC SDU的分段增加RLC头部后得到UMD PDU。RLC数据PDU可以是AMD PDU或UMD PDU。
PDU(Protocol Data Unit)：协议数据单元。
SDU(Service Data Unit)：服务数据单元。
在本公开中，将从上层接收或发往上层的数据称为SDU，将发往下层或从下层接收的数据称为PDU。例如，PDCP实体从上层接收的数据或发往上层的数据称为PDCP SDU；PDCP实体从RLC实体接收到的数据或发往RLC实体的数据称为PDCP PDU(也就是RLC SDU)。RLC实体从PDCP实体接收到的数据称为RLC SDU，RLC实体递交到下层(即，媒体访问控制(MAC)层)的数据称为RLC PDU，包括RLC数据PDU和RLC控制PDU。RLC数据PDU由来自上层的RLC SDU生成，RLC控制PDU是状态PDU，所述状态PDU用于提供对RLC SDU或其分段的肯定确认ACK或否定确认NACK。
目前最新达成的3GPP TS38.322版本1.0.0(具体见3GPP提案R2-1709752，在此提案中记为版本0.3.0)中的图4.2.1.3.1-1示出了RLC AM实体模型，在本文中以图1示出。如图1所示，AM RLC实体发送端为来自PDCP实体的RLC SDU生成RLC头部(header)并将生成的RLC头部存储在发送缓存区中。当接收到来自下层的数据发送指示时，为RLC SDU增加RLC头部后递交给下层。如果RLC SDU加上RLC头部后超过了下层指示的可发送数据大小，则对RLC SDU进行分段并修改对应的头部，然后为RLC SDU分段增加RLC头部并递交给下层。在图1所示RLC AM实体模型中，AM RLC实体的发送缓存区存储的是RLC SDU。
然而，这种在发送缓存区中存储RLC SDU及其关联的RLC头部的处理方式，在RLC实体接收到下层的数据发送指示时，为RLC SDU增加头部后再发送给下层，增加了数据发送时延。
以下将参照图2，对根据本公开示例性实施例的在UE处执行的用于处理RLC SDU的方法进行描述。图2示出了根据本发明示例性实施例的在UE处执行的用于处理RLC SDU的方法200的流程图。具体地，方法200 在UE中的RLC实体处执行。
如图2所示，方法200可以包括步骤S201、S202和S203。
在步骤S201中，RLC实体可以通过向来自上层实体(例如，PDCP实体)的RLC SDU增加RLC头部来生成RLC数据PDU，也可以描述为，RLC实体将来自上层实体(例如，PDCP实体)的RLC SDU映射为RLC数据PDU。
在步骤S202中，将所生成的RLC数据PDU存储在发送缓存区中。
在步骤S203中，当接收到来自下层实体(例如，MAC实体)的数据发送指示时，将在发送缓存区中存储的RLC数据PDU发送给下层实体。
如果在发送缓存区中存储的RLC数据PDU超过所述数据发送指示中所指示的可发送数据大小，则对所述RLC数据PDU进行分段并修改RLC头部后发送(也可以描述为“递交”，下同)给下层实体。换言之，当递交给下层的RLC数据PDU包含RLC SDU的分段，则对发送缓存区存储的RLC数据PDU或其对应的RLC SDU进行分段并修改RLC头部后发送给下层实体。
在一示例性实施例中，所述RLC实体可以是AM RLC实体。在该示例性实施例中，方法200具体在AM RLC实体的发送端处执行。稍后将结合图3(a)和3(b)对该示例性实施例进行描述。
在该示例性实施例中，方法200还可以包括：在AM RLC实体处维护发送状态变量TX_Next，所述发送状态变量用于存储将分配给下一个从上层实体接收到的RLC SDU的序列号；以及AM RLC实体在将当前发送状态变量TX_Next的值关联到一个从上层实体接收到的RLC SDU之后将TX_Next的值增加1。
在另一示例性实施例中，所述RLC实体可以是UM RLC发送实体。在该示例性实施例中，方法200具体在UM RLC发送实体处执行。稍后将结合图4对该示例性实施例进行描述。
相应地，本公开的技术方案提出将图1所示的RLC AM实体模型修改为如图3(a)或3(b)所示。图3(a)和3(b)分别示出了根据本公开示例性实施例的RLC AM实体模型的示意图。
如图3(a)和3(b)所示，AM RLC实体的发送端可以在步骤S201中向来自例如PDCP实体的RLC SDU增加RLC头部，以生成AMD PDU，也可以描述为，将来自例如PDCP实体的RLC SDU映射为AMD PDU。
在步骤S202中，AM RLC实体的发送端可以将AMD PDU存储在发送缓存区中。
在步骤S203中，AM RLC实体的发送端接收到来自例如MAC实体的数据发送指示时，将发送缓存区存储的AMD PDU递交给MAC实体。
如果在发送缓存区中存储的AMD PDU超过所述数据发送指示中所指示的可发送数据大小，则对所述RLC数据PDU进行分段并修改RLC头部后发送给下层实体。换言之，当递交给下层的AMD PDU包含RLC SDU的分段，则对发送缓存区存储的AMD PDU或其对应的RLC SDU进行分段并修改RLC头部后发送给下层实体。
图3(a)或3(b)示出的修改后的RLC AM实体模型至少包括以下模块(也可称为功能)：发送缓存区模块、重传缓存模块、分段和修改RLC头部模块、RLC控制模块、增加RLC头部模块。
下面具体描述AM RLC实体发送端各个模块的作用及各个模块间的相互关系。
发送缓存区模块用于将来自例如PDCP实体的RLC SDU映射为AMD PDU，即，为RLC SDU关联一个序列号TX_Next并通过将AMD PDU的序列号设置为TX_Next的值来构建AMD PDU，将AMD PDU存储在发送缓存区中。
重传缓存模块用于存储等待重传的AMD PDU或已经递交给下层但尚未确认发送成功的AMD PDU。AMD PDU在递交给下层时会同时存储在重传缓存区中。当接收到来自对等实体的状态PDU中指示某个AMD PDU未发送成功时，从重传缓存区中取出所述AMD PDU递交给下一层。如果所述AMD PDU超过了下层指示的可发送数据的大小，则将所述AMD PDU递交给分段和修改RLC头部模块以对所述AMD PDU进行分段。
分段和修改RLC头部模块根据下层指示的可发送数据的大小对存储在发送缓存区或重传缓存区的AMD PDU进行分段或重分段并修改RLC头部后递交给下层实体。
RLC控制模块根据AM RLC实体接收端接收到的RLC PDU产生状态 PDU的负载。
增加RLC头部模块为来自RLC控制模块的数据(即状态PDU的负载)增加头部生成RLC控制PDU或状态PDU。
可选地，3GPP TS38.322版本1.0.0中的5.1.3.1.1节中AM RLC实体对来自上层的RLC SDU的处理流程可修改为如下过程：
对于每个来自上层的RLC SDU，AM RLC实体为所述RLC SDU关联值为TX_Next的序列号SN，并通过将AMD PDU的SN设置为TX_Next的值来构建所述AMD PDU。将所述AMD PDU存储在发送缓存区中。设置TX_Next的值为TX_Next+1。
可选地，当AMD PDU(或RLC SDU)需要进行分段时，AM RLC实体修改所述AMD PDU的RLC头部(或RLC SDU所关联的头部)。分段得到的AMD PDU的序列号与被分段的AMD PDU相同，或者分段得到的AMD PDU的序列号与对应的RLC SDU的序列号相同。
可选地，将修改后的RLC头部和对应的RLC SDU分段存储在发送缓存区中。具体的，当AMD PDU(或RLC SDU)需要进行分段时，例如一个RLC SDU分成两段，分别称为第一段和第二段，为RLC SDU的各分段生成包含分段偏移SO的RLC头部，且所述分段的RLC头部中包括的序列号与原RCL SDU相同。需要说明的是，所述分段操作也适用于UMD PDU或UM RLC发送实体。
本公开中，AM RLC实体维护发送状态变量TX_Next，所述变量用于存储下一个新产生的AMD PDU的序列号或下一个将被分配的序列号或已分配的序列号的下一个或下一个将为从上层接收到的RLC SDU分配的序列号或将分配给从下一个上层接收到的RLC SDU的序列号或将分配给从上层接收到的新的RLC SDU的序列号。如果序列号用12比特标识，则TX_Next取值范围为0到4095，TX_Next取值＝算数运算得到的值模(modulo)4096；如果序列号用18比特标识，则TX_Next取值范围为0到262143，TX_Next取值＝算数运算得到的值模(modulo)262144。发送状态变量TX_Next的初始值为0，所述变量可以通过以下两种方式之一更新：
方式一：TX_Next的值在AM RLC实体将当前TX_Next关联到一个从上层接收到的RLC SDU时更新或增加1。可选的，当AM RLC实体发送端 支持数据预处理时才执行此操作。
方式二：TX_Next的值在AM RLC实体发送序列号为TX_Next的AMD PDU时更新或增加1。可选的，当AM RLC实体发送端不支持数据预处理时才执行此操作。
可选的，AM RLC实体发送端是否支持数据预处理是通过RRC信令配置。可选的，通过媒体访问MAC控制元素CE动态激活和/或去激活数据预处理，或者通过RLC控制PDU动态激活和/或去激活数据预处理。
可选的，对于从上层接收到的RLC SDU，AM RLC实体可以为所述RLC SDU分配序列号SN＝TX_Next并构建AMD PDU，所述AMD PDU的序列号置为TX_Next；然后，设置TX_Next的值为TX_Next+1(即，将TX_Next的值增加1)。
为了达到非确认UM RLC发送实体和AM RLC实体发送端的操作一致性，本公开的技术方案提出将3GPP TS38.322版本1.0.0中的图4.2.1.2.1-1所示的两个UM对等实体模型修改为图4示出的两个UM对等实体模型。
下面具体描述UM RLC发送实体中各个模块的作用及模块间的相互关系。
在图4示出的UM-RLC发送实体模型中，UM RLC发送实体包含至少以下两个模块(也可称为功能)：发送缓存区模块和分段和修改RLC头部模块。其中，发送缓存区模块将来自例如PDCP实体的RLC SDU映射为UMD PDU并存储在发送缓存区中。在接收到来自下层的传输机会(即发送数据)的指示时，分段和修改RLC头部模块按照来自下层实体的数据发送指示所指示的可发送的数据大小将发送缓存区中的UMD PDU向下层发送或将UMD PDU或其对应的RLC SDU分段并修改RLC头部后向下层发送。
本公开的上述示例性实施例所述的将RLC数据PDU存储在发送缓存区中的实现机制，使得AM RLC实体发送端或UM RLC发送实体可以在接收到来自下层的数据发送指示时直接将存储在发送缓存区中的RLC数据PDU发送给下层，降低了数据发送时延。
在另一示例性实施例中，UE的RLC实体可以将RLC SDU和关联的RLC头部存储在发送缓存区中。
相应地，本公开的技术方案提出可以如下修改3GPP TS38.322版本1.0.0 中5.1.3.1.1节关于RLC发送端的处理流程。
AM RLC实体接收来自上层实体(例如，PDCP实体)的RLC SDU，并为所述RLC SDU生成序列号为TX_Next的值的RLC头部(或为RLC SDU关联值为TX_Next的序列号SN，生成RLC头部)。将所述RLC头部和/或RLC SDU存储在发送缓存区中。设置TX_Next的值为TX_Next+1(即，将TX_Next的值增加1)。
可选地，当需要对RLC SDU进行分段时，AM RLC实体修改所述RLC SDU对应的头部，并将修改后的头部连同RLC SDU分段存储在发送缓存区中。
可选地，当递交AMD PDU到下层时，AM RLC实体发送端为RLC SDU或RLC SDU分段增加RLC头部。或者，当递交AMD PDU到下层时，AM RLC实体发送端将AM PDU的序列号设置为对应RLC SDU关联的序列号。或者，当递交AMD PDU到下层时，AM RLC实体发送端为RLC SDU或RLC SDU分段增加RLC头部来构建AMD PDU。或者，如果递交到下层的AMD PDU包含RLC SDU分段，则将AMD PDU的序列号设置为对应RLC SDU的序列号。
以下将参照图5，对根据本发明示例性实施例的UE的结构进行描述。图5示意性地示出了根据本发明示例性实施例的执行用于处理RLC SDU的方法的UE的结构框图。UE 500可以用于执行参考图2描述的方法200。为了简明，在此仅对根据本公开示例性实施例的UE的示意性结构进行描述，而省略了如前参考图2描述的方法200中已经详述过的细节。
如图5所示，UE 500包括用于外部通信的通信接口501；处理单元或处理器502，该处理器502可以是单个单元或者多个单元的组合，用于执行方法的不同步骤；存储器503，其中存储有计算机可执行指令，所述指令在被处理器502执行时，可以使UE 500的RLC实体执行以下过程：
通过向来自上层实体的RLC SDU增加RLC头部来生成RLC数据协议数据单元PDU；以及
将所生成的RLC数据PDU存储在发送缓存区中。
所述指令在被处理器502执行时，还可以使UE 500的RLC实体执行以下过程：
当RLC实体接收到来自下层实体的数据发送指示时，将在发送缓存区中存储的RLC数据PDU发送给下层实体。
在一示例性实施例中，如果在发送缓存区中存储的RLC数据PDU超过所述数据发送指示中所指示的可发送数据大小，则对所述RLC数据PDU进行分段并修改RLC头部后发送给下层实体。
如前所述，所述RLC实体可以是AM RLC实体，也可以是UM RLC发送实体。在RLC实体是AM RLC实体的示例性实施例中，上述过程具体在AM RLC实体的发送端处执行；而在RLC实体是UM RLC实体的示例性实施例中，上述过程具体在UM RLC发送实体处执行。
在一示例性实施例中，所述指令在被处理器502执行时，还可以使UE500的RLC实体执行以下过程：
在AM RLC实体处维护发送状态变量TX_Next，所述发送状态变量用于存储将分配给下一个从上层实体接收到的RLC SDU的序列号；以及
AM RLC实体在将当前发送状态变量TX_Next的值关联到一个从上层实体接收到的RLC SDU之后将TX_Next的值增加1。
在RAN2 NR Adhoc#2次会议上达成分离承载(split bearer)可以采用与单载波类似的数据预处理；在RAN2#99次会议上达成NR UE可在接收到下层请求(或数据发送请求)前对上行分离承载进行数据预处理，且在接收到来自下层实体(例如，MAC实体)的请求前将数据(即预处理后的数据)递交给下层实体。从RLC层来看，RLC实体接收到来自例如PDCP实体的数据RLC SDU，并生成RLC头部(或为所述RLC SDU关联一个序列号)。在RLC实体的缓存区(所述缓存区可以是发送缓存区)中，可能存在尚未生成RLC头部的RLC SDU(或尚未关联序列号的RLC SDU)和已经生成RLC头部的RLC SDU或RLC数据PDU。然而目前，并未针对在RLC实体接收到来自PDCP实体(或称上层实体)的丢弃特定RLC SDU的指示时RLC实体的发送端应该丢弃缓存区中的哪些数据提出解决方案。
为此，本公开提出了在UE处执行的用于丢弃RLC SDU的方案。
以下将参照图6，对根据本公开示例性实施例的在UE处执行的用于丢弃RLC SDU的方法的进行描述。
图6示出了根据本发明示例性实施例的在UE处执行的用于丢弃RLC SDU的方法600的流程图。具体地，方法600在UE中的RLC实体处执行。如前所述，所述RLC实体可以是AM RLC实体，也可以是UM RLC发送实体。在RLC实体是AM RLC实体的示例性实施例中，方法600具体在AM RLC实体的发送端处执行；而在RLC实体是UM RLC实体的示例性实施例中，方法600具体在UM RLC发送实体处执行。
如图6所示，方法600可以包括步骤S601至S606。
在步骤S601中，RLC实体可以接收来自上层实体(例如，PDCP实体)的丢弃特定RLC SDU的指示。
在RLC实体接收到来自上层实体(例如，PDCP实体)的丢弃特定RLC SDU的指示之后，RLC实体可以停止为来自上层的RLC SDU分配或关联序列号。
在步骤S602中，RLC实体可以确定所述特定RLC SDU或所述特定RLC SDU的任一分段是否已经生成相应的RLC数据PDU，也可以描述为，确定所述特定RLC SDU或所述特定RLC SDU的任一分段是否映射到相应的RLC数据PDU。
如果所述特定RLC SDU或所述特定RLC SDU的任意分段尚未生成相应的RLC数据PDU，则执行步骤S603，其中RLC实体可以丢弃所述特定RLC SDU。
如果所述特定RLC SDU或所述特定RLC SDU的至少一个分段已经生成了相应的RLC数据PDU，则执行步骤S604，其中RLC实体可以确定所述特定RLC SDU或所述特定RLC SDU的任意分段生成的相应RLC数据PDU是否已向下层发送。
如果所述特定RLC SDU或所述特定RLC SDU的任意分段生成的相应RLC数据PDU尚未向下层发送，则执行步骤S605，其中RLC实体丢弃所述RLC SDU和/或相应的RLC数据PDU。
具体地，如果RLC SDU已经映射为RLC数据PDU，但是所述RLC数据PDU尚未向下层发送，则丢弃所述RLC SDU和/或对应的RLC数据PDU。或者，如果RLC SDU已经映射为RLC数据PDU，但所述RLC数据PDU或RLC数据PDU的头部不包含序列号，则UM RLC发送实体丢弃所述RLC数据PDU和/或RLC SDU。
如果RLC SDU的至少一个分段已经映射为RLC数据PDU，但是所述RLC SDU的任意分段映射到的RLC数据PDU尚未向下层发送，则丢弃所述RLC SDU和/或所述RLC SDU的分段和/或所述RLC SDU的分段对应的RLC数据PDU，或者丢弃所述RLC SDU和/或所述RLC SDU的所有分段和/或所有分段对应的RLC数据PDU。或者，如果RLC SDU已经映射为RLC数据PDU，且所述RLC数据PDU或RLC数据PDU的头部包含序列号，但是所述RLC SDU的任意分段映射到的RLC数据PDU尚未递交给下层或所述RLC SDU(或对应RLC数据PDU)的第一个分段对应的RLC数据PDU尚未发送给下层，则UM RLC发送实体丢弃所述RLC SDU的所有分段或分段对应的RLC数据PDU和/或RLC SDU。
接下来，方法600还可以包括：在被丢弃的RLC SDU或其分段已经关联了序列号、或相应的RLC数据PDU被丢弃的情况下，将所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU对应的序列号重新分配给其他RLC SDU或其分段或相应的RLC数据PDU；或者，为序列号比所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU的序列号大的RLC SDU和/或其分段和/或相应的RLC数据PDU重新分配序列号，以避免接收端的序列号间隔(SN gap)。
接下来，方法600还可以包括：设置TX_Next的值为TX_Next-1，即将TX_Next的值减少1。
接下来，方法600还可以包括：继续为来自上层实体的RLC SDU分配或关联序列号。
可选地，在步骤S603中，如果所述被丢弃的RLC SDU已经关联了序列号，则可以执行上述重新分配序列号的步骤或重新分配序列号和设置TX_Next的值为TX_Next-1的步骤。
可选地，如果所述特定RLC SDU或所述特定RLC SDU的至少一个分段生成的相应RLC数据PDU已向下层发送，则执行步骤S606，其中RLC实体不丢弃所述特定RLC SDU的相应RLC数据PDU。
以下将参照图7，对根据本发明示例性实施例的UE的结构进行描述。图7示意性地示出了根据本发明示例性实施例的执行用于丢弃RLC SDU的方法的UE的结构框图。UE 700可以用于执行参考图6描述的方法 600。为了简明，在此仅对根据本公开示例性实施例的UE的示意性结构进行描述，而省略了如前参考图6描述的方法600中已经详述过的细节。如图7所示，UE 700包括用于外部通信的通信接口701；处理单元或处理器702，该处理器702可以是单个单元或者多个单元的组合，用于执行方法的不同步骤；存储器703，其中存储有计算机可执行指令，所述指令在被处理器702执行时，可以使UE 700的RLC实体执行以下过程：
接收来自上层实体的丢弃特定RLC SDU的指示；以及
在确定所述特定RLC SDU或所述特定RLC SDU的至少一个分段已经生成相应的RLC数据PDU、但是所述RLC数据PDU尚未向下层发送的情况下，丢弃所述RLC数据PDU。
在一示例性实施例中，所述指令在被处理器702执行时，还可以使UE700的RLC实体执行以下过程：
在被丢弃的RLC SDU或其分段已经关联了序列号、或相应的RLC数据PDU被丢弃的情况下，将所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU对应的序列号重新分配给其他RLC SDU或其分段或相应的RLC数据PDU；或
为序列号比所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU的序列号大的RLC SDU和/或其分段和/或相应的RLC数据PDU重新分配序列号。
如前所述，所述RLC实体可以是AM RLC实体，也可以是UM RLC发送实体。在RLC实体是AM RLC实体的示例性实施例中，上述过程具体在AM RLC实体的发送端处执行；而在RLC实体是UM RLC实体的示例性实施例中，上述过程具体在UM RLC发送实体处执行。
需要说明的是，本公开中所述在UE处执行的用于处理RLC SDU的方法和丢弃RLC SDU的流程也可以应用于基站的RLC实体。
运行在根据本发明的设备上的计算机可执行指令或者程序可以是通过控制中央处理单元(CPU)来使计算机实现本发明的实施例功能的程序。该程序或由该程序处理的信息可以临时存储在易失性存储器(如随机存取存储器RAM)、硬盘驱动器(HDD)、非易失性存储器(如闪速存储器)、 或其他存储器系统中。
用于实现本发明各实施例功能的计算机可执行指令或程序可以记录在计算机可读存储介质上。可以通过使计算机系统读取记录在所述记录介质上的程序并执行这些程序来实现相应的功能。此处的所谓“计算机系统”可以是嵌入在该设备中的计算机系统，可以包括操作系统或硬件(如外围设备)。“计算机可读存储介质”可以是半导体记录介质、光学记录介质、磁性记录介质、短时动态存储程序的记录介质、或计算机可读的任何其他记录介质。
用在上述实施例中的设备的各种特征或功能模块可以通过电路(例如，单片或多片集成电路)来实现或执行。设计用于执行本说明书所描述的功能的电路可以包括通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现场可编程门阵列(FPGA)、或其他可编程逻辑器件、分立的门或晶体管逻辑、分立的硬件组件、或上述器件的任意组合。通用处理器可以是微处理器，也可以是任何现有的处理器、控制器、微控制器、或状态机。上述电路可以是数字电路，也可以是模拟电路。因半导体技术的进步而出现了替代现有集成电路的新的集成电路技术的情况下，本发明的一个或多个实施例也可以使用这些新的集成电路技术来实现。
此外，本发明并不局限于上述实施例。尽管已经描述了所述实施例的各种示例，但本发明并不局限于此。安装在室内或室外的固定或非移动电子设备可以用作终端设备或通信设备，如AV设备、厨房设备、清洁设备、空调、办公设备、自动贩售机、以及其他家用电器等。
如上，已经参考附图对本发明的实施例进行了详细描述。但是，具体的结构并不局限于上述实施例，本发明也包括不偏离本发明主旨的任何设计改动。另外，可以在权利要求的范围内对本发明进行多种改动，通过适当地组合不同实施例所公开的技术手段所得到的实施例也包含在本发明的技术范围内。此外，上述实施例中所描述的具有相同效果的组件可以相互替代。

Claims (10)

  1. 一种在用户设备UE处执行的方法，包括：
    在UE的无线链路控制RLC实体处，
    接收来自上层实体的丢弃特定RLC服务数据单元SDU的指示；以及
    在确定所述特定RLC SDU或所述特定RLC SDU的至少一个分段尚未向下层实体发送的情况下，丢弃所述RLC数据SDU。
  2. 根据权利要求1所述的方法，还包括：在被丢弃的RLC SDU或其分段已经关联了序列号、或相应的RLC数据PDU被丢弃的情况下，
    将所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU对应的序列号重新分配给其他RLC SDU或其分段或相应的RLC数据PDU，或
    为序列号比所述被丢弃的RLC SDU或其分段或相应的RLC数据PDU的序列号大的RLC SDU和/或其分段和/或相应的RLC数据PDU重新分配序列号。
  3. 根据权利要求1至2中任一项所述的方法，其中所述RLC实体包括：
    确认模式AM RLC实体，和/或
    非确认模式UM RLC发送实体。
  4. 一种在用户设备UE处执行的方法，包括：
    在UE的无线链路控制RLC实体处，
    通过向来自上层实体的RLC服务数据单元SDU增加RLC头部来生成RLC数据协议数据单元PDU；以及
    将所生成的RLC数据PDU存储在发送缓存区中。
  5. 根据权利要求4所述的方法，还包括：
    当RLC实体接收到来自下层实体的数据发送指示时，将在发送缓存区中存储的RLC数据PDU发送给下层实体。
  6. 根据权利要求5所述的方法，其中
    如果在发送缓存区中存储的RLC数据PDU超过所述数据发送指示中所指示的可发送数据大小，则对所述RLC数据PDU进行分段并修改RLC头部后发送给下层实体。
  7. 根据权利要求4至6中任一项所述的方法，其中所述RLC实体包括：
    确认模式AM RLC实体，和/或
    非确认模式UM RLC发送实体。
  8. 根据权利要求7所述的方法，还包括：
    在AM RLC实体处维护发送状态变量TX_Next，所述发送状态变量TX_Next用于存储将分配给下一个从上层实体接收到的RLC SDU的序列号；以及
    AM RLC实体在将当前发送状态变量TX_Next的值关联到一个从上层实体接收到的RLC SDU之后将TX_Next的值增加1。
  9. 一种用户设备UE，包括：
    通信接口，配置用于通信；
    处理器；以及
    存储器，存储有计算机可执行指令，所述指令在被处理器执行时，使所述UE执行根据权利要求1至8中任一项所述的方法。
  10. 一种计算机可读介质，在其上存储有指令，所述指令在由处理器执行时，使所述处理器执行根据权利要求1至8中任一项所述的方法。
PCT/CN2018/107602 2017-09-27 2018-09-26 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质 WO2019062760A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201710927143.0 2017-09-27
CN201710927143.0A CN109561465A (zh) 2017-09-27 2017-09-27 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质

Publications (1)

Publication Number Publication Date
WO2019062760A1 true WO2019062760A1 (zh) 2019-04-04

Family

ID=65864066

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/107602 WO2019062760A1 (zh) 2017-09-27 2018-09-26 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质

Country Status (3)

Country Link
CN (1) CN109561465A (zh)
TW (1) TW201921977A (zh)
WO (1) WO2019062760A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117641420A (zh) * 2022-08-09 2024-03-01 华为技术有限公司 数据处理方法及装置
CN117641444A (zh) * 2022-08-09 2024-03-01 华为技术有限公司 数据处理方法及装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101981962A (zh) * 2008-03-31 2011-02-23 日本电气株式会社 隐秘处理设备、隐秘处理方法和隐秘处理程序
CN102450051A (zh) * 2009-05-27 2012-05-09 日本电气株式会社 无线通信装置以及数据接收方法
CN102469511A (zh) * 2010-11-15 2012-05-23 中兴通讯股份有限公司 一种分组数据汇聚协议层处理数据的方法及系统

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101981962A (zh) * 2008-03-31 2011-02-23 日本电气株式会社 隐秘处理设备、隐秘处理方法和隐秘处理程序
CN102450051A (zh) * 2009-05-27 2012-05-09 日本电气株式会社 无线通信装置以及数据接收方法
CN102469511A (zh) * 2010-11-15 2012-05-23 中兴通讯股份有限公司 一种分组数据汇聚协议层处理数据的方法及系统

Also Published As

Publication number Publication date
CN109561465A (zh) 2019-04-02
TW201921977A (zh) 2019-06-01

Similar Documents

Publication Publication Date Title
CN110012454B (zh) 用户设备和相关方法
JP6062997B2 (ja) 無線リンク制御プロトコルデータユニットを生成するための方法および装置
TWI462626B (zh) 支援再配置無線鏈結控制參數無線通信方法及裝置
JP7376363B2 (ja) 無線リンク制御ステータスのレポーティング
US20090175163A1 (en) Method and apparatus of performing packet data convergence protocol re-establishment
CN110249659B (zh) 服务质量流重新定位
TW200929979A (en) Method and apparatus for combined medium access control and radio link control processing
WO2020156569A1 (zh) 发送rlc状态报告的方法、设备和存储介质
WO2019062760A1 (zh) 服务数据单元处理方法、丢弃方法、相应的用户设备和计算机可读介质
US20220132362A1 (en) Wireless communication methods for adaptive entity and rlc entity, and communication device
US11563524B2 (en) Wireless communication method and device
WO2019134168A1 (en) Radio link control (rlc) acknowledged mode (am) data reception
WO2019192425A1 (zh) 确认模式rlc实体及其发送/重传方法、通信设备
TWI712328B (zh) 無線電通訊方法和設備
WO2019096215A1 (zh) 无线通信方法和设备
WO2019153937A1 (zh) 无线通信方法和设备
EP4144010A2 (en) Methods and apparatus for efficient packet transmission

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

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

Country of ref document: EP

Kind code of ref document: A1