Lines Matching refs:node
163 into a node successfully, it can be changed to a temporary Provisioner.
168 Enable the device to be provisioned into a node. This option should be
170 node and communicate with other nodes in the BLE Mesh network.
324 This option should be enabled if a node is going to be a Proxy Server.
332 This option determines for how long the local node advertises using
337 node, it will start to advertise using Node Identity during the time
346 This option specifies how many Proxy Filter entries the local node supports.
357 can use the GATT bearer to send mesh messages to a node that supports the
374 If the device is a BLE Mesh node, when this option is enabled, the configuration
402 If the node sends messages very frequently a higher value makes more
403 sense, whereas if the node sends infrequently a value as low as 0
415 gets written to persistent storage after a change occurs. If the node
417 node receives messages rarely, then the value can be as low as 0 (which
419 Note that if the node operates in a security-sensitive case, and there is
431 node information after mesh stack updates. In the old version mesh
433 mesh stack, key of "mesh/role" is added in nvs, recovering node
435 selective recovery of mesh node information. Therefore, there may
436 be failure in recovering node information during node restarting
441 the old version only supports storing node information.
445 in advance before recovering node information and make sure the node
500 Indeed, this value decides the number of the network keys which can be owned by a node.
508 … Indeed, this value decides the number of the application keys which can be owned by a node.
532 … Indeed, this value decides the number of the Virtual Addresses can be supported by a node.
541 The replay protection list is used to prevent a node from replay attack,
546 number of each node should also be taken into consideration. For example, if
547 Provisioner can provision up to 20 nodes and each node contains two elements,
572 A node is not required to cache the entire Network PDU and may cache
598 In order to fulfill the above requirement, even if the node might
600 how many hours the node has been in the state. This doesn't
603 ways that the node will be used and what kind of power source it
609 duration that the node has been in the current state gets
618 If a node in Normal Operation receives a Secure Network beacon with an IV index
619 equal to the last known IV index+1 and the IV Update Flag set to 0, the node may
622 Network beacon. The node makes the choice depending on the time since last IV
623 update and the likelihood that the node has missed the Secure Network beacons
667 models the local node supports, i.e. what's the largest
668 message payload that the node needs to be able to send.
690 a node to support the Relay feature, and the Relay feature can still
692 option will let a node not support the Relay feature.
721 is required by a node, this option should be enabled. And once the node
722 enters the mesh network, it will try to find a Friend node and establish a
732 reduced scan duty cycle. The downside of this is that the node may miss
734 with a Friend node.
735 When this option is enabled, the node will stop scanning for a period of
746 When an unprovisioned device is provisioned successfully and becomes a node,
747 enabling this option will trigger the node starts to send Friend Request at
748 a certain period until it finds a proper Friend node.
756 Time in seconds from the last received message, that the node waits out
772 The contribution of the RSSI, measured by the Friend node, used in Friend
775 node, which is used to calculate the Friend Offer Delay.
785 Low Power node, which is used to calculate the Friend Offer Delay.
793 number of maximum size Lower Transport PDUs that the Friend node can store
798 int "Receive delay requested by the local node"
802 The ReceiveDelay is the time between the Low Power node sending a
804 node time to prepare the response. The value is in units of milliseconds.
812 requests sent by a Low Power node. If no requests are received
813 the Friend node before the PollTimeout timer expires, then the
816 The smaller the value, the faster the Low Power node tries to get
817 messages from corresponding Friend node and vice versa.
867 Receive Window in milliseconds supported by the Friend node.
875 This option decides the size of each buffer which can be used by a Friend node
876 to store messages for each Low Power node.
883 Size of the Subscription List that can be supported by a Friend node for a
884 Low Power node. And Low Power node can send Friend Subscription List Add or
885 Friend Subscription List Remove messages to the Friend node to add or remove
894 A Friend node can have friendship with multiple Low Power nodes at the same time,
895 while a Low Power node can only establish friendship with only one Friend node at
996 Timeout value used by the node to get response of the acknowledged
1182 needs to be invoked to add the node information into the mesh stack.