Patent US2768983A successfully refreshed from Google Patents.
Patent US9888422B2 successfully refreshed from Google Patents.
US9888422B2
Active / In Force
US
⏱️ 7.6 years remaining
System and method for adaptive access and handover configuration based on prior history in a multi-RAT environment
Assignee: Avago Technologies International Sales Pte Ltd
•
Filing: 2014-06-03
•
Granted: 2018-02-06
•
Expires: 2034-06-03
Abstract
Abstract Systems and methods for adaptive access and handover configuration based on historical data are provided. Access and handover decisions are optimized in a multiple radio access technology environment using historical data associated with network performance. Future needs for access and handovers are predicted using historical data associated with the user and historical data associated with network performance. Performance metrics are received periodically or continuously from nodes in one or more networks at a centralized controller. The centralized multi RAT controller correlates these performance metrics and determines predicted handovers for a user device. Preparations for the predicted handovers can then be made prior to the handover event.
Inventors
- 👤 Raymond Hayes
- 👤 John Walley
- 👤 Murat Mese
Bibliographic Details
Application Number
—
Jurisdiction
US
Data Source
google_patents
Last Synchronized
2026-11-01 22:07
CPC Classifications
H04W36/245; H; H04; H04W; H04W36/00; H04W36/0005; H04W36/0083; H04W36/0085; H04W36/00837; H04W36/008375
Claims Analysis
Total Claims: 23
Claim 1
Independent Claim
210 words
A method, in a network controller, for implementing handover decisions based on performance data, comprising: predicting, by the network controller, an application that is to be run at a future time on a user device served by a first network access device based on an affinity group of user devices for the user device, wherein the affinity group is generated based on usage patterns for the user device that track use of the application that is to be run at the future time on the user device; retrieving performance metrics for the application that is to be run at the future time on the user device, wherein the performance metrics for the application that is predicted, by the network controller, to be run at the future time on the user device are determined based on observations of a plurality of potential paths and each of the plurality of potential paths comprises a set of network nodes; determining a handover path to a second network access device for the application that is to be run at the future time on the user device based on the performance metrics and historical travel patterns for the user device; and communicating the handover path to the first network access device serving the user device.
Claim 2
Independent Claim
210 words
A method, in a network controller, for implementing handover decisions based on performance data, comprising: predicting, by the network controller, an application that is to be run at a future time on a user device served by a first network access device based on an affinity group of user devices for the user device, wherein the affinity group is generated based on usage patterns for the user device that track use of the application that is to be run at the future time on the user device; retrieving performance metrics for the application that is to be run at the future time on the user device, wherein the performance metrics for the application that is predicted, by the network controller, to be run at the future time on the user device are determined based on observations of a plurality of potential paths and each of the plurality of potential paths comprises a set of network nodes; determining a handover path to a second network access device for the application that is to be run at the future time on the user device based on the performance metrics and historical travel patterns for the user device; and communicating the handover path to the first network access device serving the user device.
Claim 3
Dependent Claim
21 words
The method of claim 1 , further comprising: receiving the performance metrics for the application from a plurality of user devices.
Claim 4
Dependent Claim
19 words
The method of claim 2 , further comprising: receiving the performance metrics for the application from a network node.
Claim 5
Dependent Claim
34 words
The method of claim 3 , further comprising: compiling the performance metrics for the application; and generating a pathway performance metrics profile for the application based on the compiled performance metrics for the application.
Claim 6
Dependent Claim
42 words
The method of claim 1 , wherein the performance metrics include observed network latencies for the plurality of potential paths, observed error rates for the plurality of potential paths, or observed quality of service (QoS) data for the plurality of potential paths.
Claim 7
Dependent Claim
16 words
The method of claim 1 , wherein the first network access device is a base station.
Claim 8
Dependent Claim
16 words
The method of claim 1 , wherein the second network access device is an access point.
Claim 9
Dependent Claim
25 words
The method of claim 4 , wherein the pathway performance metrics profile for the application includes pathway performance metrics for the plurality of potential paths.
Claim 10
Dependent Claim
37 words
The method of claim 8 , wherein the pathway performance metrics of a path of the plurality of potential paths includes performance metrics associated with each network node of the set of networks nodes of the path.
Claim 11
Dependent Claim
45 words
The method of claim 1 , wherein predicting the application that is to be run at the future time on the user device includes: predicting the application that is to be run at the future time on the user device based on the usage patterns.
Claim 12
Dependent Claim
176 words
A network controller, comprising: a processor; and a storage coupled to the processor, wherein the processor is configured to compile received performance metrics for an application and generate a pathway performance metrics profile for the application based on the compiled performance metrics for the application, wherein the compiled performance metrics for the application are determined based on observations of a plurality of potential paths, wherein the storage is configured to store the pathway performance metrics profile for the application, wherein the processor is further configured to predict that the application is to be run at a future time on a user device based on an affinity group that identifies user devices based on the user device, retrieve the pathway performance metrics profile for the application from the storage, and determine a handover path for the user device based on the pathway performance metrics profile for the application and historical travel patterns for the user device, and wherein the affinity group is generated based on usage patterns for the user device that track use of the application.
Claim 13
Dependent Claim
176 words
A network controller, comprising: a processor; and a storage coupled to the processor, wherein the processor is configured to compile received performance metrics for an application and generate a pathway performance metrics profile for the application based on the compiled performance metrics for the application, wherein the compiled performance metrics for the application are determined based on observations of a plurality of potential paths, wherein the storage is configured to store the pathway performance metrics profile for the application, wherein the processor is further configured to predict that the application is to be run at a future time on a user device based on an affinity group that identifies user devices based on the user device, retrieve the pathway performance metrics profile for the application from the storage, and determine a handover path for the user device based on the pathway performance metrics profile for the application and historical travel patterns for the user device, and wherein the affinity group is generated based on usage patterns for the user device that track use of the application.
Claim 14
Dependent Claim
26 words
The network controller of claim 11 , wherein the pathway performance metrics profile for the application includes pathway performance metrics for the plurality of potential paths.
Claim 15
Dependent Claim
38 words
The network controller of claim 12 , wherein the pathway performance metrics of a path of the plurality of potential paths includes performance metrics associated with each network node of a set of networks nodes of the path.
Claim 16
Dependent Claim
26 words
The network controller of claim 11 , wherein the compiled performance metrics include observed network latency, observed error rates, or observed quality of service (QoS) data.
Claim 17
Dependent Claim
39 words
The network controller of claim 12 , wherein the processor is further configured to select a path from the plurality of potential paths as the handover path based on the pathway performance metrics for the plurality of potential paths.
Claim 18
Dependent Claim
46 words
The network controller of claim 11 , wherein the user device is served by a first network access device and the handover path includes a second network access device, and wherein the first network access device and the second access device utilize different radio access technologies.
Claim 19
Dependent Claim
18 words
The network controller of claim 11 , wherein the network controller is shared by a plurality of networks.
Claim 20
Independent Claim
181 words
A method, in a network controller, for implementing handover decisions based on performance data, comprising: retrieving performance metrics for an application that is to be run at a future time on a user device, wherein the performance metrics for the application are determined based on observations of a plurality of potential paths and each of the plurality of potential paths comprises a set of network nodes, wherein the application that is to be run at the future time on the user device is determined based on an affinity group that identifies user devices based on the user device, wherein the affinity group is generated based on usage patterns for the user device that track use of the application that is to be run at the future time on the user device; determining a handover path for the application that is to be run at the future time on the user device based on the performance metrics for the application and historical travel patterns for the user device; and communicating the handover path to a network access device serving the user device.
Claim 21
Independent Claim
181 words
A method, in a network controller, for implementing handover decisions based on performance data, comprising: retrieving performance metrics for an application that is to be run at a future time on a user device, wherein the performance metrics for the application are determined based on observations of a plurality of potential paths and each of the plurality of potential paths comprises a set of network nodes, wherein the application that is to be run at the future time on the user device is determined based on an affinity group that identifies user devices based on the user device, wherein the affinity group is generated based on usage patterns for the user device that track use of the application that is to be run at the future time on the user device; determining a handover path for the application that is to be run at the future time on the user device based on the performance metrics for the application and historical travel patterns for the user device; and communicating the handover path to a network access device serving the user device.
Claim 22
Dependent Claim
21 words
The method of claim 18 , further comprising: receiving the performance metrics for the application from a plurality of user devices.
Claim 23
Dependent Claim
19 words
The method of claim 19 , further comprising: receiving the performance metrics for the application from a network node.
References Cited (Backward Citations)
US6044075A
Cited
US6577868B1
Cited
US6456862B2
Cited
US7433929B2
Cited
US8849276B2
Cited
US20030210666A1
Cited
US7072701B2
Cited
US20040198360A1
Cited
US20040066759A1
Cited
US20060129630A1
Cited
US7574661B2
Cited
US20040185851A1
Cited
US7318111B2
Cited
US20060025149A1
Cited
US20060098614A1
Cited
DE102004049705A1
Cited
US20060193295A1
Cited
US20060166677A1
Cited
US20060223575A1
Cited
US8396526B2
Cited
US20090281403A1
Cited
US20070026811A1
Cited
US20070115899A1
Cited
US20080014957A1
Cited
US8396472B2
Cited
US20080085711A1
Cited
US20080096560A1
Cited
US20080101292A1
Cited
US20080102815A1
Cited
US8428674B2
Cited
US8000276B2
Cited
US20080244095A1
Cited
US20080242301A1
Cited
US20100202322A1
Cited
US7817964B2
Cited
US20090016299A1
Cited
US20090175239A1
Cited
US9467923B2
Cited
US20100062800A1
Cited
US20100075665A1
Cited
US7848756B2
Cited
US20100099393A1
Cited
US20140071895A1
Cited
US8566455B1
Cited
US9042373B2
Cited
US8526375B2
Cited
US20100240370A1
Cited
US8514778B1
Cited
US8379551B2
Cited
US20110096754A1
Cited
US20110110229A1
Cited
US20110182272A1
Cited
US8787172B2
Cited
US9344947B2
Cited
US8908636B2
Cited
US20150003243A1
Cited
US20110310850A1
Cited
US20110310851A1
Cited
US20140153547A1
Cited
US20110310737A1
Cited
US20120028638A1
Cited
US20120071739A1
Cited
US20120188949A1
Cited
US20120188873A1
Cited
EP2685771A1
Cited
US20140079007A1
Cited
WO2012163260A1
Cited
US8811187B2
Cited
US20130065632A1
Cited
CN102355694A
Cited
US20130268628A1
Cited
WO2013126859A2
Cited
US20150036672A1
Cited
CN102595509A
Cited
WO2013181191A1
Cited
CN102711184A
Cited
US20140003404A1
Cited
US20150304812A1
Cited
US20140051458A1
Cited
US20140066117A1
Cited
US20140094208A1
Cited
US20140162648A1
Cited
US20140171761A1
Cited
US20140199980A1
Cited
US20140220967A1
Cited
US20140256326A1
Cited
US20140378141A1
Cited
US20140355566A1
Cited
US20140355501A1
Cited
US20140355522A1
Cited
US20140357224A1
Cited
US9049613B2
Cited
US20150003420A1
Cited
WO2015073753A1
Cited
US9516665B2
Cited
USPTO Annuity & Maintenance Windows
| Annuity Stage | Window Opens | Payment Deadline | Surcharge Period Until | Estimated Fee | Status |
|---|---|---|---|---|---|
| 3.5 Years (Year 4) | 2021-02-05 | 2021-08-07 | 2022-02-06 | $2000.00 | Window Closed / Lapsed |
| 7.5 Years (Year 8) | 2025-02-05 | 2025-08-07 | 2026-02-06 | $3760.00 | Window Closed / Lapsed |
| 11.5 Years (Year 12) | 2029-02-05 | 2029-08-07 | 2030-02-06 | $7700.00 | Pending Window |