This section describes all of the properties and semantics required for managing a Thread(R) NCP.
Thread(R) NCPs have the following requirements:
PROP_INTERFACE_TYPE must be 3.All serious implementations of an NCP SHOULD also support the network save feature (See (#feature-network-save)).
The Thread(R) technology defines the following capabilities:
CAP_NET_THREAD_1_0 - Indicates that the NCP implements v1.0 of the Thread(R) standard.CAP_NET_THREAD_1_1 - Indicates that the NCP implements v1.1 of the Thread(R) standard.Properties for Thread(R) are allocated out of the Tech property section (see (#property-sections)).
6The IPv6 address of the leader. (Note: May change to long and short address of leader)
ESThe long address and short address of the parent of this node.
A(t(ES))Table containing the long and short addresses of all the children of this node.
CThe router-id of the current leader.
CThe leader weight of the current leader.
CThe leader weight for this node.
DThe local network data.
SDThe local stable network data.
SA(t(6CbCb))Data per item is:
6: IPv6 PrefixC: Prefix length in bitsb: Stable flagC: TLV flagsb: “Is defined locally” flag. Set if this network was locally defined. Assumed to be true for set, insert and replace. Clear if the on mesh network was defined by another node.A(t(6CbCbb))Data per item is:
6: Route PrefixC: Prefix length in bitsb: Stable flagC: Route preference flagsb: “Is defined locally” flag. Set if this route info was locally defined as part of local network data. Assumed to be true for set, insert and replace. Clear if the route is part of partition's network data.b: “Next hop is this device” flag. Set if the next hop for the route is this device itself (i.e., route was added by this device) This value is ignored when adding an external route. For any added route the next hop is this device.A(S)bSet to true before changing local net data. Set to false when finished. This allows changes to be aggregated into single events.
CThis property contains the value of the mode TLV for this node. The meaning of the bits in this bitfield are defined by section 4.5.2 of the Thread(R) specification.
LUsed when operating in the Child role.
SCLCAllows you to get or set the Thread(R) NETWORK_ID_TIMEOUT constant, as defined by the Thread(R) specification.
A(C) (List of active thread router ids)Note that some implementations may not support CMD_GET_VALUE router ids, but may support CMD_REMOVE_VALUE when the node is a leader.
bAllow the HOST to directly observe all IPv6 packets received by the NCP, including ones sent to the RLOC16 address.
Default value is false.
bAllow the HOST to indicate whether or not the router role is enabled. If current role is a router, setting this property to false starts a re-attach process as an end-device.
CCSpecifies the self imposed random delay in seconds a REED waits before registering to become an Active Router.
CSpecifies the preferred Router Id. Upon becoming a router/leader the node attempts to use this Router Id. If the preferred Router Id is not set or if it can not be used, a randomly generated router id is picked. This property can be set only when the device role is either detached or disabled.
A(t(ESLCcCbLL))Data per item is:
E: Extended/long addressS: RLOC16L: AgeC: Link Quality Inc: Average RSSC: Mode (bit-flags)b: true if neighbor is a child, false otherwise.L: Link Frame CounterL: MLE Frame CounterCSpecifies the maximum number of children currently allowed. This parameter can only be set when Thread(R) protocol operation has been stopped.
DThe leader network data.
DThe stable leader network data.
A(t(ULE))CAP_THREAD_COMMISSIONERData per item is:
U: PSKdL: Timeout in secondsE: Extended/long address (optional)Passess Pre-Shared Key for the Device to the NCP in the commissioning process. When the Extended address is ommited all Devices which provided a valid PSKd are allowed to join the Thread(R) Network.
bCAP_THREAD_COMMISSIONERSet to true to enable the native commissioner. It is mandatory before adding the joiner to the network.
bCAP_THREAD_TMF_PROXYSet to true to enable the TMF proxy.
dSSCAP_THREAD_TMF_PROXYData per item is:
d: CoAP frameS: source/destination RLOC/ALOCS: source/destination port| Octects: | 2 | n | 2 | 2 |
|---|---|---|---|---|
| Fields: | Length | CoAP | locator | port |
This property allows the host to send and receive TMF messages from the NCP's RLOC address and support Thread-specific border router functions.
bThis property specifies the value used in Thread(R) MLE Discovery Request TLV during discovery scan operation. Default value is false.
bThis property is used to enable/disable EUI64 filtering during discovery scan operation. Default value is false.
SThis property specifies the PANID used for filtering during discovery scan operation. Default value is 0xffff (broadcast PANID) which disables PANID filtering.
ECAP_OOB_STEERING_DATAThis property can be used to set the steering data for MLE Discovery Response messages.