Abstract: Methods and apparatus for use in reducing signal latency in a mobile network with use of localized Unified Data Management (UDM) entities are described. For example, the technique may employ a plurality of localized UDMs, where each localized UDM is associated with a unique location area. A localized UDM provides for storage of, in a localized Unified Data Repository (UDR), subscriber profile data associated with a subscriber of user equipment (UE). The subscriber profile data stored in the localized UDR may be a replica or copy of at least a subset of subscriber profile data for the subscriber stored in a UDR of a “centralized” UDM. Query access to the localized UDR may be provided for network functions (NFs) or subscriber/UEs. The replica or copy of subscriber profile data may be stored in the localized UDR for those subscribers having use in the location area.

Abstract: In one embodiment, an apparatus includes a memory, a communications interface and a processor. The processor is operatively coupled to the memory and the communications interface. The processor is configured to receive, at a first time, a label identifier associated with an aggregated link within the communications network via the communications interface. The aggregated link including a plurality of redundant links. The processor is configured to receive, at a second time after the first time, a data packet including the label identifier via the communications interface. The processor is configured to send at least a portion of the data packet via a first link separate from the aggregated link based on the label identifier. The processor is configured to not send the data packet via a link from the plurality of redundant links of the aggregated link based on the label identifier.

Abstract: The disclosure relates to performing a reliable broadcast from a source device to a plurality of nodes. In an aspect, a representative node establishes a first wireless communication link with each of one or more non-representative nodes, receives, from each of the one or more non-representative nodes, information indicating an ability of the one or more non-representative nodes to sniff wireless communications, establishes a second wireless communication link with the source device, configures the second wireless link based on the information received from the one or more non-representative nodes, sends control information for the second wireless communication link to each of the one or more non-representative nodes, and receives communications from the source device over the second wireless communication link, wherein the one or more non-representative nodes sniff the communications on the second wireless communication link based on the control information for that link.

Abstract: A network device receives, from another network device associated with a first data center, a route update that includes a common virtual network identifier or a first virtual network identifier associated with the first data center. The network device translates the common virtual network identifier or the first virtual network identifier to a second virtual network identifier associated with a second data center, where the second data center is different than the first data center. The network device provides the route update, with the second virtual network identifier, to the second data center.

Abstract: Systems, methods, and computer-readable media for managing service calls over a network may include a signal routing engine with a maintained forwarding table for various network functions and micro-services in a services back end for the network. The signal routing engine can include a call conversion service for converting REST API calls to an internal network call protocol for increasing network function processing speeds, decreasing bandwidth usage, and improving network responsiveness and manageability.

Abstract: The disclosure generally relates to using directionality to reduce flooding in a wireless mesh network. In an aspect, a node of the wireless mesh network receives a message for a destination node in the wireless mesh network, determines whether or not the message came from a direction of the destination node, drops the message based on determining that the message came from the direction of the destination node, and forwards the message based on determining that the message did not come from the direction of the destination node.

Abstract: A first device may receive information that identifies a second device. The second device may be connected to the first device or a third device. The second device may be a source of traffic to be received by the first device. The first device may determine whether the second device is local or remote to the first device based on receiving the information. The first device may store first information or second information based on determining whether the second device is local or remote. The first information may identify a route associated with the second device. The second information may identify a single route associated with multiple second devices. The first device may provide the traffic using the first information or the second information after storing the first information or the second information.

Abstract: The disclosure generally relates to congestion control, message analysis, and other improvements in a wireless mesh network. For example, according to various aspects, one or more devices in the wireless mesh network may be configured as monitoring nodes and a graph representing a message flow path in at least a portion of the wireless mesh network may be generated based at least in part on information related to one or more messages observed at the monitoring nodes. The graph can then be used to identify a path used to relay a message from at least one destination node to at least one source node (e.g., via one or more intermediate nodes). As such, a time-to-live (TTL) value to be used in messages communicated between the source node and the destination node can be appropriately configured based on a hop count between the source node and the destination node.

Abstract: This disclosure describes techniques for utilizing VXLANs within a network, such as a data center, for transporting L2 customer communications. Moreover, the disclosure describes techniques for auto-discovering, for each VXLAN, a corresponding replication node for replicating and distributing unknown destination, broadcast, and multicast frames to VXLAN Tunnel Endpoints (“VTEPs”) within the data center. Further, the techniques facilitate, by the replication node, discovery and auto-registration of the VTEPs for the respective customer network. As such, the techniques may facilitate configuration of VXLANs without necessarily relying on multicast protocols to provide such functionality. In this way, the techniques described herein may be used to supplement or even replace reliance on multicast protocols, such as the Protocol Independent Multicast (PIM) protocol, when configuring VXLANs within a network.

Abstract: A device may receive, via a first message, first route information for directing network traffic for a network. The first route information may identify a media access control (MAC) route corresponding to a MAC address associated with a host device connecting to a subnet of the network. The first route information may fail to include Internet protocol (IP)/MAC binding information associated with the host device. The device may transmit a request for IP/MAC binding information associated with the host device. The device may receive a response, to the request for IP/MAC binding information, identifying the IP/MAC binding information. The device may advertise, via a second message, second route information for directing network traffic for the network based on receiving the response identifying the LP/MAC binding information. The second route information may identify the IP/MAC binding information associated with the host device.

Abstract: A first device may receive information that identifies a second device. The second device may be connected to the first device or a third device. The second device may be a source of traffic to be received by the first device. The first device may determine whether the second device is local or remote to the first device based on receiving the information. The first device may store first information or second information based on determining whether the second device is local or remote. The first information may identify a route associated with the second device. The second information may identify a single route associated with multiple second devices. The first device may provide the traffic using the first information or the second information after storing the first information or the second information.

Abstract: In some embodiments, an apparatus includes a management module configured to assign a unique set of identifiers to each network control entity from a set of network control entities. As a result, a network control entity from the set of network control entities can assign an identifier from its unique set of identifiers to a port in response to that network control entity receiving a login request from the port. The set of network control entities is associated with a distributed multi-stage switch. The management module is also configured to store a zone set database associated with the distributed multi-stage switch. The management module is configured to send an instance of an active zone set stored within the zone set database to each network control entity from the set of network control entities such that each network control entity can enforce the active zone set.

Abstract: In some embodiments, a switch module is configured to receive from a first edge device a multicast data unit having a VLAN identifier. The switch module is configured to select a set of port modules based on the VLAN identifier. The switch module is configured to define an unmodified instance of the multicast data unit for each port module from the set of port modules. The switch module is configured to send the unmodified instance of the multicast data unit to each port module from the set of port modules, such that each port module applies a filter to the received instance of the multicast data unit to restrict that received instance of the multicast data unit from being sent to a second edge device via that port module if the second edge device is associated with a VLAN domain different than a VLAN domain of the first edge device.

Abstract: In some embodiments, a non-transitory processor-readable medium stores code representing instructions configured to cause a processor to receive, from an access switch, a first signal including forwarding state information associated with a first peripheral processing device from a set of peripheral processing devices. The code can further represent instructions configured to cause the processor to receive, from the first peripheral processing device, a second signal including a data packet. The code can further represent instructions configured to cause the processor to send, to a replication engine associated with the set of peripheral processing devices, a third signal such that the replication engine (1) defines a copy of the data packet, which is included within the third signal, and (2) sends, to a second peripheral processing device from the set of peripheral processing devices, a fourth signal including the copy of the data packet.

Abstract: A device may receive, via a first message, first route information for directing network traffic for a network. The first route information may identify a media access control (MAC) route corresponding to a MAC address associated with a host device connecting to a subnet of the network. The first route information may fail to include Internet protocol (IP)/MAC binding information associated with the host device. The device may transmit a request for IP/MAC binding information associated with the host device. The device may receive a response, to the request for IP/MAC binding information, identifying the IP/MAC binding information. The device may advertise, via a second message, second route information for directing network traffic for the network based on receiving the response identifying the IP/MAC binding information. The second route information may identify the IP/MAC binding information associated with the host device.

Abstract: In some embodiments, an apparatus includes a scheduler disposed at a control device of a switch fabric system. The scheduler is configured to receive a control plane request associated with the switch fabric system having a data plane and a control plane separate from the data plane. The scheduler is configured to designate a control plane entity based on the control plane request and state information of each control plane entity from a set of control plane entities associated with the control plane and instantiated as a virtual machine. The scheduler is configured to send a signal to a compute device of the switch fabric system in response to the control plane request such that the control plane entity is instantiated as a virtual machine at the compute device.

Abstract: In some embodiments, a system includes a set of network control entities associated with a distributed multi-stage switch. Each network control entity from the set of network control entities is configured to manage at least one edge device having a set of ports and coupled to the distributed multi-stage switch. Each network control entity from the set of network control entities is associated with a unique set of identifiers. A network control entity from the set of network control entities is configured to assign a unique identifier from its unique set of identifiers to a port from the set of ports of the at least one edge device in response to the network control entity receiving a login request associated with the port.

Abstract: In some embodiments, a non-transitory processor-readable medium stores code representing instructions configured to cause a processor to receive, from an access switch, a first signal including forwarding state information associated with a first peripheral processing device from a set of peripheral processing devices. The code can further represent instructions configured to cause the processor to receive, from the first peripheral processing device, a second signal including a data packet. The code can further represent instructions configured to cause the processor to send, to a replication engine associated with the set of peripheral processing devices, a third signal such that the replication engine (1) defines a copy of the data packet, which is included within the third signal, and (2) sends, to a second peripheral processing device from the set of peripheral processing devices, a fourth signal including the copy of the data packet.

Abstract: In some embodiments, an apparatus includes a first network control entity configured to be implemented at a first edge device. The first network control entity is configured to receive a control packet from a peripheral processing device via a tunnel that is between the peripheral processing device and the first network control entity and that includes at least a portion within a second edge device. The first network control entity is configured to determine routing information associated with the peripheral processing device based on the control packet. The first network control entity is configured to send the routing information to a second network control entity such that the second network control entity routes a data unit addressed to the peripheral processing device to the second edge device without sending the data unit to the first edge device.

Abstract: A device may receive, via a first message, first route information for directing network traffic for a network. The first route information may identify a media access control (MAC) route corresponding to a MAC address associated with a host device connecting to a subnet of the network. The first route information may fail to include Internet protocol (IP)/MAC binding information associated with the host device. The device may transmit a request for IP/MAC binding information associated with the host device. The device may receive a response, to the request for IP/MAC binding information, identifying the IP/MAC binding information. The device may advertise, via a second message, second route information for directing network traffic for the network based on receiving the response identifying the IP/MAC binding information. The second route information may identify the IP/MAC binding information associated with the host device.