Abstract: Systems and methods are disclosed for selecting a parent node in a time-slotted channel hopping (“TSCH”) network. A method can include synchronizing, by a low-energy node, communications with a channel hopping pattern of a primary TSCH network. The method can further include transmitting, by the low-energy node, a selection-phase enhanced beacon request that requests an enhanced beacon from TSCH nodes with availability to accept children and with at least a specified link quality using the synchronized communications. The method can further include receiving, by the low-energy node, a selection-phase enhanced beacon from a TSCH node. The method can further include transmitting, by the low-energy node, an adoption request to the TSCH node. The method can further include receiving, by the low-energy node, an adoption response from the TSCH node indicating the TSCH node is managing the primary TSCH network join on behalf of the low-energy node.

Abstract: Systems and methods are disclosed for interleaving communications with a home area network (HAN) and a data network. A gateway device interleaves communications within timeslots of a time slotted channel hopping protocol. A gateway device can be configured to determine, during a first portion of a timeslot, whether the gateway device received a portion of a message from a data network. If the gateway device receives no messages from the data network during the first portion of the timeslot, the gateway device switches to listen for communication from the HAN during a second portion of the timeslot. If the gateway device receives a portion of the message from the HAN, the gateway device continues to receive receives the remainder of the message until one or more trigger conditions that cause the gateway device to listen for communication from the data network.

Abstract: Systems and methods are provided for maintaining a low power endpoint (LPE) synchronized on a time synchronized channel hopping network (TSCH). An LPE receives a guaranteed time slot (GTS) from a parent node. The LPE determines a wake-up time that coincides with or is prior to the GTS. The LPE enters a low power mode to conserve power until the wake-up time occurs. At that time, the LPE enters a regular power mode and may communicate with the parent node.

Abstract: Systems and methods are disclosed for interleaving communications with a home area network (HAN) and a data network. A gateway device interleaves communications within timeslots of a time slotted channel hopping protocol. A gateway device can be configured to determine, during a first portion of a timeslot, whether the gateway device received a portion of a message from a data network. If the gateway device receives no messages from the data network during the first portion of the timeslot, the gateway device switches to listen for communication from the HAN during a second portion of the timeslot. If the gateway device receives a portion of the message from the HAN, the gateway device continues to receive receives the remainder of the message until one or more trigger conditions that cause the gateway device to listen for communication from the data network.

Abstract: An IP packet may include an IP header and one or more optional IP extension headers. The packet may contain non-IP protocol data in one of the IP extension headers. An application that uses non-IP protocol data may use the non-IP protocol data from the IP extension header. This allows an application designed for a non-IP protocol stack to operate on a device with an IP protocol stack with minimal modification. The non-IP protocol data may alternatively support non-IP routing options within a network or sub-network.

Abstract: A node receives status data associated with a current collector in the network, where the node is active on the current collector. The node also receives status data associated with a candidate collector in the network, where the node is not active on the candidate collector. An analysis of the status data of the collectors is generated, where the analysis includes at least comparing respective network loads reported in the received status data. An optimal collector is determined from among the current collector and the candidate collector. The determination of the optimal collector is based at least in part upon the analysis of the status data of the collectors. The node remains active on the current collector when the current collector is determined to be the optimal collector, and the node becomes active on the candidate collector when the candidate collector is determined to be the optimal collector.

Abstract: Systems and methods are disclosed for selecting a parent node in a time-slotted channel hopping (“TSCH”) network. A method can include synchronizing, by a low-energy node, communications with a channel hopping pattern of a primary TSCH network. The method can further include transmitting, by the low-energy node, a selection-phase enhanced beacon request that requests an enhanced beacon from TSCH nodes with availability to accept children and with at least a specified link quality using the synchronized communications. The method can further include receiving, by the low-energy node, a selection-phase enhanced beacon from a TSCH node. The method can further include transmitting, by the low-energy node, an adoption request to the TSCH node. The method can further include receiving, by the low-energy node, an adoption response from the TSCH node indicating the TSCH node is managing the primary TSCH network join on behalf of the low-energy node.

Abstract: An IP packet may include an IP header and one or more optional IP extension headers. The packet may contain non-IP protocol data in one of the IP extension headers. An application that uses non-IP protocol data may use the non-IP protocol data from the IP extension header. This allows an application designed for a non-IP protocol stack to operate on a device with an IP protocol stack with minimal modification. The non-IP protocol data may alternatively support non-IP routing options within a network or sub-network.

Abstract: An IP packet may include an IP header and one or more optional IP extension headers. The packet may contain non-IP protocol data in one of the IP extension headers. An application that uses non-IP protocol data may use the non-IP protocol data from the IP extension header. This allows an application designed for a non-IP protocol stack to operate on a device with an IP protocol stack with minimal modification. The non-IP protocol data may support routing options within a network or sub-network.

Abstract: A node receives status data associated with a current collector in the network, where the node is active on the current collector. The node also receives status data associated with a candidate collector in the network, where the node is not active on the candidate collector. An analysis of the status data of the collectors is generated, where the analysis includes at least comparing respective network loads reported in the received status data. An optimal collector is determined from among the current collector and the candidate collector. The determination of the optimal collector is based at least in part upon the analysis of the status data of the collectors. The node remains active on the current collector when the current collector is determined to be the optimal collector, and the node becomes active on the candidate collector when the candidate collector is determined to be the optimal collector.

Abstract: Systems and methods are provided for maintaining a low power endpoint (LPE) synchronized on a time synchronized channel hopping network (TSCH). An LPE receives a guaranteed time slot (GTS) from a parent node. The LPE determines a wake-up time that coincides with or is prior to the GTS. The LPE enters a low power mode to conserve power until the wake-up time occurs. At that time, the LPE enters a regular power mode and may communicate with the parent node.

Abstract: An IP packet may include an IP header and one or more optional IP extension headers. The packet may contain non-IP protocol data in one of the IP extension headers. An application that uses non-IP protocol data may use the non-IP protocol data from the IP extension header. This allows an application designed for a non-IP protocol stack to operate on a device with an IP protocol stack with minimal modification. The non-IP protocol data may support routing options within a network or sub-network.