Systems, methods and media for small cell idle mode mobility

• US 9,226,255 B2
• Filed: 11/25/2013
• Issued: 12/29/2015
• Est. Priority Date: 11/25/2013
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Grayson, Mark, Okmyanskiy, Anton, Graham, Mickael James, Kudsi, Mansoorali Naushadali
• Primary Examiner(s): Batista, Marcos
• Application Number:
  US14/088,536
• Publication Number:
  US 20150148036A1
• Time in Patent Office: 764 Days
• Field of Search: 455/435.1, 370/338
• US Class Current: 1/1
• CPC Class Codes: H04W 4/025 using location based information parameters
• CPC Class Codes: H04W 60/02 by periodical registration
• CPC Class Codes: H04W 68/06 using multi-step notification by changing the notification area
• CPC Class Codes: H04W 8/06 Registration at serving network Location Register, VLR or user mobility server
• CPC Class Codes: H04W 84/045 using private Base Stations, e.g. femto Base Stations, home Node B
• CPC Class Codes: H04W 88/005 Data network PoA devices

Abstract

Systems and methods for small cell idle mode mobility include receiving, at a first small cell of a preconfigured cluster of small cells, a mobility area update request from a user equipment (UE). The method can also include registering location information of the UE with a small cell gateway, and retrieving a core network periodic timer for the UE from a mobility server. If certain conditions are met, the first small cell forwards the mobility area update request to a core network via the small cell gateway. Otherwise, the method can include the first small cell updating the location information of the UE with the mobility server, generating a locally-generated mobility area update accept message, and sending a locally generated mobility area update accept message to the UE along with a local periodic timer instructing the UE to send another mobility area update request when the local periodic timer expires.

Claims

1. A method comprising:

receiving, at a first small cell of a plurality of small cells, a message including a mobility area update request from a user equipment (UE), wherein the plurality of small cells constitute a preconfigured cluster of small cells;

registering location information of the UE with a small cell gateway in communication with the preconfigured cluster of small cells;

retrieving a core network periodic timer for the UE from a mobility server in communication with the preconfigured cluster of small cells;

if it is determined that at least one of the following is true;

(i) the mobility area update request from the UE is received at the first small cell for a first time after the UE moves into a preconfigured cluster area covered by all of the small cells from the preconfigured cluster of small cells, (ii) the core network periodic timer has expired, and (iii) the mobility area update request from the UE is received at the first small cell for the first time after the UE is turned on;

(a) forwarding the mobility area update request to a core network via the small cell gateway,

(b) receiving a core network-generated mobility area update accept message from the core network in response to the mobility area update request, and

(c) updating the core network periodic timer for the UE in the mobility server with a time at which the core network-generated mobility area update accept message was received;

otherwise;

(a) generating a locally-generated mobility area update accept message in response to the mobility area update request;

updating the location information of the UE with the mobility server; and

sending (i) at least one of the locally generated mobility area update accept message and the core network-generated mobility area update accept message to the UE, and (ii) a local periodic timer to the UE instructing the UE to send another mobility area update request when the local periodic timer expires.

2. The method of claim 1, further comprising receiving, at the first small cell, a paging request from the core network, and paging the UE from the first small cell in response to the paging request.

3. The method of claim 2, further comprising determining whether the UE is no longer located within a local area covered by the first small cell, and, if the UE is no longer located within the local area, sending the paging request to each remaining small cell in the preconfigured cluster of small cells to allow a second small cell in the preconfigured cluster to page the UE in response to the paging request, wherein the paging request is sent over inter-small-cell connections established between the first small cell and each remaining small cell in the preconfigured cluster of small cells.

4. The method of claim 1, wherein the mobility area update request comprises at least one of a location area update request and a routing area update request, and wherein the mobility area update response comprises at least one of a location area update response and a routing area update response.

5. The method of claim 1, wherein the determination of whether the mobility area update request from the UE is received at the first small cell for a first time after the UE moves into a preconfigured cluster area covered by all of the small cells from the preconfigured cluster of small cells is based on a previous mobility area code within the mobility area update request.

6. The method of claim 5, wherein the previous mobility area code comprises at least one of a location area code and a routing area code.

7. The method of claim 1 wherein the preconfigured cluster of small cells share at least one of a common location area code and a common routing area code.

8. The method of claim 1 wherein the preconfigured cluster of small cells share at least one of a known set of location area codes and a known set of routing area codes.

9. The method of claim 1 wherein the small cells include Home Node Bs (HNBs), and the small cell gateway is a Home Node B Gateway (HNB-GW).

10. The method of claim 3, wherein the inter-small-cell connections are I_URH connections.

11. The method of claim 1 wherein the local periodic timer and the core network periodic timer include at least one of T3212 periodic location area update timers and T3312 periodic routing area update timers.

12. The method of claim 1, wherein the mobility server is incorporated into a standalone device.

13. The method of claim 1, wherein the mobility server is incorporated into the small cell gateway.

14. The method of claim 1, wherein the mobility server is distributed across each small cell in the preconfigured cluster of small cells.

15. A network device comprising:

a memory capable of storing data; and

a processor coupled to the memory;

the network device configured to;

receive a message including a mobility area update request from a user equipment (UE), wherein the network device is part of a preconfigured cluster of network devices;

register location information of the UE with a gateway in communication with the preconfigured cluster of network devices;

retrieve a core network periodic timer for the UE from a mobility server in communication with the preconfigured cluster of network devices;

if it is determined that at least one of the following is true;

(i) the mobility area update request from the UE is received at the network device for a first time after the UE moves into a preconfigured cluster area covered by all of the network devices from the preconfigured cluster of network devices, (ii) the core network periodic timer has expired, and (iii) the mobility area update request from the UE is received at the network device for the first time after the UE is turned on;

(a) forward the mobility area update request to a core network via the gateway,

(b) receive a core network-generated mobility area update accept message from the core network in response to the mobility area update request, and

(c) update the core network periodic timer and the location information of the UE in the mobility server with a time at which the core network-generated mobility area update accept message was received;

otherwise;

(a) generate a locally-generated mobility area update accept message in response to the mobility area update request;

updating the location information of the UE with the mobility server; and

send (i) at least one of the locally-generated mobility area update accept message and the core network-generated mobility area update accept message to the UE, and (ii) a local periodic timer to the UE instructing the UE to send another mobility area update request when the local periodic timer expires.

16. The network device of claim 15, wherein the network device is further configured to use the data to cause the network device to receive a paging request from the core network, and to page the UE in response to the paging request.

17. The network device of claim 16, wherein the network device is further configured to use the data to cause the network device to determine whether the UE is no longer located within a local area covered by the network device, and, if the UE is no longer located within the local area, send the paging request to each remaining network device in the preconfigured cluster of network devices to allow a second network device in the preconfigured cluster to page the UE in response to the paging request, wherein the paging request is sent over inter-network device connections established between the network device and each remaining network device in the preconfigured cluster of network devices.

18. The network device of claim 15, wherein the mobility area update request includes at least one of a location area update request and a routing area update request, and wherein the mobility area update response includes at least one of a location area update response and a routing area update response.

19. The network device of claim 15, wherein the determination of whether the mobility area update request from the UE is received at the network device for a first time after the UE moves into a preconfigured cluster area covered by all of the network devices from the preconfigured cluster of network devices is based on a previous mobility area code within the mobility area update request.

20. The network device of claim 19, wherein the previous mobility area code comprises at least one of a location area code and a routing area code.

21. The network device of claim 15, wherein the preconfigured cluster of network devices share at least one of a common location area code and a common routing area code.

22. The network device of claim 15, wherein the preconfigured cluster of network devices share at least one of a known set of location area codes and a known set of routing area codes.

23. The network device of claim 15, wherein the network devices include Home Node Bs (HNBs), and the gateway is a Home Node B Gateway (HNB-GW).

24. The network device of claim 17, wherein the inter-network device connections are I_URH connections.

25. The network device of claim 15, wherein the local periodic timer and the core network periodic timer include at least one of T3212 periodic location area update timers and T3312 periodic routing area update timers.

26. The network device of claim 15, wherein the mobility server is incorporated into a standalone device.

27. The network device of claim 15, wherein the mobility server is incorporated into the gateway.

28. The network device of claim 15, wherein the mobility server is distributed across each network device in the preconfigured cluster of network devices.