WO2015139557A1 - 分组数据汇聚协议pdcp实体及其执行的方法 - Google Patents

分组数据汇聚协议pdcp实体及其执行的方法 Download PDF

Info

Publication number
WO2015139557A1
WO2015139557A1 PCT/CN2015/073625 CN2015073625W WO2015139557A1 WO 2015139557 A1 WO2015139557 A1 WO 2015139557A1 CN 2015073625 W CN2015073625 W CN 2015073625W WO 2015139557 A1 WO2015139557 A1 WO 2015139557A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdcp
entity
sdu
smaller
sequence number
Prior art date
Application number
PCT/CN2015/073625
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 夏普株式会社
Priority to US15/126,481 priority Critical patent/US20170085492A1/en
Publication of WO2015139557A1 publication Critical patent/WO2015139557A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using 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
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/50—Queue scheduling
    • H04L47/62—Queue scheduling characterised by scheduling criteria
    • H04L47/624—Altering the ordering of packets in an individual queue

Definitions

  • the present invention relates to mobile communications, and in particular to a packet data convergence protocol PDCP entity and a method for performing the same, for enabling a receiving side PDCP entity to deliver an out-of-order received PDCP SDU to an upper layer as early as possible.
  • the layer 2 (User-Plane Protocol Stack) of the 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) system consists of 3 sub-layers, from high to low: packet data convergence protocol ( Packet Data Convergence Protocol (PDCP) layer, Radio Link Control (RLC) layer, and Media Access Control layer.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control
  • MDU Media Access Control
  • a Service Data Unit (SDU) is received from a higher layer to provide services for the layer
  • PDU Protocol Data Unit
  • the RLC layer receives packets from the PDCP. These packets are PDCP PDUs for the PDCP layer but RLC SDUs for the RLC layer.
  • the PDCP entity used to transmit the PDCP PDU is called PDCP Tx
  • the RLC entity used to transmit the RLC PDU is called RLC Tx.
  • the process is reversed, with each layer sending an SDU to the upper layer and the upper layer receiving it as a PDU.
  • the PDCP entity for receiving the PDCP PDU is called PDCP Rx
  • the RLC entity for receiving the RLC PDU is called RLC Rx.
  • the PDCP SDU is identified by a PDCP sequence number (SN)
  • the PDCP SDU has the same sequence number as the corresponding PDCP PDU and the RLC SDU
  • the RLC PDU is identified by the RLC sequence number.
  • the PDCP sequence number and the RLC sequence number can be recycled.
  • the new PDCP SDU is numbered again from the minimum value, but the corresponding superframe number is incremented by 1.
  • a COUNT consisting of a PDCP sequence number and a Hyper Frame Number (HFN) uniquely identifies a PDCP SDU.
  • each radio bearer has a PDCP entity and an RLC entity.
  • Each base station also known as a NodeB or evolved NodeB (eNB)
  • each user equipment has one MAC entity.
  • the user equipment may be a user terminal, a user node, a mobile terminal or a tablet.
  • the function of the RLC layer is implemented by an RLC entity, and the RLC entity can be configured into one of three data transmission modes: (1) Transparent Mode (TM); (2) Acknowledged Mode (AM); (3) Unacknowledged Mode (UM).
  • TM Transparent Mode
  • AM Acknowledged Mode
  • UM Unacknowledged Mode
  • the RLC entity is responsible for the sequential transmission and reception of the RLC SDU.
  • the RLC sender the RLC entity in the base station or the user equipment re-segment the RLC SDUs from the PDCP entity according to the size indicated by the MAC layer, and add an RLC header to form an RLC PDU and send the RLC PDUs in sequence.
  • the RLC header includes an RLC SN allocated for the RLC PDU.
  • the RLC entity receives the RLC PDUs from the lower layer, reorders and concatenates the RLC PDUs in ascending order of RLC SN, and delivers the reassembled RLC SDUs to the PDCP layer in order from small to large.
  • the 3GPP LTE Release 12 standard under development includes standardization work for user equipments having dual connectivity capabilities, a primary base station (Master eNB, MeNB), and a secondary base station (Secondary eNB, SeNB).
  • the primary base station is responsible for maintaining the Radio Resource Management (RRM) measurement configuration of the user equipment and requesting the secondary base station to provide additional equipment for the user equipment based on the received measurement report or traffic conditions or bear type. Resources.
  • RRM Radio Resource Management
  • the secondary base station configures the serving cell for the user equipment or rejects the request due to insufficient resources.
  • the option 3C shown in FIG. 1 has the following features: (1) the primary base station communicates with the Serving Gateway (S-GW) through the S1-U interface; (2) the bearer is separated in the primary base station; (3) for the separated bearer (split bearer), there are corresponding RLC entities in the primary base station and the secondary base station.
  • the RLC entity located at the secondary base station interacts with the upper layer (ie, the PDCP entity located at the primary base station) through an Xn interface, which includes the X2 interface.
  • the serving cells configured for the user equipment are classified into two categories: (1) a primary cell group (MCG) composed of serving cells of the MeNB (2) A Secondary Cell Group (SCG) consisting of a serving cell of the SeNB.
  • MCG primary cell group
  • SCG Secondary Cell Group
  • the user equipment with dual connectivity capability configures one PDCP entity and two RLC entities for the split bearer, where the PDCP entity corresponds to the PDCP entity in the MCG.
  • the one RLC entity corresponds to an RLC entity in the MCG
  • the another RLC entity corresponds to an RLC entity in the SCG.
  • each PDCP Rx corresponds to only one RLC Rx.
  • the reordering function of the RLC receiving entity ensures that the PDCP Rx receives the PDCP PDUs in order from the RLC layer.
  • one PDCP Rx corresponds to two RLC Rx, and the PDCP PDU received by the PDCP Rx from the two RLC Rx is out of order. Therefore, PDCP Rx needs to reorder the PDCP PDUs from the two RLC Rx.
  • the PDCP reordering function proposed at the 3GPP TSG RAN WG2 Meeting #85 meeting will adopt a UM RLC similar t-Reordering timer based rearrangement method.
  • the main idea of the method is: PDCP Rx receives PDCP PDUs from two RLC Rx, and when receiving unscheduled PDCP PDUs, stores the unordered PDCP PDUs in the reordering buffer and starts t -Reordering timer, waiting for the missing PDCP PDU to arrive.
  • the PDCP SDUs that have been received in order are delivered to the upper layer.
  • the present invention aims to provide a mechanism for a receiving-side PDCP entity to deliver an unordered PDCP SDU to an upper layer as early as possible.
  • a first aspect of the present invention provides a method performed by a packet data convergence protocol PDCP entity on a receiving side, comprising: an unscheduled packet data convergence protocol received from a lower layer entity of a PDCP entity
  • the protocol data unit PDCP PDU is mapped to the PDCP SDU and stored in the reordering buffer; it is determined whether the sequence number of the missing PDCP SDU is smaller than the smaller of the maximum sequence numbers of the PDCP SDUs received by the PDCP entity from the two lower layer entities respectively.
  • the sequence number stored in the reordering buffer is smaller than the missing PDCP.
  • the PDCP SDU of the sequence number of the SDU and the PDCP SDU whose sequence number is greater than the sequence number of the missing PDCP SDU and which is consecutive to the sequence number of the missing PDCP SDU are delivered to the upper entity of the PDCP entity.
  • the method according to the first aspect of the present invention it is possible to judge whether the sequence number of the missing PDCP SDU is smaller than the smaller one in descending order of the serial number of the missing PDCP SDU, and if a missing PDCP is judged If the sequence number of the SDU is smaller than the smaller one, it is no longer determined whether the sequence number of the remaining missing PDCP SDU is smaller than the smaller one.
  • a second aspect of the present invention provides another method performed by a packet data convergence protocol PDCP entity on a receiving side, comprising: aggregating packet data that is received from a lower layer entity of a PDCP entity and that is not arriving in order
  • the protocol protocol data unit PDCP PDU is mapped to the PDCP SDU and stored in the reordering buffer; and the sequence number stored in the reordering buffer is less than or equal to the maximum sequence of PDCP SDUs received by the PDCP entity from the two lower layer entities respectively
  • the smaller of the numbers, the PDCP SDU and its subsequent consecutive PDCP SDUs are submitted to the upper entity of the PDCP entity.
  • the sequence number stored in the reordering buffer is less than or equal to the PDCP of the smaller one of the maximum sequence numbers of PDCP SDUs received by the PDCP entity from the two lower layer entities, respectively.
  • the upper layer entity that the SDU and its subsequent consecutive PDCP SDUs deliver to the PDCP entity may include: determining the PDCP SDU of the PDCP SDU stored in the reordering buffer according to the sequence number of the PDCP SDUs stored in the reordering buffer from the largest to the smallest Whether the sequence number is less than or equal to the smaller one, and if it is determined that the sequence number of one PDCP SDU is less than or equal to the smaller one, it is no longer determined whether the sequence number of the remaining PDCP SDUs is less than or equal to the smaller one. And the remaining PDCP SDUs, the determined PDCP SDU whose sequence number is smaller than the smaller one and the subsequent consecutive PDCP SDUs are delivered to the upper entity of the PDCP entity.
  • a third aspect of the present invention provides a method performed by a packet data convergence protocol PDCP entity on a transmitting side, comprising: deleting a PDCP SDU whose expiration timer has expired; and transmitting an indication to the PDCP entity on the receiving side that all or part of the The PDCP Control PDU of the expired PDCP SDU.
  • the PDCP Control PDU may indicate an expired PDCP SDU having the largest sequence number satisfying the condition that all PDCP SDUs whose sequence number is smaller than the sequence number of the expired PDCP SDU have been Expired or confirmed to be sent successfully.
  • the PDCP control PDU may indicate an expired PDCP SDU that meets the condition that the sequence number of the expired PDCP SDU is greater than the successfully transmitted PDCP SDU confirmed by two lower layer entities of the transmitting side PDCP entity respectively. The smaller of the largest serial numbers.
  • the PDCP Control PDU may include a plurality of fields, and one of the plurality of fields may indicate the expired PDCP SDU in the form of a sequence number or a bitmap.
  • the present invention also provides a packet data convergence PDCP entity corresponding to the methods of the first to third aspects.
  • the PDCP receiving entity can deliver the PDCP SDU to the upper layer as early as possible, thereby reducing the radio link delay and improving the reliability of the radio link.
  • 1 is a schematic diagram of a dual connectivity deployment option 3C given in 3GPP TR 36.842;
  • FIG. 2 is a flow chart showing a method for a PDCP receiving entity to deliver an unscheduled PDCP SDU to an upper layer as early as possible according to the first aspect of the present invention
  • Figure 3 is a flow chart showing an exemplary embodiment of a method in accordance with the first aspect of the present invention
  • FIG. 4 is a flow chart showing another example embodiment of a method in accordance with the first aspect of the present invention.
  • FIG. 5 is a flowchart showing a method for a PDCP receiving entity to deliver an unscheduled PDCP SDU to an upper layer as early as possible according to the second aspect of the present invention
  • FIG. 6 is a flowchart showing a method performed by a PDCP transmitting entity according to a third aspect of the present invention, which helps a PDCP receiving entity to deliver an unscheduled PDCP SDU to an upper layer as early as possible;
  • FIG. 7 is a schematic diagram showing a PDCP Control PDU that can be employed in a method in accordance with the third aspect of the present invention.
  • FIG. 8 is a schematic diagram showing a state of a PDCP transmitting entity buffer
  • FIG. 9 is a diagram showing, by a PDCP transmitting entity, whether a PDCP SDU is deleted from a PDCP receiving entity, according to an exemplary embodiment of the method of the third aspect of the present invention. Flow chart of the law;
  • Figure 10 is a block diagram showing the structure of a PDCP entity performing the method according to the first aspect of the present invention.
  • Figure 11 is a block diagram showing the structure of a PDCP entity performing the method according to the second aspect of the present invention.
  • Figure 12 is a block diagram of the structure of a PDCP entity performing the method in accordance with the third aspect of the present invention.
  • the method starts in step S210, and the packet data convergence protocol protocol data unit PDCP PDU received by the PDCP entity from the lower layer entity is not mapped to the PDCP SDU, and is stored in the reordering buffer.
  • the PDCP entity determines whether the sequence number of the missing PDCP SDU is smaller than the smaller of the maximum sequence numbers of the PDCP SDUs that the PDCP entity receives from the two lower layer entities respectively.
  • step S230 if the sequence number of the missing PDCP SDU is smaller than the smaller one, the PDCP entity will store the PDCP SDU whose sequence number in the reordering buffer is smaller than the sequence number of the missing PDCP SDU. And a PDCP SDU whose sequence number is greater than the sequence number of the missing PDCP SDU and is consecutive to the sequence number of the missing PDCP SDU is submitted to the upper entity.
  • FIGS 3 and 4 further illustrate a flow chart of two specific implementations of the above method.
  • the embodiment of the present invention only describes the operations performed when the user equipment is used as the receiving end in the case of the downlink and the operations performed when the MCG is used as the transmitting end, and those skilled in the art will understand that without departing from the present disclosure.
  • the process is also applicable to operations performed by the MCG as a receiving end during uplink communication and by the user equipment as a transmission The operation performed at the end.
  • the PDCP entity corresponding to the split bearer in the UE maintains three state variables Next_PDCP_RX_SN, MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the state variable Next_PDCP_RX_SN holds the next PDCP SDU sequence number that is desired to be received, and the initial value is 0.
  • the PDCP entity updates the Next_PDPC_RX_SN to the maximum sequence number of the PDCP SDU submitted to the upper layer every time after submitting the PDCP SDU to the upper layer.
  • the state variable MCG_PDCP_RX_SN holds the maximum sequence number of the PDCP SDU received from the RLC Rx corresponding to the MCG RLC Tx, the initial value of the MCG_PDCP_RX_SN is 0, and the serial number of the received PDCP SDU from the RLC Rx corresponding to the MCG RLC Tx
  • the MCG_PDCP_RX_SN is set to the sequence number of the received PDCP SDU
  • the state variable SCG_PDCP_RX_SN holds the maximum sequence number of the PDCP SDU received from the RLC Rx corresponding to the SCG RLC Tx, and the initial value is 0.
  • the SCG_PDCP_RX_SN is set to the sequence number of the received PDCP SDU.
  • the comparison of the size of the serial number refers to the comparison of the COUNT value corresponding to the serial number
  • the addition and subtraction operation of the serial number also refers to adding or subtracting the corresponding COUNT value. operating.
  • the PDCP entity receives the PDCP PDU from the lower layer.
  • the PDCP entity refers to a PDCP receiving entity corresponding to a separate bearer in the UE.
  • the PDCP entities mentioned in the subsequent steps refer to the PDCP receiving entities corresponding to the separated bearers in the UE, unless otherwise specified.
  • the PDCP entity determines whether the received PDCP PDU is from RLC Rx corresponding to MCG RLC Tx or RLC Rx corresponding to SCG RLC Tx. If the PDCP SDU is from the RLC Rx corresponding to the MCG RLC Tx, step 3003 is performed. If the PDCP SDU is from the RLC Rx corresponding to the SCG RLC Tx, step 3005 is performed.
  • step 3003 the PDCP entity determines whether the sequence number of the PDCP PDU is greater than a state variable MCG_PDCP_RX_SN. If yes, step 3004 is performed; otherwise, step 3007 is performed.
  • step 3004 the PDCP entity sets the value of the state variable MCG_PDCP_RX_SN Set to the serial number of the PDCP PDU.
  • step 3005 the PDCP entity determines whether the sequence number of the PDCP PDU is greater than a state variable SCG_PDCP_RX_SN. If yes, go to step 3006, otherwise, go to step 3007.
  • step 3006 the PDCP entity sets the value of the state variable SCG_PDCP_Rx_SN to the sequence number of the PDCP PDU.
  • step 3007 the PDCP entity determines whether the PDCP PDU arrives in order, and if so, performs step 3008; otherwise, step 3009 is performed.
  • the sequential arrival of the PDCP PDU means that the PDCP PDU sequence number is a minimum sequence number of the PDCP SDU waiting to be received (or referred to as a miss), that is, Next_PDCP_RX_SN. For example, suppose the maximum sequence number of the PDCP SDU that the PDCP entity has submitted to the upper layer is 4, and the PDCP SDUs that are not sequentially received in the PDCP reordering buffer are 6, 7, and 9. If the sequence number of the received PDCP PDU is 5, the PDCP PDU is said to arrive in order. If the sequence number of the received PDCP PDU is 8, the PDCP PDU is said to arrive out of order.
  • the PDCP entity deletes the PDCP PDU header and decomposes it into a PDCP SDU after decryption and IP header decompression.
  • the PDCP SDU and its subsequent consecutive PDCP SDUs are then handed over to the upper layer.
  • the PDCP entity updates Next_PDCP_RX_SN to the maximum sequence number of the PDCP SDU submitted to the upper layer plus one. For example, in the example described in step 3007, if the PDCP PDU sequence number received by the PDCP entity is 5, the PDCP entity decompresses the PDCP PDU with the sequence number 5 and decompresses the IP header into a sequence number of 5.
  • the PDCP SDUs are then successively delivered to the upper layer and the value of Next_PDCP_RX_SN is set to 8 in order to deliver the PDCP SDUs of sequence numbers 5, 6, and 7.
  • the PDCP entity updates the smaller one of the MCG_PDCP_RX_SN and the SCG_PDCP_RX_SN to the maximum sequence number of the PDCP SDU that has been submitted to the upper layer plus one.
  • the variable Next_PDCP_RX_SN may not be needed, and it is determined in step 3007 whether the received PDCP SDU is in order by comparing the received PDCP SDU sequence number with the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN. Received.
  • the PDCP entity deletes the header of the PDCP PDU, decompresses it by decryption and IP header, and maps it into a PDCP SDU and saves it in the reordering buffer.
  • the PDCP entity determines whether the missing PDCP SDU sequence number is less than State variable MCG_PDCP_RX_SN. If the missing PDCP SDU sequence number is smaller than the state variable MCG_PDCP_RX_SN, step 3011 is performed, otherwise, it ends.
  • the missing PDCP SDU refers to a PDCP SDU waiting to be received. For example, in the example described in step 3007, if the received PDCP PDU sequence number is 8, the missing PDCP SDU sequence number is 5.
  • step 3011 the PDCP entity determines whether the missing PDCP SDU sequence number is less than the state variable SCG_PDCP_RX_SN. If the missing PDCP SDU sequence number is less than the state variable SCG_PDCP_RX_SN, then step 3012 is performed, otherwise, it ends.
  • the PDCP entity submits all PDCP SDUs stored in the PDCP reordering buffer that are smaller than the missing PDCP SDU sequence number and the consecutive PDCP SDUs to the upper layer.
  • the PDCP entity updates Next_PDCP_RX_SN to the maximum sequence number of the PDCP SDU submitted to the upper layer plus one. For example, suppose the maximum sequence number of the PDCP SDU that the PDCP entity has submitted to the upper layer is 4, and the PDCP SDUs that are not sequentially received in the PDCP reordering buffer are 6, 9, and 12.
  • MCG_PDCP_Rx_SN is 4 and SCG_PDCP_Rx_SN is 12.
  • Step 3010 is sequentially performed in descending order, and subsequent steps are performed according to the judgment result. First, step 3010 is performed on the PDCP SDU of sequence number 11, which does not satisfy the condition set in step 3010.
  • step 3010 and step 3011 are performed on the PDCP SDU of sequence number 8, which satisfies the conditions set by step 3010 and step 3011, and according to step 3012, the unordered reception and sequence stored in the PDCP reordering buffer are received.
  • the PDCP SDU whose number is smaller than the missing PDCP SDU is delivered to the upper layer, that is, the PDCP SDU with the sequence number of 6 is delivered to the upper layer.
  • the PDCP SDU with the sequence number and the serial number 8 of the missing PDCP SDU needs to be submitted to the upper layer, that is, the serial number.
  • the upper layer is submitted for the PDCP SDUs of 9 and 10, and the value of Next_PDCP_RX_SN is updated to 10.
  • the PDCP SDU with serial number 12 is still stored in the reordering buffer.
  • the variable Next_PDCP_RX_SN may not be needed, and the PDCP entity updates the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN to the maximum sequence number of the PDCP SDU that has been submitted to the upper layer plus one.
  • step 3007 can be performed first, and if the determination result is no, steps 3002 to 3006 are performed, and then step 3009 and subsequent steps are performed.
  • the order of execution of step 3010 and step 3011 can also be exchanged.
  • step 3010 and step 3011 need to be performed separately for each missing PDCP SDU. For example, the missing PDCP SDUs are processed separately in the order of the serial number from large to small or from small to large.
  • the PDCP entity can determine that the missing PDCP SDU whose sequence number is smaller than the PDCP SDU has been lost, so The missing PDCP SDU whose sequence number is smaller than the PDCP SDU does not need to perform step 3010 and step 3011 and subsequent steps related to the judgment result.
  • the PDCP entity corresponding to the split bearer in the UE also maintains the state variable Min_PDCP_RX_SN.
  • the value of the state variable Min_PDCP_RX_SN is set to the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN, and each time MCG_PDCP_RX_SN or SCG_PDCP_RX_SN is updated, Min_PDCP_RX_SN is updated accordingly.
  • the initial value of Min_PDCP_RX_SN is 0. It should be noted that the size comparison of the serial numbers herein refers to the comparison of the COUNT values corresponding to the serial numbers.
  • Step 4001 is the same as step 3001, and the embodiments of the present invention are not described in detail herein.
  • Step 4002 is the same as step 3002, and the embodiments of the present invention are not described in detail herein.
  • Step 4003 is the same as step 3003, and the embodiments of the present invention are not described in detail herein.
  • Step 4004 is the same as step 3004, and the embodiments of the present invention are not described in detail herein.
  • Step 4005 is the same as step 3005, and the embodiments of the present invention are not described in detail herein.
  • Step 4006 is the same as step 3006, and the embodiments of the present invention are not described in detail herein.
  • step 4007 the value of the state variable Min_PDCP_RX_SN is set to the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • Step 4008 is the same as step 3007, and the embodiment of the present invention is not described in detail herein.
  • Step 4009 is the same as step 3008, and the embodiments of the present invention are not described in detail herein.
  • Step 4010 is the same as step 3009, and the embodiments of the present invention are not described in detail herein.
  • step 4011 the PDCP entity determines whether the missing PDCP SDU sequence number is less than the state variable Min_PDCP_RX_SN. If the missing PDCP SDU sequence number is less than the state variable Min_PDCP_RX_SN, then step 4012 is performed, otherwise, it ends.
  • Step 4012 is the same as step 3012, and the embodiment of the present invention will not be described in detail herein.
  • step 4008 can be performed first, and if the determination result is no, steps 4002 to 4007 are performed, and then step 4010 and subsequent steps are performed.
  • step 4012 if there are multiple missing PDCP SDUs, step 4011 needs to be performed separately for each missing PDCP SDU. For example, the missing PDCP SDUs are processed separately in the order of the serial number from large to small or from small to large.
  • the PDCP entity may determine that the missing PDCP SDU whose sequence number is smaller than the PDCP SDU has been lost, so the sequence number is smaller than The missing PDCP SDU of the PDCP SDU does not need to perform step 4011 and subsequent steps related to the result of the determination.
  • FIG. 5 is a flow chart showing a method for a PDCP receiving entity to deliver an out-of-order received PDCP SDU as early as possible in accordance with a second aspect of the present invention.
  • the former receives the unordered PDCP SDU sequence number stored in the PDCP receiving entity reordering buffer and the PDCP SDU received by the PDCP entity from the two lower layer entities respectively.
  • the smaller of the largest sequence numbers is compared, while the latter compares the missing PDCP SDU sequence number with the smaller of the largest sequence numbers of PDCP SDUs received by the PDCP entity from the two lower layer entities, respectively.
  • the embodiment of the present invention only describes the operations performed when the user equipment is used as the receiving end in the case of the downlink and the operations performed when the MCG is used as the transmitting end, and those skilled in the art will understand that without departing from the present disclosure.
  • the process is also applicable to operations performed when the MCG acts as a receiving end in the uplink communication process and operations performed when the user equipment acts as a transmitting end.
  • the method starts in step S510, and the unsorted packet data convergence protocol protocol data unit PDCP PDU received by the PDCP entity from the lower layer entity is mapped into a PDCP SDU and stored in the reordering buffer. .
  • the PDCP entity corresponding to the split bearer in the UE may also maintain and update the two state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the MCG_PDCP_RX_SN value is set to the received PDCP PDU sequence number; if the received PDCP PDU is from the SCG And said The sequence number of the PDCP PDU is greater than SCG_PDCP_RX_SN, and the SCG_PDCP_RX_SN value is set to the received PDCP PDU sequence number.
  • the size comparison of the serial numbers herein refers to the comparison of the COUNT values corresponding to the serial numbers.
  • the PDCP entity submits the unsorted PDCP SDU whose sequence number is less than or equal to the smaller of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN in the PDCP reordering buffer and its subsequent consecutive PDCP SDUs to the upper layer.
  • the PDCP entity may compare the unordered PDCP SDU sequence number in the PDCP reordering buffer with the smaller one of the state variable state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN according to the sequence number from large to small or from small to large.
  • the PDCP SDU whose sequence number is less than or equal to the smaller of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN and its subsequent consecutive PDCP SDUs are delivered to the upper layer.
  • the sequence number of the PDCP SDU that is not received in sequence is less than or equal to the smaller of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN, the sequence number is changed from the smaller to the smaller of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the PDCP entity may determine that the PDCP SDU whose sequence number is smaller than the unordered reception of the PDCP SDU is also smaller than the smaller one of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN, so the PDCP whose sequence number is smaller than the PDCP SDU is not received in order.
  • the SDU does not need to be compared with the smaller of the state variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the maximum sequence number of the PDCP SDU that the PDCP entity has submitted to the upper layer is 4, and the PDCP SDUs that are not sequentially received in the PDCP reordering buffer are 6, 9, 10, and 12.
  • MCG_PDCP_Rx_SN is 4, and SCG_PDCP_Rx_SN is 12.
  • the PDCP entity updates the MCG_PDCP_Rx_SN to 8, and the SCG_PDCP_Rx_SN remains unchanged, still at 12.
  • the PDCP SDUs that are not sequentially received in the PDCP reordering buffer are 6, 8, 9, 10, and 12.
  • the PDCP entity may also maintain a state variable Next_PDCP_RX_SN for determining whether the received PDCP SDU is received in order.
  • the PDCP entity also updates the smaller one of the MCG_PDCP_RX_SN and the SCG_PDCP_RX_SN to the maximum sequence number of the PDCP SDU that has been submitted to the upper layer plus one.
  • the variable Next_PDCP_RX_SN may not be needed, and it is judged whether the received PDCPSDU is sequentially received by comparing the received PDCP SDU sequence number with the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the PDCP receiving entity may also maintain three state variables, namely, MCG_PDCP_RX_SN, SCG_PDCP_RX_SN, and Min_PDCP_RX_SN.
  • the PDCP entity compares the out-of-order received PDCP SDU sequence number stored in the reordering buffer with Min_PDCP_RX_SN.
  • the PDCP SDU whose sequence number is less than or equal to the state variable Min_PDCP_RX_SN and its subsequent consecutive PDCP SDUs that are not sequentially received in the PDCP reordering buffer are delivered to the upper layer.
  • the present invention provides a method for performing the PDCP sending entity shown in FIG. 6 to implement the PDCP sending entity to the PDCP SDU.
  • Period of PDCP SDU Period of PDCP SDU.
  • the PDCP transmitting entity sends an indication message to the PDCP receiving entity to indicate that the specific PDCP SDU has expired and is deleted.
  • the indication message may be a newly defined PDCP Control PDU.
  • FIG. 7 shows a structure of the PDCP Control PDU.
  • the fields of the PDCP Control PDU shown in Figure 7 have the following meanings:
  • the D/C field is used to indicate whether the PDCP PDU at the receiving end is a PDCP Control PDU or a PDCP Data PDU. In this embodiment, it may be set to 0 to indicate that the PDCP PDU is a PDCP Control PDU.
  • the PDU type field is used to indicate the type of the PDCP control PDU. In this embodiment, since a new PDCP Control PDU is to be defined, the type field may take other values different from 000 and 001, for example, 010.
  • the PDCP sequence number field is used to indicate the expired PDCP SDU sequence number that was deleted.
  • a sequence number of the plurality of deleted PDCP SDUs or a bitmap generated by the plurality of deleted PDCP SDUs may be included in the PDCP Control PDU. This information can be described in other information fields. Other information fields are optional.
  • the PDCP Control PDU sent by the PDCP Tx to the PDCP Rx indicates the expired PDCP SDU that has the largest sequence number and satisfies the condition that the PDCP SDU whose sequence number is smaller than the expired PDCP SDU sequence number has expired or is confirmed to have been successfully transmitted.
  • PDCP SDUs with serial numbers 1, 2, 3, 4, 5, 6, 7, 8, 9 in the PDCP Tx need to be sent, and PDCP SDUs with serial numbers 1, 2, and 8 have been The lower layer confirms successful transmission.
  • the PDCP SDUs with sequence numbers 2, 4, 5, and 7 are deleted due to expiration.
  • the PDCP SDUs with sequence numbers of 6, 9 have been sent but have not been confirmed by the lower layer.
  • the expired PDCP SDU sequence number of the expired PDCP SDU that satisfies the condition ie, the PDCP SDU whose sequence number is less than the expired PDCP SDU sequence number has expired or is confirmed to have been successfully sent
  • the PDCP Rx may determine that the missing PDCP SDUs with the sequence number of 5 and the sequence number less than 5 have expired, thereby submitting the PDCP SDU with the sequence number 3 stored in the reordering buffer. Give the upper layer.
  • the transmitted PDCP Control PDU indicates that the following conditions have expired PDCP SDU:
  • the sequence number of the expired PDCP SDU is larger than the smaller one of the maximum sequence numbers of the successfully transmitted PDCP SDUs respectively confirmed by the two lower layer entities of the transmitting side PDCP entity.
  • the PDCP Tx can maintain two state variables MCG_PDCP_TX_SN and SCG_PDCP_TX_SN.
  • the state variable MCG_PDCP_TX_SN holds the maximum sequence number of the successfully transmitted PDCP SDU reported by the MCG RLC Tx, with an initial value of zero.
  • the MCG_PDCP_TX_SN is set to the sequence number of the confirmed PDCP SDU.
  • the state variable SCG_PDCP_TX_SN holds the maximum sequence number of the successfully transmitted PDCP SDU confirmed by the SCG RLC Tx, with an initial value of zero.
  • the SCG_PDCP_TX_SN is set to the sequence number of the received PDCP SDU.
  • the size comparison of the serial numbers herein refers to the comparison of the COUNT values corresponding to the serial numbers.
  • step 910 when the PDCP Tx detects that the deletion timer associated with a PDCP SDU expires, the PDCP SDU is deleted.
  • step 920 the PDCP Tx determines whether the sequence number of the deleted PDCP SDU is greater than MCG_PDCP_TX_SN. If it is greater, step 940 is performed; otherwise, step 930 is performed.
  • step 930 the PDCP Tx determines whether the sequence number of the deleted PDCP SDU is greater than the SCG PDCP TX SN. If it is greater, step 940 is performed, otherwise, it ends.
  • step 940 the PDCP Tx generates a PDCP Control PDU according to the deleted PDCP SDU and sends it to the PDCP Rx.
  • step 920 and step 930 can be exchanged.
  • step 920 and step 930 may also be performed in combination, that is, if the deleted PDCP SDU sequence number is greater than the smaller of the PDCP SDU maximum sequence number confirmed by the MCG RLC Tx and the PDCP SDU maximum sequence number confirmed by the SCG RLC Tx.
  • the deleted PDCP SDU needs to be reported to the PDCP Rx.
  • the state variable Min_PDCP_TX_SN needs to be maintained.
  • Min_PDCP_TX_SN The value of the state variable Min_PDCP_TX_SN is set to be the smaller of MCG_PDCP_TX_SN and SCG_PDCP_TX_SN, and each time MCG_PDCP_TX_SN or SCG_PDCP_TX_SN is updated, Min_PDCP_TX_SN is updated accordingly.
  • the initial value of Min_PDCP_TX_SN is 0. If the PDCP SDU sequence number expired by the deletion timer is greater than Min_PDCP_TX_SN, the expired PDCP SDU sequence number information is included in the PDCP Control PDU transmitted to the PDCP Rx.
  • FIG. 10 shows a schematic block diagram of the PDCP entity 1000.
  • the PDCP entity 1000 includes a PDCP processing device 1010, a determining device 1020, and a delivery device 1030.
  • the PDU processing apparatus 1010 is configured to map the unsorted packet data convergence protocol protocol data unit PDCP PDU received from the lower layer entity of the PDCP entity into a PDCP SDU, and store it in the reordering buffer.
  • the determining device 1020 is configured to determine whether the sequence number of the missing PDCP SDU is smaller than a smaller one of the maximum sequence numbers of the PDCP SDUs received by the PDCP entity from the two lower layer entities respectively.
  • the submitting device 1030 is configured to: when the sequence number of the missing PDCP SDU is smaller than the smaller one, the PDCP stored in the reordering buffer is smaller than the PDCP of the missing serial number of the PDCP SDU.
  • the SDU and the PDCP SDU whose serial number is larger than the serial number of the missing PDCP SDU and consecutive to the serial number of the missing PDCP SDU is submitted to the PDCP The upper entity of the body.
  • the determining means 1020 may be configured to: determine, according to the sequence number of the missing PDCP SDUs, from the largest to the smallest, whether the sequence number of the missing PDCP SDU is smaller than the smaller one, and if a missing one is determined If the sequence number of the PDCP SDU is smaller than the smaller one, it is no longer determined whether the sequence number of the remaining missing PDCP SDU is smaller than the smaller one.
  • FIG. 11 shows a schematic block diagram of the PDCP entity 1100.
  • the PDCP entity 1100 includes a PDU processing device 1110 and a delivery device 1120.
  • the PDU processing apparatus 1110 is configured to map the unsorted packet data convergence protocol protocol data unit PDCP PDU received from the lower layer entity of the PDCP entity into a PDCP SDU, and store it in the reordering buffer.
  • the submitting apparatus 1120 is configured to: store a sequence number stored in a reordering buffer that is smaller than or equal to a PDCP SDU of a smaller one of a maximum sequence number of PDCP SDUs received by a PDCP entity from two lower layer entities, and subsequent consecutive ones thereof
  • the PDCP SDU is submitted to the upper entity of the PDCP entity.
  • the delivery device 1120 may be configured to: determine, according to the sequence number of the PDCP SDUs stored in the reordering buffer, from the largest to the smallest, whether the sequence number of the PDCP SDU of the PDCP SDU stored in the reordering buffer is smaller than Or equal to the smaller one, and if it is determined that the sequence number of one PDCP SDU is less than or equal to the smaller one, it is no longer determined whether the sequence number of the remaining PDCP SDUs is less than or equal to the smaller one, and the rest The PDCP SDU, the determined sequence number is smaller than the smaller one of the PDCP SDU and its subsequent consecutive PDCP SDUs are submitted to the upper entity of the PDCP entity.
  • the foregoing PDCP entities 1000 and 1100 may each be implemented in a primary cell group MCG or a user equipment, and may further include: variable storage means for maintaining and updating two variables MCG_PDCP_RX_SN and SCG_PDCP_RX_SN such that the MCG_PDCP_RX_SN indicates the PDCP entity from The maximum sequence number of the PDCP SDU received by the RLC entity in the MCG or the RLC entity corresponding to the RLC entity in the MCG, the SCG_PDCP_RX_SN indicating that the PDCP entity is from the RLC entity in the SCG or from the user equipment The maximum sequence number of the PDCP SDU received by the RLC entity corresponding to the RLC entity in the SCG.
  • the variable storage device may also maintain and update the variable Min_PDCP_RX_SN to indicate the smaller of MCG_PDCP_RX_SN and SCG_PDCP_RX_SN.
  • the variable storage device may also maintain and update the variable Next_PDCP_RX_SN to indicate that the maximum sequence number of the PDCP SDU submitted to the upper entity is incremented by one.
  • the initial value of the variable being maintained can be set to zero.
  • the invention also proposes a related PDCP entity 1200.
  • FIG. 12 shows a schematic block diagram of the PDCP entity 1200.
  • the PDCP entity 1200 includes an SDU deletion device 1210 and a PDCP control PDU transmitting device 1220.
  • the SDU deleting device 1210 is configured to delete a PDCP SDU whose expiration timer has expired.
  • the PDCP control PDU sending means 1220 is configured to send a PDCP Control PDU indicating all or part of the expired PDCP SDU to the PDCP entity on the receiving side.
  • the PDCP entity 1200 may be implemented in a primary cell group MCG or user equipment, and may further comprise: variable storage means for maintaining and updating two variables MCG_PDCP_TX_SN and SCG_PDCP_TX_SN, the MCG_PDCP_TX_SN indicating by the RLC entity in the MCG or by the user equipment The maximum sequence number of the successfully transmitted PDCP SDU confirmed by the RLC entity corresponding to the RLC entity in the MCG, the SCG_PDCP_RX_SN indicating the RLC corresponding to the RLC entity in the SCG or the RLC entity in the SCG in the user equipment The maximum sequence number of the PDCP SDU that was successfully sent by the entity.
  • the variable storage device may also maintain and update the variable Min_PDCP_TX_SN to indicate the smaller of MCG_PDCP_TX_SN and SCG_PDCP_TX_SN. The initial value of the variable being maintained can be set to zero.

Abstract

公开了分组数据汇聚协议PDCP实体执行的方法以及相应的实体设备。所述方法包括：将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者；以及如果所述遗漏的PDCP SDU的序列号小于所述较小者，则将重排序缓冲区中存储的序列号小于所述遗漏的PDCP SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给PDCP实体的上层实体。

Description

分组数据汇聚协议PDCP实体及其执行的方法 技术领域
本发明涉及移动通信，具体地，涉及分组数据汇聚协议PDCP实体及其执行的方法，用于使得接收侧PDCP实体能够尽早将未按序接收的PDCP SDU递交到上层。
背景技术
第三代伙伴计划(3GPP)长期演进(LTE)系统的层2(layer 2)用户平面协议栈(User-Plane Protocol Stack)由3个子层组成，从高到低依次为：分组数据汇聚协议(Packet Data Convergence Protocol，PDCP)层、无线链路控制(Radio Link Control，RLC)层和媒体接入控制(Media Access Control)层。在发送端，从高层接收服务数据单元(Service Data Unit，SDU)，为该层提供业务，并向低层输出协议数据单元(Protocol Data Unit，PDU)。例如：RLC层接收来自PDCP的分组(packet)。这些分组对PDCP层来说是PDCP PDU，但对RLC层来说是RLC SDU。用于发送PDCP PDU的PDCP实体称为PDCP Tx，用于发送RLC PDU的RLC实体称为RLC Tx。在接收端，该过程是相反的，每层向上层发送SDU，上层作为PDU接收。用于接收PDCP PDU的PDCP实体称为PDCP Rx，用于接收RLC PDU的RLC实体称为RLC Rx。PDCP SDU由PDCP序列号(sequence number，SN)标识，PDCP SDU与对应的PDCP PDU和RLC SDU具有相同的序列号，RLC PDU由RLC序列号标识。PDCP序列号和RLC序列号可循环利用。当PDCP序列号达到最大值时，新的PDCP SDU又从最小值开始编号，但对应的超帧号增加1。PDCP序列号和超帧号(Hyper Frame Number，HFN)组成的COUNT唯一标识一个PDCP SDU。
3GPP LTE版本11中，每一无线承载(bearer)有一个PDCP实体(entity)和一个RLC实体。每个基站(也称为NodeB或演进NodeB(eNB))和每个用户设备(UE)均有一个MAC实体。这里，用户设备可以是用户终端，用户节点，移动终端或平板电脑。RLC层的功能通过RLC实体(entity)来实现，RLC实体可配置为3种数据传输模式之一： (1)透明模式(Transparent Mode，TM)；(2)确认模式(Acknowledged Mode，AM)；(3)非确认模式(Unacknowledged Mode，UM)。在AM RLC和UM RLC模式下，RLC实体负责RLC SDU的按序发送和接收。具体地，在RLC发送方，基站或用户设备中的RLC实体将来自PDCP实体的RLC SDU按照MAC层指示的大小依次重新进行分段(segmentation)并添加RLC报头(Header)形成RLC PDU并依次发送，RLC报头中包含为所述RLC PDU分配的RLC SN。在RLC接收方，RLC实体从下层接收RLC PDU，将这些RLC PDU按照RLC SN升序重排序和重组(concatenate)，并将重组后的RLC SDU按照从小到大的顺序依次递交给PDCP层。
正在制定中的3GPP LTE版本12标准中，包含关于具有双连接(dual connectivity)能力的用户设备、主基站(Master eNB，MeNB)、辅基站(Secondary eNB，SeNB)的标准制定工作。主基站负责维护用户设备的无线资源管理(Radio Resource Management，RRM)测量配置并且基于接收到的测量报告或流量状况(traffic conditions)或承载类型(bear type)向辅基站请求为用户设备提供额外的资源。辅基站接收到主基站的请求后为用户设备配置服务小区或因没有足够的资源而拒绝所述请求。
基于承载分离(bearer split)的不同方式和用户平面协议栈的不同，在3GPP TSG-RAN2第83bis次会议上，确定1A和3C两种用户平面架构(User-plane Architecture)作为双连接部署方式的标准化选项。图1示出的选项3C具有如下特征：(1)主基站通过S1-U接口与业务网关(Serving Gateway，S-GW)通信；(2)承载在主基站中分离；(3)对于分离承载(split bearer)，在主基站和辅基站中都有对应RLC实体(entity)。在选项3C中，位于辅基站的RLC实体与上层(即位于主基站的PDCP实体)通过Xn接口进行交互，所述Xn接口包括X2接口。基于所述特征，在双连接部署方案3C中，为用户设备配置的服务小区(serving cell)分成两类：(1)由MeNB的服务小区组成的主小区群(Master Cell Group，MCG)(2)由SeNB的服务小区组成的辅小区群(Secondary Cell Group，SCG)。相应的，具有双连接能力的用户设备为分离承载配置一个PDCP实体和两个RLC实体，所述PDCP实体与MCG中的PDCP实体对应， 所述一个RLC实体与MCG中的RLC实体对应，所述另一个RLC实体与SCG中的RLC实体对应。
在3GPP LTE版本11中，由于每个PDCP Rx只对应一个RLC Rx。RLC接收实体的重排序功能确保PDCP Rx从RLC层按序接收PDCP PDU。但在承载分离的双连接部署方式下，一个PDCP Rx对应两个RLC Rx，PDCP Rx从两个RLC Rx接收到的PDCP PDU是乱序的。因此，PDCP Rx需要对来自两个RLC Rx的PDCP PDU重新进行排序。在3GPP TSG RAN WG2Meeting#85次会议上提出PDCP重排功能将采用UM RLC类似的基于t-Reordering定时器的重排方法。所述方法的主要思想为：PDCP Rx从两个RLC Rx接收PDCP PDU，当接收到未按序到达的PDCP PDU时，将未按序到达的PDCP PDU存储在重排序缓冲区中，并启动t-Reordering定时器，等待遗漏的PDCP PDU到来。当接收到遗漏的PDCP PDU，则将已按序接收的PDCP SDU递交到上层。但是，当某个PDCP SDU在PDCP发送实体中由于删除计时器(discardtimer)到期而被删除或由于在X2接口上传输丢失时，这些未按序接收的PDCP PDU将存储在重排序缓冲区中直到t-Reordering定时器到期才被递交到上层。这将增大PDCP SDU的时延并延后TCP流量控制功能。当t-Reordering定时器设置较大时，将导致未按序接收的PDCP PDU因在重传缓冲区中等待已删除或已丢失的PDCP PDU而超过其有效期，进而影响无线链路的传输时延和可靠性。
发明内容
鉴于现有技术中存在的以上问题，本发明旨在提供一种机制，使得接收侧PDCP实体能够尽早将未按序接收的PDCP SDU递交给上层。
为实现上述目的，本发明的第一方面提供了一种由接收侧的分组数据汇聚协议PDCP实体执行的方法，包括：将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者；以及如果所述遗漏的PDCP SDU的序列号小于所述较小者，则将重排序缓冲区中存储的序列号小于所述遗漏的PDCP  SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给PDCP实体的上层实体。
在根据本发明第一方面的方法中，可以按遗漏的PDCP SDU的序列号从大到小的顺序判断遗漏的PDCP SDU的序列号是否小于所述较小者，并且如果判断出一个遗漏的PDCP SDU的序列号小于所述较小者，则不再判断其余遗漏的PDCP SDU的序列号是否小于所述较小者。
为实现上述目的，本发明的第二方面提供了另一种由接收侧的分组数据汇聚协议PDCP实体执行的方法，包括：将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；以及将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
在根据本发明第二方面的方法中，所述将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体可以包括：按重排序缓冲区中存储的PDCP SDU的序列号从大到小的顺序判断重排序缓冲区中存储的PDCP SDU的PDCP SDU的序列号是否小于或等于所述较小者，并且如果判断出一个PDCP SDU的序列号小于或等于所述较小者，则不再判断其余PDCP SDU的序列号是否小于或等于所述较小者，而将其余PDCP SDU、所判断出的序列号小于所述较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
本发明的第三方面提供了一种由发送侧的分组数据汇聚协议PDCP实体执行的方法，包括：删除删除计时器已到期的PDCP SDU；以及向接收侧的PDCP实体发送指示全部或部分已到期PDCP SDU的PDCP控制PDU。
在根据本发明第三方面的方法中，所述PDCP控制PDU可以指示序列号最大的满足如下条件的已到期PDCP SDU：序列号小于所述已到期PDCP SDU的序列号的所有PDCP SDU已经过期或已被确认发送成功。 可选地，所述PDCP控制PDU可以指示满足如下条件的已到期PDCP SDU：所述已到期PDCP SDU的序列号大于发送侧PDCP实体的两个下层实体分别确认的已成功发送的PDCP SDU的最大序列号中的较小者。所述PDCP控制PDU可以包括多个字段，所述多个字段之一可以以序列号或位图的形式指示所述已到期PDCP SDU。
本发明还提供了与第一至第三方面的方法相对应的分组数据汇聚PDCP实体。
通过采用本发明提出的技术方案，在PDCP接收实体接收到来自PDCP发送实体发送的PDCP SDU之后，能够尽早将PDCP SDU递交给上层，从而能够减少无线链路时延并提高无线链路可靠性。
附图说明
通过下文结合附图的详细描述，本发明的上述和其它特征将会变得更加明显，其中：
图1为3GPP TR36.842中给出的双连接部署选项3C的示意图；
图2是示出了根据本发明第一方面的由PDCP接收实体尽早向上层递交未按序接收的PDCP SDU的方法的流程图；
图3是示出了根据本发明第一方面的方法的一个示例实施例的流程图；
图4是示出了根据本发明第一方面的方法的另一示例实施例的流程图；
图5是示出了根据本发明第二方面的由PDCP接收实体尽早向上层递交未按序接收的PDCP SDU的方法的流程图；
图6是示出了根据本发明第三方面的由PDCP发送实体执行的方法的流程图，所述方法有助于PDCP接收实体尽早向上层递交未按序接收的PDCP SDU；
图7是示出了可以在根据本发明第三方面的方法中采用的PDCP控制PDU的示意图；
图8是示出了PDCP发送实体缓冲区状态的示意图；
图9是示出了根据本发明第三方面的方法的一个示例实施例的由PDCP发送实体确定是否向PDCP接收实体报告PDCP SDU被删除的方 法的流程图；
图10是执行根据本发明第一方面的方法PDCP实体的结构的框图；
图11是执行根据本发明第二方面的方法的PDCP实体的结构的框图；以及
图12是执行根据本发明第三方面的方法的PDCP实体的结构的框图。
具体实施方式
下面，通过结合附图对本发明的具体实施例的描述，本发明的原理和实现将会变得明显。应当注意的是，本发明不应局限于下文所述的具体实施例。另外，为了简便起见，省略了对与本发明没有直接关联的公知技术的详细描述，以防止对本发明的理解造成混淆。
下文以LTE Rel-12移动通信系统及其后续的演进版本作为示例应用环境，具体描述了根据本发明的多个实施例。然而，需要指出的是，本发明不限于以下实施例，而可以适用于更多其它的无线通信系统，例如今后的5G蜂窝通信系统。
首先，参照图2，描述根据本发明第一方面的由PDCP接收实体尽早向上层递交未按序接收的PDCP SDU的方法。如图所示，该方法起始于步骤S210，由PDCP实体将从下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中。接着，在步骤S220中，PDCP实体判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者。然后，在步骤S230中，如果所述遗漏的PDCP SDU的序列号小于所述较小者，则PDCP实体将重排序缓冲区中存储的序列号小于所述遗漏的PDCP SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给上层实体。
图3和图4进一步示出了上述方法的两个具体实现的流程图。为简单起见，本发明实施例仅描述了下行链路的情况下用户设备做为接收端时执行的操作及MCG作为发送端时执行的操作，本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，所述过程也适用于上行链路通信过程中MCG作为接收端时执行的操作及用户设备作为发送 端时执行的操作。
在图3所示的实施例中，UE中分离承载对应的PDCP实体维护三个状态变量Next_PDCP_RX_SN、MCG_PDCP_RX_SN和SCG_PDCP_RX_SN。所述状态变量Next_PDCP_RX_SN保存下一个希望接收的PDCP SDU序列号，初始值为0，PDCP实体每次向上层递交PDCP SDU后都要将Next_PDPC_RX_SN更新为递交到上层的PDCP SDU的最大序列号加1。所述状态变量MCG_PDCP_RX_SN保存从与MCG RLC Tx对应的RLC Rx接收到的PDCP SDU的最大序列号，MCG_PDCP_RX_SN初始值为0，当接收到的来自与MCG RLC Tx对应的RLC Rx的PDCP SDU的序列号大于MCG_PDCP_RX_SN时，将MCG_PDCP_RX_SN置为所述接收到的PDCP SDU的序列号；所述状态变量SCG_PDCP_RX_SN保存从与SCG RLC Tx对应的RLC Rx接收到的PDCP SDU的最大序列号，初始值为0，当接收到的来自与SCG RLC Tx对应的RLC Rx的PDCP SDU的序列号大于SCG_PDCP_RX_SN时，将SCG_PDCP_RX_SN置为所述接收到的PDCP SDU的序列号。需要说明的是，在此处以及此后描述的实施例中，序列号的大小比较是指所述序列号对应的COUNT值的比较，对序列号的加减操作也是指对对应的COUNT值加减操作。
如图3所示，在步骤3001中，PDCP实体从下层接收PDCP PDU。所述PDCP实体是指UE中分离承载对应的PDCP接收实体。为简单起见，如未特别指出，后续步骤中提到的PDCP实体均指UE中分离承载对应的PDCP接收实体。
在步骤3002中，PDCP实体判断所述接收到的PDCP PDU是来自与MCG RLC Tx对应RLC Rx还是来自与SCG RLC Tx对应RLC Rx。如果所述PDCP SDU是来自与MCG RLC Tx对应RLC Rx，则执行步骤3003。如果所述PDCP SDU是来自与SCG RLC Tx对应RLC Rx，则执行步骤3005。
在步骤3003中，PDCP实体判断所述PDCP PDU的序列号是否大于状态变量MCG_PDCP_RX_SN。如果是，则执行步骤3004，否则，执行步骤3007。
在步骤3004中，PDCP实体将状态变量MCG_PDCP_RX_SN的值 设置为所述PDCP PDU的序列号。
在步骤3005中，PDCP实体判断所述PDCP PDU的序列号是否大于状态变量SCG_PDCP_RX_SN。如果是，则执行步骤3006，否则，执行步骤3007。
在步骤3006中，PDCP实体将状态变量SCG_PDCP_Rx_SN的值设置为所述PDCP PDU的序列号。
在步骤3007中，PDCP实体判断所述PDCP PDU是否按序到达，如果是，则执行步骤3008，否则，执行步骤3009。所述PDCP PDU按序到达是指所述PDCP PDU序列号为等待接收的(或称为遗漏的)PDCP SDU最小序列号，即为Next_PDCP_RX_SN。例如，假设PDCP实体已经提交给上层的PDCP SDU最大序列号为4，PDCP重排序缓冲区中存储的未按序接收的PDCP SDU为6，7，9。如果所述接收到的PDCP PDU的序列号为5，则称所述PDCP PDU按序到达。如果所述接收到的PDCP PDU的序列号为8，则称所述PDCP PDU为非按序到达。
在步骤3008中，PDCP实体删除所述PDCP PDU报头并经过解密和IP报头解压缩后映射为PDCP SDU。然后将所述PDCP SDU及其后连续的PDCP SDU交给上层。PDCP实体将Next_PDCP_RX_SN更新为递交到上层的PDCP SDU最大序列号加1。例如，在步骤3007所描述的例子中，如果所述PDCP实体接收到的PDCP PDU序列号为5，则PDCP实体将序号为5的PDCP PDU经解密和IP报头解压缩后映射为序列号为5的PDCP SDU，然后将序列号为5、6、7的PDCP SDU依次递交给上层并将Next_PDCP_RX_SN的值置为8。
可选的，PDCP实体将MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者更新为已递交到上层的PDCP SDU的最大序列号加1。在这种情况下，可以不需要变量Next_PDCP_RX_SN，并在步骤3007中通过将接收到的PDCP SDU序列号与MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者进行比较来判断所述接收到的PDCP SDU是否是按序接收的。
在步骤3009中，PDCP实体将所述PDCP PDU删除报头并经过解密和IP报头解压缩后映射为PDCP SDU并保存在重排序缓冲区中。
在步骤3010中，PDCP实体判断遗漏的PDCP SDU序列号是否小于 状态变量MCG_PDCP_RX_SN。如果所述遗漏的PDCP SDU序列号小于状态变量MCG_PDCP_RX_SN，则执行步骤3011，否则，结束。所述遗漏的PDCP SDU是指等待接收的PDCP SDU。例如，在步骤3007所描述的例子中，如果所述接收到的PDCP PDU序列号为8，则所述遗漏的PDCP SDU序列号为5。
在步骤3011中，PDCP实体判断遗漏的PDCP SDU序列号是否小于状态变量SCG_PDCP_RX_SN。如果所述遗漏的PDCP SDU序列号小于状态变量SCG_PDCP_RX_SN，则执行步骤3012，否则，结束。
在步骤3012中，PDCP实体将存储在PDCP重排序缓冲区中的所有序列号小于所述遗漏的PDCP SDU序列号的PDCP SDU及所述遗漏的PDCP SDU之后连续的PDCP SDU递交到上层。同时，PDCP实体将Next_PDCP_RX_SN更新为递交到上层的PDCP SDU最大序列号加1。例如，假设PDCP实体已经提交给上层的PDCP SDU最大序列号为4，PDCP重排序缓冲区中存储的未按序接收的PDCP SDU为6、9、12。MCG_PDCP_Rx_SN为4，SCG_PDCP_Rx_SN为12。在接收到来自MCG的序列号为10的PDCP SDU后，PDCP重排序缓冲区中存储的未按序接收的PDCP SDU为6、9、10、12，MCG_PDCP_Rx_SN为10，SCG_PDCP_Rx_SN为12。所述遗漏的PDCP SDU序列号为5、7、8、11。按从大到小的顺序依次执行步骤3010及根据判断结果执行后续步骤。首先对所述序列号为11的PDCP SDU执行步骤3010，它不满足步骤3010设定的条件。然后，对所述序列号为8的PDCP SDU执行步骤3010和步骤3011，它满足步骤3010和步骤3011设定的条件，根据步骤3012，将PDCP重排序缓冲区中存储的未按序接收且序列号小于所述遗漏PDCP SDU的PDCP SDU递交到上层，即将序列号为6的PDCP SDU递交上层，此外还需要将序列号与遗漏的PDCP SDU的序列号8连续的PDCP SDU递交上层，即将序列号为9和10的PDCP SDU递交上层，并将Next_PDCP_RX_SN的值更新为10。但序列号为12的PDCP SDU仍存储在重排序缓冲区中。
可选的，可以不需要变量Next_PDCP_RX_SN，并且PDCP实体将MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者更新为已递交到上层的PDCP SDU的最大序列号加1。
需要说明的是，步骤3002至步骤3006与步骤3007的执行顺序可交换，即可先执行步骤3007，如果判断结果为否，则执行步骤3002至3006，然后执行步骤3009及其后续步骤。步骤3010和步骤3011的执行顺序也可交换。此外，如果有多个遗漏的PDCP SDU，则需要对各个遗漏的PDCP SDU分别执行步骤3010和步骤3011。例如，对所述遗漏的PDCP SDU按照序列号从大到小或从小到大的顺序分别处理。如果采用从大到小的顺序处理，当某个遗漏的PDCP SDU同时满足步骤3010和步骤3011时，则PDCP实体可判断出序列号小于所述PDCP SDU的遗漏的PDCP SDU已经丢失，所以，对序列号小于所述PDCP SDU的遗漏的PDCP SDU不需要再执行步骤3010和步骤3011及与其判断结果相关的后续步骤。
在图4描述的实施例中，除了状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN以外，UE中分离承载对应的PDCP实体还维护状态变量Min_PDCP_RX_SN。所述状态变量Min_PDCP_RX_SN的值设置为MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者，每次更新MCG_PDCP_RX_SN或SCG_PDCP_RX_SN时，相应的更新Min_PDCP_RX_SN。Min_PDCP_RX_SN初始值为0。需要说明的是，此处序列号的大小比较是指所述序列号对应的COUNT值的比较。
步骤4001与步骤3001相同，本发明实施例在此不再详述。
步骤4002与步骤3002相同，本发明实施例在此不再详述。
步骤4003与步骤3003相同，本发明实施例在此不再详述。
步骤4004与步骤3004相同，本发明实施例在此不再详述。
步骤4005与步骤3005相同，本发明实施例在此不再详述。
步骤4006与步骤3006相同，本发明实施例在此不再详述。
在步骤4007中，将状态变量Min_PDCP_RX_SN的值置为MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
步骤4008与步骤3007相同，本发明实施例在此不再详述。
步骤4009与步骤3008相同，本发明实施例在此不再详述。
步骤4010与步骤3009相同，本发明实施例在此不再详述。
在步骤4011中，PDCP实体判断遗漏的PDCP SDU序列号是否小于状态变量Min_PDCP_RX_SN。如果所述遗漏的PDCP SDU序列号小于状态变量Min_PDCP_RX_SN，则执行步骤4012，否则，结束。
步骤4012与步骤3012相同，本发明实施例在此不再详述。
需要说明的是，步骤4002至步骤4007与步骤4008的执行顺序可交换，即可先执行步骤4008，如果判断结果为否，则执行步骤4002至4007，然后执行步骤4010及其后续步骤。此外在步骤4012中，如果有多个遗漏的PDCP SDU，则需要对各个遗漏的PDCP SDU分别执行步骤4011。例如，对所述遗漏的PDCP SDU按照序列号从大到小或从小到大的顺序分别处理。如果采用从大到小的顺序处理，当对某个遗漏的PDCP SDU执行步骤4011时，则PDCP实体可判断出序列号小于所述PDCP SDU的遗漏的PDCP SDU已经丢失，所以，对序列号小于所述PDCP SDU的遗漏的PDCP SDU不需要再执行步骤4011及与其判断结果相关的后续步骤。
图5示出了根据本发明第二方面的由PDCP接收实体尽早向上层递交未按序接收的PDCP SDU的方法的流程图。该方法与图2所示的方法的关键区别在于：前者将PDCP接收实体重排序缓冲区中存储的未按序接收的PDCP SDU序列号与PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者进行比较，而后者将遗漏的PDCP SDU序列号与PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者进行比较。为简单起见，本发明实施例仅描述了下行链路的情况下用户设备做为接收端时执行的操作及MCG作为发送端时执行的操作，本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，所述过程也适用于上行链路通信过程中MCG作为接收端时执行的操作及用户设备作为发送端时执行的操作。
如图所示，该方法起始于步骤S510，由PDCP实体将从下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中。
与以上结合图3和图4描述的实施例类似的，在具体实现中，UE中分离承载对应的PDCP实体也可以维护并更新两个状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN。如果PDCP实体从下层接收到的PDCP PDU来自MCG，且所述PDCP PDU的序列号大于MCG_PDCP_RX_SN，则将MCG_PDCP_RX_SN值置为所述接收到的PDCP PDU序列号；如果所述接收到的PDCP PDU来自SCG，且所述 PDCP PDU的序列号大于SCG_PDCP_RX_SN，则将SCG_PDCP_RX_SN值置为所述接收到的PDCP PDU序列号。需要说明的是，此处序列号的大小比较是指所述序列号对应的COUNT值的比较。
在步骤520中，PDCP实体将PDCP重排序缓冲区中未按序接收的序列号小于或等于状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者的PDCP SDU及其后续连续PDCP SDU递交给上层。
具体的，PDCP实体可按照序列号从大到小或从小到大的顺序逐一将PDCP重排序缓冲区中未按序接收的PDCP SDU序列号与状态变量状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者进行比较，将序列号小于或等于状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者的PDCP SDU及其后续连续的PDCP SDU递交给上层。如果按照序列号从大到小的顺序与状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者进行比较，当某个未按序接收的PDCP SDU的序列号小于或等于状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者时，PDCP实体可判断出序列号小于所述PDCP SDU的未按序接收的PDCP SDU也一定小于状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者，所以，对序列号小于所述PDCP SDU的未按序接收的PDCP SDU不需要再与状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者进行比较。
例如：假设PDCP实体已经提交给上层的PDCP SDU最大序列号为4，PDCP重排序缓冲区中存储的未按序接收的PDCP SDU为6、9、10、12。此时，MCG_PDCP_Rx_SN为4，SCG_PDCP_Rx_SN为12。在接收到来自MCG的序列号为8的PDCP SDU后，PDCP实体更新MCG_PDCP_Rx_SN为8，SCG_PDCP_Rx_SN保持不变，仍为12。PDCP重排序缓冲区中存储的未按序接收的PDCP SDU为6、8、9、10、12。此时，由于重排序缓冲区中序列号为8的PDCP SDU满足序列号同时小于或等于状态变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中较小者的条件，故将序列号小于或等于8的PDCP SDU(SN＝6、8)及序列号与8连续的后续PDCP SDU(SN＝9、10)递交到上层，即将序列号为6、8、9、10的PDCP SDU递交给上层。
与以上结合图3描述的实施例类似地，PDCP实体还可以维护状态变量Next_PDCP_RX_SN，用于判断所述接收到的PDCP SDU是否是按序接收的。可选的，PDCP实体还将MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者更新为已递交到上层的PDCP SDU的最大序列号加1。在这种情况下，可以不需要变量Next_PDCP_RX_SN，并通过将接收到的PDCP SDU序列号与MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者进行比较来判断所述接收到的PDCPSDU是否是按序接收的。
需要说明的是，与以上结合图4示出的实施例类似，PDCP接收实体也可以维护3个状态变量，即MCG_PDCP_RX_SN、SCG_PDCP_RX_SN和Min_PDCP_RX_SN。此时，在步骤520中，PDCP实体将重排序缓冲区中保存的未按序接收的PDCP SDU序列号与Min_PDCP_RX_SN比较。将PDCP重排序缓冲区中未按序接收的序列号小于或等于状态变量Min_PDCP_RX_SN的PDCP SDU及其后续连续PDCP SDU递交给上层。
此外，为实现PDCP接收实体尽早向上层递交未按序接收的PDCP SDU，本发明提出了如图6所示的PDCP发送实体执行的方法，包括步骤S610，由PDCP发送实体删除删除计时器已到期的PDCP SDU。在步骤S620中，PDCP发送实体向PDCP接收实体发送一个用于指示特定PDCP SDU已经过期被删除的指示消息。所述指示消息可为新定义的PDCP控制PDU。图7示出了所述PDCP控制PDU的一种结构。图7所示PDCP控制PDU的各域(field)含义如下：
D/C域用于指示接收端所述PDCP PDU为PDCP控制PDU还是PDCP数据PDU。在本实施例中可置为0，用于指示所述PDCP PDU为PDCP控制PDU。PDU类型域用于指示该PDCP控制PDU的类型，在本实施例中，由于要定义一个新的PDCP控制PDU，该类型域可取不同于000和001的其他值，例如，为010。PDCP序列号域用于指示被删除的已过期PDCP SDU序列号。当有多个PDCP SDU因过期被删除时，可以在所述PDCP控制PDU中包含所述多个被删除的PDCP SDU的序列号或由所述多个被删除的PDCP SDU生成的位图。这些信息可以用其他信息域描述。其他信息域为可选。
为避免PDCP Tx因删除过期PDCP SDU而向PDCP Rx发送不必要的PDCP控制PDU。PDCP Tx向PDCP Rx发送的PDCP控制PDU指示序列号最大的满足如下条件的已过期PDCP SDU：序列号小于所述已过期PDCP SDU序列号的PDCP SDU已经过期或被确认已成功发送。例如，在图8中，PDCP Tx中有序列号为1、2、3、4、5、6、7、8、9的PDCP SDU需要发送，序列号为1、2、8的PDCP SDU已被下层确认成功发送，序列号为2、4、5、7的PDCP SDU因到期被删除，序列号为6、9的PDCP SDU已经发送但还未被下层确认。因为已过期的PDCP SDU中满足条件(即序列号小于所述已过期PDCP SDU序列号的PDCP SDU已过期或被确认已成功发送)的已过期PDCP SDU序列号有2、4、5，其中序列号5最大，所以PDCP Tx向PDCP Rx发送的PDCP控制PDU包含的序列号为5。PDCP Rx接收到所述PDCP控制PDU后，可以判断出序列号为5及序列号小于5的遗漏的PDCP SDU均已过期，从而将存储在重排序缓冲区中的序列号为3的PDCP SDU递交给上层。
在另一种由PDCP发送实体执行的选择性地向PDCP接收实体发送用于指示特定PDCP SDU已被删除的PDCP控制PDU的实施例中，所发送的PDCP控制PDU指示满足如下条件的已到期PDCP SDU：所述已到期PDCP SDU的序列号大于发送侧PDCP实体的两个下层实体分别确认的已成功发送的PDCP SDU的最大序列号中的较小者。此时，PDCP Tx可以维护两个状态变量MCG_PDCP_TX_SN和SCG_PDCP_TX_SN。所述状态变量MCG_PDCP_TX_SN保存由MCG RLC Tx报告的已成功发送的PDCP SDU的最大序列号，初始值为0。当由MCG RLC Tx确认的已成功发送的PDCP SDU的序列号大于MCG_PDCP_TX_SN时，将MCG_PDCP_TX_SN置为所述确认的PDCP SDU的序列号。所述状态变量SCG_PDCP_TX_SN保存由SCG RLC Tx确认的已成功发送的PDCP SDU的最大序列号，初始值为0。当由SCG RLC Tx确认的已成功发送的PDCP SDU的序列号大于SCG_PDCP_TX_SN时，将SCG_PDCP_TX_SN置为所述接收到的PDCP SDU的序列号。需要说明的是，此处序列号的大小比较是指所述序列号对应的COUNT值的比较。
如图9的具体流程图所示，在步骤910中，PDCP Tx检测到某PDCP SDU所关联删除计时器到期，则删除所述PDCP SDU。
在步骤920中，PDCP Tx判断所述被删除的PDCP SDU的序列号是否大于MCG_PDCP_TX_SN，如果大于，则执行步骤940，否则，执行步骤930。
在步骤930中，PDCP Tx判断所述被删除的PDCP SDU的序列号是否大于SCG PDCP TX SN，如果大于，则执行步骤940，否则，结束。
在步骤940中，PDCP Tx根据所述被删除的PDCP SDU生成PDCP控制PDU并发送给PDCP Rx。
需要说明的是，步骤920和步骤930的执行顺序可以交换。此外，步骤920和步骤930还可以合并执行，即如果被删除的PDCP SDU序列号大于被MCG RLC Tx确认的PDCP SDU最大序列号和被SCG RLC Tx确的PDCP SDU最大序列号中的较小者时，所述被删除的PDCP SDU需要报告给PDCP Rx。此时，在PDCP Tx中除需要维护状态变量MCG_PDCP_TX_SN和SCG_PDCP_TX_SN外，还需要维护状态变量Min_PDCP_TX_SN。所述状态变量Min_PDCP_TX_SN的值设置为MCG_PDCP_TX_SN和SCG_PDCP_TX_SN中的较小者，每次更新MCG_PDCP_TX_SN或SCG_PDCP_TX_SN时，相应的更新Min_PDCP_TX_SN。Min_PDCP_TX_SN初始值为0。如果删除计时器到期的PDCP SDU序列号大于Min_PDCP_TX_SN，则所述过期的PDCP SDU序列号信息包含在向PDCP Rx发送的PDCP控制PDU中。
与根据本发明第一方面的方法相对应地，本发明还提出了相关的PDCP实体1000。图10示出了该PDCP实体1000的示意结构方框图。
如图所示，该PDCP实体1000包括PDCP处理装置1010、判断装置1020以及递交装置1030。所述PDU处理装置1010用于将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中。所述判断装置1020用于判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者。所述递交装置1030用于在所述遗漏的PDCP SDU的序列号小于所述较小者的情况下，则将重排序缓冲区中存储的序列号小于所述遗漏的PDCP SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给PDCP实 体的上层实体。
优选地，所述判断装置1020可以被配置为：按遗漏的PDCP SDU的序列号从大到小的顺序判断遗漏的PDCP SDU的序列号是否小于所述较小者，并且如果判断出一个遗漏的PDCP SDU的序列号小于所述较小者，则不再判断其余遗漏的PDCP SDU的序列号是否小于所述较小者。
与根据本发明第二方面的方法相对应地，本发明还提出了相关的PDCP实体1100。图11示出了该PDCP实体1100的示意结构方框图。
如图所示，该PDCP实体1100包括PDU处理装置1110以及递交装置1120。所述PDU处理装置1110用于将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中。所述递交装置1120用于将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
优选地，所述递交装置1120可以被配置为：按重排序缓冲区中存储的PDCP SDU的序列号从大到小的顺序判断重排序缓冲区中存储的PDCP SDU的PDCP SDU的序列号是否小于或等于所述较小者，并且如果判断出一个PDCP SDU的序列号小于或等于所述较小者，则不再判断其余PDCP SDU的序列号是否小于或等于所述较小者，而将其余PDCP SDU、所判断出的序列号小于所述较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
上述PDCP实体1000和1100均可以在主小区群MCG或用户设备中实现，并且还可以包括：变量存储装置，用于维护并更新两个变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN，使得所述MCG_PDCP_RX_SN指示所述PDCP实体从MCG中的RLC实体或从用户设备中与MCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示所述PDCP实体从SCG中的RLC实体或从用户设备中与SCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号。所述变量存储装置还可以维护并更新变量Min_PDCP_RX_SN，使其指示MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
在一个实施例中，当所述PDCP实体向其上层实体递交PDCP SDU时， MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者可以被更新为递交给上层实体的PDCP SDU的最大序列号加1。在另一实施例中，所述变量存储装置还可以维护并更新变量Next_PDCP_RX_SN，使其指示递交给上层实体的PDCP SDU的最大序列号加1。所维护的变量的初始值可以设置为0。
与根据本发明第三方面的方法相对应地，本发明还提出了相关的PDCP实体1200。图12示出了该PDCP实体1200的示意结构方框图。
如图所示，该PDCP实体1200包括SDU删除装置1210以及PDCP控制PDU发送装置1220。所述SDU删除装置1210用于删除删除计时器已到期的PDCP SDU。所述PDCP控制PDU发送装置1220用于向接收侧的PDCP实体发送指示全部或部分已到期PDCP SDU的PDCP控制PDU。
PDCP实体1200可以在主小区群MCG或用户设备中实现，并且还可以包括：变量存储装置，用于维护并更新两个变量MCG_PDCP_TX_SN和SCG_PDCP_TX_SN，所述MCG_PDCP_TX_SN指示由MCG中的RLC实体或由用户设备中与MCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示由SCG中的RLC实体或由用户设备中与SCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号。所述变量存储装置还可以维护并更新变量Min_PDCP_TX_SN，使其指示MCG_PDCP_TX_SN和SCG_PDCP_TX_SN中的较小者。所维护的变量的初始值可以设置为0。
尽管以上已经结合本发明的优选实施例示出了本发明，但是本领域的技术人员将会理解，在不脱离本发明的精神和范围的情况下，可以对本发明进行各种修改、替换和改变。因此，本发明不应由上述实施例来限定，而应由所附权利要求及其等价物来限定。

Claims (45)

  1. 一种由分组数据汇聚协议PDCP实体执行的方法，包括：
    将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；
    判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者；以及
    如果所述遗漏的PDCP SDU的序列号小于所述较小者，则将重排序缓冲区中存储的序列号小于所述遗漏的PDCP SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给PDCP实体的上层实体。
  2. 根据权利要求1所述的方法，其中，按遗漏的PDCP SDU的序列号从大到小的顺序判断遗漏的PDCP SDU的序列号是否小于所述较小者，并且
    如果判断出一个遗漏的PDCP SDU的序列号小于所述较小者，则不再判断其余遗漏的PDCP SDU的序列号是否小于所述较小者。
  3. 根据权利要求1或2所述的方法，其中，所述方法是在主小区群MCG或用户设备中执行的。
  4. 根据权利要求1所述的方法，其中，所述PDCP实体维护并更新两个变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN，使得所述MCG_PDCP_RX_SN指示所述PDCP实体从MCG中的RLC实体或从用户设备中与MCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示所述PDCP实体从SCG中的RLC实体或从用户设备中与SCG中的RLC实体相对应的RLC实体接收到的PDCP_SDU的最大序列号。
  5. 根据权利要求4所述的方法，其中，当所述PDCP实体向其上层实体递交PDCP SDU时，MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者被更新为递交给上层实体的PDCP SDU的最大序列号加1。
  6. 根据权利要求4所述的方法，其中，所述PDCP实体还维护并更新变量Next_PDCP_RX_SN，使其指示递交给上层实体的PDCP SDU的 最大序列号加1。
  7. 根据权利要求4所述的方法，其中，所述PDCP实体还维护并更新变量Min_PDCP_RX_SN，使其指示MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
  8. 根据权利要求4至7中任一项所述的方法，其中，所述PDCP实体维护的变量的初始值为0。
  9. 一种分组数据汇聚协议PDCP实体，包括：
    PDU处理装置，用于将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；
    判断装置，用于判断遗漏的PDCP SDU的序列号是否小于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者；以及
    递交装置，用于在所述遗漏的PDCP SDU的序列号小于所述较小者的情况下，则将重排序缓冲区中存储的序列号小于所述遗漏的PDCP SDU的序列号的PDCP SDU以及序列号大于所述遗漏的PDCP SDU的序列号且与所述遗漏的PDCP SDU的序列号连续的PDCP SDU递交给PDCP实体的上层实体。
  10. 根据权利要求9所述的实体，其中，所述判断装置被配置为：按遗漏的PDCP SDU的序列号从大到小的顺序判断遗漏的PDCP SDU的序列号是否小于所述较小者，并且
    如果判断出一个遗漏的PDCP SDU的序列号小于所述较小者，则不再判断其余遗漏的PDCP SDU的序列号是否小于所述较小者。
  11. 根据权利要求9或10所述的实体，其中，所述实体是在主小区群MCG或用户设备中实现的。
  12. 根据权利要求9所述的实体，还包括：变量存储装置，用于维护并更新两个变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN，使得所述MCG_PDCP_RX_SN指示所述PDCP实体从MCG中的RLC实体或从用户设备中与MCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示所述PDCP实体从SCG中的RLC实体或从用户设备中与SCG中的RLC实体相对应的 RLC实体接收到的PDCP SDU的最大序列号。
  13. 根据权利要求12所述的实体，其中，当所述PDCP实体向其上层实体递交PDCP SDU时，MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者被更新为递交给上层实体的PDCP SDU的最大序列号加1。
  14. 根据权利要求12所述的实体，其中，所述变量存储装置还维护并更新变量Next_PDCP_RX_SN，使其指示递交给上层实体的PDCP SDU的最大序列号加1。
  15. 根据权利要求12所述的实体，其中，所述变量存储装置还维护并更新变量Min_PDCP_RX_SN，使其指示MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
  16. 根据权利要求12至15中任一项所述的实体，其中，所维护的变量的初始值为0。
  17. 一种由分组数据汇聚协议PDCP实体执行的方法，包括：
    将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；以及
    将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
  18. 根据权利要求17所述的方法，其中，所述将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体包括：
    按重排序缓冲区中存储的PDCP SDU的序列号从大到小的顺序判断重排序缓冲区中存储的PDCP SDU的PDCP SDU的序列号是否小于或等于所述较小者，并且
    如果判断出一个PDCP SDU的序列号小于或等于所述较小者，则不再判断其余PDCP SDU的序列号是否小于或等于所述较小者，而将其余PDCP SDU、所判断出的序列号小于所述较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
  19. 根据权利要求17或18所述的方法，其中，所述方法是在主小 区群MCG或用户设备中执行的。
  20. 根据权利要求17所述的方法，其中，所述PDCP实体维护并更新两个变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN，使得所述MCG_PDCP_RX_SN指示所述PDCP实体从MCG中的RLC实体或从用户设备中与MCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示所述PDCP实体从SCG中的RLC实体或从用户设备中与SCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号。
  21. 根据权利要求20所述的方法，其中，当所述PDCP实体向其上层实体递交PDCP SDU时，MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者被更新为递交给上层实体的PDCP SDU的最大序列号加1。
  22. 根据权利要求17所述的方法，其中，所述PDCP实体还维护并更新变量Next_PDCP_RX_SN，使其指示递交给上层实体的PDCP SDU的最大序列号加1。
  23. 根据权利要求17所述的方法，其中，所述PDCP实体还维护并更新变量Min_PDCP_RX_SN，使其指示MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
  24. 根据权利要求17至23中任一项所述的方法，其中，所述PDCP实体维护的变量的初始值为0。
  25. 一种分组数据汇聚协议PDCP实体，包括：
    PDU处理装置，用于将从PDCP实体的下层实体接收的、未按序到达的分组数据汇聚协议协议数据单元PDCP PDU映射为PDCP SDU，并存储在重排序缓冲区中；以及
    递交装置，用于将重排序缓冲区中存储的序列号小于或等于PDCP实体分别从两个下层实体接收到的PDCP SDU的最大序列号中的较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
  26. 根据权利要求25所述的方法，其中，所述递交装置被配置为：
    按重排序缓冲区中存储的PDCP SDU的序列号从大到小的顺序判断重排序缓冲区中存储的PDCP SDU的PDCP SDU的序列号是否小于或等于所述较小者，并且
    如果判断出一个PDCP SDU的序列号小于或等于所述较小者，则不再判断其余PDCP SDU的序列号是否小于或等于所述较小者，而将其余PDCP SDU、所判断出的序列号小于所述较小者的PDCP SDU及其后续连续的PDCP SDU递交给PDCP实体的上层实体。
  27. 根据权利要求25或26所述的实体，其中，所述实体是在主小区群MCG或用户设备中实现的。
  28. 根据权利要求25所述的实体，还包括：变量存储装置，用于维护并更新两个变量MCG_PDCP_RX_SN和SCG_PDCP_RX_SN，使得所述MCG_PDCP_RX_SN指示所述PDCP实体从MCG中的RLC实体或从用户设备中与MCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示所述PDCP实体从SCG中的RLC实体或从用户设备中与SCG中的RLC实体相对应的RLC实体接收到的PDCP SDU的最大序列号。
  29. 根据权利要求28所述的实体，其中，当所述PDCP实体向其上层实体递交PDCP SDU时，MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者被更新为递交给上层实体的PDCP SDU的最大序列号加1。
  30. 根据权利要求28所述的实体，其中，所述变量存储装置还维护并更新变量Next_PDCP_RX_SN，使其指示递交给上层实体的PDCP SDU的最大序列号加1。
  31. 根据权利要求28所述的实体，其中，所述变量存储装置还维护并更新变量Min_PDCP_RX_SN，使其指示MCG_PDCP_RX_SN和SCG_PDCP_RX_SN中的较小者。
  32. 根据权利要求28至31中任一项所述的实体，其中，所维护的变量的初始值为0。
  33. 一种由发送侧的分组数据汇聚协议PDCP实体执行的方法，包括：
    删除删除计时器已到期的PDCP SDU；以及
    向接收侧的PDCP实体发送指示全部或部分已到期PDCP SDU的PDCP控制PDU。
  34. 根据权利要求33所述的方法，其中，所述PDCP控制PDU指示序列号最大的满足如下条件的已到期PDCP SDU：序列号小于所述已 到期PDCP SDU的序列号的所有PDCP SDU已经过期或已被确认发送成功。
  35. 根据权利要求33所述的方法，其中，所述PDCP控制PDU指示满足如下条件的已到期PDCP SDU：所述已到期PDCP SDU的序列号大于发送侧PDCP实体的两个下层实体分别确认的已成功发送的PDCP SDU的最大序列号中的较小者。
  36. 根据权利要求33所述的方法，其中，所述PDCP控制PDU包括多个字段，所述多个字段之一以序列号或位图的形式指示所述已到期PDCP SDU。
  37. 根据权利要求33至36中任一项所述的方法，其中，所述方法是在主小区群MCG或用户设备中执行的。
  38. 根据权利要求35所述的方法，其中，所述发送侧的PDCP实体维护并更新两个变量MCG_PDCP_TX_SN和SCG_PDCP_TX_SN，所述MCG_PDCP_TX_SN指示由MCG中的RLC实体或由用户设备中与MCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示由SCG中的RLC实体或由用户设备中与SCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号。
  39. 根据权利要求38所述的方法，其中，所述PDCP实体还维护并更新变量Min_PDCP_TX_SN，使其指示MCG_PDCP_TX_SN和SCG_PDCP_TX_SN中的较小者。
  40. 根据权利要求38至39中任一项所述的方法，其中，所述PDCP实体维护的变量的初始值为0。
  41. 一种发送侧的分组数据汇聚协议PDCP实体，包括：
    SDU删除装置，用于删除删除计时器已到期的PDCP SDU；以及
    PDCP控制PDU发送装置，用于向接收侧的PDCP实体发送指示全部或部分已到期PDCP SDU的PDCP控制PDU。
  42. 根据权利要求41所述的实体，其中，所述实体是在主小区群MCG或用户设备中实现的。
  43. 根据权利要求41所述的实体，还包括：变量存储装置，用于维护并更新两个变量MCG_PDCP_TX_SN和SCG_PDCP_TX_SN，所述 MCG_PDCP_TX_SN指示由MCG中的RLC实体或由用户设备中与MCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号，所述SCG_PDCP_RX_SN指示由SCG中的RLC实体或由用户设备中与SCG中的RLC实体相对应的RLC实体确认的已成功发送的PDCP SDU的最大序列号。
  44. 根据权利要求43所述的实体，其中，所述变量存储装置还维护并更新变量Min_PDCP_TX_SN，使其指示MCG_PDCP_TX_SN和SCG_PDCP_TX_SN中的较小者。
  45. 根据权利要求43至44中任一项所述的实体，其中，所维护的变量的初始值为0。
PCT/CN2015/073625 2014-03-19 2015-03-04 分组数据汇聚协议pdcp实体及其执行的方法 WO2015139557A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US15/126,481 US20170085492A1 (en) 2014-03-19 2015-03-04 Packet data convergence protocol (pdcp) entity and method performed by the same

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201410103924.4 2014-03-19
CN201410103924.4A CN104935413B (zh) 2014-03-19 2014-03-19 分组数据汇聚协议pdcp实体及其执行的方法

Publications (1)

Publication Number Publication Date
WO2015139557A1 true WO2015139557A1 (zh) 2015-09-24

Family

ID=54122397

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2015/073625 WO2015139557A1 (zh) 2014-03-19 2015-03-04 分组数据汇聚协议pdcp实体及其执行的方法

Country Status (3)

Country Link
US (1) US20170085492A1 (zh)
CN (1) CN104935413B (zh)
WO (1) WO2015139557A1 (zh)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2017192138A2 (en) 2016-05-04 2017-11-09 Intel IP Corporation User equipment (ue) and methods for reception of packets on a split radio bearer
EP3217715A4 (en) * 2014-11-07 2018-06-20 Nec Corporation Wireless communication system, base station, and communication method
CN109792312A (zh) * 2017-03-03 2019-05-21 Oppo广东移动通信有限公司 一种传输数据的方法、终端设备和网络设备
CN110622543A (zh) * 2017-04-28 2019-12-27 瑞典爱立信有限公司 用于分组数据汇聚协议(pdcp)重新排序的网络节点及其中的方法
TWI741146B (zh) * 2017-03-23 2021-10-01 大陸商Ｏｐｐｏ廣東移動通信有限公司 傳輸資料的方法和終端設備

Families Citing this family (42)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101927017B1 (ko) * 2015-02-09 2019-02-20 후아웨이 테크놀러지 컴퍼니 리미티드 Rlc 데이터 패킷 오프로딩 방법 및 기지국
KR101870022B1 (ko) * 2015-04-02 2018-06-22 주식회사 케이티 무선 베어러 재구성 방법 및 그 장치
US10397754B2 (en) * 2015-08-06 2019-08-27 Qualcomm Incorporation Packet data convergence protocol reordering with enhanced component carriers
CN108781403B (zh) * 2016-01-08 2020-12-08 华为技术有限公司 终端设备、接入网设备、空口配置方法和无线通信系统
CN107094299B (zh) * 2016-02-18 2021-03-12 中国移动通信集团公司 自适应于接入网架构的数据处理方法及接入网架构
CN107404769A (zh) * 2016-05-20 2017-11-28 中国移动通信有限公司研究院 一种数据传输方法和装置
CN107438273B (zh) * 2016-05-26 2021-07-30 中兴通讯股份有限公司 承载转移中数据处理状态的确定方法及装置
CN107872842B (zh) * 2016-09-27 2021-01-15 中国移动通信有限公司研究院 一种数据接收方法及装置
CN108234550B (zh) * 2016-12-14 2020-06-12 中国移动通信有限公司研究院 一种信息发送方法、信息接收方法及pdcp实体
US11018984B2 (en) 2017-03-24 2021-05-25 Nokia Technologies Oy Packet data convergence protocol windows with split bearers
KR102293999B1 (ko) * 2017-03-31 2021-08-27 삼성전자 주식회사 무선 통신 시스템에서 장치 및 이의 버퍼 제어 방법
US10999019B2 (en) 2017-03-31 2021-05-04 Samsung Electronics Co., Ltd. Apparatus and buffer control method thereof in a wireless communication system
CN108668320B (zh) 2017-03-31 2020-11-03 维沃移动通信有限公司 一种分段组包方法及接收端
JP7101170B2 (ja) * 2017-05-02 2022-07-14 株式会社Ｎｔｔドコモ 無線通信システム及び無線通信方法
CN108810984B (zh) * 2017-05-05 2020-03-24 维沃移动通信有限公司 数据处理方法及装置
CN109150432A (zh) * 2017-06-15 2019-01-04 夏普株式会社 无线通信方法和设备
CN109150425B (zh) 2017-06-15 2020-04-24 维沃移动通信有限公司 一种数据处理方法、移动终端及计算机可读存储介质
MX2019000419A (es) * 2017-08-10 2019-06-20 Lg Electronics Inc Metodo para realizar un restablecimiento de una entidad pdcp asociada con la entidad um de rlc en un sistema de comunicacion inalambrica y un dispositivo para lo mismo.
BR112020003429A2 (pt) * 2017-08-21 2020-09-08 Beijing Xiaomi Mobile Software Co., Ltd. método e dispositivo para indicar uma rádio portadora
CN109429269B (zh) * 2017-08-22 2022-02-22 中国电信股份有限公司 序列号动态调整方法、装置和基站
CN109428684B (zh) * 2017-08-30 2020-11-27 中国移动通信有限公司研究院 一种数据传输方法、rlc实体及pdcp实体
CN109474651B (zh) * 2017-09-08 2020-08-25 华为技术有限公司 处理数据的方法和设备
WO2019047912A1 (zh) * 2017-09-08 2019-03-14 华为技术有限公司 处理数据的方法和设备
CN111447610B (zh) 2017-09-28 2021-08-31 Oppo广东移动通信有限公司 无线通信的方法和终端设备
CN109728876B (zh) * 2017-10-31 2023-04-18 夏普株式会社 更新发送状态变量的方法和用户设备
WO2019090730A1 (zh) * 2017-11-10 2019-05-16 Oppo广东移动通信有限公司 数据复制下的处理方法及相关设备
CN109803277B (zh) * 2017-11-16 2020-12-22 华为技术有限公司 数据包处理的方法和设备
EP3766279B1 (en) 2018-07-10 2022-12-21 Samsung Electronics Co., Ltd. Method and system for optimizing the feedback mechanism in data link layer
CN110858828A (zh) * 2018-08-22 2020-03-03 普天信息技术有限公司 一种pdcp sdu重排序方法和装置
CN112771992A (zh) * 2018-10-08 2021-05-07 瑞典爱立信有限公司 无线通信网络中的网络节点和方法
CN111756485B (zh) 2019-03-27 2022-09-02 华为技术有限公司 一种控制定时器、数据包处理方法及设备
US11418631B2 (en) * 2019-07-24 2022-08-16 Mediatek Inc. Efficient packet delivery methods and associated communications apparatus
CN111163081B (zh) * 2019-12-26 2022-04-22 展讯通信（上海）有限公司 数据传输方法、装置、设备及存储介质
WO2021148856A1 (en) * 2020-01-23 2021-07-29 Zeku Inc. Techniques for queueing packet data units at a medium access control layer
CN115804034A (zh) * 2020-06-29 2023-03-14 高通股份有限公司 分层式丢失分组检测
CN111711566B (zh) * 2020-07-03 2021-07-27 西安电子科技大学 多路径路由场景下的接收端乱序重排方法
WO2022047670A1 (zh) * 2020-09-02 2022-03-10 华为技术有限公司 处理数据包的方法和通信装置
CN114554544B (zh) * 2020-11-20 2023-08-15 中国移动通信有限公司研究院 一种传输方法、通知方法、传输单元和网络侧设备
CN113473563B (zh) * 2021-07-05 2022-09-02 中国联合网络通信集团有限公司 分配方法、移动网络切换方法、系统、服务器及介质
AU2021480242A1 (en) * 2021-12-23 2024-04-11 Lenovo (Beijing) Limited Methods and apparatuses for supporting a packet discarding operation in a pdcp layer due to a packet loss
CN115277608B (zh) * 2022-07-22 2023-10-24 哲库科技(北京)有限公司 无线通信的方法及设备
CN117499991A (zh) * 2022-07-26 2024-02-02 华为技术有限公司 一种数据交付方法及通信设备

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1951052A (zh) * 2004-04-19 2007-04-18 Lg电子株式会社 用于增强um rlc数据处理的装置和方法
CN101729524A (zh) * 2008-11-03 2010-06-09 大唐移动通信设备有限公司 一种数据处理方法、装置、rlc实体及pdcp实体
CN101874387A (zh) * 2007-11-27 2010-10-27 高通股份有限公司 用于在无线通信系统中处理切换期间的无序分组的方法和装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7936719B2 (en) * 2006-04-20 2011-05-03 Toshiba America Research, Inc. Packet loss prevention during handoff using packet copy-and-forward
CN101841853A (zh) * 2009-03-17 2010-09-22 中兴通讯股份有限公司 一种用户设备以及用户设备接收下行数据的方法
WO2010148356A1 (en) * 2009-06-19 2010-12-23 Research In Motion Limited Mechanisms for data handling during a relay handover with s1 termination at evolved universal terrestrial radio access network access node

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1951052A (zh) * 2004-04-19 2007-04-18 Lg电子株式会社 用于增强um rlc数据处理的装置和方法
CN101874387A (zh) * 2007-11-27 2010-10-27 高通股份有限公司 用于在无线通信系统中处理切换期间的无序分组的方法和装置
CN101729524A (zh) * 2008-11-03 2010-06-09 大唐移动通信设备有限公司 一种数据处理方法、装置、rlc实体及pdcp实体

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3217715A4 (en) * 2014-11-07 2018-06-20 Nec Corporation Wireless communication system, base station, and communication method
US10548145B2 (en) 2014-11-07 2020-01-28 Nec Corporation Wireless communication system, base station, and communication method
US11528715B2 (en) 2014-11-07 2022-12-13 Nec Corporation Wireless communication system, base station, and communication method
WO2017192138A2 (en) 2016-05-04 2017-11-09 Intel IP Corporation User equipment (ue) and methods for reception of packets on a split radio bearer
EP3453131A4 (en) * 2016-05-04 2019-12-18 Intel IP Corporation USER EQUIPMENT (UE) AND METHODS OF RECEIVING PACKETS ON A DIVIDED RADIO MEDIUM
CN109792312A (zh) * 2017-03-03 2019-05-21 Oppo广东移动通信有限公司 一种传输数据的方法、终端设备和网络设备
TWI741146B (zh) * 2017-03-23 2021-10-01 大陸商Ｏｐｐｏ廣東移動通信有限公司 傳輸資料的方法和終端設備
CN110622543A (zh) * 2017-04-28 2019-12-27 瑞典爱立信有限公司 用于分组数据汇聚协议(pdcp)重新排序的网络节点及其中的方法
US11477845B2 (en) 2017-04-28 2022-10-18 Telefonaktiebolaget Lm Ericsson (Publ) Network node and methods therein for packet data convergence protocol (PDCP) reordering

Also Published As

Publication number Publication date
CN104935413B (zh) 2019-12-27
US20170085492A1 (en) 2017-03-23
CN104935413A (zh) 2015-09-23

Similar Documents

Publication Publication Date Title
WO2015139557A1 (zh) 分组数据汇聚协议pdcp实体及其执行的方法
US11696202B2 (en) Communication method, base station, terminal device, and system
US20210051639A1 (en) Method and System for Protocol Layer Enhancements in Data Offload Over Small Cells
US11395365B2 (en) Method and system for handling PDCP operation in wireless communication system
WO2018127238A1 (zh) 信息处理方法及装置
US11006312B2 (en) PDCP packet-based DDDS frame transmission
US11432223B2 (en) Methods and apparatuses for selecting a first base station or a second base station to transmit a packet data unit (PDU) to a user equipment (UE)
WO2015117537A1 (zh) 由辅基站和主基站执行的通信方法以及相应的基站
US8817806B2 (en) Method and apparatus for flow control between RLC and PDCP in a communication
JP4440300B2 (ja) 無線通信システムの分離型媒体アクセス制御プロトコル構造と、これを用いたデータ送受信方法並びにハンドオーバー方法及びそのシステム
US20160255675A1 (en) Method and apparatus for reconfiguring a bearer
EP3447978A1 (en) Data transmission method and device
EP3065456A1 (en) User equipment and method
CN110249659B (zh) 服务质量流重新定位
WO2018103675A1 (zh) 数据流重映射方法及装置和用户设备、ran设备
WO2017185941A1 (zh) 一种数据传输方法及相关设备
KR20140097610A (ko) 다중 무선 접속 기술 기반 통신 시스템에서의 무선 링크 제어 상태 보고 전송 방법 및 장치
KR102307472B1 (ko) 이중 연결 네트워크에서의 연계 기지국의 데이터 전송 속도를 추정하는 방법 및 그 방법이 적용된 기지국
TWI797414B (zh) 用於行動性增強之方法及其使用者設備
US10735549B2 (en) Network apparatus
US20220394554A1 (en) Method and arrangements for desired buffer size target time
CN108200605B (zh) 一种基站的数据传输方法和装置
JP6831828B2 (ja) 基地局
JP2018056855A (ja) ユーザ装置及び信号送信方法
WO2018218416A1 (zh) 用户面数据处理方法、相关设备及系统

Legal Events

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

Ref document number: 15764237

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 15126481

Country of ref document: US

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15764237

Country of ref document: EP

Kind code of ref document: A1