Go to file
openharmony_ci a925c2f070
!377 support mission label updated
Merge pull request !377 from ccll/master
2022-09-09 08:06:13 +00:00
etc distributed data api switching 2022-07-30 16:15:56 +08:00
figures update readme 2022-02-25 09:48:55 +08:00
interfaces modify gn 2022-09-02 09:49:23 +08:00
sa_profile delete useless code 2022-07-27 19:31:40 +08:00
services !377 support mission label updated 2022-09-09 08:06:13 +00:00
utils/native/include remove zuri from dmsfwk 2022-03-21 14:34:24 +08:00
.gitattributes update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
bundle.json DMS 上报应用信息 2022-08-27 17:10:30 +08:00
dmsfwk.gni upload distributed component to memmgr 2022-08-29 21:14:22 +08:00
hisysevent.yaml 修改HisysEvent封装函数 2022-06-27 16:45:49 +08:00
LICENSE update OpenHarmony 2.0 Canary 2021-06-02 02:21:10 +08:00
OAT.xml sync code to master 2021-12-21 23:26:50 -08:00
README_zh.md !286 【OpenHarmony开源贡献者计划2022】修改readme 2022-08-01 02:23:13 +00:00
README.md update readme 2022-07-26 15:09:37 +08:00

Distributed Scheduler

Introduction

Distributed Scheduler is used for cross-device component management. It allows the local device to access or control remote components, and enables app collaboration in distributed scenarios. Its main functions are as follows:

  • Remote ability startup: Starts an ability on a remote device.
  • Remote ability migration: Migrates an ability to a remote device.
  • Remote ability binding: Binds an ability on a remote device.

System Architecture

Figure 1 Distributed Scheduler architecture

Directory Structure

/foundation/ability
├── dmsfwk                      # DMS framework (DMS is short for Distributed Manager Service, also called the Distributed Scheduler Service)
├── dmsfwk_lite                # Lightweight DMS framework

Repositories Involved

Distributed Scheduler

ability_dmsfwk

ability_dmsfwk_lite