Encoded intervals representation of the Thread link quality: * 3 (> 20 dB) * 2 (> 10 dB) * 1 (> 2 dB) * 0 (<= 2 dB) The Thread object is based on the Thread Group specifications: Thread 1.3.0 Specification {{bibref|ThreadSpec}}. It defines interface object ({{object|Radio}} and {{object|MLE}}), and application object ({{object|BorderRouter}}). {{numentries}} {{numentries}} {{numentries}} {{numentries}} The BorderRouter is capable of forwarding between a Thread Network and a non-Thread Network. Each BorderRouter entry is associated with a particular Thread Network (or MLE) instance via the {{param|MLEReference}} parameter. Enables or disables this border router. Indicates the status of this border router. Globally unique ID generated by the Thread Border Router. Define the Thread network to which it belongs. Define the routing and forwarding configuration of the BorderRouter, in order to access the Thread Network it manages. This is the way to manage ::/64 prefix used for global addressing of the mesh network (see Thread Specification {{bibref|ThreadIPv6Addressing}} "IPv6 Address Configuration"). This object models an 802.15.4 wireless radio ({{bibref|802.15.4-2020}}) on the device (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}). {{list}} List items represent supported transmit power levels as {{units}} of full power. For example, "0,25,50,75,100". A -1 item indicates auto mode (automatic decision by CPE). Auto mode allows the {{object}} to adjust transmit power accordingly. For example, this can be useful for power-save modes such as EU-CoC, where the {{object}} can adjust power according to activity in the CPE. Indicates the current transmit power level as a {{units}} of full power. The value MUST be one of the values reported by the {{param|TransmitPowerSupported}} parameter. A value of -1 indicates auto mode (automatic decision by device). This radio's Thread hardware version. This radio's Thread firmware version. This object models the Mesh Link Establishment (MLE) (a stackable interface object as described in {{bibref|TR-181i2|Section 4.2}}) used to establish and configure secure radio link of Thread network. The items in the list indicate the supported Thread version. The associated border router can only support one standard at a time. The operating standard this {{object}} instance is configured for. {{numentries}} {{numentries}} Indicates the leader data. The full Network Data Version the Node currently uses. The 8-bit {{param}} the Node attempts to utilize upon becoming a router or leader on the Thread network. The Thread Leader Partition ID for the Thread network to which the Node is joined. The Network Data Version for the stable subset of data the Node currently uses. The Thread Leader weight used when operating in the Leader role. Thread network configuration parameters are managed using an active and one optional pending Operational Dataset objects. The active Operational Dataset includes parameters (defined in the Thread specification, see {{bibref|ThreadSpec}}) that are currently in use across an entire Thread network. The active Operational Dataset contains: * Timestamp * Channel * Channel Mask * Extended PAN ID * Mesh-Local Prefix * Network Name * PAN ID * PSKc * Network key * Security Policy The pending Operational Dataset is used to communicate changes to the active Operational Dataset before they take effect. The pending Operational Dataset contains all the parameters from the Active Operational Dataset, with the addition of: Delay Timer. Indicates the status of this dataset. {{param}} of the dataset, depending status, it represent : * Active Timestamp (timestamp of the current dataset) * Pending Timestamp An unsigned 32-bit number in milliseconds indicate the Time Remaining when pending Dataset will be activated. This value MUST be 0 for active dataset. The IEEE 802.15.4 channel value of the interface defined in {{bibref|ThreadSpec}} (Thread specification only supports the 2450 MHz channels). The name of the network link to the interface. The IEEE 802.15.4 PAN ID value link to the interface. The IEEE 802.15.4 ExtPAN ID value link to the interface. Indicate the mesh-local IPv6 prefix for the Thread network. Indicates the channels within channel page 0, in the 2.4GHz ISM band. The channels are represented in most significant bit order, with bit value 1 meaning selected, bit value 0 meaning unselected. Pre-Shared Key Credential for inband commissioning. Key of the network. The {{object}} provide an administrator a way to enable or disable certain security related behaviors.  The rotation time of the security policy. The flags indicates the current security policies for the Thread partition of the current dataset. The {{param}} is an ordered concatenation of case sensitive characters containing list elements (may be empty). indicates that obtaining the Network Key for out-of-band commissioning is enabled indicates that Native Commissioning using PSKc is allowed indicates that Thread 1.x Routers are enabled indicates that external Commissioner authentication is allowed using PSKc Indicates that Thread 1.2 Commercial Commissioning is enabled indicate that autonomous Enrollment is enabled indicate that Network Key Provisioning is enabled indicates the Thread Network supports Commercial Commissioning Mode : CCM A table of the nodes currently associated to the Thread network defined by this {{object|##.MLE.}} instance. This includes the host nodes. The date and time in UTC when associated Thread node on the device has received data from remote node. Unique MacID of the node. Rloc of the node. The current state of the Thread node.  if the associated node is a Child, the {{object|Neighbor}} and {{object|Route}} tables MUST be empty Thread Device mode value. {{numentries}} {{numentries}} {{numentries}} Entries in this table reference nodes that are immediate neighbors of the associated node instance. This table is empty if the {{param|#.RoutingRole}} is not a {{enum|Router|#.RoutingRole}} or {{enum|Leader|#.RoutingRole}}. References the Thread node that is an immediate neighbor of the {{object|##.AssociatedNode}}. By construction the {{param|#.RoutingRole}} of {{object|##.AssociatedNode}} MUST be {{enum|Router|#.RoutingRole}} or {{enum|Leader|#.RoutingRole}}. The average Received Signal Strength Indicator (RSSI) is the average measurement of the signal strength received by the parent router node from the neighbor node. Entries in this table depend on the associated node routing capabilities defined by the {{param|#.RoutingRole}} and {{param|#.Mode}} according to the Thread Specification (i.e. a child node has an empty {{object}} table). It maintains information for each link to Router neighbor as follows:  * the Router ID assigned to that neighbor. * the routing cost. * the incoming link quality metric calculated from the measured link margin for messages received from the neighbor. * the incoming link quality metric reported by the neighbor for messages arriving from this Router.  Router ID of the route table entry. The routing cost advertised by the Next Hop to reach {{param|ID}}. Link Quality for messages received from {{param|ID}}, depending on the Link Margin value average of the received relative signal strength. Link Quality for messages sent to {{param|ID}}, depending on the Link Margin value average of the sent relative signal strength. This object represents the list of IPv6 addresses associated with the Thread node. The IPv6 address may be of one the following types. Enumeration of: * LinkLocal (Address reachable by a single radio transmission with the prefixes fe80::/16). * MeshLocal (Address reachable within the same Thread network with the prefix defined by the Thread network). * Global (Address reachable from outside a Thread network with the prefix provided by the Border Router). Router ID of the route table entry. The table of nodes hosted on the device. Unique MacID of the node.  The connectivity status. When {{true}} this {{object}} instance participates to the Thread network referenced by {{param|MLEReference}}. Connect the node to the Thread network managed by the Mesh Link Established. Start the BorderRouter Agent. Stop the BorderRouter Agent. Perform an IEEE 802.15.4 Active Scan ({{bibref|802.15.4-2020}}). This table list the set of PAN discovered and reachable from the node. Personal Area Network Identifier (ex: 0xFFFF). MAC Extended Address. Radio channels in the range [11-26]. Received Signal Strength Indicator, this field SHALL have the units of {{units}}, having the range -128 {{units}} to 0 {{units}}. Link Quality Indicator (LQI) depending on the Link Margin value average of the received relative signal strength. Perform an IEEE 802.15.4 Energy Scan ({{bibref|802.15.4-2020}} and {{bibref|ED_scan_802.15.4}}). Received Signal Strength Indicator for each channel in the range [11-26]. Radio channel in the range [11-26]. Received Signal Strength Indicator, this field SHALL have the units of {{units}}, having the range -128 {{units}} to 0 {{units}}. Create, or replace existing, {{object|Dataset}} instance. When this command is call : * if the {{object|Device.Thread.MLE.{i}.}} instance is enabled and {{param|Status}} is Up then all nodes attached to the interface receive the order to change their Dataset, * else the active Dataset is stored and will be activated when the {{object|Device.Thread.MLE.{i}.}} instance becomes enabled and Up. The TLV encodings for the active {{object|Dataset}} parameters that will be used across an entire Thread network. The active Operational Dataset TLVs encode : * Active Timestamp * Channel * Channel Mask * Extended PAN ID * Mesh-Local Prefix * Network Name * PAN ID * PSKc * Security Policy The encoding in {{param}} for the active Dataset field is defined in the Thread specification (see {{bibref|ThreadSpec}}). Create, or replace existing, pending {{object|Dataset}} instance with parameters provided in the TLVs. The TLV encodings for the pending Dataset parameters that will be use across an entire Thread network. The pending Operational Dataset TLVs encode : * Pending Timestamp * Channel * Channel Mask * Extended PAN ID * Mesh-Local Prefix * Network Name * PAN ID * PSKc * Security Policy The encoding in {{param}} for the pending Dataset field is defined in the Thread specification (see {{bibref|ThreadSpec}}). Get the TLVs of the active {{object|Dataset}} ({{param|Dataset.{i}.Status}} is active). The TLV encodings for the active Dataset parameters that will be use across an entire Thread network. The active Operational Dataset TLVs encode : * Active Timestamp * Channel * Channel Mask * Extended PAN ID * Mesh-Local Prefix * Network Name * PAN ID * PSKc * Security Policy The encoding in {{param}} for the active Dataset field is defined in the Thread specification (see {{bibref|ThreadSpec}}). Get the TLVs of the pending {{object|Dataset}} ({{param|Dataset.{i}.Status}} is pending). The TLV encodings the pending Dataset parameters that will be use across an entire Thread network. The pending Operational Dataset TLVs encode : * Pending Timestamp * Channel * Channel Mask * Delay Timer * Extended PAN ID * Mesh-Local Prefix * Network Name * PAN ID * PSKc * Security Policy The encoding in {{param}} for the pending Dataset field is defined in the Thread specification (see {{bibref|ThreadSpec}}). The {{command}} command provides a mechanism to obtain connectivity, topology, and link quality data from all the Thread devices in a Thread network (see {{bibref|ThreadSpec|Section Diagnostic Commands}}). On invocation, the agent sends a Thread Get Diagnostic Request to {{param|TargetIPv6Address}} (unicast or multicast address). This command requests the TLVs defined in the {{param|RequestedTLVTypes}} list. For unicast, the command completes on first response or timeout ({{param|RequestTimeout}}); for multicast, the agent aggregates all responses received before the {{param|RequestTimeout}} expires, then returns the set. The IPv6 destination address (unicast or multicast). In a Thread network, specific addresses are reserved for multicast use targeting different groups of devices, depending on the scope : * FF02::1 : "Link-Local All Nodes" multicast address, all Full Thread Devices (FTD) and Minimal End Devices (MED); * FF02::2 : "All-Routers" multicast address, all FTDs; * FF03::1 : "Realm-Local All-Nodes" multicast address, all FTDs and MEDs; * FF03::2 : "Realm-Local All-Routers" multicast address, all FTDs; List of requested TLV IDs as defined in {{bibref|ThreadSpec|Table Diagnostic TLVs}}. Examples of TLV IDs extracted from {{bibref|ThreadSpec}}, the number of defined TLV IDs in the Thread specification can increase in future releases: * 0x00 ExtMacAddress (Extended MAC Address (EUI‑64) of the radio interface) * 0x01 Address16 (Node’s 16‑bit RLOC address) * 0x02 Mode (Device mode flags (RX‑on‑when‑idle, FTD/MTD, FullNetData…)) * 0x03 Timeout (MLE timeout, notably for children) * 0x04 Connectivity (Connectivity indicators: parent priority, link qualities, cost to Leader…) * 0x05 Route64 (Routing information, router table, in Route64 format) * 0x06 LeaderData (Partition/leader data (PartitionId, Weighting, DataVersion…)) * 0x07 NetworkData (Full Network Data) * 0x08 IPv6AddressList (Node’s IPv6 address list) * 0x09 MacCounters (MAC counters (Tx/Rx, Retries, CCA failure, FCS error…)) * 0x0E BatteryLevel (Battery level if exposed) * 0x0F SupplyVoltage (Supply voltage if exposed) * 0x10 ChildTable (Child table (if Node acts as parent/router)) * 0x11 ChannelPages (Supported channel pages) * 0x12 TypeList (List of supported Network Diagnostics TLV types) * 0x13 MaxChildTimeout (Maximum child timeout (Thread 1.2+)) * 0x18 Version (Node’s Thread version) Overall time in {{units}} to wait for responses. One entry for each respondent Nodes to the {{command}} request. Source IPv6 address observed for the response (Mesh‑Local or Link‑Local), as received by the initiator. One entry per TLV returned by the Node. TLV ID in hexadecimal, as defined in {{bibref|ThreadSpec}} (also see examples from {{param|RequestedTLVTypes}}). Raw TLV value encoded in base64 (the Value field only; Type and Length excluded).