Mobile network operating method

• US 10,075,376 B2
• Filed: 03/18/2013
• Issued: 09/11/2018
• Est. Priority Date: 04/18/2007
• Status: Active Grant

• Current Assignee: WAAV Incorporated
• Original Assignee: WAAV Incorporated
• Inventors: Fulknier, John C, Smith, Brian J
• Primary Examiner(s): Wu, Jianye
• Application Number:
  US13/846,575
• Publication Number:
  US 20140269327A1
• Time in Patent Office: 2,003 Days
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 47/125 by balancing the load, e.g. traffic engineering
• CPC Class Codes: H04W 28/0205 at the air interface dynamic wireless traffic scheduling H04W72/12
• CPC Class Codes: H04W 40/18 based on predicted events

Abstract

A network routing method includes operating a plurality of mobile computing devices in a cellular network environment with each mobile computing device including one or more cellular network interface devices each operable as a client of a cellular network that provides access to a WAN. Non-locally reachable network traffic originating on each mobile computer device is routed the one or more cellular network interfaces to a network controller reachable over the WAN. The network controller receives the non-locally reachable traffic and routes the non-locally reachable traffic to its original destination IP address. The network controller further operates to cause reply traffic responsive to the non-locally reachable traffic to be routed back to the network controller. The network controller further operates to route the reply traffic back to the originating mobile computer device over any of the one more cellular network interfaces.

Claims

1. A network routing method comprising:

operating a mobile computing device in a cellular network environment wherein the mobile computing device includes a subnet microprocessor, a subnet memory module in communication with the subnet microprocessor, a cellular network interface device in communication with the subnet microprocessor and a local area network interface device in communication with the subnet microprocessor;

operating the cellular network interface device to become a client of a cellular network that provides network access to a WAN, wherein the cellular network interface device is assigned a cellular IP address;

operating a network controller as a node on the WAN, wherein the network controller comprises a controller microprocessor, a controller memory and a WAN network interface device each in communication with the controller microprocessor and wherein the WAN network interface device is assigned a controller IP address;

operating the mobile computing device to establish a local subnet in communication with locally reachable network devices, wherein at least one of the locally reachable network devices is established as a client of the local subnet and wherein, the local subnet assigns each client of the local subnet a subnet IP address;

receiving, by the local subnet, from any client of the local subnet, a subnet data packet comprising, an IP payload and an inner IP header that precedes the IP payload, wherein the inner IP header includes a source IP address corresponding with the subnet IP address of the subnet client that the subnet data packet was received from, and a destination IP address corresponding with a destination IP address of the subnet data packet;

reading by the mobile computing device, from the inner IP header, the destination IP address of the subnet data packet, and the source IP address corresponding with the subnet IP address of the subnet client that the subnet data packet was received from;

determining, by the mobile computing device, if the destination IP address of the subnet data packet is a subnet IP address associated with the local subnet; and

,

if not;

assigning, by the mobile computing device, to an exit data packet, a first network route for routing the exit data packet to the controller IP address over the cellular network interface device; and

,

modifying, by the mobile computing device, the subnet data packet, to form the exit data packet, wherein the exit data packet comprises, the IP payload, the inner IP header preceding the IP payload, and a tunnel IP header preceding the inner IP header, wherein the tunnel IP header includes a destination IP address corresponding with the controller IP address, and a source IP address corresponding with the cellular IP address;

routing, by the mobile computing device, the exit data packet out of the mobile computing device, over the first network route;

receiving, by the network controller, the exit data packet;

modify, by the network controller, the exit data packet to form a WAN data packet wherein the WAN data packet includes the subnet data packet and a WAN IP header that precedes the subnet data packet, wherein the WAN IP header is configured to route the subnet data packet to the destination IP address of the subnet data packet and further configured to cause one or more reply data packets responsive to the subnet data packet to be routed back to the network controller; and

,

modifying, by the network controller, the one or more reply data packets to form a reply tunnel packet that includes the reply data packet and a reply tunnel IP header that precedes the reply data packet, wherein the reply tunnel IP header is configured to route the reply data packet to the mobile computing device.

2. The method of claim 1 further comprising:

generating, by the mobile computing device, a first data table stored on the mobile computing device;

storing, by the mobile computing device, in the first data table, data read from the inner IP header and listed in the tunnel IP header; and

,

associating, by the mobile computing device, the exit data packet, with the destination IP addresses of the subnet data packet, the cellular IP address and the subnet IP address of the subnet client that the subnet data packet was received from.

3. The method of claim 1 further comprising:

reading, by the network controller, from the tunnel IP header, the cellular IP address listed therein and removing the tunnel IP header from the exit data packet;

reading, by the network controller, from the inner IP header, the destination IP address of the subnet data packet and the subnet IP address of the subnet client that the subnet data packet was received from;

determining, by the network controller, if the destination IP address of the subnet data packet is a locally reachable subnet IP address associated with the network controller; and

,

if not;

assigning, by the network controller, to the WAN data packet, a second network route for routing the WAN data packet, to the destination IP address of the subnet data packet, over the WAN network interface device;

wherein the WAN IP header includes, a destination IP address corresponding with the destination IP address of the subnet data packet and a source IP address corresponding with the controller IP address.

4. The method of claim 3 further comprising:

receiving, by the network controller, from the destination IP address of the subnet data packet, the one or more reply data packets responsive to the WAN data packet;

wherein each reply data packet comprises, a reply IP payload and a reply IP header preceding the reply IP payload, wherein the reply IP header includes a destination IP address corresponding with the network controller IP address, and a source IP address corresponding with the destination IP address of the subnet data packet;

reading, by the network controller, from the reply IP header, the destination IP address of the subnet data packet, and removing the reply IP header from the reply data packet;

determining, by the network controller, from data stored by the network controller, the WAN data packet corresponding with the reply data packet, a cellular IP address presently corresponding with the cellular network interface device and the subnet IP address of the subnet client that the subnet data packet was received from; and

assigning, by the network controller, to a reply tunnel packet, a third network route for routing, the reply tunnel packet, to the cellular IP address presently corresponding with the cellular network interface device, over the WAN network interface device;

modifying, by the network controller, the reply data packet to form the reply tunnel packet, wherein the reply tunnel packet comprises, the reply IP payload, a reply inner IP header that precedes the reply IP payload and a reply IP tunnel header that precedes the reply inner IP header, wherein the reply inner IP header includes a destination IP address corresponding with the subnet IP address of the subnet client that the subnet data packet was received from and a source IP address corresponding with the destination IP address of the subnet data packet, wherein the reply tunnel IP header includes a destination IP address corresponding with the cellular IP address presently corresponding with the cellular network interface device and a source IP address corresponding with the network controller IP address; and

,

routing, by the network controller, the reply tunnel packet, out of the network controller, over the third network route.

5. The method of claim 2 further comprising:

generating, by the network controller, a second data table, stored on the network controller;

storing, by the network controller, in the second data table, data read from each of the tunnel IP header, the inner IP header and listed in the WAN IP header; and

,

associating, by the network controller, the WAN data packet, with the destination IP address of the subnet data packet, the cellular IP address, and the subnet IP address of the subnet client that the subnet data packet was received from.

6. The method of claim 4 further comprising:

receiving, by the mobile computing device, from the network controller, over the cellular network interface device, the reply tunnel packet;

reading, by the mobile computing device, the cellular IP address from the reply tunnel IP header and removing the reply tunnel IP header from the reply tunnel packet;

reading, by the mobile computing device, from the reply inner IP header, the destination IP address corresponding with the subnet IP address that the subnet data packet was received from and the source IP address corresponding with the subnet client that the subnet data packet was received from; and

,

routing, by the mobile computer device, the reply IP packet to the source IP address that the subnet data packet was received from.

7. The method of claim 6 further comprising:

generating, by the mobile computing device, a first data table stored on the mobile computing device;

generating, by the network controller, a second data table stored on the network controller;

storing, by the mobile computing device, in the first data table, data read from the inner IP header and listed in the tunnel IP header of the exit data packet;

associating, by the mobile computing device, the exit data packet, with the destination IP addresses of the subnet data packet, the cellular IP address and the subnet IP address of the subnet client that the subnet data packet was received from;

storing, by the network controller, in the second data table, data read from the inner IP header and listed in the tunnel IP header of the exit data packet and data read from the reply inner header and the reply tunnel header;

associating, by the network controller, the exit data packet with the destination IP address of the subnet data packet, the cellular IP address, presently corresponding with the cellular network interface device, and the subnet IP address of the subnet client that the subnet data packet was received from;

storing, by the mobile computing device, in the first data table, data read from the reply tunnel IP header and from the reply inner IP header that at least includes, the subnet IP address that the subnet data packet was received from, the destination IP address of the subnet data packet, and the cellular IP address presently corresponding with the cellular network interface device; and

,

associating, by the mobile computing device, the reply tunnel packet with the destination IP address of the subnet data packet, the cellular IP address, presently corresponding with the cellular network interface device, and the subnet IP address of the subnet client that the subnet data packet was received from.

8. The method of claim 7 wherein the subnet data packet further lists in the inner IP header thereof, first control data associated with routing the subnet data packet wherein the first control data is included by the subnet client that the subnet data packet was received from, further comprising:

reading, by the mobile computing device, from the subnet data packet inner IP header, the first control data;

storing, by the mobile computing device, in the first data table, at least a portion of the first control data; and

,

associating, by the mobile computing device, the stored first control data with, the destination IP addresses of the subnet data packet and with the subnet IP address of the subnet client that the subnet data packet was received from.

9. The method of claim 8 wherein the first control data comprises a subnet packet ID, further comprising:

storing, by the mobile computing device, in the first data table, the subnet packet ID; and

,

associating, by the mobile computing device, the subnet packet ID with the destination IP addresses of the subnet data packet, the subnet IP address of the subnet client that the subnet data packet was received from and the cellular IP address.

10. The method of claim 9 further comprising:

generating, by the mobile computing device, after assigning the first network route to the exit data packet, second control data associated with routing the exit data packet over the first network route, wherein the second control data is different from the first control data;

writing, by the mobile computing device, to the tunnel IP header, the second control data;

writing, by the mobile computing device, to the first data table, at least a portion of the second control data and,

associating, by the mobile computing device, the stored second control data with the destination IP addresses of the subnet data packet, the subnet IP address of the subnet client that the subnet data packet was received from and the cellular IP address.

11. The method of claim 10 further comprising:

reading, by the network controller, from the tunnel IP header, the second control data;

storing, by the network controller, to the second data table, at least a portion of the second control data;

associating, by the network controller, the stored second control data with the destination IP addresses of the subnet data packet, the subnet IP address of the subnet client that the subnet data packet was received from and the cellular IP address.

12. The method of claim 10 wherein the mobile computing device has a subnet ID, further comprising:

including, by the mobile computing device, the subnet ID in the second control data listed in the tunnel IP header and stored in the first data table;

reading, by the network controller, from the tunnel IP header, the subnet ID;

storing, by the network controller, in the second data table, the subnet ID; and

,

associating, by the network controller and by the mobile computing device the subnet ID with the cellular IP address.

13. The method of claim 10 further comprising:

generating, by the network controller, after assigning the second network route to the WAN data packet, third control data associated with routing the WAN data packet over the second network route, wherein the third control data is different from the first and the second control data;

writing, by the network controller, to the WAN IP header, the third control data;

writing, by the network controller, to the second data table, at least a portion of the third control data and,

associating, by the network controller, the stored third control data with the destination IP addresses of the subnet data packet, the subnet IP address of the subnet client that the subnet data packet was received from and the cellular IP address.

14. The method of claim 2 wherein the mobile computing device has a subnet ID, further comprising:

writing, by the mobile computing device, to the tunnel IP header, the subnet ID,

storing, by the mobile computing device, in the first data table, the subnet ID; and

,

associating, by the mobile computing device, the subnet ID with the subnet data packet, with the exit data packet corresponding with the subnet data packet and with the cellular IP address.

15. The method of claim 3 wherein mobile computing device has a subnet ID, further comprising:

writing, by the mobile computing device, to the tunnel IP header, the subnet ID;

storing, by the mobile computing device, the subnet ID;

associating, by the mobile computing device, the subnet ID with the subnet data packet, with the exit data packet corresponding with the subnet data packet and with the cellular IP address;

reading, by the network controller, from the tunnel IP header, the subnet ID;

storing, by the network controller, the subnet ID; and

,

associating, by the network controller, the subnet ID with the exit data packet, with the WAN data packet corresponding with the exit data packet, with the reply tunnel packet and with the cellular IP address.

16. The method of claim 14 wherein the mobile computing device has a subnet ID further comprising:

generating by the mobile computer device, from data stored in the first data table, a subnet network update at least listing, the subnet ID, the cellular IP address presently associated with the cellular network interface device, and each cellular IP address that has historically been associated with the cellular network interface device; and

,

uploading, by the mobile computing device, to the network controller, the subnet network update.

17. The method of claim 16 further comprising:

receiving, by the network controller, from the mobile computing device, the subnet network update;

storing, by the network controller, at least a portion of the data listed in the subnet network update; and

,

associating, by the network controller, the cellular IP address presently associated with the cellular network interface device and each cellular IP address that was historically associated with the cellular network interface device with the subnet ID.

18. A network routing method comprising the steps of:

operating, a mobile computing device, in a cellular network environment, wherein the mobile computing device comprises, a subnet microprocessor, a subnet memory module in communication with the subnet microprocessor, one or more local area network interface devices in communication with the subnet microprocessor and a plurality of cellular network interface devices in communication with the subnet microprocessor;

operating, a network controller comprising, a controller microprocessor, a controller memory module, in communication with the controller microprocessor, and a Wide Area Network interface device in communication with the controller microprocessor, wherein the network controller is established as a client of a Wide Area Network (WAN) and is assigned, a controller IP address;

establishing, by the one or more local area network interface devices, one or more local subnets operating on the mobile computing device, wherein each local subnet comprises at least one locally reachable network device operating as a client thereof and wherein each client thereof is assigned, a subnet IP address corresponding with one of the one or more local subnets;

operating at least two of the plurality of cellular network interface devices as a client of a cellular network that provides network access to the WAN, wherein each client of the cellular network is assigned, a cellular IP address corresponding with the cellular network;

receiving, by the mobile computing device, from one or more clients of the one or more local subnets, a plurality of subnet data packets, wherein each subnet data packet comprises, an IP payload and an IP inner header that precedes the IP payload, wherein the IP inner header lists therein, a destination IP address of the IP payload, a source IP address corresponding with a subnet IP address of the subnet client device that the subnet data packet was received from, and first control data;

reading, by the mobile computing device, from the inner IP header of each of the plurality of subnet data packets, the destination IP address of the IP payload, the source IP address corresponding with the subnet IP address of the subnet client device that the subnet data packet was received from, and the first control data;

determining, by the mobile computing device, for each of the plurality of subnet data packets received thereby, if the destination IP address of the IP payload is a locally reachable subnet IP address corresponding with one of the one or more local subnets; and

,

if not;

selecting, by the mobile computing device, one of the at least two clients of the cellular network as a first network route for routing each subnet data packet not having a locally reachable destination IP address out of the mobile computing device;

modifying, by the mobile computing device, each subnet data packet, not having a locally reachable destination IP address, to form a corresponding exit data packet configured to be routed to the network controller over the selected client of the cellular network; and

,

routing, by the mobile computing device, the exit data packet to the network controller over the selected client of the cellular network.

19. The network routing method of claim 18 wherein each exit data packet comprises, the subnet data packet corresponding therewith encapsulated by a tunnel IP header that precedes the inner IP header, wherein the tunnel IP header lists therein, a destination IP address corresponding with the network controller IP address and a source IP address corresponding with the cellular IP address of the selected client of the cellular network.

20. The method of claim 19 wherein the tunnel IP header further lists second control data therein, wherein the second control data is different from the first control data.

21. The method of claim 20 wherein each of the first control data and the second control data comprises any one of:

a packet IP version, a header length, a packet length, a packet type, a packet quality of service, a packet ID tag, packet fragmentation and offset data, a packet protocol, a check sum for error detection, a time to live and a reply port assignment.

22. The method of claim 18 wherein the inner IP header and the tunnel IP header are each configured for a different packet protocol.

23. The method of claim 19 further comprising the steps of:

generating, by the mobile computing device, a first data table, stored by the mobile computing device;

storing, by the mobile computing device, in the first data table, at least a portion of the data read from the inner IP header and at least a portion of the data written to the tunnel IP header; and

,

associating, by the mobile computing device, in the first data table, each subnet data packet and the exit date packet corresponding therewith, with, the destination IP address of the of the IP payload, the subnet IP address of the subnet client device that the subnet data packet was received from, and the cellular IP address of the selected client of the cellular network.

24. The method of claim 18 wherein each of the at least two of the plurality of cellular network interface devices operating as a client of the cellular network provides a different upload route between the mobile computing device and the network controller, further comprising the steps of:

operating each of the mobile computing device and the network controller to acquire, for each different upload route the network operating characteristics thereof;

exchanging, between the mobile computing device and the network controller, the network operating characteristic of each different upload route; and

,

storing, on each of the mobile computing device and the network controller, the network operating characteristic of each different upload route.

25. The method of claim 24 further comprising the step of;

operating, by the mobile computing device, an upload routing scheme configured to select, for each exit data packet, the client of the cellular network corresponding with an upload route that has a favorable network operating characteristic.

26. The method of claim 25 wherein operating the upload routing scheme further comprising the steps of:

storing, on the mobile computing device, upload route selection criteria;

comparing, by the mobile computing device, the upload route selection criteria with the network operating characteristic of each different upload route; and

,

selecting, by the mobile computing device, the client of the cellular network corresponding with the upload route that is most favorably matched to upload route selection criteria.

27. The method of claim 18:

wherein the cellular network that provides network access to the WAN includes a plurality of cellular networks, each of a different cellular network type;

wherein the plurality of cellular network interface devices in communication with the subnet microprocessor includes at least one cellular network interface device operable to be established as a client of each different cellular network type;

wherein the step of, selecting, by the mobile computing device, one of the at least two clients of the cellular network as a first network route includes selecting different cellular network interface device types operating as a client of different cellular network types.

28. The network routing method of claim 27:

wherein each exit data packet comprises, the subnet data packet corresponding therewith encapsulated by a tunnel IP header preceding the inner IP header;

wherein the tunnel IP header lists therein, a destination IP address corresponding with the network controller IP address, a source IP address corresponding with the cellular IP address of the selected client of the cellular network, and second control data;

wherein the tunnel IP header is configured to be compatible with being routed to the network controller over the selected cellular network interface device type and corresponding cellular network type.

29. The method of claim 18 further comprising the steps of:

receiving, by the mobile computing device, from the network controller, over at least two of the plurality of cellular network interface devices operating as a client of the cellular network, a plurality of reply tunnel packets each being responsive to a subnet data packet corresponding therewith;

wherein each reply tunnel packet includes a reply inner IP header preceding a reply IP payload, wherein the reply inner IP header lists therein, the subnet IP address of the subnet client device that the subnet data packet was received from, and the corresponding destination IP address of the subnet data packet;

reading, by the mobile computing device, from the reply inner IP header, the subnet IP address of the subnet client device that the subnet data packet was received from and the destination IP address of the subnet data packet; and

,

routing, by the mobile computer device, the reply IP payload to the subnet IP address that the subnet data packet was received from.

30. The method of claim 18 further comprising the step of:

receiving, by the network controller, from the mobile computing device, a plurality of exit data packets, wherein a portion of the plurality of exit data packets is received over a plurality of first network routes each corresponding with a different one of the least two clients of the cellular network.

31. The method of claim 21, further composing the steps of:

receiving, by the network controller, from the mobile computing device, a plurality of exit data packets, wherein a portion of the plurality of exit data packets is received over a plurality of first network routes with each first network route corresponding with a different one of the least two clients of the cellular network;

reading, by the network controller, from the tunnel IP header of each exit data packet, the cellular IP address listed therein, and removing the tunnel IP header therefrom;

reading, by the network controller, from the inner IP header of each exit data packet, the destination IP address of the subnet data packet, and the subnet IP address of the subnet client that the subnet data packet was received from;

determining, by the network controller, if the destination IP address of the subnet data packet is a locally reachable IP address associated with the network controller; and

,

if not;

assigning, by the network controller, to a WAN data packet corresponding with the exit data packet, a second network route for routing the WAN data packet from the network controller, to the destination IP address of the subnet data packet over the WAN network interface device;

modifying, by the network controller, the exit data packet to form the WAN data packet corresponding therewith, wherein the WAN data packet is modified to correspond with routing the WAN data packet over the assigned second network route; and

,

routing, by the network controller, the WAN data packet to the destination IP address of the subnet data packet over the assigned second network route.

32. The network routing method of claim 31 wherein the WAN data packet comprises, the subnet data packet encapsulated by a WAN IP header preceding the inner IP header, wherein the WAN IP header lists therein a destination IP address corresponding with the destination IP address of the subnet data packet, and a source IP address corresponding with the network controller IP address.

33. The method of claim 32 further comprising the steps of:

generating, by the network controller, a second data table, stored by the network controller;

storing, by the network controller, in the second data table, at least a portion of the data read from the inner IP header and at least a portion of the data written to the WAN IP header; and

,

associating, by the network controller, in the second data table, each WAN data packet and the exit data packet corresponding therewith, with, the destination IP address of the of the IP payload, the subnet IP address of the subnet client device that the subnet data packet was received from and the cellular IP address corresponding with the exit data packet.

34. The method of claim 33 wherein the WAN IP header further lists third control data therein and wherein the third control data is different from the second control data.

35. The method of claim 33 wherein the third control data comprises any one of:

a packet IP version, a header length, a packet length, a packet type, a packet quality of service, a packet ID tag, packet fragmentation and offset data, a packet protocol, a check sum for error detection, a time to live and a reply port assignment.

36. The method of claim 31 further comprising the steps of:

receiving, by the network controller, from the destination IP address of the subnet data packet, a reply data packet responsive to the WAN data packet, wherein the reply data packet comprises, a reply IP payload and a reply IP header preceding the reply IP payload, wherein the reply IP header includes, a destination IP address corresponding with the network controller IP address and a source IP address corresponding with the destination IP address of the subnet data packet;

reading, by the network controller, from the reply IP header, the destination IP address of the subnet data packet, and removing the reply IP header from the reply data packet;

determining, by the network controller, from the data stored on the second data table, the exit data packet corresponding with the reply data packet, the cellular IP address corresponding with the exit data packet and any other cellular IP addresses corresponding with the at least two clients of the cellular network;

selecting, by the network controller, one of the at least two clients of the cellular network as a third network route for routing a reply tunnel data packet to the mobile computing device over;

modifying, by the mobile computing device, each reply data packet to form a corresponding reply tunnel data packet configured to be routed to the mobile computing device over the selected client of the cellular network; and

,

routing, by network, the reply tunnel data packet to the mobile computing device over the selected client of the cellular network.

37. A network routing method comprising:

deploying, a network controller, on a network reachable from a WAN, wherein the network controller comprises a controller microprocessor and an associated controller memory module and one or more WAN network interface devices in communication with the controller microprocessor, wherein the one or more WAN network interface devices is each assigned a controller IP address and wherein the network controller is not operated as an autonomous system router of the WAN;

deploying, a mobile computing device, in a cellular network environment, wherein the mobile computing device comprises, a subnet microprocessor, and an associated subnet memory module, one or more local area network interface devices, each in communication with the subnet microprocessor, and a cellular network interface device in communication with the subnet microprocessor, wherein clients of the local area network are each assigned, a subnet IP address, and wherein the cellular network interface device is established as a client of a cellular network that provides a gateway to the WAN and is assigned, a cellular IP address by the cellular network;

receiving, by the mobile computing device, from clients of the local area network, a plurality of subnet data packets that have a destination IP address that is not a subnet IP address;

assigning, by the mobile computing device, to each subnet data packet that has a destination IP address that is not a subnet IP address, a first network route that exits the mobile computing device over the cellular network interface device, passes over the cellular network to the WAN gateway and passes over the WAN to the controller IP address;

modifying, by the mobile computing device, each subnet data packet that has a destination IP address that is not a subnet IP address, to form a corresponding exit data packet, wherein the corresponding exit data packet comprises the subnet data packet encapsulated by a tunnel IP header wherein the tunnel IP header is configured to route the exit data packet over the first network route;

receiving, by the network controller, the plurality of exit data packets over the one or more WAN interface devices;

removing, by the network controller, the tunnel IP header from each exit data packet to reveal the corresponding subnet data packet;

forming, by the network controller, a WAN data packet corresponding with the subnet data packet by encapsulating the subnet data packet with a WAN IP header

wherein the WAN IP header is configured to route the WAN data packet to the destination IP address of the subnet data packet and to generate a reply data packet responsive to the WAN data packet that is routed back to the network controller over the one or more WAN interface devices.