Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for automatically building an internet protocol (IP) network involves at a first network element, obtaining a first IP address from a Dynamic Host Configuration Protocol (DHCP) server, at the first network element, receiving a DHCP request from a second network element on an unnumbered interface of the first network element, and at the first network element, forwarding the DHCP request from the second network element to the DHCP server using the first IP address as a relay IP address.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for automatic Open Shortest Path First (OSPF) configuration involves at a first router, receiving OSPF communications from a second router and at the first router, deriving OSPF configuration for the first router based on the received OSPF communications to match OSPF configuration of the second router.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for automatically building an internet protocol (IP) network involves at a first network element, obtaining a first IP address from a Dynamic Host Configuration Protocol (DHCP) server, at the first network element, receiving a DHCP request from a second network element on an unnumbered interface of the first network element, and at the first network element, forwarding the DHCP request from the second network element to the DHCP server using the first IP address as a relay IP address.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for communications involves establishing a tunnel connection between a switch of a network and a gateway of the network and in response to a communications device connecting to a network port of the switch, conducting data traffic involving the communications device through the tunnel connection between the switch and the gateway.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for automatic network service configuration involves using a packet manager of a switch in a network, receiving a packet containing dynamic host configuration protocol (DHCP) request information from a network device in the network, and using the packet manager of the switch in the network, obtaining routing configuration and Address Resolution Protocol (ARP) configuration of the network device in response to the packet containing the DHCP request information.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method of communications involves at a head end (HE), receiving an authentication message from a wireless access point (AP) deployed at a customer site, at the HE, performing a load balance operation in response to the authentication message to select a first authenticator from authenticators of the HE, at the HE, performing an authentication operation using the first authenticator based on the authentication message to generate an authentication request, and from the HE, transmitting the authentication request to an authentication server.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method of automatic network service initiation involves obtaining, from a network service server at a first network device of a network service block (NSB), network address information using a network service client at a second network device of the NSB that is connected with the first network device, at the second network device of the NSB, obtaining network service configuration information based on the network address information, and, performing automatic network service initiation of the second network device of the NSB based on the network service configuration information.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method of automatic network service initiation involves obtaining, from a network service server at a first network device of a network service block (NSB), network address information using a network service client at a second network device of the NSB that is connected with the first network device, at the second network device of the NSB, obtaining network service configuration information based on the network address information, and, performing automatic network service initiation of the second network device of the NSB based on the network service configuration information.

Abstract: Embodiments of a device and method are disclosed. In an embodiment, a method for network management involves at a switch connected to redundant network devices, receiving a notification indicating that a first network device of the redundant network devices is active, where the redundant network devices share a first internet protocol (IP) address, and at the switch, configuring routing information to include a route to the first IP address via a second IP address of the first network device.

Abstract: A computer-implemented method for facilitating communications between two peer nodes in a network. The method comprises (a) configuring a first of the peer nodes to transmit a Path Maximum Transmission Unit (PMTU) request to a second of the peer nodes; wherein the PMTU request comprises a PMTU test value; (b) configuring the second peer node to transmit a PMTU reply responsive to receiving the PMTU request; said PMTU reply comprising a PMTU value set to match the PMTU test value in PMTU request; and (c) configuring the first peer node to determine a PMTU for the network based on determinations of fragmentation in connection with the PMTU reply.

Abstract: A computer-implemented method for facilitating communications between two peer nodes in a network. The method comprises (a) configuring a first of the peer nodes to transmit a Path Maximum Transmission Unit (PMTU) request to a second of the peer nodes; wherein the PMTU request comprises a PMTU test value; (b) configuring the second peer node to transmit a PMTU reply responsive to receiving the PMTU request; said PMTU reply comprising a PMTU value set to match the PMTU test value in PMTU request; and (c) configuring the first peer node to determine a PMTU for the network based on determinations of fragmentation in connection with the PMTU reply.

Abstract: A computer-implemented method for facilitating communications between two peer nodes in a network. The method comprises (a) configuring a first of the peer nodes to transmit a Path Maximum Transmission Unit (PMTU) request to a second of the peer nodes; wherein the PMTU request comprises a PMTU test value; (b) configuring the second peer node to transmit a PMTU reply responsive to receiving the PMTU request; said PMTU reply comprising a PMTU value set to match the PMTU test value in PMTU request; and (c) configuring the first peer node to determine a PMTU for the network based on determinations of fragmentation in connection with the PMTU reply.

Abstract: A charging detail record transmission capability is provided herein. A mobile gateway (MG) generates charging detail records (CDRs) intended for delivery to a charging gateway function (CGF). The CDRs are propagated toward both a first and second charging data function (CDFs). The first and second CDFs buffer the CDRs. The first CDF is configured for propagating CDRs toward the CGF. The second CDF is configured for propagating CDRs toward the CGF when the first CDF fails. The CGF is configured for acknowledging receipt of CDRs to the first or second CDF from which the CDRs are received. The first CDF is configured for acknowledging, to the second CDF, receipt of acknowledgment messages from the first CDF. The second CDF is configured for, upon failure of the first CDF, initiating a process for determining which of the CDRs buffered at the second CDF need to be propagated to the CGF.

Abstract: A charging detail record transmission capability is provided herein. A mobile gateway (MG) generates charging detail records (CDRs) intended for delivery to a charging gateway function (CGF). The CDRs are propagated toward both a first and second charging data function (CDFs). The first and second CDFs buffer the CDRs. The first CDF is configured for propagating CDRs toward the CGF. The second CDF is configured for propagating CDRs toward the CGF when the first CDF fails. The CGF is configured for acknowledging receipt of CDRs to the first or second CDF from which the CDRs are received. The first CDF is configured for acknowledging, to the second CDF, receipt of acknowledgment messages from the first CDF. The second CDF is configured for, upon failure of the first CDF, initiating a process for determining which of the CDRs buffered at the second CDF need to be propagated to the CGF.

Abstract: A charging detail record transmission capability is provided herein. A mobile gateway (MG) generates charging detail records (CDRs) intended for delivery to a charging gateway function (CGF). The CDRs are propagated toward both a first and second charging data function (CDFs). The first and second CDFs buffer the CDRs. The first CDF is configured for propagating CDRs toward the CGF. The second CDF is configured for propagating CDRs toward the CGF when the first CDF fails. The CGF is configured for acknowledging receipt of CDRs to the first or second CDF from which the CDRs are received. The first CDF is configured for acknowledging, to the second CDF, receipt of acknowledgment messages from the first CDF. The second CDF is configured for, upon failure of the first CDF, initiating a process for determining which of the CDRs buffered at the second CDF need to be propagated to the CGF in order to ensure that none of the CDRs generated by the MG are lost due to the failure of the first CDF.

Abstract: A system and method converting a unicast client request into a multicast client request is provided, the method comprising: receiving the unicast client request; mapping the unicast client request destination IP address and unicast client request destination port to a multicast record, wherein the multicast record contains a multicast destination internet protocol (IP) address and wherein the multicast destination IP address corresponds to the unicast client request destination IP address and unicast client request destination port; and transmitting the multicast client request that mirrors the received unicast client request to a plurality of destination servers using the multicast destination IP address that corresponds to the unicast client request destination IP address and unicast client request destination port.

Abstract: A charging detail record transmission capability is provided herein. A mobile gateway (MG) generates charging detail records (CDRs) intended for delivery to a charging gateway function (CGF). The CDRs are propagated toward both a first and second charging data function (CDFs). The first and second CDFs buffer the CDRs. The first CDF is configured for propagating CDRs toward the CGF. The second CDF is configured for propagating CDRs toward the CGF when the first CDF fails. The CGF is configured for acknowledging receipt of CDRs to the first or second CDF from which the CDRs are received. The first CDF is configured for acknowledging, to the second CDF, receipt of acknowledgment messages from the first CDF. The second CDF is configured for, upon failure of the first CDF, initiating a process for determining which of the CDRs buffered at the second CDF need to be propagated to the CGF in order to ensure that none of the CDRs generated by the MG are lost due to the failure of the first CDF.

Abstract: A system and method converting a unicast client request into a multicast client request is provided, the method comprising: receiving the unicast client request; mapping the unicast client request destination IP address and unicast client request destination port to a multicast record, wherein the multicast record contains a multicast destination internet protocol (IP) address and wherein the multicast destination IP address corresponds to the unicast client request destination IP address and unicast client request destination port; and transmitting the multicast client request that mirrors the received unicast client request to a plurality of destination servers using the multicast destination IP address that corresponds to the unicast client request destination IP address and unicast client request destination port.