The method includes: generating, by a first device, a first packet including a BIER header, where the BIER header includes entropy, and the entropy includes a first part and a second part; determining, by the first device based on the first packet, that there are a plurality of forwarding entries used to forward the first packet; selecting, by the first device, one forwarding entry from the plurality of forwarding entries based on the first part, where the selected forwarding entry includes an address of a second device, and the second device is a next-hop device of the first device; and sending, by the first device, the first packet to the second device, where the second part is used by the second device to select, from a plurality of forwarding entries used to forward the first packet, a forwarding entry used by the second device to forward the first packet.

A data multicast implementation method, apparatus, and system are provided. In some embodiments, a transmission device receives a standby forwarding path establishment request, where the standby forwarding path establishment request includes a device identifier, has a destination address being an address of a multicast source device, and is used to request to establish a standby forwarding path between a multicast destination device identified by the device identifier and the multicast source device. In those embodiments, when determining, based on the device identifier in the standby forwarding path establishment request, that the transmission device is located on an active forwarding path between the multicast destination device and the multicast source device, the transmission device skips using the transmission device as a device on the standby forwarding path between the multicast destination device and the multicast source device, and skips forwarding the standby forwarding path establishment request.

Described herein are methods and devices (e.g., routers) that add in-network services to a multiprotocol label switching (MPLS) network. A method can include a router of the MPLS network receiving a packet and modifying the packet by adding one or more MPLS extension headers, adding a header of the extension header(s), and adding an indication within an MPLS label stack that one or more MPLS extension headers have been added to the packet. The method can also include the router forwarding the packet as modified to another router of the MPLS network. In certain embodiments, an extension header label (EHL) within a label value field of a label stack entry indicates that one or more MPLS extension headers have been added to the packet. In other embodiments, a forward equivalent class (FEC) indicates that one or more MPLS extension headers follow the MPLS label stack.

Methods, systems, and devices for wireless communications are described. In some wireless systems, a base station centralized unit (CU) may communicate with a user equipment (UE) through a multi-hop backhaul architecture. This multi-hop backhaul connection may include a donor base station and any number of relay base stations connected via backhaul links. In some cases, the relay base stations or the UE may experience data congestion in a logical channel-specific buffer. The relay base stations or UE may implement backpressure signaling (e.g., in the medium access control (MAC) layer) to mitigate the congestion. A wireless device operating as a mobile termination (MT) endpoint may transmit a backpressure report message to a wireless device operating as a base station distributed unit (DU) endpoint for the logical channel. The base station DU may adjust a scheduling rate for data unit transmissions over the indicated logical channel based on the backpressure report.

An Internet of Things (IoT) platform is disclosed which includes: a network; a plurality of IoT servers coupled together and serviced by the network; a plurality of IoT managers coupled to each other and to the plurality of IoT servers; and a plurality of IoT devices electrically coupled to the plurality of IoT managers, wherein the IoT servers and the IoT managers of the present invention are operable to configure a plug-and-play and point to multipoint communication environment where the plurality of IoT devices, the plurality of IoT servers, and the plurality of IoT managers communicate with one another in a plug-and-play manner and in a point to multipoint manner regardless of their physical connections, industrial standards, and communication protocols.

The disclosed invention provide system and method to ensure resiliency in a network where audio capturing service experiences a failure on one or more active nodes. The network failover system is coupled to a Layer 3 (L3) network and communicates with a network switch through which network packets are transmitted. The failover system performs operations that include receiving network packets that are mirrored via the network switch, monitoring a primary node that captures audio data in the network packets, sending the network packets to a fallback node during an outage of the primary node, examining the network packets to determine which packets are audio-related packets, collecting audio-related packets, and storing the collected audio-related packets in a data storage. The fallback node is in the Layer 3 (L3) network.

Example methods are provided for a host to perform multicast packet handling a software-defined networking (SDN) environment. One example method may comprise: in response to detecting, from a virtualized computing instance supported by the host, a request to join a first inner multicast group address, obtaining an outer multicast group address that is assigned to the first inner multicast group address and one or more second inner multicast group addresses; and generating and sending a request to join the outer multicast group address to one or more multicast-enabled network devices. In response to detecting an ingress encapsulated multicast packet that includes an outer header addressed to the outer multicast group address and an inner header addressed to the first inner multicast group address, the host may generate and send a decapsulated multicast packet to the virtualized computing instance that has joined the first inner multicast group address.

A Protocol Independent Multicast (PIM) designated networking device election system includes a first networking device and a second networking device that are coupled to the first edge device. The second networking device receives a first PIM message from the first networking device and determines that the first PIM message indicates that the first networking device supports designated networking device election based on an interface performance property. The second networking device then determines whether a first interface performance property indication indicates that a first interface performance property of the first networking device or a second interface performance property of the second networking device satisfy an interface performance property condition. In response to determining that the second interface performance property satisfies the interface performance property condition, the second networking device forwards first data traffic received at the second networking device toward the first edge device.

In some embodiments, a method receives a selection of a logical router in the first computing device in a first site of a plurality of sites as a preferred egress point to an external network for the logical router. The logical router is instantiated on computing devices in the plurality of sites and a single site in the sites is the preferred egress point for the logical router. The method stores identification information for the logical router in a routing table that stores identification information for multiple logical routers. The identification information is unique among multiple logical routers. The method advertises via a routing instance in a control plane to other computing devices in other sites the identification information for the logical router to indicate the logical router in the first computing device in the first site is the preferred egress point.

Techniques are disclosed for seamless integration between a multicasting Virtual Private Network and an edge replicated multicast network. For example, a controller (e.g., software defined networking (SDN) controller) may facilitate the integration between a multicasting VPN network and an edge replicated multicast network through the selection of a multicast bridge node from virtual routers specified in the multicast replication tree, and sending information identifying the multicast bridge node to a provider edge (PE) device for the source VPN such that the PE device may use the information to steer multicast traffic from the source VPN site across the Layer 3 VPN network to the multicast bridge node of the receiver VPN site. When the multicast bridge node receives the multicast traffic, the multicast bridge node determines from the information that it is to receive the multicast traffic and to perform the edge replicated multicast using the edge replicated multicast tree.