tron

interface-config-bluetooth-instance

Configures settings required to enable TRON-tracking and reporting.
TRON is a proprietary FedEx BLE asset-tracking application that tracks tagged packages moving through a distribution center. It is a multi-tier application consisting of the following elements:
  • ID Nodes – These are small, battery-powered Bluetooth Low Energy (BLE) devices attached to FedEx packages. Each ID Node is uniquely identified by its Bluetooth device address. The ID Node sends out BLE advertisements, with a payload containing information about the state and configuration of the ID Node.
  • Fixed Master Node (FMN) – This is the TRON software running on the AP. The FMN listens for BLE advertisements beaconed by the ID Nodes. When the FMN senses an ID Node, it records state and condition of the node and reports this information to the FedEx backend server. Changes in the ID Node state are also reported at regular interval.

    The FMN also connects to an ID Node to read/write arbitrary Generic Attribute Profile (GATT) attributes, as instructed by the backend server.

    WiNG APs can track up to 2000 ID Nodes at a time.

  • The FedEx backend provisioning server – This is a FedEx proprietary application that tracks the ID Nodes based on the information sent to it by the FMN.
  • Message Queuing Telemetry Transport (MQTT) Broker – All communication between the FMN and the backend server is through the MQTT Broker.

    MQTT is a standard publish-subscribe-based messaging protocol, which allows clients to exchange messages through an intermediate component, called the broker, A client (the publisher) publishes messages on a particular “topic” to the MQTT Broker, which filters these messages and forwards them correctly to other clients (the subscribers) that have subscribed to that “topic”. The FMN and FedEx backend server are the clients (publisher and subscriber) of the MQTT Broker.

To enable TRON tracking, you will need a controller with the TRON license applied and TRON-capable APs adopted to this controller. To TURN ON the TRON capability on a WiNG AP:
  • The adopting controller must explicitly ‘give permission‘ to the AP to enable the TRON feature. For this, apply the TRON license on the controller (NX5500, NX7500, NX9500, NX9600, and VX900). For more information on applying the TRON license, see license.
  • The AP should have the ‘initial configurations‘ set in its Bluetooth interface context. Use this command to set the initial configurations. See below for more information.
Note

Note

Before setting the initial configurations, set the AP‘s bluetooth radio mode to tron-tracking. For more information, see mode.

TRON GPS Enhancement

WiNG 7.3.1 introduces an enhanced TRON software. Going forward, TRON-capable WiNG APs will include the AP‘s GPS coordinates in the updates sent to the FedEx backend server. The following commands are associated with this new capability:
  • geo-coordinates <LATITUDE> <LOGITUDE> - Use this command to configure the AP‘s GPS coordinates.
  • show gps coordinates – Use this command to check the AP‘s GPS coordinates.

Supported in the following platforms

Syntax

tron [delete-operating-config-on-start|ignore-mqtt-truststore|initial-config|reconstruct-nodetype-db-on-start]
tron delete-operating-config-on-start
tron ignore-mqtt-truststore
tron initial-config mqtt [client-prefix <WORD>|password <WORD>|port <1025-65535>|
server [<IP>|<HOST-NAME>]|topic-publish-prefix <LINE>|topic-subscribe-prefix <LINE>|username <WORD>]
tron reconstruct-nodetype-db-on-start

Parameters

tron delete-operating-config-on-start
tron delete-operating-config-on-start Enables the TRON software, on the AP, to delete the TRON “operating configuration” before starting any other TRON operations. Issue this command only if you wish to reload the operating configuration from the provisioning server.

When the TRON software up for the first time, it uses the "initial-configuration" to connect with the backend provisioning server and download the operating configuration. This operating configuration is stored in the AP‘s file system and it persists across TRON enable/disable operations and AP reboots. To delete the "operating configuration" execute this command.

After the operating configuration has been deleted, the AP re-connects to the provisioning server and downloads the operating configuration. After the download is complete, issue the no → tron delete-operating-config-on-start command to retain the new operating configuration across reboots and enable/disable operations.

Note: To view the operating configuration, execute the show → tron → operating-configuration → {on <AP-NAME>} command. For more information, see tron (show command).
tron ignore-mqtt-truststore
tron ignore-mqtt-truststore Enable this option to force the MQTT functionality on the AP to use URIs beginning with tcp: and not ssl:.

When enabled, the TRON software, on starting up, ignores existing MQTT truststore (aka, certificate file), and uses a URI that begins with tcp: instead of ssl:. This option disabled by default.

Note: If you execute this command while the TRON software is up and running, it will have no effect until you restart the TRON software.
tron initial-config mqtt [client-prefix <WORD>|password <WORD>|port <1025-65535>|
server [<IP>|<HOST-NAME>]|topic-publish-prefix <LINE>|topic-subscribe-prefix <LINE>|username <WORD>]
tron initial-config mqtt Sets the initial configurations required by the TRON-capable WiNG AP to recognize and associate with the MQTT Broker. After associating with the Broker, the WiNG AP begins exchanging messages with the FedEx backend server. This FedEx backend server downloads the operating configuration to the AP.
Note: The initial configurations are mandatory. However, once the AP is provisioned with the FedEx proprietary operating configuration, the initial configuration is ignored. To view the operating configuration, execute the show → tron → operating-configuration → {on <AP-NAME>} command. For more information, see tron (show command).
Note: The FMN also connects to an ID Node to read/write arbitrary GATT attributes, as instructed by the back-end server.
client-prefix <WORD> Configures the MQTT client‘s prefix
  • <WORD> – Provide the prefix (should not exceed 16 characters in length).
Note: The default value is ‘FMN‘.
password <WORD> Configures the password required to authenticate with the MQTT Broker. You will need a username/password combination in order for the FMN to authenticate and associate with the MQTT Broker. Use the ‘username‘ and ‘password‘ options to specify the username and password respectively.
  • <WORD> – Specify the password either as clear text or as encrypted text. In case of clear text, the password should not exceed 32 characters in length).
Note: The password is displayed as clear or encrypted text depending on whether or not ‘password encryption‘ has been enabled on the AP. For more information on enabling password-encryption, see password-encryption .
port <1025-65535> Configures the port on which the MQTT Broker is reachable
  • <1025-65535> – Provide the port number form 1025 - 65535.
Note: The default value is 61613.
server [<IP>|<HOST-NAME>] Identifies the MQTT server either by its IP address or hostname. This the server hosting the MQTT Broker.
  • <IP> – Provide the server‘s IP address in the A.B.C.D format.
  • <HOST-NAME> – Provide the server‘s hostname.
Note: The hostname should not exceed 255 characters in length.
topic-publish-prefix <LINE> Configures the prefix of the topic published by the FMN
  • <LINE> – Specify the publish topic prefix.
Note: The input should not exceed 255 characters in length.
topic-subscribe-prefix <LINE> Configures the prefix of the topic subscribed by the FMN
  • <LINE> – Specify the subscribe topic prefix.
Note: The input should not exceed 255 characters in length.
username <WORD> Configures the username required to authenticate with the MQTT Broker. You will need a username/password combination in order for the FMN to authenticate and associate with the MQTT Broker. Use the ‘username‘ and ‘password‘ options to specify the username and password respectively.
Note: The username should not exceed 32 characters in length.
tron reconstruct-nodetype-db-on-start
tron reconstruct-nodetype-db-on-start Enables reconstruction of the node-type database. When enabled, the TRON software (FMN) discards existing database and on-the-fly, reconstructs a database containing “node-type” to a specific layout of GATT services and characteristics mappings.

Each ID Node, within a physical space, sends out Bluetooth advertisements that includes the ‘node-type‘ (for example, 0x11) information. When the TRON functionality on the WiNG AP, connects to an ID Node for the first time, it discovers and caches the ID Node‘s layout for GATT services and characteristics in the ‘node-type‘ database/table. Subsequent GATT discovery of other ID Nodes is skipped on the assumption that ID Nodes advertising the same node-type value as the first ID Node will have the same layout for their GATT services and characteristics. This node-type database, created at the first instance of connection, persists across AP reboots and enabling/disabling of the TRON functionality on the AP. If on the ID Nodes, the layout of the GATT services and characteristics changes (post database creation), the existing database is no longer valid. In this scenario, use this command to discard the existing database and recreate a new one.

Note: This parameter is not mandatory, and is disabled by default.

Examples

NOC-NX9500(config-profile-test8533-if-bluetooth1)#tron initial-config mqtt client-prefix fmn
NOC-NX9500(config-profile-test8533-if-bluetooth1)#tron initial-config mqtt server 1.2.3.4
NOC-NX9500(config-profile-test8533-if-bluetooth1)#tron initial-config mqtt topic-publish-prefix idnodes
NOC-NX9500(config-profile-test8533-if-bluetooth1)#tron initial-config mqtt topic-subscribe-prefix idnodes
NOC-NX9500(config-profile-test8533-if-bluetooth1)#tron initial-config mqtt username fmn
NOC-NX9500(config-profile-test8533-if-bluetooth1)#show context
 interface bluetooth1
  shutdown
  mode tron-tracking
  tron initial-config mqtt server 1.2.3.4
  tron initial-config mqtt username fmn
  tron initial-config mqtt password 0 fmn@1234
  tron initial-config mqtt client-prefix fmn
  tron initial-config mqtt topic-publish-prefix idnodes
  tron initial-config mqtt topic-subscribe-prefix idnodes
NOC-NX9500(config-profile-test8533-if-bluetooth1)#
Following command configures the GPS coordinates of the AP. When configured, the GPS coordinates are posted by the TRON software, running on the AP, to the FedEx backend server.
ap460-FD2E50(config-device-48-9B-D5-FD-2E-50)#geo-coordinates 43.8385367 -79.3817021
ap460-FD2E50(config-device-48-9B-D5-FD-2E-50)#commit
ap460-FD2E50(config-device-48-9B-D5-FD-2E-50)#show context
ap460 48-9B-D5-FD-2E-50
 use profile default-ap460
 use rf-domain default
 hostname ap460-FD2E50
 geo-coordinates 43.8385367 -79.3817021
--More--
ap460-FD2E50(config-device-48-9B-D5-FD-2E-50)

Following command displays the AP's GPS coordinates.

ap460-FD2E50#show gps coordinates

Last location recorded at UTC time : Wed Jan 1 00:19:16 2020 :  Latitude : 43.8385367 Longitude : -79.3817021
ap460-FD2E50#

Related Commands

no (bluetooth-inf-config-command) Removes the TRON related configurations set on this Bluetooth radio.