View source for Arrcus Inc. (20240283770). High Availability Network Address Translation simplified abstract

=High Availability Network Address Translation=


==Organization Name==

[[:Category:Arrcus Inc.|Arrcus Inc.]]


[[Category:Arrcus Inc.]]

==Inventor(s)==

[[:Category:Keyur Patel of San Jose CA (US)|Keyur Patel of San Jose CA (US)]][[Category:Keyur Patel of San Jose CA (US)]]

[[:Category:Sujay Gopinathan of Fremont CA (US)|Sujay Gopinathan of Fremont CA (US)]][[Category:Sujay Gopinathan of Fremont CA (US)]]

[[:Category:Sreekanth Kannan of Fremont CA (US)|Sreekanth Kannan of Fremont CA (US)]][[Category:Sreekanth Kannan of Fremont CA (US)]]

[[:Category:Arthi Ayyangar of Los Altos CA (US)|Arthi Ayyangar of Los Altos CA (US)]][[Category:Arthi Ayyangar of Los Altos CA (US)]]

==High Availability Network Address Translation - A simplified explanation of the abstract==


This abstract first appeared for US patent application 20240283770 titled 'High Availability Network Address Translation

==Simplified Explanation==
In a computing environment, such as a cloud computing environment, nodes perform network address translation (NAT) for multiple workloads. An active node handles NAT for the workloads, maintains a NAT table, creates sub-interfaces, and functions as a DHCP server. The NAT table and sub-interfaces are duplicated on a standby node to ensure continuity in case of failure.

* Nodes in a computing environment perform NAT for multiple workloads.
* An active node manages NAT, maintains a NAT table, creates sub-interfaces, and acts as a DHCP server.
* Standby node duplicates the NAT table and sub-interfaces for failover.
* Routing table is updated upon failure to direct workloads to the standby node.
* Traffic can continue to be processed by the standby node without disrupting network or application sessions.

==Key Features and Innovation==
* Active node performs NAT for workloads and maintains a NAT table.
* Creation of sub-interfaces and functioning as a DHCP server.
* Standby node replicates NAT table and sub-interfaces for failover.
* Seamless transition of workloads to standby node upon failure.
* Continuous processing of traffic without disrupting network or application sessions.

==Potential Applications==
This technology can be applied in:
* Cloud computing environments
* Data centers
* Network infrastructure management

==Problems Solved==
* Ensures continuity of network and application sessions in case of node failure.
* Efficient management of NAT for multiple workloads.
* Seamless failover process without disruption.

==Benefits==
* Improved reliability and availability of network services.
* Enhanced network performance and efficiency.
* Simplified management of NAT and DHCP services.

==Commercial Applications==
* This technology can be utilized by cloud service providers to enhance the reliability of their services.
* Data centers can benefit from the seamless failover capabilities to ensure uninterrupted operations.
* Network infrastructure companies can improve the efficiency of their services by implementing this technology.

==Questions about the Technology==
===How does this technology improve network reliability?===
This technology ensures continuity of network and application sessions by seamlessly transitioning workloads to a standby node in case of failure.

===What are the potential applications of this technology beyond cloud computing environments?===
This technology can also be applied in data centers and network infrastructure management to enhance reliability and efficiency.


==Original Abstract Submitted==

a computing environment, such as a cloud computing environment, may include nodes performing nat for a plurality of workloads. an active node performs nat for the workloads, including maintaining a nat table. the active node may create sub-interfaces for the workloads and function as a dhcp server. the nat table and sub-interfaces may be recreated on a standby node. upon detecting failure, a routing table is updated to direct workloads to connect to the standby node and traffic may continue to be processed by the standby node without disrupting network or application sessions.



[[Category:H04L61/2567]]
[[Category:H04L12/46]]
[[Category:H04L41/0816]]
[[Category:H04L67/1008]]
[[Category:H04L67/1034]]
[[Category:H04L101/622]]
[[Category:CPC_H04L61/2567]]