← Back to the chapter · Previous detail

Technical detail · WirelessHART Network Management

Count slot positions and forwarding opportunities

22.8 Under the Hood: Scheduling, Health, and Keys

The Network Manager's hardest job is the schedule. The manager assigns links using a slot and channel offset, along with the intended transmitter, receiver, graph and direction. That makes the plan analysable; it still depends on usable field links and enough scheduled resources. It then keeps a live picture from health reports — link quality, missed transmissions, retries, and queue behavior — and when a link degrades it recomputes routes and slots and pushes the updates out. That closed loop is why the network is self-healing without every device making independent routing decisions.

Put the schedule accounting into a concrete review. WirelessHART uses time-slotted communication, commonly discussed in 10 ms time slots. A 1 second repeating superframe therefore has 100 slot positions per channel-offset track. That does not mean all 100 are free for one sensor: links must be assigned to the right transmitter, receiver, graph, direction, and channel offset, and routing devices need forwarding links too. If a route change causes one router to forward 6 extra reports every 30 seconds and each forwarded report is given one normal opportunity plus one retry opportunity, the local schedule needs about 6 x 2 = 12 additional forwarding opportunities per 30-second period before diagnostics and management traffic.

Security is handled by the Security Manager, which owns the key hierarchy: a join key authenticates a device onto the network, a network key authenticates data-link-layer messages across the network, and session keys secure specific network-layer communication relationships. Keys are distributed and rotated centrally. A replacement device therefore has two independent gates: it must have acceptable identity and key material, and it must receive graph and schedule resources that keep plant data healthy.

Because management and security are centralized, the manager is a critical component, and serious deployments treat it as managed infrastructure rather than a convenience screen. The engineering evidence should include backup or redundancy expectations, the last known graph and schedule revision, who can approve joins, who can rotate keys, and how a failed manager or gateway would be detected. The same centralization that creates deterministic, secure behavior also creates an operations responsibility: every join, route, schedule, channel, and key-management change needs a record that another engineer can audit later.

Release rule: do not accept a management revision until join evidence, route diversity, schedule pressure, channel observations, key ownership, and rollback criteria are all recorded.

← Back to the chapter · Previous detail