[go: up one dir, main page]

WO2014019240A1 - 一种数据处理方法、基站和用户设备 - Google Patents

一种数据处理方法、基站和用户设备 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
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/CN2012/079690
Other languages
English (en)
French (fr)
Inventor
黄曲芳
常俊任
张宏平
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
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 Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN201280001992.9A priority Critical patent/CN104509042B/zh
Priority to PCT/CN2012/079690 priority patent/WO2014019240A1/zh
Publication of WO2014019240A1 publication Critical patent/WO2014019240A1/zh
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00Arrangements for detecting or preventing errors in the information received
    • H04L1/12Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16Arrangements 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/18Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867Arrangements specially adapted for the transmitter end
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/0005Control or signalling for completing the hand-off
    • H04W36/0011Control 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

本发明提供一种数据处理方法、基站和用户设备,所述数据处理方法包括:当用户设备UE由源基站向目标基站切换时,所述源基站将下行常规PDCP序列号窗口内未被所述UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。该数据处理方法可以避免在UE从使用扩展的PDCPSN的源基站切换至使用常规的PDCPSN的目标基站时存在的数据包丢失的问题。

Description

一种数据处理方法、基站和用户设备 技术领域
本发明属于通信技术领域,尤其涉及一种数据处理方法、基站和用户设备。
背景技术
新一代的移动通信系统,如LTE(Long Term Evolution ,长期演进),可以提升数据传输速度,达到更好的用户体验。LTE一般由接入层和非接入层构成的,大部分情况下,接入层提供按序递交的功能。其中按序递交是指发送方的接入层从上层收到包,经过传输后,以相同的顺序将这些包传到接收方的高层,请参阅图1,为现有技术提供的接入层和上层的序递交的示意图。
接入层又细分为PDCP(Packet Data Convergence Protocol,分组数据汇聚协议)、RLC(Radio Link Control,无线链路控制层协议)、MAC(Medium Access Control,介质访问控制协议)、物理层等几个层次。通常情况下,按序递交功能是由RLC层提供的。发送方的RLC将每个包都加上编号,交给MAC层处理,如果MAC层和物理层在传输过程中发生了乱序,则接收方的RLC会将先收到的包存储起来,等到其它包到达后,再按顺序递交给PDCP层。请参阅图2,为现有技术提供的基站切换时的RLC层的按序递交的示意图。
发送方一共发出了5个包,接收方已经成功收到1、3、5号包,2、4号包尚未成功收到。接收方的接入层把1号包送交上层,3、5号包则存储在自己的缓存中,等着2、4号包的到来。如果先收到2号包,则接收方的接入层将按顺序向上层分别递交2、3号包,并继续等待4号包,4号包到来后,再按顺序向上层分别递交4、5号包;如果先收到4号包,收方的接入层将4号包存到缓存中,继续等待2号包,等到2号包到来后,按顺序向上层分别递交2、3、4、5号包。
正常情况下,RLC就可以保证按序递交了,但是在基站切换时,因为RLC要做重置,会导致RLC存储的数据包全部清空,所以RLC的按序递交功能就不再生效了,这时就需要用到PDCP 的按序递交功能。接收方的RLC先将自己收到的包先送交给PDCP,再将自己的缓存清空。切换后,接收方的PDCP继续接收包,再把这些包按序递交给上层。
由于无线通信中无线接口是一个传输瓶颈,为了减少切换前后空口的重传,提升空口效率,3GPP使用了数据前送(Data forwarding)的方式,即源基站将PDCP层存储的一些包通过X2接口传给目标基站,这样,目标基站就提前复原了源基站的状态,这些通过X2接口传过的包,就不需要在空口传输了。
现有的数据前送方法中,要求源基站和目标基站使用相同长度的PDCP序号(PDCP SN),同时,PDCP的窗口大小也是由PDCP序号长度决定的。现有系统中,PDCP的序号最长是12位,相应地,PDCP的窗口大小为2(12-1),即最多可以有2048个包存储在PDCP的缓存中,超出2048,则必然有两个包的PDCP SN相同,无法识别。
为了适应不同业务模型的需求, 3GPP已经同意从第11版开始延长PDCP SN,即基站可支持扩展的PDCP SN。如果用户设备(UE)从使用扩展的PDCP SN的基站切换至不支持扩展的PDCP SN的基站时,现有的数据前送方法存在数据包丢失的问题。
技术问题
本发明实施例提供一种数据处理方法,以解决用户设备在不同版本的基站间进行切换时存在的数据包丢失的问题。
技术解决方案
第一方面,所述数据处理方法包括:
当用户设备UE由源基站向目标基站切换时,所述源基站将下行常规分组数据汇聚协议PDCP序列号窗口内未被所述UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
在第一方面的第一种可能的实现方式中,还包括:
所述源基站将上行常规PDCP序列号窗口内所述源基站已接收的数据包发送至所述目标基站;和
所述源基站丢弃上行扩展PDCP序列号窗口内的剩余数据包,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
其中,所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
结合第一方面或者第一方面的第一种可能的实现方式,在第一方面的第二种可能的实现方式中,所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包发送至所述目标基站,具体包括:
所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述源基站向所述目标基站发送所述下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和所述目标基站使用的PDCP序列号长度的序列号。
结合第一方面的第二种可能的实现方式,在第三种可能的实现方式中,还包括:
所述源基站将所述下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号,并将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和所述目标基站使用的PDCP序列号长度的序列号发送至所述目标基站;
其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
结合第一方面或者第一方面的第一种可能的实现方式,在第四种可能的实现方式中,所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包发送至所述目标基站,具体包括:
所述源基站将所述常规PDCP序列号窗口内未被所述UE确认的数据包去掉所述源基站分配的PDCP 序列号,并将所述常规PDCP序列号窗口内未被所述UE确认的数据包对应的PDCP SDU发送至所述目标基站。
结合第一方面的第四种可能的实现方式,在第一方面的第五种可能的实现方式中,还包括:
所述源基站将所述下行常规PDCP序列号窗口内的剩余数据包去掉所述源基站分配的PDCP 序列号,并将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至所述目标基站;
其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
第二方面,所述数据处理方法包括
当用户设备UE由源基站切换至目标基站后,所述UE在切换后将上行常规分组数据汇聚协议PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
在第二方面的第一种可能的实现方式中,还包括:
所述UE丢弃下行扩展PDCP序列号窗口内的剩余数据包,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
结合第二方面或者第二方面的第一种可能的实现方式,在第二方面的第二种可能的实现方式中,所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包发送至所述目标基站,具体包括:
所述UE将所述上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述UE根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
结合第二方面的第二种可能的实现方式,在第二方面的第三种可能的实现方式中,还包括:
所述UE将所述上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号,根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的未被所述源基站确认的数据包。
结合第二方面的第二种可能的实现方式或者第二方面的第三种可能的实现方式,在第二方面的第四种可能的实现方式中,还包括:
所述UE将所述上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号,根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的数据包。
结合第二方面或者第二方面的第一种可能的实现方式,在第二方面的第五种可能的实现方式中,所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包发送至所述目标基站,具体包括:
所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包分配PDCP序列号,采用所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
结合第二方面的第五种可能的实现方式,在第二方面第六种可能的实现方式中,还包括:
所述UE将所述上行常规PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号,采用所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的未被所述源基站确认的数据包。
结合第二方面的第五种可能的实现方式或者第二方面的第六种可能的实现方式,在第二方面的第七种可能的实现方式中,还包括:
所述UE将所述上行扩展PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP 序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号,并采用所述重新分配的PDCP序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包。
第三方面,所述基站包括:
发送单元,用于在用户设备UE由所述基站向目标基站切换时,将下行常规分组数据汇聚协议PDCP序列号窗口内未被所述UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
在第三方面的第一种可能的实现方式中,所述发送单元还用于将所述上行常规PDCP序列号窗口内所述基站已接收的数据包发送至所述目标基站;
所述基站还包括:
丢弃单元,用于丢弃所述上行扩展PDCP序列号窗口内的剩余数据包,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
其中,所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
结合第三方面或者第三方面的第一种可能的实现方式,在第三方面第二种可能的实现方式中,所述基站还包括:
转换单元,用于将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述发送单元,还用于向所述目标基站发送所述下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和获取的所述目标基站使用的PDCP序列号长度的序列号。
结合第三方面的第二种可能的实现方式,在第三方面第三种可能的实现方式中,所述转换单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述发送单元,还用于将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和获取的所述目标基站使用的PDCP序列号长度的序列号发送至所述目标基站;
其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
结合第一方面或者第一方面的第一种可能的实现方式,在第三方面的第四种实现方式中,所述基站还包括:
剥离单元,用于将所述常规PDCP序列号窗口内未被所述UE确认的数据包去掉所述源基站分配的PDCP 序列号;
所述发送单元还用于将所述常规PDCP序列号窗口内未被所述UE确认的数据包对应的PDCP SDU发送至所述目标基站。
结合第三方面的第四种可能的实现方式,在第三方面第五种可能的实现方式中,所述剥离单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包去掉所述源基站分配的PDCP 序列号;
所述发送单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至所述目标基站;
其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
第四方面,所述用户设备包括:
发送单元,用于在所述用户设备由源基站切换至目标基站后,将上行常规PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
在第四方面的第一种可能的实现方式中,所述用户设备还包括:
丢弃单元,用于丢弃下行扩展PDCP序列号窗口内的剩余数据包,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
结合第四方面或者第四方面的第一种可能的实现方式,在第四方面的第二种可能的实现方式中,还包括:
转换单元,用于将所述上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
第一构造单元,用于根据获取的所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站。
结合第四方面的第二种可能的实现方式,在第四方面第三种可能的实现方式中,所述转换单元还用于将所述上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述第一构造单元,还用于根据获取的所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的未被所述源基站确认的数据包。
结合第四方面的第二种可能的实现方式或者第四方面的第三种可能的实现方式,在第四方面的第四种可能的实现方式中,
所述转换单元还用于将所述上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
所述第一构造单元,还用于根据获取的所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的数据包。
结合第四方面或者第四方面的第一种可能的实现方式,在第四方面的第五种可能的实现方式中,所述用户设备还包括:
重分单元,用于将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包分配PDCP序列号;
第二构造单元,用于根据获取的所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包对应的PDCP PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站。
结合第四方面的第五种可能的实现方式,在第四方面的第六种可能的实现方式中,所述重分单元,还用于将所述上行常规PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号;
所述第二构造单元,还用于根据获取的所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的未被所述源基站确认的数据包。
结合第四方面的第五种可能的实现方式或者第四方面的第六种可能的实现方式,在第四方面第七种可能的实现方式中,所述重分单元,还用于将所述上行扩展PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP 序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号;
所述第二构造单元,还用于根据获取的所述重新分配的PDCP序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包。
有益效果
从上述方案中可以看出,本发明实施例在UE从使用扩展的PDCP SN的源基站切换至使用常规的PDCP SN的目标基站时,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站发送至目标基站,UE将上行常规PDCP序列号窗口内未被源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至目标基站,从而避免在UE从使用扩展的PDCP SN的源基站切换至使用常规的PDCP SN的目标基站时存在的数据包丢失的问题。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例或现有技术描述中所需要使用的附图作简单地介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域普通技术人员来讲,在不付出创造性劳动性的前提下,还可以根据这些附图获得其他的附图。
图1是现有技术提供的接入层和上层的序递交的示意图;
图2是现有技术提供的基站切换时的RLC层的按序递交的示意图;
图3是本发明实施例提供的数据处理方法的实现流程图;
图4是本发明另一实施例提供的数据处理方法的实现流程图;
图5是本发明另一实施例提供的数据处理方法的实现流程图;
图6是本发明实施例提供的数据处理方法的交互实现流程图;
图7是本发明一实施例提供的下行数据的处理方法的示意图;
图8是本发明另一实施例提供的上行数据的处理方法的示意图;
图9是本发明另一实施例提供的数据前送方法的实现流程图;
图10是本发明另一实施例提供的下行数据的处理方法的示意图;
图11是本发明另一实施例提供的数据处理方法的实现流程图;
图12是本发明另一实施例数据处理方法的实现流程图;
图13是本发明另一实施例提供的下行数据的处理示意图;
图14是本发明实施例提供的基站的结构框图;
图15是本发明实施例提供的用户设备的结构框图;
图16是本发明实施例提供的基站的组成结构;
图17是本发明实施例提供的用户设备的组成结构。
本发明的实施方式
为了使本发明的目的、技术方案及优点更加清楚明白,以下结合附图及实施例,对本发明进行进一步详细说明。应当理解,此处所描述的具体实施例仅仅用以解释本发明,并不用于限定本发明。
为了说明本发明所述的技术方案,下面通过具体实施例来进行说明。下述的各实施例均适用于如下场景:UE从源基站切换至目标基站时,源基站使用扩展的PDCP SN,而目标基站使用常规的PDCP SN。为了便于说明,在后续的说明中,均以源基站的PDCP SN的长度为14位,目标基站的PDCP SN的长度为13位为例。
图3示出了本发明一实施例提供的数据处理的方法的实现流程,该方法的执行主体为源基站,详述如下:
S101,当用户设备UE由源基站向目标基站切换时,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。其中下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。
在本实施例中,当源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站确定上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。其中上行常规PDCP序列号窗口的起始标识是指上行数据中源基站未接收到的第一个数据包的标识。下行常规PDCP序列号窗口的起始标识为下行数据中源基站向UE传送且未被UE确认的第一个数据包的标识。其中数据包的标识为数据包的PDCP SN。
优选的是,当UE由源基站向目标基站切换时,源基站将上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识告知UE。源基站可以通过以下方式中的任意一种将上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识告知UE:源基站在发送至UE的切换命令中具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识,或者源基站通过MAC层信令或其它底层信令告知UE上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
优选的是,该方法还包括:
源基站根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;源基站根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
其中上行常规PDCP序列号窗口和下行常规PDCP序列号窗口是指依据常规PDCP SN的长度确定的窗口。上行扩展PDCP序列号窗口和下行扩展PDCP序列号窗口是指依据扩展的PDCP SN的长度确定的窗口。举例说明如下:
当常规PDCP SN的长度为13位,扩展的PDCP SN的长度为14位时,则上行常规PDCP序列号窗口和下行常规PDCP序列号窗口的大小均为2(13-1)=4096,而上行扩展PDCP序列号窗口和下行扩展PDCP序列号窗口的大小均为2(14-1)=8192。
优选的是,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包通过X2接口发送至目标基站。
优选的是,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包发送至目标基站的具体过程如下:
源基站将下行常规PDCP序列号窗口内未被UE确认的数据包携带PDCP SN通过X2接口发送至目标基站。其中下行常规PDCP序列号窗口内未被UE确认的数据包携带的PDCP SN为转换成目标基站的PDCP SN长度的PDCP SN。其具体过程如下:
源基站将下行常规PDCP序列号窗口内未被UE确认的数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号;
源基站向目标基站发送下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和目标基站使用的PDCP序列号长度的序列号。
在本实施例中,源基站采用在PDCP SDU外的上层协议头中(比如GTP头)携带目标基站使用的PDCP序列号长度的PDCP SN的方式将目标基站使用的PDCP序列号长度的PDCP SN发送至目标基站。这样,使得由源基站发送至目标基站的下行常规PDCP序列号窗口内未被UE确认的数据包均携带目标基站使用的PDCP序列号长度的PDCP SN。举例说明如下:
假设源基站的PDCP SN的长度为14位,目标基站的PDCP SN的长度为13位,则源基站先将下行常规PDCP序列号窗口内未被UE确认的数据包的14位的PDCP SN转换成13位的PDCP SN。其中具体的转换方式为:直接将14位的PDCP SN的高位去掉。源基站将下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP SDU和转换后的PDCP SN通过X2接口发送至目标基站,使得发送至目标基站的下行常规PDCP序列号窗口内未被UE确认的数据包携带转换后的PDCP SN。
优选的是,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包发送至目标基站,具体包括:
源基站将常规PDCP序列号窗口内未被UE确认的数据包去掉源基站分配的PDCP 序列号,并将常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP SDU发送至目标基站。
优选的是,该方法还包括:
源基站将下行常规PDCP序列号窗口内的剩余数据包去掉源基站分配的PDCP 序列号,并将下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至目标基站。
其中,下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的未被UE确认的数据包。
优选的是,源基站将下行扩展PDCP序列号窗口内的剩余数据包通过X2接口发送至目标基站,具体包括:
源基站将下行扩展PDCP序列号窗口内的剩余数据包作为新的数据包通过X2接口发送至目标基站。其具体过程如下:
源基站将下行扩展PDCP序列号窗口内的剩余数据包去掉源基站分配的PDCP SN,源基站将下行扩展PDCP序列号窗口内的剩余数据包对应的PDCP SDU按顺序发送至目标基站。在本领域中去掉PDCP SN也称为剥离PDCP SN。
优选的是,该方法还包括:
源基站将下行扩展PDCP序列号窗口外的从网关收到的数据包按顺序直接发送至目标基站。
优选的是,该方法还包括:
源基站将上行常规PDCP序列号窗口内源基站已接收的数据包发送至目标基站。
其中源基站将上行常规PDCP序列号窗口内源基站已接收的数据包通过X2接口发送至目标基站,其具体过程如下:
源基站将上行常规PDCP序列号窗口内源基站已接收的数据包携带PDCP SN通过X2接口发送至目标基站。其中上行常规PDCP序列号窗口内源基站已接收的数据包携带的PDCP SN为转换成目标基站使用的PDCP SN长度的PDCP SN。其具体过程如下:
源基站将上行常规PDCP序列号窗口内源基站已接收的数据包的PDCP SN转换成目标基站使用的PDCP序列号长度的PDCP SN;
源基站向目标基站发送上行常规PDCP序列号窗口内源基站已接收的数据包对应的PDCP SDU和目标基站使用的PDCP序列号长度的PDCP SN。在本实施例中,源基站采用在PDCP SDU外的上层协议头中(比如GTP头)携带目标基站使用的PDCP序列号长度的PDCP SN的方式将目标基站使用的PDCP序列号长度的PDCP SN发送至目标基站。这样,使得由源基站发送至目标基站的上行常规PDCP序列号窗口内源基站已接收的数据包均携带目标基站使用的PDCP序列号长度的PDCP SN。
优选的是,该方法包括:
源基站丢弃上行扩展PDCP序列号窗口内的剩余数据包,其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。
图4示出了本发明另一实施例提供的数据处理方法的实现流程,该方法适用于与图3所示的方法对应的UE侧,详述如下:
S201,当UE由源基站切换至目标基站后,UE将上行常规PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。
在本实施例中,当UE由源基站切换至目标基站时,UE自行推断出上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识,或者UE从源基站接收上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
UE根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;UE根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
在本发明一实施例中,UE将上行常规PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包通过无线接口发送至目标基站。
优选的是,UE将上行常规PDCP序列号窗口内未被所述源基站确认的数据包发送至目标基站的具体过程如下:
UE将上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP SN转换成目标基站使用的PDCP序列号长度的PDCP SN;
UE根据目标基站使用的PDCP序列号长度的PDCP SN重新构造上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU,并将重新构造的PDCP PDU发送至所述目标基站。优选的是,UE将上行扩展PDCP序列号窗口内的剩余数据包通过无线接口发送至目标基站, 作为新的数据包通过无线接口发送至所述目标基站,其具体过程如下:
UE将上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成目标基站使用的PDCP序列号长度的序列号;
根据目标基站使用的PDCP序列号长度的序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU,并将重新构造的PDCP PDU发送至所述目标基站。
在本发明另一实施例中,UE将上行常规PDCP序列号窗口内未被源基站确认的数据包发送至目标基站,具体包括:
UE将上行常规PDCP序列号窗口内未被源基站确认的数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内未被源基站确认的数据包分配PDCP序列号,采用重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内未被源基站确认的数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至所述目标基站。
优选的是,还包括:
UE将上行常规PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号,采用重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站;
其中,上行常规PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的未被源基站确认的数据包。
优选的是,还包括:
UE将上行扩展PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP 序列号,并根据目标基站使用的PDCP序列号长度重新为上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号,并采用重新分配的PDCP序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站;
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。优选的是,该方法还包括:
UE将上行扩展PDCP序列号窗口外的从上层接收到的数据包通过无线接口发送至目标基站,其具体过程如下:
UE根据目标基站使用的PDCP SN为上行扩展PDCP序列号窗口外的从上层接收到的数据包分配PDCP SN,并采用分配的PDCP SN构造PDCP PDU,将构造的PDCP PDU按顺序发送至目标基站。
优选的是,在UE由源基站切换至目标基站后,UE丢弃下行扩展PDCP序列号窗口内的剩余数据包,在与目标基站建立连接后,继续从目标基站接收数据包,UE的PDCP层将接收的数据包按序向上层递交。其中下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包。
在图3和图4所示的实施例中,目标基站通过X2接口从源基站接收下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包,以及下行扩展PDCP序列号窗口外的从网关收到的数据包后,对于携带有PDCP SN的数据包,则沿用该数据包携带的PDCP SN,构造PDCP业务数据单元(PDU)向UE发送;对于未携带PDCP SN的数据包,为其分配PDCP SN后,构造PDCP PDU向UE发送。
目标基站通过X2接口从源基站接收上行常规PDCP序列号窗口内源基站已接收的数据包,并在与UE建立底层连接后,继续通过无线接口从UE接收上行常规PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包,目标基站的PDCP层将接收的数据包按序向上层递交。
在图3和图4所示的实施例中,当UE从源基站切换至目标基站时,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包通过X2接口发送至目标基站,UE丢弃下行扩展PDCP序列号窗口内的剩余数据包,并继续从目标基站接收数据包,并将接收的数据包按序提交至上层,从而避免了UE从源基站切换至目标基站时下行数据的数据包丢失和数据包重复的问题;源基站将上行常规PDCP序列号窗口内源基站已接收的数据包通过X2接口发送至目标基站,同时UE将上行常规PDCP序列号窗口内未被源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包通过无线接口发送至目标基站,从而避免了UE从源基站切换至目标基站时上行数据的数据包丢失和数据包重复的问题。
图5示出了本发明第另一实施例提供的数据处理方法的实现流程,该实施例的方法是在图3或者图4的基础上做的进一步改进,详述如下:
S301,源基站向UE发送切换命令。该切换命令具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
优选的是,该方法还包括:
当UE由源基站向目标基站切换时,源基站向目标基站发送切换请求;
源基站接收目标基站发送的切换响应。该切换响应具有目标基站不支持扩展PDCP 序列号窗口的信息。
在本实施例中,当源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站选定目标基站,并向选定的目标基站发送切换请求,目标基站在接收到源基站发送的切换请求后,如果同意接收这个UE,就向源基站返回切换响应,以完成源基站与目标基站之间的切换协商。
S302,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。其中下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。其具体过程如上所述,在此不再赘述。
在本实施例中,当UE需要从源基站切换至目标基站时,源基站与目标基站完成切换协商后,源基站获知目标基站不支持扩展的PDCP SN后,即向UE发送切换命令,UE在接收到源基站的切换命令后,依据该切换命令中的下行窗口的起始标识和上行窗口的起始标识进行上、下行数据的处理后,即可切换至目标基站,从而不仅避免了UE在不同版本的基站间进行切换时存在的数据包丢失和数据包重复的问题,同时避免了UE在不同版本的基站间进行切换时存在的切换延时问题。
为了使图5所示的方法更为清楚,以下以交互图的形式对其进行详细说明。
请参阅图6,为本发明实施例提供的数据处理方法的交互实现流程。
1、UE向源基站发送测量报告。
2、源基站在接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站选定目标基站,并向选定的目标基站发送切换请求。
3、目标基站接收到源基站发送的切换请求后,如果同意接收这个UE,就向源基站返回切换响应,以完成源基站与目标基站之间的切换协商。
4、源基站依据目标基站返回的切换响应获知目标基站不支持扩展的PDCP SN。
5、源基站向UE发送切换命令。该切换命令具有下行窗口的起始标识和上行窗口的起始标识。
6、源基站和UE对上下行数据进行处理。其中源基站和UE对上下行数据进行处理的具体处理过程如图3、图4所示,在此不再赘述。
7、UE切换至目标基站,与目标基站建立底层连接后,继续数据传输,使得UE从源基站切换至目标基站。
为了便于说明,以下以一个具体的示例对本发明实施例提供的上述方法进行举例说明。
请参阅图7,为本发明实施例提供的下行数据的处理流程,在该示例中,以源基站使用的扩展PDCP SN是14比特,目标基站使用的PDCP SN是13比特为例。
在该示例中,假设从源基站下发至UE的下行数据中第一个未被UE确认的数据包的标识为56号数据包,即源基站确定的下行常规PDCP序列号窗口的起始标识为56,且假设在需要进行切换时,从源基站发送至UE的56至4153号数据包中57至4152号数据包均已得到UE的确认。则UE进行基站切换时的下行数据的处理过程如下:
当源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站选定目标基站,并向选定的目标基站发送切换请求,目标基站在接收到源基站发送的切换请求后,向源基站返回切换响应,以完成源基站与目标基站之间的切换协商。
源基站依据目标基站返回的切换响应获知目标基站不支持扩展的PDCP SN时,源基站向UE发送携带下行常规PDCP序列号窗口的起始标识(即56)的切换命令。同时源基站依据下行常规PDCP序列号窗口的起始标识(即56)确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界。由于下行常规PDCP序列号窗口的起始标识、下行扩展PDCP序列号窗口的起始标识的起始位置相同,而下行常规PDCP序列号窗口的长度为4096,下行扩展PDCP序列号窗口的长度为8192,从而可以确定下行常规PDCP序列号窗口的终止标识为(55+4096)=4151,下行扩展PDCP序列号窗口的终止标识为(55+8192)=8247。
源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。即下行常规PDCP序列号窗口的起始为56,终止为4151,而由于从源基站发送至UE的57至4152号数据包均已得到UE的确认,因此,下行常规PDCP序列号窗口内未被UE确认的数据包为PDCP SN为56的数据包。而下行扩展PDCP序列号窗口内的剩余数据包为PDCP SN为4152、4153的数据包,所以,源基站将下行常规PDCP序列号窗口内的PDCP SN为56的数据包的PDCP SN的高位去掉后,携带上该转换后的PDCP SN发送至目标基站。同时源基站将PDCP SN为4152、4153的数据包去掉PDCP SN后发送至目标站,同时将从网关新收到的数据包直接发送至目标基站。
在目标基站侧,目标基站通过X2接口从源基站接收数据包,对于携带PDCP SN的数据包,则沿用该PDCP SN,构造PDCP PDU向UE发送,对于未携带PDCP SN的数据包,目标基站为其分配PDCP SN后,构造PDCP PDU,并将构造的PDCP PDU通过无线接口发送至UE。
在UE侧,请参阅图7,在切换前,57至4151、4152号数据包为已经收到并确认的数据包,则在接收到源基站发送的切换命令后,依据该切换命令中携带的下行常规PDCP序列号窗口的起始标识(即56)确定下行常规PDCP序列号窗口的边界(即56-4151),丢弃下行常规PDCP序列号窗口外的数据包(如4152),并从源基站切换至目标基站,在与目标基站建立底层连接后,继续从目标基站接收数据包,UE的PDCP层按序将数据包递交至UE的上层。
请参阅图8,为本发明实施例提供的上行数据的处理流程,在该示例中,以源基站使用的扩展PDCP SN是14比特,目标基站使用的PDCP SN是13比特为例。
在该示例中,假设从UE发送至源基站的上行数据中源基站未接收到的第一个数据包的标识为56号数据包,所以源基站确定的上行常规PDCP序列号窗口的起始标识为56,且假设在需要进行切换时,从UE发送至源基站的57、59至4152号数据包均已得到源基站的确认。则切换过程中上行数据的处理流程如下:
源基站与目标基站进行切换协商后获知目标基站不支持扩展的PDCP SN时,源基站向UE发送携带上行常规PDCP序列号窗口的起始标识(即56)的切换命令。同时源基站依据上行常规PDCP序列号窗口的起始标识(即56)确定上行常规PDCP序列号窗口的终止标识(即4151)。
对于上行数据,源基站将上行常规PDCP序列号窗口内已成功收到的数据包的PDCP SN转换成目标基站的PDCP序列号长度的SN后,将PDCP SDU和转换后的PDCP SN通过X2接口发送至目标基站(即57、59至4151号数据包), 同时丢弃上行常规PDCP序列号窗口外的数据包(即4152号数据包)。
在UE侧,请参阅图8,在切换前,UE在接收到源基站发送的切换命令后,UE根据上行常规PDCP序列号窗口的起始标识(即56)确定上行常规PDCP序列号窗口的边界(即56-4151)。在切换后,将上行常规PDCP序列号窗口内未被确认的数据包(56、58)的PDCP SN转换成目标基站的PDCP SN长度的PDCP SN后通过无线接口发送至目标基站,并将上行扩展PDCP序列号窗口内的剩余数据包(如4152号数据包)的PDCP SN转换成目标基站的PDCP SN长度的PDCP SN后通过无线接口发送至目标基站,同时将扩展窗口外的从上层收到的新数据包分配PDCP SN,并采用分配的PDCP SN构造PDCP PDU后发送至目标基站。
图9示出了本发明另一实施例提供的数据处理方法的实现流程,该实施例的方法是在图3的基础上做的进一步改进,在该实施例中,源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站选定目标基站,并与选定的目标基站进行切换协商后,向UE发送重配置请求,在接收到UE的重配置响应后,源基站向UE发送切换命令,详述如下:
S401,当UE由源基站向目标基站切换时,源基站向目标基站发送切换请求。
S402,源基站接收目标基站发送的切换响应。该切换响应具有目标基站不支持扩展PDCP 序列号窗口的信息。
S403,源基站向UE发送重配置请求,以对源基站和UE进行重配置,并接收UE返回的重配置响应。
在本实施例中,源基站依据目标基站返回的切换响应获知目标基站不支持扩展的PDCP SN时,源基站向UE发送重配置请求。该重配置请求具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识,以对源基站和UE进行重配置,并接收UE返回的重配置响应。
其中重配置源基站的具体过程如下:源基站依据重配置请求中的下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界,将下行扩展PDCP序列号窗口内的剩余数据包均作为新的数据包;源基站依据重配置请求中的上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界,丢弃上行扩展PDCP序列号窗口内的剩余数据包。
其中重配置UE的具体过程如下:UE依据重配置请求中的下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界,丢弃下行扩展PDCP序列号窗口内的剩余数据包; UE依据重配置请求中的上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界,将上行扩展PDCP序列号窗口内剩余的数据包均作为新的数据包。
请参阅图10,为本发明实施例提供的下行数据的处理流程,其中示出了重配置前和重配置后源基站侧和UE侧PDCP缓冲区的下行数据的缓存状态。重配置前,源基站侧的PDCP缓冲区中缓存有下行常规PDCP序列号窗口内的数据包56至4151、下行扩展PDCP序列号窗口内剩余的数据包4152和4153以及从网关接收到的新数据包,重配置后,源基站侧的PDCP缓冲区中,将下行扩展PDCP序列号窗口内剩余的数据包均作为新的数据包。重配置前,UE侧的PDCP缓冲区中缓存有上行常规PDCP序列号窗口内的数据包57至4151以及上行扩展PDCP序列号窗口内剩余的数据包4152,重配置后,UE侧的PDCP缓冲区中仅缓存上行常规PDCP序列号窗口内的数据包57至4151,上行扩展PDCP序列号窗口内剩余的数据包4152被丢弃。
S404,源基站向UE发送切换命令。
S405,源基站将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。其中下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。其具体过程如上所述,在此不再赘述。
S406,源基站将上行常规PDCP序列号窗口内源基站已接收的数据包发送至目标基站。其具体过程如上所述,在此不再赘述。在本实施例中,当UE需要从源基站切换至目标基站时,源基站先与目标基站进行切换协商,再与UE交互,对UE进行重配置后,源基站向UE发送切换命令,源基站和UE对上下行数据进行处理后,UE从源基站切换至目标基站。
在本发明另一实施例中,源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站选定目标基站后,先向UE发送重配置请求,在接收到UE的重配置响应后,再与选定的目标基站进行切换协商后,源基站向UE发送切换命令。
图11示出了本发明另一实施例提供的数据处理方法的实现流程,该方法适用于源基站侧,详述如下:
S501,当用户设备UE由源基站向目标基站切换时,源基站将下行常规PDCP序列号窗口内的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中,下行扩展PDCP序列号窗口内的数据包可以包括下行常规PDCP序列号窗口内未被UE确认的数据包和下行常规PDCP序列号窗口内的剩余数据包。例如,上述下行扩展PDCP序列号窗口内的数据包为该窗口内的所有数据包。上述下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内未被UE确认的数据包。
在本实施例中,当源基站接收到UE的测量报告,并依据该测量报告确定UE需要进行基站切换时,源基站确定上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。其中上行常规PDCP序列号窗口的起始标识是指上行数据中源基站未接收到的第一个数据包的标识。下行常规PDCP序列号窗口的起始标识为下行数据中源基站向UE传送且未被UE确认的第一个数据包的标识。其中数据包的标识为数据包的PDCP SN。
源基站根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;源基站根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
优选的是,该方法还包括:
当UE由源基站向目标基站切换时,源基站向UE发送全配置的切换命令。该全配置的切换命令具有下行常规PDCP序列号窗口的起始标识和上行常规PDCP序列号窗口的起始标识。
其中全配置的切换指令是指用于指示UE进行全配置并从源基站切换至目标基站的指令。其中全配置指令要求UE将源基站配置的参数、缓存状态等均清空。
优选的是,源基站将下行常规PDCP序列号窗口内的所有数据包通过X2接口发送至目标基站。
在本发明一实施例中,源基站将下行常规PDCP序列号窗口内的所有数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号,并将下行常规PDCP序列号窗口内的所有数据包对应的PDCP SDU和目标基站使用的PDCP序列号长度的序列号发送至目标基站。
在本发明另一实施例中,源基站将下行常规PDCP序列号窗口内的所有数据包去掉源基站分配的PDCP 序列号,并将下行常规PDCP序列号窗口内的所有数据包对应的PDCP SDU发送至目标基站。
在本实施例中,源基站将下行扩展PDCP序列号窗口内的剩余数据包均作为新数据包通过X2接口发送至目标基站。其具体过程如下:
源基站将下行扩展PDCP序列号窗口内的剩余数据包去掉源基站分配的PDCP序列号,并将下行扩展PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至目标基站。
优选的是,该方法还包括:
源基站将下行扩展PDCP序列号窗口外的源基站从网关新收到的数据包按顺序直接发送至目标基站。
图12示出了本发明另一实施例提供的数据处理方法的实现流程,该方法适用于与图11所示的方法对应的UE侧,详述如下:
S601,当用户设备UE由源基站切换至目标基站后,UE将上行常规PDCP序列号窗口内的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。上述上行扩展DCP序列号窗口内的数据包可以为该窗口内的所有数据包。并且,该上行常规PDCP序列号窗口内的所有数据包包括常规PDCP序列号窗口内的未被源基站确认的数据包和常规PDCP序列号窗口内的剩余数据包。
在本实施例中,当UE由源基站切换至目标基站时,UE自行推断出上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识,或者UE从源基站接收全配置的切换指令,该全配置的切换指令具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
UE根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;UE根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
优选的是,UE将上行常规PDCP序列号窗口内的所有数据包,和上行扩展PDCP序列号窗口内的剩余数据包通过无线接口发送至目标基站。
在本发明一实施例中,UE将上行常规PDCP序列号窗口内的所有数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号,根据目标基站使用的PDCP序列号长度的序列号重新构造上行常规PDCP序列号窗口内未被源基站确认的数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至所述目标基站。
优选的是,UE将上行扩展PDCP序列号窗口内的剩余数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号,根据目标基站使用的PDCP序列号长度的序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至所述目标基站。
在本发明另一实施例中,UE将上行常规PDCP序列号窗口内的所有数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内未被源基站确认的数据包分配PDCP序列号,采用重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内未被源基站确认的数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
优选的是,UE将上行扩展PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号,采用重新分配的PDCP序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
在本发明另一实施例中,该方法还包括:
UE将上行扩展PDCP序列号窗口外的从上层接收到的数据包通过无线接口发送至目标基站,其具体过程如下:
UE根据目标基站使用的PDCP SN为上行扩展PDCP序列号窗口外的从上层接收到的数据包分配PDCP SN,并采用分配的PDCP SN构造PDCP PDU,将构造的PDCP PDU按顺序发送至目标基站。
在本发明另一实施例中, UE丢弃下行常规PDCP序列号窗口内的数据包,和下行扩展PDCP序列号窗口内的剩余数据包,在与目标基站建立连接后,从目标基站接收数据包,UE的PDCP层将接收的数据包按序向上层递交。其中下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包。
在图11和图12所示的实施例中,目标基站通过X2接口从源基站接收下行常规PDCP序列号窗口内未被UE确认的数据包,下行常规PDCP序列号窗口内的剩余数据包,和下行扩展PDCP序列号窗口内的剩余数据包后,对于携带有PDCP SN的数据包,则沿用该数据包携带的PDCP SN,构造PDCP PDU向UE发送;对于未携带PDCP SN的数据包,为其分配PDCP SN后,构造PDCP PDU向UE发送。
目标基站通过无线接口从UE接收上行常规PDCP序列号窗口内未被源基站确认的数据包,上行常规PDCP序列号窗口内的剩余数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,目标基站的PDCP层将接收的数据包按序向上层递交。
为了便于说明,以下以一个具体的示例对本发明实施例提供的上述方法进行举例说明。
请参阅图13,为本发明实施例提供的下行数据的处理流程,在该示例中,以源基站使用的扩展PDCP SN是14比特,目标基站使用的PDCP SN是13比特为例。
在该示例中,假设从源基站下发至UE的下行数据包括PDCP SN为31至34的数据包,其中PDCP SN为32、34的数据包已被UE确认,PDCP SN为31、33的数据包未被UE确认。则基站切换时的数据处理流程如下:
源基站将下行常规PDCP序列号窗口内已被UE确认的数据包和下行常规PDCP序列号窗口内的剩余数据包(如PDCP SN为31至34的数据包)均发送至目标基站,同时将下行扩展PDCP序列号窗口内的剩余数据包作为新的数据包发送至目标基站。
目标基站通过X2接口从源基站接收到数据包后,对于携带有PDCP SN的数据包,则沿用该数据包携带的PDCP SN,构造PDCP PDU向UE发送;对于未携带PDCP SN的数据包,为其分配PDCP SN后,构造PDCP PDU向UE发送。
UE在接收到源基站发送的全配置的切换命令后,将UE的PDCP内缓存的数据包全部丢弃。UE在与目标基站建立底层连接后,从目标基站接收数据包。
图14示出了本发明实施例提供的基站的结构框图,为了便于说明,仅示出了与本发明实施例相关的部分。该基站包括:
发送单元11在用户设备UE由基站向目标基站切换时,将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。
优选的是,该发送单元11还用于将上行常规PDCP序列号窗口内基站已接收的数据包发送至目标基站。此时,该基站还包括丢弃单元12。该丢弃单元12丢弃上行扩展PDCP序列号窗口内的剩余数据包。
其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
优选的是,该基站还包括转换单元13。该转换单元13将下行常规PDCP序列号窗口内未被UE确认的数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。此时,发送单元11还用于向目标基站发送下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和获取的目标基站使用的PDCP序列号长度的序列号。
优选的是,转换单元13还用于将下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。此时,发送单元11还用于将下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和获取的目标基站使用的PDCP序列号长度的序列号发送至目标基站。
其中,下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
优选的是,该基站还包括剥离单元14。该剥离单元14将常规PDCP序列号窗口内未被UE确认的数据包去掉源基站分配的PDCP 序列号。此时,发送单元11还用于将常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP SDU发送至目标基站。
优选的是,剥离单元14还用于将下行常规PDCP序列号窗口内的剩余数据包去掉源基站分配的PDCP 序列号。此时,发送单元11还用于将下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至目标基站。
其中,下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的未被UE确认的数据包。
优选的是,该基站还包括第一窗口确定单元15和第二窗口确定单元16。其中:
第一窗口确定单元15根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界。
需要说明的是,本文中,第一窗口确定单元中的“第一”在此仅为表述和指代的方便,并不意味着在本发明的具体实现方式中一定会有与之对应的第二窗口确定单元。“第一”也不代表顺序。
第二窗口确定单元16根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中,上行常规PDCP序列号窗口的起始标识为上行数据中源基站未接收到的第一个数据包的标识,下行常规PDCP序列号窗口的起始标识为下行数据中源基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
其中上行常规PDCP序列号窗口的起始标识是指上行数据中源基站未接收到的第一个数据包的标识。下行常规PDCP序列号窗口的起始标识为下行数据中源基站向UE传送且未被UE确认的第一个数据包的标识。其中数据包的标识为数据包的PDCP SN。
优选的是,该发送单元11还用于向UE发送切换命令,该切换命令具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
优选的是,该发送单元还用于向目标基站发送切换请求。该基站还包括接收单元17。该接收单元17接收目标基站发送的切换响应,该切换响应具有目标基站不支持扩展PDCP 序列号窗口的信息。
上述实施例示出了本发明实施例提供的基站的组成结构,本发明实施例提供的基站可以用于实施图3和图11对应实施例中基站执行的步骤,例如,发送单元11可以执行图3中的S101。
图15示出了本发明实施例提供的用户设备的结构框图,为了便于说明,仅示出了与本发明实施例相关的部分。该用户设备包括:
发送单元21在用户设备由源基站切换至目标基站后,将上行常规PDCP序列号窗口内未被源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
优选的是,该用户设备还包括丢弃单元22。该丢弃单元22丢弃下行扩展PDCP序列号窗口内的剩余数据包,该下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。
其中,下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
优选的是,该用户设备还包括转换单元23和第一构造单元24。该转换单元23将上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。第一构造单元24根据目标基站使用的PDCP序列号长度的序列号重新构造上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU。发送单元21还用于将重新构造的PDCP PDU发送至所述目标基站。
优选的是,转换单元23还用于将上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成目标基站使用的PDCP序列号长度的序列号。第一构造单元24还用于根据目标基站使用的PDCP序列号长度的序列号重新构造上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU。发送单元21还用于将重新构造的PDCP PDU发送至目标基站。
其中,上行常规PDCP序列号窗口内的剩余数据包不包括常规PDCP序列号窗口内的未被源基站确认的数据包。
优选的是,该转换单元23还用于将上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成目标基站使用的PDCP序列号长度的序列号。第一构造单元24还用于根据目标基站使用的PDCP序列号长度的序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU。发送单元21还用于将重新构造的PDCP PDU发送至所述目标基站。
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括常规PDCP序列号窗口内的数据包。
优选的是,用户设备还包括重分单元25和第二构造单元26。该重分单元25将上行常规PDCP序列号窗口内未被源基站确认的数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内未被源基站确认的数据包分配PDCP序列号。第二构造单元26用于根据重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内未被源基站确认的数据包对应的PDCP PDU。发送单元21还用于将重新构造的PDCP PDU发送至目标基站。
优选的是,重分单元25还用于将上行常规PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号。第二构造单元26还用于根据重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU。发送单元21还用于将重新构造的PDCP PDU发送至目标基站。
其中,上行常规PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的未被源基站确认的数据包。
优选的是,重分单元25还用于将上行扩展PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP 序列号,并根据目标基站使用的PDCP序列号长度重新为上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号。第二构造单元26还用于根据重新分配的PDCP序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站。
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。
优选的是,用户设备还包括第一窗口确定单元27和第二窗口确定单元28。其中:
第一窗口确定单元27根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界。
第二窗口确定单元28根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中,上行常规PDCP序列号窗口的起始标识为上行数据中源基站未接收到的第一个数据包的标识,下行常规PDCP序列号窗口的起始标识为下行数据中源基站向所述UE传送且未被UE确认的第一个数据包的标识。
优选的是,用户设备还包括接收单元29。该接收单元29接收源基站发送的切换命令或重配置请求,该切换命令或重配置请求具有下行常规PDCP序列号窗口的起始标识和上行常规PDCP序列号窗口的起始标识。
本领域普通技术人员可以理解为上述基站和用户设备所包括的各个单元和模块只是按照功能逻辑进行划分的,但并不局限于上述的划分,只要能够实现相应的功能即可;另外,各功能单元和模块的具体名称也只是为了便于相互区分,并不用于限制本发明的保护范围。
上述实施例示出了本发明实施例提供的用户设备的组成结构,本发明实施例提供的用户设备可以用于实施图3和图11对应实施例中用户设备执行的步骤,例如,发送单元21可以执行图4中的S201。
图16示出了本发明实施例提供的基站的组成结构,本发明实施例提供的基站可以用于实施图3和图11对应实施例的方法,为了便于说明,仅示出了与本发明实施例相关的部分,具体技术细节未揭示的,请参照图3和图11对应实施例。该基站包括:
发射器31在用户设备UE由基站向目标基站切换时,将下行常规PDCP序列号窗口内未被UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和下行常规PDCP序列号窗口的起始位置相同。
优选的是,该发射器31还用于将上行常规PDCP序列号窗口内源基站已接收的数据包发送至目标基站。该基站还包括处理器32。该处理器32丢弃上行扩展PDCP序列号窗口内的剩余数据包。
其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和上行常规PDCP序列号窗口的起始位置相同。
优选的是,该处理器32还用于将下行常规PDCP序列号窗口内未被UE确认的数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。发射器31还用于向目标基站发送下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和目标基站使用的PDCP序列号长度的序列号。
优选的是,该处理器32还用于将下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。发射器31还用于将下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和目标基站使用的PDCP序列号长度的序列号发送至目标基站。
其中,下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
优选的是,该处理器32还用于将常规PDCP序列号窗口内未被UE确认的数据包去掉源基站分配的PDCP 序列号。发射器31还用于将常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP SDU发送至目标基站。
优选的是,该处理器32还用于将下行常规PDCP序列号窗口内的剩余数据包去掉源基站分配的PDCP 序列号。发射器31还用于将下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至目标基站。
其中,下行常规PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的未被UE确认的数据包。
优选的是,该处理器32还用于根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界,根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中,上行常规PDCP序列号窗口的起始标识为上行数据中源基站未接收到的第一个数据包的标识,下行常规PDCP序列号窗口的起始标识为下行数据中源基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
其中上行常规PDCP序列号窗口的起始标识是指上行数据中源基站未接收到的第一个数据包的标识。下行常规PDCP序列号窗口的起始标识为下行数据中源基站向UE传送且未被UE确认的第一个数据包的标识。其中数据包的标识为数据包的PDCP SN。
优选的是,发射器31还用于向UE发送切换命令,该切换命令具有上行常规PDCP序列号窗口的起始标识和下行常规PDCP序列号窗口的起始标识。
优选的是,该基站还包括接收器33。该接收器33用于接收目标基站发送的切换响应,该切换响应具有目标基站不支持扩展PDCP 序列号窗口的信息。
本领域技术人员可以理解,图16中示出的组成结构并不构成对基站的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
图17示出了本发明另一实施例提供的用户设备的组成结构,本发明实施例提供的用户设备可以用于实施图4和图12对应实施例的方法,为了便于说明,仅示出了与本发明实施例相关的部分,具体技术细节未揭示的,请参照图4和图12对应实施例。该用户设备包括:
发射器41在用户设备由源基站切换至目标基站后,将上行常规PDCP序列号窗口内未被源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至目标基站。
其中上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。上行扩展PDCP序列号窗口包括上行常规PDCP序列号窗口,上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
优选的是,该用户设备还包括处理器42。该处理器42丢弃下行扩展PDCP序列号窗口内的剩余数据包,该下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包。
其中,下行扩展PDCP序列号窗口包括下行常规PDCP序列号窗口,下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
优选的是,该处理器42还用于将上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成目标基站使用的PDCP序列号长度的序列号。发射器41还用于根据目标基站使用的PDCP序列号长度的序列号重新构造上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU,并将重新构造的PDCP PDU发送至所述目标基站。
优选的是,处理器42还用于将上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成目标基站使用的PDCP序列号长度的序列号。处理器42还用于根据目标基站使用的PDCP序列号长度的序列号重新构造上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站。
其中,上行常规PDCP序列号窗口内的剩余数据包不包括常规PDCP序列号窗口内的未被源基站确认的数据包。
优选的是,该处理器42还用于将上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成目标基站使用的PDCP序列号长度的序列号。发射器41还用于根据目标基站使用的PDCP序列号长度的序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU,并将重新构造的PDCP PDU发送至所述目标基站。
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括常规PDCP序列号窗口内的数据包。
优选的是,处理器42还用于将上行常规PDCP序列号窗口内未被源基站确认的数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内未被源基站确认的数据包分配PDCP序列号。发射器41还用于采用重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内未被源基站确认的数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站。
优选的是,处理器42还用于将上行常规PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP序列号,并根据目标基站使用的PDCP序列号长度重新为上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号。发射器41还用于采用重新分配的PDCP序列号重新构造上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站。
其中,上行常规PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的未被源基站确认的数据包。
优选的是,处理器42还用于将上行扩展PDCP序列号窗口内的剩余数据包去掉UE分配的PDCP 序列号,并根据目标基站使用的PDCP序列号长度重新为上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号。发射器41还用于采用重新分配的PDCP序列号重新构造上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将重新构造的PDCP PDU发送至目标基站。
其中,上行扩展PDCP序列号窗口内的剩余数据包不包括上行常规PDCP序列号窗口内的数据包。
优选的是,处理器42还用于根据下行常规PDCP序列号窗口的起始标识确定下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界,根据上行常规PDCP序列号窗口的起始标识确定上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界。
其中,上行常规PDCP序列号窗口的起始标识为上行数据中源基站未接收到的第一个数据包的标识,下行常规PDCP序列号窗口的起始标识为下行数据中源基站向所述UE传送且未被UE确认的第一个数据包的标识。
优选的是,用户设备还包括接收器43。该接收器43接收源基站发送的切换命令或重配置请求,该切换命令或重配置请求具有下行常规PDCP序列号窗口的起始标识和上行常规PDCP序列号窗口的起始标识。
本领域技术人员可以理解,图17中示出的组成结构并不构成对用户设备的限定,可以包括比图示更多或更少的部件,或者组合某些部件,或者不同的部件布置。
在本发明实施例中,当UE需要从使用扩展的PDCP SN的源基站切换至不使用扩展的PDCP SN的目标基站时,发方将标准窗口内未确认的数据包发送至目标基站,并将标准窗口外的数据包均作为新数据包发送至目标基站,收方将标准窗口外的数据包均丢弃,或者发方将标准窗口内的所有数据包发送至目标基站,并将标准窗口外的数据包均作为新数据包发送至目标基站,收方将标准窗口内外的数据包均丢弃,对于上行数据,发方为UE,收方为源基站,对于下行数据,发方为源基站,收方为UE,这样即可避免在UE从使用扩展的PDCP SN的源基站切换至不使用扩展的目标基站时存在的数据包丢失的问题。同时在源基站与目标基站进行切换协商后,源基站向UE发送携带上行窗口的起始标识和下行窗口的起始标识的切换命令后,源基站和UE进行数据处理后再进行基站切换操作,从而避免了UE在不同版本的基站间进行切换时存在的切换延时问题。
本领域普通技术人员还可以理解,实现上述实施例方法中的全部或部分步骤是可以通过程序来指令相关的硬件来完成,所述的程序可以在存储于一计算机可读取存储介质中,所述的存储介质,包括ROM/RAM、磁盘、光盘等。
以上所述仅为本发明的较佳实施例而已,并不用以限制本发明,凡在本发明的精神和原则之内所作的任何修改、等同替换和改进等,均应包含在本发明的保护范围之内。

Claims (39)

  1. 一种数据处理方法,其特征在于,所述方法包括:
    当用户设备UE由源基站向目标基站切换时,所述源基站将下行常规分组数据汇聚协议PDCP序列号窗口内未被所述UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
    其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
  2. 如权利要求1所述的数据处理方法,其特征在于,还包括:
    所述源基站将上行常规PDCP序列号窗口内所述源基站已接收的数据包发送至所述目标基站;和
    所述源基站丢弃上行扩展PDCP序列号窗口内的剩余数据包,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
    其中,所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
  3. 如权利要求1至2所述的数据处理方法,其特征在于,所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包发送至所述目标基站,具体包括:
    所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述源基站向所述目标基站发送所述下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和所述目标基站使用的PDCP序列号长度的序列号。
  4. 如权利要求3所述的数据处理方法,其特征在于,还包括:
    所述源基站将所述下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号,并将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和所述目标基站使用的PDCP序列号长度的序列号发送至所述目标基站;
    其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
  5. 如权利要求1或2所述的数据处理方法,其特征在于,所述源基站将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包发送至所述目标基站,具体包括:
    所述源基站将所述常规PDCP序列号窗口内未被所述UE确认的数据包去掉所述源基站分配的PDCP 序列号,并将所述常规PDCP序列号窗口内未被所述UE确认的数据包对应的PDCP SDU发送至所述目标基站。
  6. 如权利要求5所述的数据处理方法,其特征在于,还包括:
    所述源基站将所述下行常规PDCP序列号窗口内的剩余数据包去掉所述源基站分配的PDCP 序列号,并将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至所述目标基站;
    其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
  7. 如权利要求1-6任一项所述的数据处理方法,其特征在于,还包括:
    所述常规PDCP序列号窗口的序列号为13比特,所述扩展PDCP序列号窗口的序列号为14比特。
  8. 如权利要求1-7任一项所述的数据处理方法,其特征在于,还包括:
    所述源基站根据所述下行常规PDCP序列号窗口的起始标识确定所述下行常规PDCP序列号窗口的边界和所述下行扩展PDCP序列号窗口的边界;和
    所述源基站根据所述上行常规PDCP序列号窗口的起始标识确定所述上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界;
    其中,所述上行常规PDCP序列号窗口的起始标识为上行数据中所述源基站未接收到的第一个数据包的标识,所述下行常规PDCP序列号窗口的起始标识为下行数据中所述源基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
  9. 如权利要求8所述的数据处理方法,其特征在于,还包括:
    所述源基站向所述UE发送切换命令,所述切换命令具有所述上行常规PDCP序列号窗口的起始标识和所述下行常规PDCP序列号窗口的起始标识。
  10. 如权利要求9所述的数据处理方法,其特征在于,还包括:
    所述源基站向所述目标基站发送切换请求;
    所述源基站接收所述目标基站发送的切换响应,所述切换响应具有所述目标基站不支持所述扩展PDCP 序列号窗口的信息。
  11. 一种数据处理方法,其特征在于,所述方法包括:
    当用户设备UE由源基站切换至目标基站后,所述UE将上行常规分组数据汇聚协议PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
    其中,所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
  12. 如权利要求11所述的数据处理方法,其特征在于,还包括:
    所述UE丢弃下行扩展PDCP序列号窗口内的剩余数据包,所述下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包;
    其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
  13. 如权利要求11或12所述的数据处理方法,其特征在于,所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包发送至所述目标基站,具体包括:
    所述UE将所述上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述UE根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
  14. 如权利要求13所述的数据处理方法,其特征在于,还包括:
    所述UE将所述上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号,根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的未被所述源基站确认的数据包。
  15. 如权利要求13或14所述的数据处理方法,其特征在于,还包括:
    所述UE将所述上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号,根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的数据包。
  16. 如权利要求11或12所述的数据处理方法,其特征在于,所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包发送至所述目标基站,具体包括:
    所述UE将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包分配PDCP序列号,采用所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站。
  17. 如权利要求16所述的数据处理方法,其特征在于,还包括:
    所述UE将所述上行常规PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号,采用所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的未被所述源基站确认的数据包。
  18. 如权利要求16或17所述的数据处理方法,其特征在于,还包括:
    所述UE将所述上行扩展PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP 序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号,并采用所述重新分配的PDCP序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU,并将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包。
  19. 如权利要求11至18任一项所述的数据处理方法,其特征在于,还包括:
    所述UE根据所述下行常规PDCP序列号窗口的起始标识确定所述下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;和
    所述UE根据所述上行常规PDCP序列号窗口的起始标识确定所述上行常规PDCP序列号窗口的边界和所述上行扩展PDCP序列号窗口的边界;
    其中,所述上行常规PDCP序列号窗口的起始标识为上行数据中所述源基站未接收到的第一个数据包的标识,所述下行常规PDCP序列号窗口的起始标识为下行数据中所述源基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
  20. 如权利要求19所述的数据处理方法,其特征在于,还包括:
    所述UE接收所述源基站发送的切换命令或重配置请求,所述切换命令或所述重配置请求具有所述下行常规PDCP序列号窗口的起始标识和所述上行常规PDCP序列号窗口的起始标识。
  21. 一种基站,其特征在于,所述基站包括:
    发送单元,用于在用户设备UE由所述基站向目标基站切换时,将下行常规分组数据汇聚协议PDCP序列号窗口内未被所述UE确认的数据包,和下行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述下行扩展PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的数据包;
    其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
  22. 如权利要求21所述的基站,其特征在于,
    所述发送单元还用于将上行常规PDCP序列号窗口内所述基站已接收的数据包发送至所述目标基站;
    所述基站还包括:
    丢弃单元,用于丢弃上行扩展PDCP序列号窗口内的剩余数据包,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
    其中,所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
  23. 如权利要求21至22所述的基站,其特征在于,所述基站还包括:
    转换单元,用于将所述下行常规PDCP序列号窗口内未被所述UE确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述发送单元,还用于向所述目标基站发送所述下行常规PDCP序列号窗口内未被UE确认的数据包对应的PDCP业务数据单元SDU和获取的所述目标基站使用的PDCP序列号长度的序列号。
  24. 如权利要求23所述的基站,其特征在于,
    所述转换单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述发送单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU和获取的所述目标基站使用的PDCP序列号长度的序列号发送至所述目标基站;
    其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
  25. 如权利要求21或22所述的基站,其特征在于,所述基站还包括:
    剥离单元,用于将所述常规PDCP序列号窗口内未被所述UE确认的数据包去掉所述源基站分配的PDCP 序列号;
    所述发送单元还用于将所述常规PDCP序列号窗口内未被所述UE确认的数据包对应的PDCP SDU发送至所述目标基站。
  26. 如权利要求25所述的基站,其特征在于,
    所述剥离单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包去掉所述源基站分配的PDCP 序列号;
    所述发送单元还用于将所述下行常规PDCP序列号窗口内的剩余数据包对应的PDCP SDU发送至所述目标基站;
    其中,所述下行常规PDCP序列号窗口内的剩余数据包不包括所述下行常规PDCP序列号窗口内的未被所述UE确认的数据包。
  27. 如权利要求21-26任一项所述的基站,其特征在于,所述基站还包括:
    第一窗口确定单元,用于根据所述下行常规PDCP序列号窗口的起始标识确定所述下行常规PDCP序列号窗口的边界和所述下行扩展PDCP序列号窗口的边界;和
    第二窗口确定单元,用于根据所述上行常规PDCP序列号窗口的起始标识确定所述上行常规PDCP序列号窗口的边界和上行扩展PDCP序列号窗口的边界;
    其中,所述上行常规PDCP序列号窗口的起始标识为上行数据中所述基站未接收到的第一个数据包的标识,所述下行常规PDCP序列号窗口的起始标识为下行数据中所述基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
  28. 如权利要求27所述的基站,其特征在于,所述发送单元,还用于向所述UE发送切换命令,所述切换命令具有所述上行常规PDCP序列号窗口的起始标识和所述下行常规PDCP序列号窗口的起始标识。
  29. 如权利要求28所述的基站,其特征在于,所述发送单元,还用于向所述目标基站发送切换请求;
    所述基站,还包括:
    接收单元,用于接收所述目标基站发送的切换响应,所述切换响应具有所述目标基站不支持所述扩展PDCP序列号窗口的信息。
  30. 一种用户设备,其特征在于,包括:
    发送单元,用于在所述用户设备由源基站切换至目标基站后,将上行常规分组数据汇聚协议PDCP序列号窗口内未被所述源基站确认的数据包,和上行扩展PDCP序列号窗口内的剩余数据包发送至所述目标基站,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包;
    所述上行扩展PDCP序列号窗口包括所述上行常规PDCP序列号窗口,所述上行扩展PDCP序列号窗口和所述上行常规PDCP序列号窗口的起始位置相同。
  31. 如权利要求30所述的用户设备,其特征在于,还包括:
    丢弃单元,用于丢弃下行扩展PDCP序列号窗口内的剩余数据包,所述下行扩展PDCP序列号窗口内的剩余数据包不包括下行常规PDCP序列号窗口内的数据包;
    其中,所述下行扩展PDCP序列号窗口包括所述下行常规PDCP序列号窗口,所述下行扩展PDCP序列号窗口和所述下行常规PDCP序列号窗口的起始位置相同。
  32. 如权利要求30或31所述的用户设备,其特征在于,还包括:
    转换单元,用于将所述上行常规PDCP序列号窗口内未被源基站确认的数据包的PDCP序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    第一构造单元,用于根据获取的所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行PDCP序列号窗口内未被源基站确认的数据包对应的PDCP业务数据单元 PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站。
  33. 如权利要求32所述的用户设备,其特征在于:
    所述转换单元,还用于将所述上行常规PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述第一构造单元,还用于根据获取的所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的未被所述源基站确认的数据包。
  34. 如权利要求32或33所述的用户设备,其特征在于:
    所述转换单元还用于将所述上行扩展PDCP序列号窗口内的剩余数据包的PDCP 序列号转换成所述目标基站使用的PDCP序列号长度的序列号;
    所述第一构造单元,还用于根据所述目标基站使用的PDCP序列号长度的序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应PDCP PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述常规PDCP序列号窗口内的数据包。
  35. 如权利要求30或31所述的用户设备,其特征在于,所述用户设备还包括:
    重分单元,用于将所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包分配PDCP序列号;
    第二构造单元,用于根据获取的所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内未被所述源基站确认的数据包对应的PDCP PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站。
  36. 如权利要求35所述的用户设备,其特征在于:
    所述重分单元,还用于将所述上行常规PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行常规PDCP序列号窗口内的剩余数据包分配PDCP序列号;
    所述第二构造单元,还用于根据获取的所述重新分配的PDCP序列号重新构造所述上行常规PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行常规PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的未被所述源基站确认的数据包。
  37. 如权利要求35或36所述的用户设备,其特征在于:
    所述重分单元,还用于将所述上行扩展PDCP序列号窗口内的剩余数据包去掉所述UE分配的PDCP 序列号,并根据所述目标基站使用的PDCP序列号长度重新为所述上行扩展PDCP序列号窗口内的剩余数据包分配PDCP序列号;
    所述第二构造单元,还用于根据获取的所述重新分配的PDCP序列号重新构造所述上行扩展PDCP序列号窗口内的剩余数据包对应的PDCP PDU;
    所述发送单元,还用于将所述重新构造的PDCP PDU发送至所述目标基站;
    其中,所述上行扩展PDCP序列号窗口内的剩余数据包不包括所述上行常规PDCP序列号窗口内的数据包。
  38. 如权利要求30至37任一项所述的用户设备,其特征在于,还包括:
    第一窗口确定单元,用于根据所述下行常规PDCP序列号窗口的起始标识确定所述下行常规PDCP序列号窗口的边界和下行扩展PDCP序列号窗口的边界;和
    第二窗口确定单元,用于根据所述上行常规PDCP序列号窗口的起始标识确定所述上行常规PDCP序列号窗口的边界和所述上行扩展PDCP序列号窗口的边界;
    其中,所述上行常规PDCP序列号窗口的起始标识为上行数据中所述源基站未接收到的第一个数据包的标识,所述下行常规PDCP序列号窗口的起始标识为下行数据中所述源基站向所述UE传送且未被所述UE确认的第一个数据包的标识。
  39. 如权利要求38所述的用户设备,其特征在于,还包括:
    接收单元,用于接收所述源基站发送的切换命令或重配置请求,所述切换命令或所述重配置请求具有所述下行常规PDCP序列号窗口的起始标识和所述上行常规PDCP序列号窗口的起始标识。
PCT/CN2012/079690 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备 Ceased WO2014019240A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201280001992.9A CN104509042B (zh) 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备
PCT/CN2012/079690 WO2014019240A1 (zh) 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2012/079690 WO2014019240A1 (zh) 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备

Publications (1)

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

Family

ID=50027154

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2012/079690 Ceased WO2014019240A1 (zh) 2012-08-03 2012-08-03 一种数据处理方法、基站和用户设备

Country Status (2)

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

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018228342A1 (zh) * 2017-06-13 2018-12-20 华为技术有限公司 切换控制方法及装置
WO2020088538A1 (zh) * 2018-11-02 2020-05-07 华为技术有限公司 一种通信方法及装置
WO2021035445A1 (zh) * 2019-08-23 2021-03-04 Oppo广东移动通信有限公司 小区切换时的数据传输方法及装置

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 大唐移动通信设备有限公司 传输方法及设备
CN117044297A (zh) * 2021-04-01 2023-11-10 华为技术有限公司 用于在进行中的通信会话期间增强小区重选的设备和方法

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 华为技术有限公司 在切换过程中处理数据的方法及装置
CN103024840B (zh) * 2007-08-09 2015-08-05 华为技术有限公司 数据转发的方法和演进基站
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 (zh) * 2017-06-13 2018-12-20 华为技术有限公司 切换控制方法及装置
EP3614736A4 (en) * 2017-06-13 2020-05-06 Huawei Technologies Co., Ltd. TRANSFER MANAGEMENT METHOD AND APPARATUS
WO2020088538A1 (zh) * 2018-11-02 2020-05-07 华为技术有限公司 一种通信方法及装置
WO2021035445A1 (zh) * 2019-08-23 2021-03-04 Oppo广东移动通信有限公司 小区切换时的数据传输方法及装置

Also Published As

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

Similar Documents

Publication Publication Date Title
WO2020204501A1 (en) Method for supporting access to closed network, ue, base station and readable storage medium
WO2021006691A1 (en) Method and device for routing data packet, and method and device for controlling data packet transmission
WO2018030819A1 (en) Method and apparatus for supporting movement of user equipment in wireless communications
WO2013019035A2 (en) Apparatus and method for supporting handover
WO2021066515A1 (en) Master node, secondary node and user equipment in mobile communication network and communication methods therebetween
WO2020116899A1 (en) Method and equipment for handover
WO2015096160A1 (zh) 一种保持业务连续性的方法及设备
WO2015142104A1 (en) Method and apparatus for transmitting/receiving signal in mobile communication system supporting a plurality of carriers
EP3420754A1 (en) Method and enb equipment for supporting seamless handover
WO2021015579A1 (en) Method for supporting handover in mobile communication network
WO2013066129A1 (en) Method and device for supporting group handover
WO2012165794A2 (ko) 이기종 네트워크 기반 데이터 동시 전송 서비스 시스템 및 그 방법
WO2020091449A1 (en) Session setup method, session management functional entity, base station, and storage medium
WO2013073836A1 (en) Method and device of supporting group mobility
WO2014019240A1 (zh) 一种数据处理方法、基站和用户设备
WO2022086233A1 (en) Method and device for multicast transmission
WO2020222578A1 (ko) Nas 프로토콜을 이용한 세션 및 이동성 관리 방안
WO2022231231A1 (en) Method and device for supporting handover
WO2024029932A1 (en) Method and device for handover optimization
WO2016159634A1 (ko) 무선 베어러 재구성 방법 및 그 장치
WO2018143769A1 (en) Method and device for controlling data transmission, method and apparatus for controlling continuity of ue
WO2017171506A1 (en) Method and enb equipment for supporting seamless handover
CN107211404A (zh) 一种数据传输方法及装置
WO2022211496A1 (en) Method and apparatus for using nas message for data protection
WO2015000117A1 (zh) 一种模拟拨测用户侧和网络侧的方法及设备

Legal Events

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

Ref document number: 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