ABSTRACT
Abstract
A method for redundant communication at a network gateway includes (1) exchanging data packets with a network application via a first access communication interface, (2) exchanging data packets with customer premises equipment (CPE) via a local communication interface, and (3) in response to occurrence of a first event, exchanging at least some data packets with the network application via a second access communication interface that is different from the first access communication interface.
Description
RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 17/017,472, filed on Sep. 10, 2020, which claims benefit of priority to U.S. Provisional Patent Application Ser. No. 62/898,087, filed on Sep. 10, 2019. Each of the aforementioned patent applications is incorporated herein by reference.
BACKGROUND
Network gateways are used to interface customer premises equipment (CPE) with an access communication network, such as a cable access communication network, a digital subscriber line (DSL) access communication network, an optical access communication network, or a wireless access communication network. As such, a network gateway is key element of a premises communication network. For example, a premises communication network will be inoperable if its network gateway fails.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of a communication system including a network gateway with redundant communication capability, according to an embodiment.
FIG. 2 is a dataflow diagram illustrating one example of operation of the FIG. 1 system.
FIG. 3 is a dataflow diagram illustrating another example of operation of the FIG. 1 system.
FIG. 4 is a flow chart of a method for redundant communication at a network gateway, according to an embodiment.
FIG. 5 is a schematic diagram of one embodiment of the network gateway of the FIG. 1 communication system.
FIG. 6 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 7 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 8 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by an optical communication link and a wireless communication link.
FIG. 9 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 10 is a schematic diagram of yet another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 11 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by an optical communication link and a wireless communication link.
FIG. 12 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by wireless communication links.
FIG. 13 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by wireline communication links.
FIG. 14 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by wireline communication links.
FIG. 15 is a schematic diagram of an alternate embodiment of the network gateway of the FIG. 1 communication system.
FIG. 16 is a schematic diagram of a communication system including an embodiment of the FIG. 15 network gateway, according to an embodiment.
FIG. 17 is a schematic diagram of a communication system including an alternate network gateway, according to an embodiment.
FIG. 18 is a schematic diagram of an alternate embodiment of the FIG. 12 communication system.
DETAILED DESCRIPTION OF THE EMBODIMENTS
There is significant interest in achieving high reliability in premises communication networks, such as communication networks in homes and businesses. For example, a home communication network's user may be significantly inconvenienced if the communication network fails. As another example, a business may be unable to operate and thereby loose significant revenue if the business's communication network fails. Furthermore, property damage or even personal injury may result from failure of a communication network which performs an essential function.
Accordingly, many network gateways are now available with a backup power source, such as a backup battery, to power the network gateway in case a primary power source fails. Such inclusion of a backup power source in a network gateway helps achieve reliability by reducing likelihood of downtime due to a power failure. However, conventional network gateways are susceptible to downtime due to failure of an access communication network supporting the network gateway. For example, a network gateway supported by a wireline access network will experience downtime if a cable of the wireline access network is severed. As another example, a network gateway supported by a wireless access network will experience downtime if a wireless base station of the wireless access network suffers storm damage.
Disclosed herein are network gateways with redundant communication capability which at least partially overcome the above discussed drawbacks of conventional network gateways. These new network gateways include a plurality of access communication interfaces, which advantageously enable the network gateways to be supported by two or more different access networks, thereby achieving communication redundancy. Consequently, the new network gateways can continue to operate even if a supporting access network fails. In some embodiments, there is essentially no downtime in event of an access network failure, while in some other embodiments, there is only a short downtime, e.g. less than one minute, in response to an access network failure.
FIG. 1 is a schematic diagram of a communication system 100 including a network gateway 102 , where network gateway 102 is one embodiment of the new network gateways with redundant communication capability. Communication system 100 further includes a plurality of communication links 104 , termination devices 106 , a multi-path protocol (MPP) end point 108 , a traffic aggregator 110 , a network 112 , a network application 114 , and CPE 116 . In this document, specific instances of an item may be referred to by use of a numeral in parentheses (e.g. communication link 104 ( 1 )) while numerals without parentheses refer to any such item (e.g. communication links 104 ). Network gateway 102 includes a plurality of access communication interfaces 118 , a router 120 , an MPP end point 122 , a traffic aggregator 124 , and a local communication interface 126 .
Network gateway 102 is implemented, for example, by electrical circuitry (not shown) and/or by optical elements (not shown). Network gateway 102 may include additional elements without departing from the scope hereof. Additionally, two or more elements of network gateway 102 may be combined or at least partially implemented by common hardware, software, and/or firmware. For example, in some embodiments, one or more of router 120 , MPP end point 122 , and traffic aggregator 124 are implemented by common electrical circuitry (not shown). As another example, in some embodiments, one or more of router 120 , MPP end point 122 , and traffic aggregator 124 are implemented by a processor (not shown) executing non-transitory instructions in the form of software and/or firmware that are stored in a memory subsystem (not shown).
Network 112 includes, for example, the Internet, an Intranet, and/or one or more other communication networks. Network application 114 is communicatively coupled to network 112 , and network application 114 includes one or more resources that may be used by CPE 116 . Examples of network application 114 include, but are not limited to, a content application, a communication application, a gaming application, a productivity application, etc. Network 112 communicatively couples network application 114 to traffic aggregator 110 . Traffic aggregator 110 is communicatively coupled between network 112 and MPP end point 108 . Traffic aggregator 110 is configured to aggregate, e.g. encapsulate, downlink data packets from network 112 and transmit the aggregated data packets to MPP end point 108 . Additionally, traffic aggregator 110 is configured to de-aggregate, e.g. un-encapsulate, uplink data packets received from MPP end point 108 . MPP end point 108 cooperates with MPP end point 122 to establish multi-path communication between network 112 and <figure-callout id="102" label="network gateway" filenames="US1
RELATED APPLICATIONS
This application is a continuation of U.S. patent application Ser. No. 17/017,472, filed on Sep. 10, 2020, which claims benefit of priority to U.S. Provisional Patent Application Ser. No. 62/898,087, filed on Sep. 10, 2019. Each of the aforementioned patent applications is incorporated herein by reference.
BACKGROUND
Network gateways are used to interface customer premises equipment (CPE) with an access communication network, such as a cable access communication network, a digital subscriber line (DSL) access communication network, an optical access communication network, or a wireless access communication network. As such, a network gateway is key element of a premises communication network. For example, a premises communication network will be inoperable if its network gateway fails.
BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a schematic diagram of a communication system including a network gateway with redundant communication capability, according to an embodiment.
FIG. 2 is a dataflow diagram illustrating one example of operation of the FIG. 1 system.
FIG. 3 is a dataflow diagram illustrating another example of operation of the FIG. 1 system.
FIG. 4 is a flow chart of a method for redundant communication at a network gateway, according to an embodiment.
FIG. 5 is a schematic diagram of one embodiment of the network gateway of the FIG. 1 communication system.
FIG. 6 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 7 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 8 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by an optical communication link and a wireless communication link.
FIG. 9 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 10 is a schematic diagram of yet another embodiment of the FIG. 1 communication system where communication links are embodied by a hybrid optical-electrical communication link and a wireless communication link.
FIG. 11 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by an optical communication link and a wireless communication link.
FIG. 12 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by wireless communication links.
FIG. 13 is a schematic diagram of an embodiment of the FIG. 1 communication system where communication links are embodied by wireline communication links.
FIG. 14 is a schematic diagram of another embodiment of the FIG. 1 communication system where communication links are embodied by wireline communication links.
FIG. 15 is a schematic diagram of an alternate embodiment of the network gateway of the FIG. 1 communication system.
FIG. 16 is a schematic diagram of a communication system including an embodiment of the FIG. 15 network gateway, according to an embodiment.
FIG. 17 is a schematic diagram of a communication system including an alternate network gateway, according to an embodiment.
FIG. 18 is a schematic diagram of an alternate embodiment of the FIG. 12 communication system.
DETAILED DESCRIPTION OF THE EMBODIMENTS
There is significant interest in achieving high reliability in premises communication networks, such as communication networks in homes and businesses. For example, a home communication network's user may be significantly inconvenienced if the communication network fails. As another example, a business may be unable to operate and thereby loose significant revenue if the business's communication network fails. Furthermore, property damage or even personal injury may result from failure of a communication network which performs an essential function.
Accordingly, many network gateways are now available with a backup power source, such as a backup battery, to power the network gateway in case a primary power source fails. Such inclusion of a backup power source in a network gateway helps achieve reliability by reducing likelihood of downtime due to a power failure. However, conventional network gateways are susceptible to downtime due to failure of an access communication network supporting the network gateway. For example, a network gateway supported by a wireline access network will experience downtime if a cable of the wireline access network is severed. As another example, a network gateway supported by a wireless access network will experience downtime if a wireless base station of the wireless access network suffers storm damage.
Disclosed herein are network gateways with redundant communication capability which at least partially overcome the above discussed drawbacks of conventional network gateways. These new network gateways include a plurality of access communication interfaces, which advantageously enable the network gateways to be supported by two or more different access networks, thereby achieving communication redundancy. Consequently, the new network gateways can continue to operate even if a supporting access network fails. In some embodiments, there is essentially no downtime in event of an access network failure, while in some other embodiments, there is only a short downtime, e.g. less than one minute, in response to an access network failure.
FIG. 1 is a schematic diagram of a communication system 100 including a network gateway 102 , where network gateway 102 is one embodiment of the new network gateways with redundant communication capability. Communication system 100 further includes a plurality of communication links 104 , termination devices 106 , a multi-path protocol (MPP) end point 108 , a traffic aggregator 110 , a network 112 , a network application 114 , and CPE 116 . In this document, specific instances of an item may be referred to by use of a numeral in parentheses (e.g. communication link 104 ( 1 )) while numerals without parentheses refer to any such item (e.g. communication links 104 ). Network gateway 102 includes a plurality of access communication interfaces 118 , a router 120 , an MPP end point 122 , a traffic aggregator 124 , and a local communication interface 126 .
Network gateway 102 is implemented, for example, by electrical circuitry (not shown) and/or by optical elements (not shown). Network gateway 102 may include additional elements without departing from the scope hereof. Additionally, two or more elements of network gateway 102 may be combined or at least partially implemented by common hardware, software, and/or firmware. For example, in some embodiments, one or more of router 120 , MPP end point 122 , and traffic aggregator 124 are implemented by common electrical circuitry (not shown). As another example, in some embodiments, one or more of router 120 , MPP end point 122 , and traffic aggregator 124 are implemented by a processor (not shown) executing non-transitory instructions in the form of software and/or firmware that are stored in a memory subsystem (not shown).
Network 112 includes, for example, the Internet, an Intranet, and/or one or more other communication networks. Network application 114 is communicatively coupled to network 112 , and network application 114 includes one or more resources that may be used by CPE 116 . Examples of network application 114 include, but are not limited to, a content application, a communication application, a gaming application, a productivity application, etc. Network 112 communicatively couples network application 114 to traffic aggregator 110 . Traffic aggregator 110 is communicatively coupled between network 112 and MPP end point 108 . Traffic aggregator 110 is configured to aggregate, e.g. encapsulate, downlink data packets from network 112 and transmit the aggregated data packets to MPP end point 108 . Additionally, traffic aggregator 110 is configured to de-aggregate, e.g. un-encapsulate, uplink data packets received from MPP end point 108 . MPP end point 108 cooperates with MPP end point 122 to establish multi-path communication between network 112 and network gateway 102 via the plurality of communication links 104 , using a multi-path data transmission protocol.
Each communication link 104 is, for example, an electrical communication link, an optical communication link, or a wireless communication link. Additionally, in some embodiments, one or more of communication links 104 are a hybrid communication link, e.g. a hybrid optical-electrical communication link, a hybrid optical-wireless communication link, a hybrid electrical-wireless communication link, a hybrid optical-electrical-wireless communication link, etc. Accordingly, in some embodiments, each communication link 104 includes one or more of an electrical cable (e.g. a coaxial electrical cable, a twisted pair electrical cable, an Ethernet electrical cable, a universal serial bus (USB) electrical cable), an optical cable, and wireless transceivers (e.g., wireless radio transceivers and/or wireless optical transceivers). Each communication link 104 communicatively couples a respective termination device 106 and a respective access communication interface 118 . Specifically, communication link 104 ( 1 ) communicatively couples termination device 106 ( 1 ) and access communication interface 118 ( 1 ), and communication link 104 ( 2 ) communicatively couples termination device 106 ( 2 ) and access communication interface 118 ( 2 ).
Each termination device 106 is configured to interface its respective communication link 104 with MPP end point 108 . Examples of termination devices 106 include, but are not limited to, a cable modem termination system (CMTS), a digital subscriber line access multiplexer (D SLAM), an optical line terminal (OLT), an optical network unit (ONU), a wireless communication station controller, such as a wireless communication system packet core, a wireless communication evolved packet core (EPC), a fifth generation (5G) wireless communication packet core, a sixth generation (6G) wireless communication packet core, a WiFi controller, a satellite communication system controller, a router, a switch, a hub, a USB controller, a Bluetooth controller, and extensions, modifications, and successions of any of the foregoing. Two or more termination device 106 instances could be replaced with a single termination device supporting multiple communication links 104 without departing from the scope hereof.
Each access communication interface 118 is configured to interface its respective communication link 104 with network gateway 102 , and each access communication interface 118 need not have the same configuration. In some embodiments, one or more access communication interfaces 118 are a wireless communication interface, including but not limited to a wireless communication interface configured to communicate via a cellular communication protocol (e.g., a Long Term Evolution (LTE) communication protocol, a 5G communication protocol, a 6G communication protocol), a WiFi communication protocol, a satellite communication protocol, a Bluetooth communication protocol, and/or a free space optical communication protocol. In some embodiments, one or more access communication interfaces 118 are an electrical communication interface, including but not limited an electrical communication interface configured to electrically couple to one or more of a coaxial electrical cable, a twisted pair electrical cable, an Ethernet electrical cable, and a USB electrical cable. In some embodiments, one or more of access communication interfaces 118 are an optical communication interface, such as configured to communicatively couple to an optic cable.
Router 120 is configured to route data packets between (a) CPE 116 and (b) each access communication interface 118 . Although only a single connection is depicted between router 120 and MPP end point 122 , in some embodiments, router 120 forms a separate respective logical connection between each access communication interface 118 and MPP end point 122 . As discussed above, MPP end point 122 cooperates with MPP end point 108 to establish multi-path communication between network 112 and network gateway 102 via the plurality of communication links 104 , using a multi-path data transmission protocol. In some embodiments, the multi-path data transmission protocol is a multi-path transmission control protocol (MPTCP). Traffic aggregator 124 is configured to aggregate, e.g. encapsulate, uplink data packets from CPE 116 and transmit the aggregated data packets to MPP end point 122 . Additionally, traffic aggregator 124 is configured to de-aggregate, e.g. un-encapsulate, downlink data packets received from MPP end point 122 .
Local communication interface 126 is configured to interface network gateway 102 with CPE 106 . In some embodiments, local communication interface 126 includes one or more of a wireless communication interface (e.g., configured to communicate via a cellular communication protocol (e.g., a LTE communication protocol, a 5G communication protocol, a 6G communication protocol), a WiFi communication protocol, a satellite communication protocol, a Bluetooth communication protocol, and/or a free space optical communication protocol), an electrical communication interface (e.g., configured to electrically couple to one or more of a coaxial electrical cable, a twisted pair electrical cable, an Ethernet electrical cable, and a USB electrical cable), and an optical communication interface (e.g. configured to communicatively couple to an optic cable).
CPE 116 is illustrated as including a mobile telephone 128 and a personal computer 130 , which are each illustrated as being communicatively coupled to network gateway 102 via local communication interface 126 . For example, in some embodiments, mobile telephone 128 is communicatively coupled to local communication interface 126 via a wireless communication link, and personal computer 130 is communicatively coupled to local communication interface 126 via an Ethernet electrical cable. However, the number of elements of CPE 116 , as well as the configuration of each element of CPE 116 , may vary without departing from the scope hereof. Examples of possible CPE 116 include, but are not limited to, a mobile telephone, a computer, a set-top device, a data storage device, an Internet of Things (IoT) device, an entertainment device, a computer networking device, a smartwatch, a wearable device with wireless capability, a medical device, a security device, a monitoring device, and a wireless access device (including, for example, an eNB, a gNB, a Wi-Fi-based wireless access point, an IAB access point, a microcell, a picocell, a femtocell, a macrocell, a Wi-Fi-based application, a satellite communication device, etc).
Use of MPP end points
108 and 122 advantageously makes presence of the plurality of communication links 114 invisible to network application 114 and CPE 116 . Specifically, network gateway 102 presents a single network identifier ID1, which represents the network gateway, to each of network application 114 and CPE 116 , even though each access communication interface 118 ( 1 ) and 118 ( 2 ) is represented by its own respective network identifier. Specifically, access communication interface 118 ( 1 ) is represented by a network identifier ID2, and access communication interface 118 ( 2 ) is represented by a network identifier ID3, where each of ID1, ID2, and ID3 are different. MPP end points
108 and 122 hide presence of ID2 and ID3 to network application 114 and CPE 116 , such that network application 114 and CPE 116 are only aware of ID1. In some embodiments, each of ID1, ID2, and ID3 is an Internet Protocol (IP) address, such as a version 4 IP address, a version 6 IP address, or a successor version IP address.
Presence of a plurality of access communication interfaces 118 in network gateway 102 advantageously enables network gateway 102 to be supported by multiple access networks, where each communication link 104 is associated with a respective access network. Consequently, network gateway 102 is capable of continuing to operate in event of failure of one communication link 104 . Additionally, in some embodiments, presence of MPP endpoint 122 in network gateway 102 causes failure of a communication link 104 to be imperceptible to CPE 116 and network application 114 , such that network gateway 102 does not experience downtime in response to the communication link 104 failure. Furthermore, some embodiments of network gateway 102 are configured to leverage the plurality of access communication interfaces 118 to simultaneously transmit data packets through a plurality of communication links 104 , such as to achieve high data transmission throughput.
Each of FIGS. 2 and 3 is a dataflow diagram illustrating a respective example of operation of communication system 100 of FIG. 1 . FIGS. 2 and 3 include vertical lines logically representing each of CPE 116 , communication interface 118 ( 1 ), communication interface 118 ( 2 ), termination device 106 ( 1 ), termination device 106 ( 2 ), and network application 114 . Network 112 , traffic aggregator 110 , MPP end point 108 , communication links 104 , router 120 , MPP end point 122 , traffic aggregator 124 , and local communication interface 126 are not shown in FIGS. 2 and 3 for illustrative clarity.
Referring to FIG. 2 at time t 1 , uplink data packets are transferred from CPE 116 to network application 114 via access communication interface 118 ( 1 ), communication link 104 ( 1 ), and termination device 106 ( 1 ). At time t 2 , downlink data packets are transferred from network application 114 to CPE 116 via termination device 106 ( 1 ), communication link 104 ( 1 ), and access communication interface 118 ( 1 ). At time t 3 an event occurs, and network gateway 102 transfers data packets between CPE 116 and network application 114 via access interface 118 ( 2 ), instead of access interface 118 ( 1 ), in response to the event occurrence. Examples of the event include, but are not limited to, failure of communication link 104 ( 1 ), degradation of communication link 104 ( 1 ), congestion on communication link 104 ( 1 ), or increase in cost to use communication link 104 ( 1 ). Accordingly, at time t 4 , uplink data packets are transferred from CPE 116 to network application 114 via access communication interface 118 ( 2 ), communication link 104 ( 2 ), and termination device 106 ( 2 ). At time t 5 , downlink data packets are transferred from network application 114 to CPE 116 via termination device 106 ( 2 ), communication link 104 ( 2 ), and access communication interface 118 ( 2 ). Thus, network gateway 102 continues to operate by using access communication interface 118 ( 2 ) and its associated communication link 104 ( 2 ) despite the event occurrence at time t 3 .
FIG. 3 illustrates an example of operation of communication system 100 where network gateway 102 initially uses both access communication interfaces 118 ( 1 ) and 118 ( 2 ) to transfer data packets between CPE 116 and network application 114 , and network gateway 102 subsequently uses only access communication interface 118 ( 2 ) in response to an event occurrence. At time t 1 , uplink data packets are transferred from CPE 116 to network application 114 via access communication interface 118 ( 1 ), communication link 104 ( 1 ), and termination device 106 ( 1 ). Additionally, at time t 2 , uplink data packets are transferred from CPE 116 to network application 114 via access communication interface 118 ( 2 ), communication link 104 ( 2 ), and termination device 106 ( 2 ), such that network gateway 102 essentially uses both communication links 104 ( 1 ) and 104 ( 2 ) in parallel. Similarly, at time t 3 , downlink data packets are transferred from network application 114 to CPE 116 via termination device 106 ( 1 ), communication link 104 ( 1 ), and access communication interface 118 ( 1 ). Additionally, at time t 4 , downlink data packets are transferred from network application 114 to CPE 116 via termination device 106 ( 2 ), communication link 104 ( 2 ), and access communication interface 118 ( 2 ).
At time t 5 an event occurs, and network gateway 102 transfers data packets between CPE 116 and network application 114 via access interface 118 ( 2 ), instead of access interface 118 ( 1 ), in response to the event occurrence. Examples of the event include, but are not limited to, failure of communication link 104 ( 1 ), degradation of communication link 104 ( 1 ), congestion on communication link 104 ( 1 ), or increase in cost to use communication link 104 ( 1 ). Accordingly, at time t 6 , uplink data packets are transferred from CPE 116 to network application 114 via access communication interface 118 ( 2 ), communication link 104 ( 2 ), and termination device 106 ( 2 ). At time t 7 , downlink data packets are transferred from network application 114 to CPE 116 via termination device 106 ( 2 ), communication link 104 ( 2 ), and access communication interface 118 ( 2 ). Thus, network gateway 102 continues to operate by using access communication interface 118 ( 2 ) and its associated communication link 104 ( 2 ) despite the event occurrence at time t 5 .
FIG. 4 is a flow chart of a method 400 for redundant communication at a network gateway. Although method 400 is discussed below with respect to communication system 100 of FIG. 1 , method 400 could be used with other communication systems including network gateway 102 , or a variation thereof, without departing from the scope hereof. In a block 402 of method 400 , data packets are exchanged with a network application gateway via a first access communication interface. In one example of block 402 , network gateway 102 exchanges data packets with network application 114 via access communication interface 118 ( 1 ). In a block 404 of method 400 , data packets are exchanged with CPE via a local access communication interface. In one example of block 404 , network gateway 102 exchanges data packets with CPE 116 via local communication interface 126 . In a block 406 of method 400 , at least some data packets are exchanged with the network application via a second access communication interface that is different from the first access communication interface, in response to occurrence of a first event. In one example of block 406 , network gateway 102 exchanges data packets with network application 114 via access communication interface 118 ( 2 ), in response to an event occurrence. Examples of the event include, but are not limited to, failure of communication link 104 ( 1 ), degradation of communication link 104 ( 1 ), congestion on communication link 104 ( 1 ), increase in cost to use communication link 104 ( 1 ), or availability of communication link 104 ( 2 ) after communication link 104 ( 2 ) was previously unavailable.
FIG. 5 is a schematic diagram of a network gateway 502 , which is one possible embodiment of
CLAIMS
Claims ( 16 )
What is claimed is:
1. A method for redundant communication at a network gateway, comprising:
exchanging data packets with a network application via a first access communication interface;
exchanging data packets with customer premises equipment (CPE) via a local communication interface;
exchanging at least some data packets with the network application via a second access communication interface that is different from the first access communication interface; and
representing the network gateway to the network application using a first Internet Protocol (IP) address irrespective of whether using the first access communication interface to exchange data packets with the network application or the second access communication interface to exchange data packets with the network application.
2. The method of claim 1 , further comprising:
representing the first access communication interface using a second IP address that is different from the first IP address; and
representing the second access communication interface using a third IP address that is different from each of the first IP address and the second IP address.
3. The method of claim 1 , further comprising representing the network gateway to the CPE using the first IP address.
4. The method of claim 1 , further comprising aggregating data packets received at the network gateway from the CPE for transfer to the network application via either the first access communication interface or the second access communication interface.
5. The method of claim 4 , further comprising exchanging data packets with the network application at least partially using a multi-path protocol.
6. The method of claim 5 , wherein the multi-path protocol comprises a multi-path transmission control protocol (MPTCP).
7. The method of claim 1 , wherein:
the first access communication interface is configured to communicatively couple to one of a coaxial electrical cable, a twisted pair electrical cable, and an optical cable; and
the second access communication interface is configured to communicatively couple to one of an Ethernet electrical cable and a universal serial bus (USB) electrical cable.
8. The method of claim 1 , wherein:
the first access communication interface is configured to communicatively couple to one of a coaxial electrical cable, a twisted pair electrical cable, and an optical cable; and
the second access communication interface comprises a wireless communication interface.
9. The method of claim 1 , wherein each of the first access communication interface and the second access communication interface comprises a respective wireless communication interface.
10. The method of claim 1 , further comprising routing data packets between (a) the CPE and (b) each of the first access communication interface and the second access communication interface.
11. A network gateway with redundant communication capability, comprising:
a first access communication interface;
a second access communication interface;
a local communication interface;
a router configured to route data packets between (a) customer premises equipment (CPE) communicatively coupled to the local communication interface and (b) each of the first access communication interface and the second access communication interface; and
a multi-path protocol end point configured to present a single Internet Protocol (IP) address to the CPE irrespective of whether the router is routing data packets between the CPE and the first access communication interface or between the CPE and the second access communication interface.
12. The network gateway of claim 11 , wherein the multi-path protocol end point is further configured to exchange data packets with a network application via each of the first and second access communication interfaces using a multi-path data transmission protocol.
13. The network gateway of claim 12 , where the multi-path data transmission protocol comprises a multi-path transmission control protocol (MPTCP).
14. The network gateway of claim 11 , wherein:
the first access communication interface is configured to communicatively couple to one of a coaxial electrical cable, a twisted pair electrical cable, and an optical cable; and
the second access communication interface is configured to communicatively couple to one of an Ethernet electrical cable and a universal serial bus (USB) electrical cable.
15. The network gateway of claim 11 , wherein:
the first access communication interface is configured to communicatively couple to one of a coaxial electrical cable, a twisted pair electrical cable, and an optical cable; and
the second access communication interface comprises a wireless communication interface.
16. The network gateway of claim 11 , wherein each of the first access communication interface and the second access communication interface comprises a respective wireless communication interface.
US18/157,894
2019-09-10
2023-01-23
Network gateways with redundant communication capability, and associated methods
Active
US12010010B1
( en )
Priority Applications (1)
Application Number
Priority Date
Filing Date
Title
US18/157,894
US12010010B1
( en )
2019-09-10
2023-01-23
Network gateways with redundant communication capability, and associated methods
Applications Claiming Priority (3)
Application Number
Priority Date
Filing Date
Title
US201962898087P
2019-09-10
2019-09-10
US17/017,472
US11563673B1
( en )
2019-09-10
2020-09-10
Network gateways with redundant communication capability, and associated methods
US18/157,894
US12010010B1
( en )
2019-09-10
2023-01-23
Network gateways with redundant communication capability, and associated methods
Related Parent Applications (1)
Application Number
Title
Priority Date
Filing Date
US17/017,472
Continuation
US11563673B1
( en )
2019-09-10
2020-09-10
Network gateways with redundant communication capability, and associated methods
Publications (1)
Publication Number
Publication Date
US12010010B1
true
US12010010B1 ( en )
2024-06-11
Family
ID=84978065
Family Applications (2)
Application Number
Title
Priority Date
Filing Date
US17/017,472
Active
US11563673B1
( en )
2019-09-10
2020-09-10
Network gateways with redundant communication capability, and associated methods
US18/157,894
Active
US12010010B1
( en )
2019-09-10
2023-01-23
Network gateways with redundant communication capability, and associated methods
Family Applications Before (1)
Application Number
Title
Priority Date
Filing Date
US17/017,472
Active
US11563673B1
( en )
2019-09-10
2020-09-10
Network gateways with redundant communication capability, and associated methods
Country Status (1)
Country
Link
US
( 2 )
US11563673B1
( en )
Families Citing this family (2)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US11563673B1
( en )
*
2019-09-10
2023-01-24
Cable Television Laboratories, Inc.
Network gateways with redundant communication capability, and associated methods
CN114520938A
( en )
*
2020-11-20
2022-05-20
å为ææ¯æéå ¬å¸
Data transmission method and related equipment
Citations (8)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20060262775A1
( en )
2003-08-26
2006-11-23
Norbert Lobig
Method for controlling highly accessible user access networks via a packet-based network service point
US20060291378A1
( en )
2005-06-28
2006-12-28
Alcatel
Communication path redundancy protection systems and methods
US20160164777A1
( en )
*
2013-04-17
2016-06-09
Systech Corporation
Gateway device for machine-to-machine communication with dual cellular interfaces
US20190335520A1
( en )
2018-04-27
2019-10-31
Nokia Solutions And Networks Oy
Traffic steering for stateless packets over multipath networks
US20200310920A1
( en )
2019-03-29
2020-10-01
Honeywell International Inc.
Redundant controllers or input-output gateways without dedicated hardware
US20210234729A1
( en )
2020-01-29
2021-07-29
Arris Enterprises Llc
Methods, systems, and devices for steering packets across multiple access technologies
US20220141666A1
( en )
*
2019-03-04
2022-05-05
Systech Corporation
Gateway device for secure machine-to-machine communication
US11563673B1
( en )
*
2019-09-10
2023-01-24
Cable Television Laboratories, Inc.
Network gateways with redundant communication capability, and associated methods
2020
2020-09-10
US
US17/017,472
patent/US11563673B1/en
active
Active
2023
2023-01-23
US
US18/157,894
patent/US12010010B1/en
active
Active
Patent Citations (10)
* Cited by examiner, â Cited by third party
Publication number
Priority date
Publication date
Assignee
Title
US20060262775A1
( en )
2003-08-26
2006-11-23
Norbert Lobig
Method for controlling highly accessible user access networks via a packet-based network service point
US20060291378A1
( en )
2005-06-28
2006-12-28
Alcatel
Communication path redundancy protection systems and methods
US20160164777A1
( en )
*
2013-04-17
2016-06-09
Systech Corporation
Gateway device for machine-to-machine communication with dual cellular interfaces
US20190159046A1
( en )
2013-04-17
2019-05-23
Systech Corporation
Gateway device for machine-to-machine communication with dual cellular interfaces
US20210006991A1
( en )
*
2013-04-17
2021-01-07
Systech Corporation
Gateway device for machine-to-machine communication with dual cellular interfaces
US20190335520A1
( en )
2018-04-27
2019-10-31
Nokia Solutions And Networks Oy
Traffic steering for stateless packets over multipath networks
US20220141666A1
( en )
*
2019-03-04
2022-05-05
Systech Corporation
Gateway device for secure machine-to-machine communication
US20200310920A1
( en )
2019-03-29
2020-10-01
Honeywell International Inc.
Redundant controllers or input-output gateways without dedicated hardware
US11563673B1
( en )
*
2019-09-10
2023-01-24
Cable Television Laboratories, Inc.
Network gateways with redundant communication capability, and associated methods
US20210234729A1
( en )
2020-01-29
2021-07-29
Arris Enterprises Llc
Methods, systems, and devices for steering packets across multiple access technologies
Also Published As
Publication number
Publication date
US11563673B1
( en )
2023-01-24
Similar Documents
Publication
Publication Date
Title
CN110049512B
( en )
2022-08-02
Forward-transmission network data processing device and method
EP3777294B1
( en )
2026-04-29
Wireless access point and method for providing backup network connections
US8374129B2
( en )
2013-02-12
Circuit switched millimeter wave communication network
US9608838B2
( en )
2017-03-28
Bonded interconnection of local networks
US8254905B2
( en )
2012-08-28
Service monitoring and disconnection notification in a wireless gateway device
CN103875216A
( en )
2014-06-18
An access system, communication method and equipment for an optical fiber network
JP2014121054A
( en )
2014-06-30
Base station apparatus
US11563673B1
( en )
2023-01-24
Network gateways with redundant communication capability, and associated methods
US12028185B2
( en )
2024-07-02
Methods, systems, and devices for steering packets across multiple access technologies
CN115348633A
( en )
2022-11-15
Method, system, device and storage medium for switching active and standby links of base station gateway
US20160087896A1
( en )
2016-03-24
Interface Switching Method and Device
CN109983799B
( en )
2021-06-01
an integrated access system
US7522614B1
( en )
2009-04-21
Multi-service access platform for telecommunications and data networks
US11652711B1
( en )
2023-05-16
Systems and methods for providing individualized communication service
CN108337162B
( en )
2020-11-10
System and method for supporting dual-homing protection
JP2008167331A
( en )
2008-07-17
Extended maintenance domain level management method, communication apparatus, program, and data structure
US11265795B2
( en )
2022-03-01
Small cell backhaul
US11947403B1
( en )
2024-04-02
Systems and methods for operating a termination device of an access communication network
US12052653B1
( en )
2024-07-30
Converged access communication systems and associated methods
CN115913904A
( en )
2023-04-04
Data communication method, device and equipment based on flow control transmission protocol
JP7039888B2
( en )
2022-03-23
Master station communication device, subscriber side device, and optical communication network system
US12341630B1
( en )
2025-06-24
Communication network gateways and associated methods
US11627506B1
( en )
2023-04-11
Systems and methods for reducing latency during handover of user equipment between wireless base stations
CN115441981B
( en )
2024-12-10
Scheduling system, method, device, electronic device and storage medium
JP2009135681A
( en )
2009-06-18
Communication system and media converter
Legal Events
Date
Code
Title
Description
2023-01-23
FEPP
Fee payment procedure
Free format text : ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY
2023-02-09
FEPP
Fee payment procedure
Free format text : ENTITY STATUS SET TO SMALL (ORIGINAL EVENT CODE: SMAL); ENTITY STATUS OF PATENT OWNER: SMALL ENTITY
2024-05-22
STCF
Information on status: patent grant
Free format text : PATENTED CASE