Starting from version 6.0.0(20), this kit supports network handover (multi-network concurrency).
Multi-network concurrency refers to the system capability to establish multiple network paths through provided APIs. When an app initiates a multi-network concurrency request, the device determines the concurrency combination based on the service scenario, applies corresponding concurrency controls, and evaluates the benefits of concurrency. The principles for using multi-network concurrency are: app-initiated requests (with restricted permissions), system-level governance, and minimal usage.
The functions involved in the process are as follows:
Concurrency listening: The app listens for any changes of the multi-network concurrency status. Meanwhile, the network subsystem of the device provides suggestions such as initiating or releasing multi-network concurrency.
Quota query: The app obtains the quota information of multi-network concurrency (including the used and remaining sessions and durations) to proactively manage and optimize the usage of multi-network concurrency.
Concurrency initiation: Before initiating multi-network concurrency, the app can proactively call the service scenario setting API to notify the device of entering a specific service scenario, and trigger multi-network concurrency through an explicit initiation API.
NIC binding: In the API for listening to the multi-network concurrency status, a newly acquired NIC is bound either by socket or by app.
Concurrency termination: When the app's network performance becomes normal, it must proactively release multi-network concurrency and call the service scenario setting API to notify the device of exiting the specific service scenario. The device may also proactively release multi-network concurrency to prevent misuse.
Benefit measurement: The consistency between app-reported transmission experience and device-calculated results is evaluated based on app feedback and system QoE algorithms.
Note: Multi-network concurrency is governed by factors such as the network acceleration switch setting, permission scope, quotas, and power consumption. Non-compliant behavior may trigger penalties, including but not limited to concurrency termination, quota reduction, and revocation of restricted permissions.