Abstract:
In one embodiment, a device in a wireless network receives a request from a node in the network requesting electrical power. The device determines one or more power transmission parameters for the node. The device determines a power transmission schedule for the node. The device sends wireless network communications to the node in response to the request and based on the determined one or more power transmission parameters and transmission schedule for the node. The node converts the wireless network communications into stored electrical power.
Abstract:
In one embodiment, a device in a network determines whether a destination address of a packet received by the device is within a neighbor discovery (ND) cache of the device. The device determines whether the destination address is not in a set of addresses used to generate an address lookup array or possibly in the set of addresses used to generate the address lookup array, in response to determining that the destination address of the packet is not within the ND cache. The device performs address resolution for the destination address of the packet, in response to determining that the destination address of the packet is possibly in the set of addresses used to generate the address lookup array.
Abstract:
In one embodiment, a method comprises detecting a traffic condition by a network device in a loop-free routing topology comprising routing arcs for reaching a destination device, each routing arc comprising a first edge, a second edge, and at least a third network device configured for routing any network traffic along the routing arc toward the destination device and exiting via any one of the first or second edges of the routing arc, the traffic condition proximate to the first edge of at least one of the routing arcs in which the network device is positioned; and the network device initiating load balancing based on sending a management frame over a data plane of the at least one routing arc toward the corresponding second edge, the management frame requesting a change in load balancing for at least one of an identified traffic class based on the detected traffic condition.
Abstract:
In one embodiment, a scheduling device in a network receives routing metrics regarding a network path between a device controller and a networked device. The scheduling device also receives controller metrics for the device controller. The scheduling device determines time costs associated with the network path and one or more control operations performed by the device controller, based on the routing and controller metrics. The scheduling device generates a communication schedule based on the time costs and instructs the device controller and the networked device to use the communication schedule.
Abstract:
In one embodiment, a device in a network sets a timer interval based in part on a distance between the device and a backbone of the network. The device receives a unicast communication destined for a remote destination that was sent via broadcast. The device determines a count of receipt acknowledgements of the communication sent by other devices in the network. At the end of the timer interval, the device sends a receipt acknowledgement of the communication via broadcast, in response to the count of receipt acknowledgements sent by other devices in the network being below a threshold amount.
Abstract:
In one embodiment, a device in a network determines whether a destination address of a packet received by the device is within a neighbor discovery (ND) cache of the device. The device determines whether the destination address is not in a set of addresses used to generate an address lookup array or possibly in the set of addresses used to generate the address lookup array, in response to determining that the destination address of the packet is not within the ND cache. The device performs address resolution for the destination address of the packet, in response to determining that the destination address of the packet is possibly in the set of addresses used to generate the address lookup array.
Abstract:
In one embodiment, a device in a network receives metrics regarding a node in the network. The device uses the metrics as input to a machine learning model. The device determines, using the machine learning model and based on the metrics, an indication of abnormality of the node oscillating between using a plurality of different routing parents in the network. The device provides a results notification based on the indication of abnormality of the node oscillating between using the plurality of different routing parents.
Abstract:
In one embodiment, a particular node operates a distributed routing protocol in a shared-media communication network, and distributes timeslot allocations using the routing protocol, where the particular node as a parent node allocates a pool of timeslots available to child nodes of the parent node. The parent node specifically allocates particular timeslots from the pool to particular child nodes according to particular flows from a source to a target in the shared-media communication network in order to meet a defined time budget for a resultant time-synchronized path from the source to the target.
Abstract:
In one embodiment, a device in an anchorless network receives an update message from a first neighbor of the device. The update message indicates a movement of a node in the network to a new position in the network. The device updates a forwarding table of the device to reverse a link direction associated with the node, in response to receiving the update message. The device sends the update message to a second neighbor of the device towards a prior position of the node in the network.
Abstract:
In one embodiment, a device in a network determines whether a destination address of a packet received by the device is within a neighbor discovery (ND) cache of the device. The device determines whether the destination address is not in a set of addresses used to generate an address lookup array or possibly in the set of addresses used to generate the address lookup array, in response to determining that the destination address of the packet is not within the ND cache. The device performs address resolution for the destination address of the packet, in response to determining that the destination address of the packet is possibly in the set of addresses used to generate the address lookup array.