H04L67/1027

NAT-BASED TRAFFIC STEERING

Techniques for NAT-based steering of traffic in cloud-based networks. The techniques may include establishing, by a frontend node of a network, a connection with a client device. The frontend node may receive, via the connection, a packet including an indication of an identity of a service hosted on a backend node of the network. Based at least in part on the indication, the frontend node may establish a second connection with the backend node. Additionally, the frontend node may store a mapping indicating that packets received from the client device are to be sent to the backend node. The techniques may also include receiving another packet at the frontend node or another frontend node of the network. Based at least in part on the mapping, the frontend node or other frontend node may alter one or more network addresses of the other packet and forward it to the backend node.

METHOD AND APPARATUS FOR ENHANCED CLIENT PERSISTENCE IN MULTI-SITE GSLB DEPLOYMENTS

Some embodiments provide a method that, at a first domain name system (DNS) cluster of a set of DNS clusters, receives a DNS request from a client. The first DNS cluster identifies, based on an identifier of the client in the DNS request, a home DNS cluster of the client. The method forwards the DNS request to the home DNS cluster. The home DNS cluster supplies a DNS response to the client. Identifying the home DNS cluster, in some embodiments, includes performing a hash on the identifier of the client. Supplying the DNS response, in some embodiments, includes receiving a virtual IP (VIP) address associated with one of a plurality of sets of application servers to the client and providing the received VIP address to the client in the DNS response.

Load balancing communication sessions in a networked computing environment

Techniques for load balancing communication sessions in a networked computing environment are described herein. The techniques may include establishing a first communication session between a client device and a first computing resource of a networked computing environment. Additionally, the techniques may include storing, in a data store, data indicating that the first communication session is associated with the first computing resource. The techniques may further include receiving, at a second computing resource of the networked computing environment, traffic associated with a second communication session that was sent by the client device, and based at least in part on accessing the data stored in the data store, establishing a traffic redirect such that the traffic and additional traffic associated with the second communication session is sent from the second computing resource to the first computing resource.

Load balancing communication sessions in a networked computing environment

Techniques for load balancing communication sessions in a networked computing environment are described herein. The techniques may include establishing a first communication session between a client device and a first computing resource of a networked computing environment. Additionally, the techniques may include storing, in a data store, data indicating that the first communication session is associated with the first computing resource. The techniques may further include receiving, at a second computing resource of the networked computing environment, traffic associated with a second communication session that was sent by the client device, and based at least in part on accessing the data stored in the data store, establishing a traffic redirect such that the traffic and additional traffic associated with the second communication session is sent from the second computing resource to the first computing resource.

Methods, systems, and computer-readable media for distributing S1 connections to mobility management entities (MMEs) and N2 connections to access and mobility management functions (AMFs)
11576072 · 2023-02-07 · ·

A method for distributing connections to mobility management node instances includes publishing IP addresses for receiving connection requests and ingress messages from RAN nodes. The method further includes maintaining connection loading measurements of the mobility management node instances, receiving a connection request message generated by a RAN node for initiating a connection with one of the mobility management node instances, applying a connection distribution algorithm to select a mobility management node instance to handle the connection request message, and creating an association between an IP address of the selected mobility management node instance and an IP address and port of the RAN node extracted from a source IP address and source port field of the connection request. The method further includes forwarding the connection request message to the selected mobility management node instance.

In-packet version tagging utilizing a perimeter NAT

Various embodiments are directed to receiving, at a receiving device, a packet from a node in a first network. determining a version identifier for the packet, encoding the version identifier into the packet, and transmitting the packet containing the encoded version identifier to a load balancing device in a second network. The version identifier may be encoded into a destination port field of the packet. The receiving device may be a perimeter network address translation device. The packet is received at the load balancing device, where the version identifier is extracted and a hash of source address information is performed. The version and hash are used to select a back-end device in the second network. The packet is transmitted to the selected back-end device.

Link quality measurements and link status detection

A network device may include a processor. The processor is configured to: receive a network address of a load balancer device from a management device; send a test request to the load balancer device based on the received network address; obtain a network address of a data collector device from the load balancer device; and perform a test with the data collector device. The data collector device is configured to: obtain a result of the test; and send the result to a data lake.

Link quality measurements and link status detection

A network device may include a processor. The processor is configured to: receive a network address of a load balancer device from a management device; send a test request to the load balancer device based on the received network address; obtain a network address of a data collector device from the load balancer device; and perform a test with the data collector device. The data collector device is configured to: obtain a result of the test; and send the result to a data lake.

Policy-based forwarding to a load balancer of a load balancing cluster

Some embodiments of the invention provide a method for forwarding data messages between a client and a server (e.g., between client and server machines and/or applications). In some embodiments, the method receives a data message that a load balancer has directed from a particular client to a particular server after selecting the particular server from a set of several candidate servers for the received data message's flow. The method stores an association between an identifier associated with the load balancer and a flow identifier associated with the message flow, and then forwards the received data message to the particular server. The method subsequently uses the load balancer identifier in the stored association to forward to the particular load balancer a data message that is sent by the particular server. The method of some embodiments is implemented by an intervening forwarding element (e.g., a router) between the load balancer set and the server set.

PFCP Session Load Balancer
20220345519 · 2022-10-27 ·

Importing of a UE address into a VRF of perimeter equipment is facilitate by receiving a VPN update from the perimeter equipment including a route target of the perimeter equipment and a gNodeB address. In addition, session information is obtained by intercepting traffic between the UE address and a UPF. The session information including the UE address and address of a gNodeB to which the UE is connected. By matching the gNodeB addresses from the VPN update and the session information, the route target of the perimeter equipment to which the UE is connected may be determined. The UE address may then be imported exclusively into the VRF of the perimeter equipment.