# US 2017/0257801 A1 · Method and nodes for handling a ue which has moved from an old location to a new location

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0257801 A1
- Document ID: US20170257801A1
- Status: Published application
- Kind: A1
- Application number: 14/912,021
- Filed: 2016-01-14
- Published: 2017-09-07
- Earliest claimed: 2016-01-14
- Assignees: Telefonaktiebolaget LM Ericsson (publ)
- Applicants: TELEFONAKTIEBOLAGET L M ERICSSON (publ)
- Inventors: Stefan TOTH; Gunnar RYDNELL; Ann-Christine SANDER
- Web page: https://patentgrep.com/patent/US20170257801A1

## CPC

- H04W 36/0033: {with transfer of context information}
- H04W 8/10: between location register and external networks
- H04W 64/003: {locating network equipment}
- H04W 48/20: Selecting an access point
- H04W 92/14: between access point controllers and backbone network device
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

The embodiments herein relate to a method performed by a mobility node for handling a UE which has moved from an old to a new location. The mobility node retrieves UE context from a database. The mobility node determines whether there is a change of mobility node and first gateway at the new location. When there is a change of the first gateway, the mobility node initiates setup of a tunnel between a second gateway and a new first gateway. When there is a change of the mobility node, the mobility node provides a subscriber server with UE context for a new mobility node at the new location. The mobility node transmits updated UE context to the database.

## Claims

### Claim 1

A method performed by a mobility node for handling a User Equipment, UE, which has moved from an old location to a new location, the method comprising:
retrieving UE context information from a database when the UE has moved from the old location to the new location, wherein the UE context information comprises mobility node information for a mobility node which currently serves the UE;
determining whether there is a change of which mobility node and first gateway should serve the UE at the new location;
when there is a change of the first gateway, initiating setup of a tunnel between a second gateway and a new first gateway;
when there is a change of the mobility node, providing a subscriber server with UE context information comprising mobility node information for a new mobility node which serves the UE at the new location; and
transmitting updated UE context information comprising mobility node information for the new mobility node to the database.

### Claim 2 (depends on 1)

The method according to claim 1, when there is a change of the first gateway, the initiating setup of the tunnel further comprises:
transmitting a Create Session Request message to the new first gateway; and
receiving a Create Session Response message from the new first gateway.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the providing the subscriber server with UE context information comprising mobility node information for the new mobility node further comprises:
transmitting an Update Location message to the subscriber server, wherein the Update Location message comprises the UE context information comprising mobility node information for the new mobility node; and
receiving an Update Location Acknowledgement message from the subscriber server.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the provided UE context information further comprises state information indicating whether a mobility node which serves the UE is stateless or stateful.

### Claim 5 (depends on 1)

The method according to claim 1, wherein there is no signaling towards an old mobility node and an old first gateway when there has not been any change of mobility node and first gateway.

### Claim 6 (depends on 1)

The method according to claim 1, wherein the setup of the tunnel is initiated when there is a change of first gateway and mobility node and when there is a change of first gateway and no change of mobility node.

### Claim 7 (depends on 1)

The method according to claim 1, wherein the subscriber server is provided with information about the new mobility node when there is a change of mobility node and first gateway and when there is a change of mobility node and no change of first gateway.

### Claim 8 (depends on 1)

The method according to claim 1, wherein at least one of an old mobility node, a new mobility node, an old first gateway and the new first gateway are stateless.

### Claim 9 (depends on 1)

The method according to claim 1, wherein the movement of the UE from the old location to the new location is a Tracking Area Update, TAU, procedure or a Routing Area Update, RAU, procedure.

### Claim 10 (depends on 1)

The method according to claim 1, wherein the mobility node is a Mobility Management Entity, MME, or a virtualized Mobility Management Entity, vMME.

### Claim 11

A method performed by a subscriber server for handling a User Equipment, UE, (101) which has moved from an old location to a new location, the method comprising:
when there is a change of which mobility node serves the UE at the new location, obtaining, from a new mobility node, UE context information comprising mobility node information for the new mobility node which serves the UE at the new location.

### Claim 12 (depends on 11)

The method according to claim 11, wherein the obtaining UE context information further comprises:
receiving an Update Location message from the new mobility node, wherein the Update Location message comprises the UE context information comprising the mobility node information for the new mobility node; and
transmitting an Update Location Acknowledgement message to the new mobility node.

### Claim 13 (depends on 11)

The method according to claim 11, wherein the obtained UE context information further comprises state information indicating whether the new mobility node is stateless or stateful.

### Claim 14 (depends on 13)

The method according to claim 13, further comprising:
based on previously saved state information for the old mobility node, determining whether a Cancel Location message should be sent to the old mobility node.

### Claim 15 (depends on 14)

The method according to claim 14, wherein the Cancel Location message is not sent to the old mobility node when the previously saved state information indicates that the old mobility node is stateless and wherein the Cancel Location message is sent to the old mobility node when the previously saved state information indicates that the old mobility node is stateful.

### Claim 16 (depends on 11)

The method according to claim 11, wherein the subscriber server obtains the UE context information when there is a change of mobility node and first gateway and when there is a change of mobility node and no change of first gateway.

### Claim 17 (depends on 11)

The method according to claim 11, wherein the subscriber server is a Home Subscriber Server, HSS, a virtualized HSS, vHSS, a Home Location Register, HLR, or a virtualized HLR, vHLR.

### Claim 18 (depends on 11)

The method according to claim 11, wherein at least one of an old mobility node, a new mobility node, an old first gateway and the new first gateway are stateless.

### Claim 19 (depends on 11)

The method according to claim 11, wherein the movement of the UE from the old location to the new location is a Tracking Area Update, TAU, procedure or a Routing Area Update, RAU, procedure.

### Claim 20

A mobility node for handling a User Equipment, UE, which has moved from an old location to a new location, the mobility node being adapted to:
retrieve UE context information from a database when the UE has moved from the old location to the new location, wherein the UE context information comprises mobility node information for a mobility node which currently serves the UE;
determine whether there is a change to which mobility node and first gateway should serve the UE at the new location;
when there is a change of the first gateway, initiate setup of a tunnel between a second gateway and a new first gateway;
when there is a change of the mobility node, provide a subscriber server with UE context information comprising mobility node information for a new mobility node which serves the UE at the new location; and
provide updated UE context information comprising mobility node information for the new mobility node to the database.

### Claim 21 (depends on 20)

The mobility node according to claim 20, being further adapted to:
transmit a Create Session Request message to the new first gateway; and
receive a Create Session Response message from the new first gateway.

### Claim 22 (depends on 20)

The mobility node according to claim 20, being further adapted to:
transmit an Update Location message to the subscriber server, wherein the Update Location message comprises the UE context information comprising mobility node information for the new mobility node; and
receive an Update Location Acknowledgement message from the subscriber server.

### Claim 23 (depends on 20)

The mobility node according to claim 20, wherein the provided UE context information further comprises state information indicating whether a mobility node which the UE is associated with is stateless or stateful.

### Claim 24 (depends on 20)

The mobility node according to claim 20, wherein there is no signaling towards an old mobility node and an old first gateway when there has not been any change of mobility node and first gateway.

### Claim 25 (depends on 20)

The mobility node according to claim 20, wherein the setup of the tunnel is initiated when there is a change of first gateway and mobility node and when there is a change of first gateway and no change of mobility node.

### Claim 26 (depends on 20)

The mobility node according to claim 20, wherein the subscriber server is provided with information about the new mobility node when there is a change of mobility node and first gateway and when there is a change of mobility node and no change of first gateway.

### Claim 27 (depends on 20)

The mobility node according to claim 20, wherein at least one of an old mobility node, a new mobility node, an old first gateway and the new first gateway are stateless.

### Claim 28 (depends on 20)

The mobility node according to claim 20, wherein the movement of the UE from the old location to the new location is a Tracking Area Update, TAU, procedure or a Routing Area Update, RAU, procedure.

### Claim 29 (depends on 20)

The mobility node according to claim 20, wherein the mobility node is a Mobility Management Entity, MME, or a virtualized Mobility Management Entity, vMME.

### Claim 30

A subscriber server for handling a User Equipment, UE, which has moved from an old location to a new location, the subscriber server being adapted to:
when there is a change to which mobility node serves the UE at the new location, obtain, from a new mobility node, UE context information comprising mobility node information for the new mobility node which serves the UE at the new location.

### Claim 31 (depends on 30)

The subscriber server according to claim 30, being further adapted to:
receive an Update Location message from the new mobility node, wherein the Update Location message comprises the UE context information, and wherein the UE context information comprises mobility node information for the new mobility node; and to
transmit an Update Location Acknowledgement message to the new mobility node.

### Claim 32 (depends on 30)

The subscriber server according to claim 30, wherein the obtained UE context information further comprises state information indicating whether the new mobility node is stateless or stateful.

### Claim 33 (depends on 32)

The subscriber server according to claim 32, being further adapted to:
based on previously saved state information for the old mobility node, determine whether a Cancel Location message should be sent to the old mobility node.

### Claim 34 (depends on 33)

The subscriber server according to claim 33, wherein the Cancel Location message is not sent to the old mobility node when the previously saved state information indicates that the old mobility node is stateless and wherein the Cancel Location message is sent to the old mobility node when the previously saved state information indicates that the old mobility node is stateful.

### Claim 35 (depends on 30)

The subscriber server according to claim 30, wherein the subscriber server is adapted to obtain the UE context information when there is a change of mobility node and first gateway and when there is a change of mobility node and no change of first gateway.

### Claim 36 (depends on 30)

The subscriber server according to claim 30, wherein the subscriber server is a Home Subscriber Server, HSS, a virtualized HSS, vHSS, a Home Location Register, HLR, or a virtualized HLR, vHLR.

### Claim 37 (depends on 30)

The subscriber server according to claim 30, wherein at least one of an old mobility node, a new mobility node, an old first gateway and the new first gateway are stateless.

### Claim 38 (depends on 30)

The subscriber server according to claim 30, wherein the movement of the UE from the old location to the new location is a Tracking Area Update, TAU, procedure or a Routing Area Update, RAU, procedure.

### Claim 39

A method performed by a communications system for handling a User Equipment, UE, which has moved from an old location to a new location, the method comprising:
retrieving, at a mobility node, a UE context information from a database has moved from the old location to the new location, wherein the UE context information comprises mobility node information for a mobility node which currently serves the UE;
determining, at the mobility node whether there is a change to which mobility node and first gateway should serve the UE at the new location;
when there is a change of the first gateway, initiating, at the mobility node, setup of a tunnel between a second gateway and a new first gateway;
when there is a change of the mobility node, providing, from the mobility node to a subscriber server, UE context information comprising mobility node information for a new mobility node which serves the UE at the new location;
when there is a change to which mobility node the UE is associated with when it has moved to the new location, obtaining, at the subscriber server and from a new mobility node, UE context information comprising mobility node information for the new mobility node which serves the UE at the new location; and
transmitting updated UE context information comprising mobility node information for the new mobility node from the mobility node to the database.

### Claim 40

A communications system for handling a User Equipment, UE, which has moved from an old location to a new location, the communications system being adapted to:
retrieve, at a mobility node, UE context information from a database when the UE has moved from the old location to the new location, wherein the UE context information comprises mobility node information for a mobility node which currently serves the UE;
determine, at the mobility node, whether there is a change to which mobility node and first gateway should serve the UE at the new location;
when there is a change of the first gateway, initiate, at the mobility node, setup of a tunnel between a second gateway and a new first gateway;
when there is a change of the mobility node, provide, from the mobility node to a subscriber server, UE context information comprising mobility node information for a new mobility node which serves the UE at the new location;
when there is a change to which mobility node serves the UE at the new location, obtain, at the subscriber server and from a new mobility node, UE context information comprising mobility node information for the new mobility node which serves the UE at the new location; and transmit updated UE context information comprising mobility node information for the new mobility node from the mobility node to the database.

### Claim 41 (depends on 1)

A first computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to claim 1.

### Claim 42 (depends on 41)

A first carrier comprising the first computer program of claim 41, wherein the first carrier is a non-transitory computer readable storage medium.

### Claim 43 (depends on 11)

A second computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to claim 11.

### Claim 44 (depends on 43)

A second carrier comprising the second computer program of claim 43, wherein the second carrier is a non-transitory computer readable storage medium.

### Claim 45 (depends on 39)

A third computer program comprising instructions which, when executed on at least one processor, cause the at least one processor to carry out the method according to claim 39.

### Claim 46 (depends on 45)

A third carrier comprising the third computer program of claim 45, wherein the third carrier is a non-transitory computer readable storage medium.
