SYSTEM AND METHOD FOR BANDWIDTH PROFILE BASED ALLOCATION AND MANAGEMENT OF A TIME-VARYING TOPOLOGY NETWORK

• US 20200137633A1
• Filed: 12/29/2019
• Published: 04/30/2020
• Est. Priority Date: 09/30/2016
• Status: Active Grant

• Current Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Original Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Inventors: Torres, Robert James, Kay, Stanley Edward, Choquette, George
• Granted Patent: US 11,153,786 B2
• Time in Patent Office: Days
• CPC Class Codes: H04B 7/18519 Operations control, administration or maintenance
• CPC Class Codes: H04B 7/18521 Systems of inter linked satellites, i.e. inter satellite service for optical links between satellites H04B10/118
• CPC Class Codes: H04B 7/18584 Arrangements for data networking, i.e. for data packet routing, for congestion control data switching networks H04L12/00
• CPC Class Codes: H04B 7/195 Non-synchronous stations
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 47/762 triggered by the network
• CPC Class Codes: H04L 47/83 based on usage prediction
• CPC Class Codes: H04W 24/10 Scheduling measurement reports ; Arrangements for measurement reports
• CPC Class Codes: H04W 28/02 Traffic management, e.g. flow control or congestion control
• CPC Class Codes: H04W 28/0268 using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] negotiating SLA or negotiating QoS H04W28/24
• CPC Class Codes: H04W 28/0289 Congestion control load shedding arrangements in network planning H04W16/08; performing reselection for handling the traffic H04W36/22; wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 28/10 Flow control between communication endpoints
• CPC Class Codes: H04W 28/24 Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
• CPC Class Codes: H04W 8/04 Registration at HLR or HSS [Home Subscriber Server]

Abstract

Disclosed methods include a resource manager in a multiple node network receiving a demand for additional bandwidth, from a terminal, and the resource manager having updated information on the state of the mobile node network and, using that the state information, performing test allocation of the requested bandwidth to the requesting terminal. Disclosed methods include determining whether previous commitments of service can be met with the test allocation in place. Associated with a positive result, an allocation is sent to the terminal.

Claims

1-20. -20. (canceled)

21. A user terminal apparatus for profile based ingress management, comprising:

a processor;

a memory coupled to the processor, the memory configured to store instructions that, when executed by the processor, cause the processor to;

store in the memory an ingress bandwidth profile, the ingress bandwidth profile including an ingress bandwidth profile parameter,

receive a packet having an indication of a priority level,

determine whether the packet is within the ingress bandwidth profile, and

based at least in part on a result of the determining whether the packet is within the ingress bandwidth profile being that the packet is within the ingress bandwidth profile, to;

enqueue the packet in a priority queue, in accordance with the priority level,

determine whether a bandwidth allocation update is required and,

based at least in part on a result of the determining whether the bandwidth allocation update is required, to;

schedule the packet for a transmission, and

transmit the packet, based at least in part on the schedule.

22. A user terminal apparatus in accordance with claim 21 for profile based ingress management, wherein the result of the determining whether the bandwidth allocation update is required is that the bandwidth allocation update is not required.

23. A user terminal apparatus in accordance with claim 21 for profile based ingress management, wherein the instructions also include instructions that, when executed by the processor, cause the processor, based at least in part on the result of the determining whether the packet is within the ingress bandwidth profile being that the packet is not within the ingress bandwidth profile, to discard the packet.

24. A user terminal apparatus in accordance with claim 21 for profile based ingress management, wherein to determine whether the packet is within the ingress bandwidth profile includes to:

determine an ingress classification of the packet, and

apply the ingress bandwidth profile to the determined ingress classification.

25. A user terminal apparatus in accordance with claim 21 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor to:

determine, in association with enqueuing the packet in the priority queue, a fill state of the priority queue,

wherein;

to determine whether a bandwidth allocation update is required is based at least in part on the fill state of the priority queue.

26. A user terminal apparatus in accordance with claim 25 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor, in association with determining that the bandwidth allocation is required, to:

evaluate a state of the user terminal, and

send a bandwidth request to an external resource manager, based at least in part on the evaluated state.

27. A user terminal apparatus in accordance with claim 26 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor, in response to receipt of a bandwidth allocation corresponding to the bandwidth request, to:

schedule the packet for transmission, and

transmit the packet, based at least in part on the schedule.

28. A user terminal apparatus in accordance with claim 26 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor to proceed, based at least in part on sending the bandwidth request to the external resource manager, to

schedule the packet for transmission, and

transmit the packet, based at least in part on the schedule.

29. A user terminal apparatus in accordance with claim 21 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor to:

selectively bypass, based at least in part on a rule or trigger condition, determining whether another packet is within the ingress bandwidth profile,

enqueue the other packet in the priority queue, in accordance with the priority level,

determine whether a bandwidth allocation update is required and, based at least in part on the bandwidth allocation update being determined as not required, to;

schedule the other packet for a transmission, and

transmit the other packet, based at least in part on the schedule.

30. A user terminal apparatus in accordance with claim 29 for profile based ingress management, wherein the instructions also include instructions that when executed by the processor cause the processor, in association with determining that bandwidth allocation is required, to:

evaluate a state of the user terminal,

send a bandwidth request to an external resource manager, based at least in part on the evaluated state,

schedule the packet for transmission, and

transmit the packet, based at least in part on the schedule.

31. A method for profile based user terminal management of ingress, comprising:

receiving a packet having an indication of a priority level; and

determining whether the packet is within an ingress bandwidth profile, and

based at least in part on a result of the determining whether the packet is within the ingress bandwidth profile being that the packet is within the ingress bandwidth profile;

enqueuing the packet in a priority queue, in accordance with the priority level,

determining whether a bandwidth allocation update is required and,

based at least in part on a result of the determining whether the bandwidth allocation update is required;

scheduling the packet for a transmission, and

transmitting the packet, based at least in part on the schedule.

32. A method in accordance with claim 31 for profile based user terminal management of ingress, wherein the result of the determining whether the bandwidth allocation update is required is that the bandwidth allocation update is not required.

33. A method in accordance with claim 31 for profile based user terminal management of ingress, wherein the method further comprises:

based at least in part on the result of the determining whether the packet is within the ingress bandwidth profile being that the packet is not within the ingress bandwidth profile, discarding the packet.

34. A method in accordance with claim 31 for profile based user terminal management of ingress, wherein determining whether the packet is within the ingress bandwidth profile includes:

retrieving the ingress bandwidth profile from a storage or via a link;

determining an ingress classification of the packet, and

applying the ingress bandwidth profile to the determined ingress classification.

35. A method in accordance with claim 31 for profile based user terminal management of ingress, wherein the method further includes:

determining, in association with enqueuing the packet in the priority queue, a fill state of the priority queue,

wherein;

determining whether bandwidth allocation update is required is based at least in part on the fill state of the priority queue.

36. A method in accordance with claim 35 for profile based user terminal management of ingress, wherein the method further includes, in association with determining that bandwidth allocation:

evaluating a state of the user terminal, and

sending a bandwidth request to an external resource manager, based at least in part on the evaluated state.

37. A method in accordance with claim 36 for profile based user terminal management of ingress, wherein the method further includes, in response to receiving a bandwidth allocation in response to the bandwidth request:

scheduling the packet for transmission, and

transmitting the packet, based at least in part on the schedule.

38. A method in accordance with claim 37 for profile based user terminal management of ingress, wherein the method further includes, based at least in part on sending the bandwidth request to the external resource manager:

scheduling the packet for transmission, and

transmitting the packet, based at least in part on the schedule.

39. A method in accordance with claim 31 for profile based user terminal management of ingress, wherein the method further includes:

selectively, based at least in part on a rule or trigger condition,

bypassing determining whether another packet is within the ingress bandwidth profile,

enqueuing the other packet in the priority queue, in accordance with the priority level,

determining whether another bandwidth allocation update is required and, based at least in part on the other bandwidth allocation update being determined as not required;

scheduling the other packet for transmission, and

transmitting the other packet, based at least in part on the schedule.