Search

US-12621723-B2 - Inter virtual-eNodeB optimized handover for gateway core network (GWCN)

US12621723B2US 12621723 B2US12621723 B2US 12621723B2US-12621723-B2

Abstract

Methods, systems and computer readable media are disclosed for providing inter virtual-eNodeB optimized handover. In one example embodiment, a method includes sending, from a first eNodeB, a handover required message to a first HetNet Gateway (HNG)/virtual eNodeB; matching a target cell in a virtual eNodeB database; receiving, at a second eNodeB, a handover request from a second HNG/virtual eNodeB; sending, by the second eNodeB, a handover request acknowledge message to the second HNG/virtual eNodeB; and performing call context switching using the virtual eNodeB database.

Inventors

  • Sunil Jamkhandikar
  • Ravikiran Raje

Assignees

  • PARALLEL WIRELESS, INC.

Dates

Publication Date
20260505
Application Date
20211012

Claims (20)

  1. 1 . A method for providing inter virtual-eNodeB optimized handover, comprising: receiving, from a first eNodeB at a first HetNet Gateway (HNG)/virtual eNodeB, a handover required message for a handover for a user equipment (UE) from the first eNodeB to a target eNodeB; matching, via the first HNG/virtual eNodeB, the target eNodeB in a virtual eNodeB database to a second HNG/virtual eNodeB; wherein the target eNodeB receives from the second HNG/virtual eNodeB, based on the handover required message, a handover request message; sending, from the first HNG/virtual eNodeB to the first eNodeB, based on the handover request message, a handover command message to handover to the second eNodeB, wherein the second eNodeB is the target eNodeB; wherein the target eNodeB sends to the second HNG/virtual eNodeB, based on the handover request message, a handover request acknowledge message; and performing call context switching for the UE between a virtualization of the first eNodeB in the first HNG/virtual eNodeB and a virtualization of the second eNodeB in the first HNG/virtual eNodeB without exchanging signaling based on the matching and the handover request message.
  2. 2 . The method of claim 1 wherein the matching is based on a Mobility Management Entity (MME) match.
  3. 3 . The method of claim 2 further comprising, by the first HNG/virtual eNodeB, avoiding exchanging of S1 signaling between the virtualization of the first eNodeB and the virtualization of the second eNodeB.
  4. 4 . The method of claim 1 wherein the second eNodeB sends a handover notify message to the second HNG/virtual eNodeB.
  5. 5 . The method of claim 1 wherein the second HNG/virtual eNodeB sends a path switch release message to the MME, the path switch release message being the only signaling for the handover sent to the MME.
  6. 6 . The method of claim 5 wherein the MME sends a path switch acknowledge message to the second HNG/virtual eNodeB.
  7. 7 . The method of claim 1 , wherein the virtualization of the first eNodeB and the virtualization of the second eNodeB are in the first HNG.
  8. 8 . The method of claim 1 , wherein matching further comprises determining by the virtualization of the first eNodeB that the target cell is connected to the virtualization of the second eNodeB in the same HNG.
  9. 9 . A system for providing inter virtual-eNodeB optimized handover, comprising: a first HetNet Gateway (HNG)/virtual eNodeB, including a processor and a memory, in communication with a first eNodeB in a cellular core network, a second eNodeB in communication with the first eNodeB via the cellular core network, and a virtual eNodeB database, wherein a second HetNet Gateway (HNG)/virtual eNodeB is in communication with the second eNodeB, and the first HNG/virtual eNodeB; wherein the processor is configured to: receive, from the first eNodeB, a handover required message for a handover for a user equipment (UE) from the first eNodeB to a target eNodeB; match the target eNodeB in the virtual eNodeB database to the second HNG/virtual eNodeB; send to the first eNodeB, based on the handover request message, a handover command message to handover to the second eNodeB, wherein the second eNodeB is the target eNodeB; and perform call context switching for the UE between a virtualization of the first eNodeB in the first HNG/virtual eNodeB and a virtualization of the second eNodeB in the first HNG/virtual eNodeB without exchanging signaling based on the match and the handover request message; wherein the target eNodeB receives from the second HNG/virtual eNodeB, based on the handover required message, a handover request message; and wherein the target eNodeB sends to the second HNG/virtual eNodeB, based on the handover request message, a handover request acknowledge message.
  10. 10 . The system of claim 9 wherein match is based on a Mobility Management Entity (MME) match.
  11. 11 . The system of claim 10 wherein the processor is further configured to avoid exchanging of SI signaling between the virtualization of the first eNodeB and the virtualization of the second eNodeB.
  12. 12 . The system of claim 9 wherein the second eNodeB sends a handover notify message to the second HNG/virtual eNodeB.
  13. 13 . The system of claim 9 wherein a Mobility Management Entity (MME) is in communication with the second HNG/virtual eNodeB and wherein the second HNG/virtual eNodeB sends a path switch release message to the MME, the path switch release message being the only signaling for the handover sent to the MME.
  14. 14 . The system of claim 13 wherein the MME sends a path switch acknowledge message to the second HNG/virtual eNodeB.
  15. 15 . A non-transitory computer-readable medium containing instructions for providing inter virtual-eNodeB optimized handover which, when executed, cause a system to perform steps comprising: receiving, from a first eNodeB at a first HetNet Gateway (HNG)/virtual eNodeB, a handover required message for a handover for a user equipment (UE) from the first eNodeB to a target eNodeB; matching, via the first HNG/virtual eNodeB, the target eNodeB in a virtual eNodeB database to a second HNG/virtual eNodeB; wherein the eNodeB receives from the second HNG/virtual eNodeB, based on the handover required message, a handover request message; sending, from the first HNG/virtual eNodeB to the first eNodeB, based on the handover request message, a handover command message to handover to the second eNodeB, wherein the second eNodeB is the target eNodeB; wherein the target eNodeB sends to the second HNG/virtual eNodeB, based on the handover request message, a handover request acknowledge message; and performing call context switching for the UE between a virtualization of the first eNodeB in the first HNG/virtual eNodeB and a virtualization of the second eNodeB in the first HNG/virtual eNodeB without exchanging signaling based on the matching and the handover request message.
  16. 16 . The computer-readable medium of claim 15 wherein the matching is based on a Mobility Management Entity (MME) match.
  17. 17 . The computer-readable medium of claim 16 further comprising instructions for, by the first HNG/virtual eNodeB, avoiding exchanging of S1 signaling between the virtualization of the first eNodeB and the virtualization of the second eNodeB.
  18. 18 . The computer-readable medium of claim 15 wherein the second eNodeB sends a handover notify message to the second HNG/virtual eNodeB.
  19. 19 . The computer-readable medium of claim 15 wherein the second HNG/virtual eNodeB sends a path switch release message to the MME, the path switch release message being the only signaling for the handover sent to the MME.
  20. 20 . The computer-readable medium of claim 19 wherein the MME sends a path switch acknowledge message to the second HNG/virtual eNodeB.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS This application claims priority under 35 U.S.C. § 119(e) to U.S. Provisional Pat. App. No. 63/089,844, filed Oct. 9, 2020, titled “Inter Virtual-eNodeB Optimized Handover for Gateway Core Network (GWCN)” which is hereby incorporated by reference in its entirety for all purposes. The present application hereby incorporates by reference U.S. Pat. App. Pub. Nos. US20110044285, US20140241316; WO Pat. App. Pub. No. WO2013145592A1; EP Pat. App. Pub. No. EP2773151A1; U.S. Pat. No. 8,879,416, “Heterogeneous Mesh Network and Multi-RAT Node Used Therein,” filed May 8, 2013; U.S. Pat. No. 8,867,418, “Methods of Incorporating an Ad Hoc Cellular Network Into a Fixed Cellular Network,” filed Feb. 18, 2014; U.S. patent application Ser. No. 14/777,246, “Methods of Enabling Base Station Functionality in a User Equipment,” filed Sep. 15, 2016; U.S. patent application Ser. No. 14/289,821, “Method of Connecting Security Gateway to Mesh Network,” filed May 29, 2014; U.S. patent application Ser. No. 14/642,544, “Federated X2 Gateway,” filed Mar. 9, 2015; U.S. patent application Ser. No. 14/711,293, “Multi-Egress Backhaul,” filed May 13, 2015; U.S. Pat. App. No. 62/375,341, “S2 Proxy for Multi-Architecture Virtualization,” filed Aug. 15, 2016; U.S. patent application Ser. No. 15/132,229, “MaxMesh: Mesh Backhaul Routing,” filed Apr. 18, 2016, each in its entirety for all purposes, respectively. This application also hereby incorporates by reference in their entirety each of the following U.S. Pat. applications or Pat. App. Publications: US20150098387A1; US20170055186A1; US20170273134A1; US20170272330A1; and Ser. No. 15/713,584. This application also hereby incorporates by reference in their entirety U.S. patent application Ser. No. 16/424,479, “5G Interoperability Architecture,” filed May 28, 2019; and U.S. Provisional Pat. Application No. 62/804,209, “5G Native Architecture,” filed Feb. 11, 2019. BACKGROUND In cellular networks, base stations have a limited reach, to achieve connectivity between mobile devices—which may be mobile—handover is necessary. Handover or hand off is a process in telecommunication and mobile communication in which cellular transmission (voice or data) is transferred from one base station (cell site) to another without losing connectivity to the cellular transmission. Handover is a core element in deploying mobile transmission as it creates data sessions or connects phone calls between mobile devices which are constantly on the move. Existing handover procedures are defined by 3GPP spec 36.413. One type of handover is one in which the channel source cell is released before the channel in the target is engaged. In this type of handover, the connection to the source is broken just before or along with when the connection to the target is made. It is also called break before making handover. Another type of handover is one in which the source cell is retained and works in parallel with the target cell for a while. In this case, connection to the target cell is established before connection to the source is broken. This type of handover allows a parallel connection between several channels to provide better service. It is very effective in areas with poor coverage. Another type of handover is an inter virtual eNodeB handover. There type of handovers can cause increased signaling as well as processing overload on the MME in case of hEnB attached to separate virtual eNodeB's of the HNG solution, or ENodeB's attached to separate virtual ENodeB's of the HNG solution. SUMMARY This handover problem can be addressed by optimizing the handover within the HNG solution so that the handover signaling load is not transferred to MME, as well as the need for processing the handovers and finding the target either using Target eNbid or TAC based routing for higher release MMEs. (We can be independent instead of relying on MME to support TAC based routing.) The task of searching for Target eNb IDs especially in case of home-eNbs with non-matching eNbids behind the hEnBw, would mean that MME needs capability to do TAC based handover and increases the processing load per handover (decreases signaling load significantly). In one example embodiment a method for providing inter virtual-eNodeB optimized handover, includes sending, from a first eNodeB, a handover required message to a first HetNet Gateway (HNG)/virtual eNodeB; matching a target cell in a virtual eNodeB database; receiving, at a second eNodeB, a handover request from a second HNG/virtual eNodeB; sending, by the second eNodeB, a handover request acknowledge message to the second HNG/virtual eNodeB; and performing call context switching using the virtual eNodeB database. In another example embodiment a system for providing inter virtual-eNodeB optimized handover includes a first eNodeB; a first HetNet Gateway (HNG)/virtual eNodeB in communication with the first eNodeB; a second eNodeB; and a second HetNet Gateway (HNG)/virtual e