WO2014019240A1 - Procédé de traitement de données, station de base et équipement d'utilisateur - Google Patents

Procédé de traitement de données, station de base et équipement d'utilisateur Download PDF

Info

Publication number
WO2014019240A1
WO2014019240A1 PCT/CN2012/079690 CN2012079690W WO2014019240A1 WO 2014019240 A1 WO2014019240 A1 WO 2014019240A1 CN 2012079690 W CN2012079690 W CN 2012079690W WO 2014019240 A1 WO2014019240 A1 WO 2014019240A1
Authority
WO
WIPO (PCT)
Prior art keywords
sequence number
pdcp sequence
base station
pdcp
number window
Prior art date
Application number
PCT/CN2012/079690
Other languages
English (en)
Chinese (zh)
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 CN201280001992.9A priority Critical patent/CN104509042B/zh
Priority to PCT/CN2012/079690 priority patent/WO2014019240A1/fr
Publication of WO2014019240A1 publication Critical patent/WO2014019240A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection

Definitions

  • the present invention belongs to the field of communications technologies, and in particular, to a data processing method, a base station, and a user equipment.
  • LTE Long Term Evolution
  • long-term evolution A new generation of mobile communication systems such as LTE (Long Term Evolution) , long-term evolution), can improve data transmission speed and achieve a better user experience.
  • LTE generally consists of an access layer and a non-access stratum.
  • the access layer provides the function of delivering in order.
  • the in-order delivery means that the access layer of the sender receives the packets from the upper layer, and after the transmission, the packets are transmitted to the upper layer of the receiver in the same order.
  • FIG. 1 the access layer provided by the prior art is provided. Schematic diagram of the submission of the upper layer.
  • the access layer is further subdivided into PDCP (Packet Data Convergence Protocol, Packet Data Convergence Protocol, RLC (Radio Link Control, Radio Link Control Layer Protocol), MAC (Medium Access) Control, medium access control protocol, physical layer and other levels.
  • PDCP Packet Data Convergence Protocol
  • RLC Radio Link Control, Radio Link Control Layer Protocol
  • MAC Medium Access Control
  • the orderly delivery function is provided by the RLC layer.
  • the sender's RLC adds each packet to the MAC layer for processing. If the MAC layer and the physical layer are out of order during transmission, the receiver's RLC will store the packet received first, and wait until the packet is received. After the other packets arrive, they are submitted to the PDCP layer in order.
  • FIG. 2 is a schematic diagram of the sequential delivery of the RLC layer when the base station is switched according to the prior art.
  • the sender sent a total of 5 packets, the receiver has successfully received the 1, 3, and 5 packets, and the 2 and 4 packets have not been successfully received.
  • the access layer of the receiver sends the first packet to the upper layer, and the third and fifth packets are stored in its own cache, waiting for the arrival of the second and fourth packets. If the first packet is received, the receiving layer of the receiving party will submit the 2nd and 3rd packets respectively to the upper layer in order, and continue to wait for the 4th packet. After the arrival of the 4th packet, the upper layer will be submitted to the upper layer in sequence. No. 5 package; if the first packet is received, the access layer of the receiver will save the packet No. 4 to the cache, and continue to wait for the second packet. After the arrival of the second packet, the upper layer will submit 2, 3 respectively. 4, 5 package.
  • RLC can guarantee to deliver in order, but when the base station switches, because the RLC needs to be reset, the RLC stored data packets are completely emptied, so the RLC's sequential delivery function is no longer effective. Need to use PDCP The orderly delivery function. The receiver's RLC first sends the packet it receives to the PDCP first, and then clears its own cache. After the handover, the PDCP of the receiver continues to receive the packets, and then delivers the packets to the upper layer in order.
  • 3GPP uses data forwarding (Data Forwarding, that is, the source base station transmits some packets stored in the PDCP layer to the target base station through the X2 interface, so that the target base station restores the state of the source base station in advance, and the packets transmitted through the X2 interface do not need to be in the air interface. Transmitted.
  • Data Forwarding that is, the source base station transmits some packets stored in the PDCP layer to the target base station through the X2 interface, so that the target base station restores the state of the source base station in advance, and the packets transmitted through the X2 interface do not need to be in the air interface. Transmitted.
  • the source base station and the target base station are required to use the PDCP sequence number of the same length (PDCP).
  • PDCP PDCP sequence number of the same length
  • the window size of the PDCP is also determined by the length of the PDCP sequence number.
  • the serial number of the PDCP is up to 12 bits.
  • the window size of the PDCP is 2 (12-1), that is, up to 2048 packets can be stored in the buffer of the PDCP. If it exceeds 2048, there must be two. Pack of PDCP The SN is the same and cannot be recognized.
  • 3GPP has agreed to extend the PDCP SN from the 11th edition, that is, the base station can support extended PDCP. SN. If the user equipment (UE) switches from a base station using the extended PDCP SN to a base station that does not support the extended PDCP SN, the existing data forwarding method has a problem of packet loss.
  • UE user equipment
  • the embodiment of the invention provides a data processing method to solve the problem of data packet loss existing when a user equipment switches between different versions of base stations.
  • the data processing method comprises:
  • the source base station When the user equipment UE is handed over from the source base station to the target base station, the source base station will not receive the data packet that is not confirmed by the UE in the downlink normal packet data convergence protocol PDCP sequence number window, and the remaining data in the downlink extended PDCP sequence number window. Sending a packet to the target base station, where the remaining data packet in the downlink extended PDCP sequence number window does not include the data packet in the downlink normal PDCP sequence number window;
  • the downlink extended PDCP sequence number window includes the downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the method further includes:
  • the source base station discards the remaining data packets in the uplink extended PDCP sequence number window, and the remaining data packets in the uplink extended PDCP sequence number window do not include the data packets in the uplink regular PDCP sequence number window;
  • the uplink extended PDCP sequence number window includes the uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink normal PDCP sequence number window have the same starting position.
  • the source base station is not in the downlink normal PDCP sequence number window
  • the acknowledged data packet is sent to the target base station, and specifically includes:
  • the source base station converts a PDCP sequence number of a data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window into a sequence number of a PDCP sequence number length used by the target base station;
  • the source base station sends, to the target base station, a PDCP service data unit SDU corresponding to a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window, and a sequence number of a PDCP sequence number length used by the target base station.
  • the method further includes:
  • the remaining data packet in the downlink normal PDCP sequence number window does not include a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the source base station the data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window
  • the sending to the target base station specifically includes:
  • the source base station removes a PDCP that is not acknowledged by the UE in the normal PDCP sequence number window, and removes the PDCP allocated by the source base station. a serial number, and transmitting, to the target base station, a PDCP SDU corresponding to a data packet that is not acknowledged by the UE in the normal PDCP sequence number window.
  • the method further includes:
  • the source base station removes the remaining data packets in the downlink normal PDCP sequence number window from the PDCP allocated by the source base station. a serial number, and transmitting, to the target base station, a PDCP SDU corresponding to the remaining data packet in the downlink normal PDCP sequence number window;
  • the remaining data packet in the downlink normal PDCP sequence number window does not include a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the data processing method includes
  • the UE After the user equipment UE is handed over from the source base station to the target base station, the UE will not receive the data packet that is not confirmed by the source base station in the PDCP sequence number window of the uplink normal packet data convergence protocol, and the uplink extended PDCP sequence number window after the handover.
  • the remaining data packets are sent to the target base station, and the remaining data packets in the uplink extended PDCP sequence number window do not include the data packets in the uplink regular PDCP sequence number window;
  • the uplink extended PDCP sequence number window includes the uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink normal PDCP sequence number window have the same starting position.
  • the method further includes:
  • the UE discards the remaining data packets in the downlink extended PDCP sequence number window, and the remaining data packets in the downlink extended PDCP sequence number window do not include the data packets in the downlink normal PDCP sequence number window;
  • the downlink extended PDCP sequence number window includes the downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the UE is not the source base station in the uplink normal PDCP sequence number window
  • the acknowledged data packet is sent to the target base station, and specifically includes:
  • the method further includes:
  • the UE will PDCP of the remaining data packets in the uplink regular PDCP sequence number window Converting a sequence number into a sequence number of a PDCP sequence number length used by the target base station, and reconstructing a PDCP corresponding to the remaining data packet in the uplink normal PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station a PDU, and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink regular PDCP sequence number window does not include a data packet in the normal PDCP sequence number window that is not confirmed by the source base station.
  • the method further includes:
  • Transmitting, by the UE, PDCP of remaining data packets in the uplink PDCP sequence number window Converting a sequence number into a sequence number of a PDCP sequence number length used by the target base station, and reconstructing a remaining data packet corresponding to the PDCP in the uplink extended PDCP sequence number window according to a sequence number of a PDCP sequence number length used by the target base station a PDU, and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the regular PDCP sequence number window.
  • the UE is not in the uplink normal PDCP sequence number window
  • the acknowledged data packet is sent to the target base station, and specifically includes:
  • the UE removes the PDCP sequence number allocated by the UE from the data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window, and re-establishes the uplink according to the length of the PDCP sequence number used by the target base station.
  • the data packet that is not acknowledged by the source base station in the normal PDCP sequence number window is allocated a PDCP sequence number, and the data that is not confirmed by the source base station in the uplink normal PDCP sequence number window is reconstructed by using the reassigned PDCP sequence number.
  • Package corresponding PDCP a PDU and transmitting the reconstructed PDCP PDU to the target base station.
  • the method further includes:
  • the UE removes the remaining data packet in the uplink normal PDCP sequence number window from the PDCP sequence number allocated by the UE, and re-creates the uplink normal PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the remaining data packet is assigned a PDCP sequence number, and the PDCP corresponding to the remaining data packet in the uplink normal PDCP sequence number window is reconstructed by using the reassigned PDCP sequence number.
  • a PDU and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink regular PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window that is not confirmed by the source base station.
  • the method further includes:
  • the UE removes the remaining data packet in the uplink extended PDCP sequence number window from the PDCP allocated by the UE a serial number, and re-assigning a PDCP sequence number to the remaining data packets in the uplink extended PDCP sequence number window according to the PDCP sequence number length used by the target base station, and reconstructing the uplink by using the reassigned PDCP sequence number Extend the PDCP corresponding to the remaining packets in the PDCP sequence number window a PDU, and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink normal PDCP sequence number window.
  • the base station includes:
  • a sending unit configured to: when the user equipment UE is switched by the base station to the target base station, the data packet that is not confirmed by the UE in the downlink normal packet data convergence protocol PDCP sequence number window, and the downlink extended PDCP sequence number window And sending the remaining data packet to the target base station, where the remaining data packet in the downlink extended PDCP sequence number window does not include the data packet in the downlink normal PDCP sequence number window;
  • the downlink extended PDCP sequence number window includes the downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the sending unit is further configured to send a data packet that is received by the base station in the uplink regular PDCP sequence number window to the target base station;
  • the base station further includes:
  • a discarding unit configured to discard the remaining data packet in the uplink extended PDCP sequence number window, where the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink normal PDCP sequence number window;
  • the uplink extended PDCP sequence number window includes the uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink normal PDCP sequence number window have the same starting position.
  • the base station further includes:
  • a converting unit configured to convert a PDCP sequence number of a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window into a sequence number of a PDCP sequence number length used by the target base station;
  • the sending unit is further configured to send, to the target base station, a PDCP service data unit SDU corresponding to a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window, and a length of a PDCP sequence number used by the target base station that is obtained. Serial number.
  • the converting unit is further configured to: use a PDCP sequence of the remaining data packets in the downlink normal PDCP sequence number window Converting the number into a serial number of the length of the PDCP sequence number used by the target base station;
  • the sending unit is further configured to: PDCP corresponding to the remaining data packets in the downlink normal PDCP sequence number window Sending, by the SDU, the acquired sequence number of the PDCP sequence number length used by the target base station to the target base station;
  • the remaining data packet in the downlink normal PDCP sequence number window does not include a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the base station further includes:
  • a stripping unit configured to remove a PDCP that is not acknowledged by the UE in the normal PDCP sequence number window, and remove the PDCP allocated by the source base station serial number;
  • the sending unit is further configured to: PDCP corresponding to the data packet that is not confirmed by the UE in the normal PDCP sequence number window
  • the SDU is sent to the target base station.
  • the stripping unit is further configured to remove the remaining data packet in the downlink normal PDCP sequence number window.
  • PDCP assigned by the source base station serial number
  • the sending unit is further configured to: PDCP corresponding to the remaining data packets in the downlink normal PDCP sequence number window Sending an SDU to the target base station;
  • the remaining data packet in the downlink normal PDCP sequence number window does not include a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the user equipment includes:
  • a sending unit configured to: after the user equipment is switched by the source base station to the target base station, the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window, and the remaining data packet in the uplink extended PDCP sequence number window Sending to the target base station, the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink normal PDCP sequence number window;
  • the uplink extended PDCP sequence number window includes the uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink normal PDCP sequence number window have the same starting position.
  • the user equipment further includes:
  • a discarding unit configured to discard the remaining data packet in the downlink extended PDCP sequence number window, where the remaining data packet in the downlink extended PDCP sequence number window does not include the data packet in the downlink normal PDCP sequence number window;
  • the downlink extended PDCP sequence number window includes the downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the method further includes:
  • a converting unit configured to convert a PDCP sequence number of a data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window into a sequence number of a PDCP sequence number length used by the target base station;
  • a first constructing unit configured to reconstruct, according to the obtained serial number of the length of the PDCP sequence number used by the target base station, a PDCP service data unit corresponding to the data packet that is not confirmed by the source base station in the uplink PDCP sequence number window PDU;
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station.
  • the converting unit is further configured to: use the PDCP of the remaining data packet in the uplink regular PDCP sequence number window Converting the serial number into a serial number of the length of the PDCP sequence number used by the target base station;
  • the first constructing unit is further configured to reconstruct, according to the acquired sequence number of the PDCP sequence number length used by the target base station, a PDCP corresponding to the remaining data packet in the uplink normal PDCP sequence number window.
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink regular PDCP sequence number window does not include a data packet in the normal PDCP sequence number window that is not confirmed by the source base station.
  • the converting unit is further configured to extend PDCP of the remaining data packets in the uplink extended PDCP sequence number window Converting the serial number into a serial number of the length of the PDCP sequence number used by the target base station;
  • the first constructing unit is further configured to reconstruct, according to the acquired sequence number of the length of the PDCP sequence number used by the target base station, the remaining data packet corresponding to the PDCP in the uplink extended PDCP sequence number window.
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the regular PDCP sequence number window.
  • the user equipment further includes:
  • a re-segment unit configured to remove a PDCP sequence number allocated by the UE from a data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window, and re-establish the PDCP sequence number length according to the target base station Allocating a PDCP sequence number to a data packet that is not acknowledged by the source base station in the uplink regular PDCP sequence number window;
  • a second constructing unit configured to reconstruct, according to the obtained re-allocated PDCP sequence number, a PDCP corresponding to a data packet that is not confirmed by the source base station in the uplink normal PDCP sequence number window PDU;
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station.
  • the re-dividing unit is further configured to use the remaining data packet in the uplink conventional PDCP sequence number window Deleting the PDCP sequence number allocated by the UE, and re-assigning the PDCP sequence number to the remaining data packets in the uplink regular PDCP sequence number window according to the PDCP sequence number length used by the target base station;
  • the second constructing unit is further configured to reconstruct, according to the obtained re-allocated PDCP sequence number, a PDCP corresponding to the remaining data packet in the uplink normal PDCP sequence number window.
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink regular PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window that is not confirmed by the source base station.
  • the re-segment unit is further used to The remaining data packets in the uplink extended PDCP sequence number window are removed from the PDCP allocated by the UE. a serial number, and re-assigning a PDCP sequence number to the remaining data packets in the uplink extended PDCP sequence number window according to the length of the PDCP sequence number used by the target base station;
  • the second constructing unit is further configured to reconstruct, according to the obtained re-allocated PDCP sequence number, a PDCP corresponding to the remaining data packet in the uplink extended PDCP sequence number window.
  • the sending unit is further configured to send the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink normal PDCP sequence number window.
  • the embodiment of the present invention uses the extended PDCP from the UE.
  • the source base station of the SN switches to use the regular PDCP
  • the source base station sends the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station, and the UE sends the uplink routine.
  • the data packet in the PDCP sequence number window that is not acknowledged by the source base station, and the remaining data packet in the uplink extended PDCP sequence number window are sent to the target base station, thereby avoiding the extended PDCP in the UE from using.
  • FIG. 1 is a schematic diagram of an order delivery of an access layer and an upper layer provided by the prior art
  • FIG. 2 is a schematic diagram of sequential delivery of an RLC layer when a base station is switched according to the prior art
  • FIG. 3 is a flowchart of an implementation of a data processing method according to an embodiment of the present invention.
  • FIG. 4 is a flowchart of an implementation of a data processing method according to another embodiment of the present invention.
  • FIG. 5 is a flowchart of an implementation of a data processing method according to another embodiment of the present invention.
  • FIG. 6 is a flowchart of an interaction implementation of a data processing method according to an embodiment of the present invention.
  • FIG. 7 is a schematic diagram of a method for processing downlink data according to an embodiment of the present invention.
  • FIG. 8 is a schematic diagram of a method for processing uplink data according to another embodiment of the present invention.
  • FIG. 9 is a flowchart of an implementation of a data forwarding method according to another embodiment of the present invention.
  • FIG. 10 is a schematic diagram of a method for processing downlink data according to another embodiment of the present invention.
  • FIG. 11 is a flowchart of an implementation of a data processing method according to another embodiment of the present invention.
  • FIG. 12 is a flowchart of an implementation of a data processing method according to another embodiment of the present invention.
  • FIG. 13 is a schematic diagram of processing of downlink data according to another embodiment of the present invention.
  • FIG. 14 is a structural block diagram of a base station according to an embodiment of the present invention.
  • FIG. 15 is a structural block diagram of a user equipment according to an embodiment of the present invention.
  • FIG. 16 is a structural diagram of a base station according to an embodiment of the present invention.
  • FIG. 17 is a structural diagram of a user equipment according to an embodiment of the present invention.
  • the following description will be made by way of specific embodiments.
  • the following embodiments are applicable to the scenario where the source base station uses the extended PDCP when the UE switches from the source base station to the target base station.
  • SN while the target base station uses a regular PDCP SN.
  • the length of the PDCP SN of the source base station is 14 bits, and the PDCP of the target base station is used.
  • the length of the SN is 13 bits as an example.
  • FIG. 3 is a flowchart showing an implementation process of a data processing method according to an embodiment of the present invention.
  • the execution body of the method is a source base station, and the details are as follows:
  • the source base station sends the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include data packets in the downlink normal PDCP sequence number window.
  • the source base station when the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, the source base station determines the start identifier of the uplink regular PDCP sequence number window and the downlink normal PDCP sequence number window. Start tag.
  • the initial identifier of the uplink normal PDCP sequence number window refers to the identifier of the first data packet that is not received by the source base station in the uplink data.
  • the initial identifier of the downlink normal PDCP sequence number window is the identifier of the first data packet transmitted by the source base station to the UE and not confirmed by the UE in the downlink data. Where the identification of the data packet is the PDCP of the data packet SN.
  • the source base station informs the UE of the start identifier of the uplink regular PDCP sequence number window and the start identifier of the downlink regular PDCP sequence number window.
  • the source base station may notify the UE of the start identifier of the uplink regular PDCP sequence number window and the start identifier of the downlink regular PDCP sequence number window by any one of the following methods: the source base station has an uplink regular PDCP in the handover command sent to the UE.
  • the start identifier of the sequence number window and the start identifier of the downlink normal PDCP sequence number window, or the source base station informs the UE of the start identifier of the uplink normal PDCP sequence number window and the downlink normal PDCP sequence number through MAC layer signaling or other underlying signaling.
  • the starting identifier of the window is not limited to MAC layer signaling or other underlying signaling.
  • the method further comprises:
  • the source base station determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window; the source base station determines the uplink regular PDCP sequence according to the start identifier of the uplink regular PDCP sequence number window. The boundary of the number window and the boundary of the uplink extended PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the uplink conventional PDCP sequence number window and the downlink regular PDCP sequence number window refer to the conventional PDCP.
  • the length of the SN determines the window.
  • the uplink extended PDCP sequence number window and the downlink extended PDCP sequence number window refer to a window determined according to the length of the extended PDCP SN. An example is as follows:
  • the source base station sends the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station through the X2 interface.
  • the specific process of the source base station transmitting the data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window to the target base station is as follows:
  • the source base station carries the PDCP that is not acknowledged by the UE in the downlink normal PDCP sequence number window.
  • the SN is sent to the target base station through the X2 interface.
  • the PDCP SN carried in the data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window is the PDCP of the PDCP SN length converted to the target base station. SN.
  • the source base station converts the PDCP sequence number of the data packet not confirmed by the UE in the downlink normal PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station;
  • the source base station sends, to the target base station, the PDCP service data unit SDU corresponding to the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the sequence number of the PDCP sequence number length used by the target base station.
  • the source base station is adopted in PDCP.
  • the PDCP sequence length PDCP SN in the upper layer protocol header (such as the GTP header) outside the SDU carries the PDCP sequence number length of the target base station.
  • the SN is sent to the target base station.
  • the data packets not confirmed by the UE in the downlink normal PDCP sequence number window sent by the source base station to the target base station carry the PDCP of the PDCP sequence number length used by the target base station.
  • An example is as follows:
  • the source base station first converts the 14-bit PDCP SN of the data packet not confirmed by the UE in the downlink normal PDCP sequence number window into the 13-bit PDCP. SN.
  • the specific conversion method is: directly remove the high position of the 14-bit PDCP SN.
  • the source base station will perform the PDCP corresponding to the data packet not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the SDU and the converted PDCP SN are sent to the target base station through the X2 interface, so that the data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window sent to the target base station carries the converted PDCP. SN.
  • the source base station sends the data packet that is not acknowledged by the UE in the downlink normal PDCP sequence number window to the target base station, and specifically includes:
  • the source base station removes the PDCP allocated by the source base station from the data packet not confirmed by the UE in the regular PDCP sequence number window.
  • the serial number and the PDCP SDU corresponding to the data packet not confirmed by the UE in the normal PDCP sequence number window is sent to the target base station.
  • the method further comprises:
  • the source base station removes the remaining data packets in the downlink normal PDCP sequence number window and removes the PDCP allocated by the source base station.
  • the serial number and the PDCP SDU corresponding to the remaining data packets in the downlink normal PDCP sequence number window are sent to the target base station.
  • the remaining data packet in the downlink normal PDCP sequence number window does not include the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the source base station sends the remaining data packets in the downlink extended PDCP sequence number window to the target base station through the X2 interface, which specifically includes:
  • the source base station sends the remaining data packet in the downlink extended PDCP sequence number window as a new data packet to the target base station through the X2 interface.
  • the specific process is as follows:
  • the source base station removes the remaining data packets in the downlink extended PDCP sequence number window and removes the PDCP allocated by the source base station. SN, the source base station sequentially transmits the PDCP SDU corresponding to the remaining data packets in the downlink extended PDCP sequence number window to the target base station. Removing PDCP SN in the field is also called stripping PDCP. SN.
  • the method further comprises:
  • the source base station directly transmits the data packets received from the gateway outside the downlink extended PDCP sequence number window to the target base station in order.
  • the method further comprises:
  • the source base station transmits the data packet received by the source base station in the uplink conventional PDCP sequence number window to the target base station.
  • the source base station sends the data packet received by the source base station in the uplink normal PDCP sequence number window to the target base station through the X2 interface, and the specific process is as follows:
  • the source base station carries the PDCP that the source base station has received in the uplink conventional PDCP sequence number window.
  • the SN is sent to the target base station through the X2 interface.
  • the PDCP SN carried by the data packet received by the source base station in the uplink conventional PDCP sequence number window is the PDCP of the PDCP SN length converted to the target base station. SN.
  • the source base station will uplink PDCP sequence number window to the PDCP of the data packet received by the source base station. Converting the SN into a PDCP SN of a PDCP sequence number length used by the target base station;
  • the source base station sends, to the target base station, the PDCP corresponding to the data packet received by the source base station in the uplink regular PDCP sequence number window.
  • the PDCP SN of the length of the PDCP sequence number used by the SDU and the target base station.
  • the source base station is adopted in PDCP.
  • the PDCP sequence length PDCP SN in the upper layer protocol header (such as the GTP header) outside the SDU carries the PDCP sequence number length of the target base station.
  • the SN is sent to the target base station. In this way, the data packets received by the source base station in the uplink regular PDCP sequence number window sent by the source base station to the target base station all carry the PDCP of the PDCP sequence number length used by the target base station. SN.
  • the method comprises:
  • the source base station discards the remaining data packets in the uplink extended PDCP sequence number window, wherein the remaining data packets in the uplink extended PDCP sequence number window do not include the data packets in the uplink regular PDCP sequence number window.
  • FIG. 4 is a flowchart showing an implementation of a data processing method according to another embodiment of the present invention. The method is applicable to the UE side corresponding to the method shown in FIG.
  • the UE After the UE is handed over to the target base station by the source base station, the UE sends the data packet that is not confirmed by the source base station in the uplink normal PDCP sequence number window, and the remaining data packet in the uplink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink regular PDCP sequence number window.
  • the UE when the UE is handed over from the source base station to the target base station, the UE inferrs the start identifier of the uplink regular PDCP sequence number window and the start identifier of the downlink normal PDCP sequence number window, or the UE receives the uplink from the source base station.
  • the start identifier of the regular PDCP sequence number window and the start identifier of the downlink normal PDCP sequence number window when the UE is handed over from the source base station to the target base station, the UE inferrs the start identifier of the uplink regular PDCP sequence number window and the start identifier of the downlink normal PDCP sequence number window, or the UE receives the uplink from the source base station.
  • the start identifier of the regular PDCP sequence number window and the start identifier of the downlink normal PDCP sequence number window when the UE is handed over from the source base station to the target base station, the UE inferrs the start identifier of the uplink regular PD
  • the UE determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window; the UE determines the uplink regular PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window.
  • the boundary and the uplink extend the boundary of the PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the UE sends the data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window and the remaining data packet in the uplink extended PDCP sequence number window to the target base station through the wireless interface.
  • the specific process of the UE transmitting the data packet that is not acknowledged by the source base station in the uplink regular PDCP sequence number window to the target base station is as follows:
  • the UE will PDCP of the data packet in the uplink normal PDCP sequence number window that is not confirmed by the source base station. Converting the SN into a PDCP SN of a PDCP sequence number length used by the target base station;
  • the SN reconstructs the PDCP service data unit PDU corresponding to the data packet that is not acknowledged by the source base station in the uplink PDCP sequence number window, and reconstructs the PDCP.
  • the PDU is sent to the target base station.
  • the UE sends the remaining data packets in the uplink extended PDCP sequence number window to the target base station through the wireless interface.
  • the specific process is as follows:
  • the UE will uplink the PDCP of the remaining data packets in the PDCP sequence number window. Converting the serial number into a serial number of the length of the PDCP sequence number used by the target base station;
  • the UE sends a data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window to the target base station, and specifically includes:
  • the UE removes the PDCP sequence number allocated by the UE from the data packet that is not confirmed by the source base station in the uplink normal PDCP sequence number window, and re-establishes the uplink normal PDCP sequence number window in the uplink normal PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the data packet is assigned a PDCP sequence number, and the PDCP sequence number in the uplink conventional PDCP sequence number window is reconstructed from the PDCP sequence number window.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the method further comprises:
  • the UE removes the PDCP sequence number allocated by the UE from the remaining data packets in the uplink normal PDCP sequence number window, and re-assigns the PDCP sequence number to the remaining data packets in the uplink regular PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the reassigned PDCP sequence number reconstructs the PDCP corresponding to the remaining packets in the uplink regular PDCP sequence number window. a PDU and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink regular PDCP sequence number window does not include the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window.
  • the method further comprises:
  • the UE removes the remaining data packets in the uplink extended PDCP sequence number window and removes the PDCP allocated by the UE. Serial number, and re-assign the PDCP sequence number to the remaining data packets in the uplink extended PDCP sequence number window according to the length of the PDCP sequence number used by the target base station, and reconstruct the remaining in the uplink extended PDCP sequence number window by using the reassigned PDCP sequence number.
  • PDCP corresponding to the packet a PDU and transmitting the reconstructed PDCP PDU to the target base station;
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window.
  • the method further comprises:
  • the UE sends the data packet received from the upper layer outside the uplink extended PDCP sequence number window to the target base station through the wireless interface, and the specific process is as follows:
  • the UE allocates PDCP according to the PDCP SN used by the target base station for the data packet received from the upper layer outside the window of the uplink extended PDCP sequence number.
  • the SN constructs a PDCP PDU with the allocated PDCP SN, and sends the constructed PDCP PDU to the target base station in sequence.
  • the UE discards the remaining data packets in the downlink extended PDCP sequence number window, and after establishing a connection with the target base station, continues to receive data packets from the target base station, and the PDCP layer of the UE will The received data packets are delivered to the upper layer in order.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include the data packets in the downlink normal PDCP sequence number window.
  • the target base station receives, from the source base station, the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window from the source base station, And after receiving the data packet received from the gateway outside the window of the extended PDCP sequence number, the PDCP is carried.
  • the data packet of the SN is transmitted to the UE by using the PDCP SN carried by the data packet, and the PDCP service data unit (PDU) is configured to be sent to the UE; for the data packet not carrying the PDCP SN, the PDCP is allocated to the PDCP SN. After the SN, the PDCP PDU is constructed and sent to the UE.
  • the target base station receives the data packet received by the source base station in the uplink normal PDCP sequence number window from the source base station through the X2 interface, and after receiving the underlying connection with the UE, continues to receive the uplink conventional PDCP sequence number from the UE through the wireless interface.
  • the data packet acknowledged by the source base station and the remaining data packets in the uplink extended PDCP sequence number window, and the PDCP layer of the target base station delivers the received data packet to the upper layer in order.
  • the source base station when the UE switches from the source base station to the target base station, the source base station will not identify the data packet in the downlink normal PDCP sequence number window that is not confirmed by the UE, and the downlink extended PDCP sequence number window.
  • the remaining data packets are sent to the target base station through the X2 interface, and the UE discards the remaining data packets in the downlink extended PDCP sequence number window, and continues to receive the data packets from the target base station, and submits the received data packets to the upper layer in order, thereby avoiding The problem of data packet loss and data packet repetition of downlink data when the UE switches from the source base station to the target base station; the source base station sends the data packet received by the source base station in the uplink conventional PDCP sequence number window to the target base station through the X2 interface, and the UE will The data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window, and the remaining data packet in the uplink extended PDCP sequence number window are sent to the target base station through the wireless interface, thereby avoiding uplink data when the UE switches from the source base station to the target base station.
  • the problem of packet loss and packet duplication are sent to the target base station through the wireless interface, thereby avoiding uplink data when
  • FIG. 5 is a flowchart showing an implementation process of a data processing method according to another embodiment of the present invention. The method of the embodiment is further improved on the basis of FIG. 3 or FIG. 4, and is described in detail as follows:
  • the source base station sends a handover command to the UE.
  • the handover command has a start identifier of the uplink regular PDCP sequence number window and a start identifier of the downlink regular PDCP sequence number window.
  • the method further comprises:
  • the source base station When the UE is handed over from the source base station to the target base station, the source base station sends a handover request to the target base station;
  • the source base station receives the handover response sent by the target base station.
  • the handover response has a target base station that does not support extended PDCP.
  • the information of the serial number window is not limited to the following abbreviations: “A” and “B” in the following abbreviations: “A” in the following abbreviations: “A” in the following abbreviations: “A” in the following abbreviations: “A” in the following abbreviations, PDCP, etc.
  • the source base station when the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, the source base station selects the target base station, and sends a handover request to the selected target base station, where the target base station is After receiving the handover request sent by the source base station, if it agrees to receive the UE, it returns a handover response to the source base station to complete the handover negotiation between the source base station and the target base station.
  • the source base station sends the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include data packets in the downlink normal PDCP sequence number window.
  • the source base station learns that the target base station does not support the extended PDCP.
  • the UE sends a handover command to the UE.
  • the UE processes the uplink and downlink data according to the start identifier of the downlink window and the start identifier of the uplink window in the handover command. Switching to the target base station, thereby avoiding the problem of packet loss and data packet duplication when the UE switches between different versions of the base station, and avoiding the handover delay of the UE when switching between different versions of the base stations problem.
  • FIG. 6 is an interaction implementation process of a data processing method according to an embodiment of the present invention.
  • the UE sends a measurement report to the source base station.
  • the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, the source base station selects the target base station, and sends a handover request to the selected target base station.
  • the target base station After receiving the handover request sent by the source base station, if the target base station agrees to receive the UE, it returns a handover response to the source base station to complete the handover negotiation between the source base station and the target base station.
  • the source base station learns that the target base station does not support the extended PDCP SN according to the handover response returned by the target base station.
  • the source base station sends a handover command to the UE.
  • the handover command has a start identifier of the downlink window and a start identifier of the uplink window.
  • the source base station and the UE process the uplink and downlink data.
  • the specific processing process of the source base station and the UE processing the uplink and downlink data is shown in FIG. 3 and FIG. 4 , and details are not described herein again.
  • the UE switches to the target base station, and after establishing an underlying connection with the target base station, the data transmission is continued, so that the UE switches from the source base station to the target base station.
  • FIG. 7 is a flowchart of processing downlink data provided by an embodiment of the present invention.
  • an extended PDCP used by a source base station is used.
  • the SN is 14 bits, and the PDCP SN used by the target base station is 13 bits as an example.
  • the identifier of the first data packet that is not acknowledged by the UE in the downlink data that is sent from the source base station to the UE is the 56th data packet, that is, the start identifier of the downlink normal PDCP sequence number window determined by the source base station. It is 56, and it is assumed that when the handover is required, the packets of numbers 57 to 4152 in packets 56 to 4153 transmitted from the source base station to the UE have been confirmed by the UE.
  • the process of processing downlink data when the UE performs base station handover is as follows:
  • the source base station When the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, the source base station selects the target base station, and sends a handover request to the selected target base station, where the target base station receives the source base station and sends the handover request. After the handover request, the handover response is returned to the source base station to complete the handover negotiation between the source base station and the target base station.
  • the source base station learns that the target base station does not support extended PDCP according to the handover response returned by the target base station.
  • the source base station sends a handover command to the UE that carries the start identifier (ie, 56) of the downlink normal PDCP sequence number window.
  • the source base station determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier (ie, 56) of the downlink normal PDCP sequence number window.
  • the source base station transmits the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station. That is, the start of the downlink normal PDCP sequence number window is 56, and the termination is 4151. Since the data packets from the source base station to the UE are all confirmed by the UE, the downlink normal PDCP sequence number window is not The packet confirmed by the UE is PDCP. The SN is 56 packets. The remaining data packet in the downlink extended PDCP sequence number window is PDCP. The SN is a packet of 4152 and 4153.
  • the source base station will PDCP of the packet with the PDCP SN of 56 in the downlink normal PDCP sequence number window. After the high bit of the SN is removed, the converted PDCP SN is carried to the target base station. At the same time, the source base station removes the PDCP from the packets with the PDCP SN of 4152 and 4153. After the SN is sent to the target station, the data packet newly received from the gateway is directly sent to the target base station.
  • the target base station On the target base station side, the target base station receives the data packet from the source base station through the X2 interface, and carries the PDCP.
  • the data packet of the SN is used to construct the PDCP PDU to be transmitted to the UE.
  • the target base station For the data packet not carrying the PDCP SN, the target base station allocates the PDCP SN to construct the PDCP.
  • the PDU and the constructed PDCP PDU is sent to the UE through the wireless interface.
  • the data packets of 57 to 4151 and 4152 are received and acknowledged, and after receiving the handover command sent by the source base station, according to the handover command
  • the start identifier (ie, 56) of the downlink normal PDCP sequence number window determines the boundary of the downlink normal PDCP sequence number window (ie, 56-4151), discards the data packet outside the downlink normal PDCP sequence number window (eg, 4152), and the source base station Switching to the target base station, after establishing an underlying connection with the target base station, continuing to receive data packets from the target base station, the PDCP layer of the UE sequentially delivers the data packet to the upper layer of the UE.
  • FIG. 8 is a flowchart of processing uplink data according to an embodiment of the present invention.
  • an extended PDCP used by a source base station is used.
  • the SN is 14 bits, and the PDCP SN used by the target base station is 13 bits as an example.
  • the identifier of the first data packet that is not received by the source base station in the uplink data sent from the UE to the source base station is the 56th data packet, so the start identifier of the uplink normal PDCP sequence number window determined by the source base station It is 56, and it is assumed that when the handover is required, the data packets No. 57, 59 to 4152 transmitted from the UE to the source base station have been confirmed by the source base station.
  • the processing flow of the uplink data during the handover process is as follows:
  • the source base station After the source base station performs handover negotiation with the target base station, it is learned that the target base station does not support extended PDCP.
  • the source base station sends a handover command to the UE that carries the start identifier (ie, 56) of the uplink normal PDCP sequence number window.
  • the source base station determines the termination identifier (ie, 4151) of the uplink regular PDCP sequence number window according to the start identifier (ie, 56) of the uplink regular PDCP sequence number window.
  • the source base station will uplink PDCP of the data packet that has been successfully received in the normal PDCP sequence number window.
  • the PDCP SDU and the converted PDCP SN are sent to the target base station (ie, packets 57, 59 to 4151) through the X2 interface.
  • the data packet outside the window of the normal PDCP sequence number ie, packet number 4152 is discarded.
  • the UE determines the boundary of the uplink regular PDCP sequence number window according to the start identifier (ie, 56) of the uplink regular PDCP sequence number window. (ie 56-4151). After switching, the PDCP of the unacknowledged data packet (56, 58) in the normal PDCP sequence number window will be uplinked. PDCP converted to the PDCP SN length of the target base station After the SN is sent to the target base station through the wireless interface, and the PDCP SN of the remaining data packets (such as the 4152 data packet) in the uplink extended PDCP sequence number window is converted into the PDCP of the target base station.
  • the start identifier ie, 56
  • the PDCP of the unacknowledged data packet (56, 58) in the normal PDCP sequence number window will be uplinked.
  • PDCP converted to the PDCP SN length of the target base station After the SN is sent to the target base station through the wireless interface, and the PDCP SN
  • the PDCP SN of the SN length is sent to the target base station through the radio interface, and the new data packet received from the upper layer outside the extended window is allocated to the PDCP SN, and the PDCP is configured by using the allocated PDCP SN.
  • the PDU is sent to the target base station.
  • FIG. 9 is a flowchart showing an implementation process of a data processing method according to another embodiment of the present invention.
  • the method of the embodiment is further improved on the basis of FIG. 3, in which the source base station receives the measurement of the UE.
  • Reporting, and determining, according to the measurement report, that the UE needs to perform the base station handover the source base station selects the target base station, and after performing handover negotiation with the selected target base station, sends a reconfiguration request to the UE, after receiving the reconfiguration response of the UE.
  • the source base station sends a handover command to the UE, which is as follows:
  • the source base station sends a handover request to the target base station.
  • the source base station receives a handover response sent by the target base station.
  • the handover response has a target base station that does not support extended PDCP.
  • the information of the serial number window is not limited to PDCP.
  • the source base station sends a reconfiguration request to the UE to reconfigure the source base station and the UE, and receive a reconfiguration response returned by the UE.
  • the source base station learns that the target base station does not support extended PDCP according to the handover response returned by the target base station.
  • the source base station sends a reconfiguration request to the UE.
  • the reconfiguration request has a start identifier of an uplink regular PDCP sequence number window and a start identifier of a downlink normal PDCP sequence number window to reconfigure the source base station and the UE, and receive a reconfiguration response returned by the UE.
  • the specific process of reconfiguring the source base station is as follows: the source base station determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window in the reconfiguration request, and expands the downlink. The remaining data packets in the PDCP sequence number window are used as new data packets; the source base station determines the boundary of the uplink regular PDCP sequence number window and the uplink extended PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window in the reconfiguration request. The boundary of the uplink extended PDCP sequence number window is discarded.
  • the specific process of reconfiguring the UE is as follows: the UE determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window in the reconfiguration request, and discards the downlink extended PDCP sequence. The remaining data packets in the number window; The UE determines the boundary of the uplink regular PDCP sequence number window and the boundary of the uplink extended PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window in the reconfiguration request, and uses the remaining data packets in the uplink extended PDCP sequence number window as New packet.
  • FIG. 10 is a process flow of downlink data according to an embodiment of the present invention, where a buffer state of downlink data of a source base station side and a UE side PDCP buffer after reconfiguration and reconfiguration is shown.
  • the PDCP buffer on the source base station side buffers the data packets 56 to 4151 in the downlink normal PDCP sequence number window and the remaining data packets 4152 and 4153 in the downlink extended PDCP sequence number window and the new data received from the gateway.
  • the remaining data packets in the downlink extended PDCP sequence number window are regarded as new data packets.
  • the PDCP buffer in the UE side buffers the data packets 57 to 4151 in the uplink normal PDCP sequence number window and the remaining data packets 4152 in the uplink extended PDCP sequence number window.
  • the PDCP buffer on the UE side is reconfigured. Only the data packets 57 to 4151 in the uplink regular PDCP sequence number window are buffered, and the remaining data packets 4152 in the uplink extended PDCP sequence number window are discarded.
  • the source base station sends a handover command to the UE.
  • the source base station sends the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include data packets in the downlink normal PDCP sequence number window.
  • the source base station sends the data packet received by the source base station in the uplink regular PDCP sequence number window to the target base station.
  • the specific process is as described above, and will not be described here.
  • the source base station performs handover negotiation with the target base station, and then interacts with the UE. After the UE is reconfigured, the source base station sends a handover command to the UE, and the source base station After processing the uplink and downlink data with the UE, the UE switches from the source base station to the target base station.
  • the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, after the source base station selects the target base station, first sends a reconfiguration request to the UE, and receives the reconfiguration request. After the reconfiguration response of the UE, after the handover negotiation with the selected target base station, the source base station sends a handover command to the UE.
  • FIG. 11 is a flowchart showing an implementation process of a data processing method according to another embodiment of the present invention. The method is applicable to a source base station side, and is described in detail as follows:
  • the source base station sends the data packet in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the data packet in the downlink extended PDCP sequence number window may include a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window and a remaining data packet in the downlink normal PDCP sequence number window.
  • the data packet in the downlink extended PDCP sequence number window is all data packets in the window.
  • the remaining data packets in the downlink normal PDCP sequence number window do not include data packets that are not acknowledged by the UE in the downlink normal PDCP sequence number window.
  • the source base station when the source base station receives the measurement report of the UE, and determines, according to the measurement report, that the UE needs to perform the base station handover, the source base station determines the start identifier of the uplink regular PDCP sequence number window and the downlink normal PDCP sequence number window. Start tag.
  • the initial identifier of the uplink normal PDCP sequence number window refers to the identifier of the first data packet that is not received by the source base station in the uplink data.
  • the initial identifier of the downlink normal PDCP sequence number window is the identifier of the first data packet transmitted by the source base station to the UE and not confirmed by the UE in the downlink data. Where the identification of the data packet is the PDCP of the data packet SN.
  • the source base station determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window; the source base station determines the uplink regular PDCP sequence according to the start identifier of the uplink regular PDCP sequence number window. The boundary of the number window and the boundary of the uplink extended PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the method further comprises:
  • the source base station When the UE is handed over from the source base station to the target base station, the source base station sends a fully configured handover command to the UE.
  • the fully configured handover command has a start identifier of a downlink normal PDCP sequence number window and a start identifier of an uplink regular PDCP sequence number window.
  • the fully configured handover instruction refers to an instruction for instructing the UE to perform full configuration and to switch from the source base station to the target base station.
  • the full configuration command requires the UE to clear the parameters configured by the source base station, the buffer status, and the like.
  • the source base station sends all data packets in the downlink normal PDCP sequence number window to the target base station through the X2 interface.
  • the source base station converts the PDCP sequence number of all the data packets in the downlink normal PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station, and the downlink normal PDCP sequence number window is PDCP corresponding to all packets
  • the sequence number of the length of the PDCP sequence number used by the SDU and the target base station is transmitted to the target base station.
  • the source base station removes all the data packets in the downlink normal PDCP sequence number window from the PDCP allocated by the source base station.
  • the serial number and the PDCP SDU corresponding to all the data packets in the downlink normal PDCP sequence number window are sent to the target base station.
  • the source base station sends the remaining data packets in the downlink extended PDCP sequence number window as new data packets to the target base station through the X2 interface.
  • the specific process is as follows:
  • the source base station removes the PDCP sequence number allocated by the source base station from the remaining data packets in the downlink extended PDCP sequence number window, and extends the PDCP corresponding to the remaining data packets in the downlink extended PDCP sequence number window.
  • the SDU is sent to the target base station.
  • the method further comprises:
  • the source base station directly transmits the data packet newly received by the source base station outside the window of the downlink extended PDCP sequence number from the gateway to the target base station in sequence.
  • FIG. 12 is a flowchart showing an implementation of a data processing method according to another embodiment of the present invention. The method is applicable to the UE side corresponding to the method shown in FIG.
  • the UE After the user equipment UE is handed over to the target base station by the source base station, the UE sends the data packet in the uplink regular PDCP sequence number window and the remaining data packet in the uplink extended PDCP sequence number window to the target base station.
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window.
  • the data packet in the uplink extended DCP sequence number window may be all data packets in the window.
  • all data packets in the uplink regular PDCP sequence number window include data packets not confirmed by the source base station and remaining data packets in the regular PDCP sequence number window in the regular PDCP sequence number window.
  • the UE when the UE is handed over from the source base station to the target base station, the UE itself infers the start identifier of the uplink regular PDCP sequence number window and the start identifier of the downlink normal PDCP sequence number window, or the UE receives the full source from the source base station.
  • the configured handover instruction has a start identifier of an uplink regular PDCP sequence number window and a start identifier of a downlink normal PDCP sequence number window.
  • the UE determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink normal PDCP sequence number window; the UE determines the uplink regular PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window.
  • the boundary and the uplink extend the boundary of the PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the UE sends all the data packets in the uplink regular PDCP sequence number window and the remaining data packets in the uplink extended PDCP sequence number window to the target base station through the wireless interface.
  • the UE converts the PDCP sequence number of all data packets in the uplink regular PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station, according to the sequence of the PDCP sequence number length used by the target base station. No. reconstructs the PDCP corresponding to the data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window. The PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the UE converts the PDCP sequence number of the remaining data packet in the uplink extended PDCP sequence number window into a sequence number of the PDCP sequence number length used by the target base station, and reconstructs the uplink according to the serial number of the PDCP sequence number length used by the target base station. Extend the PDCP corresponding to the remaining packets in the PDCP sequence number window The PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the UE removes the PDCP sequence number allocated by the UE from all the data packets in the uplink normal PDCP sequence number window, and re-establishes the uplink normal PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the PDCP sequence number is assigned to the data packet acknowledged by the source base station, and the PDCP corresponding to the data packet not confirmed by the source base station in the uplink regular PDCP sequence number window is reconstructed by using the reassigned PDCP sequence number. a PDU and transmitting the reconstructed PDCP PDU to the target base station.
  • the UE removes the PDCP sequence number allocated by the UE from the remaining data packet in the uplink extended PDCP sequence number window, and re-assigns the PDCP to the remaining data packets in the uplink extended PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the serial number reconstructing the PDCP corresponding to the remaining data packets in the uplink extended PDCP sequence number window by using the reassigned PDCP sequence number a PDU and transmitting the reconstructed PDCP PDU to the target base station.
  • the method further includes:
  • the UE sends the data packet received from the upper layer outside the uplink extended PDCP sequence number window to the target base station through the wireless interface, and the specific process is as follows:
  • the UE allocates PDCP according to the PDCP SN used by the target base station for the data packet received from the upper layer outside the window of the uplink extended PDCP sequence number.
  • the SN constructs a PDCP PDU with the allocated PDCP SN, and sends the constructed PDCP PDU to the target base station in sequence.
  • the UE discards the data packet in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window, and after establishing a connection with the target base station, receives the data packet from the target base station, and the PDCP layer of the UE will receive the data packet. Submit in order to the upper layer.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include the data packets in the downlink normal PDCP sequence number window.
  • the target base station receives, from the source base station, the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window through the X2 interface, and the remaining data packet in the downlink normal PDCP sequence number window, and After extending the remaining data packets in the PDCP sequence number window, the PDCP is carried.
  • the data packet of the SN is constructed by using the PDCP SN carried by the data packet to construct a PDCP PDU to be sent to the UE; for the data packet not carrying the PDCP SN, after the PDCP SN is allocated, the PDCP is constructed.
  • the PDU is sent to the UE.
  • the target base station receives, from the UE, the data packet in the uplink regular PDCP sequence number window that is not confirmed by the source base station, and the remaining data packet in the uplink regular PDCP sequence number window, and the remaining data packet in the uplink extended PDCP sequence number window are sent to the UE.
  • the target base station, the PDCP layer of the target base station delivers the received data packets to the upper layer in order.
  • FIG. 13 is a flowchart of processing downlink data according to an embodiment of the present invention.
  • an extended PDCP used by a source base station is used.
  • the SN is 14 bits, and the PDCP SN used by the target base station is 13 bits as an example.
  • the downlink data delivered from the source base station to the UE includes a packet with a PDCP SN of 31 to 34, where PDCP
  • the data packets with SNs 32 and 34 have been confirmed by the UE, and the data packets with PDCP SNs of 31 and 33 are not confirmed by the UE.
  • the data processing procedure when the base station switches is as follows:
  • the source base station will be the data packet that has been confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink normal PDCP sequence number window (such as PDCP).
  • the data packets with SNs of 31 to 34 are all sent to the target base station, and the remaining data packets in the downlink extended PDCP sequence number window are sent to the target base station as new data packets.
  • the target base station After the target base station receives the data packet from the source base station through the X2 interface, it carries the PDCP.
  • the data packet of the SN is constructed by using the PDCP SN carried by the data packet to construct a PDCP PDU to be sent to the UE; for the data packet not carrying the PDCP SN, after the PDCP SN is allocated, the PDCP is constructed.
  • the PDU is sent to the UE.
  • the UE After receiving the fully configured handover command sent by the source base station, the UE discards all the data packets buffered in the PDCP of the UE. After establishing the underlying connection with the target base station, the UE receives the data packet from the target base station.
  • FIG. 14 is a structural block diagram of a base station according to an embodiment of the present invention. For convenience of description, only parts related to the embodiment of the present invention are shown.
  • the base station includes:
  • the transmitting unit 11 transmits the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include data packets in the downlink normal PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the start position of the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window are the same.
  • the sending unit 11 is further configured to send the data packet received by the base station in the uplink regular PDCP sequence number window to the target base station.
  • the base station further includes a discarding unit 12.
  • the discarding unit 12 discards the remaining data packets in the uplink extended PDCP sequence number window.
  • the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink regular PDCP sequence number window.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the base station further includes a conversion unit 13.
  • the converting unit 13 converts the PDCP sequence number of the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station.
  • the sending unit 11 is further configured to send, to the target base station, a PDCP service data unit SDU corresponding to the data packet not confirmed by the UE in the downlink normal PDCP sequence number window, and a sequence number of the PDCP sequence number length used by the acquired target base station.
  • the converting unit 13 is further configured to convert the PDCP sequence number of the remaining data packets in the downlink normal PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station.
  • the sending unit 11 is further configured to: PDCP corresponding to the remaining data packets in the downlink normal PDCP sequence number window. The sequence number of the length of the PDCP sequence number used by the SDU and the acquired target base station is transmitted to the target base station.
  • the remaining data packet in the downlink normal PDCP sequence number window does not include the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the base station further includes a stripping unit 14.
  • the stripping unit 14 removes the PDCP allocated by the source base station from the data packet not confirmed by the UE in the normal PDCP sequence number window. serial number.
  • the sending unit 11 is further configured to send the PDCP SDU corresponding to the data packet that is not confirmed by the UE in the normal PDCP sequence number window to the target base station.
  • the stripping unit 14 is further configured to remove the remaining data packets in the downlink normal PDCP sequence number window from the PDCP allocated by the source base station. serial number.
  • the sending unit 11 is further configured to send the PDCP SDU corresponding to the remaining data packets in the downlink normal PDCP sequence number window to the target base station.
  • the remaining data packet in the downlink normal PDCP sequence number window does not include the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the base station further includes a first window determining unit 15 and a second window determining unit 16. among them:
  • the first window determining unit 15 determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink regular PDCP sequence number window.
  • the “first” in the first window determining unit is merely a convenience for the description and the reference, and does not mean that there must be a corresponding number in the specific implementation manner of the present invention.
  • Two window determination unit. “First” does not represent the order.
  • the second window determining unit 16 determines the boundary of the uplink regular PDCP sequence number window and the boundary of the uplink extended PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window.
  • the initial identifier of the uplink normal PDCP sequence number window is the identifier of the first data packet that is not received by the source base station in the uplink data
  • the start identifier of the downlink normal PDCP sequence number window is the downlink data source source base station to the UE.
  • the initial identifier of the uplink normal PDCP sequence number window refers to the identifier of the first data packet that is not received by the source base station in the uplink data.
  • the initial identifier of the downlink normal PDCP sequence number window is the identifier of the first data packet transmitted by the source base station to the UE and not confirmed by the UE in the downlink data. Where the identification of the data packet is the PDCP of the data packet SN.
  • the sending unit 11 is further configured to send a handover command to the UE, where the handover command has a start identifier of an uplink regular PDCP sequence number window and a start identifier of a downlink normal PDCP sequence number window.
  • the sending unit is further configured to send a handover request to the target base station.
  • the base station also includes a receiving unit 17.
  • the receiving unit 17 receives a handover response sent by the target base station, where the handover response has a target base station that does not support extended PDCP. The information of the serial number window.
  • the foregoing embodiment shows a component structure of a base station according to an embodiment of the present invention.
  • the base station provided by the embodiment of the present invention may be used to implement the steps performed by the base station in the corresponding embodiment of FIG. 3 and FIG. 11, for example, the sending unit 11 may perform FIG. S101 in.
  • FIG. 15 is a structural block diagram of a user equipment according to an embodiment of the present invention. For convenience of description, only parts related to the embodiment of the present invention are shown.
  • the user equipment includes:
  • the transmitting unit 21 transmits the data packet that is not confirmed by the source base station in the uplink normal PDCP sequence number window and the remaining data packet in the uplink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink regular PDCP sequence number window.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the user equipment further includes a discarding unit 22.
  • the discarding unit 22 discards the remaining data packets in the downlink extended PDCP sequence number window, and the remaining data packets in the downlink extended PDCP sequence number window do not include the data packets in the downlink normal PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the user equipment further comprises a conversion unit 23 and a first construction unit 24.
  • the converting unit 23 converts the PDCP sequence number of the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station.
  • the first constructing unit 24 reconstructs the PDCP service data unit corresponding to the data packet that is not confirmed by the source base station in the uplink PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station.
  • PDU The sending unit 21 is further configured to send the reconstructed PDCP PDU to the target base station.
  • the converting unit 23 is further configured to use the PDCP of the remaining data packets in the uplink conventional PDCP sequence number window.
  • the serial number is converted to the serial number of the length of the PDCP sequence number used by the target base station.
  • the first constructing unit 24 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink regular PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station. PDU.
  • the sending unit 21 is further configured to send the reconstructed PDCP PDU to the target base station.
  • the remaining data packets in the uplink regular PDCP sequence number window do not include the data packets in the normal PDCP sequence number window that are not confirmed by the source base station.
  • the converting unit 23 is further configured to extend the PDCP of the remaining data packets in the uplink PDCP sequence number window.
  • the serial number is converted to the serial number of the length of the PDCP sequence number used by the target base station.
  • the first constructing unit 24 is further configured to reconstruct the remaining data packet corresponding to the PDCP in the uplink extended PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station. PDU.
  • the sending unit 21 is further configured to send the reconstructed PDCP PDU to the target base station.
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the regular PDCP sequence number window.
  • the user equipment further comprises a re-segment unit 25 and a second construction unit 26.
  • the re-sorting unit 25 removes the PDCP sequence number allocated by the UE from the data packet that is not confirmed by the source base station in the uplink normal PDCP sequence number window, and re-is not in the uplink conventional PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the packet acknowledged by the source base station allocates a PDCP sequence number.
  • the second constructing unit 26 is configured to reconstruct, according to the reassigned PDCP sequence number, the PDCP corresponding to the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window. PDU.
  • the sending unit 21 is further configured to send the reconstructed PDCP PDU to the target base station.
  • the re-segment unit 25 is further configured to remove the remaining data packet in the uplink regular PDCP sequence number window from the PDCP sequence number allocated by the UE, and re-establish the uplink PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the remaining packets are assigned the PDCP sequence number.
  • the second constructing unit 26 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink regular PDCP sequence number window according to the reassigned PDCP sequence number. PDU.
  • the sending unit 21 is further configured to send the reconstructed PDCP PDU to the target base station.
  • the remaining data packet in the uplink regular PDCP sequence number window does not include the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window.
  • the re-segment unit 25 is further configured to remove the remaining data packets in the uplink extended PDCP sequence number window and remove the PDCP allocated by the UE.
  • the serial number is re-assigned to the remaining data packets in the uplink extended PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the second constructing unit 26 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink extended PDCP sequence number window according to the reassigned PDCP sequence number.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window.
  • the user equipment further includes a first window determining unit 27 and a second window determining unit 28. among them:
  • the first window determining unit 27 determines the boundary of the downlink normal PDCP sequence number window and the boundary of the downlink extended PDCP sequence number window according to the start identifier of the downlink regular PDCP sequence number window.
  • the second window determining unit 28 determines the boundary of the uplink regular PDCP sequence number window and the boundary of the uplink extended PDCP sequence number window according to the start identifier of the uplink regular PDCP sequence number window.
  • the initial identifier of the uplink normal PDCP sequence number window is the identifier of the first data packet that is not received by the source base station in the uplink data
  • the start identifier of the downlink normal PDCP sequence number window is the downlink data source source base station to the UE.
  • the user equipment further comprises a receiving unit 29.
  • the receiving unit 29 receives a handover command or a reconfiguration request sent by the source base station, where the handover command or the reconfiguration request has a start identifier of the downlink regular PDCP sequence number window and a start identifier of the uplink regular PDCP sequence number window.
  • the foregoing embodiment shows the component structure of the user equipment provided by the embodiment of the present invention.
  • the user equipment provided by the embodiment of the present invention may be used to implement the steps performed by the user equipment in the corresponding embodiment of FIG. 3 and FIG. 11, for example, the sending unit 21 may S201 in Fig. 4 is executed.
  • FIG. 16 is a diagram showing the structure of a base station according to an embodiment of the present invention.
  • the base station provided by the embodiment of the present invention may be used to implement the method in the embodiment of FIG. 3 and FIG. 11.
  • the base station includes:
  • the transmitter 31 transmits the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and the remaining data packet in the downlink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the downlink extended PDCP sequence number window do not include data packets in the downlink normal PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the start position of the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window are the same.
  • the transmitter 31 is further configured to send the data packet received by the source base station in the uplink conventional PDCP sequence number window to the target base station.
  • the base station also includes a processor 32. The processor 32 discards the remaining data packets within the uplink extended PDCP sequence number window.
  • the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink regular PDCP sequence number window.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the processor 32 is further configured to convert a PDCP sequence number of a data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window into a sequence number of a PDCP sequence number length used by the target base station.
  • the transmitter 31 is further configured to send, to the target base station, a PDCP service data unit SDU corresponding to the data packet not confirmed by the UE in the downlink normal PDCP sequence number window and a sequence number of the PDCP sequence number length used by the target base station.
  • the processor 32 is further configured to convert the PDCP sequence number of the remaining data packets in the downlink normal PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station.
  • the transmitter 31 is further configured to PDCP corresponding to the remaining data packets in the downlink normal PDCP sequence number window. The sequence number of the length of the PDCP sequence number used by the SDU and the target base station is transmitted to the target base station.
  • the remaining data packet in the downlink normal PDCP sequence number window does not include the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the processor 32 is further configured to remove the PDCP allocated by the source base station from the data packet that is not confirmed by the UE in the normal PDCP sequence number window. serial number.
  • the transmitter 31 is further configured to send a PDCP SDU corresponding to a data packet that is not confirmed by the UE in the normal PDCP sequence number window to the target base station.
  • the processor 32 is further configured to remove the remaining data packets in the downlink normal PDCP sequence number window from the PDCP allocated by the source base station. serial number.
  • the transmitter 31 is further configured to send the PDCP SDU corresponding to the remaining data packets in the downlink normal PDCP sequence number window to the target base station.
  • the remaining data packet in the downlink normal PDCP sequence number window does not include the data packet that is not confirmed by the UE in the downlink normal PDCP sequence number window.
  • the processor 32 is further configured to determine a boundary of a downlink normal PDCP sequence number window and a boundary of a downlink extended PDCP sequence number window according to a start identifier of the downlink normal PDCP sequence number window, according to an uplink conventional PDCP sequence number window.
  • the start identifier determines the boundary of the uplink regular PDCP sequence number window and the boundary of the uplink extended PDCP sequence number window.
  • the initial identifier of the uplink normal PDCP sequence number window is the identifier of the first data packet that is not received by the source base station in the uplink data
  • the start identifier of the downlink normal PDCP sequence number window is the downlink data source source base station to the UE.
  • the initial identifier of the uplink normal PDCP sequence number window refers to the identifier of the first data packet that is not received by the source base station in the uplink data.
  • the initial identifier of the downlink normal PDCP sequence number window is the identifier of the first data packet transmitted by the source base station to the UE and not confirmed by the UE in the downlink data. Where the identification of the data packet is the PDCP of the data packet SN.
  • the transmitter 31 is further configured to send a handover command to the UE, where the handover command has a start identifier of the uplink regular PDCP sequence number window and a start identifier of the downlink regular PDCP sequence number window.
  • the base station further includes a receiver 33.
  • the receiver 33 is configured to receive a handover response sent by the target base station, where the handover response has a target base station that does not support extended PDCP.
  • the information of the serial number window is configured to receive a handover response sent by the target base station, where the handover response has a target base station that does not support extended PDCP. The information of the serial number window.
  • FIG. 16 do not constitute a limitation to a base station, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • FIG. 17 is a diagram showing the structure of a user equipment according to another embodiment of the present invention.
  • the user equipment provided by the embodiment of the present invention can be used to implement the method corresponding to the embodiment of FIG. 4 and FIG. 12.
  • the user equipment includes:
  • the transmitter 41 After the user equipment is handed over to the target base station by the source base station, the transmitter 41 transmits the data packet in the uplink normal PDCP sequence number window that is not confirmed by the source base station and the remaining data packet in the uplink extended PDCP sequence number window to the target base station.
  • the remaining data packets in the uplink extended PDCP sequence number window do not include data packets in the uplink regular PDCP sequence number window.
  • the uplink extended PDCP sequence number window includes an uplink regular PDCP sequence number window, and the uplink extended PDCP sequence number window and the uplink conventional PDCP sequence number window have the same starting position.
  • the user equipment further includes a processor 42.
  • the processor 42 discards the remaining data packets in the downlink extended PDCP sequence number window, and the remaining data packets in the downlink extended PDCP sequence number window do not include the data packets in the downlink normal PDCP sequence number window.
  • the downlink extended PDCP sequence number window includes a downlink normal PDCP sequence number window, and the downlink extended PDCP sequence number window and the downlink normal PDCP sequence number window have the same starting position.
  • the processor 42 is further configured to convert the PDCP sequence number of the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window into the sequence number of the PDCP sequence number length used by the target base station.
  • the transmitter 41 is further configured to reconstruct, according to the sequence number of the PDCP sequence number length used by the target base station, the PDCP service data unit corresponding to the data packet that is not confirmed by the source base station in the uplink PDCP sequence number window. The PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the processor 42 is further configured to PDCP of the remaining data packets in the uplink conventional PDCP sequence number window.
  • the serial number is converted to the serial number of the length of the PDCP sequence number used by the target base station.
  • the processor 42 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink regular PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the remaining data packets in the uplink regular PDCP sequence number window do not include the data packets in the normal PDCP sequence number window that are not confirmed by the source base station.
  • the processor 42 is further configured to extend the PDCP of the remaining data packets in the uplink PDCP sequence number window.
  • the serial number is converted to the serial number of the length of the PDCP sequence number used by the target base station.
  • the transmitter 41 is further configured to reconstruct the remaining data packet corresponding to the PDCP in the uplink extended PDCP sequence number window according to the sequence number of the PDCP sequence number length used by the target base station.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the regular PDCP sequence number window.
  • the processor 42 is further configured to: remove the PDCP sequence number allocated by the UE from the data packet that is not acknowledged by the source base station in the uplink normal PDCP sequence number window, and re-establish the uplink normal PDCP sequence according to the length of the PDCP sequence number used by the target base station.
  • the packet in the number window that is not acknowledged by the source base station is assigned a PDCP sequence number.
  • the transmitter 41 is further configured to reconstruct the PDCP corresponding to the data packet not confirmed by the source base station in the uplink regular PDCP sequence number window by using the reassigned PDCP sequence number.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the processor 42 is further configured to remove the remaining data packet in the uplink regular PDCP sequence number window from the PDCP sequence number allocated by the UE, and re-establish the uplink normal PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the remaining packets are assigned the PDCP sequence number.
  • the transmitter 41 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink conventional PDCP sequence number window by using the reassigned PDCP sequence number.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the remaining data packet in the uplink regular PDCP sequence number window does not include the data packet that is not confirmed by the source base station in the uplink regular PDCP sequence number window.
  • the processor 42 is further configured to remove the remaining data packets in the uplink extended PDCP sequence number window from the PDCP allocated by the UE.
  • the serial number is re-assigned to the remaining data packets in the uplink extended PDCP sequence number window according to the length of the PDCP sequence number used by the target base station.
  • the transmitter 41 is further configured to reconstruct the PDCP corresponding to the remaining data packets in the uplink extended PDCP sequence number window by using the reassigned PDCP sequence number.
  • the PDU and the reconstructed PDCP PDU is sent to the target base station.
  • the remaining data packet in the uplink extended PDCP sequence number window does not include the data packet in the uplink regular PDCP sequence number window.
  • the processor 42 is further configured to determine, according to a start identifier of the downlink normal PDCP sequence number window, a boundary of the downlink normal PDCP sequence number window and a boundary of the downlink extended PDCP sequence number window, according to the start of the uplink conventional PDCP sequence number window.
  • the identifier determines the boundary of the uplink regular PDCP sequence number window and the boundary of the uplink extended PDCP sequence number window.
  • the initial identifier of the uplink normal PDCP sequence number window is the identifier of the first data packet that is not received by the source base station in the uplink data
  • the start identifier of the downlink normal PDCP sequence number window is the downlink data source source base station to the UE.
  • the user equipment further includes a receiver 43.
  • the receiver 43 receives a handover command or a reconfiguration request sent by the source base station, where the handover command or the reconfiguration request has a start identifier of the downlink regular PDCP sequence number window and a start identifier of the uplink regular PDCP sequence number window.
  • FIG. 17 do not constitute a limitation to the user equipment, and may include more or less components than those illustrated, or a combination of certain components, or different component arrangements.
  • the sender when the UE needs to switch from the source base station using the extended PDCP SN to not using the extended PDCP
  • the sender sends the unacknowledged data packet in the standard window to the target base station, and sends the data packet outside the standard window to the target base station as a new data packet
  • the receiver sends the data packet outside the standard window.
  • Discard, or the sender sends all the data packets in the standard window to the target base station, and sends the data packets outside the standard window to the target base station as new packets.
  • the receiver discards the data packets inside and outside the standard window for the uplink. Data, the sender is the UE, and the receiver is the source base station.
  • the sender is the source base station and the receiver is the UE, so that the extended PDCP can be avoided in the UE from using.
  • the source base station After the source base station performs the handover negotiation with the target base station, the source base station sends a handover command carrying the start identifier of the uplink window and the start identifier of the downlink window to the UE, and then the source base station and the UE perform data processing and then perform the base station handover operation.
  • the handover delay problem existing when the UE performs handover between different versions of the base stations is avoided.

Landscapes

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

Abstract

La présente invention concerne un procédé de traitement de données, une station de base et un équipement d'utilisateur (UE). Ledit procédé de traitement de données est le suivant : lorsqu'un UE passe d'une station de base source à une station de base cible, ladite station de base source envoie à la station de base cible des paquets de données sans accusé de réception par ledit UE dans une fenêtre de nombre de séquences PDCP normal de liaison descendante et des paquets de données résiduelles dans une fenêtre de nombre de séquences PDCP étendu de liaison descendante, lesdits paquets de données dans la fenêtre de nombre de séquences PDCP normal de liaison descendante sont exclus desdits paquets de données résiduelles dans la fenêtre de nombre de séquences PDCP étendu de liaison descendante, ladite fenêtre de nombre de séquences PDCP normal de liaison descendante étant comprise dans la fenêtre de nombre de séquences PDCP étendu de liaison descendante, ladite fenêtre de nombre de séquences PDCP étendu de liaison descendante et ladite fenêtre de nombre de séquences PDCP normal de liaison descendante ayant la même position de départ. Ledit procédé de traitement de données évite le problème de paquets de données manquants lorsque l'UE passe d'une station de base source utilisant un nombre de séquences PDCP étendu à une station de base cible utilisant un nombre de séquences PDCP normal.
PCT/CN2012/079690 2012-08-03 2012-08-03 Procédé de traitement de données, station de base et équipement d'utilisateur WO2014019240A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201280001992.9A CN104509042B (zh) 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备
PCT/CN2012/079690 WO2014019240A1 (fr) 2012-08-03 2012-08-03 Procédé de traitement de données, station de base et équipement d'utilisateur

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/079690 WO2014019240A1 (fr) 2012-08-03 2012-08-03 Procédé de traitement de données, station de base et équipement d'utilisateur

Publications (1)

Publication Number Publication Date
WO2014019240A1 true WO2014019240A1 (fr) 2014-02-06

Family

ID=50027154

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/079690 WO2014019240A1 (fr) 2012-08-03 2012-08-03 Procédé de traitement de données, station de base et équipement d'utilisateur

Country Status (2)

Country Link
CN (1) CN104509042B (fr)
WO (1) WO2014019240A1 (fr)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018228342A1 (fr) * 2017-06-13 2018-12-20 华为技术有限公司 Procédé et appareil de gestion de transferts
WO2020088538A1 (fr) * 2018-11-02 2020-05-07 华为技术有限公司 Procédé et appareil de communication
WO2021035445A1 (fr) * 2019-08-23 2021-03-04 Oppo广东移动通信有限公司 Procédé et appareil permettant de transmettre des données pendant un transfert intercellulaire de cellule

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108512628A (zh) * 2017-02-24 2018-09-07 上海朗帛通信技术有限公司 一种被用于基站、ue中的用于高层传输的方法和装置
CN114390619B (zh) * 2020-10-21 2024-02-09 大唐移动通信设备有限公司 传输方法及设备
WO2022205333A1 (fr) * 2021-04-01 2022-10-06 Huawei Technologies Co., Ltd. Dispositifs et procédés pour améliorer une resélection de cellule pendant des sessions de communication en cours

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500289A (zh) * 2008-01-29 2009-08-05 华为技术有限公司 下行数据包转发方法、系统及演进基站
CN101932004A (zh) * 2009-06-25 2010-12-29 大唐移动通信设备有限公司 一种数据链路层的数据发送处理方法及设备
CN102076040A (zh) * 2011-01-19 2011-05-25 新邮通信设备有限公司 一种切换过程中的数据转发方法和系统
CN102265701A (zh) * 2008-12-24 2011-11-30 高通股份有限公司 用于对数据分组进行高效处理的优化报头

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101018109B (zh) * 2006-02-09 2010-06-23 中兴通讯股份有限公司 一种自动重传请求的移动性管理方法
CN100551157C (zh) * 2006-03-29 2009-10-14 中兴通讯股份有限公司 一种基站切换方法
CN101047967B (zh) * 2006-03-30 2010-12-01 华为技术有限公司 在切换过程中处理数据的方法及装置
CN101365239B (zh) * 2007-08-09 2012-12-12 华为技术有限公司 数据转发的方法、演进基站和长期演进网络
CN100583801C (zh) * 2007-11-30 2010-01-20 华为技术有限公司 一种动态建立组播虚拟局域网域的方法、系统及交换设备
CN102333099B (zh) * 2011-10-27 2014-09-10 杭州华三通信技术有限公司 一种安全控制方法和设备

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101500289A (zh) * 2008-01-29 2009-08-05 华为技术有限公司 下行数据包转发方法、系统及演进基站
CN102265701A (zh) * 2008-12-24 2011-11-30 高通股份有限公司 用于对数据分组进行高效处理的优化报头
CN101932004A (zh) * 2009-06-25 2010-12-29 大唐移动通信设备有限公司 一种数据链路层的数据发送处理方法及设备
CN102076040A (zh) * 2011-01-19 2011-05-25 新邮通信设备有限公司 一种切换过程中的数据转发方法和系统

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018228342A1 (fr) * 2017-06-13 2018-12-20 华为技术有限公司 Procédé et appareil de gestion de transferts
EP3614736A4 (fr) * 2017-06-13 2020-05-06 Huawei Technologies Co., Ltd. Procédé et appareil de gestion de transferts
WO2020088538A1 (fr) * 2018-11-02 2020-05-07 华为技术有限公司 Procédé et appareil de communication
WO2021035445A1 (fr) * 2019-08-23 2021-03-04 Oppo广东移动通信有限公司 Procédé et appareil permettant de transmettre des données pendant un transfert intercellulaire de cellule

Also Published As

Publication number Publication date
CN104509042A (zh) 2015-04-08
CN104509042B (zh) 2017-11-17

Similar Documents

Publication Publication Date Title
WO2018030819A1 (fr) Procédé et appareil permettant la prise en charge du déplacement d'un équipement d'utilisateur dans des communications sans fil
WO2020204501A1 (fr) Procédé de prise en charge d'accès à un réseau fermé, ue, station de base et support d'enregistrement lisible
WO2015096160A1 (fr) Procédé et dispositif pour maintenir la continuité du service
WO2013019035A2 (fr) Appareil et procédé de prise en charge d'un transfert intercellulaire
WO2020116899A1 (fr) Procédé et équipement de transfert
WO2015142104A1 (fr) Procédé et appareil pour émettre/recevoir un signal dans un système de communication mobile prenant en charge une pluralité de porteuses
WO2021006691A1 (fr) Procédé et dispositif de routage de paquet de données, et procédé et dispositif de commande de transmission de paquet de données
EP3420754A1 (fr) Procédé et équipement de noeud b évolué (enb) pour prendre en charge un transfert intercellulaire continu
WO2014019240A1 (fr) Procédé de traitement de données, station de base et équipement d'utilisateur
WO2013066129A1 (fr) Procédé et dispositif pour supporter le transfert de groupe
WO2012165794A2 (fr) Système et procédé destinés à un service de transmission de données simultanée dans un réseau hétérogène
WO2021066515A1 (fr) Nœud principal, nœud secondaire et équipement d'utilisateur dans un réseau de communication mobile et leurs procédés de communication entre eux
WO2020222578A1 (fr) Procédé de gestion de session et de mobilité au moyen de protocoles nas
WO2020091449A1 (fr) Procédé d'établissement de session, entité fonctionnelle de gestion de session, station de base, et support d'informations
WO2013073836A1 (fr) Procédé et dispositif de prise en charge de mobilité de groupe
WO2021015579A1 (fr) Procédé de prise en charge detransfert dans un réseau de communication mobile
WO2016159634A1 (fr) Procédé de reconfiguration d'un support sans fil et dispositif associé
WO2022231231A1 (fr) Procédé et dispositif de prise en charge d'un transfert
WO2017171506A1 (fr) Procédé et équipement de nœud b évolué (enb) pour prendre en charge un transfert intercellulaire continu
WO2022086233A1 (fr) Procédé et dispositif de transmission de multidiffusion
WO2015000117A1 (fr) Procédé et dispositif de simulation d'un test de numérotation d'un côté utilisateur et d'un côté réseau
WO2022086217A1 (fr) Nœuds, équipements utilisateur et procédés associés
WO2018143769A1 (fr) Procédé et dispositif de commande de transmission de données, procédé et appareil de commande de continuité d'ue
WO2024029932A1 (fr) Procédé et dispositif d'optimisation de transfert
WO2015106459A1 (fr) Procédé de transmission de données transférées de façon transparente, et entité de service commune

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

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

Country of ref document: EP

Kind code of ref document: A1