US 12,231,328 B2
Standby access gateway function signaling for a dynamic host configuration protocol
Venkatesh Padebettu, Bangalore (IN); and Kiran Kumar K, Bangalore (IN)
Assigned to Juniper Networks, Inc., Sunnyvale, CA (US)
Filed by Juniper Networks, Inc., Sunnyvale, CA (US)
Filed on Apr. 14, 2022, as Appl. No. 17/659,186.
Prior Publication US 2023/0336467 A1, Oct. 19, 2023
Int. Cl. H04L 45/24 (2022.01); H04L 45/247 (2022.01); H04L 45/42 (2022.01); H04L 45/586 (2022.01); H04L 61/5014 (2022.01)
CPC H04L 45/42 (2013.01) [H04L 45/24 (2013.01); H04L 45/247 (2022.05); H04L 45/586 (2013.01); H04L 61/5014 (2022.05)] 13 Claims
OG exemplary drawing
 
1. A method, comprising:
communicating, by a first access gateway function (AGF) device, with a first core network device to establish a network connection with a core network;
receiving, by the first AGF device and from a second AGF device, a communication indicating at least one of a subscriber identity, session information, subscriber context, or session transport information associated with an active session between the second AGF device and a dynamic host configuration protocol (DHCP) client device;
detecting, by the first AGF device, that the second AGF device is associated with a failure for the active session between the second AGF device and the DHCP client device;
transmitting, by the first AGF device and to the first core network device, a request to switch a first path associated with the active session from the second AGF device to the first AGF device, wherein the request indicates at least one of the subscriber identity, the session information, the subscriber context, or the session transport information;
receiving, by the first AGF device and from the first core network device, an indication of information associated with a second path between a second core network device and the first AGF device for the active session associated with the DHCP client device; and
forwarding, by the first AGF device, one or more data communications between the second core network device and the DHCP client device associated with the active session via the second path.