Changing LTE specific anchor with simple tunnel switching
First Claim
Patent Images
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 Assignments
0 Petitions
Accused Products
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.
-
Citations
16 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8)
-
-
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. - View Dependent Claims (10, 11, 12, 13, 14)
-
-
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.
-
Specification