This article aims to deeply explore the technical details of Huawei's HarmonyOS Next system (as of API 12 currently) and is summarized based on actual development practices.
It is mainly used as a carrier for technical sharing and exchange. Inevitable errors and omissions may exist. Colleagues are welcome to put forward valuable opinions and questions for common progress.
This article is original content. Any form of reprint must indicate the source and original author.

I. Project Background and Demand Analysis

The background data synchronizer is a tool for automatically updating application data in an inactive state. It is suitable for applications such as weather and news. It can automatically start synchronization tasks according to conditions such as network and charging, which not only meets the real-time update needs of data but also effectively saves the power and resources of the device. Key requirements include:

• Regular data update: The background synchronizer updates weather, news and other data when conditions are met.
• Resource conservation: Avoid frequent scheduling to cause power consumption of the device, and at the same time optimize the operating efficiency of the synchronization task.

II. Technical Requirements and Challenges

To ensure the low-power operation and high efficiency of the background data synchronizer, the following key technical issues need to be solved:

1. Flexible task trigger conditions: Start tasks according to conditions such as Wi-Fi and charging status set by users to reduce consumption of mobile data traffic and battery power.
2. Control task execution frequency: Perform intelligent scheduling in different activity groups to reduce resource waste caused by high-frequency task execution.

III. Design Ideas

1. Task management and trigger condition design

In HarmonyOS Next, we can use deferred tasks (Deferred Task) to meet the data synchronization needs. Deferred tasks allow us to configure task trigger conditions, such as starting when connected to Wi-Fi or when charging, so that synchronization is performed only when device resource conditions permit, saving system resources. Deferred task trigger conditions include:

• Network type: Select to trigger tasks only under Wi-Fi to avoid consuming mobile traffic.
• Battery status: Can be set to execute when the device is charging or when the battery is sufficient to reduce battery consumption.

2. Architecture design and resource management

Using the task scheduling strategy and active grouping mechanism provided by HarmonyOS Next, the background data synchronizer can schedule tasks according to the usage frequency and resource situation of the application. HarmonyOS groups applications into different activity levels and limits task execution frequency for each group, greatly reducing resource waste.

IV. Key Technology Implementation

1. Configuration of deferred task trigger conditions

To achieve intelligent synchronization, we configure task trigger conditions through the WorkScheduler deferred task interface. The following is an example of a deferred task configuration for network and charging conditions:

import { workScheduler } from '@kit.BackgroundTasksKit';

// Create deferred task configuration
const syncWorkInfo = {
    workId: 1, // Set deferred task ID
    networkType: workScheduler.NetworkType.NETWORK_TYPE_WIFI, // Execute under Wi-Fi condition
    isCharging: true, // Start when charging
    bundleName: 'com.example.app', // Application package name
    abilityName: 'DataSyncAbility' // Ability of synchronization function
};

// Start deferred task
try {
    workScheduler.startWork(syncWorkInfo);
    console.info('Deferred task started successfully');
} catch (error) {
    console.error(`Deferred task start failed: ${error.message}`);
}

2. Task execution frequency control and system scheduling

HarmonyOS Next limits the execution frequency of background tasks within a certain range to ensure that applications in different groups do not frequently occupy system resources with low-frequency tasks. The background task scheduling system with WorkScheduler as the core can flexibly switch among the following groups:

• "Commonly used" group: Tasks are executed at most once every 24 hours and are suitable for applications that rely slightly on synchronization.
• "Rarely used" group: Only executed once every 48 hours and is suitable for applications that are rarely used.

This frequency management strategy ensures that tasks will not be triggered frequently, thus significantly reducing power consumption of the device.

3. Example code: Implementation of deferred task for background data synchronization task

The following code implements the complete configuration and control process of the background data synchronization task:

import { workScheduler } from '@kit.BackgroundTasksKit';
import { BusinessError } from '@kit.BasicServicesKit';

// Create work task instance
const dataSyncWorkInfo = {
    workId: 2, // Deferred task ID
    networkType: workScheduler.NetworkType.NETWORK_TYPE_WIFI, // Wi-Fi condition
    isCharging: true, // Execute when charging
    bundleName: 'com.example.app', // Application package name
    abilityName: 'DataSyncAbility' // Synchronization Ability
};

// Start data synchronization task
function startDataSyncTask() {
    try {
        workScheduler.startWork(dataSyncWorkInfo);
        console.info('Background data synchronization task started successfully');
    } catch (error) {
        console.error(`Background data synchronization task start failed, error code: ${error.code}, message: ${error.message}`);
    }
}

// Stop data synchronization task
function stopDataSyncTask() {
    try {
        workScheduler.stopWork(dataSyncWorkInfo);
        console.info('Background data synchronization task has stopped');
    } catch (error) {
        console.error(`Failed to stop data synchronization task, error code: ${error.code}, message: ${error.message}`);
    }
}

// Execute task
startDataSyncTask();

In this example, the data synchronization task will start when the conditions of Wi-Fi network and charging status are met. workId is used to uniquely identify the task for convenient subsequent operations such as pausing and canceling.

4. Example of frequency control

Based on deferred task scheduling, the start frequency of tasks can be controlled according to the usage frequency grouping of applications. For example, if an application is classified as the "rarely used" group, the execution interval of the data synchronization task will be automatically set to 48 hours to achieve energy-saving control.

V. Synchronizer optimization scheme and future extended application scenarios

Through the background task management capabilities of HarmonyOS Next, we have implemented an energy-saving data synchronizer triggered under different conditions and reduced the consumption of device resources. In the future, we can further optimize the execution conditions and frequency control strategies of data synchronization tasks to adapt to more application scenarios:

1. Dynamically adjust frequency: Dynamically adjust the data synchronization frequency by analyzing the application usage behavior of users. For example, increase the synchronization frequency when the application is active and reduce the frequency when the application is idle.
2. Extend other synchronization scenarios: Extend the data synchronizer to other scenarios that require background data processing, such as message push and cache cleaning.

VI. Summary

This article shows how to use HarmonyOS Next's deferred tasks and intelligent scheduling strategies through the implementation of an energy-saving background data synchronizer to achieve a balance between ensuring application data real-time and system resource consumption. The intelligent configuration of deferred tasks and system resource scheduling will help developers significantly optimize device power consumption while meeting user needs, providing solid technical support for energy-saving application development.