WO2009018784A1 - Procédé de réacheminement de données, nœud b évolué et réseau d'évolution à long terme - Google Patents

Procédé de réacheminement de données, nœud b évolué et réseau d'évolution à long terme Download PDF

Info

Publication number
WO2009018784A1
WO2009018784A1 PCT/CN2008/071928 CN2008071928W WO2009018784A1 WO 2009018784 A1 WO2009018784 A1 WO 2009018784A1 CN 2008071928 W CN2008071928 W CN 2008071928W WO 2009018784 A1 WO2009018784 A1 WO 2009018784A1
Authority
WO
WIPO (PCT)
Prior art keywords
data packet
user data
enb
sent
sgw
Prior art date
Application number
PCT/CN2008/071928
Other languages
English (en)
French (fr)
Inventor
Yong Qiu
Min Huang
Ying Huang
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 PL08783921T priority Critical patent/PL2187664T3/pl
Priority to ES08783921.3T priority patent/ES2496616T3/es
Priority to EP08783921.3A priority patent/EP2187664B1/en
Publication of WO2009018784A1 publication Critical patent/WO2009018784A1/zh
Priority to HRP20140817AT priority patent/HRP20140817T1/hr

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/02Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W36/00Hand-off or reselection arrangements
    • H04W36/08Reselecting an access point
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W88/00Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08Access point devices

Definitions

  • the present invention relates to the field of mobile communications, and in particular, to a method for data forwarding in a handover process, and an evolved base station and a long term evolution network. Background technique
  • a core network device and an evolved base station are included.
  • the core network equipment includes a Mobility Management Entity (MME) and a Serving Gateway (SGW).
  • MME belongs to the control plane. It is responsible for the mobility management of the control plane, including user context and mobility state management, and assigning user temporary identity identifiers.
  • SGW belongs to the user plane part. When it is in the idle state, it initiates paging for downlink data, and manages to save IP bearers. Parameters and intra-network routing information, etc.; MME and SGW are connected in a mesh, and one MME can control several SGWs.
  • the core network device communicates with the eNB using the S1 interface, and the eNB uses the X2 interface for communication.
  • the handover of the core network between the eNBs refers to the process in which the user equipment (User Equipment, UE) disconnects the source eNB and accesses the target eNB.
  • the source eNB interacts with the UE, and the source eNB receives the measurement report.
  • the handover process includes the following three phases: a handover preparation phase, the source eNB interacts with the target eNB, and after receiving the handover request response, the source eNB sends a handover command to the UE.
  • the UE interacts with the target eNB, and the target eNB receives the UE.
  • the target eNB interacts with the core network device, and after receiving the handover complete response, the target eNB sends the release resource information to the source eNB, and the source eNB releases the resource.
  • the X2 handover process includes:
  • Step 1 The source eNB sends measurement control information (Measure Control) to the UE.
  • Measure Control Measure Control
  • Step 2 The UE sends measurement report information (Measure Reports) to the source eNB.
  • Step 3 The source eNB performs a handover decision (HO decision);
  • Step 4 The source eNB sends handover request information (Handover Request) to the target eNB.
  • Step 5 The target eNB performs admission control (Admission Control);
  • Step 6 The target eNB sends a handover request response message (Handover Request Ack) to the source eNB.
  • Handover Request Ack a handover request response message
  • Step 7 The source eNB sends handover command information (Handover Command) to the UE.
  • Step 8 the UE sends synchronization information (Synchronisation) to the target eNB;
  • Step 9 The target eNB sends an uplink information (UL allocation + TA for UE) to the UE.
  • Step 10 The UE sends a handover acknowledgement message (Handover Confirm) to the target eNB.
  • Step 11 The target eNB sends handover completion information (Handover Complete) to the SGW.
  • Step 12 The SGW performs path handover, and sends handover completion response information (Handover Complete Ack) to the target eNB.
  • Step 13 The target eNB sends Release Resource information to the source eNB.
  • Step 14 The source eNB performs Release Resources.
  • the SGW Before the handover completion phase, the SGW sends a user data packet to the source eNB; after the handover completion phase, after the SGW performs the path handover, the SGW sends the user data packet to the target eNB.
  • the source eNB Before the handover execution phase, the source eNB directly sends the user data packet delivered by the SGW to the UE.
  • the source eNB In the handover execution phase, the source eNB has disconnected from the UE, and the source eNB cannot directly send the user data packet sent by the SGW to the UE.
  • the source eNB forwards the user data packet sent by the SGW to the target eNB by using the X2 interface, and the target eNB receives the data packet.
  • the X2 port data packet forwarded by the source eNB (the user data packet forwarded by the X2 interface between the eNBs is simply referred to as the X2 port data packet) is sent to the UE.
  • the target eNB receives the S1 port data packet (the user data packet sent by the SGW to the eNB is simply referred to as the S1 port data packet), so as to ensure the number of users received by the UE.
  • the S1 port data packet is sent.
  • the target eNB After the target eNB receives the handover confirmation information sent by the UE, the target eNB starts the timer; sends the X2 port data packet before the timer expires; and sends the S1 port data packet after the timer expires. .
  • the end marker is added to the last user data packet sent to the source eNB, and the user data packet carrying the last tag is sent to the source eNB; the source eNB forwards the bearer end to the target eNB.
  • the target eNB After the target eNB receives the user data packet carrying the last tag, it learns that the user data packet of the source eNB has been sent, sends the user data packet carrying the last tag to the UE, and sends the S1 port data packet. .
  • the embodiments of the present invention provide a method for forwarding data in a handover process, an evolved base station, and a long-term evolution network, so as to improve the efficiency of the target eNB in forwarding user data packets during the X2 handover process.
  • An embodiment of the present invention provides a data forwarding method, in which a handover end phase of a core network is not involved in an evolved base station eNB, the method includes: after the user plane processes the gateway SGW to perform path switching, the target evolved base station eNB receives the SGW and sends the data to the SGW. The user data packet is received by the target eNB, and the user data packet sent by the SGW is sent to the user equipment.
  • the embodiment of the present invention further provides a long term evolution network, including: a user equipment, a source evolved base station eNB, a target eNB, and a user plane processing gateway SGW,
  • a long term evolution network including: a user equipment, a source evolved base station eNB, a target eNB, and a user plane processing gateway SGW,
  • the target eNB is configured to: after receiving the path switching by the SGW, receive the user data packet sent by the SGW, and after receiving the special data packet including the end tag sent by the source eNB, send the SGW to the user equipment.
  • An embodiment of the present invention further provides an evolved base station eNB, including:
  • a data packet receiving unit configured to receive a user data packet sent by the user plane processing gateway SGW;
  • a special data packet determining unit configured to determine whether a special data packet including an end tag is received;
  • the packet sending unit is configured to: when the special packet determining unit determines that the special data packet including the end tag is received, send the user data packet sent by the SGW received by the data packet receiving unit to the user equipment.
  • the embodiment of the present invention further provides a data forwarding method, in which the handover end phase of the core network is not involved in the evolved base station eNB, including: the user plane processing gateway SGW performs path switching; the target evolved base station eNB receives the user data delivered by the SGW. If the source eNB determines that there is a user data packet that needs to be sent to the target eNB in the transmit data buffer, the source eNB adds a last tag to the last user data packet sent to the target eNB, and the target eNB receives the packet.
  • the user data packet sent by the SGW is sent to the user equipment after the user data packet carrying the last tag is sent to the user equipment; or if the source eNB determines to send the data buffer. If there is no user data packet to be sent to the target eNB, the source eNB constructs a special data packet including an end tag, and transmits the special data packet including the end tag to the target eNB, and the target eNB receives the foregoing end tag. Special data packet, sent to the above user equipment SGW issued said user data packets.
  • the embodiment of the present invention further provides a data forwarding method, where the handover end phase of the core network is not involved in the evolved base station eNB, the method includes: the target eNB acquires a packet domain tunneling protocol user plane GTP of the next user data packet to be sent by the source eNB. - the U sequence number and the GTP_U sequence number of the first user data packet sent by the user plane processing gateway SGW; the GTP_U sequence number of the user data packet to be sent next by the source eNB and the first one sent by the SGW The GTP_U sequence number of the user data packet is determined to be that the user data packet sent by the source eNB to the target eNB has been sent; and the user data packet delivered by the SGW is sent to the user equipment.
  • the embodiment of the invention further provides a long term evolution network, including: a user equipment, a user plane processing gateway SGW, a target evolved base station eNB, and a source eNB,
  • the target eNB the user acquires a packet domain tunneling protocol user plane GTP_U sequence number of the next user data packet to be sent by the source eNB, and a GTP_U sequence number of the first user data packet sent by the SGW, according to the foregoing Determining, by the source eNB, the GTP_U sequence number of the user data packet to be sent and the GTP_U sequence number of the first user data packet sent by the SGW, determining that the user data packet sent by the source eNB to the target eNB has been sent. Sending the user data packet delivered by the SGW to the user equipment.
  • An embodiment of the present invention further provides an evolved base station eNB, including:
  • the next sequence number obtaining unit is configured to obtain a packet domain tunneling protocol user plane GTP_U sequence number of the next source eNB ready to send the user data packet;
  • the first sequence number obtaining unit is configured to obtain a GTP_U sequence number of the first user data packet sent by the user plane processing gateway SGW;
  • the sending end determining unit determines whether the source eNB ends transmitting the user data packet according to the GTP_U sequence number of the next source eNB ready to send the user data packet and the GTP_U sequence number of the first user data packet sent by the SGW. ;
  • a data packet sending unit configured to: when the sending end determining unit determines that the source eNB ends transmitting the user data packet, send the user data packet sent by the user plane processing gateway to the user equipment.
  • the embodiment of the invention further provides a method for obtaining a serial number, including:
  • the mobility management entity MME obtains, from the source SGW, the packet domain tunneling protocol user plane GTP_U sequence number of the next user SGW to be sent.
  • the MME sends the GTP_U sequence number to the target SGW, and the target SGW uses the GTP_U sequence number as the GTP_U sequence number of the first user data packet of the target SGW; or
  • the MME sends the GTP_U sequence number of the user data packet to be sent by the source SGW to the evolved base station eNB, so that the GTP_U sequence number between the source SGW and the target SGW has a corresponding relationship.
  • the embodiment of the present invention further provides a mobility management entity MME, including: a request information sending unit, configured to send, to the source SGW, request information for acquiring a GTP_U serial number of the next user data packet to be sent in the user plane processing gateway SGW relocation stage;
  • a sequence number receiving unit configured to receive a GTP_U sequence number of the next data packet to be sent sent by the source SGW;
  • a sequence number sending unit configured to send, to the target SGW, a GTP_U sequence number of the next source SGW that is to be sent by the sequence number receiving unit, or to send the next source SGW to the evolved base station eNB.
  • the GTP-U sequence number of the user data packet has a correspondence between the GTP_U sequence number between the source SGW and the target SGW.
  • the embodiment of the present invention further provides a long term evolution network, including: a mobility management entity MME, a target user plane processing gateway SGW, and a source SGW,
  • the MME is configured to acquire, from the source SGW, a packet domain tunneling protocol user plane GTP_U sequence number of the next user data packet to be sent by the source SGW, and send the GTP_U sequence number to the target SGW;
  • the target SGW is configured to receive the GTP_U sequence number, and use the GTP_U sequence number as the GTP_U sequence number of the first user data packet of the target SGW.
  • the embodiment of the invention further provides a data forwarding method, including:
  • the user plane processing gateway SGW receives the request information that the source eNB sends the user data packet to the source eNB after receiving the handover request response information;
  • the SGW stops sending the user data packet to the source eNB
  • the SGW After the path is switched, the SGW sends a user data packet to the target eNB.
  • the target eNB receives the handover completion response information sent by the SGW, and sends the user data packet sent by the SGW to the user equipment.
  • the embodiment of the invention further provides a data forwarding method, including:
  • the source evolved base station eNB After the source evolved base station eNB sends a handover command to the user equipment, the source evolved base station eNB sends a control plane message and a user data packet to the target eNB.
  • the control plane message carries the first GTP_U sequence number and the packet data convergence layer protocol PDCP sequence number that the target eNB should be numbered, and the user data packet sent by the source eNB to the target eNB includes: processed by the PDCP layer.
  • the target eNB When the target eNB is smaller than the first GTP_U sequence number that the target eNB should number, and the GTP_U sequence number of the first user data packet sent by the SGW to the target eNB, the target eNB continues to the user.
  • the device sends the user data packet sent by the source eNB to the target eNB;
  • the target eNB When the target eNB sends a GTP_U sequence number of the first user data packet sent by the SGW to the target eNB according to the first GTP_U sequence number that the target eNB should number, the target eNB sends the GTP_U sequence number of the first user data packet to the target eNB.
  • the target eNB does not need to wait for the timer to time out before sending the S1 port data packet, thereby improving the forwarding of the user data packet in the handover process without involving the core network. effectiveness.
  • the embodiment of the invention further provides a method for acquiring a sequence number, a mobility management entity, and a long term evolution network.
  • the MME obtains a GTP_U sequence number of the user SGW that is sent to acquire the next user data packet to be sent.
  • the next GTP_U sequence number to be sent to the user data packet is sent to the target SGW, and the target SGW uses the GTP_U sequence number of the next user data packet to be sent as the GTP_U sequence number of the first user data packet sent by itself.
  • the GTP_U sequence number of the first user data packet sent by the target SGW to the eNB is continuous with the GTP_U sequence number of the last user data packet sent by the source SGW to the eNB.
  • FIG. 2 is a simplified flowchart of a data forwarding method according to Embodiment 1 of the present invention
  • FIG. 3 is a simplified flowchart of a data forwarding method according to Embodiment 2 of the present invention.
  • FIG. 4 is a simplified flowchart of a data forwarding method according to Embodiment 3 of the present invention
  • FIG. 5 is a simplified flowchart of a data forwarding method according to Embodiment 5 of the present invention.
  • FIG. 6 is a simplified flowchart of a data forwarding method according to Embodiment 6 of the present invention.
  • FIG. 7a is a schematic flowchart of a first target SGW according to Embodiment 8 of the present invention, which obtains a GTP_U sequence number of a user data packet to be sent by a source SGW;
  • FIG. 7b is a schematic flowchart of a second target SGW according to Embodiment 8 of the present invention, which obtains a GTP_U sequence number of a user data packet sent by a source SGW;
  • FIG. 7c is a schematic diagram of a simplified flow chart of obtaining a GTP_U sequence number of a user data packet to be sent by a source SGW according to a third target SGW provided by Embodiment 8 of the present invention.
  • FIG. 7 is a simplified schematic flowchart of obtaining a GTP_U sequence number of a user data packet sent by a source SGW according to a fourth target SGW according to Embodiment 8 of the present invention.
  • Embodiment 8 is a simplified flowchart of a data forwarding method according to Embodiment 10 of the present invention.
  • FIG. 9 is a flowchart of recovering an S1 port data packet by an X2 handover failure source eNB according to Embodiment 10 of the present invention.
  • FIG. 11 is a simplified flowchart of a data forwarding method according to Embodiment 11 of the present invention.
  • FIG. 12 is a schematic structural diagram of an evolved base station eNB according to Embodiment 4 of the present invention.
  • FIG. 13 is a schematic structural diagram of an evolved base station eNB according to Embodiment 7 of the present invention.
  • FIG. 14 is a schematic structural diagram of a mobility management entity MME according to Embodiment 9 of the present invention. detailed description
  • This embodiment mainly introduces the handover completion phase of the X2 handover procedure (the division of the specific X2 handover procedure phase is the same as the background technology), and the target eNB determines to send the user data packet delivered by the SGW to the UE by receiving the special data packet constructed by the source eNB ( That is, the timing of sending the S1 port packet).
  • the specific steps of this embodiment include:
  • Step 201 The SGW performs path switching.
  • Step 202 The target eNB receives the user data packet delivered by the SGW.
  • Step 203 After the source eNB receives the release resource information sent by the target eNB, if the source eNB If there is no user data packet sent to the target eNB in the transmit data buffer, the source eNB constructs a special data packet including the end tag, and transmits the special data packet including the end tag to the target eNB.
  • the special data packet including the end tag carries the sequence number of the Packet Data Convergence Protocol (PDCP) of the next packet to be transmitted by the source eNB.
  • the source eNB can know the PDCP sequence number of the last user data packet that has been sent according to the transmission data buffer, and the sequence number is incremented by 1, which is the sequence number of the PDCP of the next data packet to be sent by the source eNB.
  • PDCP Packet Data Convergence Protocol
  • the source eNB can know the PDCP sequence number of the last user data packet that has been sent according to the transmission data buffer, and the sequence number is incremented by 1, which is the sequence number of the PDCP of the next data packet to be sent by the source eNB.
  • a certain byte of the packet header of the data packet may be set, so that the special data packet has a function of indicating the end of the transmission, that is, the special data packet is in the current transmission data packet.
  • the last packet The special data packet does not
  • Step 204 After receiving the special data packet that is sent by the source eNB and including the end tag, the target eNB learns that the X2 port data packet is sent, and sends the user data packet sent by the SGW to the UE.
  • the target eNB receives the special data packet including the end tag, and obtains the PDCP sequence number carried by the data packet.
  • the target eNB calculates the user data packet to be sent to the UE according to the PDCP sequence number before transmitting the first user data packet of the S1 port.
  • the PDCP sequence number ensures that the PDCP number received by the UE is continuous.
  • the source eNB notifies the target eNB of the end of the data packet transmission by constructing and transmitting the special data packet including the end tag to the target eNB when the data buffer has no user data packet; the target eNB receives After the special data packet including the end tag is sent, the user data packet sent by the SGW is sent to the UE, that is, the S1 port data packet is forwarded to the UE.
  • the target eNB when the data buffer of the source eNB is not sent by the user data packet to the target eNB, the target eNB does not need to wait for the timer to time out to forward the S1 port data packet, thereby improving forwarding during the X2 handover process.
  • Embodiment 2 This embodiment mainly introduces the handover completion phase of the X2 handover process (the specific X2 handover process phase is divided into the background technology), and the target eNB determines to forward the user data packet delivered by the SGW to the user by receiving the special data packet constructed by the SGW. The timing of sending the S1 port packet).
  • the specific steps of this embodiment include:
  • Step 301 When receiving the path switching request, the SGW constructs a special data packet including an end tag, and sends the special data packet including the end tag to the source eNB.
  • the SGW notifies the source eNB that the transmission of the S1 port sent by the SGW to the source eNB during the X2 handover is terminated by transmitting the special packet including the end tag.
  • the structure of the special data packet is the same as that in the first embodiment, and details are not described herein again.
  • the special data packet including the end tag does not carry user data, and the target eNB does not send the special data packet including the end tag to the UE.
  • Step 302 The target eNB receives the user data packet delivered by the SGW.
  • Step 303 After receiving the special data packet including the end tag, the source eNB sends the special data packet including the end tag to the target eNB, and notifies the target eNB that the X2 port data packet transmission sent by the source eNB to the target eNB is ended in the X2 handover process. .
  • Step 304 After receiving the handover complete response message sent by the SGW, the target eNB sends the user data packet sent by the SGW to the UE if the special data packet including the end tag sent by the source eNB is received, and the X2 port data packet has been forwarded. .
  • step 3031 The above step 303 in this embodiment can be replaced by step 3031:
  • Step 3031 The source eNB reconstructs a special data packet including the end tag according to the special data packet sent by the SGW and includes the end tag, and sends the reconstructed special data packet including the end tag to the target eNB.
  • the special data packet including the end tag reconstructed by the source eNB carries the sequence number of the PDCP of the next packet to be transmitted by the source eNB.
  • the source eNB can know the PDCP sequence number of the last user data packet that has been sent according to the transmission data buffer, and the sequence number is incremented by 1, which is the sequence number of the PDCP of the next data packet to be sent by the source eNB.
  • the target eNB receives the special data packet including the end tag, and obtains the PDCP sequence number carried by the data packet.
  • the target eNB calculates the user data packet to be sent to the UE according to the PDCP sequence number before transmitting the first user data packet of the S1 port.
  • the PDCP sequence number ensures that the PDCP number received by the UE is continuous.
  • the SGW constructs and transmits a special data packet including the end tag, and notifies the source eNB that the data packet transmission sent by the SGW is ended in the X2 handover process; the source eNB transmits to the target eNB. Sending the special data packet including the end tag, and notifying the target eNB that the user data packet forwarded by the X2 port has been sent in the X2 handover process; the target eNB sends the special data packet including the end tag, and then sends the SGW to the UE.
  • the user data packet that is, the S1 port data packet is forwarded to the UE.
  • the target eNB does not need to wait for the timer to time out to forward the SI port data packet, thereby improving the efficiency of forwarding the user data packet in the X2 handover process.
  • This embodiment mainly introduces the handover completion phase of the X2 handover procedure (the division of the specific X2 handover procedure phase is the same as the background technology), and the target eNB determines to forward the user data packet or the special data packet carrying the end marker constructed by the source eNB.
  • the timing of the user data packet delivered by the SGW that is, the S1 port packet is sent.
  • the specific steps of this embodiment include:
  • Step 401 the SGW performs path switching.
  • Step 402 The target eNB receives the user data packet delivered by the SGW.
  • Step 403 After receiving the release resource information sent by the target eNB, the source eNB determines whether there is a user data packet sent to the target eNB in the data buffer. If yes, go to step 404. Otherwise, go to step 405.
  • Step 404 The source eNB adds a last tag to the last user data packet in the user data packet, and sends the user data packet carrying the last tag to the target eNB. Step 406 is performed.
  • Step 405 The source eNB constructs a special data packet including an end tag, and sends the special data packet including the end tag to the target eNB, and step 407 is performed.
  • the special data packet including the end tag carries the PDCP sequence number of the next data packet to be transmitted by the source eNB.
  • the source eNB can know the PDCP sequence number of the user data packet data that has been sent according to the transmission data buffer, and the sequence number is incremented by one, which is the next user data to be sent by the source eNB.
  • the serial number of the PDCP of the packet is the serial number of the PDCP of the packet.
  • a certain byte of the packet header of the data packet may be set, so that the special data packet has a function of indicating the end of the transmission, that is, the special data packet is in the current transmission data packet.
  • the last packet The structure of the special data packet is the same as that in the first embodiment, and details are not described herein again.
  • the special data packet including the end tag does not carry the user data, and the target eNB does not send the special data packet including the end tag to the UE.
  • Step 406 The target eNB determines that the user data packet carrying the last tag is received, and sends the user data packet carrying the last tag to the UE, and step 408 is performed.
  • Step 407 The target eNB determines that the special data packet including the end tag is received, and performs step 408.
  • the target eNB receives the special data packet including the end tag, and obtains the PDCP sequence number carried by the data packet.
  • the target eNB calculates the user data packet to be sent to the UE according to the PDCP sequence number before transmitting the first user data packet of the S1 port.
  • the PDCP sequence number ensures that the PDCP number received by the UE is continuous.
  • Step 408 The target eNB sends an S1 port data packet to the UE.
  • the source eNB determines whether there is a user data packet that needs to be sent to the target eNB in the sending data buffer, and constructs a user data packet carrying the last tag or a special data packet including the end tag, and sends the data packet to the target eNB. Notifying the target eNB that the X2 port data packet has been sent to the end; the target eNB sends the S1 port user data packet to the UE. With the technical solution provided in this embodiment, the target eNB does not need to wait for the timer to time out to send the S1 port data packet, which improves the efficiency of forwarding the user data packet in the X2 switching process.
  • Embodiment 4 Embodiment 4
  • the embodiment provides a long term evolution network, where the network includes: a source eNB, a target eNB, a UE, and an SGW.
  • the target eNB After receiving the handover complete response message sent by the SGW, the target eNB transmits the user data packet of the S1 port to the UE if receiving the special data packet including the end tag sent by the source eNB. As shown in FIG. 12, the target eNB further includes: a user data packet receiving unit 1210, a special data packet determining unit 1220, and a user data packet transmitting unit 1230.
  • the user data packet receiving unit 1210 receives the user data packet sent by the user plane processing gateway; after receiving the handover completion response information sent by the SGW, the special data packet determining unit 1220 determines whether a special data packet including the end tag is received, if The result of receiving the special data packet is generated; the user data packet transmitting unit 1230 transmits the S1 port user data packet received by the user data packet receiving unit to the UE when the special data packet determining unit generates the result of receiving the special data packet.
  • the special data packet including the end tag received by the target eNB may be constructed by the SGW or may be constructed by the source eNB.
  • a certain byte of the packet header of the data packet may be set, so that the special data packet has a function of indicating the end of the transmission, that is, the special data packet is in the current transmission data packet.
  • the last packet The structure of the special data packet is the same as that of the first embodiment, and details are not described herein again.
  • the special data packet including the end tag does not carry the user data, and the target eNB does not send the special data packet including the end tag to the UE.
  • the SGW constructs a special data packet including an end tag, and transmits the special data packet including the end tag to the source eNB.
  • the source eNB receives the special data packet including the end tag sent by the SGW.
  • the target eNB forwards the special data packet containing the end tag. After receiving the special data packet including the end tag, the target eNB starts to send the S1 port data packet to the UE.
  • the target eNB After receiving the release resource information sent by the target eNB, if the source eNB determines that the transmission data buffer does not send the user data packet to the target eNB, construct a special data packet including the end tag, and send the special data including the end tag to the target eNB. package. After receiving the special data packet including the end tag, the target eNB starts to send the S1 port data packet to the UE.
  • the end tag may be added to the last user data packet sent to the target eNB, and sent to the target eNB.
  • the target eNB sends the user data packet carrying the last tag to the UE after receiving the user data packet carrying the last tag, and then starts to send the S1 port data packet.
  • the SGW structure includes a special packet including the end tag
  • the source eNB sends the S1 packet sent by the SGW to the source eNB.
  • the source eNB reconstructs a special data packet including an end tag
  • the reconstructed special data packet including the end tag carries the PDCP sequence number of the next user data packet to be sent by the source eNB.
  • the target eNB sends the user data packet carrying the last tag to the UE, and then starts transmitting the S1 port data packet.
  • the source eNB can know the PDCP sequence number of the last user data packet sent according to the transmission data buffer, and the sequence number is incremented by 1, which is the serial number of the PDCP of the next data packet to be sent by the source eNB.
  • the target eNB receives the special data packet including the end tag, and obtains the PDCP sequence number carried by the data packet.
  • the target eNB calculates the user data packet to be sent to the UE according to the PDCP sequence number before transmitting the first user data packet of the S1 port.
  • the PDCP sequence number ensures that the PDCP number received by the UE is continuous.
  • the data forwarding method provided in this embodiment is that, in the X2 handover process, the target eNB sends the GPRS Tunneling Protocol User (GTP U) sequence number and the SGW according to the next user TP Tunneling Protocol User (GTP U) sequence number of the user data packet to be sent by the source eNB.
  • the GTP_U sequence number of the first user data packet determines when the X2 port data packet of the source eNB is transmitted, and starts to send the S1 port data packet to the UE.
  • FIG. 5 it is a simplified flowchart of the data forwarding method provided by this embodiment.
  • Step 501 After receiving the handover request response information sent by the target eNB, the source eNB acquires a GPRS Tunneling Protocol User (GTP U) of the next user data packet to be sent by the source eNB.
  • the sequence number sends the GTP_U sequence number of the next source eNB ready to send the user data packet to the target eNB.
  • GTP U GPRS Tunneling Protocol User
  • the source eNB receives the handover request response information sent by the target eNB. After that, the user data packet is stopped from being sent to the UE.
  • the SGW sends the user data packet to the source eNB by using the GPRS Tunneling Protocol (GTP).
  • GTP GPRS Tunneling Protocol
  • the user data packet carries the GTP_U sequence number.
  • the GTP_U sequence number carried by the user data packet sent by the SGW is continuous, generally continuous. Increment.
  • the source eNB can know the PDCP sequence number of the last user data packet that has been sent according to the transmission data buffer, and the sequence number is incremented by one, which is the sequence number of the PDCP of the user data packet to be sent by the source eNB.
  • the source eNB sends the GTP_U sequence number of the next user data packet to be sent by the source eNB to the target eNB, and the following two methods are used: One is to construct the carrier eNB next preparation on the control plane. Sending the message to the target eNB by sending a message of the GTP_U sequence number and the PDCP sequence number of the user data packet, for example, sending the GTP_U sequence number and the PDCP sequence number of the user data packet that is to be sent by the source eNB.
  • the method of constructing a special data packet by the source eNB in the foregoing first embodiment the source eNB stops sending the user data packet to the user equipment after receiving the handover request response message sent by the target eNB.
  • Step 502 The target eNB acquires the GTP_U sequence number of the next user data packet to be sent by the source eNB and the GTP_U sequence number of the first user data packet sent by the SGW.
  • the SGW sends a user data packet to the target eNB.
  • the target eNB acquires the GTP_U sequence number of the first user data packet sent by the SGW.
  • the SGW maintains the continuity of the GTP-U sequence number when the path is switched.
  • the specific method may be: after receiving the handover complete message of the target eNB, the SGW performs path switching, and sets a GTP_U sequence number of the switched path according to the GTP_U sequence number of the path before the handover, so that the GTP_U sequence The number is continuous.
  • Step 503 After the handover completion response message sent by the core network device, the target eNB receives the GTP_U sequence number of the user data packet to be sent by the source eNB and the first user data sent by the SGW.
  • the GTP-U sequence number of the packet is determined to be sent by the source eNB.
  • the user data packet (ie, the X1 port data packet) sent to the target eNB has been sent, and the target eNB sends the user data packet (ie, the S1 port data packet) delivered by the SGW to the UE.
  • (1) Obtain user data sent by the source eNB to the target eNB during the handover phase according to the GTP_U sequence number of the next user data packet to be sent by the source eNB and the GTP_U sequence number of the first user data packet sent by the SGW. If all the GTP_U sequence numbers of the packet are received, if the user data packet corresponding to all the GTP_U sequence numbers is received, it is determined that the user data packet (ie, the X2 port data packet) sent by the source eNB to the target eNB has been sent.
  • the GTP_U sequence number of the next user data packet to be sent by the source eNB is 1000
  • the GTP_U sequence number of the first user data packet sent by the SGW is 1000. Then, in this interface conversion, there is no description.
  • the forwarding data of the X2 port, the target eNB directly sends the data packet from the S1 port to the UE.
  • the GTP_U sequence number of the next user data packet to be sent by the source eNB is 1000
  • the GTP_U sequence number of the first user data packet sent by the SGW is 1051.
  • the source eNB The GTP_U sequence number of the user data packet sent to the target eNB is 1000 to 1050.
  • the target eNB may have various methods to determine whether the user data packet forwarded by the source eNB is transmitted. For example, the target eNB may save the GTP U sequence number calculated from 1000 to 1050 to the database.
  • the target eNB acquires the GTP-U sequence of the user data packet.
  • the target eNB sends the user data packets sent by all the source eNBs to the UE.
  • the target eNB when receiving the user data packet from the X2 port, acquires the GTP_U sequence number of the user data packet, and when transmitting the user data packet to the UE, saves the GTP_U sequence number of the obtained user data packet as Another database; when getting user data
  • the GTP-U serial number database of the packet is the same as the database record of the first GTP-U serial number segment, the user data packet that the source eNB needs to forward through the X2 port has been sent, and the target eNB sends all the packets to the UE. User data packets sent by the source eNB.
  • the GTP_U sequence number of the next user data packet to be sent by the source eNB is 1000
  • the GTP_U sequence number of the first user data packet sent by the SGW is 1051.
  • the source eNB The maximum GTP_U sequence number of the user data packet forwarded to the target eNB through the X2 port is 1050. If the user data packet with the GTP_U sequence number 1050 is received from the X2 port, it is determined that the source eNB ends transmitting the user data packet.
  • the GTP_U sequence number of the next user data packet to be sent by the source eNB is smaller than the GTP_U sequence number of the first user data packet sent by the SGW, determining that the user data packet sent by the source eNB to the target eNB has not yet been
  • the X2 port data packet sent by the source eNB is continuously sent to the UE, until the GTP_U sequence number of the next source eNB ready to send the user data packet is equal to the GTP_U sequence number of the first user data packet sent by the SGW. If the data is not forwarded from the source eNB, the S1 port data packet sent by the SGW to the target eNB is started to be sent to the UE.
  • the source eNB may not send the next GTP_U sequence number of the next user to send the user data packet to the target eNB, but send the last user data sent by the source eNB to the UE in the X2 handover preparation phase.
  • the GTP_U sequence number of the packet because the GTP_U sequence number of the user data packet is continuous, the target eNB may also send the GTP_U sequence number and the SGW of the last user data packet sent by the source eNB to the UE.
  • the GTP_U sequence number of the first user data packet can be determined by the source eNB to end transmitting the user data packet.
  • the source eNB sends the GTP_U sequence number of the next ready to send user data packet sent by the source eNB to the target eNB, and the target eNB sends the GTP_U of the next user data packet to be sent according to the source eNB.
  • the sequence number and the GTP_U sequence number of the first user data packet sent by the SGW may determine that the source eNB ends transmitting the user data packet, and then sends the user data packet sent by the SGW to the UE; the target eNB does not need to wait for the timer to time out.
  • Sending S1 port data packets improves the efficiency of forwarding user data packets during X2 handover.
  • the data forwarding method provided in this embodiment is also determined by the target eNB according to the GTP_U sequence number of the next user data packet to be sent by the source eNB and the GTP_U sequence number of the first user data packet sent by the SGW.
  • the data packet When the data packet is sent, it starts to send the S1 port data packet to the UE.
  • the eNB is the GTP_U sequence number of the next source eNB ready to send the user data packet obtained by the PDCP sequence number of the next user data packet to be received by the UE.
  • FIG. 6, is a flowchart of a data forwarding method according to Embodiment 6 of the present invention.
  • Step 601 In the X2 handover execution phase, the UE sends the PDCP sequence number of the next user data packet to be received by the UE to the target eNB.
  • the UE when the UE sends the handover confirmation information to the target eNB, the UE adds the PDCP sequence number of the next user data packet to be received to the handover confirmation information; and sends the next eNB ready to receive the user data packet to the target eNB.
  • the next PDCP sequence number to be received for the user data packet means that the UE calculates the PDCP sequence number of the next household data packet to be received according to the PDCP sequence number of the last user data packet received from the source eNB in the X2 handover preparation phase.
  • Step 602 The target eNB acquires a GTP_U sequence number of the next source eNB ready to send the user data packet, and a GTP_U sequence number of the first user data packet sent by the SGW.
  • the target eNB acquires a PDCP sequence number of the UE to receive the user data packet, and obtains the user data packet that is sent by the source eNB and carries the PDCP sequence number.
  • the GTP-U sequence number carried is used as the GTP_U sequence number of the target eNB that is ready to send the user data packet after the source eNB receives the handover request response message.
  • obtaining the GTP-U sequence number through the control plane signaling according to the method in the fifth method, and constructing, on the control plane, a message carrying the GTP_U sequence number and the PDCP sequence number of the next user data packet to be sent by the source eNB, The target eNB sends the message.
  • the SGW maintains the continuity of the GTP-U sequence number when the path is switched.
  • the specific method may be: after receiving the message that the eNB completes the handover, the SGW performs path switching, and sets the GTP_U sequence number of the switched path according to the GTP U sequence number of the path before the handover, so that the GTP U serial number is consecutive.
  • Step 603 After the handover completion response message is sent by the SGW, the target eNB selects the GTP_U sequence number of the next user data packet to be sent by the source eNB and the GTP_U of the first user data packet sent by the SGW.
  • the sequence number determines that the user data packet (ie, the X2 port data packet) sent by the source eNB to the target eNB has been sent, and the target eNB sends the user data packet (ie, the S1 port data packet) delivered by the SGW to the UE.
  • the method that has been sent is the same as that in the fifth embodiment, and will not be described here.
  • the UE acquires the PDCP sequence number of the next user data packet to be received according to the PDCP sequence number of the last user data packet received from the source eNB in the X2 handover preparation phase, and sends the PDCP sequence number to the target eNB. If the target eNB receives the user data packet that is sent by the source eNB and carries the PDCP sequence number of the next user data packet to be received, obtains the GTP_U sequence number carried by the user data packet, or the source eNB sends the X2 control signaling to notify the target.
  • the GTP-U sequence number that the eNB should send next uses the acquired GTP U sequence number as the next GTP-U sequence number of the source eNB to send the user data packet after receiving the handover request response information; the target eNB passes the The first GTP_U sequence number of the user data packet sent and the GTP_U sequence number of the first user data packet sent by the SGW, determining that the source eNB receives the transmitted user data packet, and then The UE sends the user data packet delivered by the SGW; the target eNB does not need to wait for the timer to time out to send the S1 port data packet, which improves the efficiency of forwarding the user data packet in the X2 handover process.
  • the embodiment provides a long term evolution network, including: a source eNB, a target eNB, and an SGW.
  • the source eNB After receiving the handover request response information, acquires the next GTP U sequence number of the user data packet to be sent, and sends the GTP-U to the target eNB to transmit the next user data packet to be sent after the source eNB receives the handover request response message.
  • the target eNB acquires the GTP_U sequence number of the next source eNB ready to send the user data packet and the GTP_U sequence number of the first user data packet sent by the SGW; the handover of the core network is not involved between the eNBs After receiving the handover complete response message sent by the core network device, determining, according to the GTP_U sequence number of the next source eNB that is to send the user data packet, and the GTP_U sequence number of the first user data packet, determining that the source eNB ends the sending user The data packet is sent to the UE by the user data packet sent by the SGW.
  • the target eNB includes: a next sequence number acquiring unit 1310, configured to acquire a GTP_U sequence number of the next ready to send user data packet after the source eNB receives the handover request response information;
  • the sequence number obtaining unit 1320 is configured to obtain a GTP_U sequence number of the first user data packet sent by the SGW, and the sending end determining unit 1330 is configured to receive the core network device in a handover end phase in which the core network is not involved between the eNBs.
  • the GTP_U serial number of the next user data packet to be sent and the GTP_U serial number of the one user data packet acquired by the one serial number acquisition unit acquired by the next serial number acquisition unit Determining whether the source eNB ends the transmission of the user data packet, and if so, the generation source eNB ends the transmission of the user data packet; and the data packet transmission unit 1340, when the transmission end determination unit generates the result of the source eNB ending the transmission of the user data packet, The UE sends the user data packet delivered by the SGW.
  • the method for the target eNB to obtain the GTP_U sequence number of the next source eNB to send the user data packet may be: the source eNB carries the GTP_U sequence number of the next user data packet to be sent in a message sent to the target eNB. . It can also be the following method:
  • the UE target eNB sends the next PDCP sequence number ready to receive the user data packet; the target eNB Acquiring the PDCP sequence number of the next user to receive the user data packet sent by the UE. If the target eNB receives the user data packet carrying the PDCP sequence number, the target eNB acquires the GTP_U sequence number carried by the user data packet, and obtains the The GTP-U sequence number is used as the next GTP-U sequence number of the source eNB to send the user data packet.
  • the SGW sends the user data packet to the eNB by using the GTP protocol.
  • the user data packet carries the GTP-U serial number.
  • the GTP-U serial number carried by the user data packet sent by the SGW is continuous, and is generally continuously incremented.
  • the eNB can verify the user data packet sent by the SGW according to the continuity of the GTP_U sequence number.
  • the target SGW In the SGW relocation phase, in the prior art, the target SGW (Relocated SGW) cannot know the GTP_U sequence number of the next user data packet to be sent by the source SGW (SGW before relocation), resulting in SGW heavy
  • the GTP_U sequence number of the first user data packet sent by the target SGW to the eNB is not continuous with the GTP_U sequence number of the last user data packet sent by the source SGW to the eNB.
  • the next GTP-U sequence number of the source SGW to be sent to transmit the user data packet refers to the GTP-U sequence number of the next user data packet to be sent after the source SGW sends the last user data packet to the eNB in the SGW relocation phase.
  • the technical solution provided by this embodiment is:
  • the MME obtains the GTP_U sequence number of the next source SGW to be sent by the source SGW, and the MME sends the GTP_U of the source SGW to prepare the next user data packet to the target SGW.
  • the serial number; the target SGW uses the GTP_U sequence number of the next ready to transmit user data packet as the GTP_U sequence number of the first user data packet transmitted to the eNB.
  • the target SGW will send the first user data packet carrying the GTP_U sequence number to the eNB. In this way, the continuity of the GTP-U sequence number of the data packet transmitted by the eNB can be maintained.
  • Step 7al the eNB sends a handover complete message (Ho complete) to the MME;
  • Step 7a2 the MME receives the Ho complete message and sends a data request message (Data req) to the source SGW to source the GTP of the next data packet to be sent by the SGW.
  • Ho complete handover complete message
  • Data req data request message
  • Step 7a3 the source SGW sends the GTP_U sequence number of the next data packet to be sent by the source SGW to the MME through a data request response message (Data req ack);
  • Step 7a4 The MME sends a GTP_U sequence number of the next data packet to be sent by the source SGW to the eNB through the handover completion response message (Ho complete ack) of the control plane, so that the GTP_U sequence number between the SGWs has a corresponding relationship. , to achieve a continuous purpose.
  • the target eNB adds the GTP_U sequence number as an offset and adds the GTP_U sequence number of the first data packet sent by the target SGW, and the GTP-U sequence of the data packet forwarded by the source eNB. No comparison, it is judged whether the forwarding data of the X2 port is sent. If the former is greater than or equal to the latter, the X2 port does not forward the data, and the target eNB directly sends the data of the SGW to the UE. If the former is smaller than the latter, the data is forwarded by the X2 port, and the target eNB forwards the data of the X2 port to the UE. After that, the UE sends the data from the SWG.
  • step 7bb-7b3 is the same as step 7al-7a3 above, and details are not described herein again.
  • Step 7b4 The MME sends the GTP_U sequence number of the next data packet to be sent by the source SGW to the target SGW by using a Create bearer req message.
  • the MME initiates the selection of the target SGW.
  • the MME sends a data request message (Data req) to the source SGW to source the GTP_U sequence number of the next sent data packet of the SGW;
  • Step 7c2 the SGW sends the GTP_U sequence number of the next data packet sent by the source SGW to the MME by using a data request response message (Data req ack);
  • step 7c3 the MME informs the target SGW of the GTP_U sequence number of the next data packet to be sent by the source SGW through the Create bearer req message.
  • the selection target SGW may also be initiated by the source SGW.
  • the step 7dl-7d3 is the same as the above step 7cl-7c3, and further includes: Step 7d0: The source SGW sends an SGW redirection request to the MME;
  • the MME After receiving the above redirection request, the MME starts step 7dl.
  • the MME obtains the GTP_U sequence number of the user SGW sent by the source SGW to obtain the next user data packet to be sent, and the next GTP-U sequence to be sent to send the user data packet.
  • the number is sent to the target SGW, and the target SGW uses the GTP_U sequence number of the next user data packet to be sent as the GTP_U sequence number of the first user data packet sent by itself; or the MME obtains the source SGW to send the next ready to send.
  • the GTP_U sequence number of the user data packet, and the GTP_U sequence number of the next user data packet to be sent is sent to the e B, so that the GTP_U sequence number between the SGWs has a corresponding relationship; thereby realizing the SGW weight
  • the GTP_U sequence number of the first user data packet sent by the target SGW to the eNB is consecutive with the GTP_U sequence number of the last user data packet sent by the source SGW to the eNB.
  • the long-term evolution network of this embodiment includes: an MME, configured to send, to the source SGW, request information for acquiring a GTP_U sequence number of the next user data packet to be sent in the SGW relocation phase; and sending the information to the target SGW from the source SGW.
  • the U serial number has a corresponding relationship.
  • the source SGW is configured to receive, by the MME, request information for acquiring a GTP_U sequence number of the next user data packet to be sent, and send, to the MME, a GTP_U sequence number that is to be used to send the user data packet; and a target SGW, configured to receive The next GTP_U sequence number to be sent by the MME to send the user data packet, and the GTP_U sequence number of the next user data packet to be sent is used as the GTP_U sequence number of the first user data packet.
  • the MME includes: a request information sending unit 1410, configured to send, to the source SGW, request information for acquiring a GTP_U sequence number of the next user data packet to be sent in the SGW relocation phase;
  • the unit 1420 is configured to receive the next preparation sent by the source SGW.
  • the sequence number sending unit 1430 configured to send, to the target SGW, a GTP_U sequence number of the next ready to send user data packet received by the sequence number receiving unit; or for transmitting to the eNB
  • the GTP_U sequence number of the next user data packet to be sent by the source SGW is such that the GTP_U sequence number between the source SGW and the target SGW has a corresponding relationship.
  • the data forwarding method provided by this embodiment specifically includes the following steps: Step 801: After receiving the handover request response information sent by the target eNB, the source eNB sends a stop source to the SGW. The eNB sends request information of the user data packet. Before receiving the request response information sent by the target eNB, the SGW sends a user data packet to the source eNB, and the source eNB sends the user data packet delivered by the SGW to the UE. It can be understood that, when the specific eNB sends the request information to the SGW, the source eNB may send the request information to the SGW to stop sending the user data packet to the source eNB.
  • Step 802 After receiving the request information for stopping sending the user data packet to the source eNB, the SGW stops sending the user data packet to the source eNB. As shown in step 6a or 7a of Fig. 9, these two timings may be selected.
  • Step 803 After the path switching is performed in the X2 handover completion phase, the SGW sends a user data packet to the target eNB.
  • Step 804 After receiving the handover completion response message sent by the SGW, the target eNB starts to send the user data packet delivered by the SGW to the UE.
  • the source eNB After determining that the X2 handover fails and restoring the connection of the source eNB, sending, to the SGW, request information for resuming transmission of the user data packet to the source eNB; after receiving the request information for transmitting the user data packet to the source eNB, the SGW resumes transmitting the user data to the source eNB. package. Step 9 of Figure 9.
  • the X2 handover failure source eNB recovers the S1 port data packet according to the tenth embodiment of the present invention.
  • the flow chart includes the following steps:
  • Steps 1 to 5 are the same as steps 1 to 5 of the background art, and are not described here.
  • Step 6 The target eNB sends a handover request response message to the source eNB, and the source eNB sends a bearer to the core network device to send the user to the source eNB.
  • Step 7 The source eNB sends handover command information to the UE.
  • Step 8 The UE sends information that is restored to the source eNB to the source eNB.
  • Step 9 After the source eNB determines that the handover fails, the UE resumes the connection with the source eNB, and the source eNB sends a request message for resuming the transmission of the user data packet to the source eNB to the SGW.
  • the SGW receives the request information for sending the user data packet to the source eNB. Resume sending user data packets to the source eNB.
  • the source eNB after receiving the handover request response information sent by the target eNB, the source eNB sends a request message for stopping the transmission of the user data packet to the source eNB, and the SGW stops the request information after the SGW receives the request information.
  • the user data packet sent by the SGW is sent; the target eNB does not need to wait for the timer to time out to send the S1 port data packet, which improves the efficiency of forwarding the user data packet in the X2 handover process.
  • the eNB After the eNB determines that the X2 handover fails, the eNB sends a request message for resuming transmission of the user data packet to the source eNB, and the SGW resumes transmitting the user data to the source eNB after receiving the request information. Packet; thus, when the X2 handover fails, the network is restored to the state before the X2 handover, and the network is guaranteed to operate normally.
  • the data forwarding method provided in this embodiment is in the X2 handover preparation phase (the specific handover procedure phase is divided into the background technology), after the source eNB sends the handover command information (Handover Command) to the UE, the source eNB and the UE are disconnected, and the source The eNB needs to perform data forwarding through the X2 port. At this time, the source eNB sends a control plane message to the target eNB, where the control plane message carries the PDCP sequence number and the GTP_U sequence number of the first user data packet that the target eNB should number.
  • the control plane message carries the PDCP sequence number and the GTP_U sequence number of the first user data packet that the target eNB should number.
  • Target eNB root According to the GTP_U sequence number and the GTP_U sequence number of the first user data packet sent by the SGW, it is determined when the X2 port data packet of the source eNB is transmitted, and the S1 port data packet is started to be sent to the UE. As shown in FIG. 11, the specific steps of this embodiment are as follows:
  • Step 1101 After the source eNB sends the handover command information (Handover Command) to the UE, the source eNB sends a control plane message to the target eNB, for example, a handover confirmation message (Ho commit), as shown in FIG. 10
  • the other process steps in the figure are the same as the background art flow chart, and are not described here.
  • the control plane message carries the PDCP sequence number and the GTP_U sequence number of the first user data packet that the target eNB should number.
  • the PDCP sequence number of the first user data packet that the target eNB should be numbered is:
  • the source eNB adds 1 to the PDCP sequence number of the last user data packet that has been sent from the PDCP layer to the lower layer, and the source eNB is next ready to send the user.
  • the GTP-U sequence number of the data packet is: the GTP_U sequence number of the last user data packet that the source eNB has sent from the PDCP layer to the lower layer is incremented by one.
  • Step 1102 The source eNB forwards the user data packet to the target eNB.
  • the source eNB carries the PDCP sequence number when transmitting the user data packet through the X2 port. In this case, the source eNB selectively transmits the user data packet to the target eNB according to whether the lower layer receives the receiving response of the UE. For example, before the handover, the source eNB directly transmits the user data packets 1, 2, 3 and 4 to the UE, the UE only receives the user data packets 1 and 4, and the UE transmits the reception response of the user data packets 1 and 4 to the source eNB, then After the handover, the source eNB forwards only the user data packets 2 and 3 to the target eNB according to the reception response.
  • the data that the source eNb forwards to the target eNb through the X2 port includes three cases of combining the above two kinds of user data packets, that is, two cases including only one type of data packet, and one case including two types of data packets at the same time.
  • the source eNB sends two user data packets with PDCP sequence numbers of 1, 3, respectively, to the target eNB, that is, the two data packets are processed by the PDCP layer and have a PDCP sequence number.
  • source The eNB sends a control plane message (such as a Ho commit message) to the target eNB, where the control plane message carries a PDCP sequence number of 4, and the GTP U sequence number is 5.
  • the target eNB receives the PDCP number 4 for the next data packet sent to the UE when receiving the control plane message.
  • Step 1103 The target eNB determines, according to the GTP_U sequence number of the next user data packet to be sent by the source eNB, which is carried by the control plane message (such as Ho commit), the data packet forwarded by the source eNB to the target eNB through the X2 port. Whether the transmission is completed, if the transmission is not completed, the X2 port data packet is continuously sent to the UE, and if the transmission is completed, the S1 port data packet is started to be sent to the UE.
  • the control plane message such as Ho commit
  • the method for determining whether the X2 port data packet is sent in this step may be: the target eNB acquires the GTP_U sequence number of the first S1 port data packet sent by the SGW to the target eNB, and associates it with the GTP in the control plane message. U serial numbers are compared. When the GTP U sequence number in the control plane message (Ho commit) is smaller than the GTP_U sequence number of the first S1 port data packet sent by the SGW to the target eNB, the source eNB also has an X2 port sent to the target eNB.
  • Ho commit the GTP U sequence number in the control plane message
  • the data packet, and the difference between the two GTP_U serial numbers is used to learn that there are still several X2 port data packets to be sent, and the target eNB sends the X2 port data packet to the UE.
  • the PDCP SN in the control plane message is numbered. If there is a PDCP sequence number, the sequence number is used to send the data packet to the UE.
  • the GTP_U sequence number in the control plane message (Ho commit) is equal to the GTP_U sequence number of the first S1 port data packet sent by the SGW to the target eNB, it indicates that the source eNB has not sent the X2 port to the target eNB.
  • the target eNB starts to send the user data packet of the S1 port to the UE.
  • the number is based on the PDCP SN in the control plane message.
  • the serial number of the PDCP is used to number the packet.
  • the method in the present step can also use a similar method in the fifth embodiment of the present invention, and details are not described herein again.
  • the solution requires that the GTP-U sequence number sent by the SGW before and after the path switch maintains continuity, and multiple methods may be used, for example, the packet data network processing gateway PDN-GW uniformly allocates the GTP-U sequence number, or may similarly The method of maintaining the continuity of the GTP-U serial number provided in the eighth embodiment is used.
  • a timer can be added to the target eNB to ensure that if the timer expires, the data of the S1 port is directly delivered.
  • the technical solution provided by the eleventh embodiment can enable the target eNB to know in time when the source eNB sends the X2 port data packet, and starts sending the S1 port data packet to the UE, without the target eNB waiting for the timer to expire. Improve the efficiency of forwarding user data packets during X2 handover.

Description

数据转发的方法、 演进基站和长期演进网络 技术领域
本发明涉及移动通信领域, 尤其涉及切换过程中数据转发的方法与演进 基站和长期演进网络。 背景技术
在长期演进( Long Term Evolution , LTE ) 网络中, 包括核心网设备和演 进基站( eNode B , eNB )。核心网设备包括移动管理实体 (Mobility Management Entity, MME)和用户面处理网关 ( Serving Gateway, SGW )。 MME属于控制 面部分, 负责控制面的移动性管理, 包括用户上下文和移动状态管理, 分配 用户临时身份标识等; SGW属于用户面部分, 负责空闲状态时为下行数据发 起寻呼, 管理保存 IP承载参数和网络内路由信息等; MME与 SGW之间呈网 状连接, 一个 MME可以控制若干个 SGW。 核心网设备与 eNB之间使用 S1 接口进行通信, eNB之间使用 X2接口进行通信。
eNB 间不涉及核心网的切换 (简称 X2 切换) 是指用户设备 (User Equipment, UE ) 断开源 eNB , 接入目标 eNB的过程。 切换之前, 包括测量 阶段, 源 eNB与 UE进行交互, 源 eNB接收到测量报告。 切换过程包括以下 3个阶段: 切换预备阶段, 源 eNB与目标 eNB进行交互, 源 eNB接收切换请 求应答后, 向 UE发送切换命令; 切换执行阶段, UE与目标 eNB进行交互, 目标 eNB接收到 UE的切换确认信息; 切换完成阶段, 目标 eNB与核心网设 备进行交互, 目标 eNB接收切换完成应答后, 向源 eNB发送释放资源信息, 源 eNB释放资源。
如图 1所示现有技术的 X2切换流程图, X2切换流程包括:
切换前测量阶段:
步骤 1 , 源 eNB向 UE发送测量控制信息( Measurement Control );
步骤 2 , UE向源 eNB发送测量报告信息 ( Measurement Reports )。 切换预备阶段:
步骤 3 , 源 eNB进行切换决策( HO decision );
步骤 4, 源 eNB向目标 eNB发送切换请求信息 ( Handover Request ); 步骤 5 , 目标 eNB进行接纳控制 ( Admission Control );
步骤 6 , 目标 eNB向源 eNB发送切换请求应答信息 ( Handover Request Ack );
步骤 7 , 源 eNB向 UE发送切换命令信息( Handover Command )。
切换执行阶段:
步骤 8, UE向目标 eNB发送同步信息 ( Synchronisation );
步骤 9,目标 eNB向 UE发送为 UE分配上行链路信息( UL allocation + TA for UE );
步骤 10, UE向目标 eNB发送切换确认信息( Handover Confirm )。
切换完成阶段:
步骤 11 , 目标 eNB向 SGW发送切换完成信息 ( Handover Complete ); 步骤 12 , SGW 进行路径切换, 向目标 eNB 发送切换完成应答信息 ( Handover Complete Ack );
步骤 13 , 目标 eNB向源 eNB发送释放资源信息 ( Release Resource ); 步骤 14, 源 eNB进行释放资源 ( Release Resources )。
在切换完成阶段之前, SGW向源 eNB发送用户数据包;在切换完成阶段, SGW进行路径切换后, SGW向目标 eNB发送用户数据包。
在切换执行阶段之前, 源 eNB直接向 UE发送 SGW下发的用户数据包。 在切换执行阶段, 源 eNB已经和 UE中断了连接, 源 eNB不能将 SGW下发 的用户数据包直接发送给 UE,源 eNB使用 X2接口向目标 eNB转发 SGW下 发的用户数据包, 目标 eNB接收到 UE发送的切换确认信息后, 将源 eNB转 发过来的 X2口数据包(在 eNB之间的 X2接口转发的用户数据包简称为 X2 口数据包)发送给 UE。 在切换完成阶段, 目标 eNB接收 S1口数据包(SGW 下发给 eNB的用户数据包简称为 S1 口数据包), 为保证 UE接收到的用户数 据包的有序性, 目标 eNB发送完 X2口数据包后, 才发送 S1口数据包。
在现有技术中,在 X2切换执行阶段, 目标 eNB接收 UE发送的切换确认 信息后, 启动定时器; 在定时器超时前,发送 X2口数据包; 在定时器超时后, 发送 S1口数据包。 在 X2切换完成阶段, SGW进行路径切换前, 把末尾标记 添加到发送给源 eNB的最后一个用户数据包, 向源 eNB发送该携带末尾标记 的用户数据包; 源 eNB向目标 eNB转发该携带末尾标记的用户数据包; 当目 标 eNB接收到该携带末尾标记的用户数据包后,获知源 eNB的用户数据包已 经发完, 向 UE发送该携带末尾标记的用户数据包后, 发送 S1口数据包。
在对现有技术的研究和实践过程中, 发明人发现现有技术存在以下问题: 如果 SGW没有用户数据包需要向源 eNB发送, 则源 eNB就不会接收到携带 末尾标记的用户数据包, 目标 eNB也就不会接收到源 eNB转发的携带末尾标 记的用户数据包, 此时, 目标 eNB无法获知源 eNB的用户数据包何时发完, 只有等待定时器超时, 才能发送 S1口数据包。 可见, 目标 eNB在 X2切换过 程中转发用户数据包的效率不高。 发明内容
本发明实施例提供一种切换过程中数据转发的方法与演进基站和长期演 进网络, 以提高目标 eNB在 X2切换过程中转发用户数据包的效率。
本发明实施例提供一种数据转发的方法, 在演进基站 eNB间不涉及核心 网的切换结束阶段, 该方法包括: 在用户面处理网关 SGW进行路径切换后, 目标演进基站 eNB接收上述 SGW下发的用户数据包; 上述目标 eNB收到源 eNB发送的包含结束标记的特殊数据包,向用户设备发送上述 SGW下发的用 户数据包。
本发明实施例还提供一种长期演进网络, 包括: 用户设备、 源演进基站 eNB , 目标 eNB和用户面处理网关 SGW,
上述目标 eNB , 用于在上述 SGW进行路径切换后,接收上述 SGW下发 的用户数据包,并在接收到上述源 eNB发送的包含结束标记的特殊数据包后, 向上述用户设备发送上述 SGW下发的用户数据包。 本发明实施例还提供一种演进基站 eNB, 包括:
数据包接收单元, 用于接收用户面处理网关 SGW下发的用户数据包; 特殊数据包判断单元, 用于判断是否接收到包含结束标记的特殊数据包; 和
数据包发送单元, 用于当上述特殊数据包判断单元判断接收到所述包含 结束标记的特殊数据包时, 向用户设备发送上述数据包接收单元接收的上述 SGW下发的用户数据包。
本发明实施例还提供一种数据转发的方法, 在演进基站 eNB间不涉及核 心网的切换结束阶段, 包括: 用户面处理网关 SGW进行路径切换; 目标演进 基站 eNB接收上述 SGW下发的用户数据包; 如果源 eNB确定发送数据緩冲 区中有需要向上述目标 eNB发送的用户数据包,则上述源 eNB在向上述目标 eNB发送的最后一个用户数据包上添加末尾标记并发送, 目标 eNB接收到上 述携带末尾标记的用户数据包, 则在向用户设备发送上述携带末尾标记的用 户数据包后, 向上述用户设备发送上述 SGW下发的用户数据包; 或者如果源 eNB确定发送数据緩冲区中没有需要向上述目标 eNB发送的用户数据包, 则 上述源 eNB构造包含结束标记的特殊数据包,并向上述目标 eNB发送上述包 含结束标记的特殊数据包,目标 eNB接收到上述包含结束标记的特殊数据包, 向上述用户设备发送上述 SGW下发的用户数据包。
本发明实施例还提供一种数据转发的方法, 在演进基站 eNB间不涉及核 心网的切换结束阶段, 包括: 目标 eNB获取源 eNB下一个准备发送的用户数 据包的分组域隧道协议用户面 GTP— U序列号和用户面处理网关 SGW发送的 第一个用户数据包的 GTP— U序列号; 根据上述源 eNB下一个准备发送的用 户数据包的 GTP— U序列号和上述 SGW发送的第一个用户数据包的 GTP— U 序列号, 确定上述源 eNB向上述目标 eNB发送的用户数据包已发送完毕; 向 用户设备发送上述 SGW下发的用户数据包。
本发明实施例还提供一种长期演进网络, 包括: 用户设备、 用户面处理 网关 SGW、 目标演进基站 eNB和源 eNB, 上述目标 eNB, 用户获取上述源 eNB下一个准备发送的用户数据包的分 组域隧道协议用户面 GTP— U序列号和上述 SGW发送的第一个用户数据包的 GTP— U序列号, 并根据上述源 eNB下一个准备发送的用户数据包的 GTP— U 序列号和上述 SGW发送的第一个用户数据包的 GTP— U序列号, 确定上述源 eNB向上述目标 eNB发送的用户数据包已发送完毕, 向用户设备发送上述 SGW下发的用户数据包。
本发明实施例还提供一种演进基站 eNB, 包括:
下一个序列号获取单元, 用于获取源 eNB下一个准备发送用户数据包的 分组域隧道协议用户面 GTP— U序列号;
第一个序列号获取单元,用于获取用户面处理网关 SGW发送的第一个用 户数据包的 GTP— U序列号;
发送结束判断单元, 根据上述源 eNB下一个准备发送用户数据包的 GTP— U序列号和上述 SGW发送的第一个用户数据包的 GTP— U序列号,判断 上述源 eNB是否结束发送用户数据包;
数据包发送单元, 用于当所述发送结束判断单元判断上述源 eNB结束发 送用户数据包时, 向用户设备发送上述用户面处理网关下发的用户数据包。
本发明实施例还提供了一种获取序列号的方法, 包括:
在用户面处理网关 SGW重定位阶段, 移动管理实体 MME从源 SGW获 取上述源 SGW 下一个准备发送的用户数据包的分组域隧道协议用户面 GTP— U序列号;
上述 MME向目标 SGW发送上述 GTP— U序列号, 上述目标 SGW把上 述 GTP— U序列号作为上述目标 SGW第一个用户数据包的 GTP— U序列号; 或者,
上述 MME向演进基站 eNB发送上述源 SGW下一个准备发送的用户数 据包的 GTP— U序列号,使源 SGW和目标 SGW之间的 GTP— U序列号有对应 关系。
本发明实施例还提供一种移动管理实体 MME, 包括: 请求信息发送单元,用于在用户面处理网关 SGW重定位阶段,向源 SGW 发送获取下一个准备发送用户数据包的 GTP— U序列号的请求信息;
序列号接收单元,用于接收源 SGW发送的下一个准备发送用户数据包的 GTP— U序列号;
序列号发送单元, 用于向目标 SGW发送序列号接收单元接收的上述源 SGW下一个准备发送用户数据包的 GTP— U序列号;或者用于向演进基站 eNB 发送上述源 SGW下一个准备发送的用户数据包的 GTP— U序列号,使源 SGW 和目标 SGW之间的 GTP— U序列号有对应关系。
本发明实施例还提供一种长期演进网络, 包括: 移动管理实体 MME, 目 标用户面处理网关 SGW和源 SGW,
上述 MME, 用于从上述源 SGW获取上述源 SGW下一个准备发送的用 户数据包的分组域隧道协议用户面 GTP— U序列号, 并向上述目标 SGW发送 上述 GTP— U序列号;
上述目标 SGW, 用于接收上述 GTP— U序列号, 并把上述 GTP— U序列号 作为上述目标 SGW第一个用户数据包的 GTP— U序列号。
本发明实施例还提供一种数据转发的方法, 包括:
在演进基站 eNB间不涉及核心网的切换过程中, 用户面处理网关 SGW 接收源 eNB在收到切换请求应答信息后发送的停止向源 eNB发送用户数据包 的请求信息;
上述 SGW停止向上述源 eNB发送用户数据包;
上述 SGW进行路径切换后, 向上述目标 eNB发送用户数据包; 上述目标 eNB接收上述 SGW发送的切换完成应答信息, 向用户设备发 送上述 SGW下发的用户数据包。
本发明实施例还提供一种数据转发的方法, 包括:
在演进基站间不涉及核心网的切换过程中, 源演进基站 eNB向用户设备 发送切换命令后, 向目标 eNB发送控制面消息和用户数据包, 上述控面消息中携带目标 eNB应该进行编号的第一个 GTP— U序列号和 分组数据汇聚层协议 PDCP序列号,上述源 eNB向所述目标 eNB发送的用户 数据包包括: 经过 PDCP层处理的用户数据包和 /或未经过 PDCP层处理的用 户数据包;
当上述目标 eNB根据所述目标 eNB应该进行编号的第一个 GTP— U序列 号小于上述 SGW向目标 eNB发送的第一个用户数据包的 GTP— U序列号时, 上述目标 eNB继续向上述用户设备发送上述源 eNB向上述目标 eNB发送的 用户数据包;
当上述目标 eNB根据上述目标 eNB应该进行编号的第一个 GTP— U序列 号等于上述 SGW向目标 eNB发送的第一个用户数据包的 GTP— U序列号时, 上述目标 eNB向上述用户设备发送上述 SGW向上述目标 eNB发送的用户数 据包。
从以上的技术方案可以看出, 进行不涉及核心网的切换时, 目标 eNB不 需要等待定时器超时, 才能发送 S1口数据包, 从而提高在不涉及核心网的切 换过程中转发用户数据包的效率。
发明实施例进一步提供一种获取序列号的方法、 移动管理实体和长期演 进网络, 在 SGW重定位阶段, MME获取源 SGW发送获取下一个准备发送 的用户数据包的 GTP— U序列号, 将该下一个准备发送用户数据包的 GTP— U 序列号发送给目标 SGW, 目标 SGW把下一个准备发送用户数据包的 GTP— U 序列号作为自身发送的第一个用户数据包的 GTP— U序列号,从而实现在 SGW 重定位完成后, 目标 SGW向 eNB发送的第一用户数据包的 GTP_U序列号与 源 SGW向 eNB发送的最后一个用户数据包的 GTP— U序列号是连续的。 附图说明
图 1为现有技术的 X2切换简化流程图;
图 2为本发明实施例一提供的数据转发方法简化流程图;
图 3为本发明实施例二提供的数据转发方法简化流程图;
图 4为本发明实施例三提供的数据转发方法简化流程图; 图 5为本发明实施例五提供的数据转发方法简化流程图;
图 6为本发明实施例六提供的数据转发方法简化流程图;
图 7a为本发明实施例八提供的第一种目标 SGW获得源 SGW下一个准备 发送的用户数据包 GTP— U序列号的简化流程示意图;
图 7b为本发明实施例八提供的第二种目标 SGW获得源 SGW下一个准 备发送的用户数据包 GTP— U序列号的简化流程示意图;
图 7c为本发明实施例八提供的第三种目标 SGW获得源 SGW下一个准备 发送的用户数据包 GTP— U序列号的简化流程示意图;
图 7d为本发明实施例八提供的第四种目标 SGW获得源 SGW下一个准 备发送的用户数据包 GTP— U序列号的简化流程示意图;
图 8为本发明实施例十提供的数据转发方法简化流程图;
图 9为本发明实施例十提供的 X2切换失败源 eNB恢复 S1口数据包流程 图;
图 10为本发明实施例十一 X2切换简化流程图;
图 11为本发明实施例十一提供的数据转发方法简化流程图;
图 12为本发明实施例四中演进基站 eNB结构示意图;
图 13为本发明实施例七中演进基站 eNB结构示意图;
图 14为本发明实施例九中移动管理实体 MME结构示意图。 具体实施方式
实施例一
本实施例主要介绍在 X2切换流程的切换完成阶段(具体 X2切换流程阶 段的划分同背景技术 ), 目标 eNB通过接收源 eNB构造的特殊数据包, 确定 向 UE发送 SGW下发的用户数据包(即发送 S1 口数据包) 的时机。 如图 2 所示, 本实施例的具体步骤包括:
步骤 201 , SGW进行路径切换。
步骤 202, 目标 eNB接收 SGW下发的用户数据包。
步骤 203 , 源 eNB接收目标 eNB发送的释放资源信息后,如果源 eNB的 发送数据緩冲区中没有向目标 eNB发送的用户数据包,则源 eNB构造包含结 束标记的特殊数据包, 并向目标 eNB发送该包含结束标记的特殊数据包。
上述包含结束标记的特殊数据包中携带源 eNB下一个准备发送的数据包 的分组数据汇聚层协议 ( Packet Data Convergence Protocol , PDCP )的序列号。 源 eNB根据发送数据緩冲区可知道已发送的最后一个用户数据包的 PDCP序 列号, 该序列号加 1 , 就是源 eNB下一个准备发送的数据包的 PDCP的序列 号。 在构造包含结束标记的特殊数据包的时候, 可以对数据包的包头的某个 字节进行设置, 使该特殊数据包具有指示发送结束的功能, 即表明该特殊数 据包为当前发送数据包中最后一个数据包。 该特殊数据包没有携带用户数据, 目标 eNB接收到该特殊数据包后, 不会向 UE发送。
表 1
Figure imgf000011_0001
步骤 204,目标 eNB接收到源 eNB发送的包含结束标记的特殊数据包后, 得知 X2口数据包发送完毕, 向 UE发送 SGW下发的用户数据包。
目标 eNB接收到包含结束标记的特殊数据包,获取该数据包携带的 PDCP 序列号; 目标 eNB在发送 S1口第一个用户数据包前,根据该 PDCP序列号计 算准备向 UE发送的用户数据包 PDCP序列号, 从而保证 UE接收到的 PDCP 号是连续的。
从以上技术方案可以看出,源 eNB在发送数据緩冲区没有用户数据包时, 通过构造和发送包含结束标记的特殊数据包给目标 eNB, 通知目标 eNB X2 口数据包发送结束; 目标 eNB接收到该包含结束标记的特殊数据包后, 向 UE 发送 SGW下发的用户数据包, 即向 UE转发 S1 口数据包。 通过本实施例的 技术方案, 当源 eNB的发送数据緩冲区没有用户数据包向目标 eNB发送时, 目标 eNB不需要等待定时器超时才转发 S1口数据包,提高了在 X2切换过程 中转发用户数据包的效率。 实施例二 本实施例主要介绍在 X2切换流程的切换完成阶段(具体 X2切换流程阶 段的划分同背景技术 ), 目标 eNB通过接收 SGW构造的特殊数据包, 确定向 用户转发 SGW下发的用户数据包(即发送 S1 口数据包) 的时机。 如图 3所 示, 本实施例的具体步骤包括:
步骤 301 , SGW收到路径切换请求时, 构造一个包含结束标记的特殊数 据包, 向源 eNB发送该包含结束标记的特殊数据包。
SGW通过发送上述包含结束标记的特殊数据包, 通知源 eNB此次 X2切 换过程中 SGW发送给源 eNB的 S1口数据包发送结束。该特殊数据包的结构 同实施例一, 此处不再赘述。 包含结束标记的特殊数据包没有携带用户数据, 目标 eNB接收到该包含结束标记的特殊数据包后, 不会向 UE发送。
步骤 302, 目标 eNB接收 SGW下发的用户数据包。
步骤 303 , 源 eNB接收包含结束标记的特殊数据包后, 向目标 eNB发送 该包含结束标记的特殊数据包, 通知目标 eNB此次 X2切换过程中源 eNB发 送给目标 eNB的 X2口数据包转发结束。
步骤 304, 目标 eNB接收 SGW发送的切换完成应答信息后,如果接收到 源 eNB发送的包含结束标记的特殊数据包, 获知 X2口数据包已经转发结束, 则向 UE发送 SGW下发的用户数据包。
本实施例中的上述步骤 303可以用步骤 3031进行替换:
步骤 3031 , 源 eNB根据 SGW发送的包含结束标记的特殊数据包重新构 造一个包含结束标记的特殊数据包, 并向目标 eNB发送该重新构造的包含结 束标记的特殊数据包。
上述由源 eNB重新构造的包含结束标记的特殊数据包中携带源 eNB下一 个准备发送的数据包的 PDCP的序列号。 源 eNB根据发送数据緩冲区可知道 已发送的最后一个用户数据包的 PDCP序列号, 该序列号加 1 , 就是源 eNB 下一个准备发送的数据包的 PDCP的序列号。 目标 eNB接收到包含结束标记 的特殊数据包,获取该数据包携带的 PDCP序列号; 目标 eNB在发送 S1口第 一个用户数据包前, 根据该 PDCP序列号计算准备向 UE发送的用户数据包 PDCP序列号, 从而保证 UE接收到的 PDCP号是连续的。
从以上技术方案可以看出, X2 切换完成阶段, SGW通过构造并发送包 含结束标记的特殊数据包,通知源 eNB此次 X2切换过程中 SGW下发的数据 包发送结束; 源 eNB发送向目标 eNB发送该包含结束标记的特殊数据包, 通 知目标 eNB此次 X2切换过程中 X2口转发的用户数据包已经发送结束; 目标 eNB接收到包含结束标记的特殊数据包后,向 UE发送 SGW下发的用户数据 包,即向 UE转发 S1口数据包。可见通过本实施例提供的技术方案, 目标 eNB 不需要等待定时器超时才转发 SI 口数据包, 提高了在 X2切换过程中转发用 户数据包的效率。 实施例三
本实施例主要介绍在 X2切换流程的切换完成阶段(具体 X2切换流程阶 段的划分同背景技术 ), 目标 eNB通过接收源 eNB构造的携带末尾标记的用 户数据包或特殊数据包, 确定向用户转发 SGW 下发的用户数据包(即发送 S1口数据包) 的时机。 如图 4所示, 本实施例的具体步骤包括:
步骤 401 , SGW进行路径切换
步骤 402 , 目标 eNB接收 SGW下发的用户数据包。
步骤 403 , 源 eNB接收目标 eNB发送的释放资源信息后, 判断发送数据 緩冲区中是否有向目标 eNB发送的用户数据包, 如果有, 执行步骤 404 , 否 则, 执行步骤 405。
步骤 404 , 源 eNB在用户数据包中的最后一个用户数据包上添加末尾标 记, 并向目标 eNB发送携带末尾标记的用户数据包; 执行步骤 406。
步骤 405 , 源 eNB构造包含结束标记的特殊数据包, 向目标 eNB发送该 包含结束标记的特殊数据包, 执行步骤 407。
该包含结束标记的特殊数据包携带源 eNB 下一个准备发送的数据包的 PDCP序列号。 源 eNB根据发送数据緩冲区可知道已经发送的用户数据包数 据的 PDCP序列号, 该序列号加 1 , 就是源 eNB下一个准备发送的用户数据 包的 PDCP的序列号。
在构造包含结束标记的特殊数据包的时候, 可以对数据包的包头的某个 字节进行设置, 使该特殊数据包具有指示发送结束的功能, 即表明该特殊数 据包为当前发送数据包中最后一个数据包。 该特殊数据包的结构同实施例一, 此处不再赘述。 包含结束标记的特殊数据包没有携带用户数据, 目标 eNB接 收到该包含结束标记的特殊数据包后, 不会向 UE发送。
步骤 406, 目标 eNB确定接收到携带末尾标记的用户数据包, 向 UE发 送该携带末尾标记的用户数据包, 执行步骤 408。
步骤 407, 目标 eNB确定接收到上述包含结束标记的特殊数据包, 执行 步骤 408。
目标 eNB接收到包含结束标记的特殊数据包,获取该数据包携带的 PDCP 序列号; 目标 eNB在发送 S1口第一个用户数据包前,根据该 PDCP序列号计 算准备向 UE发送的用户数据包 PDCP序列号, 从而保证 UE接收到的 PDCP 号是连续的。
步骤 408, 目标 eNB向 UE发送 S1口数据包。
从以上技术方案可以看出, 源 eNB通过判断发送数据緩冲区是否有需要 发送给目标 eNB的用户数据包, 构造携带末尾标记的用户数据包或包含结束 标记的特殊数据包发送给目标 eNB , 通知目标 eNB此次 X2口数据包已经发 送结束; 目标 eNB向 UE发送 S1口用户数据包。通过本实施例提供的技术方 案, 使目标 eNB不需要等待定时器超时才发送 S1口数据包, 提高了在 X2切 换过程中转发用户数据包的效率。 实施例四
本实施例提供一种长期演进网络, 该网络包括: 源 eNB、 目标 eNB、 UE 和 SGW。
目标 eNB接收 SGW发送的切换完成应答信息后, 如果接收到源 eNB发 送的包含结束标记的特殊数据包, 则向 UE发送 S1口的用户数据包。 如图 12所示, 上述目标 eNB进一步包括: 用户数据包接收单元 1210、 特殊数据包判断单元 1220和用户数据包发送单元 1230。用户数据包接收单元 1210接收用户面处理网关下发的用户数据包; 特殊数据包判断单元 1220在 eNB接收 SGW发送的切换完成应答信息后,判断是否接收到包含结束标记的 特殊数据包, 如果是, 产生接收到特殊数据包的结果; 用户数据包发送单元 1230在特殊数据包判断单元产生接收到特殊数据包的结果时, 向 UE发送用 户数据包接收单元接收的 S1口用户数据包。
上述目标 eNB接收到的包含结束标记的特殊数据包可以由 SGW构造, 也可以由源 eNB构造。 在构造包含结束标记的特殊数据包的时候, 可以对数 据包的包头的某个字节进行设置, 使该特殊数据包具有指示发送结束的功能, 即表明该特殊数据包为当前发送数据包中最后一个数据包。 该特殊数据包的 结构同实施例一, 此处不再赘述。 包含结束标记的特殊数据包没有携带用户 数据, 目标 eNB接收到该包含结束标记的特殊数据包后, 不会向 UE发送。
下面分别介绍由 SGW和源 eNB构造上述特殊数据包的情况:
( 1 ) 由 SGW构造;
在 X2切换的结束阶段, SGW进行路径切换后, 构造包含结束标记的特 殊数据包, 向源 eNB发送该包含结束标记的特殊数据包; 源 eNB接收 SGW 发送的包含结束标记的特殊数据包, 向目标 eNB转发该包含结束标记的特殊 数据包。 目标 eNB在接收到该包含结束标记的特殊数据包后, 开始向 UE发 送 S1口数据包。
( 2 ) 由源 eNB构造;
源 eNB接收目标 eNB发送的释放资源信息后,如果确定发送数据緩冲区 没有向目标 eNB发送的用户数据包, 则构造包含结束标记的特殊数据包, 并 向目标 eNB发送包含结束标记的特殊数据包。 目标 eNB在接收到该包含结束 标记的特殊数据包后, 开始向 UE发送 S1口数据包。
如果源 eNB确定发送数据緩冲区有向目标 eNB发送的用户数据包,可以 在向目标 eNB发送的最后一个用户数据包上添加末尾标记, 向目标 eNB发送 携带末尾标记的用户数据包, 目标 eNB在接收到该携带末尾标记的用户数据 包后,向 UE发送该携带末尾标记的用户数据包, 然后开始发送 S1口数据包。
上述由 eNB构造包含结束标记的特殊数据包的情况,还包括另一种情况: SGW构造包含一个包含结束标记的特殊数据包通知源 eNB由 SGW下发 给源 eNB的 S1 口数据包发送完毕, 源 eNB接收到该特殊数据包后, 重新构 造一个包含结束标记的特殊数据包, 这个重新构造的包含结束标记的特殊数 据包携带源 eNB下一个准备发送的用户数据包的 PDCP序列号。 目标 eNB在 接收到该重新构造的包含结束标记的特殊数据包后,向 UE发送该携带末尾标 记的用户数据包, 然后开始发送 S1口数据包。
源 eNB 根据发送数据緩冲区可知道已发送的最后一个用户数据包的 PDCP序列号, 该序列号加 1 , 就是源 eNB下一个准备发送的数据包的 PDCP 的序列号。 目标 eNB接收到包含结束标记的特殊数据包, 获取该数据包携带 的 PDCP序列号; 目标 eNB在发送 S1口第一个用户数据包前, 根据该 PDCP 序列号计算准备向 UE发送的用户数据包 PDCP序列号,从而保证 UE接收到 的 PDCP号是连续的。 实施例五
本实施例提供的数据转发方法, 是在 X2切换过程中, 目标 eNB根据源 eNB 下一个准备发送的用户数据包的分组域隧道协议用户面 ( GPRS Tunnelling Protocol User , GTP U )序列号和 SGW发送的第一个用户数据包 的 GTP— U序列号确定源 eNB的 X2口数据包何时发送完毕, 并开始向 UE发 送 S1口数据包。如图 5所示,为本实施例提供的数据转发方法的简化流程图。
步骤 501 , 在 X2切换预备阶段, 源 eNB在接收目标 eNB发送的切换请 求应答信息后, 获取源 eNB下一个准备发送的用户数据包的分组域隧道协议 用户面 ( GPRS Tunnelling Protocol User , GTP U )序列号, 向目标 eNB发送 上述源 eNB下一个准备发送用户数据包的 GTP— U序列号。
在 X2切换预备阶段, 源 eNB在接收目标 eNB发送的切换请求应答信息 后, 停止向 UE发送用户数据包。 SGW使用分组域隧道协议 (GPRS Tunnelling Protocol , GTP)向源 eNB下发用户数据包, 用户数据包携带 GTP_U序列号, SGW发送的用户数据包携带的 GTP— U序列号是连续的, 一般为连续递增。 源 eNB根据发送数据緩冲区可知道已发送的最后一个用户数据包的 PDCP序 列号, 该序列号加 1 , 就是源 eNB下一个准备发送的用户数据包的 PDCP的 序列号。
需要说明的是, 上述源 eNB向目标 eNB发送源 eNB下一个准备发送的 用户数据包的 GTP— U序列号, 可以使用以下两种方式: 一种是在控制面上构 造携带源 eNB下一个准备发送的用户数据包的 GTP— U序列号和 PDCP序列 号的消息, 向目标 eNB发送该消息, 比如, 发送携带源 eNB下一个准备发送 的用户数据包的 GTP— U序列号和 PDCP序列号的切换提交信息( ho commit ); 另一种可以结合前述实施例一中由源 eNB构造特殊数据包的方法, 源 eNB接 收到目标 eNB发送的切换请求应答消息后,停止向用户设备发送用户数据包, 在用户面上构造携带源 eNB下一个准备发送的用户数据包的 GTP— U序列号 和 PDCP序列号的特殊数据包,并将该特殊数据包作为目标 eNB向源 eNB发 送的第一个数据包向所述源 eNB发送, 特殊数据包没有携带用户数据, 目标 eNB接收到该特殊数据包后, 不会向 UE发送。
步骤 502 , 目标 eNB获取源 eNB下一个准备发送的用户数据包的 GTP— U 序列号和 SGW发送的第一个用户数据包的 GTP— U序列号。
在 X2切换完成阶段, SGW进行路径切换后, 向目标 eNB发送用户数据 包。 目标 eNB获取 SGW发送的第一个用户数据包的 GTP— U序列号。 SGW 在路径切换时, 保持 GTP— U序列号的连续性。 具体做法可以是, SGW收到 目标 eNB 的切换完成消息后, 进行路径切换, 根据切换前的路径的 GTP— U 序列号, 设定切换后的路径的 GTP— U序列号, 使得 GTP— U序列号连续。
步骤 503 , X2切换结束阶段, 目标 eNB接收核心网设备发送的切换完成 应答信息后, 根据上述源 eNB下一个准备发送的用户数据包的 GTP— U序列 号和上述 SGW发送的第一个用户数据包的 GTP— U序列号,确定源 eNB发送 给目标 eNB的用户数据包(即 X2口数据包)已经发送完毕, 目标 eNB向 UE 发送 SGW下发的用户数据包(即 S1口数据包)。
根据源 eNB下一个准备发送的用户数据包的 GTP— U序列号和 SGW发送 的第一个用户数据包的 GTP— U序列号, 确定源 eNB发送给目标 eNB的用户 数据包(即 X2口数据包) 已经发送完毕的方法有很多种, 以下列举其中的三 种。
( 1 )根据源 eNB下一个准备发送的用户数据包的 GTP— U序列号和 SGW 发送的第一个用户数据包的 GTP— U序列号, 获取源 eNB在切换阶段向目标 eNB发送的用户数据包的全部 GTP— U序列号, 如果接收到全部 GTP— U序列 号对应的用户数据包, 则确定源 eNB发送给目标 eNB的用户数据包(即 X2 口数据包) 已经发送完毕。
比如, 源 eNB 发送的下一个准备发送用户数据包的 GTP— U序列号为 1000, SGW发送的第一个用户数据包的 GTP— U序列号为 1000, 那么, 此次 接口转换中, 说明没有 X2口的转发数据, 目标 eNB直接向 UE发送从 S1口 数据包。
比如, 源 eNB 发送的下一个准备发送用户数据包的 GTP— U序列号为 1000, SGW发送的第一个用户数据包的 GTP— U序列号为 1051 , 那么, 此次 X2切换中, 源 eNB发送给目标 eNB的用户数据包的 GTP— U序列号为 1000 至 1050。 目标 eNB可以有多种方法来确定源 eNB转发的用户数据包是否发 送完毕。 这里举一个例子, 目标 eNB可以把这段计算出来 1000至 1050 的 GTP U序列号保存到数据库, 当目标 eNB从 X2口接收到用户数据包时, 目 标 eNB获取该用户数据包的 GTP— U序列号,并在向 UE发送该用户数据包时, 在上述记录 GTP—U序列号数据库中删除该序列号;当数据库的序列号为 0时, 说明源 eNB需要通过 X2口转发的用户数据包已经发完, 目标 eNB向 UE发 送了全部源 eNB发送的用户数据包。 再例如, 从 X2口接收到用户数据包时, 目标 eNB获取用户数据包的 GTP— U序列号, 在向 UE发送该用户数据包时, 把获取的用户数据包的 GTP— U序列号保存为另一个数据库; 当获取用户数据 包的 GTP— U序列号数据库和第一个保存 GTP— U序列号数段的数据库记录相 同的时候,说明源 eNB需要通过 X2口转发的用户数据包已经发完, 目标 eNB 向 UE发送了全部源 eNB发送的用户数据包。
( 2 )根据源 eNB下一个准备发送用户数据包的 GTP— U序列号和第一个 用户数据包的 GTP— U序列号, 获取源 eNB在切换阶段向目标 eNB发送的用 户数据包的最大 GTP— U序列号, 如果接收到最大 GTP— U序列号对应的用户 数据包, 确定源 eNB结束发送用户数据包。
比如, 源 eNB 发送的下一个准备发送用户数据包的 GTP— U序列号为 1000, SGW发送的第一个用户数据包的 GTP— U序列号为 1051 , 那么, 此次 X2切换中, 源 eNB通过 X2口向目标 eNB转发的用户数据包最大的 GTP— U 序列号为 1050, 如果从 X2口接收到 GTP— U序列号为 1050的用户数据包, 确定源 eNB结束发送用户数据包。
( 3 )判断当源 eNB下一个准备发送用户数据包的 GTP— U序列号大于或 等于所述 SGW发送的第一个用户数据包的 GTP— U序列号,则确定源 eNB向 所述目标 eNB发送的用户数据包已发送完毕。 当源 eNB下一个准备发送用户 数据包的 GTP— U序列号小于所述 SGW发送的第一个用户数据包的 GTP— U 序列号, 则确定源 eNB向所述目标 eNB发送的用户数据包尚未发送完毕, 继 续向 UE发送源 eNB发送的 X2口数据包, 直到源 eNB下一个准备发送用户 数据包的 GTP— U序列号等于所述 SGW发送的第一个用户数据包的 GTP— U 序列号,说明没有从源 eNB转发过来的数据,则开始向 UE发送所 SGW向目 标 eNB下发的 S1口数据包。
需要指出的是, 上述技术方案中, 源 eNB可以不向目标 eNB发送下一个 准备发送用户数据包的 GTP— U序列号, 而是发送 X2切换预备阶段源 eNB向 UE下发的最后一个用户数据包的 GTP— U序列号, 因为用户数据包的 GTP— U 序列号是连续的, 所以目标 eNB也可以根据上述源 eNB向 UE下发的最后一 个用户数据包的 GTP— U序列号和 SGW发送的第一个用户数据包的 GTP— U 序列号, 可以确定源 eNB结束发送用户数据包。 从以上技术方案可以看出, 源 eNB向目标 eNB发送源 eNB发送的下一 个准备发送用户数据包的 GTP— U序列号, 目标 eNB根据源 eNB发送的下一 个准备发送用户数据包的 GTP— U序列号和 SGW发送的第一个用户数据包的 GTP— U序列号,可以确定源 eNB结束发送用户数据包,然后向 UE发送 SGW 下发的用户数据包; 目标 eNB不需要等待定时器超时才发送 S1口数据包,提 高了在 X2切换过程中转发用户数据包的效率。 实施例六
本实施例提供的数据转发方法也是目标 eNB根据源 eNB下一个准备发送 的用户数据包的 GTP— U序列号和 SGW发送的第一个用户数据包的 GTP— U 序列号确定源 eNB的 X2口数据包何时发送完毕, 并开始向 UE发送 S1口数 据包。 但与实施例五不同之处在于, 本实施例中 eNB是通过 UE发送的 UE 下一个准备接收的用户数据包的 PDCP序列号获得的源 eNB下一个准备发送 用户数据包的 GTP— U序列号。 请参考图 6, 为本发明实施例六的数据转发方 法流程图。
步骤 601 , 在 X2切换执行阶段, UE向目标 eNB发送 UE下一个准备接 收的用户数据包的 PDCP序列号。
在 X2切换执行阶段, UE向目标 eNB发送切换确认信息时, 把 UE下一 个准备接收的用户数据包的 PDCP序列号添加到切换确认信息中;向目标 eNB 发送携带下一个准备接收用户数据包的 PDCP序列号的切换确认信息。 下一 个准备接收用户数据包的 PDCP序列号指, UE根据在 X2切换预备阶段从源 eNB接收到的最后一个用户数据包的 PDCP序列号, 计算得到即将接收的下 一个户数据包的 PDCP序号。
步骤 602, 目标 eNB获取源 eNB下一个准备发送用户数据包的 GTP— U 序列号和 SGW发送的第一个用户数据包的 GTP— U序列号。
目标 eNB获取 UE下一个准备接收用户数据包的 PDCP序列号, 如果接 收到源 eNB发送的携带上述 PDCP序列号的用户数据包, 获取该用户数据包 携带的 GTP— U序列号, 把获取的 GTP— U序列号作为源 eNB在接收切换请求 应答信息后的目标 eNB下一个准备发送用户数据包的 GTP— U序列号。 或者 根据实例五中的方法, 通过控制面信令获得 GTP— U序列号, 在控制面上构造 携带源 eNB下一个准备发送的用户数据包的 GTP— U序列号和 PDCP序列号 的消息, 向目标 eNB发送该消息。
SGW在路径切换时, 要保持 GTP— U序列号的连续性。 具体做法可以是, SGW 收到 eNB 切换完成的消息后, 进行路径切换, 根据切换前的路径的 GTP U序列号, 设定切换后的路径的 GTP_U序列号, 使得 GTP U序列号连 续。
步骤 603 , X2切换结束阶段, 目标 eNB接收 SGW发送的切换完成应答 信息后,根据源 eNB下一个准备发送用户数据包的 GTP— U序列号和 SGW发 送的第一个用户数据包的 GTP— U序列号, 确定源 eNB发送给目标 eNB的用 户数据包(即 X2口数据包) 已经发送完毕, 目标 eNB向 UE发送 SGW下发 的用户数据包(即 S1口数据包)。
上述根据源 eNB下一个准备发送用户数据包的 GTP— U序列号和 SGW发 送的第一个用户数据包的 GTP— U序列号, 确定源 eNB发送给目标 eNB的用 户数据包(即 X2口数据包) 已经发送完毕的方法同实施例五中的方法, 此处 不再赘述。
从以上技术方案可以看出, UE根据在 X2切换预备阶段从源 eNB接收到 的最后一个用户数据包的 PDCP序列号, 获取下一个准备接收用户数据包的 PDCP序列号, 并向目标 eNB发送; 目标 eNB如果接收到源 eNB发送的携带 该下一个准备接收用户数据包的 PDCP序列号的用户数据包, 获取用户数据 包携带的 GTP— U序列号, 或者源 eNB通过 X2控制信令, 告诉目标 eNB下 一个应该发送的 GTP— U序列号,目标 eNB把获取的 GTP U序列号作为源 eNB 在接收切换请求应答信息后的下一个准备发送用户数据包的 GTP— U序列号; 目标 eNB通过该第一个发送用户数据包的 GTP— U序列号和 SGW发送的第一 个用户数据包的 GTP— U序列号, 确定源 eNB接收发送用户数据包, 然后向 UE发送 SGW下发的用户数据包; 目标 eNB不需要等待定时器超时才发送 S1口数据包, 提高了在 X2切换过程中转发用户数据包的效率。 实施例七
本实施例提供一种长期演进网络包括: 源 eNB , 目标 eNB和 SGW。 源 eNB在接收切换请求应答信息后, 获取下一个准备发送用户数据包的 GTP U序列号, 向目标 eNB发送携带源 eNB在接收切换请求应答信息后的 下一个准备发送用户数据包的 GTP— U序列号的信息; 目标 eNB获取源 eNB 下一个准备发送用户数据包的 GTP— U序列号和 SGW发送的第一个用户数据 包的 GTP— U序列号; 在 eNB间不涉及核心网的切换结束阶段, 接收核心网 设备发送的切换完成应答信息后, 根据源 eNB下一个准备发送用户数据包的 GTP— U序列号和第一个用户数据包的 GTP— U序列号, 确定源 eNB结束发送 用户数据包, 向 UE发送 SGW下发的用户数据包。
其中, 如图 13所示, 目标 eNB包括: 下一个序列号获取单元 1310, 用 于获取源 eNB 在接收切换请求应答信息后的下一个准备发送用户数据包的 GTP— U序列号; 第一个序列号获取单元 1320, 用于获取 SGW发送的第一个 用户数据包的 GTP— U序列号; 发送结束判断单元 1330, 用于在 eNB间不涉 及核心网的切换结束阶段, eNB接收核心网设备发送的切换完成应答信息后, 根据下一个序列号获取单元获取的下一个准备发送用户数据包的 GTP— U序列 号和笫一个序列号获取单元获取的笫一个用户数据包的 GTP— U序列号, 判断 源 eNB是否结束发送用户数据包, 如果是, 产生源 eNB结束发送用户数据包 的结果; 数据包发送单元 1340, 用于发送结束判断单元产生源 eNB结束发送 用户数据包的结果时, 向 UE发送 SGW下发的用户数据包。
上述目标 eNB获取源 eNB下一个准备发送用户数据包的 GTP— U序列号 的方法可以是: 源 eNB将下一个准备发送用户数据包的 GTP— U序列号携带 在发送给目标 eNB的一个消息中。 也可以是下述方法:
UE目标 eNB发送下一个准备接收用户数据包的 PDCP序列号;目标 eNB 获取 UE发送的下一个准备接收用户数据包的 PDCP序列号, 如果目标 eNB 接收到源 eNB发送携带上述 PDCP序列号的用户数据包, 则获取用户数据包 携带的 GTP— U序列号, 并把获取的 GTP— U序列号作为源 eNB下一个准备发 送用户数据包的 GTP— U序列号。 实施例八
SGW使用 GTP协议向 eNB下发用户数据包,用户数据包携带 GTP— U序 列号, SGW发送的用户数据包携带的 GTP— U序列号是连续的, 一般为连续 递增。 eNB可以根据 GTP— U序列号的连续性对 SGW发送的用户数据包进行 校验。
在 SGW重定位阶段, 现有技术中, 目标 SGW (重定位后的 SGW )无法 获知源 SGW (重定位前的 SGW ) 的下一个准备发送的用户数据包的 GTP— U 序列号, 导致 SGW重定位完成时, 目标 SGW向 eNB发送的第一用户数据包 的 GTP— U序列号与源 SGW向 eNB发送的最后一个用户数据包的 GTP— U序 列号不连续。源 SGW下一个准备发送用户数据包的 GTP— U序列号指,在 SGW 重定位阶段,源 SGW向 eNB发送最后一个用户数据包后, 准备发送的下一个 用户数据包的 GTP— U序列号。
本实施例提供的技术方案是: MME从源 SGW获取该源 SGW下一个准 备发送用户数据包的 GTP— U序列号, MME向目标 SGW发送该源 SGW下一 个准备发送用户数据包的 GTP— U序列号; 目标 SGW把上述下一个准备发送 用户数据包的 GTP— U序列号作为向 eNB发送的第一个用户数据包的 GTP— U 序列号。 SGW重定位完成后, 目标 SGW将向 eNB发送携带该 GTP— U序列 号的第一个用户数据包。 这样就可以保持 eNB发送的数据包 GTP— U序列号 的连续性。
下面的实施例将结合附图详细介绍几种目标 SGW获得源 SGW下一个准 备发送的用户数据包 GTP— U序列号的方法:
( 1 )在 eNB从源 SGW向目标 SGW切换的过程中, 如图 7a所示, 步骤 7al , eNB切换完毕向 MME发送切换完毕消息 ( Ho complete ); 步骤 7a2 , MME收到 Ho complete消息向源 SGW发送数据请求消息( Data req )要源 SGW下一个准备发送的数据包的 GTP— U序列号;
步骤 7a3 , 源 SGW通过数据请求响应消息( Data req ack )将源 SGW下 一个准备发送的数据包的 GTP— U序列号发送给 MME;
步骤 7a4 , MME通过控制面的切换完成响应消息 (Ho complete ack )将 源 SGW下一个准备发送的数据包的 GTP— U序列号发送给 eNB , 使 SGW之 间的 GTP— U序列号有对应关系, 达到连续的目的。
例如: 目标 eNB将收到这个 GTP— U序列号作为偏移量和目标 SGW下发 下来的第一个数据包的 GTP— U序列号相加, 与源 eNB 转发过来数据包的 GTP— U序列号比较, 判断 X2 口的转发数据是否发送结束。 如果前者大于等 于后者, 说明 X2口没有转发的数据, 目标 eNB直接向 UE发送 SGW下来的 数据, 如果前者小于后者, 认为有 X2 口转发的数据, 目标 eNB给 UE转发 X2口的数据完后再给 UE下发 SWG过来的数据。
( 2 ) 同样在 eNB从源 SGW向目标 SGW切换的过程中, 如图 7b所示, 步骤 7bl-7b3同上述步骤 7al-7a3 , 此处不再赘述,
步骤 7b4 , MME通过承载建立请求消息( Create bearer req )消息将源 SGW 下一个准备发送的数据包的 GTP— U序列号发送给目标 SGW。
( 3 )在非切换过程中, 由 MME发起选择目标 SGW。 如图 7c所示: 步骤 7cl , MME向源 SGW发送数据请求消息 (Data req )要源 SGW下 一个发送的数据包的 GTP— U序列号;
步骤 7c2 , SGW通过数据请求响应消息 (Data req ack )把源 SGW下一 个发送的数据包的 GTP— U序列号发送给 MME;
步骤 7c3 , MME通过 Create bearer req消息告诉目标 SGW上述源 SGW 下一个准备发送的数据包的 GTP— U序列号。
( 4 )在非切换过程中, 也可以由源 SGW发起选择目标 SGW。 如图 7d 所示: 步骤 7dl-7d3同上述步骤 7cl-7c3 , 在步骤 7dl之前进一步包括: 步骤 7d0: 源 SGW向 MME发送 SGW重定向请求;
MME在收到上述重定向请求后, 开始执行步骤 7dl。
从以上的技术方案可以看出, 在 SGW重定向阶段, MME获取源 SGW 发送获取下一个准备发送的用户数据包的 GTP— U序列号,将该下一个准备发 送用户数据包的 GTP— U序列号发送给目标 SGW,目标 SGW把下一个准备发 送用户数据包的 GTP—U序列号作为自身发送的第一个用户数据包的 GTP— U 序列号; 或者 MME获取源 SGW发送获取下一个准备发送的用户数据包的 GTP— U序列号, 将该下一个准备发送用户数据包的 GTP— U序列号发送给 e B,使 SGW之间的 GTP— U序列号有对应关系;从而实现在 SGW重定位完 成后, 目标 SGW向 eNB发送的第一用户数据包的 GTP— U序列号与源 SGW 向 eNB发送的最后一个用户数据包的 GTP_U序列号是连续的。 实施例九
本实施例的长期演进网络包括: MME, 用于在 SGW重定位阶段, 向源 SGW发送获取下一个准备发送用户数据包的 GTP— U序列号的请求信息; 向 目标 SGW发送从源 SGW接收到的下一个准备发送用户数据包的 GTP— U序 列号;或者,向 eNB发送所述源 SGW下一个准备发送的用户数据包的 GTP— U 序列号,使源 SGW和目标 SGW之间的 GTP— U序列号有对应关系。源 SGW, 用于接收 MME发送的获取下一个准备发送用户数据包的 GTP— U序列号的请 求信息, 向 MME发送下一个准备发送用户数据包的 GTP— U序列号; 目标 SGW, 用于接收 MME发送的下一个准备发送用户数据包的 GTP— U序列号, 把下一个准备发送用户数据包的 GTP— U序列号作为第一个用户数据包的 GTP— U序列号。
其中, 如图 14所示, MME包括: 请求信息发送单元 1410, 用于在 SGW 重定位阶段, 向源 SGW发送获取下一个准备发送用户数据包的 GTP— U序列 号的请求信息; 序列号接收单元 1420, 用于接收源 SGW发送的下一个准备 发送用户数据包的 GTP— U序列号; 序列号发送单元 1430, 用于向目标 SGW 发送序列号接收单元接收的下一个准备发送用户数据包的 GTP— U序列号; 或 者用于向 eNB发送所述源 SGW下一个准备发送的用户数据包的 GTP— U序列 号, 使源 SGW和目标 SGW之间的 GTP— U序列号有对应关系。 实施例十
如图 8所示, 本实施例提供的一种数据转发的方法具体包括以下步骤: 步骤 801 , 在 X2切换预备阶段, 源 eNB接收目标 eNB发送的切换请求 应答信息后, 向 SGW发送停止向源 eNB发送用户数据包的请求信息。 在接 收目标 eNB发送的该请求应答信息之前, SGW向源 eNB发送用户数据包, 源 eNB向 UE发送 SGW下发的用户数据包。可以理解的是,在具体实施方案 的时候, 源 eNB向 SGW发送请求信息的时机也可以为: 源 eNB向 UE发送 切换命令信息后, 向 SGW发送停止向源 eNB发送用户数据包的请求信息。
步骤 802, SGW接收到该停止向源 eNB发送用户数据包的请求信息后, 停止向源 eNB发送用户数据包。 如图九的步骤 6a或者 7a, 这两个时机可任 选一个。
步骤 803 , 在 X2切换完成阶段, SGW进行路径切换后, 向目标 eNB发 送用户数据包。
步骤 804, 目标 eNB接收 SGW发送的切换完成应答信息后, 开始向 UE 发送 SGW下发的用户数据包。
进一步,考虑到在 X2切换执行阶段,可能发生 UE无法与目标 eNB进行 同步等原因导致 X2切换失败的特殊情况, 在上述实施例的基础上, 进一步增 加以下步骤: 在 X2切换执行阶段, 源 eNB确定 X2切换失败而恢复源 eNB 的连接后, 向 SGW发送恢复向源 eNB发送用户数据包的请求信息; SGW接 收该恢复向源 eNB发送用户数据包的请求信息后,恢复向源 eNB发送用户数 据包。 如图九的步骤 9。
请参考图九, 为本发明实施例十的 X2切换失败源 eNB恢复 S1口数据包 流程图, 包括以下步骤:
步骤 1 ~步骤 5同于背景技术的步骤 1 ~步骤 5 , 在此不再赘述; 步骤 6, 目标 eNB向源 eNB发送切换请求应答信息, 源 eNB向核心网设 备发送携带停止向源 eNB发送用户数据包的请求信息的切换通知信息;
步骤 7 , 源 eNB向 UE发送切换命令信息;
步骤 8, UE向源 eNB发送恢复到源 eNB的信息;
步骤 9, 源 eNB确定切换失败后, UE恢复与源 eNB的连接, 源 eNB向 SGW发送恢复向源 eNB发送用户数据包的请求信息; SGW接收该恢复向源 eNB发送用户数据包的请求信息后, 恢复向源 eNB发送用户数据包。
从以上技术方案可以看出, 在 X2切换预备阶段, 源 eNB接收目标 eNB 发送的切换请求应答信息后, 向 SGW发送停止向源 eNB发送用户数据包的 请求信息, SGW接收该请求信息后, 停止向源 eNB发送用户数据包; 在 X2 切换执行阶段, 源 eNB不会通过 X2口向目标 eNB转发用户数据包; 在 X2 切换完成阶段, 目标 eNB接收 SGW发送的切换完成应答信息后, 开始向 UE 发送 SGW下发的用户数据包; 目标 eNB不需要等待定时器超时才发送 S1口 数据包, 提高了在 X2切换过程中转发用户数据包的效率。
从以上技术方案可以看出, 在 X2切换执行阶段, eNB确定 X2切换失败 后, 向 SGW发送恢复向源 eNB发送用户数据包的请求信息, SGW接收到该 请求信息后恢复向源 eNB发送用户数据包; 从而实现在 X2切换失败时, 网 络恢复到 X2切换前的状态, 保证网络正常运行。 实施例十一
本实施例提供的数据转发方法, 是在 X2切换预备阶段 (具体的切换流程 阶段划分同背景技术),源 eNB向 UE发送切换命令信息( Handover Command ) 后, 源 eNB和 UE断开连接, 源 eNB需要通过 X2口进行数据转发, 此时, 源 eNB向目标 eNB发送控制面消息, 该控制面消息中携带目标 eNB应该进 行编号的第一个用户数据包的 PDCP序列号和 GTP— U序列号, 目标 eNB根 据上述的 GTP— U序列号和 SGW发送的第一个用户数据包的 GTP— U序列号 确定源 eNB的 X2口数据包何时发送完毕, 并开始向 UE发送 S1口数据包。 如图 11所示, 本实施例具体步骤如下:
步骤 1101 , 源 eNB向 UE发送切换命令信息( Handover Command )后, 获知与 UE断开连接, 源 eNB向目标 eNB发送控制面消息, 例如切换确认消 息(Ho commit ), 如图 10中 7a消息所示, 因为该图中其它流程步骤同背景 技术流程图, 此处不再赘述。 该控制面消息中携带目标 eNB应该进行编号的 第一个用户数据包的 PDCP序列号和 GTP— U序列号。
上述目标 eNB应该进行编号的第一个用户数据包的 PDCP序列号是: 源 eNB从 PDCP层已向下层发送的最后一个用户数据包的 PDCP序列号加 1 ,上 述源 eNB下一个准备发送的用户数据包的 GTP— U序列号是:源 eNB从 PDCP 层已向下层发送的最后一个用户数据包的 GTP— U序列号加 1。
步骤 1102, 源 eNB向目标 eNB转发用户数据包。
源 eNB向目标 eNB转发的用户数据包分为两种:
( 1 )经过 PDCP层处理过的用户数据包。 源 eNB通过 X2口发送该用户 数据包时自身携带 PDCP序列号。 在这种情况下, 源 eNB根据下层是否收到 UE的接收应答, 选择性地向目标 eNB发送用户数据包。 例如在切换前, 源 eNB直接向 UE发送用户数据包 1、 2、 3和 4, UE只接收到用户数据包 1和 4,并 UE向源 eNB发送用户数据包 1和 4的接收应答,那么在切换后,源 eNB 根据接收应答, 只向目标 eNB转发用户数据包 2和 3。
( 2 )没有经过 PDCP层处理过的用户数据包。 源 eNb通过 X2口发送该 用户数据包时自身不携带 PDCP序列号。
所以源 eNb通过 X2口向目标 eNb转发的数据, 包括上述 2种用户数据 包组合的三种情况, 即只包括一种数据包的两种情况, 和同时包括两种数据 包的一种情况。
例如, 源 eNB向目标 eNB发送了 PDCP序列号分别为 1、 3的两个用户 数据包, 即说明这两个数据包经过了 PDCP层处理了, 有 PDCP序列号。 源 eNB向目标 eNB发送控制面消息 (如 Ho commit消息), 该控制面消息中携 带值为 4的 PDCP序列号, GTP U序列号为 5。那么,目标 eNB在接收到 PDCP 序列号分别为 1、 3的用户数据包后, 接到上述控制面消息时, 就给下一个给 UE发送的数据包进行 PDCP编号为 4。
步骤 1103 , 目标 eNB根据控制面消息(如 Ho commit )携带的源 eNB下 一个准备发送的用户数据包的 GTP— U序列号判断 X2口数据包(即源 eNB向 目标 eNB通过 X2 口转发的数据)是否发送完毕, 如果没有发送完毕, 继续 向 UE发送 X2口数据包, 如果发送完毕, 开始向 UE发送 S1口数据包。
本步骤中判断 X2 口数据包是否发送完毕的方法可以为: 目标 eNB获取 SGW向目标 eNB发送的第一个 S1 口数据包的 GTP— U序列号, 并将其与控 制面消息中的 GTP— U序列号进行比较。 当上述控制面消息 (Ho commit)中的 GTP U序列号小于上述 SGW向目标 eNB发送的第一个 S1口数据包的 GTP— U 序列号时, 说明源 eNB还有向目标 eNB发送的 X2口数据包, 并且可以通过 上述两个 GTP— U序列号的差值获知还有几个 X2口数据包待发送,则目标 eNB 向 UE发送 X2口数据包, 对于没有 PDCP序列号的数据包, 根据该控制面消 息中的 PDCP SN进行编号, 如果有 PDCP序列号, 沿用该序列号, 向 UE发 送该数据包。当上述控制面消息(Ho commit )中 GTP— U序列号等于上述 SGW 向目标 eNB发送的第一个 S1口数据包的 GTP— U序列号时,说明源 eNB已没 有向目标 eNB发送的 X2口数据包,则目标 eNB开始向 UE发送 S1口的用户 数据包。 对于没有 X2口的数据包时, 根据该控制面消息中的 PDCP SN进行 编号,对于转发完 X2口的数据包时,接着 PDCP的序列号进行数据包的编号。
另外, 本步骤中的判断方法还可以使用本发明实施例五中类似的方法, 此处不再赘述。
本方案要求, SGW在路径切换前后下发的 GTP— U序列号保持连续性, 可以釆用多种方法,例如使用分组数据网处理网关 PDN— GW统一分配 GTP— U 序列号,或者可以类似地使用实施例八中提供的保持 GTP— U序列号连续性的 方法。 上述方案都可以同时在目标 eNB加一个定时器来保证,如果定时器超时, 就直接下发 S1口的数据。
通过以上十一个具体实施例提供的技术方案, 可以使目标 eNB及时获知 源 eNB何时发送完毕 X2口数据包, 开始向 UE发送 S1口数据包, 而不需要 目标 eNB等待定时器超时, 从而提高了 X2切换过程中转发用户数据包的效 率。
以上对本发明所提供的切换过程中数据转发的方法与演进基站和长期演 进网络进行了详细介绍, 对于本领域的一般技术人员, 依据本发明实施例的 思想, 在具体实施方式及应用范围上均会有改变之处, 综上所述, 本说明书 内容不应理解为对本发明的限制。

Claims

权 利 要求 书
1、 一种数据转发的方法, 其特征在于, 在演进基站间不涉及核心网的切换 结束阶段, 包括:
在用户面处理网关 SGW进行路径切换后,目标演进基站 eNB接收所述 SGW 下发的用户数据包;
所述目标 eNB收到源 eNB发送的包含结束标记的特殊数据包,向用户设备 发送所述 SGW下发的用户数据包。
2、 根据权利要求 1所述的方法, 其特征在于, 所述目标 eNB收到源 eNB 发送的包含结束标记的特殊数据包之前, 进一步包括:
所述源 eNB确定发送数据緩冲区中没有需要向所述目标 eNB发送的用户数 据包;
所述源 eNB向所述目标 eNB发送由所述源 eNB构造的包含结束标记的特 殊数据包, 所述包含结束标记的特殊数据包携带源 eNB下一个准备发送的用户 数据包的分组数据汇聚层协议 PDCP序列号。
3、 根据权利要求 1所述的方法, 其特征在于, 所述目标 eNB收到源 eNB 发送的包含结束标记的特殊数据包之前, 进一步包括: 包;
4、 根据权利要求 1所述的方法, 其特征在于, 所述目标 eNB收到源 eNB 发送的包含结束标记的特殊数据包之前, 进一步包括: 包;
所述源 eNB根据所述 SGW发送的包含结束标记的特殊数据包, 向所述目 标 eNB发送由所述源 eNB重新构造的包含结束标记的特殊数据包,所述源 eNB 重新构造的包含结束标记的特殊数据包中携带源 eNB下一个准备发送的用户数 据包的 PDCP序列号。
5、 根据权利要求 1至 4任一项所述的方法, 其特征在于, 所述包含结束标 记的特殊数据包的包头中设置有用于指示用户数据包发送结束的标记。
6、 一种长期演进网络, 包括: 用户设备、 源演进基站 eNB、 目标 eNB和用 户面处理网关 SGW, 其特征在于,
所述目标 eNB, 用于在所述 SGW进行路径切换后, 接收所述 SGW下发的 用户数据包, 并在接收到所述源 eNB发送的包含结束标记的特殊数据包后, 向 所述用户设备发送所述 SGW下发的用户数据包。
7、 根据权利要求 6所述的长期演进网络, 其特征在于,
所述源 eNB , 用于在确定发送数据緩冲区中没有需要向所述目标 eNB发送 的用户数据包时, 向所述目标 eNB发送由所述源 eNB构造的包含结束标记的特 殊数据包, 所述包含结束标记的特殊数据包携带源 eNB下一个准备发送的用户 数据包的 PDCP序列号。
8、 根据权利要求 6所述的长期演进网络, 其特征在于,
所述 SGW, 用于在进行路径切换后, 向所述源 eNB发送由所述 SGW构造 的包含结束标记的特殊数据包; 并向所述目标 eNB转发所述包含结束标记的特殊数据包。
9、 根据权利要求 6所述的长期演进网络, 其特征在于,
所述 SGW, 用于在进行路径切换后, 向所述源 eNB发送由所述 SGW构造 的包含结束标记的特殊数据包; 述目标 eNB发送由所述源 eNB重新构造的包含结束标记的特殊数据包,所述源 eNB重新构造的包含结束标记的特殊数据包中携带源 eNB下一个准备发送的用 户数据包的 PDCP序列号。
10、 根据权利要求 6至 9任一项所述的长期演进网络, 其特征在于, 所述 包含结束标记的特殊数据包的包头中设置有用于指示用户数据包发送结束的标 记。
11、 一种演进基站 eNB, 其特征在于, 包括:
数据包接收单元(1210 ), 用于接收用户面处理网关 SGW下发的用户数据 包;
特殊数据包判断单元( 1220 ), 用于判断是否接收到包含结束标记的特殊数 据包; 和
数据包发送单元( 1230 ), 用于当所述特殊数据包判断单元判断接收到所述 包含结束标记的特殊数据包时, 向用户设备发送所述数据包接收单元接收的所 述 SGW下发的用户数据包。
12、 根据权利要求 11所述的演进基站 eNB, 其特征在于, 所述包含结束标 记的特殊数据包的包头中设置有用于指示用户数据包发送结束的标记。
13、 一种数据转发的方法, 其特征在于, 在演进基站 eNB间不涉及核心网 的切换结束阶段, 包括:
用户面处理网关 SGW进行路径切换;
目标 eNB接收所述 SGW下发的用户数据包;
如果源 eNB确定发送数据緩冲区中有需要向所述目标 eNB发送的用户数据 包,则所述源 eNB在向所述目标 eNB发送的最后一个用户数据包上添加末尾标 记并发送, 目标 eNB接收到所述携带末尾标记的用户数据包, 则在向用户设备 发送所述携带末尾标记的用户数据包后,向所述用户设备发送所述 SGW下发的 用户数据包; 或者
如果源 eNB确定发送数据緩冲区中没有需要向所述目标 eNB发送的用户数 据包, 则所述源 eNB构造包含结束标记的特殊数据包, 并向所述目标 eNB发送 所述包含结束标记的特殊数据包, 目标 eNB接收到所述包含结束标记的特殊数 据包, 向所述用户设备发送所述 SGW下发的用户数据包。
14、 根据权利要求 13所述的方法, 其特征在于, 所述包含结束标记的特殊 数据包携带源 eNB下一个准备发送的用户数据包的 PDCP序列号, 包头中设置 有用于指示用户数据包发送结束的标记。
15、 一种数据转发的方法, 其特征在于, 在演进基站 eNB间不涉及核心网 的切换结束阶段, 包括:
目标 eNB获取源 eNB下一个准备发送的用户数据包的分组域隧道协议用户 面 GTP— U序列号和用户面处理网关 SGW发送的第一个用户数据包的 GTP— U 序列号;
根据所述源 eNB 下一个准备发送的用户数据包的 GTP— U序列号和所述 SGW发送的第一个用户数据包的 GTP— U序列号, 确定所述源 eNB向所述目标 eNB发送的用户数据包已发送完毕;
向用户设备发送所述 SGW下发的用户数据包。
16、根据权利要求 15所述的方法, 其特征在于, 所述获取所述源 eNB下一 个准备发送的用户数据包的 GTP—U序列号, 包括:
所述用户设备向所述目标 eNB发送所述用户设备下一个准备接收的用户数 据包的分组数据汇聚层协议 PDCP序列号;
所述目标 eNB根据所述用户设备下一个准备接收的用户数据包的 PDCP序 列号, 获取对应用户数据包的 GTP— U序列号, 并把所述 GTP— U序列号作为源 eNB下一个准备发送用户数据包的 GTP— U序列号。
17、根据权利要求 15所述的方法, 其特征在于, 所述获取所述源 eNB下一 个准备发送的用户数据包的 GTP— U序列号之前进一步包括:
所述源 eNB接收所述目标 eNB发送的切换请求应答信息;
所述源 eNB向所述目标 eNB发送由所述源 eNB构造的控制面的消息, 所 述消息中携带所述源 eNB 下一个准备发送的用户数据包的 GTP— U序列号和
PDCP序列号。
18、根据权利要求 15所述的方法, 其特征在于, 所述获取所述源 eNB下一 个准备发送的用户数据包的 GTP— U序列号之前进一步包括:
所述源 eNB接收到所述目标 eNB发送的切换请求应答消息;
所述源 eNB停止向用户设备发送用户数据包,将由所述源 eNB构造的用户 面的特殊数据包作为所述源 eNB向所述目标 eNB发送的第一个数据包向所述目 标 eNB发送,所述用户面的特殊数据包中携带源 eNB下一个准备发送的用户数 据包的 GTP— U序列号和 PDCP序列号。
19、 根据权利要求 15至 18所述任一种方法, 其特征在于, 所述确定所述 源 eNB向所述目标 eNB发送的用户数据包已发送完毕, 包括:
当所述源 eNB下一个准备发送用户数据包的 GTP— U序列号大于或等于所 述 SGW发送的第一个用户数据包的 GTP— U序列号,则确定所述源 eNB向所述 目标 eNB发送的用户数据包已发送完毕。
20、 一种长期演进网络, 包括: 用户设备、 用户面处理网关 SGW、 目标演 进基站 eNB和源 eNB, 其特征在于,
所述目标 eNB, 用于获取所述源 eNB下一个准备发送的用户数据包的分组 域隧道协议用户面 GTP— U序列号和所述 SGW发送的第一个用户数据包的 GTP— U序列号, 并根据所述源 eNB下一个准备发送的用户数据包的 GTP— U序 列号和所述 SGW发送的第一个用户数据包的 GTP— U序列号, 确定所述源 eNB 向所述目标 eNB发送的用户数据包已发送完毕, 向用户设备发送所述 SGW下 发的用户数据包。
21、 根据权利要求 20所述的长期演进网络, 其特征在于,
所述用户设备, 用于向所述目标 eNB发送所述用户设备下一个准备接收的 用户数据包的分组数据汇聚层协议 PDCP序列号;
所述目标 eNB , 用于根据所述用户设备下一个准备接收的用户数据包的 PDCP序列号, 获取对应用户数据包的 GTP— U序列号, 并把所述 GTP— U序列 号作为源 eNB下一个准备发送的用户数据包的 GTP— U序列号。
22、 一种演进基站 eNB, 其特征在于, 包括:
下一个序列号获取单元( 1310 ),用于获取源 eNB下一个准备发送用户数据 包的分组域隧道协议用户面 GTP— U序列号;
第一个序列号获取单元( 1320 ), 用于获取用户面处理网关 SGW发送的第 一个用户数据包的 GTP— U序列号;
发送结束判断单元( 1330 ) ,根据所述源 eNB下一个准备发送用户数据包的 GTP— U序列号和所述 SGW发送的第一个用户数据包的 GTP— U序列号,判断所 述源 eNB是否结束发送用户数据包;
数据包发送单元 ( 1340 ), 用于当所述发送结束判断单元 ( 1330 )判断所述 源 eNB结束发送用户数据包时, 向用户设备发送所述用户面处理网关下发的用 户数据包。
23、 一种获取序列号的方法, 其特征在于, 包括:
在用户面处理网关 SGW重定位阶段, 移动管理实体 MME从源 SGW获取 所述源 SGW下一个准备发送的用户数据包的分组域隧道协议用户面 GTP— U序 列号;
所述 MME向目标 SGW发送所述 GTP— U序列号, 所述目标 SGW把所述 GTP— U序列号作为所述目标 SGW第一个用户数据包的 GTP— U序列号; 或者, 所述 MME向演进基站 eNB发送所述源 SGW下一个准备发送的用户数据 包的 GTP— U序列号,使源 SGW和目标 SGW之间的 GTP— U序列号有对应关系。
24、 一种移动管理实体 MME, 其特征在于, 包括:
请求信息发送单元( 1410 ), 用于在用户面处理网关 SGW重定位阶段, 向 源 SGW发送获取下一个准备发送用户数据包的 GTP— U序列号的请求信息; 序列号接收单元( 1420 ), 用于接收源 SGW发送的下一个准备发送用户数 据包的 GTP— U序列号;
序列号发送单元( 1430 ), 用于向目标 SGW发送序列号接收单元接收的所 述源 SGW下一个准备发送用户数据包的 GTP— U序列号; 或者用于向演进基站 eNB发送所述源 SGW下一个准备发送的用户数据包的 GTP— U序列号, 使源 SGW和目标 SGW之间的 GTP— U序列号有对应关系。
25、 一种长期演进网络, 包括: 移动管理实体 MME, 目标用户面处理网关 SGW和源 SGW, 其特征在于,
所述 MME, 用于从所述源 SGW获取所述源 SGW下一个准备发送的用户 数据包的分组域隧道协议用户面 GTP— U序列号, 并向所述目标 SGW发送所述 GTP— U序列号;
所述目标 SGW, 用于接收所述 GTP— U序列号, 并把所述 GTP— U序列号作 为所述目标 SGW第一个用户数据包的 GTP— U序列号。
26、 一种数据转发的方法, 其特征在于, 包括:
在演进基站 eNB间不涉及核心网的切换过程中, 用户面处理网关 SGW接 收源 eNB在收到切换请求应答信息后发送的停止向源 eNB发送用户数据包的请 求信息;
所述 SGW停止向所述源 eNB发送用户数据包;
所述 SGW进行路径切换后, 向所述目标 eNB发送用户数据包;
所述目标 eNB接收所述 SGW发送的切换完成应答信息, 向用户设备发送 所述 SGW下发的用户数据包。
27、 根据权利要求 26所述的方法, 其特征在于, 所述方法进一步包括: 所述源 eNB确定切换失败后,所述源 eNB与用户设备恢复连接,所述源 eNB 向所述 SGW发送恢复向源 eNB发送用户数据包的请求信息;
所述源 eNB接收所述 SGW发送的用户数据包。
28、 一种数据转发的方法, 其特征在于, 所述方法包括:
在演进基站间不涉及核心网的切换过程中, 源演进基站 eNB向用户设备发 送切换命令后, 向目标 eNB发送控制面消息和用户数据包,
所述控面消息中携带目标 eNB应该进行编号的第一个分组数据汇聚层协议 PDCP序列号和分组域隧道协议用户面 GTP— U序列号,所述源 eNB向所述目标 eNB发送的用户数据包包括:经过 PDCP层处理的用户数据包和 /或未经过 PDCP 层处理的用户数据包;
当所述目标 eNB根据所述目标 eNB应该进行编号的第一个 GTP— U序列号 小于所述 SGW向目标 eNB发送的第一个用户数据包的 GTP— U序列号时,所述 目标 eNB向所述用户设备发送所述源 eNB向所述目标 eNB发送的用户数据包; 当所述目标 eNB根据所述目标 eNB应该进行编号的第一个 GTP— U序列号 等于所述 SGW向目标 eNB发送的第一个用户数据包的 GTP— U序列号时,所述 目标 eNB向所述用户设备发送所述 SGW向所述目标 eNB发送的用户数据包。
29、 根据权利要求 28所述的数据转发方法, 其特征在于, 当所述目标 eNB 收到所述源 eNB发送的未经过 PDCP层处理的用户数据包时, 所述方法进一步 包括:
所述目标 eNB将所述控制面消息携带的目标 eNB应该进行编号的第一个 PDCP序列号设置为所述未经过 PDCP层处理的用户数据包的 PDCP序列号,并 向用户设备发送所述用户数据包。
30、 根据权利要求 28所述的数据转发方法, 其特征在于, 当所述目标 eNB 收到所述源 eNB发送的经过 PDCP层处理的用户数据包时, 所述方法进一步包 括:
所述目标 eNB沿用所述经过 PDCP层处理的用户数据包自身携带的 PDCP 序列号, 并向用户设备发送所述用户数据包。
PCT/CN2008/071928 2007-08-09 2008-08-07 Procédé de réacheminement de données, nœud b évolué et réseau d'évolution à long terme WO2009018784A1 (fr)

Priority Applications (4)

Application Number Priority Date Filing Date Title
PL08783921T PL2187664T3 (pl) 2007-08-09 2008-08-07 Sposób przekazywania danych, rozwinięty NodeB i sieć ewolucji długoterminowej
ES08783921.3T ES2496616T3 (es) 2007-08-09 2008-08-07 Método de reenvío de datos, NodoB evolucionado y red de evolución a largo plazo
EP08783921.3A EP2187664B1 (en) 2007-08-09 2008-08-07 Data forwarding method, evolved nodeb and long term evolution network
HRP20140817AT HRP20140817T1 (hr) 2007-08-09 2014-08-29 Postupak prosljeđivanja podataka, evoluirani čvor-b i mreža dugoročne evolucije

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
CN200710044812 2007-08-09
CN200710044812.6 2007-08-09
CN2007101451075A CN101365239B (zh) 2007-08-09 2007-08-22 数据转发的方法、演进基站和长期演进网络
CN200710145107.5 2007-08-22

Publications (1)

Publication Number Publication Date
WO2009018784A1 true WO2009018784A1 (fr) 2009-02-12

Family

ID=40340974

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2008/071928 WO2009018784A1 (fr) 2007-08-09 2008-08-07 Procédé de réacheminement de données, nœud b évolué et réseau d'évolution à long terme

Country Status (6)

Country Link
EP (2) EP2187664B1 (zh)
CN (2) CN103024840B (zh)
ES (1) ES2496616T3 (zh)
HR (1) HRP20140817T1 (zh)
PL (1) PL2187664T3 (zh)
WO (1) WO2009018784A1 (zh)

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN103024840B (zh) * 2007-08-09 2015-08-05 华为技术有限公司 数据转发的方法和演进基站
CN101877860B (zh) * 2009-04-28 2016-01-20 中兴通讯股份有限公司 中继节点、服务网关、中继数据的传输方法及系统
CN101931937B (zh) * 2009-06-19 2013-06-12 中兴通讯股份有限公司 下行报文转发方法及服务网关
CN101965028B (zh) * 2009-07-23 2015-08-12 中兴通讯股份有限公司 一种实现x2切换的方法、装置及系统
CN102036322A (zh) * 2009-09-28 2011-04-27 中兴通讯股份有限公司 X2用户面连接状态确定方法和装置
KR101486622B1 (ko) * 2010-04-29 2015-01-29 한국전자통신연구원 캐리어 에그리게이션에 기반한 핸드오버 방법
GB201018633D0 (en) 2010-11-04 2010-12-22 Nec Corp Communication system
US8861475B2 (en) * 2011-05-19 2014-10-14 Telefonaktiebolaget L M Ericsson (Publ) Inter-RAT handover control using sequence numbers
JP6072081B2 (ja) 2012-01-31 2017-02-01 エスシーエー アイピーエルエー ホールディングス インコーポレイテッド 通信端末及び通信方法
CN102711170A (zh) * 2012-05-21 2012-10-03 中兴通讯股份有限公司 一种激活态优化切换失败的处理方法及基站
WO2014019240A1 (zh) * 2012-08-03 2014-02-06 华为技术有限公司 一种数据处理方法、基站和用户设备
US20150109927A1 (en) * 2013-10-18 2015-04-23 Qualcomm Incorporated Base station to access point interface for data bearer routing
CN107438273B (zh) * 2016-05-26 2021-07-30 中兴通讯股份有限公司 承载转移中数据处理状态的确定方法及装置
WO2018023544A1 (zh) * 2016-08-04 2018-02-08 华为技术有限公司 通信方法、用户设备、基站、控制面网元和通信系统
US10904806B2 (en) * 2016-08-12 2021-01-26 Ntt Docomo, Inc. Core network and base station
CN112261696A (zh) 2016-11-04 2021-01-22 华为技术有限公司 发送结束标记的方法、设备和系统
EP3579617B1 (en) * 2017-02-27 2023-08-23 Huawei Technologies Co., Ltd. Preventing disorder of packets during handover
CN108632921B (zh) 2017-03-23 2022-07-01 中兴通讯股份有限公司 一种核心网切换方法及装置
CN109392025B (zh) * 2017-08-11 2023-09-29 华为技术有限公司 数据传输方法和数据传输装置
CN110149166B9 (zh) 2018-02-13 2021-11-30 华为技术有限公司 传输控制方法、装置和系统
CN110635998B (zh) 2018-06-22 2021-10-26 华为技术有限公司 一种数据传输方法、相关设备及计算机存储介质
KR102510823B1 (ko) 2018-08-13 2023-03-16 삼성전자주식회사 이동통신 시스템에서 핸드오버 방법 및 장치
CN111786859A (zh) * 2020-07-17 2020-10-16 中国联合网络通信集团有限公司 丢包检测方法、装置及存储介质
CN111935745B (zh) * 2020-08-12 2024-04-12 太仓市同维电子有限公司 实现终端跨基站移动性能优化的方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1937547A (zh) * 2005-09-23 2007-03-28 华为技术有限公司 一种演进网络中的无损迁移方法
WO2007076729A1 (fr) * 2006-01-06 2007-07-12 Huawei Technologies Co., Ltd. Procede de transfert intercellulaire pour utilisateur mobile et dispositif et systeme de communication et dispositif reseau a evolution
WO2007077523A1 (en) * 2006-01-03 2007-07-12 Nokia Corporation Performing a handover procedure after transmitting the segmented service data unit (sdu) in mac layer

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1898569A1 (en) * 2005-06-30 2008-03-12 Matsusita Electric Industrial Co., Ltd. Mobile communication control method, data communication device, mobile base station, and mobile terminal
CN1901733B (zh) * 2005-07-20 2012-02-29 华为技术有限公司 无线接入技术中进行无损切换的方法
WO2007071112A1 (fr) * 2005-12-22 2007-06-28 Zte Corporation Procede de maintien de transmission de flux de paquets de donnees lors du deplacement d'un terminal mobile dans un reseau d'acces sans fil
CN103024840B (zh) * 2007-08-09 2015-08-05 华为技术有限公司 数据转发的方法和演进基站

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1937547A (zh) * 2005-09-23 2007-03-28 华为技术有限公司 一种演进网络中的无损迁移方法
WO2007077523A1 (en) * 2006-01-03 2007-07-12 Nokia Corporation Performing a handover procedure after transmitting the segmented service data unit (sdu) in mac layer
WO2007076729A1 (fr) * 2006-01-06 2007-07-12 Huawei Technologies Co., Ltd. Procede de transfert intercellulaire pour utilisateur mobile et dispositif et systeme de communication et dispositif reseau a evolution

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN), 3GPP Technical Specification Group Radio Access Network", 3GPP TS 36.300 V8.1.0, June 2007 (2007-06-01), XP008126757 *

Also Published As

Publication number Publication date
EP2187664A1 (en) 2010-05-19
HRP20140817T1 (hr) 2014-11-21
CN103024840B (zh) 2015-08-05
EP2770776A1 (en) 2014-08-27
CN103024840A (zh) 2013-04-03
PL2187664T3 (pl) 2014-11-28
EP2187664A4 (en) 2011-02-16
CN101365239A (zh) 2009-02-11
EP2187664B1 (en) 2014-06-25
ES2496616T3 (es) 2014-09-19
CN101365239B (zh) 2012-12-12

Similar Documents

Publication Publication Date Title
WO2009018784A1 (fr) Procédé de réacheminement de données, nœud b évolué et réseau d'évolution à long terme
US11582650B2 (en) Methods and system for performing handover in a wireless communication system
JP4533431B2 (ja) Ipアドレス設定の遅延によるハンドオーバー実行方法
WO2009021457A1 (fr) Procédé et dispositif de traitement de message nas (non-access stratum) en cours de transfert dans un réseau évolué
CN110199568B (zh) 连接恢复方法、接入和移动性管理功能实体及用户设备
WO2008092408A1 (en) Method, device and system for establishing s1 signaling connection in evolved network
WO2010130135A1 (zh) 一种长期演进系统中跨基站切换方法及系统
WO2011009305A1 (zh) 一种实现x2切换的方法、装置及系统
TW200926852A (en) Handover method and apparatus in a wireless telecommunications network
JP2010536293A (ja) 無線通信ネットワークにおけるハンドオーバ方法及び機器
JP5655138B2 (ja) S1ハンドオーバ方法、s1ハンドオーバのデータ伝送方法及び移動通信システム
WO2009012666A1 (fr) Procédé et système pour transmettre un message de couche de non-accès durant un transfert et station de base associée
JP5663568B2 (ja) ダウンリンク・メッセージ中継方法及びサービス・ネットワーク・ゲートウェイ
WO2013044668A1 (zh) 一种处理lipa承载的方法和设备
WO2009127120A1 (zh) 切换过程中跟踪用户的方法、装置及系统
WO2011113210A1 (zh) 多基站间本地交换的方法及装置
WO2010094235A1 (zh) 切换过程中支持多载波聚合的方法及装置
JP6457118B2 (ja) ダウンリンクデータ通知
WO2014121503A1 (zh) 一种数据传输方法以及接入网设备
WO2014146578A1 (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: 08783921

Country of ref document: EP

Kind code of ref document: A1

WWE Wipo information: entry into national phase

Ref document number: 2008783921

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE