Engineering Scope
The dormant device management platform and client are developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, managing sleep status, command queue, expiration processing, power trends and execution acknowledgments; delivering device models, server and client code, API and joint debugging records according to the agreed modules.
Check input with baseline
Check the equipment cycle, protocol, identity, command timeliness, authority and maintenance process, and clarify the scope of measurement and modification.
Implementation and adaptation
Manage sleep status, command queue, expiration processing, power trends and execution acknowledgments, and record plan choices and dependency conditions.
Target environment joint debugging
Test the status distinction between pending, received, successfully executed, and expired, and confirm the business behavior after parameter changes.
Document and record delivery
Provide device model, server and client code, API and joint debugging records, describing the version, construction or usage method.
Project Workflow
- Input confirmation: equipment cycle, protocol, identity, command aging, permissions and maintenance procedures.
- Implementation method: manage sleep status, command queue, expiration processing, power trend and execution acknowledgment.
- Phase review: Test the status distinction between pending receipt, received, successful execution and expired.
- Project delivery: equipment model, server and client code, API and joint debugging records.
Design Conditions and Functional Limits
The latest communication time and planned connection status should be displayed to distinguish between dormancy and lost connection, and avoid using the continuous online logo to cover up the temporary inability of the device to receive instructions.
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
- Equipment cycle, protocol, identity, command aging, permissions and maintenance procedures.
- 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 |
|---|---|
| Device model, server and client code, API and joint debugging records | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | The status of the test is to be received, received, executed successfully and expired, and the corresponding working conditions and results are retained. |
| 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 the device be displayed online on the platform while the device is sleeping?+
The latest communication time and planned connection status should be displayed to distinguish between dormancy and lost connection, and avoid using the continuous online logo to cover up the temporary inability of the device to receive instructions.
What information do I need to prepare before starting the project?+
This work focuses on equipment cycles, protocols, identities, command aging, permissions, and maintenance processes. 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
The power saving mode needs to check the network grant and the actual entry state, and the network search and retry under weak coverage should be measured separately. Cellular Power Consumption Analysis Reference
Online
Phone
WeChat
Top