A load balancing system based on nat64 prefixes for ipv4 terminals and ipv6 service interworking business

Abstract

The invention discloses a load balancing system for IPv4 terminals based on NAT64 prefixes and IPv6 service interworking services, including a NAT64 traffic load balancing system and a DNS64 server. The NAT64 traffic load balancing system is equipped with a load balancing module and a NAT64 module. The NAT64 traffic load The balance system is respectively connected to the IPv4 network and the IPv6 network. The IPv6 network accesses the Web server through the domain name, and the IPv6 network is also connected to the DNS64 server. The present invention can overcome the problem of slow service when the load of the NAT64 device is too large, and can match the configured NAT64 IPv6 prefix for the destination address. IPv6 packets are load balanced.

Description

technical field [0001] The invention relates to the technical field of load balancing, in particular to a load balancing system for IPv4 terminals and IPv6 service interworking services based on NAT64 prefixes. Background technique [0002] In recent years, the Internet is in the transition period from IPv4 to IPv6. At present, most of the content on the Internet is only available on IPv4. Therefore, there is a real demand for IPv6 terminals to access IPv4 resources. Stateful NAT64+DNS64 technology can provide IPv6 end users with the ability to access IPv4 content without changing the user terminal and server. It is currently an important IPv4 / IPv6 dual-stack interworking technology. [0003] Generally, a single NAT64 device can meet the functional requirements of the above-mentioned business applications. However, in the deployment scenarios of operators and large business loads, there are many user connection requests and a large amount of data transmission, and a single N...

AI Technical Summary

Problems solved by technology

[0006] The traditional load balancing system can only perform load balancing for specific unicast IPv6 / IPv4 addresses, and cannot perform load balancing for IPv6 data packets matching IPv6 address prefixes such as NAT64 addresses; the traditional load balancing system requires a separate load balancing device, and the load balancing device It becomes the performance bottleneck of cluster servers and is not suitable for super-large cluster servers; traditional load balancing systems require redundant backup load balancing devices, which do not participate in business processing, which increases system investment and is not suitable for small cluster servers

Images