Centralized ground-based route determination and traffic engineering for software defined satellite communications networks

• US 9,763,167 B2
• Filed: 08/03/2015
• Issued: 09/12/2017
• Est. Priority Date: 08/03/2014
• Status: Active Grant

• Current Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Original Assignee: Hughes Network Systems LLC (Echostar Corporation)
• Inventors: Gopal, Rajeev, Ravishankar, Channasandra
• Primary Examiner(s): Elpenord, Candal
• Application Number:
  US14/817,181
• Publication Number:
  US 20160037434A1
• Time in Patent Office: 771 Days
• Field of Search: None
• CPC Class Codes: H04B 7/1851 Systems using a satellite or space-based relay H04B7/18508, H04B7/18521 take precedence; providing specific services H04B7/18523 - H04B7/18576
• CPC Class Codes: H04B 7/18519 Operations control, administration or maintenance
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/124 using a combination of metrics
• CPC Class Codes: H04W 40/02 Communication route or path selection, e.g. power-based or shortest path routing
• CPC Class Codes: H04W 40/246 Connectivity information discovery
• CPC Class Codes: H04W 40/248 Connectivity information update

Abstract

Approaches are provided for an SDSN that employs a satellite network nodes, where central L2 network nodes are controlled via a centralized Controller. Link status information is obtained regarding links of each L2 node. Global routing constraints, satellite ephemeris data, and resource allocation information are obtained. A constellation topology of the network nodes is determined based on the ephemeris data. Network routes between pairs of endpoints are determined. Each route includes links based on the link status information regarding the links, the global routing constraints, the bandwidth resources of the links and the current allocation of bandwidth resources, and/or the constellation topology. A forwarding table is generated for each network node, wherein each forwarding table includes route entries providing a next hop indicating a destination for data packets, wherein the destination is associated with a link of the respective network node that represents a link of a respective route.

Claims

1. A method comprising:

periodically receiving, by a central system controller of a wireless communications network, link status information from each of a plurality network nodes of the wireless communications network, wherein the link status information from each of the network nodes reflects current conditions regarding each of one or more currently available communications links between the network node and one or more respective other of the plurality of network nodes, and wherein one or more of the network nodes consist of airborne wireless data communications platforms;

periodically receiving, by the central system controller, network routing constraints from one or more network operations centers of the wireless communications network, wherein the network routing constraints reflect routing requirements applicable to one or more subsets of data traffic carried over the wireless communications network;

periodically receiving, by the central system controller, resource allocation information from one or more of the one or more network operations centers, wherein the resource allocation information reflects bandwidth allocations of one or more of the communications links;

periodically determining, by the central system controller, a current constellation topology reflecting current positions of the one or more network nodes that consist of airborne wireless data communications platforms;

periodically determining, by the central system controller, updates for one or more of a plurality of network path routes, wherein each network path route consists of a data communications path between a respective pair of endpoints of the wireless communications network, and each path route includes one or more of the communications links and one or more of the network nodes, and wherein each path route update is determined based at least in part on one or more of the periodically received link status information regarding the respective links of the path route, the periodically received network routing constraints, periodically received resource allocation information regarding one or more of the respective links of the path route, and the periodically determined current constellation topology; and

generating an updated forwarding table for each of the network nodes, wherein each forwarding table includes a plurality of route entries, wherein each route entry specifies a next hop network node to which each network node of a respective path route is to route respective data packets traveling over that path route, and wherein the updated forwarding table is generated based on updates to the network path routes, and

wherein the updates for the one or more of the plurality of network path routes are determined at times based on respective changes in the one or more of the periodically received link status information regarding the respective links of the path route, the periodically received network routing constraints, the periodically received resource allocation information regarding one or more of the respective links of the path route, and the periodically determined current constellation topology, and the path routes are thereby dynamically updated in real-time based on changing conditions of the communications links.

2. The method according to claim 1, wherein the current conditions regarding each of one or more communications links between the network node and one or more respective other of the plurality of network nodes includes one or more of operational status of the link and data traffic conditions of the link.

3. The method according to claim 1, wherein the constellation topology is based at least in part on one or more of ephemeris data received from one or more of the airborne wireless data communications platforms, predetermined flight patterns of one or more of the airborne wireless data communications platforms, and the link status information received from one or more of the airborne wireless data communications platforms.

4. The method according to claim 1, wherein the one or more currently available communications links include one or more communications links between respective pairs of the airborne wireless data communications platforms.

5. The method according to claim 1, wherein one or more of the airborne wireless data communications platforms consist of data communications satellites.

6. The method according to claim 1, wherein each of the plurality of route entries of the forwarding table for a one of the network nodes provides the next network node hop for a respective data packet type designated at least by a traffic type or quality of service (QoS) requirement, a source address and a destination address.

7. The method according to claim 6, wherein the source address and destination address specify a respective one of the network path routes for the data packet type, and the updates for the respective path route for the data packet type are determined to satisfy the QoS for the data traffic type.

8. The method according to claim 6, wherein the source address indicates a respective customer site and terminal from where the respective data packet type originated and the destination address indicates a destination terminal to where the respective data packet type is being transmitted, and wherein the source address and destination address specify a respective one of the network path routes for the data packet type, and the updates for the respective path route for the data packet type are determined to satisfy one or more service level agreements (SLAs) associated with the customer and required for the data packet type.

9. A system controller of a wireless communications network, comprising:

at least one wired network interface, each configured to periodically receive link status information from each of a plurality of respective terrestrial network nodes of the wireless communications network;

at least one wireless network interface, each configured to periodically receive link status information from each of a plurality of respective airborne wireless data communications nodes of the wireless communications network; and

at least one processor; and

wherein the plurality of terrestrial network nodes and the plurality of airborne wireless data communications nodes collectively make up a plurality of network nodes, and the link status information from each of the network nodes reflects current conditions regarding each of one or more currently available communications links between the network node and one or more respective other of the plurality of network nodes,

wherein the at least one wired network interface and the at least one wireless network interface collectively make up a plurality of network interfaces, and one or more of the plurality of network interfaces is configured to periodically receive network routing constraints from one or more network operations centers of the wireless communications network, wherein the network routing constraints reflect routing requirements applicable to one or more subsets of data traffic carried over the wireless communications network,

wherein one or more of the plurality of network interfaces is configured to periodically receive resource allocation information from one or more of the one or more network operations centers, wherein the resource allocation information reflects bandwidth allocations of one or more of the communications links, wherein at least one of the at least one processor is configured to periodically determine a current constellation topology reflecting current positions of the airborne wireless data communications nodes,

wherein at least one of the at least one processor is configured to periodically determine updates for one or more of a plurality of network path routes, wherein each network path route consists of a data communications path between a respective pair of endpoints of the wireless communications network, and each path route includes one or more of the communications links and one or more of the network nodes, and

wherein each path route update is determined based at least in part on one or more of the periodically received link status information regarding the respective links of the path route, the periodically received network routing constraints, periodically received resource allocation information regarding one or more of the respective links of the path route, and the periodically determined current constellation topology,

wherein at least one of the at least one processor is configured to generate an updated forwarding table for each of the network nodes, wherein each forwarding table includes a plurality of route entries, wherein each route entry specifies a next hop network node to which each network node of a respective path route is to route respective data packets traveling over that path route, and wherein the updated forwarding table is generated based on updates to the network path routes, and

wherein the updates for the one or more of the plurality of network path routes are determined at times based on respective changes in the one or more of the periodically received link status information regarding the respective links of the path route, the periodically received network routing constraints, the periodically received resource allocation information regarding one or more of the respective links of the path route, and the periodically determined current constellation topology, and the path routes are thereby dynamically updated in real-time based on changing conditions of the communications links.

10. The system controller according to claim 9, wherein the current conditions regarding each of one or more communications links between the network node and one or more respective other of the plurality of network nodes includes one or more of operational status of the link and data traffic conditions of the link.

11. The system controller according to claim 9, wherein the constellation topology is based at least in part on one or more of ephemeris data received from one or more of the airborne wireless data communications platforms, predetermined flight patterns of one or more of the airborne wireless data communications platforms, and the link status information received from one or more of the airborne wireless data communications platforms.

12. The system controller according to claim 9, wherein the one or more currently available communications links include one or more communications links between respective pairs of the airborne wireless data communications platforms.

13. The system controller according to claim 9, wherein one or more of the airborne wireless data communications nodes consist of data communications satellites.

14. The system controller according to claim 9, wherein each of the plurality of route entries of the forwarding table for a one of the network nodes provides the next network node hop for a respective data packet type designated at least by a traffic type or quality of service (QoS) requirement, a source address and a destination address.

15. The system controller according to claim 14, wherein the source address and destination address specify a respective one of the network path routes for the data packet type, and the updates for the respective path route for the data packet type are determined to satisfy the QoS for the data traffic type.

16. The system controller according to claim 14, wherein the source address indicates a respective customer site and terminal from where the respective data packet type originated and the destination address indicates a destination terminal to where the respective data packet type is being transmitted, and wherein the source address and destination address specify a respective one of the network path routes for the data packet type, and the updates for the respective path route for the data packet type are determined to satisfy one or more service level agreements (SLAs) associated with the customer and required for the data packet type.