Engineering Scope
Wi-Fi/4G terminal intermittent networking was developed to solve specific engineering problems in low-power projects. The work starts from the customer's existing design and business requirements, compares connection maintenance, dormancy and power-off reconnection, sets batch transmission and task deadlines; delivers networking programs, policy parameters, complete connection cycle records and exception logs according to agreed modules.
Check input with baseline
Check the module, network, transmission size, connection delay and reception requirements, and clarify the scope of measurement and modification.
Implementation and adaptation
Compare connection maintenance, hibernation and power-off reconnection, set batch transmission and task deadlines, and record solution choices and dependency conditions.
Target environment joint debugging
Check the energy of authentication, link building, uploading, waiting, exiting and network disconnection recovery, and confirm the business behavior after parameter changes.
Document and record delivery
Provide networking programs, policy parameters, complete connection cycle records and exception logs, describing versions, construction or usage methods.
Project Workflow
- Enter confirmation: module, network, transfer size, connection delay and reception requirements.
- Implementation method: Compare connection maintenance, hibernation and power-off reconnection, and set batch transmission and task deadlines.
- Phase review: Check the energy of authentication, link building, uploading, waiting, exit and network disconnection recovery.
- Project delivery: networking procedures, policy parameters, complete connection cycle records and exception logs.
Design Conditions and Functional Limits
It is necessary to compare the consumption of the next startup, registration, authentication and connection reestablishment, and select according to the sending interval and network conditions. You cannot only compare the current during power outage.
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
- Module, network, transmission size, connection latency and reception requirements.
- 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 |
|---|---|
| Networking programs, policy parameters, complete connection cycle records and exception logs | Check the editability, version, usage instructions and dependencies by file list. |
| Implementation verification | Check the energy of authentication, link building, uploading, waiting, exiting and network disconnection recovery, 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
Is it more energy-saving to cut off the power immediately after each transmission?+
It is necessary to compare the consumption of the next startup, registration, authentication and connection reestablishment, and select according to the sending interval and network conditions. You cannot only compare the current during power outage.
What information do I need to prepare before starting the project?+
This work focuses on the module, network, transmission size, connection delay and reception requirements. 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