Changing LTE specific anchor with simple tunnel switching

• US 20080031159A1
• Filed: 06/15/2007
• Published: 02/07/2008
• Est. Priority Date: 06/16/2006
• Status: Active Grant

• Current Assignee: Nokia Technologies Oy (Nokia Corporation)
• Original Assignee: Nokia Corporation
• Inventors: Jokinen, Joanna
• Granted Patent: US 8,107,433 B2
• Time in Patent Office: Days
• US Class Current: 370/255
• CPC Class Codes: H04W 36/0033 with transfer of context information
• CPC Class Codes: H04W 80/04 Network layer protocols, e.g. mobile IP [Internet Protocol]
• CPC Class Codes: H04W 92/02 Inter-networking arrangements
• CPC Class Codes: H04W 92/24 between backbone network devices

Abstract

Embodiments of the invention may further provide a method for transferring an LTE anchor in an idle mode. The method includes an MME (control plane entity) initiating an LTE anchor change procedure, the MME first commands the selected new LTE anchor to set up a user plane tunnel towards the 3GPP anchor and then it updates this information towards the 3GPP anchor. Thereafter, the old tunnel is deleted from the old LTE anchor.

Claims

1. A network entity for initiating an anchor change-over procedure, comprising:

a creation unit configured to direct a creation request to a second anchor to set up a user plane tunnel towards a third generation anchor and configured to receive a response from the second anchor;

an updating unit configured to send an update context request towards the third generation anchor and to receive an update proxy context response from the third generation anchor; and

a deletion unit configured to direct a deletion request to a first anchor and to receive a deletion response from the first anchor,

wherein the network entity is configured to operate in an idle mode.

2. The network entity of claim 1, wherein the creation unit is further configured to use an external entity to decide when the second anchor is to be selected and to use the external entity to select the second anchor.

3. The network entity of claim 1, wherein when the network entity is in idle mode, the network entity includes user plane information.

4. The network entity of claim 1, wherein the creation unit is further configured send a proxy context request to the second anchor.

5. The network entity of claim 4, wherein the proxy context request includes a mobile station identifier and access context information.

6. The network entity of claim 1, wherein the creation unit is further configured to receive a proxy context response comprising the second anchor address for user plane delivery and allocated tunnel endpoint identifiers.

7. The network entity of claim 1, wherein the updating unit is further configured to send a update context request to the third generation anchor, the update context request including at least one address for the second anchor and tunnel endpoint identifiers received from the second anchor.

8. The network entity of claim 1, wherein the deletion unit is further configured to send a delete proxy context request to the first anchor to terminate operations with the first anchor, wherein the first anchor is to release resources to the third generation anchor.

9. A method for initiating an anchor change-over procedure, comprising:

directing a creation request to a second anchor to set up a user plane tunnel towards a third generation anchor;

receiving a response from the second anchor;

sending an update context request towards the third generation anchor;

receiving an update proxy context response from the third generation anchor;

directing a deletion request to a first anchor; and

receiving a deletion response from the first anchor,

wherein a network entity implementing the elements above is configured to operate in an idle mode.

10. The method of claim 9, wherein directing a creation request comprises:

using an external entity to decide when the second anchor is to be selected and using the external entity to select the second anchor.

11. The method of claim 9, wherein directing a creation request comprises sending a proxy context request to the second anchor, wherein the proxy context request includes a mobile station identifier and access context information.

12. The method of claim 9, wherein receiving a response from the second anchor comprises receiving a proxy context response comprising at least one address for the second anchor for user plane delivery and allocated tunnel endpoint identifiers.

13. The method of claim 9, wherein updating comprises sending a update context request to the third generation anchor, the update context request including at least one address for the second anchor and tunnel endpoint identifiers received from the second anchor.

14. The method of claim 9, wherein deleting comprises sending a delete proxy context request to the first anchor to terminate operations with the first anchor, wherein the first anchor is to release resources to the third generation anchor.

15. An apparatus for initiating an anchor change-over procedure, comprising:

directing means for directing a creation request to a second anchor to set up a user plane tunnel towards a third generation anchor;

receiving means for receiving a response from the second anchor;

updating means for sending an update context request towards the third generation anchor;

receiving means for receiving an update proxy context response from the third generation anchor;

directing means for direction a deletion request to a first anchor; and

receiving means for receiving a deletion response from the first anchor,

wherein the apparatus is configured to operate in an idle mode.

16. A system for implementing initiation of an anchor change-over procedure, comprising:

a mobility entity configured to direct a creation request to a second anchor to set up a user plane tunnel towards a third generation anchor,

wherein the second anchor is configured to create a tunnel towards the third generation anchor upon receipt of the creation request and to send a response to the mobility entity,

wherein upon receipt of the response from the second anchor the mobility entity is configured to update a context request towards the third generation anchor,

wherein the third generation anchor is configured to update uplink path toward the second anchor and to send an update proxy context response to the mobility entity,

wherein the mobility entity is configure to directing a deletion request to a first anchor and to receive a deletion response from the first anchor, and

wherein the mobility entity is configured to operate in an idle mode.