Engineering Scope
Thread/Zigbee sleep terminals were developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, and develops dormant terminal polling, message reception, network disconnection detection and rejoining; delivers node firmware, network configuration, gateway dependencies and timing records according to the agreed modules.
Check input with baseline
Check the Thread or Zigbee protocol stack, parent node, gateway and downlink timeliness, and clarify the measurement and modification scope.
Implementation and adaptation
Develop dormant terminal polling, message reception, network disconnection detection and rejoining, and record solution choices and dependency conditions.
Target environment joint debugging
Test polling delay, parent node restart, loss of connection recovery and business consistency, and confirm the business behavior after parameter changes.
Document and record delivery
Provide node firmware, networking configuration, gateway dependencies and timing records, describing versions, construction or usage methods.
Project Workflow
- Enter confirmation: Thread or Zigbee protocol stack, parent node, gateway and downlink aging.
- Implementation method: Develop dormant terminal polling, message reception, network disconnection detection and rejoining.
- Phase review: Test polling delay, parent node restart, loss of connection recovery and business consistency.
- Project delivery: node firmware, networking configuration, gateway dependencies and timing records.
Design Conditions and Functional Limits
It needs to be confirmed according to the protocol role and device mode; the energy consumption conditions of continuous forwarding and dormant reception are different, and the infrastructure power supply responsibility should be clearly defined.
Special services take the agreed module as the implementation boundary. When hardware modifications, third-party agreements, overall platforms or external tests are involved, the interfaces, workload and responsibilities are confirmed separately, and local modifications are not directly used as conclusions on the performance of the complete device.
Project Inputs
- Thread or Zigbee protocol stack, parent node, gateway and downlink timeliness.
- Existing prototypes and reproducible problems, or new project functionality and power consumption targets.
- Modified design, source code and third-party dependencies are allowed; functionality and compatibility need to be maintained.
- Delivery list, target environment, sample scope, project milestones and acceptance methods.
Delivery and Acceptance
| Delivery content | Check method |
|---|---|
| Node firmware, networking configuration, gateway dependencies and timing records | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Test polling delay, parent node restart, loss of connection recovery and business consistency, and retain the corresponding working conditions and results. |
| Comparison of functions and power consumption | Fixed applicable hardware, software, battery, temperature and business cycles, accounting for changes in conditions and their impact. |
| Reproduction and follow-up maintenance | Provide build or run steps, known limitations, parameter ranges, and uncovered cases. |
Frequently Asked Questions
Can battery nodes also undertake continuous routing?+
It needs to be confirmed according to the protocol role and device mode; the energy consumption conditions of continuous forwarding and dormant reception are different, and the infrastructure power supply responsibility should be clearly defined.
What information do I need to prepare before starting the project?+
The focus of this work requires the Thread or Zigbee protocol stack, parent node, gateway and downlink timeliness. When the data is incomplete, first determine the scope that needs supplementary testing or sorting out, and then proceed to implementation.
Can it be implemented together with the complete device development project?+
It can be used as a work package in the overall project, or it can be implemented separately for existing products. It is necessary to explain the interfaces with other modules, versions and final machine verification responsibilities.
Engineering References
Sleeping terminals and continuous forwarding nodes have different tasks, and the network design needs to clearly define the node roles. Thread node role reference
Online
Phone
WeChat
Top