Virtual internet protocol addresses associated with subscriber groups

Abstract

Embodiments of the present disclosure relate to a virtual internet protocol address associated with a subscriber group. In some implementations, a network device may transmit an indication that a first access gateway function user plane (AGF-UP) device is associated with an active state of a subscriber group, an indication that a second AGF-UP device is associated with a backup state of the subscriber group, and an indication of a virtual Internet Protocol (IP) address associated with the subscriber group. The network device may transmit a failover indication that the second AGF-UP device is associated with an active state of the subscriber group.

Description

Technical Field

[0001] Embodiments of the present disclosure relate to the field of computer networks, and more particularly, to virtual Internet Protocol addresses associated with subscriber groups. Background Art

[0002] In wireless and wireline convergence (WWC), subscriber equipment (e.g., customer premises equipment (CPE), such as residential gateway (RG)) is served by the access gateway function (AGF) and user plane function (UPF) of the fifth generation (5G) network. The AGF is responsible for providing services such as marking, policing, and shaping, while the UPF is responsible for providing services such as billing and lawful interception. Summary of the invention

[0003] Some embodiments described herein are directed to a method. The method may include transmitting, by a network device, an indication that a first AGF-User Plane (AGF-UP) device is associated with an active state of a subscriber group (SGRP), an indication that a second AGF-UP device is associated with a standby state of the SGRP, and an indication of a virtual Internet Protocol (IP) address associated with the SGRP. The method may include transmitting, by the network device, a failover indication that the second AGF-UP device is associated with an active state of the SGRP.

[0004] Some embodiments described herein are directed to a device. The device may include one or more memories and one or more processors. The one or more processors may transmit an indication that a first AGF-UP device is associated with an active state of SGRP, an indication that a second AGF-UP device is associated with a standby state of SGRP, and an indication of a virtual IP address associated with SGRP, wherein the virtual IP address is associated with a local endpoint of an N3 tunnel. The one or more processors may transmit a failover indication that a second AGF-UP device is associated with an active state of SGRP.

[0005] Some embodiments described herein relate to a non-transitory computer-readable medium storing a set of instructions. When executed by one or more processors of a device, the set of instructions may cause the device to transmit an indication that a first AGF-UP device is associated with an active state of SGRP, an indication that a second AGF-UP device is associated with a standby state of SGRP, and an indication of a virtual IP address associated with SGRP, wherein the virtual IP address is additionally associated with an endpoint of a CPRi tunnel. When executed by one or more processors of the device, the set of instructions may cause the device to transmit a failover indication that the second AGF-UP device is associated with an active state of SGRP.

[0006] One aspect of the present disclosure provides a method, comprising: transmitting, by a network device, an indication of a first access gateway function user plane AGF-UP device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for the subscriber group, and an indication of a virtual Internet Protocol IP address associated with the subscriber group; and transmitting, by the network device, a failover indication of the second AGF-UP device associated with the active state for the subscriber group.

[0007] According to one or more embodiments of the present disclosure, the virtual IP address is associated with a local endpoint of the N3 tunnel.

[0008] According to one or more embodiments of the present disclosure, the virtual IP address is a first virtual IP address, and the method further includes: the network device transmits a second virtual IP address associated with an endpoint of a control packet redirection interface CPRi tunnel, wherein the second virtual IP address is different from the first virtual IP address.

[0009] According to one or more embodiments of the present disclosure, the virtual IP address is also associated with an endpoint of a control packet redirection interface CPRi tunnel.

[0010] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier (F-TEID) associated with the N3 tunnel is based on the virtual IP address.

[0011] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier F-TEID associated with a user plane function UPF is associated with the N3 tunnel.

[0012] According to one or more embodiments of the present disclosure, the virtual IP address is associated with an endpoint of a control packet redirection interface CPRi tunnel.

[0013] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier (F-TEID) associated with the CPRi tunnel is based on the virtual IP address.

[0014] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier F-TEID associated with the network device is associated with the CPRi tunnel.

[0015] According to one or more embodiments of the present disclosure, the network device is an access gateway function control plane AGF-CP device.

[0016] Another aspect of the present disclosure provides a device comprising: one or more memories; and one or more processors, configured to: transmit an indication of a first access gateway function user plane AGF-UP device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for the subscriber group, and an indication of a virtual Internet Protocol IP address associated with the subscriber group, wherein the virtual IP address is associated with a local endpoint of an N3 tunnel; and transmit a failover indication of the second AGF-UP device associated with the active state for the subscriber group.

[0017] According to one or more embodiments of the present disclosure, the virtual IP address is a first virtual IP address, and wherein the one or more processors are also used to: transmit a second virtual IP address associated with an endpoint of a control packet redirection interface CPRi tunnel, wherein the second virtual IP address is different from the first virtual IP address.

[0018] According to one or more embodiments of the present disclosure, the virtual IP address is also associated with an endpoint of a control packet redirection interface CPRi tunnel.

[0019] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier (F-TEID) associated with the N3 tunnel is based on the virtual IP address.

[0020] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier F-TEID associated with a user plane function UPF is associated with the N3 tunnel.

[0021] Yet another aspect of the present disclosure provides a non-transitory computer-readable medium storing a set of instructions, the set of instructions comprising: one or more instructions which, when executed by one or more processors of a device, cause the device to: transmit an indication of a first access gateway function user plane AGF-UP device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for the subscriber group, and an indication of a virtual Internet Protocol IP address associated with the subscriber group, wherein the virtual IP address is also associated with an endpoint of a control packet redirection interface CPRi tunnel; and transmit a failover indication of the second AGF-UP device associated with the active state for the subscriber group.

[0022] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier (F-TEID) associated with the CPRi tunnel is based on the virtual IP address.

[0023] According to one or more embodiments of the present disclosure, a full tunnel endpoint identifier F-TEID associated with the device is associated with the CPRi tunnel.

[0024] According to one or more embodiments of the present disclosure, the virtual IP address is a first virtual IP address, and wherein the one or more instructions, when executed by one or more processes of the device, also cause the device to: transmit a second virtual IP address associated with a local endpoint of the N3 tunnel, wherein the second virtual IP address is different from the first virtual IP address.

[0025] According to one or more embodiments of the present disclosure, the virtual IP address is also associated with the local endpoint of the N3 tunnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 is a schematic diagram of an example implementation associated with a virtual IP address associated with SGRP.

[0027] Figure 2 is a schematic diagram of an example implementation associated with an N3 virtual IP address and a CPRi virtual IP address.

[0028] Figure 3 is a schematic diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0029] Figure 4 yes Figure 3 A schematic diagram of example components of one or more devices.

[0030] Figure 5 yes Figure 3 A schematic diagram of example components of one or more devices.

[0031] Figure 6 is a flow diagram of an example process associated with a virtual IP address associated with SGRP. DETAILED DESCRIPTION

[0032] The following detailed description of example embodiments refers to the accompanying drawings. The same reference numerals in different drawings may identify the same or similar elements.

[0033] A broadband network gateway (BNG) routes traffic to and from broadband remote access devices, such as digital subscriber line access multiplexers (DSLAMs), on Internet service provider (ISP) networks. The BNG enables subscribers to connect to broadband networks and performs authentication, authorization, and billing; assigns Internet Protocol (IP) addresses; and implements Quality of Service (QoS) policies.

[0034] To accommodate the growth in the number of subscribers, the number and types of services provided by the BNG, and the traffic processed by the BNG, a service provider may deploy a disaggregated BNG (DBNG). The DBNG provides control and user plane separation (CUPS) both physically and logically. For example, software used to perform control plane functions may be distributed for implementation by a BNG control plane (BNG-CP) device. Two or more BNG user plane (BNG-UP) devices may be maintained in the forwarding path between a subscriber device and a network to process traffic (e.g., packet flows) between the subscriber device and the network. At least one BNG-UP device may be an active BNG-UP device (e.g., an active BNG-UP device may process traffic), and at least one BNG-UP device may be a standby BNG-UP device (e.g., in the event that an active BNG-UP device fails or otherwise ceases to be active).

[0035] Efforts are underway to migrate subscribers from DBNG to AGF CUPS to advance WWC activities. WWC refers to the ability of a core network, such as a 5G core network (5GC), to provide services to subscribers connected through both wireless and wired infrastructures. For example, wireless infrastructure enables client devices (e.g., user equipment (UE), etc.) to connect to the core network through a wireless access network (e.g., gNodeB). Wired infrastructure enables subscriber devices to connect to the core network through a wired access network using wired access (e.g., transmitting information through physical elements such as optical fiber, coaxial cable, twisted pair cable, etc.). Unlike AGF CUPS, DBNG only provides limited connectivity to 5GC via wired infrastructure.

[0036] The AGF CUPS divides the AGF functions into an AGF-UP device and an AGF control plane (AGF-CP) device. For example, software that performs control plane functions may be distributed for execution by an AGF-CP device. Two or more AGF-UP devices may be maintained in a forwarding path between a subscriber device and a network to process traffic (e.g., packet flows) between the subscriber device and the network. At least one AGF-UP device may be an active AGF-UP device (e.g., an active AGF-UP device may process traffic), and at least one AGF-UP device may be a standby AGF-UP device (e.g., in the event that an active AGF-UP device fails or otherwise ceases to be active).

[0037] For example, before transmitting the packet to the UPF via the N3 interface (e.g., through an N3 tunnel, such as an N3 GTP tunnel), the active AGF-UP device may encapsulate the packet in a general packet radio service (GPRS) tunneling protocol (GTP) user plane (GTP-U) header. For example, the active AGF-UP device may transmit packets of one or more protocol data unit (PDU) sessions via one or more N3 tunnels. In some examples, each PDU session may have a unique corresponding N3 tunnel. PDU sessions that may belong to the same subscriber or different subscribers may terminate on different UPFs (e.g., N3 tunnels may terminate on different UPFs). The 5GC controls which PDU sessions (one or more) terminate on which UPFs (one or more). The active AGF-UP device may transmit (and / or receive) packets via the N3 interface using the IP address of the active AGF-UP device. For example, the IP address may be exchanged (e.g., with the UPF) as part of the fully qualified tunnel endpoint identifier (F-TEID) of the N3 tunnel during signaling.

[0038] The AGF-CP device may send control packets to and / or receive control packets from the AGF-UP device via a control packet redirection interface (CPRi). For example, for packets destined for the UPF, each PDU session may have a unique corresponding subscriber server CPRi. One or more of the PDU sessions may be associated with an IPoE subscriber in adaptive mode (e.g., for a fixed network residential gateway).

[0039] DBNG deployments (rather than AGF CUPS deployments) can use SGRP to group subscribers and appropriately provision active and standby BNG-UP devices. SGRP includes a group of subscribers (e.g., subscribers that share similar or identical network traffic characteristics, service level agreements, etc.). Therefore, there is a gap in the current SGRP model that results in SGRP in AGF CUPS being unsupported (e.g., unavailable), which hinders migration from DBNG to AGF CUPS, thereby preventing the evolution to WWC.

[0040] For example, due to the renegotiation of certain N3 tunnel parameters, such as the IP address of the standby AGF-UP device, a change (e.g., failover) from an active AGF-UP device to a standby AGF-UP device may involve excessive signaling. For example, the AGF-CP device may transmit an indication to the UPF via the 5GC that the IP address has been changed from the active AGF-UP device to the standby AGF-UP device, and the UPF transmits a confirmation of the change to the AGF-CP device via the 5GC. Such signaling may result in packet loss, thereby significantly disrupting (e.g., interrupting) subscriber services and preventing seamless failover. In addition, because the UPF does not handle subscribers at the SGRP level, the AGF-CP transmits a separate indication for each subscriber in the SGRP and receives a separate confirmation. Therefore, the signaling overhead increases by several times the number of subscribers affected by the IP address change.

[0041] Additionally or alternatively, the change from the active AGF-UP device to the standby AGF-UP device may involve excessive control traffic signaling due to the reallocation of the standby AGF-UP device IP address. For example, the AGF-CP device may renegotiate at least one CPRi associated with the PDU session with the standby AGF-UP device. For example, the AGF-CP device may allocate a subscriber server tunnel endpoint identifier (TEID) (e.g., associated with at least one CPRi) on the standby AGF-UP device to map the subscriber server TEID to an updated (e.g., correct) N3 tunnel parameter. Additionally or alternatively, the AGF-CP device may synchronize one or more other parameters due to the failover.

[0042] Furthermore, since IP prefixes are not associated with SGRP, all subscriber routes are programmed independently. For example, IP prefixes are managed for independent subscribers, even if the subscribers belong to the same SGRP. As a result, in the event of a failover, excessive resources (e.g., processing resources, computing resources, memory resources, etc.) may be consumed to manage IP prefixes.

[0043] Some embodiments described herein implement SGRP support for AGF. In some aspects, the AGF-CP device assigns one or more virtual IP addresses to the SGRP. For example, each SGRP may be associated with at least one virtual IP address. In some examples, the virtual IP address(es) may include a virtual N3 user plane IP address and / or a virtual server CPRi IP address. The AGF-UP device may use the virtual N3 user plane IP address to exchange user plane traffic with the UPF via the N3 tunnel, and / or the AGF-UP device may use the virtual server CPRi IP address to exchange control plane traffic with the AGF-CP device via CPRi.

[0044] The AGF-CP device may provide an indication of the virtual IP address(es) to the active AGF-UP device and the standby AGF-UP device. Prior to a failover, the virtual IP address(es) may be hosted only by the active AGF-UP device. For example, initially, the virtual IP address(es) may be activated on the active AGF-UP device and disabled on the standby AGF-UP device for a specified SGRP. Upon detecting a failover trigger, the AGF-CP device may activate the virtual IP address(es) on the standby AGF-UP device and disable the virtual IP address(es) on the active AGF-UP device. In this case, the virtual IP address may migrate to the standby AGF-UP device along with the SGRP when a failover occurs. If the virtual IP address includes a virtual N3 user plane IP address, the standby AGF-UP device may publish an updated route in the network connecting the standby AGF-UP device and the UPF, so that the network may deliver packets from the UPF to the standby AGF-UP device instead of the previously active AGF-UP device.

[0045] Thus, the virtual IP address(es) can enhance the current SGRP model by helping to provide SGRP support on the AGF and, therefore, on the WWC. For example, the virtual N3 user plane IP address can reduce excessive signaling (e.g., business impact) between the AGF-CP device and the 5GC by avoiding per-subscriber exchanges with the 5GC that consume excessive bandwidth. In addition, the virtual N3 user plane IP address can enable seamless failover from the active AGF-UP device to the standby AGF-UP device. For example, in the absence of a control exchange between the AGF-CP device and the 5GC, failover can occur quickly (e.g., within a sub-millisecond time frame). The virtual server CPRi IP address can reduce signaling by allowing the AGF-CP device to avoid renegotiating CPRi after a failover occurs. In addition, since the virtual IP address(es) migrates with SGRP, the IP prefix also migrates with SGRP, thereby reducing the need for IP prefix management.

[0046] Figure 1 FIG. 1 is a schematic diagram of an example implementation 100 associated with a virtual IP address associated with SGRP. Figure 1 As shown, the example implementation 100 includes a network device (eg, an AGF-CP device), a subscriber device, a first AGF-UP device, a second AGF-UP device, and a UPF. Figure 3-Figure 5 These devices are described in more detail.

[0047] As shown by reference numeral 110, the network device may transmit to the first AGF-UP device and the second AGF-UP device an indication that the first AGF-UP device is associated with an active state of SGRP, an indication that the second AGF-UP device is associated with a standby state of SGRP, and an indication of a virtual IP address associated with SGRP. For example, the first AGF-UP may be configured as an active AGF-UP for SGRP, and the second AGF-UP may be configured as a standby AGF-UP for SGRP. The virtual IP address may be an IP address that is not associated with a physical interface (e.g., a physical port). The virtual IP address may be referred to as a "loopback address", such as a "routable loopback IP address".

[0048] In some examples, the network device may transmit an indication in one or more packet forwarding control protocol (PFCP) information elements (IEs) in one or more PFCP node association messages and / or one or more PFCP session establishment messages. The AGF-CP device may use the PFCP node association message(s) to establish or update a PFCP association between the AGF-CP and the first AGF-UP device and / or the second AGF-UP device. The PFCP node association message(s) may include one or more SGRP-grouped parameters, such as a SGRP identifier (ID), a SGRP state, a virtual MAC address, a logical port, and one or more SGRP flags. The SGRP ID may indicate the SGRP to which the subscriber device belongs, and the SGRP state may be "active" (e.g., for the first AGF-UP device) or "standby" (e.g., for the second AGF-UP device). The AGF-CP device may use the PFCP session establishment message(s) to indicate one or more rules for processing and / or forwarding user plane traffic to the first AGF-UP device and / or the second AGF-UP device. The PFCP session establishment message(s) may include one or more SGRP-grouped parameters, such as a SGRP ID.

[0049] In some aspects, the virtual IP address may be associated with a local endpoint of an N3 tunnel. For example, an N3 tunnel may be configured to carry network traffic between an active AGF-UP device and a UPF (e.g., network traffic for a PDU session of a subscriber device), and the local endpoint may be the N3 tunnel local endpoint of an AGF-UP device (e.g., an active AGF-UP device). The virtual IP address may be associated with a local endpoint of an N3 tunnel because the virtual IP address may be used to (directly or indirectly) identify the AGF-UP device as the source of packets transmitted by the AGF-UP device through the N3 tunnel and / or the destination of packets transmitted by the UPF through the N3 tunnel. In some examples, the AGF-CP device may transmit a PFCP node association message containing an indication of the virtual IP address as a virtual N3 IP address.

[0050] In some aspects, the N3 tunnel may be associated with (e.g., contain or use) an F-TEID based on a virtual IP address. For example, the F-TEID based on the virtual IP address may be an endpoint ID of the N3 tunnel that identifies the active AGF-UP device. In some examples, the AGF-CP may transmit a PFCP session establishment message containing an indication of the F-TEID as the AGF-UP N3 F-TEID.

[0051] In some aspects, the N3 tunnel may be associated with an F-TEID, which is associated with the UPF. For example, the F-TEID associated with the UPF may be an endpoint ID of the N3 tunnel that identifies the UPF. In some examples, the AGF-CP may transmit a PFCP session establishment message containing an indication of the F-TEID as the UPF N3 F-TEID. In some examples, the F-TEID based on the virtual IP address and the F-TEID associated with the UPF may be the two endpoints of the N3 tunnel.

[0052] In some aspects, a virtual IP address may be associated with an endpoint of a CPRi tunnel. For example, an AGF-CP device may communicate with an active AGF-UP device via a CPRi tunnel (e.g., a tunnel that carries packets via a CPRi), and the endpoint may be a CPRi tunnel endpoint of an AGF-UP device (e.g., the active AGF-UP device). The virtual IP address may be associated with an endpoint of a CPRi tunnel because the virtual IP address may be used to (directly or indirectly) identify the active AGF-UP device as a source of packets transmitted by the AGF-UP device via the CPRi tunnel and / or a destination of packets transmitted by the AGF-CP via the CPRi tunnel. In some examples, the AGF-CP device may transmit a PFCP Node Association message containing an indication of the virtual IP address as a virtual CPRi IP address.

[0053] In some aspects, a CPRi tunnel may be associated with (e.g., contain or use) an F-TEID based on a virtual IP address. For example, the F-TEID based on the virtual IP address may be an endpoint ID of the CPRi tunnel that identifies the active AGF-UP device. In some examples, the AGF-CP may transmit a PFCP session establishment message containing an indication of the F-TEID as the AGF-UP server CPRi F-TEID.

[0054] In some aspects, the CPRi tunnel may be associated with an F-TEID associated with a network device (e.g., an AGF-CP). For example, the F-TEID based on the virtual IP address may be an endpoint ID of the CPRi tunnel that identifies the AGF-CP device. In some examples, the AGF-CP may transmit a PFCP session establishment message containing an indication of the F-TEID as the AGF-CP server CPRi F-TEID. In some examples, the F-TEID based on the virtual IP address and the F-TEID associated with the AGF-CP device may be two endpoints of the CPRi tunnel.

[0055] In some aspects, a network device (e.g., an AGF-CP) may transmit a virtual IP address associated with a local endpoint of an N3 tunnel and another virtual IP address associated with an endpoint of a CPRi tunnel that is different from the virtual IP address associated with the local endpoint of the N3 tunnel. For example, the value of the virtual IP address associated with the local endpoint of the N3 tunnel may be different from the value of the virtual IP address associated with the endpoint of the CPRi tunnel. In other aspects, a virtual IP address may be associated with a local endpoint of the N3 tunnel and an endpoint of a CPRi tunnel. For example, the same virtual IP address may be associated with a local endpoint of the N3 tunnel and an endpoint of a CPRi tunnel.

[0056] As shown by reference numeral 120, the network device may transmit a failover indication that the second AGF-UP device is associated with the active state of the SGRP. For example, the network device may transmit the failover indication in response to identifying a failover trigger (e.g., a failure of the first AGF-UP device, etc.). In some examples, the network may also transmit an indication that the first AGF-UP device is associated with the standby state.

[0057] In response to receiving the failover indication, the second AGF-UP device may communicate through the N3 tunnel and / or the CPRi tunnel using information received from the network device through the PFCP. For example, the second AGF-UP device may use the N3 tunnel endpoint (e.g., F-TEID) and / or the CPRi tunnel endpoint (e.g., F-TEID) to establish one or more states. In some examples, the second AGF-UP device may communicate with the network device (e.g., AGF-CP device) through the CPRi tunnel previously used by the first AGF-UP device. In some examples, the second AGF-UP device may publish updated routes in the network connecting the second AGF-UP device and the UPF, and when the routes converge (e.g., in the network and / or on the UPF), the second AGF-UP device and the UPF may communicate through the N3 tunnel previously used by the first AGF-UP device.

[0058] Transmitting an indication of a virtual IP address associated with SGRP can reduce signaling and bandwidth consumption. For example, a second AGF-UP device can use the virtual IP address(es) to communicate over the N3 interface and / or on the CPRi without transmitting signaling between the AGF-CP device and the 5GC to establish a new N3 tunnel, and / or between the AGF-CP device and the second AGF-UP device to establish a new CPRi tunnel. In addition, since the virtual IP address(es) migrates with the SGRP, the IP prefix also migrates with the SGRP, thereby reducing the need for IP prefix management.

[0059] The virtual IP address associated with the local endpoint of the N3 tunnel can reduce excessive signaling (e.g., business impact) between the AGF-CP and the 5GC. Because the virtual N3 user plane IP address moves with the SGRP, the AGF-CP can avoid notifying the 5GC of the SGRP switch, thereby avoiding per-subscriber exchanges with the 5GC that consume too much bandwidth. In addition, because the SGRP switch can remain hidden from the 5GC under the AGF-CP, the failover process may not depend on which UPF the SGRP PDU session is associated with. Therefore, different subscribers can be connected to different UPFs. In addition, the virtual N3 user plane IP address can achieve seamless failover from the active AGF-UP to the standby AGF-UP. For example, if there is no control exchange between the AGF-CP and the 5GC, the failover can occur quickly. For example, the updated routes issued by the AGF-UP in the network can converge quickly in the network and on the UPF (e.g., within a sub-millisecond time frame), thereby reducing disconnection during the failover time.

[0060] The virtual IP address associated with the CPRi tunnel endpoint can reduce signaling by allowing the AGF-CP to avoid renegotiating the CPRi tunnel after a failover occurs. The virtual IP address associated with the local endpoint of the N3 tunnel and the endpoint of the CPRi tunnel can reduce memory consumption by avoiding storing multiple virtual IP addresses. The virtual IP address associated with the local endpoint of the N3 tunnel is a first virtual IP address and the second virtual IP address associated with the endpoint of the CPRi tunnel is different from the first virtual IP address, which can improve configurability options.

[0061] As mentioned above, Figure 1 are provided as examples. Other examples may vary from Figure 1 as described. Figure 1 The number and arrangement of the devices shown in the figure are provided as examples. In practice, there may be more than Figure 1 More devices, fewer devices, different devices, or differently arranged devices are shown. In addition, Figure 1 Two or more of the devices shown may be implemented in a single device, or Figure 1 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, Figure 1 The illustrated set of devices (e.g., one or more devices) may perform the operations described as being performed by Figure 1 Another group of devices is shown performing one or more functions.

[0062] Figure 2 is a schematic diagram of an example implementation 200 associated with an N3 virtual IP address and a CPRi virtual IP address.

[0063] Example implementation 200 includes subscriber equipment 205, access network 210 (e.g., wired access network), AGF-UP 215 (1)-215 (3) (e.g., AGF-UP devices), UPF 220 (1) and 220 (2), core router 225, AGF-CP 230 (e.g., AGF-CP device), and core network 235. Core network 235 may be a 5GC network including one or more 5G components, such as access and mobility management function (AMF) 240, session management function (SMF) 245, etc.

[0064] AGF-CP 230 may be configured to handle control plane operations on behalf of AGF-UP 215(1)-215(3), and core network 235 may be configured to handle control plane operations on behalf of UPF 220(1) and 220(2). For example, AGF-CP 230 may communicate with AMF 240, and SMF 245 may communicate with UPF 220(1) and 220(2).

[0065] AGF-UPs 215(1)-215(3) may communicate with AGF-CP 230 via CPRi tunnels 250(1)-250(3), respectively. For example, AGF-CP 230 may configure AGF-UPs 215(1)-215(3) with SGRP AC via CPRi tunnels 250(1)-250(3). Access network 210 and one or more of AGF-UPs 215(1)-215(3) may exchange network traffic belonging to SGRP A via pseudowire 1 (PS1), exchange network traffic belonging to SGRP B via pseudowire 2 (PS2), and / or exchange network traffic belonging to SGRP C via pseudowire 3 (PS3).

[0066] Table 255 shows the mapping of AGF-UP 215(1)-215(3) to SGRP AC, where "Interface 1" represents the active configuration and "Interface 2" represents the standby configuration. As shown in the figure, for SGRP A ("PS1"), AGF-UP 215(1) ("UP1") can be configured as the active AGF-UP, while AGF-UP 215(2) ("UP2") can be configured as the standby AGF-UP; for SGRP B ("PS2"), AGF-UP 215(2) can be configured as the active AGF-UP, while AGF-UP 215(3) ("UP3") can be configured as the standby AGF-UP; for SGRP C ("PS3"), AGF-UP 215(3) can be configured as the active AGF-UP, while AGF-UP 215(1) can be configured as the standby AGF-UP.

[0067] In some examples, AGF-CP 230 may preconfigure AGF-UPs 215(1) and 215(2) for SGRP A by transmitting a PFCP node association message to AGF-UPs 215(1) and 215(2). The PFCP node association message may indicate the status of AGF-UPs 215(1) and 215(2) of SGRP A, the virtual IP address associated with SGRP A and the N3 tunnel ("N3 virtual IP address XXXX"), and / or the virtual IP address associated with SGRP A and the CPRi tunnel ("CPRi virtual IP address YYYY"). For example, the status of AGF-UP 215(1) of SGRP A may be active, while the status of AGF-UP 215(2) of SGRP A may be standby. The N3 tunnel may be N3 tunnel 260(1) or N3 tunnel 260(2), while the CPRi tunnel may be CPRi tunnel 250(1). Thus, both AGF-UP 215(1) and AGF-UP 215(2) may obtain information (eg, N3 virtual IP address XXXX) for communicating with UPF 220(1) and / or UPF 220(2), but N3 virtual IP address XXXX may remain disabled on AGF-UP 215(2).

[0068] In some examples, subscriber device 205 may send a Dynamic Host Configuration Protocol (DHCP) packet via PS1, and access network 210 may transmit the DHCP packet to AGF-UP 215(1). Based on the DHCP packet, AGF-UP 215(1) may transmit an indication of the IP address of the subscriber device to AGF-CP 230, which may determine that the subscriber device belongs to SGRP A.

[0069] AGF-CP 230 may transmit a PFCP session establishment message containing information, including CPRi F-TEID, N3 F-TEID, etc., to AGF-UP 215(1) and 215(2). AGF-UP 215(1) may establish N3 tunnel 260(1) and / or N3 tunnel 260(2) with UPF 220(1) and / or UPF 220(2). Network traffic associated with subscriber device 205 may flow between AGF-UP 215(1) and UPF 220(1) and / or UPF 220(2) via N3 tunnel 260(1) and / or 260(2).

[0070] At some time thereafter, AGF-CP 230 may detect that AGF-UP 215(1) has failed and may signal a failover to at least AGF-UP 215(2). For example, for SGRP A, AGF-CP 230 may trigger AGF-UP 215(2) to change state from standby to active. In response to the state change, AGF-UP 215(2) may activate a virtual IP address. For example, AGF-UP 215(2) may use CPRi virtual IP address YYYY in CPRi F-TEID, which may be used as the endpoint ID of CPRi tunnel 250(1). Additionally or alternatively, AGF-UP 215(2) may use N3 virtual IP address XXXX in N3 F-TEID, which may be used as the endpoint ID of N3 tunnel 260(1) or N3 tunnel 260(2). AGF-UP 215(2) may publish updated routes to routing tables in the network connecting AGF-UP 215(1)-215(3) and UPF 220(1) and 220(2), and when the routes converge, network traffic may begin to flow between AGF-UP 215(2) and UPF 220(1) and / or 220(2). For example, as shown by reference numeral 265, N3 tunnels 260(1) and 260(2) may be migrated from AGF-UP 215(1) to AGF-UP 215(2).

[0071] As mentioned above, Figure 2 are provided as examples. Other examples may vary from Figure 2 as described. Figure 2 The number and arrangement of the devices shown in the figure are provided as examples. In practice, there may be more than Figure 2 More devices, fewer devices, different devices, or differently arranged devices are shown. In addition, Figure 2 Two or more of the devices shown in FIG. 1 may be implemented in a single device, or Figure 2 The single device shown in can be implemented as multiple distributed devices. Additionally or alternatively, Figure 2 The illustrated set of devices (e.g., one or more devices) may perform the operations described as being performed by Figure 2 Another group of devices is shown performing one or more functions.

[0072] Figure 3 is a schematic diagram of an example environment 300 in which the systems and / or methods described herein may be implemented. Figure 3 As shown, example environment 300 may include CPE 305, core network 310, and data network 370. Devices and / or networks of example environment 300 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections.

[0073] CPE 305 may include one or more devices capable of receiving, processing, storing, routing, and / or providing services (e.g., packets and / or other information or metadata) in a manner described herein. For example, CPE 305 may include a router, such as a label switching router (LSR), a label edge router (LER), an ingress router, an egress router, a provider router (e.g., a provider edge router or a provider core router), a virtual router, or other types of routers. Additionally or alternatively, CPE 305 may include a gateway, a switch, a firewall, a hub, a bridge, a reverse proxy, a server (e.g., a proxy server, a cloud server, or a data center server), a load balancer, and / or the like. In some embodiments, CPE 305 may be a physical device implemented in a housing such as a chassis. In some embodiments, CPE 305 may be a virtual device implemented by one or more computing devices of a cloud computing environment or a data center. In some embodiments, a group of CPE 305 may be a group of data center nodes for routing traffic flows through a network.

[0074] In some embodiments, the core network 310 may include an example functional architecture in which the systems and / or methods described herein may be implemented. For example, the core network 310 may include an example architecture of a fifth generation (5G) next generation (NG) core network included in a 5G wireless telecommunications system. Figure 3 The example architecture of the core network 310 shown may be an example of a service-based architecture, but in some embodiments, the core network 310 may be implemented as a reference point architecture and / or a 4G core network, etc.

[0075] like Figure 3 As shown, the core network 310 may include multiple functional elements. The functional elements may include, for example, a network slice selection function (NSSF) 315, a network exposure function (NEF) 320, an authentication server function (AUSF) 325, a unified data management (UDM) component 330, a policy control function (PCF) 335, an application function (AF) 340, an AMF 345, an SMF 350, a UPF 355, and / or an AGF 360. These functional elements may be communicatively connected via a message bus 365. Figure 3 Each of the functional elements shown is implemented on one or more devices associated with a wireless telecommunications system. In some embodiments, one or more functional elements may be implemented on a physical device, such as an access point, a base station, and / or a gateway. In some embodiments, one or more functional elements may be implemented on a computing device in a cloud computing environment.

[0076] NSSF 315 includes one or more devices that select network slice instances for CPE 305. By providing network slicing, NSSF 315 allows operators to deploy multiple substantially independent end-to-end networks that may have the same infrastructure. In some embodiments, each slice may be customized for different services.

[0077] NEF 320 includes one or more devices that support exposing capabilities and / or events in the wireless telecommunication system to help other entities in the wireless telecommunication system discover network services.

[0078] The AUSF 325 includes one or more devices that act as an authentication server and support the authentication process for the CPE 305 in the wireless telecommunications system.

[0079] The UDM 330 includes one or more devices that store user data and profiles in a wireless telecommunications system. The UDM 330 may be used in the core network 310 for fixed access and / or mobile access.

[0080] The PCF 335 includes one or more devices that provide a policy framework that includes examples such as network slicing, roaming, packet processing, and / or mobility management.

[0081] AF 340 includes one or more devices that support application programs' influence over traffic routing, access to NEF 320, and / or policy control, among other examples.

[0082] The AMF 345 includes one or more devices that serve as termination points for non-access stratum (NAS) signaling and / or mobility management, etc.

[0083] SMF 350 includes one or more devices that support the establishment, modification, and release of communication sessions in a wireless telecommunications system. For example, SMF 350 may configure service steering policies at UPF 355 and / or may implement UE IP address allocation and policies, and so on.

[0084] UPF 355 includes one or more devices that serve as anchor points for intra-radio access technology and / or inter-radio access technology mobility. UPF 355 may apply rules to packets, such as rules related to packet routing, service reporting, and / or handling user plane QoS.

[0085] AGF 360 includes one or more devices that provide authentication, authorization, and accounting (AAA) services as well as hierarchical traffic shaping and supervision for the fixed network and 5G residential gateways (e.g., CPE 305) provided by UPF 355.

[0086] The message bus 365 represents a communication structure for communication between functional elements. In other words, the message bus 365 can allow communication between two or more functional elements.

[0087] Data network 370 includes one or more wired and / or wireless data networks. For example, data network 370 may include an IP multimedia subsystem (IMS), a public land mobile network (PLMN), a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network (such as an intranet), an ad hoc network, the Internet, a fiber-based network, a cloud computing network, a third-party service network, an operator service network, and / or a combination of these or other types of networks.

[0088] Figure 3 The number and arrangement of devices and networks shown are provided as examples. In practice, there may be more than Figure 3 More devices and / or networks, fewer devices and / or networks, different devices and / or networks, or differently arranged devices and / or networks are shown. Figure 3 Two or more of the devices shown may be implemented in a single device, or Figure 3 The single device shown may be implemented as multiple distributed devices. Additionally or alternatively, one set of devices (eg, one or more devices) of the example environment 300 may perform one or more functions described as being performed by another set of devices of the example environment 300.

[0089] Figure 4 yes Figure 3 305, NSSF 315, NEF 320, AUSF 325, UDM component 330, PCF 335, AF 340, AMF 345, SMF 350, UPF 355, and / or AGF 360. In some embodiments, CPE 305, NSSF 315, NEF 320, AUSF 325, UDM component 330, PCF 335, AF 340, AMF 345, SMF 350, UPF 355, and / or AGF 360 may include one or more of devices 400 and / or one or more components of device 400. Figure 4 As shown, device 400 may include a bus 410 , a processor 420 , a memory 430 , an input component 440 , an output component 450 , and a communication interface 460 .

[0090] Bus 410 includes one or more components that enable wired and / or wireless communications between components of device 400. Bus 410 may Figure 4Two or more components of a computer system are coupled together, such as via an operational coupling, a communication coupling, an electronic coupling, and / or an electrical coupling. Processor 420 includes a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a controller, a microcontroller, a digital signal processor (DSP), a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), and / or another type of processing component. Processor 420 is implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, processor 420 includes one or more processors that can be programmed to perform one or more operations or processes described elsewhere herein.

[0091] Memory 430 includes volatile and / or non-volatile memory. For example, memory 430 may include random access memory (RAM), read-only memory (ROM), a hard drive, and / or another type of memory (e.g., flash memory, magnetic memory, and / or optical memory). Memory 430 may include internal memory (e.g., RAM, ROM, or hard drive) and / or removable memory (e.g., removable via a universal serial bus connection). Memory 430 may be a non-temporary 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 embodiments, memory 430 includes one or more memories such as coupled to one or more processors (e.g., processor 420) via bus 410.

[0092] Input assembly 440 enables device 400 to receive inputs, such as user inputs and / or sensed inputs. For example, input assembly 440 may include a touch screen, a keyboard, a keypad, a mouse, a button, a microphone, a switch, a sensor, a global positioning system sensor, an accelerometer, a gyroscope, and / or an actuator. Output assembly 450 enables device 400 to provide outputs, such as via a display, a speaker, and / or a light emitting diode. Communication interface 460 enables device 400 to communicate with other devices via wired connection and / or wireless connection. For example, communication interface 460 may include a receiver, a transmitter, a transceiver, a modem, a network interface card, and / or an antenna.

[0093] Device 400 may perform one or more operations or processes described herein. For example, a non-transitory computer-readable medium (e.g., memory 430) may store a set of instructions (e.g., one or more instructions or codes) implemented by processor 420. Processor 420 may execute the set of instructions to perform one or more operations or processes described herein. In some embodiments, the set of instructions is implemented by one or more processors 420 to enable one or more processors 420 and / or device 400 to perform one or more operations or processes described herein. In some embodiments, hard-wired circuit devices may be used instead of instructions or in combination with instructions to perform one or more operations or processes described herein. Additionally or alternatively, processor 420 may be configured to perform one or more operations or processes described herein. Therefore, the embodiments described herein are not limited to any particular combination of hardware circuit devices and software.

[0094] Figure 4 The number and arrangement of components shown are provided as examples. Device 400 may include Figure 4 More components, fewer components, different components, or differently arranged components are shown. Additionally or alternatively, one set of components (eg, one or more components) of device 400 may perform one or more functions described as being performed by another set of components of device 400.

[0095] Figure 5 yes Figure 3 305, NSSF 315, NEF 320, AUSF 325, UDM component 330, PCF 335, AF 340, AMF 345, SMF 350, UPF 355, and / or AGF 360. In some embodiments, CPE 305, NSSF 315, NEF 320, AUSF 325, UDM component 330, PCF 335, AF 340, AMF 345, SMF 350, UPF 355, and / or AGF 360 may include one or more of device 500 and / or one or more components of device 500. Figure 5 As shown, the device 500 may include one or more input components 510-1 to 510-B (B≥1) (hereinafter collectively referred to as input component 510, and individually referred to as input component 510), a switch component 520, one or more output components 530-1 to 530-C (C≥1) (hereinafter collectively referred to as output component 530, and individually referred to as output component 530) and a controller 540.

[0096] The input component 510 may be one or more attachment points of a physical link, and may also be one or more entry points for incoming traffic, such as packets. The input component 510 may process incoming traffic, for example, by performing data link layer encapsulation or decapsulation. In some embodiments, the input component 510 may transmit and / or receive packets. In some embodiments, the input component 510 may include an input line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more interface cards (IFCs), packet forwarding components, line card controller components, input ports, processors, memory, and / or input queues. In some embodiments, the device 500 may include one or more input components 510.

[0097] The switch component 520 can interconnect the input component 510 with the output component 530. In some implementations, the switch component 520 can be implemented via one or more crossbar switches, via a bus, and / or using a shared memory. The shared memory can act as a temporary buffer to store packets from the input component 510 before they are ultimately scheduled for delivery to the output component 530. In some embodiments, the switch component 520 can enable the input component 510, the output component 530, and / or the controller 540 to communicate with each other.

[0098] The output component 530 can store packets and can schedule packets to be transmitted on an output physical link. The output component 530 can support data link layer encapsulation or decapsulation and / or various higher-level protocols. In some embodiments, the output component 530 can transmit packets and / or receive packets. In some embodiments, the output component 530 may include an output line card, which includes one or more packet processing components (e.g., in the form of an integrated circuit), such as one or more IFCs, packet forwarding components, line card controller components, output ports, processors, memories, and / or output queues. In some embodiments, the device 500 may include one or more output components 530. In some embodiments, the input component 510 and the output component 530 may be implemented by the same set of components (e.g., the input / output component may be a combination of the input component 510 and the output component 530).

[0099] The controller 540 includes a processor in the form of a CPU, GPU, APU, microprocessor, microcontroller, DSP, FPGA, ASIC, and / or other types of processors. The processor is implemented in hardware, firmware, or a combination of hardware and software. In some embodiments, the controller 540 may include one or more processors that can be programmed to perform functions.

[0100] In certain embodiments, the controller 540 may include RAM, ROM, and / or another type of dynamic or static storage device (eg, flash memory, magnetic memory, optical memory, etc.) that stores information and / or instructions for use by the controller 540 .

[0101] In some embodiments, the controller 540 can communicate with other devices, networks, and / or systems connected to the device 500 to exchange information about the network topology. The controller 540 can create a routing table based on the network topology information, can create a forwarding table based on the routing table, and can forward the forwarding table to the input component 510 and / or the output component 530. The input component 510 and / or the output component 530 can use the forwarding table to perform routing lookups for incoming and / or outgoing packets.

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

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

[0104] Figure 5 The number and arrangement of components shown are provided as examples. In practice, the device 500 may include more than Figure 5 More components, fewer components, different components, or differently arranged components are shown. Additionally or alternatively, one set of components (eg, one or more components) of device 500 may perform one or more functions described as being performed by another set of components of device 500.

[0105] Figure 6 is a flow chart of an example process 600 associated with a virtual IP address associated with SGRP. In some embodiments, Figure 6 One or more process blocks are created by a network device (e.g., Figure 1 In some implementations, Figure 6One or more process blocks of the method are performed by another device or a group of devices that are separate from or include the network device, such as a CPE (e.g., CPE 305), a NSSF (e.g., NSSF 315), a NEF (e.g., NEF 320), an AUSF (e.g., AUSF 325), a UDM component (e.g., UDM component 330), a PCF (e.g., PCF 335), an AF (e.g., AF 340), an AMF (e.g., AMF 345), an SMF (e.g., SMF 350), a UPF (e.g., UPF 355), and / or an AGF (e.g., AGF 360). Additionally or alternatively, Figure 6 One or more process blocks may be performed by one or more components of device 400, such as processor 420, memory 430, input component 440, output component 450 and / or communication component 460, and / or one or more components of device 500, such as input component 510, switch component 520, one or more output components 530 and controller 540.

[0106] like Figure 6 As shown, process 600 may include transmitting an indication that the first AGF-UP device is associated with an active state of SGRP, an indication that the second AGF-UP device is associated with a standby state of SGRP, and an indication of a virtual IP address associated with SGRP (block 610). For example, as described above, the network device may transmit an indication that the first AGF-UP device is associated with an active state of SGRP, an indication that the second AGF-UP device is associated with a standby state of SGRP, and an indication of a virtual IP address associated with SGRP.

[0107] like Figure 6 As further shown, process 600 may include transmitting a failover indication that the second AGF-UP device is associated with an active state of the SGRP (block 620). For example, as described above, the network device may transmit a failover indication that the second AGF-UP device is associated with an active state of the SGRP.

[0108] Process 600 may include additional implementations, such as any single implementation or any combination of implementations described below, and / or be combined with one or more other processes described elsewhere herein.

[0109] In a first embodiment, a virtual IP address is associated with the local endpoint of the N3 tunnel.

[0110] In a second embodiment, either alone or in combination with the first embodiment, the virtual IP address is a first virtual IP address, and process 600 includes transmitting a second virtual IP address associated with an endpoint of the CPRi tunnel, and the second virtual IP address is different from the first virtual IP address.

[0111] In a third embodiment, either alone or in combination with the first embodiment, a virtual IP address is also associated with an endpoint of the CPRi tunnel.

[0112] In a fourth embodiment, either alone or in combination with one or more of the first to third embodiments, the F-TEID associated with the N3 tunnel is based on a virtual IP address.

[0113] In a fifth embodiment, alone or in combination with one or more of the first to fourth embodiments, the F-TEID associated with the UPF is associated with the N3 tunnel.

[0114] In a sixth embodiment, either alone or in combination with one or more of the first to fifth embodiments, a virtual IP address is associated with an endpoint of the CPRi tunnel.

[0115] In a seventh embodiment, either alone or in combination with one or more of the first to sixth embodiments, the F-TEID associated with the CPRi tunnel is based on a virtual IP address.

[0116] In an eighth embodiment, either alone or in combination with one or more of the first to seventh embodiments, a F-TEID associated with a network device is associated with a CPRi tunnel.

[0117] In a ninth embodiment, alone or in combination with one or more of the first to eighth embodiments, the network device is an AGF-CP device.

[0118] although Figure 6 Example blocks of process 600 are shown, but in some implementations, process 600 includes Figure 6 More blocks, fewer blocks, different blocks, or differently arranged blocks may be shown in FIG. Additionally or alternatively, two or more of the blocks of process 600 may be performed in parallel.

[0119] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the embodiments.

[0120] As used herein, a service or content may include a set of packets. A packet may refer to a communication structure for communicating information, such as a PDU, a service data unit (SDU), a network packet, a datagram, a segment, a message, a block, a frame (e.g., an Ethernet frame), a portion of any of the above, and / or another type of formatted or unformatted data unit capable of being transmitted via a network.

[0121] As used herein, the term "component" may be broadly interpreted as hardware, firmware, or a combination of hardware and software. It is apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, and / or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not a limitation to these embodiments. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it should be understood that, based on the description herein, software and hardware may be used to implement the systems and / or methods.

[0122] Even though specific combinations of features are listed in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of the various embodiments. In fact, many of these features may be combined in ways not specifically listed in the claims and / or disclosed in the specification. Although each dependent claim listed below may directly depend on only one claim, the disclosure of the various embodiments includes the combination of each dependent claim with every other claim in the claim set. As used herein, a phrase referring to "at least one" in a 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 of multiple identical items.

[0123] When "a processor" or "one or more processors" (or another device or component, such as "a controller" or "one or more controllers") is described or claimed (either within a single claim or across multiple claims) as performing or being configured to perform multiple operations, the language is intended to broadly encompass a variety of processor architectures and environments. For example, unless otherwise expressly stated (e.g., via the use of "a first processor" and "a second processor" or other language that distinguishes the processors in the claims), the language is intended to encompass a single processor that performs or is configured to perform all of the operations, a group of processors that collectively perform or are configured to perform all of the operations, a first processor that performs or is configured to perform a first operation and a second processor that performs or is configured to perform a second operation, or any combination of processors that perform or are configured to perform the operations. For example, when a claim is of the form "one or more processors to: perform X; perform Y; and perform Z," the claim should be interpreted to mean "one or more processors to perform X; one or more (possibly different) processors to perform Y; and one or more (possibly different) processors to perform Z."

[0124] Unless explicitly stated, any element, action or instruction used in this article should not be considered critical or necessary. In addition, as used herein, the article "a / an" is intended to include one or more items, and can be used interchangeably with "one or more". In addition, as used herein, the article "the" is intended to include one or more items associated with the article "the", and can be used interchangeably with "one or more". In addition, as used herein, the term "set" is intended to include one or more items (e.g., a combination of related items, unrelated items, or related and unrelated items), and can be used interchangeably with "one or more". If only one item is intended to be used, the phrase "only one" or similar language is used. In addition, as used herein, the term "has / have / having" etc. is intended to be an open term. In addition, unless otherwise explicitly stated, the phrase "based on (based on)" is intended to mean "based at least in part on (based, at least in part, on)". Furthermore, as used herein, the term "or" is intended to be inclusive when used in a series and is used interchangeably with "and / or" unless expressly stated otherwise (e.g., if used in conjunction with "either" or "only one of").

Claims

1. A method comprising: transmitting, by the network device, an indication of a first access gateway function user plane, AGF-UP, device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for the subscriber group, and an indication of a virtual Internet Protocol, IP, address associated with the subscriber group; as well as A failover indication of the second AGF-UP device associated with the activity state for the subscriber group is transmitted by the network device.

2. The method of claim 1, wherein the virtual IP address is associated with a local endpoint of the N3 tunnel.

3. The method according to claim 2, wherein the virtual IP address is a first virtual IP address, and the method further comprises: A second virtual IP address associated with an endpoint of a control packet redirection interface CPRi tunnel is transmitted by the network device, wherein the second virtual IP address is different from the first virtual IP address.

4. The method of claim 2, wherein the virtual IP address is also associated with an endpoint of a control packet redirection interface (CPRi) tunnel.

5. The method of claim 2, wherein a full tunnel endpoint identifier (F-TEID) associated with the N3 tunnel is based on the virtual IP address.

6. The method of claim 2, wherein a full tunnel endpoint identifier (F-TEID) associated with a user plane function (UPF) is associated with the N3 tunnel.

7. The method of claim 1, wherein the virtual IP address is associated with an endpoint of a Control Packet Redirection Interface (CPRi) tunnel.

8. The method of claim 7, wherein a full tunnel endpoint identifier (F-TEID) associated with the CPRi tunnel is based on the virtual IP address.

9. The method of claim 7, wherein a full tunnel endpoint identifier (F-TEID) associated with the network device is associated with the CPRi tunnel.

10. The method according to claim 1, wherein the network device is an Access Gateway Function Control Plane (AGF-CP) device.

11. A device comprising: one or more memories; as well as One or more processors to: transmitting an indication of a first access gateway function user plane, AGF-UP, device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for the subscriber group, and an indication of a virtual Internet Protocol, IP, address associated with the subscriber group, wherein the virtual IP address is associated with a local endpoint of an N3 tunnel; as well as Transmitting a failover indication of the second AGF-UP device associated with the activity state for the subscriber group.

12. The apparatus of claim 11, wherein the virtual IP address is a first virtual IP address, and wherein the one or more processors are further configured to: A second virtual IP address associated with an endpoint of a control packet redirection interface CPRi tunnel is transmitted, wherein the second virtual IP address is different from the first virtual IP address.

13. The apparatus of claim 11, wherein the virtual IP address is also associated with an endpoint of a Control Packet Redirection Interface (CPRi) tunnel.

14. The apparatus of claim 11, wherein a full tunnel endpoint identifier (F-TEID) associated with the N3 tunnel is based on the virtual IP address.

15. The apparatus of claim 11, wherein a full tunnel endpoint identifier (F-TEID) associated with a user plane function (UPF) is associated with the N3 tunnel.

16. A non-transitory computer readable medium storing a set of instructions, the set of instructions comprising: One or more instructions that, when executed by one or more processors of a device, cause the device to: transmitting an indication of a first access gateway function user plane, AGF-UP, device associated with an active state for a subscriber group, an indication of a second AGF-UP device associated with a standby state for a subscriber group, and an indication of a virtual Internet Protocol, IP, address associated with the subscriber group, wherein the virtual IP address is also associated with an endpoint of a control packet redirection interface, CPRi, tunnel; and Transmitting a failover indication of the second AGF-UP device associated with the activity state for the subscriber group.

17. The non-transitory computer-readable medium of claim 16, wherein a full tunnel endpoint identifier (F-TEID) associated with the CPRi tunnel is based on the virtual IP address.

18. The non-transitory computer-readable medium of claim 16, wherein a full tunnel endpoint identifier (F-TEID) associated with the device is associated with the CPRi tunnel.

19. The non-transitory computer-readable medium of claim 16, wherein the virtual IP address is a first virtual IP address, and wherein the one or more instructions, when executed by one or more processes of the device, further cause the device to: A second virtual IP address associated with a local endpoint of the N3 tunnel is transmitted, wherein the second virtual IP address is different from the first virtual IP address.

20. The non-transitory computer-readable medium of claim 16, wherein the virtual IP address is also associated with a local endpoint of an N3 tunnel.

Images