NZ754109B2 - Return-link routing in a hybrid network - Google Patents
Return-link routing in a hybrid network Download PDFInfo
- Publication number
- NZ754109B2 NZ754109B2 NZ754109A NZ75410917A NZ754109B2 NZ 754109 B2 NZ754109 B2 NZ 754109B2 NZ 754109 A NZ754109 A NZ 754109A NZ 75410917 A NZ75410917 A NZ 75410917A NZ 754109 B2 NZ754109 B2 NZ 754109B2
- Authority
- NZ
- New Zealand
- Prior art keywords
- link data
- routing
- networks
- network
- mappings
- Prior art date
Links
- 238000013507 mapping Methods 0.000 claims abstract 47
- 238000000034 method Methods 0.000 claims abstract 21
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/02—Topology update or discovery
- H04L45/021—Ensuring consistency of routing table updates, e.g. by using epoch numbers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/24—Multipath
- H04L45/245—Link aggregation, e.g. trunking
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/54—Organization of routing tables
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/74—Address processing for routing
- H04L45/745—Address table lookup; Address filtering
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/80—Ingress point selection by the source endpoint, e.g. selection of ISP or POP
- H04L45/85—Selection among different networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/2514—Translation of Internet protocol [IP] addresses between local and global IP addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/45—Network directories; Name-to-address mapping
- H04L61/4505—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols
- H04L61/4511—Network directories; Name-to-address mapping using standardised directories; using standardised directory access protocols using domain name system [DNS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D30/00—Reducing energy consumption in communication networks
- Y02D30/50—Reducing energy consumption in communication networks in wire-line communication networks, e.g. low power modes or reduced link rate
Abstract
Embodiments provide techniques for providing return-link routing in a hybrid communications network that includes a number of different networks having different characteristics. User terminal routing systems (UTRSs) provide interfaces between local user networks and the multiple communications networks of the hybrid network. Each UTRS can include a routing table having stored mappings that are populated according to forward-link communications (implicitly or explicitly), each associating a respective one of a plurality of routing table entries with one of the communications networks. When a UTRS receives return-link data from its respective local user network, the received data indicates a destination node. The UTRS can determine which of the stored mappings corresponds to the destination node and can route the received return-link data over a selected one of the communications networks in accordance with the identified one of the mappings.
Claims (35)
1. A method for routing signals in a hybrid k, the method comprising: receiving return link data at a user terminal routing system from er premises equipment, the return link data indicating a destination node for the return link data, the user terminal routing system communicatively coupled with a plurality of networks and sing a routing table populated according to forward link data packets received by the user terminal g system from at least one of the plurality of networks, wherein each forward link data packet indicates a respective source node for the forward link data packet, such that the routing table has, stored thereon, a plurality of mappings, each between a respective one of a plurality of routing table entries and one of the plurality of networks, each routing table entry corresponding to a source node indicated by a forward link data packet; fying one of the mappings in the routing table as having the routing table entry that corresponds to the ation node indicated by the return link data; and routing the return link data over one of the plurality of networks ing to the identified one of the mappings.
2. The method of claim 1, further comprising: receiving forward link data at the user terminal via a first of the plurality of networks prior to receiving the return link data, the forward link data indicating a source node for the forward link data; updating the routing table with an updated mapping ing to the received forward link data, wherein the fying comprises determining that the destination node for the return link data corresponds to the source node for the forward link data, such that the fied one of the mappings is the updated mapping, and the routing comprises routing the return link data over the first network according to the updated mapping.
3. The method of claim 2, wherein: the updating comprises mapping the first network to a routing table entry for the source node; the routing comprises routing the return link data over the first network according to the updated mapping.
4. The method of claim 1, further comprising: receiving a control message at the user al via one of the plurality of networks, the control message ting at least one routing table update; and updating the routing table according to the at least one routing table update.
5. The method of claim 1, wherein each routing table entry comprises a five-tuple that identifies a source Internet protocol (IP) address, a source port, a destination IP address, a destination port, and a data communication protocol.
6. The method of claim 1, wherein: the return link data comprises a return link routing tuple that tes the destination node for the return link data.
7. The method of claim 6, wherein the return link routing tuple further indicates a destination Internet protocol (IP) address, and a destination port.
8. The method of claim 1, wherein: one of the ity of networks is a satellite network; and the g table is ted according to forward link data packets received by the user terminal routing system from a provider-side core node of the satellite network.
9. The method of claim 8, wherein the core node is communicatively coupled with multiple of the plurality of networks.
10. The method of claim 1, further comprising: receiving a plurality of forward link data packets at the user terminal via at least one of the plurality of networks, each forward link data packet indicating a respective source node for the forward link packet; detecting receipt of at least a threshold number of the forward link data packets that all have a same respective source node and are all received over a first network of the plurality of networks; and updating the routing table with an updated mapping in response to the detecting, the updating comprising mapping the first network to a routing table entry corresponding to the same respective source node.
11. The method of claim 1, wherein: routing the return link data according to the identified one of the mappings comprises g according to a routing rule-base that s a set of routing criteria and an alternate k of the plurality of ks, such that, in ance with whether the set of g criteria is met, the routing of the return link data is either over the one of the plurality of networks mapped in the routing table to the destination node of the return link data or over the alternate k.
12. The method of claim 1, further sing: determining, by the user terminal routing system, whether the identified one of the mappings is presently valid according to a validity window associated with the identified one of the mappings; and routing the return link data according to the identified one of the mappings only when the identified one of the mappings is presently valid.
13. The method of claim 1, further comprising: receiving d link data at the user terminal via a first network of the ity of networks, the forward link data indicating a source node for the forward-link data; identifying a corresponding one of the mappings of the routing table as corresponding to the indicated source node; determining, by the user terminal routing system, that the corresponding mapping presently directs routing over a second network of the plurality of ks; updating the corresponding mapping to direct routing over the first k only when the second network is a primary network of the plurality of networks, and the first network is not the primary k of the plurality of networks.
14. The method of claim 1, further comprising: receiving forward link data at the user terminal via one of the plurality of ks, the forward link data indicating a source node for the forward link data; identifying a corresponding one of the mappings of the routing table as corresponding to the indicated source node; determining, by the user terminal routing system, r the corresponding mapping is presently enforced according to a validity window associated with the identified one of the mappings; updating the corresponding mapping according to the received forward link data only when the ponding mapping is not presently enforced.
15. The method of claim 1, wherein at least one of the routing table entries indicates a return link destination Internet-protocol (IP) address, and r comprising: generating at least one of the mappings by: determining, by the user terminal routing system, a content host corresponding to the return link ation IP address indicated by the at least one routing table entry; identifying a pre-stored association n the content host and a g network of the plurality of networks; and generating the at least one mapping to associate the routing table entry with the identified routing k.
16. The method of claim 15, wherein the determining comprises performing a reverse domain name server (DNS) lookup.
17. The method of claim 16, wherein the reverse DNS lookup is performed by the user terminal routing system as a background task concurrently with the fying and the routing.
18. The method of claim 1, wherein the routing table is preloaded with a plurality of preloaded mappings prior to the receiving.
19. The method of claim 18, wherein each of at least a portion of the preloaded mappings is preloaded by: selecting one of a plurality of pre-stored associations between a corresponding content host and a corresponding one of the ity of networks; ming a domain name server (DNS) lookup to determine a destination Internet protocol (IP) address associated with the corresponding content host; and generating the preloaded mapping to associate the corresponding one of the plurality of networks with a routing table entry sing the destination IP address.
20. A user terminal routing system comprising: a local network interface operable to couple with a local user network; a hybrid network ace comprising a plurality of network interfaces, each operable to couple with a respective one of a plurality of communications networks of a hybrid network; a routing table having stored thereon a plurality of mappings populated according to forward link data s received via at least one of the plurality of networks, wherein each forward link data packet indicates a tive source node for the forward link data packet, each mapping associating a respective one of a plurality of routing table s with one of the plurality of communications networks, each routing table entry corresponding to a source node indicated by a forward link data packet; and a routing state machine coupled between the local network interface and the hybrid network ace, the routing state machine sing a routing state output computed according to the routing table in response to receiving return link data via the local network ace, such that: the received return link data indicates a destination node corresponding to the source node of an identified one of the mappings, and the routing state output directs routing of the received return link data over a selected one of the plurality of communications networks via the hybrid network interface in accordance with the identified one of the mappings.
21. The user terminal routing system of claim 20, further comprising: a routing table updater coupled n the hybrid network interface and the routing table, and having an update output generated according to the d link data packets received via at least one of the ity of networks, at least some of the mappings updated in se to the update output.
22. The user terminal routing system of claim 21, wherein: the update output is generable in response to receiving forward link data flows via the hybrid network interface, each forward link data flow indicating a tive source node and received via a tive one of the communications networks, such that each of the at least some of the mappings is updated according to a respective one of the received forward link data flows to map the respective source node with the respective one of the communications networks.
23. The user terminal routing system of claim 21, wherein: the update output is generable in se to receiving control messages via one of the plurality of ks, the control messages indicating respective routing table updates, such that each of at least some of the mappings is updated according a respective g table update.
24. The user terminal routing system of claim 20, wherein each routing table entry comprises an Internet protocol address.
25. The user terminal routing system of claim 20, wherein: the state machine comprises a stored routing rule-base that defines a set of routing criteria and an ate network of the plurality of networks, such that, in accordance with whether the set of g criteria is met, the routing state output direct routing of the return link data either over the one of the plurality of networks mapped in the routing table to the destination node of the return link data or over the alternate network.
26. The user terminal routing system of claim 25, wherein: the stored rule-base defines respective validity windows for at least some of the mappings; the routing state output directs g of the return link data r according to the respective validity windows.
27. The user terminal routing system of claim 20, n the g table comprises a plurality of preloaded default mappings.
28. The user terminal routing system of claim 20, wherein the local user network comprises at least one customer premises equipment (CPE) device.
29. A hybrid communications network comprising: a plurality of communications networks; a plurality of user terminal routing systems, each coupled between the plurality of communications ks and a respective local user network, each comprising a routing table having stored thereon a plurality of mappings populated according to forward link data packets received via at least one of the plurality of networks, wherein each forward link data packet indicates a respective source node for the forward link data packet, each mapping associating a respective one of a plurality of routing table s with one of the plurality of communications networks, each routing table entry corresponding to a source node indicated by a forward link data , wherein each user terminal routing system is operable to receive return-link data from its respective local user network, the received return link data indicating a destination node corresponding to the source node of an identified one of the gs, and to route the received return link data over a ed one of the ity of communications networks via the hybrid network interface in accordance with the identified one of the mappings.
30. The hybrid communications network of claim 29, wherein the plurality of communications networks comprises a satellite communications network, and a terrestrial communications network.
31. The hybrid communications network of claim 29, r sing: a provider-sider core node remote from the user terminal routing systems and coupled with the plurality of ications networks, wherein the routing table is populated according to forward link data packets received from the provider-side core node.
32. The hybrid communications network of claim 29, wherein: the routing table is updated at least in part according to forward link data flows received via the hybrid network interface, each forward link data flow indicating a respective source node and received via a respective one of the communications networks, such that each of the at least some of the mappings is updated according to a respective one of the received forward link data flows to map the respective source node with the tive one of the communications networks.
33. The hybrid communications network of claim 29, wherein: the routing table is updated at least in part according to control messages received via one of the plurality of networks, the control messages indicating respective routing table updates, such that each of at least some of the mappings is d according a respective routing table update.
34. The hybrid communications k of claim 29, wherein: each user terminal routing system is operable to route the ed return link data further in accordance with a stored routing rule-base that defines a set of routing criteria and an alternate network of the plurality of networks, such that, in accordance with whether the set of routing criteria is met, the routing of the return link data is either over the one of the plurality of networks mapped in the routing table to the destination node of the return link data or over the ate k.
35. The hybrid communications network of claim 29, each g table comprises a plurality of preloaded default mappings. 1/ + {{LQBCOU €035 a 2002 QEmLQUFOHL wE?EM 533m a QEmLQUFOE » a a . o . o .. a a ; u l a .. a n a . o . o €035 mmm? €035 DNm H €035 :Nm? Z Z Z ESE mQOUBUESSEoU SEOU mQEEUESEEoU mEEEHmF mandom 23022 a Hmmb 9:035 Euodsl Z m3 \y yy {meEoU vie a 2002 QEmLBUFOHL wardem QEmLQUFOE REESE wE?EM 23022 a EmD HamD €035 EuodkZ mo? I
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| NZ794697A NZ794697B2 (en) | 2017-12-11 | Return-link routing in a hybrid network |
Applications Claiming Priority (3)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| US201662433689P | 2016-12-13 | 2016-12-13 | |
| US15/592,097 US10511530B2 (en) | 2016-12-13 | 2017-05-10 | Return-link routing in a hybrid network |
| PCT/US2017/065612 WO2018111772A1 (en) | 2016-12-13 | 2017-12-11 | Routing in a hybrid network |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| NZ754109A NZ754109A (en) | 2024-07-05 |
| NZ754109B2 true NZ754109B2 (en) | 2024-10-08 |
Family
ID=
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2022211883B2 (en) | Return-link routing in a hybrid network | |
| US6597703B1 (en) | System, device, and method for reducing multicast forwarding states in a multicast communication system | |
| US8504722B2 (en) | Enhancing DS-lite with private IPV4 reachability | |
| US9838315B2 (en) | Stretched subnet routing | |
| US9825861B2 (en) | Packet forwarding method, apparatus, and system | |
| CN107547346B (en) | Message transmission method and device | |
| CN101483657A (en) | Implementation method and system for same side private network device access by private user | |
| US8819271B2 (en) | System and method to access and use layer 2 and layer 3 information used in communications | |
| US10484281B1 (en) | Router operating methods and apparatus using virtual VPN instances for hosts of remote extranet VPNs | |
| NZ754109B2 (en) | Return-link routing in a hybrid network | |
| NZ794697B2 (en) | Return-link routing in a hybrid network | |
| US8225389B2 (en) | Method and system to provide physical port security in a digital communication system | |
| CN109194775A (en) | A kind of improved adaptively shared network based on NAT technology |