Gateway coordinating multiple small cell radio access networks

Patent metadata

Field	Value
Publication number	US-11071032-B2
Application number	US-201615059235-A
Country	US
Kind code	B2
Filing date	Mar 2, 2016
Priority date	Mar 2, 2015
Publication date	Jul 20, 2021
Grant date	Jul 20, 2021

Abstract

A method of coordinating a plurality of radio access networks (RANs) includes aggregating, with a gateway, communications interfaces between a plurality of RANs and a packet core network through the gateway. A plurality of radio nodes (RNs) in each of the RANs is communicatively coupled to the gateway and to user equipment (UE) devices associated with the RNs in each of the RANs. The gateway also controls and coordinates mobility of the UE devices within and among the RANs. In addition, the gateway acts as a virtual enhanced NodeB (eNB) to the packet core network, thereby hiding the aggregated communications interfaces from the packet core network.

First claim

The invention claimed is:

1. A method of coordinating a plurality of radio access networks (RANs), comprising:
aggregating, with a gateway, communications interfaces between a plurality of RANs and a packet core network through the gateway, a plurality of radio nodes (RNs) in each of the plurality of RANs communicatively coupled to the gateway and to user equipment (UE) devices associated with the plurality of RNs in each of the plurality of RANs;
controlling and coordinating, with the gateway, mobility of the UE devices within and among the plurality of RANs; and
acting, with the gateway, as a virtual enhanced NodeB (eNB) to the packet core network to hide the aggregated communications interfaces from the packet core network.

2. The method of claim 1 , wherein the gateway comprises a plurality of access controller instances.

3. The method of claim 2 , further comprising assigning each of the plurality of RANs to a single one of the plurality of access controller instances so that each access controller instance controls a respective RAN to which it is assigned.

4. The method of claim 2 , further comprising:
receiving a join request from a RN and/or a RAN; and
authenticating, with a cluster manager included in the gateway, the RN and/or the RAN that sends the join request.

5. The method of claim 2 , further comprising:
receiving a join request from the plurality of RNs;
authenticating, with a cluster manager included in the gateway, the plurality of RNs that sends the join request; and
selecting, with the cluster manager, which access controller instance each of the plurality of RNs is to be assigned.

6. The method of claim 5 , wherein selecting which access controller instance each of the plurality of RNs is to be assigned is based at least in part on a signature of the plurality of RNs and a current load of the plurality of access controller instances.

7. The method of claim 2 , further comprising redirecting, with a cluster manager, one of the plurality of RANs from a first access controller instance to a second access controller instance in the event of a failure associated with the first access controller instance or for the purposes of load balancing.

8. The method of claim 2 , further comprising, launching, with a cluster manager, a new access controller instance to perform load balancing based at least in part on a current load of remaining ones of the plurality of access controller instances.

9. The method of claim 8 , further comprising:
launching the new access controller instance in response to receiving a join request from an RN and/or a RAN; and
assigning the RN and/or the RAN from which the join request was received to the new access controller instance.

10. The method of claim 2 , further comprising at least one access controller located external to the gateway.

11. The method of claim 2 , wherein each of the plurality of access controller instances includes a distributed self-organizing network (SON) (d-SON) module for provisioning RNs assigned to respective access controller instances in accordance with self-configuration, self-optimization and self-healing (SON) functionality.

12. The method of claim 11 , further comprising, coordinating, with an aggregated SON (A-SON) module, activity performed by the d-SON module in each of the plurality of access controller instances.

13. The method of claim 12 , further comprising assigning, with a cluster manager operating in coordination with the A-SON module, a newly added RN to one of the plurality of RANs.

14. The method of claim 12 , wherein coordinating the activity performed by the d-SON module includes determining that two or more selected d-SON modules can conduct SON functionality simultaneously with one another.

15. The method of claim 12 , further comprising, with the A-SON module, allocating physical cell identifiers (PCIs) and/or primary scrambling codes (PSCs) across RANs assigned to different ones of the plurality of access controller instances.

16. The method of claim 2 , further comprising conducting handover events between RNs associated with a same or a different access controller instance without signaling the packet core network.

17. The method of claim 2 , wherein the plurality of access controller instances and a hardware platform hosting the plurality of access controller instances has a network function virtualization (NFV) architecture.

18. The method of claim 2 , further comprising using a single interface for all communication between the plurality of access controller instances and the packet core network.

19. The method of claim 1 , further comprising aggregating, with the gateway, communications interfaces between at least two RANs of the plurality of RANs that operate in accordance with different protocols.

20. The method of claim 19 , wherein one of the at least two RANs operates in accordance with a Long Term Evolution (LTE) standard and the other of the at least two RANs operates in accordance with a Universal Mobile Telecommunications Systems (UMTS) standard.

21. The method of claim 18 , wherein the single interface is provided by a mobility anchor module at which all data plane traffic between the UE devices and the packet core network terminate.

22. The method of claim 6 , wherein the signature includes a geographic location of the plurality of RNs.

23. The method of claim 22 , wherein the geographic location of the plurality of RNs is specified by a location identifier selected from the group consisting of a Global Positioning System (GPS) coordinate, physical address, a radio frequency (RF) topology and an internet protocol (IP) address.

24. The method of claim 16 , further comprising responding, with the gateway, to a Radio Resource Control (RRC) connection reestablishment request by performing an RRC Reestablishment Procedure across RNs from the same or different RANs.

25. The method of claim 2 , further comprising conducting a hand-in or hand-out event between a macro cell and one of the plurality of access controller instances without signaling the packet core network.

26. The method of claim 2 , further comprising reducing call setup times by combining a plurality of control plane messages between one RN of the plurality of RNs and a service node (SN) instance to which the one RN is respectively assigned.

27. The method of claim 2 , wherein each of the plurality of access controller instances performs logical open systems interconnection (OSI) layer L3 processing.

28. The method of claim 27 , wherein each of the plurality of access controller instances performs at least a portion of logical open systems interconnection (OSI) layer L2 processing.

29. The method of claim 28 , wherein the logical OSI layer L2 processing performed by each of the plurality of access controller instances includes Packet Data Control Protocol (PDCP) processing.

Assignees

• Corning Optical Communications LLC

Inventors

• Parsay Behrooz
• Tiwari Shashikant
• Nama Hithesh
• Dandekar Yashodhan
• Dunn Brian Patrick
• Singh Jaspreet

Classifications

• H04W36/13

  Cell handover without a predetermined boundary, e.g. virtual cells · CPC title

• H04W36/00698

  using different RATs · CPC title

• H04W4/025

  using location based information parameters · CPC title

• H04W88/16

  Gateway arrangements · CPC title

• H04W28/00

  Network traffic management; Network resource management · CPC title