US10743220B2 - Handover handling - Google Patents

Handover handling Download PDF

Info

Publication number
US10743220B2
US10743220B2 US15/863,029 US201815863029A US10743220B2 US 10743220 B2 US10743220 B2 US 10743220B2 US 201815863029 A US201815863029 A US 201815863029A US 10743220 B2 US10743220 B2 US 10743220B2
Authority
US
United States
Prior art keywords
pdcp
base station
sdus
sequence
handover
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active
Application number
US15/863,029
Other versions
US20180132142A1 (en
Inventor
Jagdeep Singh Ahluwalia
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
NEC Corp
Original Assignee
NEC Corp
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 NEC Corp filed Critical NEC Corp
Priority to US15/863,029 priority Critical patent/US10743220B2/en
Publication of US20180132142A1 publication Critical patent/US20180132142A1/en
Priority to US16/922,780 priority patent/US11778521B2/en
Application granted granted Critical
Publication of US10743220B2 publication Critical patent/US10743220B2/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/0005—Control or signalling for completing the hand-off
    • H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
    • H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management
    • H04L1/1877—Buffer management for semi-reliable protocols, e.g. for less sensitive applications like streaming video
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/1607—Details of the supervisory signal
    • H04L1/1671—Details of the supervisory signal the supervisory signal being transmitted together with control information
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control
    • H04L47/34—Flow control; Congestion control ensuring sequence integrity, e.g. using sequence numbers
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L49/00—Packet switching elements
    • H04L49/55—Prevention, detection or correction of errors
    • H04L49/552—Prevention, detection or correction of errors by ensuring the integrity of packets received through redundant connections
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H04W36/023—Buffering or recovering information during reselection
    • H04W36/0235—Buffering or recovering information during reselection by transmitting sequence numbers, e.g. SN status transfer
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L2001/0092—Error control systems characterised by the topology of the transmission link
    • H04L2001/0097—Relays

Definitions

  • the present invention relates to the management of data packets in mobile telecommunications networks, particularly but not exclusively networks operating according to the 3GPP standards or equivalents or derivatives thereof.
  • the present invention provides a communication method performed by a node of a telecommunication system, the method comprising:
  • the method may be performed in a source node of the telecommunication system in which the other communication node is a mobile communication device and further comprising receiving a handover response from a target node and in response stopping transmission of data packets to the mobile communication device and forwarding PDCP SDUs with their appended sequence number stored in said PDCP buffer to the target node.
  • the mobile communication device sends a status report to the ARQ entity of the source node, which identifies the sequence number of the last in-sequence PDCP SDU received and of any received out-of-sequence PDCP SDUs.
  • the source node can then use this information to determine which PDCP SDUs stored in the PDCP buffer to send to the target node.
  • out-of-sequence PDCP SDUs received from the other communication node are buffered and forwarded to the target node at handover.
  • the uplink PDCP SDUs are marked to differentiate them from downlink PDCP SDUs.
  • the invention provides a method of facilitating handover of a mobile communication device from a source node to a target node, the method being performed in the source node and comprising, in response to receiving a handover response from the target node:
  • the invention also provides a method of facilitating handover of a mobile communication device from a source node to a target node, the method being performed in the target node and comprising, in response to transmitting a handover response to the source node:
  • the invention still further provides a method performed by a mobile communication device at handover from a source node to a target node, the method comprising:
  • the invention provides, for all methods disclosed, corresponding computer programs or computer program products for execution on corresponding equipment, the equipment itself (user equipment, nodes or components thereof) and methods of updating the equipment.
  • FIG. 1 schematically illustrates a mobile telecommunication system of a type to which the embodiment is applicable
  • FIG. 2 schematically illustrates a base station forming part of the system shown in FIG. 1 ;
  • FIG. 3 schematically illustrates a mobile communication device forming part of the system shown in FIG. 1 ;
  • FIG. 4 illustrates part of a protocol stack forming part of the communication software used to control communications between the mobile communication device and the base stations;
  • FIG. 5 shows a handover process
  • FIG. 6 illustrates the operation of the PDCP and outer ARQ entities for managing the buffering of acknowledge mode data packets.
  • FIG. 1 schematically illustrates a mobile (cellular) telecommunication system 1 in which users of mobile telephones (MT) 3 - 0 , 3 - 1 , and 3 - 2 can communicate with other users (not shown) via one of the base stations 5 - 1 or 5 - 2 and a telephone network 7 .
  • the base stations 5 use an orthogonal frequency division multiple access (OFDMA) technique in which the data to be transmitted to the mobile telephones 3 is modulated onto a plurality of sub-carriers. Different sub-carriers are allocated to each mobile telephone 3 depending on the amount of data to be sent to the mobile telephone 3 .
  • OFDMA orthogonal frequency division multiple access
  • a handover (HO) procedure is carried out in the source and target base stations 5 and in the mobile telephone 3 , to control the handover process.
  • the handover process aims to provide an optimised hard handover (HHO) between the source and target base stations 5 with the following requirements:
  • a hard handover is one where there is a break in radio transmissions between the mobile telephone and the base stations during the handover, as opposed to a soft handover, where the mobile telephone will establish a radio link with both the source and target base stations during the handover procedure.
  • it is therefore more difficult to perform a hard handover whilst minimising packet loss and packet retransmission.
  • FIG. 2 is a block diagram illustrating the main components of each of the base stations 5 used in this embodiment.
  • each base station 5 includes a transceiver circuit 21 which is operable to transmit signals to and to receive signals from the mobile telephones 3 via one or more antennae 23 (using the above described sub-carriers) and which is operable to transmit signals to and to receive signals from the telephone network 7 via a network interface 25 .
  • a controller 27 controls the operation of the transceiver circuit 21 in accordance with software stored in memory 29 .
  • the software includes, among other things, an operating system 31 and a downlink scheduler 33 .
  • the downlink scheduler 33 is operable for scheduling user data packets to be transmitted by the transceiver circuit 21 in its communications with the mobile telephones 3 .
  • the software also includes a handover module 35 , the operation of which will be described below.
  • FIG. 3 schematically illustrates the main components of each of the mobile telephones 3 shown in FIG. 1 .
  • the mobile telephones 3 each include a transceiver circuit 71 that is operable to transmit signals to and to receive signals from the base station 5 via one or more antennae 73 .
  • the mobile telephone 3 also includes a controller 75 which controls the operation of the mobile telephone 3 and which is connected to the transceiver circuit 71 on one hand and to a loudspeaker 77 , a microphone 79 , a display 81 , and a keypad 83 on the other hand.
  • the controller 75 operates in accordance with software instructions stored within memory 85 . As shown, these software instructions include, among other things, an operating system 87 . In this embodiment, the memory also provides uplink data buffers 89 .
  • the software for controlling the handover process is provided by a handover module 91 , the operation of which will be described below.
  • both the base station 5 and the mobile telephones 3 are described for ease of understanding as having respective discrete handover modules which control the handover procedure when a mobile telephone 3 moves from a source base station to a target base station.
  • the features may be provided in this way for certain applications, for example where an existing system has been modified to implement the invention, in other applications, for example in systems designed with the inventive features in mind from the outset, the handover features may be built into the overall operating system or code and so a handover module as a discrete entity may not be discernible.
  • LTE Long Term Evolution
  • UE mobile telephone 3 that is changing base stations
  • UE the mobile telephone 3 that is changing base stations
  • the source base station 5 - 1 will be referred to as the source eNodeB (or simply eNB)
  • target base station 5 - 2 will be referred to as the target eNodeB.
  • the protocol entities used in LTE have the same names as those used in UMTS except for the Radio Link Control (RLC) entities which, under LTE, are called the Outer ARQ entities.
  • RLC Radio Link Control
  • the Outer ARQ entities of LTE have substantially the same (although not identical) functionality to the RLC entities of UMTS.
  • FIG. 4 illustrates part of a protocol stack (lower three layers) used in the UE and eNodeBs.
  • the first layer is the physical layer (L1) which is responsible for the actual transmission of the data over the radio communication channel.
  • the second layer (L2) which is divided into three sub-layers—the Medium Access Control layer (L2/MAC) which is responsible for controlling access to the air interface; the Outer ARQ (Automatic Repeat request) layer (L2/OARQ) which is responsible for concatenation and segmentation of data packets, the acknowledgment of packets and the re-transmission of data packets where necessary; and the PDCP (Packet Data Convergence Protocol) layer (L2/PDCP) which is responsible for header compression and ciphering.
  • L2/MAC Medium Access Control layer
  • L2/OARQ Automatic Repeat request
  • PDCP Packet Data Convergence Protocol
  • the second layer is the Radio Resource Control (RRC) layer (L3/RRC) that is responsible for controlling radio resources used in the air interface between the eNodeB and the UE.
  • RRC Radio Resource Control
  • L2/Outer ARQ layer includes a number of Outer ARQ entities 95 used to manage the transmission of C-plane data and U-plane data
  • the L2/PDCP layer includes PDCP entities 97 used to process the C-plane and the U-plane data.
  • FIG. 5 schematically illustrates the operations performed by the PDCP entities 97 and the Outer ARQ entities 95 when processing downlink data packets.
  • a similar process is performed for uplink data packets, but in the reverse order.
  • PDCP SDUs (Service Data Units) 101 received by the PDCP entity 97 firstly undergo a header compression 102 to generate corresponding SDUs 103 with compressed headers.
  • the PDCP entity 97 then generates and appends 104 a sequence number (SN) to each SDU 103 identifying the number of the SDU in the sequence of SDUs for the UE.
  • the thus generated SDUs with SNs 105 are then buffered 106 in a PDCP buffer 107 .
  • These SDUs are then ciphered 108 to generate the ciphered PDCP PDUs 109 , which are passed to the Outer ARQ entity 95 , where they are segmented to form Outer ARQ SDU segments 111 .
  • Each Outer ARQ SDU segment is then tagged with data identifying the segment and its position within the corresponding PDCP PDU 109 .
  • the Outer ARQ entity 95 reuses the PDCP sequence number (SN) and an OFFSET and LENGTH which indicate the position and length of the Outer ARQ segment in the original PDCP PDU 109 .
  • the PDCP entity 97 During normal operation, for downlink AM (Acknowledge Mode) packets, the PDCP entity 97 will purge each PDCP SDU 105 from its buffer 107 as soon as the Outer ARQ entity 95 confirms that it has received acknowledgements for all the Outer ARQ segments 111 that contain the PDCP SDU 105 . For downlink UM (Unacknowledged Mode) packets, the PDCP entity 97 deletes each PDCP SDU 105 from its buffer 107 as soon as the Outer ARQ entity 95 acknowledges the transmission of the Outer ARQ PDUs 111 containing the PDCP SDU 105 . For uplink AM packets, the outer ARQ entity 95 receives packet segments from the UE and acknowledges receipt.
  • the Outer ARQ entity 95 then concatenates the received packet segments to generate ARQ SDUs which it forwards to the PDCP entity 97 .
  • the PDCP entity 97 then deciphers the received ARQ SDUs and if the sequence number is not out of sequence, it removes the SN and decompresses the header before forwarding the packet to an MME/SAE Gateway in the telephone network 7 .
  • the PDCP entity 97 stores the received packet in its buffer 107 , until all the missing packets have been received at which point the PDCP entity 97 reorders the SDUs based on their PDCP sequence numbers, then removes the SN, decompresses the packet headers and forwards the received packets in correct sequence to the telephone network 7 .
  • the Outer ARQ entity 95 receives the packet segments, concatenates them and sends them to the PDCP entity 97 .
  • the PDCP entity 97 then deciphers the packets, removes their sequence numbers, decompresses their headers and then forwards them to the telephone network 7 .
  • acknowledge mode (AM) Radio Link Control (RLC), in which receipt of data packets are acknowledged by the receiver, although the Outer ARQ entity (the equivalent of RLC for LTE) may not be identical to the RLC in all aspects.
  • UM unacknowledged mode
  • FIG. 6 shows timings when it is proposed to stop the U-plane data transmission in the Downlink (DL) and the Uplink (UL), together with the details of the modified sequences described. The following description explains how this approach of stopping the data flow facilitates achieving a fast lossless handover for LTE.
  • the PDCP sequence numbers are maintained during handover (used by the target eNodeB) and the source eNodeB selectively forwards all downlink PDCP SDUs (with SN) 105 (from the buffer 107 ) that have not been acknowledged by the UE to the target eNodeB, and discards any remaining downlink Outer ARQ PDU segments that have not yet been transmitted.
  • the source eNodeB also forwards uplink PDCP SDUs 105 successfully received in-sequence to the telephone network 7 (SAE Gateway), forwards uplink PDCP SDUs 105 received out-of-sequence, from the buffer 107 , to the target eNodeB and discards any remaining uplink Outer ARQ PDUs.
  • the uplink PDCP SDUs received out-of-sequence need to be marked as Uplink Packets by the PDCP entity 97 before they are forwarded to the target eNodeB PDCP entity 97 so that the target eNodeB can establish that the packet is an out-of-sequence uplink packet and not a downlink packet for transmission to the UE.
  • the target eNodeB PDCP then forwards these out-of-sequence uplink packets to the telephone network 7 once the missing uplink packets have been received from the UE.
  • the source eNodeB synchronizes the data transmission status between itself and the UE with the target eNodeB during HO. This is facilitated by stopping the data flow at an appropriate instant in time during the HO execution phase, considering that the interruption time for the user plane data is minimal.
  • the Outer ARQ entity in the source eNodeB and in the UE sends the other a status report (indicating what that device has received successfully) before stopping the data flow in the appropriate direction.
  • This status message may be a simplified report indicating only what the device has received.
  • the Outer ARQ status reports exchanged at the time of handover are based on the Outer ARQ SDUs 109 using the PDCP sequence numbers (SNs), rather than status reports based on the Outer ARQ PDUs 111 , as these would have to be larger in size (to include the PDCP SN as well as the OFFSET and LENGTH data which are needed to identify each Outer ARQ PDU 111 ) and may delay the handover.
  • the size of the Status PDU can be reduced to an order of tens of bytes, facilitating fast transmission at the time of handovers.
  • the Outer ARQ entities may exchange status PDUs based on the smaller sized ARQ PDUs. Unlike the status PDUs used during handover, these status PDUs will include the OFFSET and LENGTH data needed to identify the smaller ARQ PDUs.
  • Desideratum I is met by having PDCP entities 97 which are capable of buffering and forwarding the DL data packets from source to target eNodeB.
  • the PDCP entities 97 may buffer the data packets generated by the application after the UL transmission is stopped until the UE is switched to the target eNodeB—this requires the UE to provide buffering not present in a conventional UE, but this may not be unduly problematic to implement.
  • the source eNodeB can synchronize the data transmission status between source and target eNodeB. This is because the source eNodeB can know accurately which are the PDCP SDUs that need to be transferred to the target eNodeB based on the data in the transmission and retransmission buffer.
  • the instance when the DL data is stopped is chosen to be most optimal according to our considerations so as to have minimum interruption time. If the source eNodeB continues to schedule DL data, the UE will not be able to successfully receive or acknowledge these data packets as, immediately after receiving the handover command, it would try to synchronise with the target cell. Eventually these packets would have to be forwarded to the target eNodeB and will have to be transmitted again through the target eNodeB resulting in inefficient usage of the air interface bandwidth.
  • the UE may not be able to receive acknowledgements from the source eNodeB and the UE would have to again transmit these AM packets in the UL direction to the target eNodeB resulting in inefficient usage of the air interface bandwidth.
  • RT real time
  • packets that are transmitted in the UL direction by the UE while it is trying to gain synchronisation in the target eNodeB may get lost due to bad radio conditions in the UL and could not be recovered if the data flow is not stopped.
  • it would be beneficial to avoid any packet loss even for real time services in the UL by stopping the UL data flow during handover execution while the delay could be compensated at the receiving end by the play out buffer.
  • Another advantage of having a definitive time instant for stopping the data flow is that a simplified implicit reordering of the data packets in the target eNodeB can be achieved if the forwarded DL data packets from the source eNodeB on the X2 interface are transmitted first to the UE followed by the data received from the telephone network 7 (MME/SAE Gateway on the S1 interface).

Abstract

A system is proposed to provide handover in a mobile telecommunications environment, particularly applicable to 3GPP networks, which does not increase signalling overhead but minimises user data loss during handover. In the modified system, PDCP SDUs with Sequence numbers are buffered and retransmitted as necessary. At the time of handover, SDUs not received by the user device are forwarded to the target base station for forward transmission to the UE. The handover procedure is designed to minimise packet loss whilst keeping to a minimum the duplication of packet transmission over the air interface.

Description

CROSS REFERENCE TO RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 14/643,642, filed on Mar. 10, 2015, entitled “HANDOVER HANDLING”, which is a continuation of U.S. patent application Ser. No. 13/543,402, filed on Jul. 6, 2012, entitled “HANDOVER HANDLING”, which is a continuation of U.S. patent application Ser. No. 12/451,166, filed on Oct. 28, 2009, entitled “HANDOVER HANDLING”, now U.S. Pat. No. 9,001,781, which issued on Apr. 7, 2015, which is a national phase application of International Application No. PCT/JP2008/058589, filed on Apr. 30, 2008, entitled “HANDOVER HANDLING”, which claims priority to United Kingdom Patent Application No. 0708455.1, filed on May 1, 2007, the disclosures of which are hereby incorporated by reference.
TECHNICAL FIELD
The present invention relates to the management of data packets in mobile telecommunications networks, particularly but not exclusively networks operating according to the 3GPP standards or equivalents or derivatives thereof.
BACKGROUND ART
In mobile telecommunications networks, there is a requirement for User Equipment (UE) to handover from one base station to another. In the 3GPP, there has been recently proposed a procedure defined in the control plane (C-plane) for handover (HO) from a source eNodeB (base station) to a target eNodeB. The various acronyms applicable to 3G communications will of course be familiar to those skilled in the art but a glossary is appended for the benefit of lay readers.
Although for efficiency of understanding for those of skill in the art the invention will be described in detail in the context of a 3G system, the principles of handover can be applied to other systems, e.g. other CDMA or wireless in which a mobile device or User Equipment (UE) communicates with one of several other devices (corresponding to eNodeB) with the corresponding elements of the system changed as required.
At the RAN2/RAN3/SA2 joint meeting in St. Louis, the SAE/LTE architectural principles were agreed and the decision was to move the PDCP layer down to the eNodeB (base station). At the following RAN2 meeting in Malta it was decided that the ciphering would be performed at the PDCP layer using PDCP Sequence Numbers. Based on this decision user plane handling during handover needs further consideration and the present application proposes a suitable handover procedure.
DISCLOSURE OF THE INVENTION
According to one aspect, the present invention provides a communication method performed by a node of a telecommunication system, the method comprising:
receiving a sequence of PDCP Service Data Units, SDUs, for transmission to another communication node, such as a mobile device;
appending a sequence number to each PDCP SDU;
storing a copy of the PDCP SDUs with appended sequence number in a PDCP buffer;
ciphering the PDCP SDUs;
passing the ciphered PDCP SDUs with appended sequence numbers to an Outer ARQ entity for segmentation;
segmenting the ciphered PDCP SDUs with appended sequence numbers to generate Outer ARQ segments;
generating and appending a respective Outer ARQ header to each Outer ARQ segment to generate a corresponding Outer ARQ Protocol Data Unit, PDU, which header includes data identifying the position of the Outer ARQ segment within the corresponding PDCP SDU;
sending the generated Outer ARQ PDUs to the other communication node;
receiving acknowledgements for transmitted Outer ARQ PDUs; and
purging each PDCP SDU from the PDCP buffer once acknowledgements have been received for the Outer ARQ PDUs containing the PDCP SDU.
The method may be performed in a source node of the telecommunication system in which the other communication node is a mobile communication device and further comprising receiving a handover response from a target node and in response stopping transmission of data packets to the mobile communication device and forwarding PDCP SDUs with their appended sequence number stored in said PDCP buffer to the target node.
Preferably, the mobile communication device sends a status report to the ARQ entity of the source node, which identifies the sequence number of the last in-sequence PDCP SDU received and of any received out-of-sequence PDCP SDUs. The source node can then use this information to determine which PDCP SDUs stored in the PDCP buffer to send to the target node.
In one embodiment, out-of-sequence PDCP SDUs received from the other communication node are buffered and forwarded to the target node at handover. Before being forwarded to the target node, the uplink PDCP SDUs are marked to differentiate them from downlink PDCP SDUs.
According to another aspect, the invention provides a method of facilitating handover of a mobile communication device from a source node to a target node, the method being performed in the source node and comprising, in response to receiving a handover response from the target node:
stopping the transmission of downlink Outer ARQ PDUs from the source node to the mobile communication device;
transmitting a handover command to said mobile communication device after stopping the transmission of said downlink user data;
receiving a status packet from the mobile communication device, which status packet identifies the last in-sequence PDCP SDU received from the source node and any out-of-sequence PDCP SDUs received from the source node; and
forwarding PDCP SDUs to the target node in dependence upon the identified PDCP SDUs received by the mobile communication device.
The invention also provides a method of facilitating handover of a mobile communication device from a source node to a target node, the method being performed in the target node and comprising, in response to transmitting a handover response to the source node:
receiving forwarded downlink PDCP SDUs from the source node;
receiving forwarded uplink out-of-sequence PDCP SDUs from the source node;
transmitting Outer ARQ PDUs corresponding to the received downlink PDCP SDUs to the mobile communication device;
receiving Outer ARQ PDUs from the mobile communication device and forming from them corresponding PDCP SDUs with sequence numbers; and
reordering the received PDCP SDUs and the forwarded PDCP SDUs based on their sequence numbers and forwarding them in sequence to a telecommunication network.
The invention still further provides a method performed by a mobile communication device at handover from a source node to a target node, the method comprising:
receiving a status packet from the source node identifying the last in-sequence uplink PDCP SDUs received by the source node and any out-of-sequence PDCP SDUs received by the source node;
receiving a handover command from the source node;
transmitting a status packet to the source node identifying the last in-sequence downlink PDCP SDU received from the source node and any out-of-sequence PDCP SDUs received from the source node;
stopping transmission of data packets to the source node;
establishing a communication link with the target node;
determining PDCP SDUs to be transmitted/retransmitted to the target node based on the status packet received from the source node; and
transmitting/retransmitting the determined PDCP SDUs to the target node.
While the invention is described for ease of understanding in the context of handover from one 3G eNodeB to another, the principles may be extended to handover between nodes of different networks, e.g. a 3G network and another network.
The invention provides, for all methods disclosed, corresponding computer programs or computer program products for execution on corresponding equipment, the equipment itself (user equipment, nodes or components thereof) and methods of updating the equipment.
BRIEF DESCRIPTION OF DRAWINGS
FIG. 1 schematically illustrates a mobile telecommunication system of a type to which the embodiment is applicable;
FIG. 2 schematically illustrates a base station forming part of the system shown in FIG. 1;
FIG. 3 schematically illustrates a mobile communication device forming part of the system shown in FIG. 1;
FIG. 4 illustrates part of a protocol stack forming part of the communication software used to control communications between the mobile communication device and the base stations;
FIG. 5 shows a handover process;
FIG. 6 illustrates the operation of the PDCP and outer ARQ entities for managing the buffering of acknowledge mode data packets.
 BEST MODE CARRYING OUT THE INVENTION
Overview
FIG. 1 schematically illustrates a mobile (cellular) telecommunication system 1 in which users of mobile telephones (MT) 3-0, 3-1, and 3-2 can communicate with other users (not shown) via one of the base stations 5-1 or 5-2 and a telephone network 7. In this embodiment, the base stations 5 use an orthogonal frequency division multiple access (OFDMA) technique in which the data to be transmitted to the mobile telephones 3 is modulated onto a plurality of sub-carriers. Different sub-carriers are allocated to each mobile telephone 3 depending on the amount of data to be sent to the mobile telephone 3. When a mobile telephone 3 moves from the cell of a source base station (eg base station 5-1) to a target base station (eg base station 5-2), a handover (HO) procedure (protocol) is carried out in the source and target base stations 5 and in the mobile telephone 3, to control the handover process.
The handover process aims to provide an optimised hard handover (HHO) between the source and target base stations 5 with the following requirements:
    • 1. Lossless HHO for the non-real time (NRT) Services in order to achieve high TCP throughput performance.
    • 2. Seamless HHO for real time (RT) services to minimise the packet loss in order to have good end to end performance of the application.
    • 3. Minimization of duplicate packet transmission over the air interface.
    • 4. Minimal interruption time for the user plane data.
    • 5. In sequence delivery of NAS (Non Access Stratum) PDUs should be maintained during HO.
    • 6. No duplication and out of sequence delivery should be visible to ROHC (Robust Header Compression) and application.
A hard handover is one where there is a break in radio transmissions between the mobile telephone and the base stations during the handover, as opposed to a soft handover, where the mobile telephone will establish a radio link with both the source and target base stations during the handover procedure. As those skilled in the art will appreciate, it is therefore more difficult to perform a hard handover whilst minimising packet loss and packet retransmission.
Base Station
FIG. 2 is a block diagram illustrating the main components of each of the base stations 5 used in this embodiment. As shown, each base station 5 includes a transceiver circuit 21 which is operable to transmit signals to and to receive signals from the mobile telephones 3 via one or more antennae 23 (using the above described sub-carriers) and which is operable to transmit signals to and to receive signals from the telephone network 7 via a network interface 25. A controller 27 controls the operation of the transceiver circuit 21 in accordance with software stored in memory 29. The software includes, among other things, an operating system 31 and a downlink scheduler 33. The downlink scheduler 33 is operable for scheduling user data packets to be transmitted by the transceiver circuit 21 in its communications with the mobile telephones 3. The software also includes a handover module 35, the operation of which will be described below.
Mobile Telephone
FIG. 3 schematically illustrates the main components of each of the mobile telephones 3 shown in FIG. 1. As shown in FIG. 3, the mobile telephones 3 each include a transceiver circuit 71 that is operable to transmit signals to and to receive signals from the base station 5 via one or more antennae 73. As shown, the mobile telephone 3 also includes a controller 75 which controls the operation of the mobile telephone 3 and which is connected to the transceiver circuit 71 on one hand and to a loudspeaker 77, a microphone 79, a display 81, and a keypad 83 on the other hand. The controller 75 operates in accordance with software instructions stored within memory 85. As shown, these software instructions include, among other things, an operating system 87. In this embodiment, the memory also provides uplink data buffers 89. The software for controlling the handover process is provided by a handover module 91, the operation of which will be described below.
In the above description, both the base station 5 and the mobile telephones 3 are described for ease of understanding as having respective discrete handover modules which control the handover procedure when a mobile telephone 3 moves from a source base station to a target base station. Whilst the features may be provided in this way for certain applications, for example where an existing system has been modified to implement the invention, in other applications, for example in systems designed with the inventive features in mind from the outset, the handover features may be built into the overall operating system or code and so a handover module as a discrete entity may not be discernible.
Operation
The following description will use the nomenclature used in the Long Term Evolution (LTE) of UTRAN. Therefore, the mobile telephone 3 that is changing base stations will be referred to as UE, the source base station 5-1 will be referred to as the source eNodeB (or simply eNB) and the target base station 5-2 will be referred to as the target eNodeB. The protocol entities used in LTE have the same names as those used in UMTS except for the Radio Link Control (RLC) entities which, under LTE, are called the Outer ARQ entities. The Outer ARQ entities of LTE have substantially the same (although not identical) functionality to the RLC entities of UMTS.
FIG. 4 illustrates part of a protocol stack (lower three layers) used in the UE and eNodeBs. The first layer is the physical layer (L1) which is responsible for the actual transmission of the data over the radio communication channel. Above that is the second layer (L2), which is divided into three sub-layers—the Medium Access Control layer (L2/MAC) which is responsible for controlling access to the air interface; the Outer ARQ (Automatic Repeat request) layer (L2/OARQ) which is responsible for concatenation and segmentation of data packets, the acknowledgment of packets and the re-transmission of data packets where necessary; and the PDCP (Packet Data Convergence Protocol) layer (L2/PDCP) which is responsible for header compression and ciphering. Above the second layer is the Radio Resource Control (RRC) layer (L3/RRC) that is responsible for controlling radio resources used in the air interface between the eNodeB and the UE. As shown, the L2/Outer ARQ layer includes a number of Outer ARQ entities 95 used to manage the transmission of C-plane data and U-plane data and the L2/PDCP layer includes PDCP entities 97 used to process the C-plane and the U-plane data.
FIG. 5 schematically illustrates the operations performed by the PDCP entities 97 and the Outer ARQ entities 95 when processing downlink data packets. A similar process is performed for uplink data packets, but in the reverse order. As shown, PDCP SDUs (Service Data Units) 101 received by the PDCP entity 97 firstly undergo a header compression 102 to generate corresponding SDUs 103 with compressed headers. The PDCP entity 97 then generates and appends 104 a sequence number (SN) to each SDU 103 identifying the number of the SDU in the sequence of SDUs for the UE. The thus generated SDUs with SNs 105 are then buffered 106 in a PDCP buffer 107. These SDUs are then ciphered 108 to generate the ciphered PDCP PDUs 109, which are passed to the Outer ARQ entity 95, where they are segmented to form Outer ARQ SDU segments 111. Each Outer ARQ SDU segment is then tagged with data identifying the segment and its position within the corresponding PDCP PDU 109. In this embodiment, the Outer ARQ entity 95 reuses the PDCP sequence number (SN) and an OFFSET and LENGTH which indicate the position and length of the Outer ARQ segment in the original PDCP PDU 109.
During normal operation, for downlink AM (Acknowledge Mode) packets, the PDCP entity 97 will purge each PDCP SDU 105 from its buffer 107 as soon as the Outer ARQ entity 95 confirms that it has received acknowledgements for all the Outer ARQ segments 111 that contain the PDCP SDU 105. For downlink UM (Unacknowledged Mode) packets, the PDCP entity 97 deletes each PDCP SDU 105 from its buffer 107 as soon as the Outer ARQ entity 95 acknowledges the transmission of the Outer ARQ PDUs 111 containing the PDCP SDU 105. For uplink AM packets, the outer ARQ entity 95 receives packet segments from the UE and acknowledges receipt. The Outer ARQ entity 95 then concatenates the received packet segments to generate ARQ SDUs which it forwards to the PDCP entity 97. The PDCP entity 97 then deciphers the received ARQ SDUs and if the sequence number is not out of sequence, it removes the SN and decompresses the header before forwarding the packet to an MME/SAE Gateway in the telephone network 7. However, if the received packet is out of sequence, then the PDCP entity 97 stores the received packet in its buffer 107, until all the missing packets have been received at which point the PDCP entity 97 reorders the SDUs based on their PDCP sequence numbers, then removes the SN, decompresses the packet headers and forwards the received packets in correct sequence to the telephone network 7. For uplink UM packets, the Outer ARQ entity 95 receives the packet segments, concatenates them and sends them to the PDCP entity 97. The PDCP entity 97 then deciphers the packets, removes their sequence numbers, decompresses their headers and then forwards them to the telephone network 7.
Description of the Handover Protocol
The description that follows mainly applies to acknowledge mode (AM) Radio Link Control (RLC), in which receipt of data packets are acknowledged by the receiver, although the Outer ARQ entity (the equivalent of RLC for LTE) may not be identical to the RLC in all aspects. Specifics of unacknowledged mode (UM) Outer ARQ entities employed for real time applications such as VoIP and streaming are also brought out wherever there is a different handling applied as compared to the acknowledge mode entities.
In order to transfer the context and forward the data to support lossless inter eNodeB handover, we have appreciated that it is desirable that the source eNodeB is able to synchronize the data transmission status between itself and the target eNodeB during handover. From this we have concluded that the data flow should desirably be stopped at an appropriate instant in time during the handover execution phase considering that the interruption time for the User Plane data is minimal. However, fulfilling this desired requirement is not straightforward as stopping the data transmission through additional signalling would be problematic as it would increase the overall handover time. We have appreciated that it is possible implicitly to stop the data transmission in (one or both, preferably both) the source eNodeB and UE at the time of handover execution, by modifying the conventional approach (which is carried out solely in the C-plane) to build in some “realisation” of the handover process in the User plane data transfer process. A further desirable feature is that the number of duplicated packets transmitted over the air either by the target eNodeB or by the UE is minimised.
FIG. 6 shows timings when it is proposed to stop the U-plane data transmission in the Downlink (DL) and the Uplink (UL), together with the details of the modified sequences described. The following description explains how this approach of stopping the data flow facilitates achieving a fast lossless handover for LTE.
Referring to FIG. 6, information flow for Intra-LTE-Access Mobility Support is described.
  • 1) The UE context within the source eNodeB contains information regarding roaming restrictions which were provided either at connection establishment or at the last TA update.
  • 2) The source eNodeB entity configures the UE measurement procedures according to the area restriction information. Measurements provided by the source eNodeB entity may assist the function controlling the UE's connection mobility.
  • 3) Based on measurement results from the UE and the source eNodeB, probably assisted by additional RRM specific information, the source eNodeB decides to handover the UE to a cell controlled by the target eNodeB.
  • 4) The source eNodeB issues a handover Request to the target eNodeB entity passing necessary information to prepare the handover at the target side. The target eNodeB configures the required resources.
  • 5) Admission Control is performed by the target eNodeB to increase the likelihood of a successful handover, if the resources can be granted by target eNodeB.
  • 6) The handover preparation is finished at the target eNodeB, information for the UE to reconfigure the radio path towards the target eNodeB is passed to the source eNodeB.
  • 7) This step consists of the following sub steps.
    • a. Before submitting the HO Command to the lower protocol layers, the Radio Resource Control (RRC) entity 96 in the source eNodeB commands the Outer ARQ User Plane (UP) entities 95 to send a status packet in the downlink direction and stop the DL transmission so that these Outer ARQ entities 95 shall not submit any Outer ARQ PDUs to the lower protocol layer. The UL reception should continue. In case receiving packets are UM Outer ARQ PDUs, the Outer ARQ entity will reassemble the SDUs and transfer them to the upper layers as soon as all PDUs that contain the SDU have been received.
    • b. The UE is commanded by the source eNodeB RRC entity 96 to perform the HO; target side radio resource information is contained in the command.
    • c. On receiving the HO Command the RRC entity 96 in the UE commands the outer ARQ U-plane entities to send a status packet in the Uplink direction and stop the UL transmission. In response, the PDCP layer in the source eNodeB positively purges the corresponding PDCP SDU from its buffer 107. Following this, the UE shall immediately initiate the L1/L2 signalling in the target eNodeB after this.
    • d. Since the user plane data transmission is stopped in both directions and the status packet is exchanged in both uplink and downlink, the source eNodeB will be able to accurately synchronize the data transmission status between source and target eNodeBs, and SDU forwarding (from Source eNodeB to target eNodeB) can start from any point after this.
  • 8) The UE gains synchronisation at the target side.
  • 9) Once the UE has successfully accessed the cell, it sends an indication to the target eNodeB that the handover is completed.
  • 10 a) After submitting the handover Complete to the lower layer, the RRC entity 96 in the UE commands the PDCP entities 97 and the Outer ARQ entities 95 to resume the UL U-plane traffic.
  • 10 b) On reception of handover Complete, the RRC entity 96 in the target eNodeB commands the PDCP entities 97 and the Outer ARQ U-plane entities 95 to resume the DL traffic. The target eNodeB starts the transmission of the forwarded DL packets received from the source eNodeB.
  • 11) The MME/UPE is informed that the UE has changed cell. The UPE switches the data path to the target eNodeB and can release any U-plane/TNL resources towards the source eNodeB.
  • 12) The MME/UPE confirms the handover Complete message to the target eNodeB with the handover Complete ACK message.
  • 13) The target eNodeB triggers the release of resources at the source side. The target eNodeB can send this message directly after reception of message 9.
  • 14) Upon reception of the Release Resource message, the source eNodeB releases radio and C-plane related resources in relation to the UE context. The source eNodeB continues to perform data forwarding until an implementation dependent mechanism decides that data forwarding can be stopped and U-plane/TNL resources can be released.
  • 15) If the new cell is a member of a new Tracking Area, the UE needs to register with the MME/UPE which in turn updates the area restriction information on the target eNodeB.
    Unidirectional Stopping of the Outer ARQ Entities
Since data transmission is being stopped in the source eNodeB and in the UE at the time of handover execution, it needs to be emphasised that suspending the user plane data transfer in both directions (as in a conventional REL 6 RLC entity) would result in data loss as the data packets in flight will be discarded by the RLC entity that has been stopped. Hence for a LTE system where there will be hard handovers, the outer ARQ entity (RLC) should stop transmissions but continue to receive packets to avoid any data loss.
Packet Forwarding
In this embodiment, the PDCP sequence numbers are maintained during handover (used by the target eNodeB) and the source eNodeB selectively forwards all downlink PDCP SDUs (with SN) 105 (from the buffer 107) that have not been acknowledged by the UE to the target eNodeB, and discards any remaining downlink Outer ARQ PDU segments that have not yet been transmitted. During handover, the source eNodeB also forwards uplink PDCP SDUs 105 successfully received in-sequence to the telephone network 7 (SAE Gateway), forwards uplink PDCP SDUs 105 received out-of-sequence, from the buffer 107, to the target eNodeB and discards any remaining uplink Outer ARQ PDUs. The uplink PDCP SDUs received out-of-sequence need to be marked as Uplink Packets by the PDCP entity 97 before they are forwarded to the target eNodeB PDCP entity 97 so that the target eNodeB can establish that the packet is an out-of-sequence uplink packet and not a downlink packet for transmission to the UE. The target eNodeB PDCP then forwards these out-of-sequence uplink packets to the telephone network 7 once the missing uplink packets have been received from the UE.
Sending STATUS PDU Before Stopping the Outer ARQ Entities
In order to transfer the context and forward the data to support lossless inter eNodeB HO, the source eNodeB synchronizes the data transmission status between itself and the UE with the target eNodeB during HO. This is facilitated by stopping the data flow at an appropriate instant in time during the HO execution phase, considering that the interruption time for the user plane data is minimal. In one embodiment the Outer ARQ entity in the source eNodeB and in the UE sends the other a status report (indicating what that device has received successfully) before stopping the data flow in the appropriate direction. This status message may be a simplified report indicating only what the device has received. This allows the source eNodeB and the UE to get to know the exact data transmission status (ie what the other party has received and therefore what still has to be sent) before stopping the transmission during the HO execution. Therefore, after the HO the data transmission can resume without the need to transmit any duplicated packets over the air interface.
In the preferred embodiment, the Outer ARQ status reports exchanged at the time of handover are based on the Outer ARQ SDUs 109 using the PDCP sequence numbers (SNs), rather than status reports based on the Outer ARQ PDUs 111, as these would have to be larger in size (to include the PDCP SN as well as the OFFSET and LENGTH data which are needed to identify each Outer ARQ PDU 111) and may delay the handover. With PDCP SN based Status Reports, the size of the Status PDU can be reduced to an order of tens of bytes, facilitating fast transmission at the time of handovers. During normal operation, the Outer ARQ entities may exchange status PDUs based on the smaller sized ARQ PDUs. Unlike the status PDUs used during handover, these status PDUs will include the OFFSET and LENGTH data needed to identify the smaller ARQ PDUs.
Advantages
The precise timings that are indicated above for stopping the data flow help in meeting the following (separate) desiderata we have formulated.
    • I. Unified Lossless handover mechanism for both real-time and non real-time services
    • II. Minimal interruption time for the user plane data.
    • III. Minimising transmission of duplicate packets by eNodeB and UE.
Desideratum I is met by having PDCP entities 97 which are capable of buffering and forwarding the DL data packets from source to target eNodeB. In the UE the PDCP entities 97 may buffer the data packets generated by the application after the UL transmission is stopped until the UE is switched to the target eNodeB—this requires the UE to provide buffering not present in a conventional UE, but this may not be unduly problematic to implement. By implicitly stopping the data flows the source eNodeB can synchronize the data transmission status between source and target eNodeB. This is because the source eNodeB can know accurately which are the PDCP SDUs that need to be transferred to the target eNodeB based on the data in the transmission and retransmission buffer.
Regarding the desideratum II, since there is no explicit (additional) signalling involved for stopping the data flow in the UL as well as the DL directions, there will be no increase in the interruption time for the user plane data.
Furthermore, the instance when the DL data is stopped is chosen to be most optimal according to our considerations so as to have minimum interruption time. If the source eNodeB continues to schedule DL data, the UE will not be able to successfully receive or acknowledge these data packets as, immediately after receiving the handover command, it would try to synchronise with the target cell. Eventually these packets would have to be forwarded to the target eNodeB and will have to be transmitted again through the target eNodeB resulting in inefficient usage of the air interface bandwidth. Whilst according to conventional thinking it might be argued that for real-time services such as VoIP, stopping the data would be detrimental to the service, we have appreciated that if the source eNodeB continues to transmit DL packets there is no mechanism by which they could be recovered if the UE could not receive them while it is trying to synchronise with the target cell and this might, in practice, be at least as problematic. However we have appreciated that if the data flow is stopped and a packet forwarding mechanism is adopted, there is a possibility to eliminate packet loss in the DL, although there could be a delayed data packet delivery to the UE which could result in just a single packet being discarded in the worst case. But this could be compensated through the play-out buffer.
Similarly if the UE continues to transmit in the UL while trying to gain synchronisation with the target cell, it may not be able to receive acknowledgements from the source eNodeB and the UE would have to again transmit these AM packets in the UL direction to the target eNodeB resulting in inefficient usage of the air interface bandwidth. For real time (RT) services, packets that are transmitted in the UL direction by the UE while it is trying to gain synchronisation in the target eNodeB, may get lost due to bad radio conditions in the UL and could not be recovered if the data flow is not stopped. Hence it would be beneficial to avoid any packet loss even for real time services in the UL by stopping the UL data flow during handover execution while the delay could be compensated at the receiving end by the play out buffer.
Furthermore if the transmission of data continues both in the UL and DL directions after the handover Command is sent by the source eNodeB, it would be complicated to synchronize the data transmission status between source and target eNodeBs because of the dynamic nature of the packets in the transmission and retransmission buffers at the source eNodeB and would result in duplicated packets being transmitted again by the target eNodeB in the DL and by the UE in the UL to ensure lossless handover for non-real time (NRT) Services result in inefficient usage of the air interface bandwidth. However, for real-time services such as VoIP etc using UM mode, data packets transmitted by the source eNodeB and not received correctly at the target eNodeB, will be lost and cannot be recovered. Hence stopping the data flow for both RT and NRT services in a unified way will help in better resource utilization on the air interface for the NRT Bearers and will avoid data loss for RT services.
Another advantage of having a definitive time instant for stopping the data flow is that a simplified implicit reordering of the data packets in the target eNodeB can be achieved if the forwarded DL data packets from the source eNodeB on the X2 interface are transmitted first to the UE followed by the data received from the telephone network 7 (MME/SAE Gateway on the S1 interface).
From the above discussion it seems desirable to stop the UL and DL data transmission during the handover execution for both RT and NRT Services to support lossless Inter eNodeB handover, while aiming to keep the interruption time and transmission of duplicate packets to a minimum.
Glossary of 3GPP Terms
  • LTE—Long Term Evolution (of UTRAN)
  • eNodeB—E-UTRAN Node B
  • AGW—Access Gateway
  • UE—User Equipment—mobile communication device
  • DL—downlink—link from base to mobile
  • UL—uplink—link from mobile to base
  • AM—Acknowledge Mode
  • UM—Unacknowledged Mode
  • MME—Mobility Management Entity
  • UPE—User Plane Entity
  • HO—Handover
  • RLC—Radio Link Control
  • RRC—Radio Resource Control
  • RRM—Radio Resource Management
  • SDU—Service Data Unit
  • PDU—Protocol Data Unit
  • NAS—Non Access Stratum
  • ROHC—Robust Header Compression
  • TA—Tracking Area
  • U-plane—User Plane
  • TNL—Transport Network Layer
  • S1 Interface—Interface between Access Gateway and eNodeB
  • X2 Interface—Interface between two eNodeB
  • MMEs/SAE Gateway—New name for Access Gateway having both MME and UPE entities
The following is a detailed description of the way in which the present inventions may be implemented in the currently proposed 3GPP LTE standard. Whilst various features are described as being essential or necessary, this may only be the case for the proposed 3GPP LTE standard, for example due to other requirements imposed by the standard. These statements should not, therefore, be construed as limiting the present invention in any way.
This application is based upon and claims the benefit of priority from UK patent application No. 0708455.1, filed on May 1, 2007, the disclosure of which is incorporated herein in its entirety by reference.
REFERENCES
  • [1] R2-062754, “PDCP/RLC/MAC PDU structure”, Nokia
  • [2] R2-062800, “Sequence Numbering & Reuse of PDCP SN”, InterDigital
  • [3] R2-063389, Inter-eNB Handover (UP), NTT DoCoMo

Claims (11)

The invention claimed is:
1. A source base station comprising:
a controller; and
a transceiver circuit, wherein the controller is operable to:
control the transceiver circuit to receive data from a user equipment (UE);
process, in a radio link control (RLC) layer, the received data to form RLC service data units (SDUs);
deliver the RLC SDUs from the RLC layer to a Packet Data Convergence Protocol (PDCP) layer, each RLC SDU corresponding to a respective PDCP protocol data unit (PDU) in the PDCP layer;
process, in the PDCP layer, PDCP PDUs to form PDCP SDUs;
control the transceiver circuit to deliver the PDCP SDUs to a communication network;
control, during handover, the transceiver circuit to send a status report including a PDCP Sequence Number for identifying a first missing uplink SDU and information identifying any out-of-sequence PDCP SDUs that need to be transmitted in a target cell to a target base station; and
control the transceiver circuit to forward, to the target base station, out-of-sequence PDCP SDUs after sending the status report.
2. The source base station according to claim 1, wherein said PDCP Sequence Number is associated with a mobile communication device.
3. The source base station according to claim 1, wherein said transceiver circuit synchronizes data transmission status between the source base station and the target base station.
4. The source base station according to claim 3, wherein said transceiver circuit synchronizes data transmission status between the source base station and the target base station on sending the status report.
5. The source base station according to claim 1, wherein the out-of-sequence PDCP SDUs forwarded to the target base station comprise out-of-sequence uplink PDCP SDUs, and wherein each PDCP SDU is identified by an associated PDCP Sequence Number.
6. A system comprising:
the source base station according to claim 1;
a target base station; and
a mobile communication device.
7. A method performed by a source base station, the method comprising:
receiving data from a user equipment (UE);
processing, in a radio link control (RLC) layer, the received data to form RLC service data units (SDUs);
delivering the RLC SDUs from the RLC layer to a Packet Data Convergence Protocol (PDCP) layer, each RLC SDU corresponding to a respective PDCP protocol data unit (PDU) in the PDCP layer;
processing, in the PDCP layer, PDCP PDUs to form PDCP SDUs;
delivering the PDCP SDUs to a communication network;
sending, during handover, a status report including a PDCP Sequence Number for identifying a first missing uplink SDU and information identifying any out-of-sequence PDCP SDUs that need to be transmitted in a target cell to a target base station; and
forwarding, to the target base station, out-of-sequence PDCP SDUs after sending the status report.
8. The method according to claim 7, wherein said PDCP Sequence Number is associated with a mobile communication device.
9. The method according to claim 7, comprising synchronizing data transmission status between the source base station and the target base station.
10. The method according to claim 9, comprising synchronizing data transmission status between the source base station and the target base station on sending the status report.
11. The method according to claim 7, wherein the out-of-sequence PDCP SDUs forwarded to the target base station comprise out-of-sequence uplink PDCP SDUs, and wherein each PDCP SDU is identified by an associated PDCP Sequence Number.
US15/863,029 2007-05-01 2018-01-05 Handover handling Active US10743220B2 (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
US15/863,029 US10743220B2 (en) 2007-05-01 2018-01-05 Handover handling
US16/922,780 US11778521B2 (en) 2007-05-01 2020-07-07 Handover handling

Applications Claiming Priority (7)

Application Number Priority Date Filing Date Title
GB0708455A GB2449629A (en) 2007-05-01 2007-05-01 Buffering numbered unsegmented PDCP SDUs in 3GPP system to assist efficient hard handover
GB0708455.1 2007-05-01
PCT/JP2008/058589 WO2008140028A1 (en) 2007-05-01 2008-04-30 Handover handling
US45116609A 2009-10-28 2009-10-28
US13/543,402 US20120327901A1 (en) 2007-05-01 2012-07-06 Handover handling
US14/643,642 US9894567B2 (en) 2007-05-01 2015-03-10 Handover handling
US15/863,029 US10743220B2 (en) 2007-05-01 2018-01-05 Handover handling

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/643,642 Continuation US9894567B2 (en) 2007-05-01 2015-03-10 Handover handling

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US16/922,780 Continuation US11778521B2 (en) 2007-05-01 2020-07-07 Handover handling

Publications (2)

Publication Number Publication Date
US20180132142A1 US20180132142A1 (en) 2018-05-10
US10743220B2 true US10743220B2 (en) 2020-08-11

Family

ID=38171035

Family Applications (6)

Application Number Title Priority Date Filing Date
US12/451,166 Active 2029-08-25 US9001781B2 (en) 2007-05-01 2008-04-30 Handover handling
US13/543,402 Abandoned US20120327901A1 (en) 2007-05-01 2012-07-06 Handover handling
US14/643,642 Active US9894567B2 (en) 2007-05-01 2015-03-10 Handover handling
US15/677,845 Active US10764793B2 (en) 2007-05-01 2017-08-15 Handover handling
US15/863,029 Active US10743220B2 (en) 2007-05-01 2018-01-05 Handover handling
US16/922,780 Active 2028-07-17 US11778521B2 (en) 2007-05-01 2020-07-07 Handover handling

Family Applications Before (4)

Application Number Title Priority Date Filing Date
US12/451,166 Active 2029-08-25 US9001781B2 (en) 2007-05-01 2008-04-30 Handover handling
US13/543,402 Abandoned US20120327901A1 (en) 2007-05-01 2012-07-06 Handover handling
US14/643,642 Active US9894567B2 (en) 2007-05-01 2015-03-10 Handover handling
US15/677,845 Active US10764793B2 (en) 2007-05-01 2017-08-15 Handover handling

Family Applications After (1)

Application Number Title Priority Date Filing Date
US16/922,780 Active 2028-07-17 US11778521B2 (en) 2007-05-01 2020-07-07 Handover handling

Country Status (9)

Country Link
US (6) US9001781B2 (en)
EP (3) EP2472954B1 (en)
JP (7) JP5099383B2 (en)
KR (2) KR101346514B1 (en)
CN (2) CN103200632B (en)
ES (1) ES2745741T3 (en)
GB (1) GB2449629A (en)
TR (1) TR201909799T4 (en)
WO (1) WO2008140028A1 (en)

Families Citing this family (57)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2449629A (en) 2007-05-01 2008-12-03 Nec Corp Buffering numbered unsegmented PDCP SDUs in 3GPP system to assist efficient hard handover
US8488553B2 (en) * 2008-06-05 2013-07-16 Alcatel Lucent Method for providing seamless transition between networks following different protocols
KR101402801B1 (en) * 2008-06-27 2014-06-02 삼성전자주식회사 Method and apparatus for the reduction of serving cell change delay in mobile telecommunication system supporting hsdpa
CN101841853A (en) * 2009-03-17 2010-09-22 中兴通讯股份有限公司 User equipment and downlink data receiving method thereof
US8228871B2 (en) * 2009-03-19 2012-07-24 Telefonaktiebolaget Lm Ericsson (Publ) Wireless handover optimization
US8379547B2 (en) 2009-05-15 2013-02-19 Telefonaktiebolaget L M Ericsson (Publ) Resource selection for transmission of multiple ACK/NACK on PUCCH channel
CN102076033B (en) * 2009-11-23 2015-01-28 中兴通讯股份有限公司 Method and system for switching base station by integrally using inner ring and outer ring modes
US8891356B2 (en) 2010-06-28 2014-11-18 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link RLC sublayer
US8989140B2 (en) 2010-06-28 2015-03-24 Qualcomm Incorporated System and method for mobility in a multi-point HSDPA communication network
US8989004B2 (en) * 2010-11-08 2015-03-24 Qualcomm Incorporated System and method for multi-point HSDPA communication utilizing a multi-link PDCP sublayer
US8737211B2 (en) 2011-08-03 2014-05-27 Qualcomm Incorporated Methods and apparatuses for network configuration of user equipment communication modes in multiflow systems
US9125098B2 (en) 2011-08-03 2015-09-01 Qualcomm Incorporated Method and apparatus for flow congestion control in multiflow networks
US9014023B2 (en) 2011-09-15 2015-04-21 International Business Machines Corporation Mobile network services in a mobile data network
US10681605B2 (en) * 2012-04-20 2020-06-09 Telefonaktiebolaget Lm Ericsson (Publ) Handover for video or other streaming services
US8913556B2 (en) 2012-06-18 2014-12-16 International Business Machines Corporation Reducing packet loss in a mobile data network with data breakout at the edge
CN103533589B (en) * 2012-07-04 2018-03-13 华为技术有限公司 A kind of method for switching network, system and network side equipment
US20140045486A1 (en) 2012-08-07 2014-02-13 International Business Machines Corporation Cooperative mobility management in a mobile data network with data breakout at the edge
CN102833802B (en) 2012-08-15 2015-09-23 电信科学技术研究院 A kind of data forwarding method and equipment
US9019843B2 (en) 2012-09-13 2015-04-28 International Business Machines Corporation Utilizing stored data to reduce packet data loss in a mobile data network with data breakout at the edge
CN109743763B (en) * 2012-09-28 2023-03-31 三菱电机株式会社 Mobile communication system
US8929292B2 (en) 2012-10-04 2015-01-06 International Business Machines Corporation Mobility support in a mobile data network
WO2014067070A1 (en) * 2012-10-30 2014-05-08 华为技术有限公司 Data transmission method, switching method, data transmission apparatus, switching apparatus, user equipment, wireless access node, data transmission system and switching system
EP2947926B1 (en) * 2013-01-18 2017-08-30 Kyocera Corporation Communication control method and user terminal
US9220042B2 (en) 2013-06-25 2015-12-22 Freescale Semiconductor, Inc. Wireless communication apparatus and method
WO2015016550A1 (en) * 2013-07-29 2015-02-05 Lg Electronics Inc. Method for calculating and reporting a buffer status and device therefor
US9970577B2 (en) 2013-09-27 2018-05-15 The Procter & Gamble Company Rotary union
US9838282B2 (en) * 2014-05-09 2017-12-05 Telefonaktiebolaget Lm Ericsson (Publ) PDCP and flow control for split bearer
CN105472667B (en) * 2014-06-23 2020-04-28 索尼公司 Electronic device in wireless communication system and method thereof
CN105453645B (en) * 2014-07-23 2020-01-21 华为技术有限公司 Data packet sending and data processing device and method
US10110713B2 (en) * 2014-09-12 2018-10-23 Samsung Electronics Co., Ltd. Handling different protocol data unit types in a device to device communication system
JP2016092700A (en) * 2014-11-07 2016-05-23 株式会社Ｎｔｔドコモ User device and duplicate packet processing method
EP3238482B1 (en) * 2014-12-22 2019-05-15 Telefonaktiebolaget LM Ericsson (publ) A method for providing an application service in a cellular network
JP6708638B2 (en) * 2015-05-22 2020-06-10 株式会社Ｎｔｔドコモ User equipment, base station, and communication method
KR102419981B1 (en) * 2016-02-19 2022-07-12 삼성전자 주식회사 Apparatus and method for minimizing data interruption time during handover in a wireless network
WO2017152971A1 (en) 2016-03-09 2017-09-14 Telefonaktiebolaget Lm Ericsson (Publ) Assisting resource allocation transfer
CN113423124B (en) * 2016-04-01 2023-10-13 北京三星通信技术研究有限公司 Method for supporting seamless switching and base station equipment
US10178702B2 (en) 2016-06-10 2019-01-08 Futurewei Technologies, Inc. System and method for cell switching
GB2552825B (en) * 2016-08-11 2018-07-25 Tcl Communication Ltd Security enhancements for LTE WLAN aggregation
CN110036683A (en) 2016-10-25 2019-07-19 诺基亚技术有限公司 Anchor reorientation
CN108024295B (en) * 2016-11-03 2022-04-19 中兴通讯股份有限公司 Relay transfer method and device, terminal and base station
JP6728472B2 (en) * 2017-03-07 2020-07-22 エルジー エレクトロニクス インコーポレイティド Method and apparatus for transmitting data in CU-DU split scenario
WO2018194497A1 (en) * 2017-04-21 2018-10-25 Telefonaktiebolaget Lm Ericsson (Publ) Methods and service nodes for transferring a service session for a wireless device
US10582418B2 (en) * 2017-05-05 2020-03-03 Asustek Computer Inc. Method and apparatus of transmitting data duplication in a wireless communication system
CN109246770B (en) * 2017-05-05 2021-06-22 华为技术有限公司 Switching method, terminal equipment and network equipment
US10805836B2 (en) * 2017-05-05 2020-10-13 Qualcomm Incorporated Packet duplication at a packet data convergence protocol (PDCP) entity
US10306526B2 (en) 2017-05-12 2019-05-28 Samsung Electronics Co., Ltd Method and apparatus for controlling handover in a wireless communication system
KR102344917B1 (en) * 2017-06-30 2021-12-30 삼성전자주식회사 Apparatus and method for handover in wireless communication system
US10869223B2 (en) 2018-02-13 2020-12-15 Samsung Electronics Co., Ltd. Method and apparatus for efficient operation upon packet duplication activation and deactivation in next generation wireless communication system
US11129234B2 (en) 2018-02-13 2021-09-21 FG Innovation Company Limited Methods for packet data convergence protocol (PDCP) duplication operations and devices using the same
KR102598001B1 (en) * 2018-06-18 2023-11-06 삼성전자 주식회사 A method and apparatus for efficient packet duplication transmission in a mobile communication system
JP6636115B1 (en) 2018-10-22 2020-01-29 株式会社アマダホールディングス Laser processing machine and laser processing method
CN111200850B (en) * 2018-11-19 2022-04-05 华为技术有限公司 Communication method and device
WO2020150997A1 (en) * 2019-01-25 2020-07-30 Mediatek Singapore Pte. Ltd. Apparatus and methods to support dual-protocol for mobility enhancement
KR102160005B1 (en) * 2019-04-18 2020-09-25 한국전자통신연구원 Method of transmitting low-latency data during handover in communication system, and apparatus therefor
WO2021012168A1 (en) 2019-07-22 2021-01-28 Nokia Shanghai Bell Co., Ltd. Transmission of segments of information
CN111800832B (en) * 2019-08-01 2021-09-17 维沃移动通信有限公司 Data transmission method, User Equipment (UE) and medium
US11229083B1 (en) * 2020-09-03 2022-01-18 Verizon Patent And Licensing Inc. Systems and methods for user equipment-initiated connection release

Citations (45)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940371A (en) 1995-12-01 1999-08-17 Nokia Mobile Phones Ltd. Maintaining the composition of transferred data during handover
US20010030965A1 (en) 2000-02-14 2001-10-18 Nokia Mobile Phones Ltd. Data packet numbering in packet-switched data transmission
US20010043579A1 (en) 2000-04-07 2001-11-22 Ari Tourunen Data packet numbering in packet-switched data transmission
US20020001298A1 (en) 2000-06-28 2002-01-03 Ari Tourunen Allocating data transmission resources in packet-switched data transmission
WO2002015524A1 (en) 2000-08-14 2002-02-21 Nokia Corporation Synchronization of data packet numbers in packet-switched data transmission
US20020094814A1 (en) 2001-01-16 2002-07-18 Toomas Wigell Automatic repetition request mechanism in a radio access network
US20030007490A1 (en) 2001-07-09 2003-01-09 Lg Electronics Inc. Packet data service in radio communication system
US20030012179A1 (en) 2001-07-13 2003-01-16 Masashi Yano Mobile communication system
US20030022654A1 (en) 2001-07-27 2003-01-30 Kakani Naveen Kumar Apparatus, and associated method, for transferring data between a first target entity and a second target entity of a mobile radio communication system
US20030157927A1 (en) 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
EP1343267A2 (en) 2002-02-08 2003-09-10 ASUSTeK Computer Inc. Data transmission confirmation in a wireless communication system
US20030169725A1 (en) 2000-05-17 2003-09-11 Kalle Ahmavaara Connections in a comunication system
US20030176187A1 (en) 2000-08-10 2003-09-18 Christian Menzel Method and installation for executing a handover in mobile data transmission systems using data duplication
US20030189909A1 (en) 2002-04-05 2003-10-09 Interdigital Technology Corporation System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
US20030206534A1 (en) 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
US20030210676A1 (en) 2002-05-10 2003-11-13 Chih-Hsiang Wu Method for determining triggering of a pdcp sequence number synchronization procedure
US20040052229A1 (en) 2002-09-12 2004-03-18 Interdigital Technology Corporation System for efficient recovery of Node-B buffered data following MAC layer reset
US20050094586A1 (en) 2003-11-05 2005-05-05 Interdigital Technology Corporation Wireless communication method and system for supporting an enhanced uplink dedicated channel inter-node-B serving cell change
US20050141477A1 (en) 2002-09-24 2005-06-30 Tetsuo Tomita Packet transferring/transmitting method and mobile communication system
CN1669350A (en) 2002-09-24 2005-09-14 富士通株式会社 Data packet transferring/transmitting method and mobile communication system
US20050237976A1 (en) 2002-05-23 2005-10-27 Thomas Walldeen Data preservation
US20060098574A1 (en) 2000-10-07 2006-05-11 Lg Electronics Inc. Method for transmitting data from RLC layer in radio communication system
EP1686736A1 (en) 2005-01-26 2006-08-02 M-Stack Limited An improved method for processing traffic data in a wireless communications system
US20070047452A1 (en) 2005-08-16 2007-03-01 Matsushita Electric Industrial Co., Ltd. MAC layer reconfiguration in a mobile communication system
US20070171857A1 (en) 2005-12-22 2007-07-26 Interdigital Technology Corporation Method and apparatus for data security and automatic repeat request implementation in a wireless communication system
US20070275746A1 (en) 2006-05-25 2007-11-29 Altair Semiconductor Multi-function wireless terminal
US20070286125A1 (en) 2006-03-27 2007-12-13 Nec Corporation Method and system for transmitting data in mobile communications system
US20070291695A1 (en) 2006-05-01 2007-12-20 Interdigital Technology Corporation Method and apparatus for facilitating lossless handover in 3gpp long term evolution systems
US20080019320A1 (en) 2006-07-18 2008-01-24 Nokia Corporation Method, device, computer program, and apparatus providing embedded status information in handover control signaling
WO2008023814A2 (en) 2006-08-22 2008-02-28 Nec Corporation Buffering of packets for a lossless handover
US20080119189A1 (en) 2006-09-28 2008-05-22 Huawei Technologies Co., Ltd. Method, system and base station for transmitting data during cell handover
US20080205394A1 (en) 2007-02-28 2008-08-28 Deshpande Sachin G Overlay join latency reduction using preferred peer list
US20080254800A1 (en) 2005-10-31 2008-10-16 Sung-Duck Chun Data Transfer Management in a Radio Communications Network
US20080268850A1 (en) 2007-04-30 2008-10-30 Motorola, Inc. Method and apparatus for handover in a wireless communication system
US20080298322A1 (en) 2006-01-05 2008-12-04 Sung Duck Chun Data Transmission Method and Data Re-Transmission Method
US7512099B2 (en) 2003-12-05 2009-03-31 Nokia Siemens Networks Oy Method, system and transmitting side protocol entity for sending packet data units for unacknowledged mode services
US7512104B2 (en) 2002-02-11 2009-03-31 Telefonaktiebolaget L M Ericsson (Publ) Resolving hanging contexts when roaming in a GPRS network
WO2009045945A2 (en) 2007-10-01 2009-04-09 Interdigital Patent Holdings, Inc. Method and apparatus for pcdp discard
US20100067483A1 (en) 2007-05-01 2010-03-18 Jagdeep Singh Ahluwalia Handover handling
US20100091709A1 (en) 2007-03-19 2010-04-15 Seung-June Yi Method for processing radio protocol in mobile telecommunications system and transmitter of mobile telecommunications
US20100135249A1 (en) 2007-04-25 2010-06-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Seamless Handover in a Wireless Communication Network
US20100227614A1 (en) 2006-03-22 2010-09-09 Sung Duck Chun Method of supporting handover in a wirwless communication system
US20100232391A1 (en) 2007-02-06 2010-09-16 Lars-Bertil Olsson Method And System For Intra E-Utran Handover
US7848752B2 (en) 2003-01-29 2010-12-07 Samsung Electronics Co., Ltd. Short-range wireless communication system and a handoff processing method therefor
US9894576B2 (en) * 2006-08-15 2018-02-13 Huawei Technologies Co., Ltd. Method and system for transferring user equipment in mobile communication system

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US2679241A (en) 1950-11-17 1954-05-25 Gen Motors Corp Cylinder head gasket construction
SE0400163D0 (en) * 2004-01-28 2004-01-28 Ericsson Telefon Ab L M Method and systems of radio communications
US7693521B1 (en) * 2004-08-04 2010-04-06 Sprint Spectrum L.P. Method and system for mobile station handoff
US9247515B2 (en) * 2006-04-25 2016-01-26 Qualcomm Incorporated Enhanced mobility support for wireless communication

Patent Citations (73)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5940371A (en) 1995-12-01 1999-08-17 Nokia Mobile Phones Ltd. Maintaining the composition of transferred data during handover
US20010030965A1 (en) 2000-02-14 2001-10-18 Nokia Mobile Phones Ltd. Data packet numbering in packet-switched data transmission
US6930980B2 (en) 2000-04-07 2005-08-16 Nokia Mobile Phones Ltd. Data packet numbering in packet-switched data transmission
US20010043579A1 (en) 2000-04-07 2001-11-22 Ari Tourunen Data packet numbering in packet-switched data transmission
JP2003530764A (en) 2000-04-07 2003-10-14 ノキア コーポレイション Data packet numbering in packet-switched data transmission
US20030169725A1 (en) 2000-05-17 2003-09-11 Kalle Ahmavaara Connections in a comunication system
US20020001298A1 (en) 2000-06-28 2002-01-03 Ari Tourunen Allocating data transmission resources in packet-switched data transmission
US20030176187A1 (en) 2000-08-10 2003-09-18 Christian Menzel Method and installation for executing a handover in mobile data transmission systems using data duplication
WO2002015524A1 (en) 2000-08-14 2002-02-21 Nokia Corporation Synchronization of data packet numbers in packet-switched data transmission
US20030165161A1 (en) 2000-08-14 2003-09-04 Nokia Corporation Synchronization of data packet numbers in packet-switched data transmission
US20060098574A1 (en) 2000-10-07 2006-05-11 Lg Electronics Inc. Method for transmitting data from RLC layer in radio communication system
US20020094814A1 (en) 2001-01-16 2002-07-18 Toomas Wigell Automatic repetition request mechanism in a radio access network
US7327734B2 (en) 2001-07-09 2008-02-05 Lg Electronics Inc. Packet data service in radio communication system
US7756135B2 (en) 2001-07-09 2010-07-13 Lg Electronics Inc. Packet data service in radio communication system
JP2003111148A (en) 2001-07-09 2003-04-11 Lg Electronics Inc Packet data convergence protocol structure (pdcp) of radio communication system and its method
US20030007490A1 (en) 2001-07-09 2003-01-09 Lg Electronics Inc. Packet data service in radio communication system
US20030012179A1 (en) 2001-07-13 2003-01-16 Masashi Yano Mobile communication system
US20030022654A1 (en) 2001-07-27 2003-01-30 Kakani Naveen Kumar Apparatus, and associated method, for transferring data between a first target entity and a second target entity of a mobile radio communication system
EP1343267A2 (en) 2002-02-08 2003-09-10 ASUSTeK Computer Inc. Data transmission confirmation in a wireless communication system
US20040151154A1 (en) 2002-02-08 2004-08-05 Wu Frank Chih-Hsiang Data transmission confirmation in a wireless communication system
JP2003283592A (en) 2002-02-08 2003-10-03 Asustek Computer Inc Data transmission confirmation method in wireless communication system
US7512104B2 (en) 2002-02-11 2009-03-31 Telefonaktiebolaget L M Ericsson (Publ) Resolving hanging contexts when roaming in a GPRS network
US20030157927A1 (en) 2002-02-16 2003-08-21 Lg Electronics Inc. Method for relocating SRNS in a mobile communication system
US20160112912A1 (en) 2002-04-05 2016-04-21 Intel Corporation Hs-dsch inter-node b cell change
US6717927B2 (en) 2002-04-05 2004-04-06 Interdigital Technology Corporation System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
US20120170550A1 (en) 2002-04-05 2012-07-05 Interdigital Technology Corporation Hs-dsch inter-node b cell change
US20140362826A1 (en) 2002-04-05 2014-12-11 Yi-Ju Chao Hs-dsch inter-node b cell change
US20040165554A1 (en) 2002-04-05 2004-08-26 Interdigital Technology Corporation System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
US20030189909A1 (en) 2002-04-05 2003-10-09 Interdigital Technology Corporation System for efficient recovery of node B buffered data following serving high speed downlink shared channel cell change
US20060126567A1 (en) 2002-04-05 2006-06-15 Interdigital Technology Corporation High speed downlink shared control channel cell change
US20060153137A1 (en) 2002-04-05 2006-07-13 Interdigital Technology Corporation High speed downlink shared control channel cell change
US20060256745A1 (en) 2002-04-05 2006-11-16 Interdigital Technology Corporation HS-DSCH inter-node B cell change
US20030206534A1 (en) 2002-05-03 2003-11-06 Wu Frank Chih-Hsiang Scheme to handle radio link control service data units upon reception of a radio link control reset or reset acknowledge protocol data unit in a wireless communication system
JP2003333671A (en) 2002-05-10 2003-11-21 Asustek Computer Inc Method for determining triggering of pdcp sequence number synchronization procedure
US20030210676A1 (en) 2002-05-10 2003-11-13 Chih-Hsiang Wu Method for determining triggering of a pdcp sequence number synchronization procedure
US20050237976A1 (en) 2002-05-23 2005-10-27 Thomas Walldeen Data preservation
US20040052229A1 (en) 2002-09-12 2004-03-18 Interdigital Technology Corporation System for efficient recovery of Node-B buffered data following MAC layer reset
US7706405B2 (en) 2002-09-12 2010-04-27 Interdigital Technology Corporation System for efficient recovery of Node-B buffered data following MAC layer reset
CN1669350A (en) 2002-09-24 2005-09-14 富士通株式会社 Data packet transferring/transmitting method and mobile communication system
US20050141477A1 (en) 2002-09-24 2005-06-30 Tetsuo Tomita Packet transferring/transmitting method and mobile communication system
US8254935B2 (en) 2002-09-24 2012-08-28 Fujitsu Limited Packet transferring/transmitting method and mobile communication system
US7848752B2 (en) 2003-01-29 2010-12-07 Samsung Electronics Co., Ltd. Short-range wireless communication system and a handoff processing method therefor
US20050094586A1 (en) 2003-11-05 2005-05-05 Interdigital Technology Corporation Wireless communication method and system for supporting an enhanced uplink dedicated channel inter-node-B serving cell change
US7512099B2 (en) 2003-12-05 2009-03-31 Nokia Siemens Networks Oy Method, system and transmitting side protocol entity for sending packet data units for unacknowledged mode services
EP1686736A1 (en) 2005-01-26 2006-08-02 M-Stack Limited An improved method for processing traffic data in a wireless communications system
US7321589B2 (en) 2005-08-16 2008-01-22 Matsushita Electric Industrial Co., Ltd. MAC layer reconfiguration in a mobile communication system
US20070047452A1 (en) 2005-08-16 2007-03-01 Matsushita Electric Industrial Co., Ltd. MAC layer reconfiguration in a mobile communication system
US20080254800A1 (en) 2005-10-31 2008-10-16 Sung-Duck Chun Data Transfer Management in a Radio Communications Network
US8406767B2 (en) 2005-10-31 2013-03-26 Lg Electronics Inc. Data transfer management in a radio communications network
US20070171857A1 (en) 2005-12-22 2007-07-26 Interdigital Technology Corporation Method and apparatus for data security and automatic repeat request implementation in a wireless communication system
US20080298322A1 (en) 2006-01-05 2008-12-04 Sung Duck Chun Data Transmission Method and Data Re-Transmission Method
US20100227614A1 (en) 2006-03-22 2010-09-09 Sung Duck Chun Method of supporting handover in a wirwless communication system
US20070286125A1 (en) 2006-03-27 2007-12-13 Nec Corporation Method and system for transmitting data in mobile communications system
US20070291695A1 (en) 2006-05-01 2007-12-20 Interdigital Technology Corporation Method and apparatus for facilitating lossless handover in 3gpp long term evolution systems
US20070275746A1 (en) 2006-05-25 2007-11-29 Altair Semiconductor Multi-function wireless terminal
US20080019320A1 (en) 2006-07-18 2008-01-24 Nokia Corporation Method, device, computer program, and apparatus providing embedded status information in handover control signaling
US9894576B2 (en) * 2006-08-15 2018-02-13 Huawei Technologies Co., Ltd. Method and system for transferring user equipment in mobile communication system
WO2008023814A2 (en) 2006-08-22 2008-02-28 Nec Corporation Buffering of packets for a lossless handover
US20080119189A1 (en) 2006-09-28 2008-05-22 Huawei Technologies Co., Ltd. Method, system and base station for transmitting data during cell handover
US20100232391A1 (en) 2007-02-06 2010-09-16 Lars-Bertil Olsson Method And System For Intra E-Utran Handover
US20080205394A1 (en) 2007-02-28 2008-08-28 Deshpande Sachin G Overlay join latency reduction using preferred peer list
US20100091709A1 (en) 2007-03-19 2010-04-15 Seung-June Yi Method for processing radio protocol in mobile telecommunications system and transmitter of mobile telecommunications
US8265628B2 (en) 2007-04-25 2012-09-11 Telefonaktiebolaget Lm Ericsson (Publ) Method and apparatus for seamless handover in a wireless communication network
JP2010525737A (en) 2007-04-25 2010-07-22 テレフオンアクチーボラゲット エル エム エリクソン（パブル） Method and apparatus for seamless handover in a wireless communication network
US20100135249A1 (en) 2007-04-25 2010-06-03 Telefonaktiebolaget Lm Ericsson (Publ) Method and Apparatus for Seamless Handover in a Wireless Communication Network
US20080268850A1 (en) 2007-04-30 2008-10-30 Motorola, Inc. Method and apparatus for handover in a wireless communication system
JP2010525618A (en) 2007-05-01 2010-07-22 日本電気株式会社 Handover processing
US20100067483A1 (en) 2007-05-01 2010-03-18 Jagdeep Singh Ahluwalia Handover handling
US9001781B2 (en) 2007-05-01 2015-04-07 Nec Corporation Handover handling
US20150023370A1 (en) 2007-10-01 2015-01-22 Interdigital Patent Holdings, Inc. Method and apparatus for pcdp discard
US20090103478A1 (en) 2007-10-01 2009-04-23 Interdigital Patent Holdings, Inc. Method and apparatus for pcdp discard
US20170237837A1 (en) 2007-10-01 2017-08-17 Interdigital Patent Holdings, Inc. Method and Apparatus for PCDP Discard
WO2009045945A2 (en) 2007-10-01 2009-04-09 Interdigital Patent Holdings, Inc. Method and apparatus for pcdp discard

Non-Patent Citations (36)

* Cited by examiner, † Cited by third party
Title
3GPP 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (EUTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release x), 3GPP TS 25.xxx V0.0.2 (Jul. 2006), pp. 1-40 (40 pages).
3GPP TS 36.300 V8.1.0 (Jun. 2007) Technical Specification, 3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN); Overall description; Stage 2 (Release 8), Jun. 2007 (106 pages).
Chinese Office Action corresponding to Chinese Application No. 2013100260112, dated Feb. 12, 2015 (8 pages).
Chinese Office Action Issued by the Chinese Patent Office for Chinese Application No. 201310026011.2, dated Feb. 12, 2015 (8 pages).
Ericsson, "Sequence numbers on S1 and X2," 3GPP TSG-RAN WG3 #53bis, R3-061492, Agenda Item 7.2.4, Seoul, Korea, Oct. 10-13, 2006 (4 pages).
European Communication Pursuant to Article 94(3) EPC issued in corresponding European Patent Application No. 08752475.7, dated Sep. 16, 2016 (7 pages).
European Search Report corresponding to European Patent Application No. 12158818.0, dated Jun. 1, 2012 (10 pages).
Extended European Search Report corresponding to European Application No. 17182454.3 dated Nov. 8, 2017 (11 pages).
Fujitsu, "Handling re-ordering in LTE during Handover," 3GPP TSG RAN WG3 Meeting #55-bis, R3-070681, Agenda Item 7.3, Malta, Mar. 27-31, 3 pages (2007).
Inter Digital Communication, Intra-LTE Handover Contest Transfer and Data Forwarding, 3GGPP TSG RAN3#52, R3-060751, pp. 1-11 (2006).
Inter Digital Communications Corporation: "R2-062800 Sequence Numbering & Reuse of PDCP SN," Oct. 9-13, 2006, Seoul Korea, 3GPP TSG RAN WG2 #55 (6 pages).
Japan Notice of Reasons for Refusal issued in Japanese Patent Application No. 2018-152323, dated Aug. 20, 2019, 6 pages.
Japanese Notice of Reasons for Refusal issued in Japanese Patent Application No. 2018-152323, dated May 14, 2019, 6 pages.
Japanese Office Action corresponding to Japanese Patent Application No. 2012-12497 dated Sep. 11, 2013 (2 pages).
Japanese Office Action corresponding to Japanese Patent Application No. 2014-092445 dated Feb. 4, 2015 (4 pages).
Japanese Office Action corresponding to Japanese Patent Application No. 2015-20079 dated Jul. 6, 2016 (12 pages).
Japanese Office Action corresponding to JP 2009-545756 dated Apr. 4, 2012, with partial English language translation (4 pages).
Korean Office Action corresponding to Korean Patent Application No. 10-2011-7016285, dated Apr. 4, 2013 (3 pages).
LG Electronics, Inc., "L2 Architecture for LTE," 3GPP TSG-RAN WG2 #57bis, R2-071491, St. Julian's, Malta, Mar. 26-30, 2007 (pp. 1-4).
NEC "Lossless Intra-LTE Handover", 3GPP TSG RAN3#53, R3-0601088, Tallinn, Estonia, Aug. 28-Sep. 1, 2006, 7 pages.
NEC, "R3-0601088 Lossless Intra-LTE Handover," Aug. 28-Sep. 1, 2006, Tallin, Estonia, 3GPP TSG RAN3 #53 (7 pages).
Nokia "Way Forward for User Plane Data Handling and Ciphering Location", 3GPP TSG-RAN WG2 Meeting #57bis, R2-071590, St. Julian's, Malta Mar. 26-30, 2007, 5 pages.
Nokia, "R2-062754 PDCP/RLC/MAC PDU structure", Oct. 9-13, 2006, Seoul, Korea, 3GPP TSG-RAN WG2 Meeting #55, (9 pages).
NTT DoCoMo, Inc., "E-mail discussion on data handling at handover," 3GPP TSG RAN Wg2 #57bis RS-071294, Mar. 23, 2007 (11 pages).
NTT DoCoMo, Inc., "E-mail discussion on data handling at handover," 3GPP TSG RAN WG2 #57bis, Tdoc R2-071294, St. Julian's, Malta, Mar. 26-30, 2007 (11 pages).
NTT DoCoMo, Inc., "R2-063389 Inter-eNB Handover (UP)," Nov. 6-10, 2006, Riga, Latvia, TSG-RAN WG2 meeting #56 (5 pages).
Qualcomm Europe "Data forwarding with PDCP located in eNB," 3GPP TSG RAN WG2 #57, Feb. 12-16, 2007, St. Louis, Missouri, USA, R2-070850 (4 pages).
Samsung, "R2-061829 Re-use of PDCP SN at ARQ level?" Jun. 27-30, 2006, Cannes, France, 3GPP TSG-RAN2 Meeting #53 Bis, (9 pages).
Siemens, "3GPP TSG RAN WG3 Meeting #51," R3-060267, Denver, Colorado, U.S., Feb. 13-17, 2006 (8pages).
Siemens, "SDU Forwarding During Intra-LTe Hand-Over," 3GPP TSG Ran WG3 Meeting #52, R3-060775, Agenda Item 12.15.2, Shanghai, China, Apr. 8-12, 2006 (3 pages).
TSG-RAN Working Group 2 #55, "Data Handling for Handover," R2-062967, Seoul, Korea, Oct. 9-13, 2006 (3 pages).
U.S. Office Action issued by the United States Patent and Trademark Office for the U.S. Appl. No. 15/677,845 dated Nov. 9, 2018 (19 pages).
Universal Mobile Telecommunications System (UMTS), "Packet Data Convergence protocol (PDCP) specification (3GPP TS 25.323 version 7.4.0 Release 7); ETSI TS 125 323," ETSI Standards, LIS, Sophia Antipolis Cedex, France, vol. 3-R2, No. V7.4.0, (2007).
Universal Mobile Telecommunications System (UMTS); Feasibility Study for Evolved Universal Terrestrial Radio Access (UTRA) and Universal Terrestrial Radio Access Network (UTRAN), (3GPP TR 25.912 Version 7.1.0 Release 7), ETSI Standards, LIS, Sophia Antipolis Cedex, France, No. V7.1.0, Jan. 1, 2006 (58 pages).
Yi et al., "Method for processing radio protocol in mobile telecommunication system and transmitter of mobile telecommunications," U.S. Appl. No. 60/895,720, 133 pages (2006).
Yi et al., "Method for processing radio protocol in mobile telecommunication system and transmitter of mobile telecommunications," U.S. Appl. No. 60/896,474, 135 pages (2006).

Also Published As

Publication number Publication date
EP2143295A1 (en) 2010-01-13
US11778521B2 (en) 2023-10-03
US20100067483A1 (en) 2010-03-18
EP3253119A1 (en) 2017-12-06
JP2017085669A (en) 2017-05-18
JP2012186848A (en) 2012-09-27
WO2008140028A1 (en) 2008-11-20
US10764793B2 (en) 2020-09-01
US20180132142A1 (en) 2018-05-10
GB2449629A (en) 2008-12-03
JP2014158293A (en) 2014-08-28
KR101126901B1 (en) 2012-03-20
JP2021013202A (en) 2021-02-04
KR20110097949A (en) 2011-08-31
US20180014228A1 (en) 2018-01-11
CN101675684B (en) 2013-07-31
JP5541469B2 (en) 2014-07-09
CN103200632A (en) 2013-07-10
US9001781B2 (en) 2015-04-07
ES2745741T3 (en) 2020-03-03
KR101346514B1 (en) 2013-12-31
JP2018198451A (en) 2018-12-13
CN101675684A (en) 2010-03-17
US20200336951A1 (en) 2020-10-22
JP2016036173A (en) 2016-03-17
EP2143295B1 (en) 2019-05-22
TR201909799T4 (en) 2019-07-22
JP2010525618A (en) 2010-07-22
US20150189555A1 (en) 2015-07-02
EP2472954B1 (en) 2019-06-19
US9894567B2 (en) 2018-02-13
US20120327901A1 (en) 2012-12-27
JP5099383B2 (en) 2012-12-19
EP2472954A1 (en) 2012-07-04
GB0708455D0 (en) 2007-06-06
CN103200632B (en) 2016-04-27
JP7060057B2 (en) 2022-04-26
KR20100007946A (en) 2010-01-22

Similar Documents

Publication Publication Date Title
US11778521B2 (en) Handover handling
US10484912B2 (en) Facilitating method for handover of a mobile communication device

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STPP Information on status: patent application and granting procedure in general

Free format text: NON FINAL ACTION MAILED

STPP Information on status: patent application and granting procedure in general

Free format text: RESPONSE TO NON-FINAL OFFICE ACTION ENTERED AND FORWARDED TO EXAMINER

STPP Information on status: patent application and granting procedure in general

Free format text: FINAL REJECTION MAILED

STCV Information on status: appeal procedure

Free format text: NOTICE OF APPEAL FILED

STPP Information on status: patent application and granting procedure in general

Free format text: NOTICE OF ALLOWANCE MAILED -- APPLICATION RECEIVED IN OFFICE OF PUBLICATIONS

STCF Information on status: patent grant

Free format text: PATENTED CASE

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 4TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1551); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 4