A method and apparatus for session management. The method at a control plane function comprises determining data to be restored in a user plane function or a first Internet Protocol (IP) address pool identifier. The method further comprises sending a first session establishment request to the user plane function, wherein the first session establishment request includes a data restoration flag and the data to be restored in the user plane function or includes the first Internet Protocol address pool identifier. The first Internet Protocol address pool identifier is used by the user plane function to assign an IP address to a user equipment from the first Internet Protocol address pool identifier.

A method and apparatus for session management. The method at a control plane function comprises determining data to be restored in a user plane function or a first Internet Protocol (IP) address pool identifier. The method further comprises sending a first session establishment request to the user plane function, wherein the first session establishment request includes a data restoration flag and the data to be restored in the user plane function or includes the first Internet Protocol address pool identifier. The first Internet Protocol address pool identifier is used by the user plane function to assign an IP address to a user equipment from the first Internet Protocol address pool identifier.

A communication apparatus includes a processor and a memory. The processor executes computer-readable instructions stored in the memory. The instructions instruct the communication apparatus to establish a first network including the communication apparatus and a first device. The instructions instruct the communication apparatus to establish a second network including the communication apparatus and a second device. The instructions instruct the communication apparatus to determine a target IP address. Determining the target IP address includes identifying a particular IP address, which is an IP address of the communication apparatus used in the second type network. Determining the target IP address includes generating the target IP address to be within a particular range using the particular IP address. The particular range is a range of IP addresses that are not available in the second type network. The instructions instruct the communication apparatus to assign the target IP address to the first device.

A system and a method of establishing seamless remote access VPN connections are described. For establishment of a VPN connection for a user device, a cluster leader of a cluster of controllers identifies an active controller and a standby controller, based on network load of each controller of the cluster of controllers. An active VPN connection is established between the user device and the active controller and a standby VPN connection is established between the user device and the standby controller. The standby VPN connection is utilized in place of the active VPN connection during failover of the active controller. Because information of an active session is regularly shared by the active controller to the standby controller, the standby controller can seamlessly resume the active session during failover of the active controller.

A communication method includes a first IAB node receives a first message from a CU of an IAB donor, where the first message indicates the first IAB node to be handed over from a first parent node to a second parent node, and the first message includes a first IP address of the first IAB node. The first IAB node determines first transport network layer association information between the first IAB node and the CU of the IAB donor based on the first IP address. The first IAB node updates control plane context information of an F1 interface by using the first transport network layer association information, where the F1 interface is an interface between the first IAB node and CU of the IAB donor. An IAB node communicates with a CU of an IAB donor by using a first IP address as soon as possible after handover is completed.

Disclosed are various embodiments for distributed network address allocation management. In one embodiment, a first instance of a plurality of instances of an allocation management service assigns a first portion of a network address space to the first instance and a second portion of the network address space to a second instance of the plurality of instances. The second instance receives a request to allocate a particular network address block. The second instance allocates the particular network address block from the second portion of the network address space by updating an allocation data structure. An allocation of the particular network address block is returned in response to the request. A copy of the allocation data structure maintained by the first instance is updated asynchronously based at least in part on the allocation of the particular network address block.

Disclosed are various embodiments for distributed network address allocation management. In one embodiment, a first instance of a plurality of instances of an allocation management service assigns a first portion of a network address space to the first instance and a second portion of the network address space to a second instance of the plurality of instances. The second instance receives a request to allocate a particular network address block. The second instance allocates the particular network address block from the second portion of the network address space by updating an allocation data structure. An allocation of the particular network address block is returned in response to the request. A copy of the allocation data structure maintained by the first instance is updated asynchronously based at least in part on the allocation of the particular network address block.

A first device may establish a connection with a second device, and may provide a connection check RPC message to the second device. The first device may receive a verification RPC message from the second device, and may provide, to the second device, a sync domains RPC request that includes a first list of active domains with associated address pools. The first device may receive, from the second device, a sync domains RPC response that includes threshold values for the active domains included in the first list of active domains, and may provide, to the second device, a sync pools RPC request that includes a first list of address pools associated with the active domains. The first device may receive, from the second device, a sync pools RPC response that includes confirmation of the first list of address pools, and may allocate addresses of an address pool to a CPE.

A first device may establish a connection with a second device, and may provide a connection check RPC message to the second device. The first device may receive a verification RPC message from the second device, and may provide, to the second device, a sync domains RPC request that includes a first list of active domains with associated address pools. The first device may receive, from the second device, a sync domains RPC response that includes threshold values for the active domains included in the first list of active domains, and may provide, to the second device, a sync pools RPC request that includes a first list of address pools associated with the active domains. The first device may receive, from the second device, a sync pools RPC response that includes confirmation of the first list of address pools, and may allocate addresses of an address pool to a CPE.

A low number of available IP addresses is detected in an IP pool that available for lease from the DHCP server. A neighbor table from a gateway device behind a firewall that blocks ICMP echo requests from the DHCP server. The gateway device is triggered to broadcast an ARP request to network devices of the neighbor table behind the firewall to determine whether a specific IP address is in use. Responsive to an ARP response not being received, the control module releasing a lease for the specific IP thereby returning to the IP pool available for lease in the DHCP server.