Routing in a Hybrid Network
User terminals in hybrid networks use a routing table populated by forward link communications to efficiently route return link traffic, addressing the processing power limitation and enhancing network efficiency.
Patent Information
- Application Number
- JP2023201296
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2017-05-10
- Filing Date
- 2023-11-29
- Publication Date
- 2024-11-07
- Estimated Expiration
- 2037-12-11
AI Technical Summary
User terminals in hybrid communication networks lack sufficient processing power to make computationally intensive routing decisions for return link traffic, necessitating a cost-effective and low-complexity solution for efficient network utilization.
User terminals employ a routing table populated by forward link communications to associate FLCS identifiers with specific communication networks, enabling quick and efficient routing decisions for return link traffic based on stored mappings.
This approach allows user terminals to efficiently route return link traffic without extensive computational resources, optimizing network utilization and reducing complexity and cost.
Smart Images

Figure 0007579419000001 
Figure 0007579419000002 
Figure 0007579419000003
Abstract
Description
[Technical field]
[0001] FIELD OF THE DISCLOSURE Embodiments relate generally to communication systems, and more particularly to routing return link traffic in a hybrid communication network. [Background technology]
[0002] Many communication networks have a large number of users that interface with the communication network through a large number of user terminals. In such networks, it may be desirable for the user terminals to be implemented with relatively low cost and complexity. Some modern communication environments include hybrid networks in which a user terminal communicates with multiple different types of networks having different characteristics. For example, a hybrid network may include one or more high throughput, high latency networks (e.g., satellite networks) and one or more low throughput, low latency networks (e.g., cable networks, cellular networks, etc.). Routing different traffic flows over different networks may more efficiently utilize the overall resources of the hybrid network. However, determining which of the networks to use for each traffic flow (e.g., in real time) may be computationally intensive. While provider-side nodes of the network (e.g., gateways, core nodes, etc.) may include sufficient processing power to make such decisions for forward-link traffic, user terminals may not have sufficient processing power to make such decisions for return link traffic. Summary of the Invention
[0003] Among other things, systems and methods for providing return link routing in a hybrid communication network are described. The hybrid communication network includes many different networks with different characteristics (e.g., different latencies, different throughputs, different user costs per bit, etc.). Users may interface with the hybrid network through respective user terminals that include a user terminal routing system. For example, each user terminal routing system provides an interface between a local user network (e.g., providing local communications with one or more consumer premises equipment (CPE) devices) and multiple communication networks of the hybrid network. Each user terminal routing system may include a routing table that stores a plurality of mappings. The mappings are populated according to forward link communications received over at least one of the networks, each mapping associating a respective one of a plurality of routing table entries with one of the communication networks. Each routing table entry identifies at least one forward-link content source (FLCS) identifier, e.g., as part of a routing tuple. When the user terminal routing system receives the return link data from its respective local user network, the received return link data indicates a destination node. The user terminal routing system may determine which of the stored mappings has an FLCS identifier that corresponds (e.g., matches) to the destination node, and the user terminal routing system may route the received return link data over a selected one of the communication networks in accordance with an identified one of the mappings. [Brief description of the drawings]
[0004] The present disclosure is described in conjunction with the accompanying drawings.
[0005] [Figure 1]FIG. 1 illustrates an exemplary hybrid communication environment as the context of various embodiments. [Figure 2A] FIG. 2A illustrates a first set of examples in which return link routing decisions are made by a user terminal in a hybrid communication environment. [Figure 2B] FIG. 2B illustrates a first set of examples in which return link routing decisions are made by a user terminal in a hybrid communication environment. [Figure 2C] FIG. 2C illustrates a first set of examples in which return link routing decisions are made by a user terminal in a hybrid communication environment. [Diagram 3] FIG. 3 illustrates a second example in which return link routing decisions are made by a user terminal in a hybrid communication environment. [Figure 4] FIG. 4 illustrates a block diagram of a user terminal environment including an exemplary user terminal in communication with a local user network and a hybrid communication network in accordance with various embodiments. [Diagram 5] FIG. 5 illustrates a flow diagram of an exemplary method for return link routing by a user terminal in a hybrid network environment in accordance with various embodiments. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0006] In the accompanying drawings, similar parts and / or features may have the same reference label. Furthermore, various parts of the same type may be identified by tracing the reference label with a second label that identifies the similar part. If only a first reference label is used herein, the description is applicable to any one of the similar parts having the same first reference label regardless of the second reference label.
[0007] In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present invention. However, those skilled in the art should recognize that the present invention may be practiced without these specific details. In some instances, circuits, structures, and techniques have not been shown in detail so as not to obscure the present invention.
[0008] FIG. 1 illustrates an exemplary hybrid communication environment 100 as a context for various embodiments. As illustrated, the hybrid communication environment 100 includes a number of user terminals 110 communicating with at least one provider network node 150 via a hybrid communication network 130. The hybrid communication network 130 includes a number of communication networks 132 providing various network characteristics. The communication networks 132 may include any suitable type of network for carrying various types of traffic and may include wired, wireless, public, private, secured, unsecured network links, and / or other network links. For example, one of the communication networks 132 may provide a relatively high throughput with a relatively high latency and a relatively high cost / bit. For example, the communication network 132 may include a satellite link with a geosynchronous earth orbit (GEO) satellite, a medium earth orbit (MEO) satellite, a low earth orbit satellite (LEO) satellite, etc. Another of the communication networks 132 may provide a relatively low throughput with a relatively low latency and a relatively low cost / bit. For example, the communication networks 132 may include terrestrial networks such as digital subscriber line (DSL) networks, cable-based networks, long-term evolution (LTE) wireless networks, cellular networks, etc. Alternatively, one communication network 132 may be a GEO satellite network and another communication network 132 may be a MEO or LEO satellite network. In some cases, more than one of the communication networks 132 of the hybrid communication network 130 may have similar or identical network characteristics.
[0009] The hybrid communication network 130 may provide communication between the local user networks 105 and the content network 175 via the user terminals 110, the communication network 132, and the provider side network node 150. Each local user network 105 may include one or more customer premises equipment (CPE) 102 coupled to a respective user terminal 110 via a wired or wireless connection. For example, the user terminal 110 may include any suitable local network interface 127, such as a wired and / or wireless router that implements a local area network. The CPE 102 may be a home or office computing device, such as a desktop computer, a laptop computer, a smart phone, a tablet device, an Internet-enabled television or other appliance. The content network 175 may include any suitable remote network, such as the Internet. As shown, the content network 175 may include any suitable number of host computers 172, such as content servers. The host computer 172 may host (or otherwise provide) any suitable type of content, such as audio and / or video file access, audio and / or video streaming services, voice over Internet protocol (VoIP) services, online gaming content, messaging (including, e.g., control messages for the hybrid communications network 130), etc. For example, users may subscribe to communication services and / or content services (e.g., Internet services) that can be accessed over the hybrid communications network 130 via their CPE 102.
[0010] In some embodiments, the user terminal 110 may include a hybrid network interface 125 for receiving forward link data from and transmitting return link data to the multiple communication networks 132 of the hybrid communication network 130. For example, as described below, the user terminal 110 may include physical and / or logical ports 122, a Layer 3 routing module, a forwarding module (e.g., for forwarding via Layer 2 tunnels), and / or any other suitable components. The provider side network node 150 may include a provider side hybrid network interface 145 that includes similar or different components for interfacing with the communication networks 132 of the hybrid communication network 130. For example, the provider side hybrid network interface 145 may include physical and / or logical ports 142, a Layer 3 routing module, a forwarding module, and / or the like. The provider side network node 150 may also include a provider side routing module 160 for making routing decisions (e.g., forward link routing decisions) for routing and / or forwarding traffic on the hybrid communication network 130. The provider side routing module 160 may include a data classifier and / or any other suitable components for making routing decisions. For example, a data classifier in provider side network node 150 classifies forwarded link data destined for CPE 102 and determines over which communications network 132 the forwarded link data should then be forwarded according to the classification. Embodiments of provider side network node 150 may include any other suitable components, such as an edge server, a traffic shaper, a network accelerator, a data classifier, and / or any other suitable components. Although only one provider side network node 150 is shown coupled with all communications networks 132, other embodiments are realized with other architectures.For example, some or all of the communications network 132 may terminate on the respective provider side in respective provider side network nodes 150 (e.g., gateways, headends, mobile switching centers, etc.), which may communicate with another provider side network node 150 (e.g., a core node, etc.) that performs the forwarding link routing functions described herein.
[0011] Routing traffic through the hybrid communication network 130 involves making a decision for each suitable unit of traffic (e.g., each traffic flow, each established logical connection, each deterministic size chunk of data, each packet, etc.) regarding which of the communication networks 132 the traffic should be routed over. In the forwarding link direction, traffic typically emanates from one of the content hosts 172 and is destined for one of the CPEs 102. The traffic may be intercepted by the provider side network node 150, which may determine an appropriate routing or forwarding decision, for example, by classifying the content of the traffic. As an example, in a particular household, one member of the household may be streaming a movie while another member is surfing the Internet. The provider side network node 150 may determine to deliver streaming movies over a first communication network of the communication networks 132a that is a satellite network (e.g., because a high throughput will result in a high quality stream of the movie and high latency will not impact the viewing experience as much) and to deliver Internet surfing traffic over a second communication network of the communication networks 132b that is a DSL network (e.g., because reduced latency will likely benefit the surfing experience, while reduced throughput will likely not impact the surfing experience as much).
[0012] Data classification and other aspects of routing decisions can be very computationally intensive. For example, classification can involve deep packet inspection, statistical processing, and the like. Furthermore, a typical provider side network node 150 may be implemented with sufficient computational resources to make such decisions for forward link traffic, even in substantially real-time, and for a large number of traffic flows. However, it is typically desirable for user terminals 110 to be implemented with relatively low cost and complexity. For example, while provider side network node 150 may be implemented in a large and expensive computing environment, it is typically desirable for each user terminal 110 to be implemented as a small, inexpensive, reliable, and simple device that can be installed at each user's premises. Thus, user terminals 110 may not typically have sufficient processing power to make such decisions for return link traffic.
[0013] Accordingly, the embodiments described herein include novel systems and methods for providing return link routing in a user terminal 110 communicating with a hybrid communication network 130. As shown, each user terminal 110 includes a user terminal routing system (UTRS) 120 coupled between a hybrid network interface 125 and a local network interface 127. The UTRS 120 includes a routing module 114 and a routing table 112. As described herein, rather than making computationally intensive routing decisions, the routing module 114 may make routing decisions according to mappings that are populated and dynamically updated in the routing table 112 according to received forward link communications. For example, each mapping associates a routing table entry with one of the communication networks 132, such that when return link traffic is received by the routing module 114 (from the CPE 102), the routing module 114 may find the mapping in the routing table 112 that has the corresponding routing table entry and route the return link traffic accordingly. Each routing table entry may be uniquely identified at least according to a forward-link content source (FLCS) identifier. For example, the FLCS identifier may be an Internet protocol (IP) address that was the source IP address of previously received forward link traffic and may be the destination IP address of subsequent return link traffic. As discussed herein, the FLCS identifier may be obtained or derived from a routing tuple (e.g., a 2-tuple, a 5-tuple, etc.), a control message, a domain name server (DNS) lookup or reverse lookup, or in any other suitable manner. The routing table 112 may be implemented as a lookup table or the like that may be queried very quickly and with very low computational intensity.
[0014] 2A-2C illustrate a first set of examples in which return link routing decisions are made by a user terminal 110 in a hybrid communication environment 200. In the illustrated set of examples, the return link routing decisions are made pursuant to receipt of a forward link communication. Referring initially to FIG. 2A, the thick dashed arrows indicate a forward link traffic flow path that emanates from one of the host computers 172 in the content network 175 and terminates at one of the CPEs 102 of the local user network 105 associated with the user terminal 110. This flow is received (e.g., intercepted) by a provider side network node 150. A provider side routing module 160 in the provider side network node 150 may classify the traffic and / or make any decisions that aid in the decision regarding which communication network of the communication network 132 the traffic should be routed over. The traffic may be output to the hybrid communication network 130 via an appropriate interface (e.g., port 142) of the provider side hybrid network interface 145. In the illustrated case, the decision is to route the traffic via a first interface port 142a (eg, and a Level 3 router, not shown) to a first communications network 132a, which is a satellite network.
[0015] Traffic is received from the first communication network 132a via the first interface port 122 of the hybrid network interface 125 of the user terminal 110 and passed to the routing module 114 of the UTRS 120. The forward link traffic may be passed from the UTRS 120 to the appropriate destination CPE 102 via the local network interface 127. In addition, as described in more detail below, the routing module 114 may update (and / or determine whether to update) the routing table 112 mapping based on the received traffic. In the illustrated case, the routing module 114 may create or update a mapping in the routing table 112 based on the source IP address of the traffic and the network on which the traffic was received (i.e., the first communication network 132a). In some embodiments, the forward link traffic packet includes a tuple that includes at least one source IP address. For example, the tuple may be a two-tuple indicating a source IP address and a source port; or the tuple may be a five-tuple indicating a source IP address, a source port, a destination IP address, a destination port, and a communication protocol. The routing module 114 may store at least the source IP address as an FLCS identifier in a routing table entry. The FLCS identifier may be the routing table entry, or the routing table entry may include the FLCS and additional information. For example, some embodiments may reverse the received 5-tuple, store the reversed 5-tuple as a routing table entry in the routing table entry (i.e., such that the source port and IP address of the 5-tuple are stored as the destination port and IP address), and map the routing table entry to the receiving communication network 132. Additional information may be used in some embodiments. For example, some embodiments may have different return link mappings for traffic from different CPEs 102 having different communication protocols, etc., even when destined for the same content host 172.
[0016] 2B, following updating the routing table 112 according to the forwarded link traffic received in FIG. 2A, return link traffic is received by the UTRS 120 from the CPE 102 of the local user network 105. When the return link traffic is received, the routing module 114 may determine (e.g., parse) a destination identifier of the return link traffic and identify one of the mappings in the routing table 112 that corresponds to the destination identifier. For example, the return link traffic may indicate a destination IP address that matches an FLCS identifier of one of the routing table entries. The identified mapping in the routing table 112 maps the FLCS identifier to one of the communications networks 132. In the illustrated case, the return link traffic is destined for the same host computer 172 for which the forwarded link traffic was received on the satellite network (first communications network 132a) in FIG. 2A. The updated mapping in FIG. 2A associates the FLCS identifier of this host computer 172 with the first communications network 132a. Thus, as shown, the UTRS 120 may determine (in accordance with the routing table 112) to route the received return link traffic over the first communications network 132a (e.g., via interface port 142a and provider side routing module 160) to the destination host 172a.
[0017] In some cases, traffic associated with a particular host computer 172 may be routed differently in the forward link direction and the return link direction. FIG. 2C illustrates such a case, where return link traffic is destined for a first host computer 172a (previously mapped to a first communication network 172a in the routing table 112 of FIG. 2A) but is routed through a second communication network 172b of the hybrid communication network 130. Such cases may arise in many different contexts. In one such context, each routing table entry of the routing table 112 is uniquely identified by more than just a destination identifier. For example, the routing table 112 may include multiple routing table entries having the same destination identifier but different other parameters (e.g., different protocols, etc.). As an example of such a context, the forward link traffic received from the host computer 172a in FIG. 2A is part of a traffic flow for a streaming movie, while the return link traffic sent in FIG. 2C is a playback navigation message (e.g., "pause") sent from the CPE 102a back to the host computer 172a. In another such context, the routing module 114 and / or the routing table 112 include some routing directives that route some traffic according to some rules, regardless of whether a conflicting mapping exists in the routing table 112. For example, the routing module 114 may include a rule (or the routing table 112 may have a hierarchically dominant mapping) that always routes return link traffic from a particular CPE 102 (e.g., from a particular private return link source IP address) over the second communications network 132b. In yet another such context, other network considerations may take precedence over the routing table 112.For example, network congestion detected on the first communication network 132a may trigger a re-routing of traffic (e.g., for a large file upload) from the first communication network 132a to the second communication network 132b despite any mapping to the contrary. In yet another context, the mappings in the routing module 114 may have an associated validity window, or other type of hysteresis, etc. For example, some or all of the mappings may be changed only after a predefined threshold number of change events have occurred (e.g., only after three consecutive traffic flows have been received from a particular host computer 172 on the same one of the communication networks 132), or some or all of the mappings may only be valid over a particular window (e.g., the mappings are automatically reset to the mapping defaults after a certain period of time has elapsed since the last event that confirmed the mapping (e.g., after a particular logical connection session has ended)).
[0018] 3 illustrates a second example in which a return link routing decision is made by a user terminal 110 in a hybrid communication environment 300. In the illustrated example, the return link routing decision is made pursuant to receipt of a control message via a forward link communication. The thick dashed arrow indicates a forward link control message flow path emanating from the provider side routing module 160 of the provider side network node 150. The control message is output to the hybrid communication network 130 via an appropriate interface (e.g., port 142) of the provider side hybrid network interface 145. Although the illustrated case shows the control message being routed on one particular communication network 132, other embodiments may transmit the control message on any one or more of the communication networks 132. The control message is received from the hybrid communication network 130 (e.g., from the first communication network 132a) via the hybrid network interface 125 of the user terminal 110 (e.g., via the first interface port 122a) and passed to the routing module 114 of the UTRS 120. In this case, the control message is not passed to the CPE 102 as the control message is tailored to be used directly by the UTRS 120 to generate and / or update the mapping. The routing module 114 may obtain (e.g., parse, derive, etc.) the routing table updates from the received control message and may update the routing table 112 accordingly. For example, the control message may include a list of routing table entries (e.g., FLCS identifiers, 5-tuples, etc.) and associated communication networks 132 for which mappings may be generated. Some embodiments use a combination of techniques to populate and / or dynamically update the routing table 112 by using both control messages, such as in FIG. 3, and forwarded link traffic data, such as in FIG. 2A.
[0019] 4 illustrates a block diagram of a user terminal environment 400 according to various embodiments, including an exemplary user terminal 110 in communication with a local user network 105 and a hybrid communication network 130. As illustrated, forward link traffic 402 is received from the hybrid communication network 130 and directed to an appropriate CPE in the local user network 105, and return link traffic 452 is received from a CPE in the local user network 105 and routed (e.g., forwarded, routed, etc.) to an appropriate communication network in the hybrid communication network 130. The user terminal 110 may include a hybrid network interface 125 and a user terminal routing system (UTRS) 120 having a routing table 112 and a routing module implemented as a routing state machine 414. In some embodiments, the routing table 112 is implemented as a lookup table. In other embodiments, the routing table 112 is implemented as any suitable type of fast access data storage device.
[0020] An embodiment of the hybrid network interface 125 may include physical and / or logical network interfaces (e.g., ports 122) that may be adapted to a particular component network of the hybrid communication network 130. The hybrid network interface 125 may also include a router 470 for Layer 3 routing (e.g., on a first one of the component networks, such as a satellite network) and a forwarder 475 for Layer 2 forwarding (e.g., implementing Layer 2 tunnel endpoints). Some embodiments of the hybrid network interface 125 may include additional network interface components, such as a network address translator (NAT) 460. For example, the NAT 460 may translate between private IP addresses of CPEs of the local user network 105 and public addresses of the user terminals 110 as seen by the hybrid communication network 130.
[0021] As shown, an embodiment of the UTRS 120 includes a local network interface 127 operable to couple to (e.g., coupled with, incorporated into, etc.) the local user network 105. The UTRS 120 also includes a hybrid network interface 125 having a plurality of network interfaces 122, each operable to couple to a respective one of a plurality of communication networks 132 of a hybrid communication network 130. The UTRS 120 also includes a routing table 112 that stores a plurality of mappings populated according to forward link communications (e.g., 402, 412) received over at least one of the communication networks 132. Each mapping associates a respective one of a number of routing table entries with one of the communication networks 132, and each routing table entry identifies at least one forward-link content source (FLCS) identifier (e.g., a host computer IP address).
[0022] The UTRS 120 also includes a routing module 114, which may be implemented as a routing state machine 414, as shown. The routing state machine 414 may be implemented in any suitable manner. In some embodiments, the routing state machine 414 is a hardware state machine that performs various functions by using circuitry such as programmable circuits and processors. In other embodiments, some functions are implemented in hardware, software, firmware, or any combination thereof. If implemented in software, the functions may be stored as one or more instructions on a non-transitory computer-readable medium. A storage medium may be any available tangible medium that can be accessed by a computer. By way of example and not limitation, such computer-readable media may include RAM, ROM, EEPROM, CD-ROM, or other optical disk storage, magnetic disk storage, or other magnetic storage, or any other tangible medium that can be used to carry or store desired program code in the form of instructions or data structures and that can be accessed by a computer.
[0023] An embodiment of the routing state machine 414 is coupled between the local network interface 127 and the hybrid network interface 125, and the routing state machine 414 includes a routing state output 442 that is calculated according to the routing table 112 in response to receiving return link data 452 via the local network interface 127. The received return link data 452 indicates a destination node corresponding to the FLCS identifier of an identified one of the mappings, and the routing state output 442 directs routing of the received return link data 452 over a selected one of the communication networks 132 via the hybrid network interface 125 in accordance with the identified one of the mappings.
[0024] Some embodiments of the UTRS 120 include some or all of the mapping generator 430 and the return link router 440. In some embodiments, the routing table 112 is updated according to the received forwarding link traffic 402. As discussed herein, embodiments may populate and / or update the routing table 112 mappings in various ways (including according to the received forwarding link traffic flows 402 and / or control messages 412). For added clarity, FIG. 4 shows both types of forwarding link communications being received by the user terminal 110 (and by the UTRS 120). Furthermore, the mapping generator 430 is shown as having both a network-based updater 410 and a control-based updater 420 for updating the mappings in response to the forwarding link traffic 402 and the control messages 412, respectively. Some embodiments of the mapping generator 430 include only one of the network-based updater 410 or the control-based updater 420.
[0025] In some embodiments, forward link traffic 402 is received by hybrid network interface 125 from one of the communication networks 132 and passed to network-based updater 410 of mapping generator 430. Network-based updater 410 may obtain (e.g., parse, derive, etc.) a routing profile of the received forward link traffic 402 that includes at least one FLCS identifier (e.g., as a source IP address). In some cases, the routing profile may include an identifier of the communication network 132 on which the forward link traffic 402 was received, a source port, a destination IP address, a destination port, a routing protocol, and / or other characteristics of the forward link traffic 402. Network-based updater 410 may use the obtained routing profile to generate (e.g., generate, update, etc.) a mapping in routing table 112. For example, the FLCS identifier may be stored as a routing table entry in a mapping association with the communication network 132 on which the traffic was received, or the 5-tuple of the received forward link traffic 402 may be inverted and stored as a routing table entry and mapped to an appropriate one of the communication networks 132. The updated mappings may be populated into the routing table 112 by the mapping generator 430 .
[0026] Similarly, a control message 412 may be received as a forward link communication by hybrid network interface 125 from one or more of communication networks 132. The control message 412 may be passed to control-based updater 420 of mapping generator 430, which may obtain (e.g., parse, derive, etc.) one or more mapping updates from the control message. For example, control message 412 may indicate a list of mappings between each of a number of FLCS identifiers (and / or other routing profile information) and a respective one of communication networks 132 that will route (e.g., route, forward, etc.) return link data destined for a host computer corresponding to the FLCS. The updated mappings may be populated by mapping generator 430 into routing table 112.
[0027] In some embodiments, the routing table 112 is pre-populated and / or automatically populated at least in part with information that does not originate from forward link communications. In such cases, the routing table 112 is still dynamically updated and / or further populated from forward link communications (e.g., from forward link traffic 402 and / or control messages 412). In some such embodiments, the routing table 112 is pre-loaded with default mappings (e.g., prior to deployment at the customer premises as part of initializing the device at the customer premises). Some such embodiments include a domain name server (DNS) lookup module 437. For example, the routing table 112 may be pre-populated with default mappings between host names (e.g., content areas) and particular ones of the communication networks 132 that route return link traffic to those hosts. With the UTs 110 (e.g., and UTRS 120) coupled to the hybrid communication network 130, the DNS lookup module 437 may perform DNS lookups to resolve the mapped host names to IP addresses that are used as FLCS identifiers in the routing table entries. In some embodiments, the DNS lookup module 437 may re-resolve some or all of the hostname periodically (e.g., according to a schedule, whenever a communication indicates this hostname, and / or at any other suitable time) to ensure that the association remains fresh. Alternatively, the resolved host IP addresses are used only for default mappings, as described herein, and some or all of those mappings are dynamically updated according to received forward link communications. In some embodiments, the associations between the hostnames and the resolved host IP addresses may be stored, for example for further use, as described below.For example, control message 412 may indicate a specific mapping update for all IP addresses associated with a particular group of related hosts (e.g., when one content host uses multiple IP addresses as mirror sites as a content distribution network (CDN); when a particular group of host names are associated with the same class of traffic (e.g., video streaming); and the stored associations can be used to quickly update the mappings of multiple routing table entries according to their associations with the indicated hosts.
[0028] Some embodiments of the mapping generator 430 include or communicate with a verifier 435 that is coupled to a stored rule base 450. An embodiment of the verifier 435 may determine if and when to allow the mapping generator 430 to update the mappings in the routing table 112 according to the rules in the rule base 450. In some embodiments, some or all of the rules in the rule base 450 are hard-coded prior to deployment of the user terminal 110. In other embodiments, some or all of the rules in the rule base 450 are hardware or software programmable according to control messages 412 received via the hybrid network interface 125, by local user commands received via the local network interface 127, and / or in any other suitable manner. In some embodiments, the rule base 450 defines a validity window for some or all of the mappings in the routing table 112. For example, a particular mapping cannot be updated more than a certain number of times within a particular time frame (e.g., more than once per hour) and cannot be updated within a certain amount of time since its last update. In other embodiments, the rule base 450 defines update thresholds for some or all of the mappings. For example, a particular mapping may be updated only after some flows from a particular host are received on the same network that is different from the one to which it is currently mapped. In other embodiments, the rule base 450 defines other types of update information. For example, some hybrid communication networks 130 may be defined to have a hierarchy (e.g., a first-order communication network of communication networks 132, where all other communication networks 132 are second-order communication networks, each of the communication networks 132 being in a certain priority order, etc.). In such a case, a particular rule may take effect when a mapping is changed from a first-order network to a second-order network, from a second-order network to a first-order network, etc.For example, rule base 450 may be designed so that it is easier to update mappings from a first-order network to a second-order network (e.g., to tend to offload traffic from a first-order network) rather than mappings from a second-order network to a first-order network.
[0029] As shown, in addition to using the received forwarded link traffic 402 to update the mapping, the forwarded link traffic 402 may be forwarded to the appropriate destination CPE in the local user network 105. Although shown as being forwarded from the network-based updater 410, the forwarded link traffic 402 may be forwarded in any suitable manner, such as directly from the hybrid network interface 125. The CPEs of the local user network 105 may also generate return link traffic flows 452 destined for some destination host on the hybrid communication network 130. The return link traffic flows 452 are received by the return link router 440 of the UT 110 via the local network interface 127 so that the return link router 440 may make a determination regarding over which of the communication networks 132 the return link traffic flows 452 should be routed. As described herein, embodiments may make such determinations quickly with little computational intensity by relying on mappings stored in the routing table 112. For example, the return link router 440 obtains (e.g., parses, derives, etc.) a destination identifier (e.g., a destination IP address) from the return link traffic flow 452 and identifies a routing table entry in the routing table 112 that corresponds to (e.g., matches) the obtained destination identifier. For example, the return link router 440 performs a lookup on the routing table 112. The identified mapping may indicate over which of the communication networks 132 the return link traffic 452 should be routed.
[0030] Various embodiments may include additional considerations that may affect the routing decision. In some such embodiments, the return link router 440 is coupled with or includes a validator 435 (e.g., or there is a separate validator 435 and rule base 450 for the return link router 440). As mentioned above, in some embodiments, the rule base 450 defines a validity window for some or all of the mappings in the routing table 112. In an exemplary return link routing context, a particular mapping may be valid for a predetermined time from about the time it was last updated (after which it may revert to a previous (e.g., default) mapping); alternatively, a particular mapping is only valid at certain times of the day when some network currently has available capacity, etc. In such cases, the return link router 440 may make a routing decision based on the rules in the rule base 450 even if the rules conflict with one or more mappings in the routing table 112.
[0031] In other such embodiments, the return link router 440 is coupled with or includes a DNS lookup module 437 (e.g., or there is a separate DNS lookup module 437 in the return link router 440). As explained above, the association between the host name and the resolved host IP address may be stored for other uses. For example, the return link router 440 may use the stored association to quickly resolve the host name to a destination IP address to assist in routing return link traffic. In other embodiments, the DNS lookup module 437 may be used to perform a reverse DNS lookup to obtain the host name from the IP address. For example, the mapping may include a specific mapping (e.g., or rules may be included in the rule base 450) for routing traffic associated with some hosts through some communication networks 132 even if no other corresponding routing table entry exists in the routing table 112 (e.g., if the return link traffic indicates a different destination IP address of the content host than the one mapped in the routing table 112). In such cases, even if the indicated destination IP address is not mapped, it may be desirable to perform a reverse DNS lookup to determine, for example, whether a corresponding host is already mapped in routing table 112.
[0032] In some of these and other embodiments, the DNS lookup and / or reverse DNS lookup of DNS lookup module 437 may take too much time to perform as part of a real-time return link routing decision. Thus, some embodiments of DNS lookup module 437 may perform the DNS lookup and / or reverse DNS lookup as a background task (e.g., in parallel with return link router 440 making the routing decision). For example, when return link traffic flow 452 is received by return link router 440, return link router 440 may begin making real-time routing decisions according to available mappings in routing table 112 and / or according to rule base 450 (e.g., default mappings, etc.). Meanwhile, return link router 440 may also trigger DNS lookup module 437 to perform DNS lookup and / or reverse DNS lookup, which may result in updates to or additions to one or more mappings. The updated or new mappings may then be used by return link router 440 to route subsequent packets of the same return link traffic flow 452 and / or subsequent flows.
[0033] Upon making the routing decision, the return link router 440 may output the return link traffic flow 452 and the routing decision as a routing state output 442. The hybrid network interface 125 may use the routing state output 442 to route the return link traffic flow 452 over the hybrid communication network 130. For example, the hybrid network interface 125 may route the return link traffic flow 452 over a first component network (e.g., a satellite network) of the component network 132 as Layer 3 routing by using the router 470, route the return link traffic flow 452 over a Layer 2 tunnel through a second communication network of the communication network 132 by using a forwarder 475, or the like. In some embodiments, additional functions are performed by the hybrid network interface 125 as part of routing the return link traffic flow 452 over the hybrid communication network 130. For example, the NAT 460 may translate the private IP address of the source CPE to the public IP address of the UT 110. Additionally, some embodiments may packetize the data, modulate the data, and / or otherwise prepare the return link traffic flow 452 for communication over the selected communications network 132 .
[0034] FIG. 5 illustrates a flow diagram of an exemplary method 500 of return link routing by a user terminal in a hybrid network environment, according to various embodiments. An embodiment of the method 500 may be performed using the systems described with reference to FIGS. 1-4 or any other suitable system. An embodiment of the method 500 begins at step 504 by receiving return link data at a user terminal routing system from a customer premises equipment (CPE), the return link data indicating an associated destination node of the return link data. As described herein, a user terminal routing system (UTRS) is communicatively coupled to a plurality of networks and has a routing table that is populated according to forward link communications received by the user terminal routing system from at least one of the networks. For example, one of the networks is a satellite network, and the routing table is populated according to forward link communications received by the UTRS from a provider-side core node (e.g., or gateway) of the satellite network. In various embodiments, the core node is communicatively coupled to one, more than one, or all of the networks of the hybrid network. The routing table may be a look-up table or other suitable data store that stores a plurality of mappings, each mapping between a routing table entry and one of the networks, each routing table entry identifying at least one forwarded link content source (FLCS) identifier.
[0035] At stage 508, embodiments identify one of the mappings in the routing table as having a routing table entry corresponding to a destination node associated with the return link data. For example, the routing table entry may include any suitable FLCS identifier, such as a return link destination IP address. In some embodiments, each routing table entry includes a 5-tuple identifying a source IP address, a source port, a destination IP address, a destination port, and a data communication protocol. The return link data may include a return link routing tuple indicating an associated destination node of the return link data. The return link routing tuple may further indicate a destination Internet Protocol (IP) address and a destination port.
[0036] In step 512, embodiments route the return link data over one of the networks according to the identified one of the mappings. In some embodiments, the routing in step 512 follows the stored mapping directly. For example, the forward link data is received from a particular content host over a particular one of the networks, and the return link data sent to the content host is sent over the same particular one of the networks. In other embodiments, the routing may consider other factors. As shown, some embodiments in step 516 determine whether the mapping identified in step 508 remains valid. For example, the routing follows the mapping in step 512 directly only if the mapping is determined in step 516 to be valid, and the routing may be adjusted if the mapping is determined in step 516 to be invalid. For example, the routing in step 512 may be adjusted in step 520 according to a set of routing criteria and a routing rule base that defines another network of the plurality of networks, so that the return link data is routed either over one of the networks mapped to the destination node of the return link data in the routing table or over another network according to whether the set of routing criteria is met.
[0037] Similar types of validation, enforcement, adjustment, etc. of routing may be implemented in various ways according to various embodiments. In some embodiments, forwarding link data indicating a source node of the forwarding link data is received at the user terminal via one of the multiple networks. A corresponding one of the mappings in the routing table may be identified as corresponding to the indicated source node, and a determination may be made as to whether the corresponding mapping is currently enforced according to a validity window associated with the identified one of the mappings. In such embodiments, the corresponding mapping may be updated according to the received forwarding link data only if it is not currently enforced. In other such embodiments, forwarding link data packets may be received at the user terminal via at least one of the multiple networks, each forwarding link data packet indicating a respective source node of the forwarding link packet. The method 500 may wait to detect receipt of at least a threshold number of forwarding link data packets all having the same respective source node and received on a first network of the multiple networks; and only after such detection, in response to the detection, may update the routing table with the updated mapping. In such embodiments, the update includes mapping the first network to a routing table entry corresponding to the same respective source node. In yet other such embodiments, method 500 may determine whether the identified one of the mappings is currently valid according to a validity window associated with the identified one of the mappings, and routing in stage 512 may be performed according to the identified one of the mappings only if the identified one of the mappings is currently valid.In yet another such embodiment, method 500 may receive forwarded link data at a user terminal via a first network of the multiple networks indicating a source node of the forwarded link data; a corresponding one of the routing table mappings may be identified as corresponding to the indicated source node; a determination may be made that the corresponding mapping currently directs routing on a second network of the multiple networks; and the corresponding mapping may be updated to direct routing on the first network only if the second network is a first network of the multiple networks, and the first network is not the first network of the multiple networks.
[0038] Some embodiments of method 500 begin with populating and / or updating some or all of the routing table mappings prior to receiving at step 504. For example, at step 501, an embodiment may receive forwarded link data at a user terminal via a first one of the networks prior to receiving the return link data at step 504. The forwarded link data may indicate a source node of the forwarded link data, and the routing table may be updated with an updated mapping in accordance with the received forwarded link data. In such embodiments, identifying at step 508 may include determining that a destination node of the return link data corresponds to a source node of the forwarded link data, such that the identified one of the mappings is the updated mapping; routing at step 512 may include routing the return link data on the first network in accordance with the updated mapping. In some such embodiments, updating at step 501 includes mapping the first network to a routing table entry of the source node, and routing at step 512 includes routing the return link data on the first network in accordance with the updated mapping. Other embodiments of method 500 may begin at step 502 by receiving a control message at a user terminal over one of the networks (e.g., the control message indicating at least one routing table update) and updating a routing table according to the at least one routing table update. Still other embodiments of method 500 begin at step 503 by pre-populating some or all of the routing table with, for example, a default mapping.For example, each of at least a portion of the pre-loaded mappings may be pre-loaded by: selecting one of a plurality of pre-stored associations between the corresponding content host and a corresponding one of the plurality of networks; performing a Domain Name Server (DNS) lookup to determine a destination IP address associated with the corresponding one of the plurality of networks; generating the pre-loaded mapping to associate a routing table entry including the destination IP address with a corresponding one of the plurality of networks. Similarly, in some embodiments, at least one of the routing table entries may indicate a return link destination IP address, and at least one of the mappings may be generated by: determining a content host corresponding to the return link destination IP address indicated by the at least one routing table entry; identifying a pre-stored association between the content host and a routing network of the plurality of networks; generating at least one mapping to associate the routing table entry with the identified routing network. For example, the content host may be determined by performing a reverse DNS lookup (e.g., by the UTRS as a background task concurrently with the identifying in step 508 and / or the routing in step 512).
[0039] The methods disclosed herein include one or more acts for achieving the method. The methods and / or acts may be interchanged with one another without departing from the scope of the claims. In other words, unless a specific order of acts is specified, the order and / or use of specific acts may be modified without departing from the scope of the claims.
[0040] A computer program product may perform some of the operations presented herein. For example, such a computer program product may be a computer-readable tangible medium having instructions tangibly stored (and / or encoded) thereon, the instructions being executable by one or more processors to perform the operations described herein. The computer program product may include packaging materials. The software or instructions may also be transmitted over a transmission medium. For example, the software may be transmitted from a website, server, or other remote source using a transmission medium such as coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), or wireless technology such as infrared, radio, or microwave.
[0041] Additionally, modules and / or other suitable means for performing the methods and techniques described herein may be downloaded and / or otherwise obtained by a suitable terminal and / or coupled to a server or the like to facilitate the transfer of means for performing the methods described herein. Alternatively, the various methods described herein may be provided via storage means (e.g., RAM, ROM, physical storage media such as CDs or floppy disks, etc.) such that a user terminal and / or base station may obtain the various methods upon coupling or providing the storage means to the device. Additionally, any other suitable technique for providing the methods and techniques described herein to the device may be utilized. Feature-performing functionality may also be physically located at various locations, including being distributed such that portions of the functionality are performed at various physical locations.
[0042] In describing the present invention, the following terms will be used: the singular forms of the articles and indefinite articles include plural references unless the context dictates otherwise. Thus, for example, a reference to an item includes a reference to one or more items. A "plural noun" refers to one or more than one, and typically applies to the selection of some or all of a quantity. The term "plurality" refers to two or more items. The term "about" means that "quantities, dimensions, sizes, formulations, parameters, shapes and other characteristics need not be exact, but may be approximated and / or may be larger or smaller as desired, reflecting acceptable tolerances, conversion factors, rounding, measurement errors, and the like, and other factors known to those of ordinary skill in the art." The term "approximately" means that "the recited feature, parameter, or value need not be exactly achieved, but deviations or variations, including, for example, tolerances, measurement errors, measurement accuracy limits, and other factors known to those of ordinary skill in the art, may occur in an amount that does not eliminate the effect that the feature was intended to provide." Numerical data may be expressed or presented herein in a range format. It should be understood that such range formats are used merely for convenience and brevity, and thus should be interpreted flexibly to include not only the numerical values expressly recited as the limits of the range, but also to include all of the individual numerical values or subranges encompassed within this range, as if each numerical value and subrange were expressly recited. By way of illustration, a numerical range of "about 1 to 5" should be interpreted not only to include the explicitly recited values of about 1 to about 5, but also to include each individual value and subrange within the stated range. Thus, included within this numerical range are individual values such as 2, 3, and 4, as well as subranges such as 1 to 3, 2 to 4, 3 to 5, etc. This same principle applies to ranges reciting only a single numerical value (e.g., "more than about 1"), and thus should apply regardless of the breadth of the range or characteristic described. Multiple items may be presented in a common list for convenience. However, these lists should be interpreted as if each member of the list were individually identified as each separate and unique member.Thus, any individual member of such a list should not be construed as a de facto equivalent of any other member of the same list based solely on their presentation within a common group, unless otherwise indicated. Furthermore, when the terms "and" and "or" are used in conjunction with a list of items, they are to be interpreted broadly to mean that any one or more of the listed items may be used alone or in combination with other listed items. The term "alternatively" refers to a selection of one of two or more alternatives and is not intended to limit this selection to only the listed alternatives at a time or to only one of the listed alternatives, unless the context clearly indicates otherwise. As used herein, the term "coupled" does not require that the components are directly connected to each other. Instead, the term is also intended to include configurations having an indirect connection in which one or more other components may be included between the coupled components. For example, such other components may include amplifiers, attenuators, isolators, directional couplers, redundant switches, etc. Also, as used herein, including the claims, the word "or" used in a list of items preceded by "at least one" indicates a disjunctive list, e.g., the list "at least one of A, B, or C" means A or B or C or AB or AC or BC or ABC (i.e., A and B and C). Furthermore, the term "exemplary" does not imply that the described example is preferred or better than other examples. As used herein, a "set" of elements is intended to mean "one or more" of those elements, unless the set is explicitly required to have more than one or is explicitly allowed to be an empty set.
[0043] Various modifications, substitutions and alterations to the techniques described herein may be made without departing from the teachings of the technique as defined by the appended claims. Moreover, the scope of the disclosure and claims are not limited to the particular aspects of the processes, machines, manufacture, compositions of matter, means, methods and acts described above. Any existing or later developed processes, machines, manufacture, compositions of matter, means, methods or acts that perform substantially the same function or achieve substantially the same result as the corresponding aspects described herein may be utilized. Accordingly, the appended claims include within their scope such processes, machines, manufacture, compositions of matter, means, methods or acts.
Claims
1. 1. A method for routing a signal in a hybrid network, the method comprising: communicatively coupling a user terminal routing system to a plurality of networks having different network characteristics; maintaining a routing table populated with a plurality of mappings, each mapping associating an associated destination node of return link data with one of the plurality of networks to which the user terminal routing system is communicatively coupled, the plurality of mappings defining routing of return link data to one of the plurality of networks based on the associated destination node of the return link data, at least one of the plurality of mappings indicating a return link destination Internet Protocol (IP) address; receiving a control message including at least one routing table update; updating the routing table with updated mappings based on updates to the at least one routing table; determining, by the user terminal routing system, a content host corresponding to a destination IP address for the return link; identifying a pre-stored association between the content host and a routing network of the plurality of networks; generating at least one mapping to associate a destination IP of the return link with the identified routing network; and generating at least one of the plurality of mappings by:
2. 2. The method of claim 1, wherein said control message is received at said user terminal routing system from one of said plurality of networks.
3. The method of claim 1 further comprising: receiving the return link data at the user terminal routing system from customer premises equipment, the return link data indicating the associated destination node of the return link data; identifying one of the mappings in the routing table as corresponding to the destination node associated with the return link data; and routing the return link data over the one of the plurality of networks in accordance with the identified one of the mappings.
4. 4. The method of claim 3, wherein routing the return link data in accordance with the identified one of the mappings includes routing in accordance with a set of routing criteria and a routing rule base defining another network of the plurality of networks, and wherein the routing of the return link data is such that the return link data is either on the one network or on the other network of the plurality of networks mapped in the routing table to the destination node of the return link data in accordance with whether the set of routing criteria is satisfied.
5. 4. The method of claim 3, determining, by the user terminal routing system, whether the identified one of the mappings is currently valid according to a validity window associated with the identified one of the mappings; routing the return link data according to the identified one of the mappings only if the identified one of the mappings is currently valid.
6. 10. The method of claim 1 , The method, wherein each mapping includes a routing table entry that includes a source Internet Protocol (IP) address, a source port, a destination IP address, a destination port, and a 5-tuple that identifies a data communications protocol.
7. 10. The method of claim 1 , The method, wherein the return link data includes a return link routing tuple indicating the associated destination node of the return link data.
8. 8. The method of claim 7, The method, wherein the return link routing tuple further indicates a destination Internet Protocol (IP) address and a destination port of the return link.
9. 10. The method of claim 1 , one of the plurality of networks is a satellite network; 4. The method of claim 3, wherein said routing table is populated according to forward link communications received by said user terminal routing system from a provider side core node of said satellite network.
10. 10. The method of claim 9, The method, wherein the provider core node is communicatively coupled to multiple of the multiple networks.
11. 10. The method of claim 1 , The method, wherein said determining step includes the step of performing a reverse Domain Name Server (DNS) lookup.
12. 12. The method of claim 11, The method of claim 1, wherein said reverse DNS lookup is performed by said user terminal routing system as a background task concurrently with said identifying and said routing.
13. 10. The method of claim 1 , The method of claim 1, wherein said routing table is a preloaded table having a plurality of preloaded mappings prior to said receiving step.
14. 14. The method of claim 13, Each of at least a portion of the preloaded mappings comprises: selecting one of a plurality of pre-stored associations between a corresponding content host and a corresponding one of the plurality of networks; performing a Domain Name Server (DNS) lookup to determine a destination Internet Protocol (IP) address associated with the corresponding content host; generating said preloaded mapping to associate said corresponding ones of said plurality of networks with a routing table entry including said destination IP address.
15. In a user terminal routing system, a local network interface operable to couple to a local user network; a hybrid network interface including a plurality of network interfaces each operable to couple with a respective one of a plurality of communication networks of the hybrid network having different network characteristics; a routing table populated with a plurality of mappings each relating a destination node associated with the return link data to one of a plurality of communication networks, at least one of the plurality of mappings indicating a destination Internet Protocol (IP) address of the return link; 1. A mapping generator comprising: determining, by the user terminal routing system, a content host corresponding to a destination IP address for the return link; identifying a pre-stored association between the content host and a routing network of the plurality of communication networks; generating at least one mapping to associate a destination IP of the return link with the identified routing network; a mapping generator operative to generate at least one of the plurality of mappings by a routing table updater coupled between the hybrid network interface and the routing table, receiving a control message including at least one routing table update; a routing table updater for updating the routing table with an updated mapping based on the at least one routing table update; A user terminal routing system comprising:
16. 16. The user terminal routing system of claim 15, The control message is received at the user terminal routing system from one of the plurality of communication networks.
17. 16. The user terminal routing system of claim 15, further comprising: a routing state machine coupled between the local network interface and the hybrid network interface, the routing state machine including a routing state output calculated according to the routing table in response to receiving return link data via the local network interface; the received return link data indicating a destination node corresponding to an identified one of the mappings; the routing state output is adapted to direct routing of the received return link data on a selected network of the plurality of communication networks via the hybrid network interface in accordance with the identified one of the mappings. A user terminal routing system comprising a routing state machine.
18. 18. The user terminal routing system of claim 17, A user terminal routing system in which each destination node includes an internet protocol address.
19. 18. The user terminal routing system of claim 17, 11. A user terminal routing system comprising: a routing state machine including a stored routing rule base defining a set of routing criteria and another of the plurality of communication networks; and wherein, depending on whether the set of routing criteria is satisfied, the routing state output directs routing of the return link data either on the one of the plurality of communication networks mapped in the routing table to the destination node of the return link data or on the other of the plurality of communication networks.
20. 20. The user terminal routing system of claim 19, the stored rule base defines a validity window for each of at least some of the mappings; said routing state output directs routing of said return link data further in accordance with said respective validity windows.
21. 18. The user terminal routing system of claim 17, 4. A user terminal routing system, comprising: a return link data set including a return link routing tuple indicating a destination node associated with the return link data set.
22. 16. The user terminal routing system of claim 15, 13. A user terminal routing system, comprising: a routing table including a plurality of preloaded default mappings;
23. 16. The user terminal routing system of claim 15, A user terminal routing system, wherein said local user network includes at least one customer premises equipment (CPE) device.
24. 16. The user terminal routing system of claim 15, Each mapping includes a routing table entry that includes a 5-tuple that identifies a source Internet Protocol (IP) address, a source port, a destination IP address, a destination port, and a data communications protocol.
25. 16. The user terminal routing system of claim 15, The user terminal routing system according to claim 1, wherein the return link data includes a return link routing tuple further indicating a destination Internet Protocol (IP) address and a destination port of the return link.
26. 16. The user terminal routing system of claim 15, one of the plurality of communication networks is a satellite network; 4. A user terminal routing system, comprising: a satellite network having a provider-side core node and a routing table configured to receive data from said satellite network ...
27. 27. The user terminal routing system of claim 26, wherein said provider side core node is communicatively coupled to a plurality of said plurality of communication networks.
Citation Information
Patent Citations
Node device
JP2007068225A
Centralized ground-based route determination and traffic engineering for software defined satellite communications networks
US20160037434A1
Methods and apparatus for internet-scale routing using small-scale border routers
US8611349B1
Mobile communication system and ue
WO2014112638A1
