IP Library Granted Patent US 8,687,590
Granted Patent B2
US 8,687,590 · App. 12/573,014 · Granted Apr 1, 2014

System and method for handover between relays

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,687,590
App. No.
12/573,014
Granted
Apr 1, 2014
Kind
B2
Abstract

A method is provided for handing over a user equipment (UE). The method includes a donor access node with which the UE is in communication via a serving relay node receiving UE context information. The method further includes the donor access node using the UE context information to identify data packets that belong to the UE, wherein the data packets are forwarded from the serving relay node to a target relay node.

Claims (64)

1. A method for handing over a user equipment (UE), comprising:

a donor access node with which the UE is in communication via a serving relay node receiving UE context information; and

the donor access node using the UE context information to identify data packets that belong to the UE, wherein the data packets are forwarded from the serving relay node to a target relay node,

wherein, if relay node radio bearer context is not included in the UE handover context information, the donor access node performs a brute-force search inside each Packet Data Convergence Protocol queue of the serving relay node, based on General packet Radio Service (GPRS) Tunneling Protocol (GTP)/User Datagram Protocol (UDP)/Internet Protocol (IP) headers or a subset of GTP/UDP/IP headers, to identify the data packets that belong to the UE.

2. The method of claim 1 , wherein a target access node with which the target relay node is in communication forwards data to the target relay node after the UE completes a handover procedure to the target relay node.

3. The method of claim 2 , wherein the target access node begins forwarding data to the target relay node after receiving one of:

a handover complete message; and

an RRC reconfiguration complete message.

4. The method of claim 2 , wherein the serving access node begin forwarding data to the target relay node or the target access node after receiving a Handover Command acknowledgement message.

5. The method of claim 1 , wherein, if an S1 interface with a serving gateway/packet data network gateway terminates at the serving relay node, the UE context information includes at least one of:

a serving relay node cell global identifier;

a donor access node identifier;

security context information; and

at least one UE bearer tunnel endpoint identifier.

6. The method of claim 5 , wherein the UE context information further includes serving relay node radio bearer configuration information.

7. The method of claim 6 , wherein the donor access node, based on the relay node radio bearer configuration information, identifies a Packet Data Convergence Protocol queue of the serving relay node to which the UE belongs and checks GTP/UDP/IP headers or a subset of GTP/UDP/IP headers of each data packet to identify the data packets that belong to the UE.

8. The method of claim 1 , wherein the UE context information passes from the serving relay node to the target relay node in a Handover request message.

9. The method of claim 1 , wherein the UE context information passes from the target relay node to the donor access node in a Handover Proxy message.

10. The method of claim 1 , wherein the UE context information passes from the serving relay node to the donor access node in a Handover Proxy message, the Handover Proxy message being one of:

a radio resource control (RRC)-based message; and

an X2-based message.

11. The method of claim 1 , further comprising sending to a serving gateway/packet data network gateway at least one of:

a Proxy Data Tunneling message; and

a Stop Data Sending message.

12. The method of claim 1 , further comprising the target relay node sending a path switch message to a serving gateway/packet data network gateway and triggering an early path switch to the target access node.

13. The method of claim 1 , wherein, if a user plane and a control plane of an S1 interface with a serving gateway/packet data network gateway terminate at the serving relay node, a Handover request message is transmitted from the serving relay node to the target relay node via the serving gateway/packet data network gateway.

14. The method of claim 1 , wherein, if a user plane of an S1 interface with a serving gateway/packet data network gateway terminates at the serving relay node, a Handover request message is transmitted from the serving relay node to the target relay node without passing through the serving gateway/packet data network gateway.

15. The method of claim 1 , wherein, if a user plane of an S1 interface with a serving gateway/packet data network gateway terminates at the donor access node, the UE context information passes from the serving relay node to the donor access node in a Handover request message.

16. The method of claim 1 , wherein, if an S1 interface with a serving gateway/packet data network gateway terminates at the donor access node, the context information includes at least one of:

a UE logical flow identifier; and

serving relay node radio bearer configuration information.

17. The method of claim 16 , wherein the donor access node, based on the serving relay node radio bearer configuration information, identifies a Packet Data Convergence Protocol queue to which the UE belongs and checks the UE logical flow identifier of each data packet in the a Packet Data Convergence Protocol queue to identify the data packets that belong to the UE.

18. The method of claim 16 , wherein the UE logical flow identifier is mapped to a combination of a UE and a radio bearer through radio resource signaling between the donor access node and the serving relay node.

19. A donor access node, comprising:

a processor configured such that the donor access node receives user equipment (UE) context information associated with a UE with which the donor access node is in communication via a serving relay node and such that the donor access node uses the UE context information to identify data packets that belong to the UE, wherein the data packets are forwarded from the serving relay node to a target relay node,

wherein, if relay node radio bearer context is not included in the UE handover context information, the donor access node performs a brute-force search inside each Packet Data Convergence Protocol queue of the serving relay node, based on General Packet Radio Service (GPRS) Tunneling Protocol (GTP)/ User Datagram Protocol (UDP)/Internet Protocol (IP) headers or a subset of GTP/UDP/IP headers, to identify the data packets that belong to the UE.

20. The donor access node of claim 19 , wherein a target access node with which the target relay node is in communication forwards data to the target relay node after the UE completes a handover procedure to the target relay node.

21. The donor access node of claim 20 , wherein the target access node begins forwarding data to the target relay node after receiving one of:

a handover complete message; and

an RRC reconfiguration complete message.

22. The donor access node of claim 20 , wherein the serving access node begins forwarding data to the target relay node or the target access node after receiving a Handover Command acknowledgement message.

23. The donor access node of claim 19 , wherein, if an S1 interface with a serving gateway/packet data network gateway terminates at the serving relay node, the UE context information includes at least one of:

a serving relay node cell global identifier;

a donor access node identifier;

security context information; and

at least one UE bearer tunnel endpoint identifier.

24. The donor access node of claim 23 , wherein the UE context information further includes serving relay node radio bearer configuration information.

25. The donor access node of claim 24 , wherein the donor access node identifies a Packet Data Convergence Protocol queue of the serving relay node to which the UE belongs and checks GTP/UDP/IP headers or a subset of GTP/UDP/IP headers of each data packet to identify the data packets that belong to the UE.

26. The donor access node of claim 19 , wherein the UE context information passes from the serving relay node to the target relay node in a Handover request message.

27. The donor access node of claim 19 , wherein the UE context information passes from the target relay node to the donor access node in a Handover Proxy message.

28. The donor access node of claim 19 , wherein the UE context information passes from the serving relay node to the donor access node in a Handover Proxy message, the Handover Proxy message being one of:

a radio resource control (RRC)-based message; and

an X2-based message.

29. The donor access node of claim 19 , wherein the processor is further configured to send to a serving gateway/packet data network gateway at least one of:

a Proxy Data Tunneling message; and

a Stop Data Sending message.

30. The donor access node of claim 19 , wherein, if a user plane and a control plane of an S1 interface with a serving gateway/packet data network gateway terminate at the serving relay node, a Handover request message is transmitted from the serving relay node to the target relay node via the serving gateway/packet data network gateway.

31. The donor access node of claim 19 , wherein, if a user plane of an S1 interface with a serving gateway/packet data network gateway terminates at the serving relay node, a Handover request message is transmitted from the serving relay node to the target relay node without passing through the serving gateway/packet data network gateway.

32. The donor access node of claim 19 , wherein, if a user plane of an S1 interface with a serving gateway/packet data network gateway terminates at the donor access node, the UE context information passes from the serving relay node to the donor access node in a Handover request message.

33. The donor access node of claim 19 , wherein, if an S1 interface with a serving gateway/packet data network gateway terminates at the donor access node, the context information includes at least one of:

a UE logical flow identifier; and

serving relay node radio bearer configuration information.

34. The donor access node of claim 33 , wherein the donor access node, based on the serving relay node radio bearer configuration information, identifies a Packet Data Convergence Protocol queue to which the UE belongs and checks the UE logical flow identifier of each data packet in the Packet Data Convergence Protocol queue to identify the data packets that belong to the UE.

35. The donor access node of claim 33 , wherein the UE logical flow identifier is mapped to a combination of a UE and a radio bearer through radio resource signaling between the donor access node and the serving relay node.

Assignments (6)
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064270/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064104/0103 →
CHANGE OF NAME Recorded Jan 22, 2014
From: RESEARCH IN MOTION LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 032113/0594 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 29, 2010
From: RESEARCH IN MOTION CORPORATION
To: RESEARCH IN MOTION LIMITED
Reel/Frame 025063/0284 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2010
From: FONG, MO-HAN; BONTU, CHANDRA S.
To: RESEARCH IN MOTION LIMITED
Reel/Frame 024429/0367 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 24, 2010
From: CAI, ZHIJUN; HU, ROSE QINGYANG; YU, YI
To: RESEARCH IN MOTION CORPORATION
Reel/Frame 024479/0156 →