Method for communication, first agf device, and non-transitory computer readable medium

Abstract

The present disclosure relates to dynamic host configuration protocol alternate access gateway function signaling. In some implementations, a first access gateway function (AGF) can receive, from a second AGF, a communication indicating at least one of: a subscriber identity, session information, a subscriber context, or session transport information associated with an active session between the second AGF and a client device. The first AGF device can detect that the second AGF device is associated with a failure. The first AGF device can send, to a 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, where the request indicates at least one of the subscriber identity, the session information, the subscriber context, or the session transport information. The first AGF device can forward, via a second path, one or more data communications between the second core network device and the DHCP client device associated with the active session.

Description

Technical Field

[0001] This disclosure relates generally to the field of communications, and more specifically to methods for communications, a first access gateway function (AGF) device, and a non-transitory computer-readable medium. Background Technology

[0002] Dynamic Host Configuration Protocol (DHCP) is a network management protocol used on Internet Protocol (IP) networks to assign IP addresses and other communication parameters to devices connected to the network using a client-server architecture. A DHCP server is a network server that automatically provides and assigns IP addresses, default gateways, and other network parameters to client devices. In some cases, the network's Access Gateway Function (AGF) can act as a DHCP relay between client devices and the DHCP server. Summary of the Invention

[0003] Some implementations described herein relate to a method. This method may include communicating with a first core network device via a first Access Gateway Function (AGF) device to establish a network connection to the core network. This method may include receiving, by the first AGF device and from a second AGF device, communication indicating at least one of the following: 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. This method may include the first AGF device detecting a failure association between the second AGF device and the active session between the second AGF device and the DHCP client device. This method may include the first AGF device sending a request to the first core network device 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 following: subscriber identity, session information, subscriber context, or session transport information. This method may include receiving, by the first AGF device and from the first core network device, an indication of information associated with a second path between the second core network device and the first AGF device for an active session associated with a DHCP client device. The method may include forwarding one or more data communications between a first AGF device and a second core network device and a DHCP client device associated with an active session via a second path.

[0004] Some implementations described herein relate to a first access gateway function (AGF) device. The first access gateway function (AGF) device may include one or more memories and one or more processors. One or more processors may be configured to establish a network connection with the core network and a control plane core network device. One or more processors may be configured to establish a Protocol Data Unit (PDU) session associated with a client device via Dynamic Host Configuration Protocol (DHCP) with the control plane core network device, wherein the PDU session is associated with at least one of the following: subscriber identity, session information, subscriber context, or session transport information associated with the client device. One or more processors may be configured to forward one or more data communications associated with the PDU session between the client device and the user plane core network device. One or more processors may be configured to send a lease query communication to a second AGF device indicating at least one of the subscriber identity, session information, subscriber context, or session transport information associated with the PDU session, so that the second AGF device can maintain the PDU session with the client device.

[0005] Some implementations described herein relate to a non-transitory computer-readable medium storing a set of instructions for a first access gateway function (AGF) device. When executed by one or more processors of the first AGF device, the set of instructions enables the first AGF device to communicate with a control plane core network device to establish a network connection with the core network. When executed by one or more processors of the first AGF device, the set of instructions enables the first AGF device to receive a lease query communication from a second AGF device indicating at least one of a subscriber identity, session information, subscriber context, or session transport information associated with a Protocol Data Unit (PDU) session between the second AGF device and a client device. When executed by one or more processors of the first AGF device, the set of instructions enables the first AGF device to detect that the second AGF device has experienced a failure associated with a PDU session. When executed by one or more processors of the first AGF device, the set of instructions enables the first AGF device to send a request to the control plane core network device to switch the PDU session from the second AGF device to the first AGF device, wherein the request indicates at least one of the following: subscriber identity, session information, subscriber context, or session transport information. When executed by one or more processors of the first AGF device, this set of instructions enables the first AGF device to receive instructions from the control plane core network device regarding information associated with the path between the user plane core network device and the first AGF device for a PDU session associated with a client device. When executed by one or more processors of the first AGF device, this set of instructions enables the first AGF device to forward one or more data communications between the user plane core network device and the client device associated with the PDU session via the path. Attached Figure Description

[0006] Figure 1A-1C This is a schematic diagram of the example implementation described in this article.

[0007] Figure 2 This is a schematic diagram of an example environment in which the systems and / or methods described herein can be implemented.

[0008] Figure 3 This is a schematic diagram of the example implementation described in this article.

[0009] Figure 4 and 5 yes Figure 2 A schematic diagram of an example component of one or more devices.

[0010] Figure 6 and 7 This is a flowchart of an example process related to Alternate Access Gateway (AGF) signaling for Dynamic Host Configuration Protocol (DHCP). Detailed Implementation

[0011] The following example implementation is described in detail with reference to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.

[0012] Dynamic Host Configuration Protocol (DHCP) relays can forward communication between client devices and DHCP servers. For example, in some deployments, an Access Gateway Function (AGF) device can be or act as a DHCP relay. An AGF device can provide client devices with access to a wireless core network (e.g., a 5G core network). For example, an AGF device can provide connectivity to the wireless core network for client devices supporting Non-Access Stratum (NAS) signaling and wired-only client devices (e.g., information transfer occurs over physical components such as fiber optic cables, coaxial cables, twisted-pair cables, etc.). In such an example, the DHCP server can be a User Plane Function (UPF) device associated with the wireless core network and / or a Session Management Function (SMF) device associated with the wireless core network. The AGF device can forward DHCP communication (e.g., establishing active sessions) and / or data packets (e.g., associated with active sessions) between client devices and the UPF device to facilitate client connections to a wireless network (e.g., a 5G network).

[0013] However, in some cases, the AGF device, acting as a DHCP relay for client devices, may fail. For example, the connection between the AGF device and the client device (e.g., between the AGF device and the access network associated with the client device) and / or the AGF device itself may experience failures (e.g., software and / or hardware failures). In some cases, the detection of failures associated with the AGF device may be associated with significant delays or waiting times (e.g., because detection may be based on a DHCP update procedure that may require the client device to send a DHCP request to the AGF device so that the client device can detect that the connection with the AGF device has failed).

[0014] Furthermore, in some cases, a second AGF device (e.g., a backup AGF device) can be used as a DHCP relay for client devices. However, to establish a connection with the second AGF device, the active session associated with the client device and the first AGF device may be terminated, and the client device may need to establish a new session with the second AGF device. In other words, to switch the connection to the second AGF device after a failure associated with the first AGF device, a new DHCP setup procedure and / or a new Protocol Data Unit (PDU) session setup procedure may need to be performed to establish a connection between the client device and the wireless network. This consumes significant network resources associated with exchanging multiple messages between the client device and the second AGF device, between the second AGF device and one or more core network devices, and / or between different core network devices associated with establishing a new session with the client device. Moreover, because the previous session associated with the client device is terminated, information associated with the previous session may be lost. For example, a new session with the second AGF device may be associated with a new Internet Protocol (IP) address and / or other network parameters or identifiers different from those of the previous session. Additionally, establishing a new session associated with the second AGF device may be associated with significant delays related to the signaling required to establish the new session. As a result, client devices may be unable to access the wireless network during the latency period, leading to a performance degradation associated with the client devices.

[0015] Some implementations described herein enable standby AGF signaling for DHCP to enable client devices to switch from a first AGF device to a second AGF device without terminating the PDU session associated with the client device and / or without establishing a new DHCP connection and / or PDU session. For example, the first AGF device can act as a DHCP relay for the client device (e.g., it may be the active AGF device). The second AGF device can be a standby AGF device. The first AGF device can send communications (e.g., lease query communications) indicating subscriber identity, session information, subscriber context, and / or session transport information associated with the active session between the first AGF device and the client device, and the second AGF device can receive such communications (e.g., lease query communications), among other examples. In other words, the first AGF device can provide information to the second AGF device to enable the second AGF device to instruct the core network (e.g., to control plane core network devices) to switch the connection of the core network UPF to the client device from the first AGF device to the second AGF device. For example, information (e.g., subscriber identity, session information, and / or session transmission information) can enable the second AGF device to identify and instruct (e.g., to the core network) the client device and / or transmission information associated with the client device's active session. For example, this information could be generated by the first AGF device and / or provided by the core network to the first AGF device for establishing an active session associated with the client device.

[0016] By providing such information to a second AGF device (e.g., a backup AGF device), the second AGF device can be able to send a message to the core network indicating that, upon detecting a fault associated with the first AGF device, a first path associated with an active session of a client device will be switched from the first AGF device to the second AGF device. The core network can modify the session information associated with the active session to switch the path to the second AGF device.

[0017] As a result, the signaling required to establish (e.g., re-establish) a connection between a client device and the second AGF device after a failure associated with the first AGF device can be significantly reduced, thereby saving network and / or processing resources that would otherwise be used to establish new DHCP sessions and / or new PDU sessions associated with the client device. Therefore, active sessions associated with the client device can be maintained, and the client device may be minimally affected (e.g., in terms of data rate or data connectivity) by the failure of the first AGF device. Furthermore, the latency associated with switching the connection or connection path used by the client device to the wireless network from the first AGF device to the second AGF device can be reduced. Additionally, the second AGF device can be enabled to quickly detect (e.g., compared to detecting a faulty client device) the failure associated with the first AGF device based on signaling exchanged between the first and second AGF devices (e.g., bidirectional forwarding detection (BFD) signaling or other signaling).

[0018] Figure 1A-1C This is a schematic diagram of an example implementation 100 associated with alternative AGF signaling for DHCP. For example... Figure 1A-1C As shown, example implementation 100 includes client device 105, active AGF 110 (e.g., active AGF device), standby AGF 115 (e.g., standby AGF device), one or more control plane core network (CN) devices 120 and UPF 125. The following is in conjunction with... Figure 2 , 4 Sections 5 and 6 describe these devices in more detail. Although Figure 1A-1C Not shown, but the active AGF 110 and standby AGF 115 can be connected to client device 105 via the access network (AN). As described in more detail elsewhere herein, UPF 125 can be used as a DHCP server for client device 105. In some other implementations, SMF ( Figure 1A-1C (Not shown in the text) can act as a DHCP server in a similar manner to that described herein.

[0019] As used herein, “active” and “standby” when used in conjunction with a particular AGF refer to the connection state with client device 105 (e.g., rather than the operational state, configuration, or capabilities of the particular AGF). For example, active AGF 110 and standby AGF 115 may be similar devices and / or may be able to perform similar or the same functions (e.g., standby AGF 115 may be able to perform the operations or functions described herein related to active AGF 110 and active AGF 110 may be able to perform the operations or functions described herein related to standby AGF 115).

[0020] The active AGF 110 and the standby AGF 115 can be DHCP relays used to relay communication between client device 105 and UPF 125 (e.g., UPF 125 can provide access to a data network of the wireless network associated with UPF 125). For example, client device 105 can be any device capable of communicating via DHCP. DHCP can be associated with IP version 4 (IPv4), which can be referred to as DHCPv4, or it can be associated with IP version 6 (IPv6), which can be referred to as DHCPv6, or it can be associated with another version of DHCP.

[0021] The active AGF 110 and standby AGF 115 can be deployed between the wired access infrastructure and the wireless core network. Therefore, the active AGF 110 and standby AGF 115 can support client devices 105 that support or include NAS signaling (such as residential gateways or other client devices) and client devices 105 that are purely wired devices. This enables the wireless core network to provide services typically associated with wired networks.

[0022] As shown by reference numeral 130 in the accompanying drawings, the active AGF 110 can communicate with one or more control plane core network devices 120 to establish a connection with the core network. For example, the active AGF 110 can exchange one or more messages with the access and mobility functions (AMF) of the core network to establish a connection with the core network. Similarly, as shown by reference numeral 135 in the accompanying drawings, the standby AGF 115 can communicate with one or more control plane core network devices 120 to establish a connection with the core network. For example, the standby AGF 115 can exchange one or more messages with the AMF of the core network to establish a connection with the core network.

[0023] For example, the active AGF 110 and the standby AGF 115 can perform N2 interface setup (e.g., as defined by standards such as the Broadband Forum (BBF) and / or the 3rd Generation Partnership Project (3GPP)). The N2 interface can be an interface between the core network's control plane and the active AGF 110 or the standby AGF 115 (e.g., between AMFs of the core network). For example, the active AGF 110 and the standby AGF 115 can establish an N2 interface that connects them to the core network's AMF, thereby enabling them to access control plane services associated with the core network. This allows the active AGF 110 and the standby AGF 115 to exchange control signaling with the core network (e.g., via AMF).

[0024] As shown by reference numeral 140 in the attached figure, client device 105 may send a DHCP message requesting the initiation of a DHCP session, and active AGF 110 may receive this message. The DHCP message may be a DHCP session establishment request. For example, client device 105 may send a request to establish a DHCP session with a DHCP server (e.g., UPF 125). In some implementations, the DHCP request may be forwarded to active AGF 110 via AN. In some implementations, the DHCP request may include DHCP discovery messages or data packets (e.g., DHCP discovery queries) and / or DHCP solicitation messages or data packets.

[0025] Based on a received DHCP request, the active AGF 110 can establish a PDU session associated with client device 105. In some implementations, the active AGF 110 can generate NAS information associated with the PDU session and / or client device 105. For example, the active AGF 110 can generate subscriber identity and / or session information associated with the PDU session and / or client device 105. The information generated by the active AGF 110 may include a Subscriber Unique Permanent Identifier (SUPI) associated with client device 105 and the session, a Subscriber Unique Hidden Identifier (SUCI) associated with client device 105 and the session, a Globally Unique Temporary Identifier (GUTI) associated with client device 105 and the session, and / or a PDU session identifier, among other examples. The information generated by the active AGF 110 may be information associated with the N1 interface (e.g., as defined by BBF and / or 3GPP). For example, the N1 interface may be an interface associated with transmitting information associated with client device 105 to one or more control plane core network devices 120 (e.g., to the AMF of the core network).

[0026] As shown by reference numeral 145 in the accompanying drawings, the active AGF 110 and one or more control plane core network devices 120 (e.g., AMF) can exchange one or more messages to establish a PDU session associated with client device 105. For example, the active AGF 110 can send a PDU session establishment request to the control plane core network device 120 (e.g., AMF). The PDU session establishment request can indicate information generated by the active AGF 110. One or more control plane core network devices 120 can establish a PDU session based on the information provided by the active AGF 110. For example, the AMF can generate session transport information indicating the path or tunnel used by the active AGF 110 to communicate with the UPF 125. For example, the AMF can generate Next Generation Application Protocol (NGAP) information associated with the PDU session. The information generated by the AMF may include a globally unique AMF identifier (GUAMI) associated with the PDU session, an AMF user equipment (UE) NGAP identifier associated with the PDU session, a radio access network (RAN) UE NGAP identifier associated with the PDU session, and / or UE context information associated with the PDU session, among other examples. The control plane core network device 120 (e.g., the AMF) may send instructions to the active AGF 110 regarding the information generated by the AMF. The active AGF 110 may use this information to communicate with the UPF 125 and / or forward communication between the UPF 125 and the client device 105.

[0027] Based on establishing a PDU session, client device 105 and UPF 125 can exchange one or more communications to establish a DHCP session. For example, establishing a PDU session enables active AGF 110 to establish a connection (e.g., a path or tunnel) associated with UPF 125 (e.g., for forwarding communication between UPF 125 and client device 105). For example, UPF 125 can send a DHCP Offer message or DHCP Advertise message indicating that UPF 125 is available as a DHCP server. Active AGF 110 can forward the DHCP Offer message or DHCP Advertise message to client device 105. Client device 105 can send a DHCP Request message in response to the DHCP Offer message or DHCP Advertise message, thereby requesting network configuration data, such as IP addresses, and other examples. For example, client device 105 can select UPF 125 as the DHCP server associated with client device 105. Based on the selection of UPF 125 as the DHCP server, the client device can request network configuration from UPF 125 (e.g., via a DHCP Request message). Client device 105 can broadcast the DHCP Request message. The DHCP request message may include the IP address associated with UPF 125 (e.g., indicating that UPF 125 has been selected as the DHCP server for client device 105). Active AGF 110 may forward the DHCP request message to UPF 125.

[0028] Based on the received DHCP request message, one or more control plane CN devices 120 can generate network configuration information for client device 105. For example, one or more control plane CN devices 120 can generate IP addresses, subnet masks, default gateway IP addresses, Domain Name System (DNS) server IP addresses, and / or lease times (e.g., the amount of time the network configuration information is valid), and other examples. The network configuration information associated with the DHCP session may be referred to herein as “binding information.” One or more control plane CN devices 120 can provide the generated network configuration information for client device 105 to UPF 125. UPF 125 can send a DHCP acknowledgment (ACK) message indicating the network configuration information for client device 105. Active AGF 110 can forward the DHCP ACK message to client device 105. Client device 105 can receive and store the network configuration information. As a result, client device 105 can establish a connection to the data network associated with UPF 125.

[0029] For example, as shown by reference numeral 150, the active AGF 110 can forward one or more data communications (e.g., one or more data packets) associated with a PDU session and / or DHCP session between the client device 105 and the UPF 125. The UPF 125 can forward one or more data communications to the data network.

[0030] like Figure 1B As shown, the active AGF 110 and the standby AGF 115 can exchange one or more messages associated with an active session of the client device 105. For example, as indicated by reference numeral 155, the active AGF 110 can send and the standby AGF 115 can receive communications indicating subscriber identity, session information, and / or session transport information associated with an active session (e.g., a PDU session and / or a DHCP session) between the active AGF 110 and the client device 105. This communication can be lease query communications, such as active lease query (ALQ) communications, bulk lease query (BLQ) communications, and / or individual lease query communications, among other examples.

[0031] For example, the active AGF 110 and the standby AGF 115 can establish a Transmission Control Protocol (TCP) connection to exchange communications. In some implementations, the standby AGF 115 can send, and the active AGF 110 can receive, lease query requests (e.g., BLQ requests or ALQ requests) to request binding information (e.g., network configuration information) associated with one or more client devices, such as client device 105. The active AGF 110 can send, and the standby AGF 115 can receive, lease query communications indicating binding information associated with client device 105 (e.g., and one or more other client devices). For example, binding information may include an identifier associated with client device 105, a server identifier (e.g., a relay identifier) ​​associated with active AGF 110 (e.g., a relay identifier based on a Link Aggregation Control Protocol (LCAP) MAC address), an IP address associated with client device 105, a lease time associated with a DHCP session, a subnet mask, a DHCP client time associated with a DHCP session, a DHCP base time associated with a DHCP session, and / or an interface identifier associated with a DHCP session, and other examples.

[0032] Furthermore, communications sent from the active AGF 110 to the standby AGF 115 (e.g., lease query communications) may include information enabling the standby AGF 115 to switch a path (e.g., a path between a DHCP relay and a UPF 125) from the active AGF 110 to the standby AGF 115 in the event of a failure associated with the active AGF 110 (e.g., through communication with one or more control plane core network devices 120). For example, communications (e.g., lease query communications) may include subscriber identity, session information, subscriber context, and / or session transport information associated with an active session (e.g., a PDU session and / or a DHCP session) between the active AGF 110 and the client device 105. For example, communications (e.g., lease query communications) may include NAS information (e.g., generated by the active AGF 110) and / or indications of NGAP information (e.g., provided by one or more control plane core network devices 120, such as an AMF) associated with an active session (e.g., a PDU session and / or a DHCP session) between the active AGF 110 and the client device 105. In some implementations, communications (e.g., lease query communications) may include indications of SUPI, SUCI, GUTI, and / or PDU session identifiers associated with an active session (e.g., a PDU session and / or DHCP session) between the active AGF 110 and client device 105, as shown in other examples. Additionally or alternatively, communications (e.g., lease query communications) may include indications of GUAMI, AMF UE NGAP identifier, RAN UE GAP identifier, and UE context information (e.g., PDU session information associated with a PDU session, and / or General Packet Radio Service (GPRS) Tunneling Protocol (GTP) information associated with a PDU session) associated with an active session (e.g., a PDU session and / or DHCP session) between the active AGF 110 and client device 105, as shown in other examples.

[0033] This information enables the standby AGF 115 to request one or more control plane core network devices 120, such as AMF, to switch the path associated with the active session from the active AGF 110 to the standby AGF 115. For example, the standby AGF 115 may be able to identify the subscriber identity, session information, subscriber context, and / or session transport information associated with the active session, so that the standby AGF 115 can enable the path associated with the active session to be switched to the standby AGF 115, as described in more detail elsewhere herein.

[0034] As shown by reference numeral 160 in the attached figure, the active AGF 110 and the standby AGF 115 may exchange one or more communications to enable the standby AGF 115 to detect faults associated with the active AGF 110. For example, the active AGF 110 and the standby AGF 115 may exchange one or more Virtual Router Redundancy Protocol (VRRP) communications or one or more BFD communications to facilitate the detection of faults associated with the active AGF 110 in connection with the active session. For example, the active AGF 110 and the standby AGF 115 may utilize VRRP to establish one or more redundant routing platforms (e.g., the active AGF 110 and the standby AGF 115 are hosts associated with VRRP). The active AGF 110 (e.g., as the primary host of VRRP) may periodically send data packets to the standby AGF 115 (and / or other hosts) to enable the standby AGF 115 to assess the health status of the active AGF 110.

[0035] As another example, the active AGF 110 and the standby AGF 115 can exchange BFD communications. For instance, the standby AGF 115 can periodically send and the active AGF 110 can receive BFD data packets (e.g., BFD greeting data packets). The active AGF 110 can send and the standby AGF 115 can receive BFD responses indicating that the active AGF 110 is active and has not experienced a failure.

[0036] As indicated by reference numeral 165, the active AGF 110 may experience a failure. For example, a failure could include an event or condition that causes the active AGF 110 to lose connection with client device 105 and / or UPF 125. As indicated by reference numeral 170, the standby AGF 115 can detect a failure associated with or experienced by the active AGF 110 and the active session between the active AGF 110 and client device 105. For example, the standby AGF 115 can monitor for failures associated with the active AGF 110 based on a threshold being met by determining that the amount of time since sending BFD or VRRP communication to the active AGF 110 without receiving a response (e.g., a BFD response data packet or a VRRP response data packet) meets this threshold. For example, VRRP and / or BFD protocols can enable the standby AGF 115 to detect failures associated with the active AGF 110 based on the absence of a reply or response from the active AGF 110 after a specified interval. In other words, the standby AGF 115 can detect that the active AGF 110 has experienced a failure by executing the VRRP and / or BFD procedures through the active AGF 110, among other examples.

[0037] like Figure 1CAs shown, the standby AGF 115 can perform one or more actions to switch the path associated with the active session of client device 105 from the active AGF 110 to the standby AGF 115 (e.g., to enable client device 105 to maintain the active session and connectivity to the data network). For example, as indicated by reference numeral 175, the standby AGF 115 can send a request to one or more control plane core network devices (e.g., to the AMF) to switch the first path associated with the active session from the active AGF 110 to the standby AGF 115. This request can be a path switching request (e.g., an NGAP path switching request), such as a path switching request defined by the BBF and / or 3GPP or otherwise fixed. In some implementations, the request can indicate information provided by the active AGF 110 (e.g., as described in conjunction with reference numeral 155). For example, the request indicates subscriber identity, session information, and / or session transport information associated with the session (e.g., a PDU session and / or DHCP session) between the active AGF 110 and client device 105.

[0038] As indicated by reference numeral 180 in the attached figure, one or more control plane core network devices 120 can modify the path of a PDU session and / or DHCP session to an alternate AGF 115 (e.g., from the active AGF 110). For example, the AMF can request a Session Management Function (SMF) to modify the path based on information provided by the alternate AGF 115 (e.g., in a path switching request). For example, the SMF can communicate with the UPF 125 to modify the path (e.g., tunnel) associated with the PDU session from the active AGF 110 to the alternate AGF 115.

[0039] One or more control plane core network devices 120 (e.g., AMF) can send an indication to the standby AGF 115 that the path has been successfully switched or modified to be associated with the standby AGF 115. As a result, the standby AGF 115 can assume the role of DHCP relay for the DHCP session associated with the client device 105. For example, the standby AGF 115 can apply network configuration associated with the DHCP session and / or other information indicated by the active AGF 110 to enable the standby AGF to act as a DHCP relay. In some implementations, the standby AGF 115 can send, and the client device 105 can receive, an indication of the MAC address associated with the standby AGF 115. For example, the standby AGF 115 can send gratuitous Address Resolution Protocol (ARP) communication or gratuitous neighbor discovery communication indicating the MAC address associated with the standby AGF 115 (e.g., to enable the client device 105 to communicate with the MAC entity associated with the standby AGF 115). In some other implementations, the standby AGF 115 may not send an indication of the MAC address, such as using a virtual MAC entity shared between the standby AGF 115 and the active AGF 110 (e.g., because the client device 105 will have already received the MAC address of the virtual MAC entity from the active AGF 110).

[0040] For example, as shown by reference numeral 185, the standby AGF 115 may forward one or more data communications (e.g., one or more data packets) associated with the active session between UPF 125 and client device 105 via a second path (e.g., a path between standby AGF 115 and UPF 125). For example, the network configuration associated with client device 105 (e.g., IP address, subscriber identifier, session information, and / or session transport information) may not change, but the routing associated with one or more data communications may change, such that the data communications are forwarded to the standby AGF 115 (e.g., instead of the active AGF 110) and forwarded by the standby AGF 115 to UPF 125 or client device 105.

[0041] As a result, the signaling required to establish a connection between client device 105 and backup AGF 115 after a failure associated with active AGF 110 can be significantly reduced, thereby saving network and / or processing resources that would otherwise be used to establish new DHCP and / or new PDU sessions associated with client device 105 and backup AGF 115. Therefore, active sessions associated with client device 105 can be maintained, and client device 105 may be minimally affected (e.g., in terms of data rate or data connectivity) by the failure of active AGF 110. Furthermore, the latency associated with switching the connection or connection path from active AGF 110 to the wireless network from client device 105 to backup AGF 115 can be reduced. Additionally, backup AGF 115 can be enabled to quickly detect (e.g., compared to detecting a failure in client device 105) the failure associated with active AGF 110 based on the signaling exchanged between active AGF 110 and backup AGF 115 (e.g., BFD signaling, VRRP signaling, or other signaling).

[0042] As mentioned above, providing Figure 1A-1C As an example. Other examples can be related to... Figure 1A-1C The descriptions differ. Provided Figure 1A-1C The number and arrangement of the equipment shown are for illustrative purposes only. In reality, with... Figure 1A-1C Compared to those shown, there may be additional equipment, fewer equipment, different equipment, or different arrangements of equipment. Furthermore, Figure 1A-1C The two or more devices shown can be implemented within a single device, or Figure 1A-1C The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, Figure 1A-1C The set of devices shown (e.g., one or more devices) can perform actions described by Figure 1A-1C The other set of devices shown performs one or more functions.

[0043] Figure 2 This is a schematic diagram of an example environment 200 in which the systems and / or methods described herein can be implemented. (See diagram 200 for example.) Figure 2 As shown, example environment 200 may include client device 205, AN 210, first AGF 215, second AGF 220, core network 225, and data network 280. The devices and / or networks of example environment 200 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0044] Client device 205 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information (such as the information described herein). Client device 205 may be, may resemble, or may include client device 105. Client device 205 may include residential gateways, user equipment, network devices (e.g., label switching routers (LSRs), label edge routers (LERs), ingress routers, egress routers, provider routers, virtual routers, gateways, switches, firewalls, hubs, bridges, reverse proxies, proxy servers, cloud servers, data center servers, load balancers, etc.) or similar types of devices. Client device 205 may be any device capable of communicating via DHCP (e.g., may be referred to herein as a DHCP client device). In some implementations, client device 205 may receive network traffic from and / or provide network traffic to core network 225 via AN 210.

[0045] AN 210 may include one or more nodes associated with a wired connection to core network 225. AN 210 may include a central unit (CU) comprising a next-generation (NG) interface connecting the CU to a core unit (e.g., a next-generation core (NGC) unit), which may be a node of core network 225. AN 210 may transmit traffic between client device 205 and core network 225. In some implementations, AN 210 may perform scheduling and / or resource management for client devices 205 covered by AN 210. In some implementations, AN 210 may be controlled or coordinated by a network controller, which may perform load balancing, network-level configuration, etc. The network controller may communicate with AN 210 via wireless or wired backhaul. In some implementations, AN 210 may include a network controller, an ad hoc network (SON) module or component, or a similar module or component. In other words, AN 210 can perform network control, scheduling and / or network management functions (e.g., for uplink, downlink and / or sidelink communication of client device 205 covered by AN 210).

[0046] The first AGF 215 and the second AGF 220 may include one or more devices between the wired access infrastructure (e.g., AN 210) and the core network 225, which support residential gateways that support 5G NAS signaling (e.g., client device 205) and residential gateways that are purely wired (e.g., do not support NAS signaling).

[0047] In some implementations, core network 225 may include example functional architectures in which the systems and / or methods described herein may be implemented. For example, core network 225 may include an example architecture of a 5G NG core network included in a 5G wireless telecommunications system. Although Figure 2 The example architecture of the core network 225 shown can be an example of a service-based architecture, but in some implementations, the core network 225 can be implemented as a reference point architecture.

[0048] like Figure 2 As shown, the core network 225 may include multiple functional elements. These functional elements may include, for example, a Network Slice Selection Function (NSSF) 230, a Network Exposure Function (NEF) 235, a Network Repository Function (NRF) 240, an Authentication Server Function (AUSF) 245, a Unified Data Management (UDM) component 250, a Policy Control Function (PCF) 255, an Application Function (AF) 260, an AMF 265, an SMF 270, and / or a UPF 275, among others. These functional elements may be communicatively connected via a message bus 285. Figure 2 Each functional element shown is implemented on one or more devices associated with a wireless telecommunications system. In some implementations, one or more functional elements may be implemented on physical devices such as access points, base stations, gateways, etc. In some implementations, one or more functional elements may be implemented on computing devices in a cloud computing environment.

[0049] NSSF 230 includes one or more devices that select network slice instances for client device 205. By providing network slices, NSSF 230 allows operators to deploy multiple potentially independent end-to-end networks with the same infrastructure. In some implementations, each slice can be customized for different services. NEF 235 includes one or more devices that support the exposure of capabilities and / or events in the wireless telecommunications system to help other entities in the wireless telecommunications system discover network services. NRF 240 is a central repository of all network functions. NRF 240 can provide a single record of all network functions available in a given network, along with the profile for each and the services supported by the network function.

[0050] AUSF 245 includes one or more devices that act as authentication servers and support the process of authenticating client devices 205 in a wireless telecommunications system. UDM 250 includes one or more devices that store user data and profiles in the wireless telecommunications system. UDM 250 can be used for fixed access, mobile access, etc., in the core network 225. PCF 255 includes one or more devices that provide a policy framework that incorporates network slicing, roaming, packet processing, mobility management, etc. AF 260 includes one or more devices that support the influence of applications on traffic routing, access to NEF 235, policy control, etc.

[0051] AMF 265 includes one or more devices that act as endpoints for NAS signaling, mobility management, etc. SMF 270 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, SMF 270 can configure traffic steering policies at UPF 275, enforce user equipment IP address allocation and policies, etc. One or more control plane core network devices 120 may be or may include NSSF 230, NEF 235, NRF 240, AUSF 245, UDM250, PCF 255, AF 260, AMF 265, and / or SMF 270.

[0052] UPF 275 includes one or more devices that serve as anchors for mobility within and / or between Radio Access Technologies (RATs). UPF 275 can apply rules to data packets, such as rules regarding data packet routing, traffic reporting, handling user plane QoS, etc.

[0053] Message bus 285 represents a communication structure for communication between functional elements. In other words, message bus 285 can allow communication between two or more functional elements. Message bus 285 can be a logical and / or physical communication structure for communication between functional elements. Therefore, message bus 285 can allow communication between two or more functional elements, whether logical (e.g., using one or more application programming interfaces (APIs), and other examples) and / or physical (e.g., using one or more wired and / or wireless connections).

[0054] Data network 280 includes one or more wired and / or wireless data networks. For example, data network 280 may include IP Multimedia Subsystem (IMS), Public Land Mobile Network (PLMN), Local Area Network (LAN), Wide Area Network (WAN), Metropolitan Area Network (MAN), Private Network such as corporate intranet, self-organizing network, Internet, fiber-optic network, cloud computing network, third-party service network, carrier service network, and / or combinations of these or other types of networks.

[0055] Figure 2 The number and arrangement of devices and networks shown are provided as an example. In reality, with... Figure 2 Compared to the devices and / or networks shown, there may be additional devices and / or networks, fewer devices and / or networks, different devices and / or networks, or devices and / or networks arranged differently. Furthermore, Figure 2 The two or more devices shown can be implemented within a single device, or Figure 2 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, a group of devices (e.g., one or more devices) in example environment 200 can perform one or more functions described as being performed by another group of devices in example environment 200.

[0056] Figure 3 This is a schematic diagram of an example implementation 300 associated with alternative AGF signaling for DHCP. For example... Figure 3 As shown, example implementation 300 includes client devices (e.g., client device 105 and / or client device 205), AN (e.g., AN 210), a first AGF (e.g., first AGF 215 and / or active AGF 110), a second AGF (e.g., second AGF 220 and / or standby AGF 115), AMF (e.g., AMF 265), SMF (e.g., SMF 270), UPF (e.g., UPF 275 and / or UPF 125), and a data network (DN) (e.g., data network 280). The following is in conjunction with... Figure 2 , 4 5 describes these devices in more detail.

[0057] As shown by reference numeral 302 in the attached figure, the first AGF and AMF can communicate to establish an N2 interface. Similarly, as shown by reference numeral 304 in the attached figure, the second AGF and AMF can communicate to establish an N2 interface. For example, the first AMF and the second AMF can communicate with the AMF to establish a network connection to the core network.

[0058] As shown by reference numeral 306 in the attached figure, the client device can send DHCP messages and the AN can receive DHCP messages. A DHCP message can be a request to establish a DHCP session. For example, a DHCP message can be a DHCP discovery message (e.g., associated with DHCPv4), a DHCP solicitation message (e.g., associated with DHCPv6), or a similar type of DHCP message. As shown by reference numeral 308 in the attached figure, the AN can send DHCP messages and the first AGF can receive DHCP messages. In other words, the AN can forward DHCP messages from the client device to the first AGF.

[0059] As shown by reference numeral 310 in the attached figure, the first AGF can perform a registration process with the AMF based on a received DHCP message. For example, the registration process can be a DHCP device registration process. As shown by reference numeral 312 in the attached figure, the first AGF can send a PDU session establishment request (e.g., via the N2 interface) and the AMF can receive the PDU session establishment request. For example, the first AGF can request to establish a PDU session based on a received DHCP message sent by a client device.

[0060] As shown by reference numeral 314, the AMF can send and the SMF can receive PDU session creation communications (e.g., PDU session creation data packets). For example, based on receiving a PDU session establishment request, the AMF can communicate with the SMF to establish a PDU session associated with the first AGF. As shown by reference numeral 316, the SMF can generate or establish a PDU session and communicate with the UPF to indicate the PDU session. As shown by reference numeral 318, based on successfully establishing a PDU session with the UPF, the SMF can send and the AMF can receive a PDU session creation ACK message indicating that the PDU session has been successfully established. As shown by reference numeral 320, the first AGF and the AMF can communicate to perform PDU session resource settings. For example, the first AGF and the AMF can communicate to establish session information, network resources, and / or network functions associated with the PDU session.

[0061] As shown by reference numeral 322 in the attached figure, the client device and the UPF can exchange one or more communications to perform DHCP session setup. For example, the UPF can send (e.g., via a first AGF and / or AN) DHCP Offer messages (e.g., associated with DHCPv4), DHCP Advertisement messages (e.g., associated with DHCPv6) or similar DHCP communications indicating that the UPF is available as a DHCP server, and the client device can receive such information. The client device can send (e.g., via AN and / or the first AGF), and the UPF can receive DHCP Request communications requesting the establishment of a DHCP session with the UPF. The UPF can generate network configuration information and / or DHCP binding information to be associated with the DHCP session based on the received DHCP Request communications. The UPF can send (e.g., via the first AGF and / or AN), and the client device can receive DHCP Request ACK communications indicating that the network configuration information and / or DHCP binding information and the DHCP session have been successfully established.

[0062] In some implementations, the first AGF and the client device may exchange one or more ARP messages (e.g., ARP requests and / or ARP responses) to establish a gateway IP address associated with the routing path for use with data packets associated with the client device. As shown by reference numeral 324, one or more data packets may be routed between the data network and the client device (e.g., via the UPF, the first AGF, and the AN) based on the establishment of PDU and DHCP sessions. For example, the first AGF may forward one or more data packets (e.g., as a DHCP relay) between the client device and the UPF (e.g., a DHCP server).

[0063] As shown by reference numeral 326 in the attached figure, the first AGF and the second AGF can exchange one or more lease query communications (e.g., ALQ and / or BLQ communications). Lease query communications sent by the first AGF and received by the second AGF can indicate DHCP binding information associated with the client device. Furthermore, as combined with... Figure 1A-1CTo explain in more detail, lease query communications may indicate information that enables a second AGF to switch a path (e.g., an N3 interface path) from a first AGF to a second AGF for use in a DHCP session associated with a client device. For example, lease query communications may include indications of SUPI, SUCI, GUTI, and / or PDU session identifiers associated with an active session (e.g., a PDU session and / or a DHCP session) between the first AGF and the client device, among other examples. Additionally or alternatively, lease query communications may include, in other examples, indications of GUAMI, AMF UE NGAP identifier, RAN UE GAP identifier, and / or UE context information (e.g., PDU session information associated with a PDU session and / or GTP information associated with a PDU session) associated with an active session (e.g., a PDU session and / or a DHCP session) between the first AGF and the client device, among other examples.

[0064] As shown by reference numeral 328 in the accompanying drawings, the first AGF and the second AGF exchange (e.g., via a TCP interface) one or more VRRP communications and / or one or more BFD communications to facilitate the detection by the second AGF of faults associated with the first AGF. For example, the second AGF may detect a fault associated with the first AGF based on the absence of VRRP and / or BFD reply communications within a certain period of time. As shown by reference numeral 330 in the accompanying drawings, the first AGF may experience a fault that prevents it from forwarding or routing data packets associated with the client device. The second AGF can detect this fault, as described in more detail elsewhere herein.

[0065] As shown by reference numeral 332 in the attached figure, based on the detection of a fault, the second AGF can send, and the AMF can receive, a path switching request associated with the PDU session and / or DHCP session of the client device. The path switching request may be an NGAP path switching request. In some implementations, the path switching request may be a request to modify the N3 interface path associated with the PDU session and / or DHCP session of the client device. The path switching request may indicate information provided by the first AGF in lease query communications. For example, the path switching request may indicate indications of SUPI, SUCI, GUTI, and / or PDU session identifiers associated with the active session (e.g., PDU session and / or DHCP session) between the first AGF and the client device, among other examples. Additionally or alternatively, the lease query communications may include, in other examples, indications of GUAMI, AMF UE NGAP identifier, RAN UEEGAP identifier, and / or UE context information (e.g., PDU session information associated with the PDU session and / or GTP information associated with the PDU session) associated with the active session (e.g., PDU session and / or DHCP session) between the first AGF and the client device. This enables AMF, SMF and / or other core network devices to identify subscribers (e.g., client devices), DHCP sessions and / or PDU sessions.

[0066] As shown by reference numeral 334, the AMF can send and the SMF can receive a path switching request. For example, based on receiving a path switching request from a second AGF, the AMF can request the SMF to switch the path associated with the PDU session and / or DHCP session (e.g., the N3 interface path) to the second AGF. As shown by reference numeral 336, the SMF and / or UPF can modify the path associated with the second AGF (e.g., based on receiving a path switching request). For example, the SMF and / or UPF can modify information stored by the core network associated with the PDU session and / or DHCP session to modify the path associated with the second AGF (e.g., instead of the first AGF). As shown by reference numeral 338, based on successfully modifying the PDU session and / or DHCP session to switch the path (e.g., the N3 path) to the second AGF, the SMF can send, and the AMF can receive, a path switching ACK message indicating that the path has been successfully switched as requested. As shown by reference numeral 340, the AMF can send, and the second AGF can receive, a path switching ACK message indicating that the path has been successfully switched as requested.

[0067] In some implementations, the second AGF may send, and the client device may receive, an indication of the MAC address associated with the second AGF. For example, the second AGF may send gratuitous ARP communications or gratuitous neighbor discovery communications indicating the MAC address associated with the second AGF (e.g., to enable the client device to communicate with the MAC entity associated with the second AGF). In some other implementations, the second AGF may not send an indication of the MAC address, such as in the example of using a virtual MAC entity shared between the first and second AGFs.

[0068] As shown by reference numeral 342 in the attached figure, one or more data packets can be routed between the data network and the client device based on switching paths and modifying the PDU session (e.g., via UPF, second AGF, and AN), as described above. For example, the second AGF can forward one or more data packets (e.g., as a DHCP relay) between the client device and the UPF (e.g., a DHCP server). Figure 3 As shown, recovery from a fault associated with the first AGF can be resolved quickly and efficiently by the first AGF providing information to the second AGF, enabling the second AGF to facilitate a switch of the path from the UPF (e.g., the N3 interface path) from the first AGF to the second AGF. For example, the second AGF can assume a DHCP relay role via a path switching procedure (e.g., the NGAP path switching procedure) rather than requiring the establishment of new PDU sessions and new DHCP sessions (e.g., using similar signaling as described in conjunction with reference numerals 312, 314, 316, 318, 320, and 322). This saves processing and / or network resources that would otherwise be used to transmit similar signaling as described in conjunction with reference numerals 312, 314, 316, 318, 320, and 322 to establish new PDU sessions and / or new DHCP sessions associated with the second AGF and the client device. Furthermore, this allows the PDU and DHCP sessions to be maintained, thereby reducing the impact of a first AGF fault on the client device.

[0069] As mentioned above, providing Figure 3 As an example. Other examples may be related to... Figure 3 The descriptions are different. Figure 3 The number and arrangement of devices shown are provided as an example. In reality, with... Figure 3 Compared to those shown, there may be additional equipment, fewer equipment, different equipment, or different arrangements of equipment. Furthermore, Figure 3 The two or more devices shown can be implemented within a single device, or Figure 3 The single device shown can be implemented as multiple distributed devices. Additionally or alternatively, Figure 3The set of devices shown (e.g., one or more devices) can perform actions described by Figure 3 The other set of devices shown performs one or more functions.

[0070] Figure 4 This is a schematic diagram of an example component of device 400, which may correspond to client device 105, active AGF 110, standby AGF 115, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, first AGF 215, second AGF 220, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270 and / or UPF 275, and other examples. In some implementations, client device 105, active AGF 110, standby AGF 115, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, first AGF 215, second AGF 220, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270, and / or UPF 275 include one or more devices 400 and / or one or more components of device 400. For example... Figure 4 As shown, device 400 may include bus 410, processor 420, memory 430, input unit 440, output unit 450 and communication unit 460.

[0071] Bus 410 includes one or more components that enable wired and / or wireless communication between components of device 400. Bus 410 can... Figure 4 Two or more components are coupled together, such as via operational coupling, communication coupling, electronic coupling, and / or electrical coupling. Processor 420 includes a central processing unit, graphics processing unit, microprocessor, controller, microcontroller, digital signal processor, field-programmable gate array, application-specific integrated circuit, and / or other types of processing units. Processor 420 is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, processor 420 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0072] Memory 430 includes volatile and / or non-volatile memory. For example, memory 430 may include random access memory (RAM), read-only memory (ROM), hard disk drive, and / or another type of memory (e.g., flash memory, magnetic storage, and / or optical storage). Memory 430 may include internal memory (e.g., RAM, ROM, or hard disk drive) and / or removable memory (e.g., removable via a universal serial bus). Memory 430 may be a non-transitory computer-readable medium. Memory 430 stores information, instructions, and / or software (e.g., one or more software applications) related to the operation of device 400. In some implementations, memory 430 includes one or more memories coupled to one or more processors (e.g., processor 420), such as via bus 410.

[0073] Input component 440 enables device 400 to receive input, such as user input and / or sensed input. For example, input component 440 may include a touchscreen, keyboard, keypad, mouse, button, microphone, switch, sensor, GPS sensor, accelerometer, gyroscope, and / or actuator. Output component 450 enables device 400 to provide output, such as via a display, speaker, and / or light-emitting diode. Communication component 460 enables device 400 to communicate with other devices via a wired and / or wireless connection. For example, communication component 460 may include a receiver, transmitter, transceiver, modem, network interface card, and / or antenna.

[0074] Device 400 can perform one or more operations or procedures described herein. For example, a non-transitory computer-readable medium (e.g., memory 430) can store a set of instructions (e.g., one or more instructions or code) for execution by processor 420. Processor 420 can execute a set of instructions to perform one or more operations or procedures described herein. In some implementations, execution of a set of instructions by one or more processors 420 causes one or more processors 420 and / or device 400 to perform one or more operations or procedures described herein. In some implementations, hardwired circuitry is used in place of instructions or in combination with instructions to perform one or more operations or procedures described herein. Additionally or alternatively, processor 420 may be configured to perform one or more operations or procedures described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0075] Figure 4 The number and arrangement of components shown are provided as an example. Device 400 may include components with... Figure 4The components shown are compared to additional components, fewer components, different components, or components with different arrangements. Additionally or alternatively, a set of components of device 400 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 400.

[0076] Figure 5 This is a schematic diagram of an example component of device 500. Device 500 may correspond to client device 105, active AGF 110, standby AGF 115, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, first AGF 215, second AGF 220, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270 and / or UPF 275, and other examples. In some implementations, client device 105, active AGF 110, standby AGF 115, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, first AGF 215, second AGF 220, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270, and / or UPF 275 may include one or more devices 500 and / or one or more components of device 500. Figure 5 As shown, device 500 may include one or more input components 510-1 to 510-B (B≥1) (hereinafter collectively referred to as input components 510, individually referred to as input components 510), switching component 520, one or more output components 530-1 to 530-C (C≥1) (hereinafter collectively referred to as output components 530, individually referred to as output components 530), and controller 540.

[0077] Input component 510 may be one or more attachment points of a physical link and may be one or more entry points for incoming services such as data packets. Input component 510 may process incoming services, such as by performing data link layer encapsulation or decapsulation. In some implementations, input component 510 may send and / or receive data packets. In some implementations, input component 510 may include an input line card that includes one or more data packet processing components (e.g., in the form of integrated circuits), such as one or more interface cards (IFCs), data packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some implementations, device 500 may include one or more input components 510.

[0078] Switching unit 520 interconnects input unit 510 with output unit 530. In some implementations, switching unit 520 may be implemented via one or more crossbar switches, via a bus, and / or utilizing shared memory. Shared memory may act as a temporary buffer to store data packets before finally scheduling data packets from input unit 510 for transmission to output unit 530. In some implementations, switching unit 520 enables input unit 510, output unit 530, and / or controller 540 to communicate with each other.

[0079] Output component 530 can store data packets and schedule data packets for transmission over the output physical link. Output component 530 can support data link layer encapsulation or decapsulation, and / or various higher-level protocols. In some implementations, output component 530 can send and / or receive data packets. In some implementations, output component 530 may include an output line card comprising one or more data packet processing components (e.g., in the form of integrated circuits), such as one or more IFCs, data packet forwarding components, line card controller components, output ports, processors, memory, and / or output queues. In some implementations, device 500 may include one or more output components 530. In some implementations, input component 510 and output component 530 may be implemented by the same group of components (e.g., the input / output component may be a combination of input component 510 and output component 530).

[0080] Controller 540 includes processors and / or other types of processors, such as CPUs, GPUs, APUs, microprocessors, microcontrollers, DSPs, FPGAs, ASICs, etc. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some implementations, controller 540 may include one or more processors that can be programmed to perform functions.

[0081] In some implementations, controller 540 may include RAM, ROM and / or another type of dynamic or static storage device (e.g. flash memory, magnetic storage, optical storage, etc.) for storing information and / or instructions for use by controller 540.

[0082] In some implementations, controller 540 can communicate with other devices, networks, and / or systems connected to device 500 to exchange information about the network topology. Controller 540 can create routing tables based on the network topology information, create forwarding tables based on the routing tables, and forward the forwarding tables to input unit 510 and / or output unit 530. Input unit 510 and / or output unit 530 can use the forwarding tables to perform route looks for incoming and / or outgoing data packets.

[0083] Controller 540 may execute one or more processes described herein. Controller 540 may execute these processes in response to executing software instructions stored on a non-transitory computer-readable medium. A computer-readable medium is defined herein as a non-transitory storage device. A storage device includes storage space within a single physical storage device or storage space distributed across multiple physical storage devices.

[0084] Software instructions may be read from another computer-readable medium or from another device via a communication interface into the memory and / or storage unit associated with controller 540. When executed, the software instructions stored in the memory and / or storage unit associated with controller 540 may cause controller 540 to perform one or more processes described herein. Additionally or alternatively, hard-wired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein. Therefore, the implementations described herein are not limited to any particular combination of hardware circuitry and software.

[0085] Figure 5 The number and arrangement of components shown are provided as an example. In practice, device 500 may include components with... Figure 5 The components shown are compared to additional components, fewer components, different components, or components with different arrangements. Additionally or alternatively, a set of components of device 500 (e.g., one or more components) may perform one or more functions described as being performed by another set of components of device 500.

[0086] Figure 6 This is a flowchart of an example process 600 associated with alternate AGF signaling used for DHCP. In some implementations, Figure 6 One or more processing blocks are executed by a first AGF device (e.g., a standby AGF 115 or a second AGF 220). In some implementations, Figure 6 One or more processing frames are executed by another device or group of devices that are separate from or include the first AGF device. This device may be, for example, client device 105, active AGF 105, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, first AGF 215, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270 and / or UPF 275, and other examples. Additionally or alternatively, Figure 6One or more processing blocks can be executed by one or more components of device 400, such as processor 420, memory 430, input unit 440, output unit 450, and / or communication unit 460. Additionally or alternatively, Figure 6 One or more processing blocks can be executed by one or more components of the device 500, such as input component 510, switching component 520, output component 530 and / or controller 540.

[0087] like Figure 6 As shown, process 600 may include communicating with a first core network device to establish a network connection with the core network (block 610). For example, the first AGF device may communicate with the first core network device to establish a network connection with the core network, as described above.

[0088] like Figure 6 As further shown, process 600 may include receiving communication from the second AGF device indicating at least one of subscriber identity, session information, subscriber context, or session transport information associated with an active session between the second AGF device and the DHCP client device (block 620). For example, the first AGF device may receive communication from the second AGF device indicating at least one of subscriber identity, session information, subscriber context, or session transport information associated with an active session between the second AGF device and the DHCP client device, as described above.

[0089] like Figure 6 As further shown, process 600 may include detecting a fault association between the second AGF device and the active session between the second AGF device and the DHCP client device (block 630). For example, the first AGF device may detect a fault association between the second AGF device and the active session between the second AGF device and the DHCP client device, as described above.

[0090] like Figure 6 As further shown, process 600 may include sending a request to a first core network device to switch a first path associated with an active session from the second AGF device to the first AGF device, wherein the request indicates at least one of subscriber identity, session information, subscriber context, or session transport information (box 640). For example, the first AGF device may send a request to the first core network device to switch a first path associated with an active session from the second AGF device to the first AGF device, wherein the request indicates at least one of subscriber identity, session information, subscriber context, or session transport information, as described above.

[0091] like Figure 6As further shown, process 600 may include receiving an indication (block 650) from the first core network device of information associated with a second path for an active session associated with a DHCP client device between the second core network device and the first AGF device. For example, the first AGF device may receive an indication from the first core network device of information associated with a second path for an active session associated with a DHCP client device between the second core network device and the first AGF device, as described above.

[0092] like Figure 6 As further shown, process 600 may include forwarding one or more data communications between a second core network device and a DHCP client device associated with an active session via a second path (block 660). For example, a first AGF device may forward one or more data communications between a second core network device and a DHCP client device associated with an active session via a second path, as described above.

[0093] Process 600 may include additional implementations, such as any single implementation or any combination of multiple implementations of one or more other processes described below and / or in conjunction with those described elsewhere herein.

[0094] In the first implementation, the communication is lease query communication.

[0095] In the second implementation, either alone or in combination with the first implementation, the communication includes an indication of at least one of NAS information or NGAP information associated with the active session.

[0096] In the third implementation, either alone or in combination with one or more of the first and second implementations, the subscriber identity, session information, subscriber context, or session transmission information includes an indication of at least one of the following: SUPI associated with the DHCP client device and active session, SUCI associated with the DHCP client device and active session, GUTI associated with the DHCP client device and active session, or PDU session identifier associated with the active session.

[0097] In the fourth implementation, either alone or in combination with one or more of the first to third implementations, the subscriber identity, session information, subscriber context, or session transmission information includes an indication of at least one of the following: GUAMI associated with the active session, AMF UE NGAP identifier associated with the active session, RAN UE NGAP identifier associated with the active session, or UE context information associated with the active session.

[0098] In the fifth implementation, either alone or in combination with one or more of the first to fourth implementations, the communication includes an indication of DHCP binding information associated with the active session.

[0099] In the sixth implementation, either alone or in combination with one or more of the first to fifth implementations, process 600 includes an instruction to send MAC address information associated with the first AGF device to the DHCP client device.

[0100] In the seventh implementation, either alone or in combination with one or more of the first to sixth implementations, the first core network device is a control plane core network device, and the second core network device is a user plane core network device.

[0101] although Figure 6 An example box for process 600 is shown, but in some implementations, process 600 includes more... Figure 6 The additional boxes, fewer boxes, different boxes, or boxes with different arrangements depicted in the diagram. Alternatively or concurrently, two or more boxes of process 600 may be executed in parallel.

[0102] Figure 7 This is a flowchart of an example process 700 associated with alternative AGF signaling used for DHCP. In some implementations, Figure 7 One or more process frames are executed by a first AGF device (e.g., active AGF 110 and / or first AGF 215). In some implementations, Figure 7 One or more processing frames are executed by another device or group of devices that are separate from or include the first AGF device. This device may be, for example, client device 105, backup AGF 115, one or more control plane core network devices 120, UPF 125, client device 205, AN 210, second AGF 220, NSSF 230, NEF 235, NRF 240, AUSF 245, UDM 250, PCF 255, AF 260, AMF 265, SMF 270 and / or UPF 275, and other examples. Additionally or alternatively, Figure 7 One or more processing blocks can be executed by one or more components of device 400, such as processor 420, memory 430, input unit 440, output unit 450, and / or communication unit 460. Additionally or alternatively, Figure 7 One or more processing blocks can be executed by one or more components of the device 500, such as input component 510, switching component 520, output component 530 and / or controller 540.

[0103] like Figure 7As shown, process 700 may include establishing a network connection with the core network and the control plane core network device (block 710). For example, the first AGF device may establish a network connection with the core network and the control plane core network device, as described above.

[0104] like Figure 7 As further shown, process 700 may include establishing a PDU session associated with a client device via DHCP with the control plane core network device, wherein the PDU session is associated with at least one of subscriber identity, subscriber context, session information, or session transport information associated with the client device (box 720). For example, the first AGF device may establish a PDU session associated with a client device via DHCP with the control plane core network device, wherein the PDU session is associated with at least one of subscriber identity, session information, subscriber context, or session transport information associated with the client device, as described above.

[0105] like Figure 7 As further shown, process 700 may include forwarding one or more data communications associated with a PDU session between a client device and a user plane core network device (box 730). For example, a first AGF device may forward one or more data communications associated with a PDU session between a client device and a user plane core network device, as described above.

[0106] like Figure 7 As further shown, process 700 may include sending a lease query communication to the second AGF device indicating at least one of the following: subscriber identity, session information, subscriber context, or session transport information associated with a PDU session, so that the second AGF device can maintain the PDU session with the client device (box 740). For example, the first AGF device may send a lease query communication to the second AGF device indicating at least one of the following: subscriber identity, session information, subscriber context, or session transport information associated with a PDU session, so that the second AGF device can maintain the PDU session with the client device, as described above. For example, the lease query communication may enable the second AGF device to maintain a data structure indicating information associated with the PDU session (e.g., it may enable the second AGF device to maintain a database, a list, and / or another data structure indicating PDU session information associated with one or more client devices, including the client devices).

[0107] Process 700 may include additional implementations, such as any single implementation or any combination of multiple implementations of one or more other processes described below and / or in conjunction with those described elsewhere herein.

[0108] In the first implementation, the lease query communication includes at least one of ALQ communication, stand-alone lease query communication, or BLQ communication.

[0109] In the second implementation, either alone or in combination with the first implementation, the lease query communication includes an indication of at least one of NAS information associated with the PDU session or NGAP information associated with the PDU session.

[0110] In the third implementation, either alone or in combination with one or more of the first and second implementations, the subscriber identity, session information, subscriber context, or session transmission information includes an indication of at least one of the following: SUPI associated with the client device and PDU session, SUCI associated with the client device and PDU session, GUTI associated with the client device and PDU session, or PDU session identifier associated with the PDU session.

[0111] In the fourth implementation, either alone or in combination with one or more of the first to third implementations, the subscriber identity, session information, subscriber context, or session transmission information includes an indication of at least one of the following: GUAMI associated with the PDU session, AMF UE NGAP identifier associated with the PDU session, RAN UE NGAP identifier associated with the PDU session, PDU session information associated with the PDU session, or GTP information associated with the PDU session.

[0112] In the fifth implementation, either alone or in combination with one or more of the first to fourth implementations, the lease query communication includes an indication of DHCP binding information associated with the PDU session.

[0113] In the sixth implementation, either alone or in combination with one or more of the first to fifth implementations, process 700 includes sending one or more VRRP communications or one or more BFD communications to the second AGF device to facilitate the detection of a fault associated with the first AGF device associated with the PDU session.

[0114] although Figure 7 An example box of process 700 is shown, but in some implementations, process 700 includes more... Figure 7 The additional boxes, fewer boxes, different boxes, or boxes with different arrangements depicted in the diagram. Alternatively or concurrently, two or more boxes of process 700 may be executed in parallel.

[0115] The foregoing disclosure provides explanations and descriptions, but is not intended to be exhaustive or to limit the implementation to the precise form disclosed. Modifications and variations can be made based on the foregoing disclosure, or can be derived from the practice of implementing the methods.

[0116] As used herein, traffic or content may include a set of data packets. A data packet may refer to a communication structure used to transmit information such as a PDU, Service Data Unit (SDU), network data packet, datagram, segment, message, block, frame (e.g., Ethernet frame), a portion of any of the above, and / or another type of formatted or unformatted data unit that can be transmitted via a network.

[0117] As used in this article, depending on the context, a threshold can refer to a value that is greater than, greater than or equal to, less than, less than or equal to, equal to, or not equal to the threshold.

[0118] As used herein, the term "component" is intended to be interpreted broadly as hardware, firmware, or a combination of hardware and software. Clearly, the systems and / or methods described herein can be implemented in various forms of hardware, firmware, and / or combinations of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limited to the described implementations. Therefore, this document describes the operation and behavior of the systems and / or methods without reference to any specific software code—it should be understood that software and hardware can be used to implement the systems and / or methods based on the description herein.

[0119] Although specific combinations of features are detailed in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various implementations. In fact, many of these features can be combined in ways not detailed in the claims and / or disclosed in the specification. While each dependent claim listed below may directly depend on one claim, the disclosure of the various implementations includes combinations of each dependent claim with each other claim in the claim set. As used herein, the phrase “at least one” in the list of items refers to any combination of these items, including single members. For example, “at least one of a, b, or c” is intended to cover a, b, c, ab, ac, bc, and abc, as well as any combination having multiple identical items.

[0120] Unless expressly stated otherwise, no element, action, or instruction used herein should be construed as critical or necessary. Furthermore, as used herein, the articles “a” and “an” are intended to include one or more items and may be used interchangeably with “one or more.” Furthermore, as used herein, the article “the” is intended to include one or more items relating to the article “the” and may be used interchangeably with “one or more.” Furthermore, as used herein, the term “collection” is intended to include one or more items (e.g., related items, unrelated items, or a combination of related and unrelated items) and may be used interchangeably with “one or more.” If only one is intended to be included, the phrase “only one” or similar language is used. Furthermore, as used herein, the terms “having,” “possessing,” “having,” etc., are intended to be open-ended terms. Furthermore, unless expressly stated otherwise, the phrase “based on” is intended to mean “at least partially based on.” Furthermore, as used herein, the term “or” is intended to be included when used in a series form and may be used interchangeably with “and / or” unless expressly stated otherwise (e.g., if used in conjunction with “any one” or “only one”).

Claims

1. A method for communication, comprising: The first access gateway (AGF) device communicates with the first core network device to establish a network connection with the core network. The first AGF device receives communication from the second AGF device indicating at least one of the following: subscriber identity, session information, subscriber context, or session transfer information associated with an active session between the second AGF device and the Dynamic Host Configuration Protocol (DHCP) client device; The first AGF device detects a fault in the active session between the second AGF device and the DHCP client device. The first AGF device sends a request to the first core network device to switch the 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 following: the subscriber identity, the session information, the subscriber context, or the session transport information; The first AGF device receives an indication from the first core network device that information associated with a second path is received, the second path being between the second core network device and the first AGF device, for the active session associated with the DHCP client device; as well as One or more data communications are forwarded by the first AGF device between the second core network device and the DHCP client device associated with the active session via the second path.

2. The method according to claim 1, wherein the communication is a lease query communication.

3. The method of claim 1, wherein the communication includes an indication of at least one of the following: Non-Access Stratum (NAS) information associated with the active session or Next Generation Application Protocol (NGAP) information associated with the active session.

4. The method of claim 1, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: The subscriber's unique permanent identifier SUPI associated with the DHCP client device and the active session. The subscriber-unique hidden identifier (SUCI) associated with the DHCP client device and the active session. The globally unique temporary identifier (GUTI) associated with the DHCP client device and the active session, or Protocol Data Unit (PDU) session identifier associated with the active session.

5. The method of claim 1, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: A globally unique Access and Mobility Function (AMF) identifier (GUAMI) associated with the activity session. The AMF user equipment UE Next Generation Application Protocol (NGAP) identifier associated with the active session. The radio access network RAN ​​UE NGAP identifier associated with the active session, or UE context information associated with the active session.

6. The method of claim 1, wherein the communication includes an indication of DHCP binding information associated with the active session.

7. The method according to claim 1, further comprising: Instructions are sent to the DHCP client device to provide information about the Media Access Control (MAC) address associated with the first AGF device.

8. The method according to claim 1, wherein the first core network device is a control plane core network device, and the second core network device is a user plane core network device.

9. A first access gateway (AGF) device, comprising: One or more memory units; as well as One or more processors, used to: Establish network connections between the control plane core network equipment and the core network; A Protocol Data Unit (PDU) session associated with the client device is established with the control plane core network device via Dynamic Host Configuration Protocol (DHCP), wherein the PDU session is associated with at least one of the following: subscriber identity, session information, subscriber context, or session transport information associated with the client device; Forward one or more data communications associated with the PDU session between the client device and the user plane core network device; as well as Send a lease query communication to the second AGF device indicating at least one of the following: the subscriber identity, the session information, the subscriber context, or the session transport information associated with the PDU session, so that the second AGF device can maintain the PDU session with the client device.

10. The first AGF device according to claim 9, wherein the lease query communication includes at least one of the following: active lease query ALQ communication, individual lease query communication, or bulk lease query BLQ communication.

11. The first AGF device of claim 9, wherein the lease query communication includes an indication of at least one of: Non-Access Stratum (NAS) information associated with the PDU session or Next Generation Application Protocol (NGAP) information associated with the PDU session.

12. The first AGF device of claim 9, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: The subscriber-unique permanent identifier (SUPI) associated with the client device and the PDU session. The Subscriber Unique Hidden Identifier (SUCI) associated with the client device and the PDU session. The globally unique temporary identifier (GUTI) associated with the client device and the PDU session, or The PDU session identifier associated with the PDU session.

13. The first AGF device of claim 9, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: The globally unique access and mobility function (AMF) identifier GUAMI associated with the PDU session, The AMF (User Equipment) Next Generation Application Protocol (NGAP) identifier associated with the PDU session. The radio access network RAN ​​UE NGAP identifier associated with the PDU session, PDU session information associated with the PDU session. The General Packet Radio Service (GPRS) Tunneling Protocol (GTP) information associated with the PDU session, or UE context information associated with the PDU session.

14. The first AGF device of claim 9, wherein the lease query communication includes an indication of DHCP binding information associated with the PDU session.

15. The first AGF device according to claim 9, wherein the one or more processors are further configured to: Send one or more Virtual Router Redundancy Protocol (VRRP) communications or one or more Bidirectional Forward Detection (BFD) communications to the second AGF device to facilitate the detection of faults associated with the first AGF device in the PDU session.

16. A non-transitory computer-readable medium storing an instruction set, the instruction set comprising: One or more instructions, when executed by one or more processors of the first Access Gateway Function (AGF) device, cause the first AGF device to: Communicate with core network devices in the control plane to establish network connections with the core network; Receive a lease query communication from the second AGF device indicating at least one of the following: subscriber identity, session information, subscriber context, or session transmission information associated with a Protocol Data Unit (PDU) session between the second AGF device and the client device; The second AGF device has been detected to have experienced a failure associated with the PDU session; Send a request to the control plane core network device to switch the PDU session from the second AGF device to the first AGF device, wherein the request indicates at least one of the following: the subscriber identity, the session information, the subscriber context, or the session transport information; Instructions for receiving information associated with a path from the control plane core network device, the path being between the user plane core network device and the first AGF device, for the PDU session associated with the client device; as well as One or more data communications are forwarded between the user plane core network device and the client device associated with the PDU session via the path.

17. The non-transitory computer-readable medium of claim 16, wherein the lease query communication includes an indication of at least one of Non-Access Stratum (NAS) information associated with the PDU session or Next Generation Application Protocol (NGAP) information associated with the PDU session.

18. The non-transitory computer-readable medium of claim 16, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: The subscriber-unique permanent identifier (SUPI) associated with the client device and the PDU session. The Subscriber Unique Hidden Identifier (SUCI) associated with the client device and the PDU session. The globally unique temporary identifier (GUTI) associated with the client device and the PDU session, or The PDU session identifier associated with the PDU session.

19. The non-transitory computer-readable medium of claim 16, wherein the subscriber identity, the session information, the subscriber context, or the session transmission information includes an indication of at least one of the following: The globally unique access and mobility function (AMF) identifier GUAMI associated with the PDU session, The AMF (User Equipment) Next Generation Application Protocol (NGAP) identifier associated with the PDU session. The radio access network RAN ​​UE NGAP identifier associated with the PDU session, or UE context information associated with the PDU session.

20. The non-transitory computer-readable medium of claim 16, wherein the one or more instructions that cause the first AGF device to detect that the second AGF device has experienced the fault associated with the PDU session cause the first AGF device to: The fault in the second AGF device is detected by performing the Virtual Router Redundancy Protocol (VRRP) procedure or the Bidirectional Forwarding Detection (BFD) procedure with the second AGF device.

Images