Merge branch 'master' of gitee.com:openharmony/docs into my_doc_vod

OAT.xml

@@ -38,13 +38,13 @@
                 <!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="projectroot/[a-zA-Z0-9]{20,}.sh" desc="Temp files"/-->
-                <filteritem type="filepath" name="en/contribute" desc="already checked"/>
+                <filteritem type="filepath" name="en/contribute/.*" desc="already checked"/>
             </filefilter>
             <filefilter name="copyrightPolicyFilter" desc="Filters for copyright header policies">
                 <!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="projectroot/[a-zA-Z0-9]{20,}.sh" desc="Temp files"/-->
-                <filteritem type="filepath" name="en/contribute" desc="already checked"/>
+                <filteritem type="filepath" name="en/contribute/.*" desc="already checked"/>
             </filefilter>
             <filefilter name="licenseFileNamePolicyFilter" desc="Filters for LICENSE file policies">
                 <!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
@@ -66,7 +66,7 @@
                 <!--filteritem type="filename" name="*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="abcdefg/.*.uvwxyz" desc="Describe the reason for filtering scan results"/-->
                 <!--filteritem type="filepath" name="projectroot/[a-zA-Z0-9]{20,}.sh" desc="Temp files"/-->
-				<filteritem type="filename" name="*.jpg|*.png|*.gif|*.pdf|*.xlsm" desc="already checked"/>
+				<filteritem type="filename" name="*.jpg|*.png|*.gif|*.pdf|*.xlsm|*.zip" desc="already checked"/>
             </filefilter>
 
         </filefilterlist>

README.md

@@ -18,13 +18,15 @@ This repository stores device and application development documents provided by
 
  - master: the latest version.
 
- - OpenHarmony 3.2 Beta1. [Learn more](en/release-notes/OpenHarmony-v3.2-beta1.md)
+ - OpenHarmony 3.2 Beta5. [Learn more](en/release-notes/OpenHarmony-v3.2-beta5.md)
 
  - OpenHarmony 3.1 Release. [Learn more](en/release-notes/OpenHarmony-v3.1-release.md)
 
+   This version is upgraded to OpenHarmony 3.1.3 Release. [Learn more](en/release-notes/OpenHarmony-v3.1.3-release.md)
+
  - OpenHarmony 3.0 LTS. [Learn more](en/release-notes/OpenHarmony-v3.0-LTS.md)
 
-   This version is upgraded to OpenHarmony 3.0.3 LTS. [Learn more](en/release-notes/OpenHarmony-v3.0.3-LTS.md)
+   This version is upgraded to OpenHarmony 3.0.6 LTS. [Learn more](en/release-notes/OpenHarmony-v3.0.6-LTS.md)
 
  - OpenHarmony 2.2 Beta2. [Learn more](en/release-notes/OpenHarmony-v2.2-beta2.md)
 
@@ -32,19 +34,23 @@ This repository stores device and application development documents provided by
 
 ### Historical Stable Versions
 
-OpenHarmony_v1.x_release: OpenHarmony v1.1.4 LTS. [Learn more](en/release-notes/OpenHarmony-v1-1-4-LTS.md)
+OpenHarmony_v1.x_release: OpenHarmony 1.1.5 LTS. [Learn more](en/release-notes/OpenHarmony-v1.1.5-LTS.md)
 
 [More versions](en/release-notes/)
 
 
 ## Third-Party Open-Source Software and License Notice
 
-Third-party license: [Third-Party Open-Source Software and License Notice](en/contribute/third-party-open-source-software-and-license-notice.md)
+Third-party license: [Third-Party Open-Source Software and License Notice](en/contribute/open-source-software-and-license-notice.md)
 
-## How to Contribute
+## Contribution
 
 A great open-source project wouldn't be possible without the hard work of many contributors. We'd like to invite anyone from around the world to  [participate](en/contribute/how-to-contribute.md)  in this exciting journey, and we're grateful for your time, passion, and efforts!
 
 You can evaluate available documents, make simple modifications, provide feedback on document quality, and contribute your original content. For details, see  [Documentation Contribution](en/contribute/documentation-contribution.md).
 
 Excellent contributors will be awarded and the contributions will be publicized in the developer community.
+
+- Mailing list: docs@openharmony.io
+
+- Zulip group: documentation_sig
\ No newline at end of file

README_zh.md

@@ -18,13 +18,15 @@
 
  - master：最新开发版本。  
 
- - OpenHarmony 3.2 Beta1版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.2-beta1.md)了解版本详情。
+ - OpenHarmony 3.2 Beta5版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.2-beta5.md)了解版本详情。
 
  - OpenHarmony 3.1 Release版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.1-release.md)了解版本详情。
 
+    该版本已更新至OpenHarmony 3.1.3 Release，点击[此处](zh-cn/release-notes/OpenHarmony-v3.1.3-release.md)了解版本详情。
+
  - OpenHarmony 3.0 LTS版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.0-LTS.md)了解版本详情。
- 
-    该版本已更新至OpenHarmony 3.0.3 LTS，点击[此处](zh-cn/release-notes/OpenHarmony-v3.0.3-LTS.md)了解版本详情。
+
+    该版本已更新至OpenHarmony 3.0.6 LTS，点击[此处](zh-cn/release-notes/OpenHarmony-v3.0.6-LTS.md)了解版本详情。
 
  - OpenHarmony 2.2 Beta2版本：点击[此处](zh-cn/release-notes/OpenHarmony-v2.2-beta2.md)了解版本详情。
 
@@ -32,7 +34,7 @@
 
 ### 历史稳定版本
 
-OpenHarmony_v1.x_release：OpenHarmony 1.1.4 LTS稳定版本，点击[此处](zh-cn/release-notes/OpenHarmony-v1-1-4-LTS.md)了解版本详情。
+OpenHarmony_v1.x_release：OpenHarmony 1.1.5 LTS稳定版本，点击[此处](zh-cn/release-notes/OpenHarmony-v1.1.5-LTS.md)了解版本详情。
 
 如需了解更多版本详情，点击[此处](zh-cn/release-notes/)。
 
@@ -47,4 +49,8 @@ OpenHarmony_v1.x_release：OpenHarmony 1.1.4 LTS稳定版本，点击[此处](zh
 
 您可以对现有文档进行评价、简单更改、反馈文档质量问题、贡献您的原创内容，详细请参考[贡献文档](zh-cn/contribute/贡献文档.md)。
 
-卓越贡献者将会在开发者社区文档贡献专栏表彰公示。
+卓越贡献者将会在开发者社区文档贡献专栏表彰公示。
\ No newline at end of file
+
+- 邮件列表：docs@openharmony.io
+
+- Zulip群组：documentation_sig
\ No newline at end of file

docker/Dockerfile

@@ -35,14 +35,15 @@ RUN sed -i "s@http://.*archive.ubuntu.com@http://repo.huaweicloud.com@g" /etc/ap
 	&& pip3 install six --upgrade --ignore-installed six \
 	&& mkdir -p /home/tools \
 	&& mkdir -p /home/tools/gn \
-	&& wget -P /home/tools https://repo.huaweicloud.com/harmonyos/compiler/clang/10.0.1-62608/linux/llvm.tar.gz \
+	&& wget -P /home/tools https://repo.huaweicloud.com/openharmony/compiler/clang/12.0.1-530132/linux/clang-530132-linux-x86_64.tar.bz2 \
 	&& wget -P /home/tools https://repo.huaweicloud.com/harmonyos/compiler/hc-gen/0.65/linux/hc-gen-0.65-linux.tar \
 	&& wget -P /home/tools https://repo.huaweicloud.com/harmonyos/compiler/gcc_riscv32/7.3.0/linux/gcc_riscv32-linux-7.3.0.tar.gz \
 	&& wget -P /home/tools https://repo.huaweicloud.com/harmonyos/compiler/ninja/1.9.0/linux/ninja.1.9.0.tar \
 	&& wget -P /home/tools https://repo.huaweicloud.com/harmonyos/compiler/gn/1717/linux/gn-linux-x86-1717.tar.gz \
 	&& wget -P /home/tools https://mirrors.huaweicloud.com/nodejs/v14.15.4/node-v14.15.4-linux-x64.tar.xz \
 	&& wget -P /home/tools https://hm-verify.obs.cn-north-4.myhuaweicloud.com/qemu-5.2.0.tar.xz \
-    	&& tar -xvf /home/tools/llvm.tar.gz -C /home/tools \
+    	&& tar -jxvf /home/tools/clang-530132-linux-x86_64.tar.bz2 -C /home/tools \
+		&& mv /home/tools/clang-530132 /home/tools/llvm \
 	&& tar -xvf /home/tools/hc-gen-0.65-linux.tar -C /home/tools \
 	&& tar -xvf /home/tools/gcc_riscv32-linux-7.3.0.tar.gz -C /home/tools \
 	&& tar -xvf /home/tools/ninja.1.9.0.tar -C /home/tools \

docker/LICENSE

-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright [yyyy] [name of copyright owner]
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

docker/build.sh

-#!/bin/bash
-
-# Copyright (c) 2020 Huawei Device Co., Ltd.
-# Licensed under the Apache License, Version 2.0 (the "License");
-# you may not use this file except in compliance with the License.
-# You may obtain a copy of the License at
-#
-#     http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing, software
-# distributed under the License is distributed on an "AS IS" BASIS,
-# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-# See the License for the specific language governing permissions and
-# limitations under the License.
-
-docker build -t openharmony-docker:1.0.0 .

en/Legal-Notices.md

+# Legal Notices
+
+**Copyright (c) 2020-2022 OpenAtom OpenHarmony. All rights reserved.** 
+
+## Copyright
+
+All copyrights of the OpenHarmony documents are reserved by OpenAtom OpenHarmony.
+
+The OpenHarmony documents are licensed under Creative Commons Attribution 4.0 International (CC BY 4.0). For easier understanding, you can visit [Creative Commons](https://creativecommons.org/licenses/by/4.0/) to get a human-readable summary of the license. For the complete content, see [Creative Commons Attribution 4.0 International Public License](https://creativecommons.org/licenses/by/4.0/legalcode). 
+
+## Trademarks and Permissions
+
+No content provided in the OpenHarmony documentation shall be deemed as a grant of the approval or right to use any trademark, name, or logo of the OpenAtom Foundation and OpenAtom OpenHarmony. No third parties shall use any of the aforementioned trademarks, names, or logos in any way without explicit prior written permission of the OpenAtom Foundation. 
+
+## Disclaimer
+
+The information in the OpenHarmony documents is subject to change without notice.
+
+The OpenHarmony documents are provided without any express or implied warranty. In any case, the OpenAtom Foundation or the copyright owner is not liable for any direct or indirect loss arising from the use of the OpenHarmony documents, regardless of the cause or legal theory, even if the OpenHarmony documents have stated that there is a possibility of such loss.
+
+<!--no_check-->
\ No newline at end of file

en/application-dev/IDL/idl-guidelines.md

@@ -7,7 +7,7 @@ To ensure successful communications between the client and server, interfaces re
 
 ![IDL-interface-description](./figures/IDL-interface-description.png)
 
-IDL provides the following functions:
+**IDL provides the following functions:**
 
 - Declares interfaces provided by system services for external systems, and based on the interface declaration, generates C, C++, JS, or TS code for inter-process communication (IPC) or remote procedure call (RPC) proxies and stubs during compilation.
 
@@ -17,7 +17,7 @@ IDL provides the following functions:
 
 ![IPC-RPC-communication-model](./figures/IPC-RPC-communication-model.png)
 
-IDL has the following advantages:
+**IDL has the following advantages:**
 
 - Services are defined in the form of interfaces in IDL. Therefore, you do not need to focus on implementation details.
 
@@ -149,198 +149,53 @@ The value of <*formal_param_attr*> can be **in**, **out**, or **inout**, indicat
 
 ## How to Develop
 
-### Development Using C++
+### Obtaining IDL
+On DevEco Studio, choose **Tools > SDK Manager** to view the local installation path of the OpenHarmony SDK. The following figure uses DevEco Studio 3.0.0.993 as an example.
+![SDKpath](./figures/SDKpath.png)
+![SDKpath](./figures/SDKpath2.png)
 
-#### Creating an IDL File
-
- You can use C++ to create IDL files. An example IDL file is as follows:
+Go to the local installation path, choose **toolchains > 3.x.x.x** (the folder named after the version number), and check whether the executable file of IDL exists.
 
-```cpp
-  interface OHOS.IIdlTestService {
-      int TestIntTransaction([in] int data);
-      void TestStringTransaction([in] String data);
-  }
-```
+> **NOTE**: Use the SDK of the latest version. The use of an earlier version may cause errors in some statements.
 
-You can run the **./idl -gen-cpp -d dir -c dir/iTest.idl** command (**-d** indicates the output directory) to generate the interface file, stub file, and proxy file in the **dir** directory in the execution environment. The names of the generated interface class files are the same as that of the IDL file, except that the file name extensions are **.h** and **.cpp**. For example, the files generated for **IIdlTestService.idl** are **i_idl_test_service.h**, **idl_test_service_proxy.h**, **idl_test_service_stub.h**, **idl_test_service_proxy.cpp**, and **idl_test_service_stub.cpp**.
+If the executable file does not exist, download the SDK package from the mirror as instructed in the [Release Notes](../../release-notes). The following uses the [3.2 Beta3](../../release-notes/OpenHarmony-v3.2-beta3.md#acquiring-source-code-from-mirrors) as an example.
 
-#### Exposing Interfaces on the Server
+For details about how to replace the SDK package, see [Guide to Switching to Full SDK](../quick-start/full-sdk-switch-guide.md).
 
-The stub class generated by IDL is an abstract implementation of the interface class and declares all methods in the IDL file.
+After obtaining the executable file, perform subsequent development steps based on your scenario.
 
-```cpp
-#ifndef OHOS_IDLTESTSERVICESTUB_H
-#define OHOS_IDLTESTSERVICESTUB_H
-#include <iremote_stub.h>
-#include "iidl_test_service.h"
-
-namespace OHOS {
-class IdlTestServiceStub : public IRemoteStub<IIdlTestService> {
-public:
-    int OnRemoteRequest(
-        /* [in] */ uint32_t code,
-        /* [in] */ MessageParcel& data,
-        /* [out] */ MessageParcel& reply,
-        /* [in] */ MessageOption& option) override;
-
-private:
-    static constexpr int COMMAND_TEST_INT_TRANSACTION = MIN_TRANSACTION_ID + 0;
-    static constexpr int COMMAND_TEST_STRING_TRANSACTION = MIN_TRANSACTION_ID + 1;
-};
-} // namespace OHOS
-#endif // OHOS_IDLTESTSERVICESTUB_H
-```
+### Development Using TS
 
-You need to inherit the interface class defined in the IDL file and implement the methods in the class. In addition, you need to register the defined services with SAMGR during service initialization. In the following code snippet, **TestService** inherits the **IdlTestServiceStub** interface class and implements the **TestIntTransaction** and **TestStringTransaction** methods.  
+#### Creating an IDL File
 
-```cpp
-#ifndef OHOS_IPC_TEST_SERVICE_H
-#define OHOS_IPC_TEST_SERVICE_H
-
-#include "hilog/log.h"
-#include "log_tags.h"
-#include "idl_test_service_stub.h"
-
-namespace OHOS {
-class TestService : public IdlTestServiceStub {
-public:
-    TestService();
-    ~TestService();
-    static int Instantiate();
-    ErrCode TestIntTransaction(int data, int &rep) override;
-    ErrCode TestStringTransaction(const std::string& data) override;
-private:
-    static constexpr HiviewDFX::HiLogLabel LABEL = { LOG_CORE, LOG_ID_IPC, "TestService" };
-};
-} // namespace OHOS
-#endif // OHOS_IPC_TEST_SERVICE_H
-```
+You can use TS to create IDL files.
 
-The sample code for registering a service is as follows:
+ For example, create a file named **IIdlTestService.idl** with the following content: 
 
 ```cpp
-#include "test_service.h"
-
-#include <string_ex.h>
-
-#include "if_system_ability_manager.h"
-#include "ipc_debug.h"
-#include "ipc_skeleton.h"
-#include "iservice_registry.h"
-#include "system_ability_definition.h"
-
-namespace OHOS {
-using namespace OHOS::HiviewDFX;
-
-int TestService::Instantiate()
-{
-    ZLOGI(LABEL, "%{public}s call in", __func__);
-    auto saMgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
-    if (saMgr == nullptr) {
-        ZLOGE(LABEL, "%{public}s:fail to get Registry", __func__);
-        return -ENODEV;
-    }
-
-    sptr<IRemoteObject> newInstance = new TestService();
-    int result = saMgr->AddSystemAbility(IPC_TEST_SERVICE, newInstance);
-    ZLOGI(LABEL, "%{public}s: IPC_TEST_SERVICE result = %{public}d", __func__, result);
-    return result;
-}
-
-TestService::TestService()
-{
-}
-
-TestService::~TestService()
-{
-}
-
-ErrCode TestService::TestIntTransaction(int data, int &rep)
-{
-    ZLOGE(LABEL, " TestService:read from client data = %{public}d", data);
-    rep = data + data;
-    return ERR_NONE;
-}
-
-ErrCode TestService::TestStringTransaction(const std::string &data)
-{
-    ZLOGE(LABEL, "TestService:read string from client data = %{public}s", data.c_str());
-    return data.size();
-}
-} // namespace OHOS
+  interface OHOS.IIdlTestService {
+      int TestIntTransaction([in] int data);
+      void TestStringTransaction([in] String data);
+  }
 ```
 
-#### Calling Methods from the Client for IPC
-
-The C++ client obtains the service proxy defined in the system through SAMGR and then invokes the interface provided by the proxy. The sample code is as follows:
+Run the **idl -gen-ts -d *dir* -c dir/IIdlTestService.idl** command in the folder where the executable file is located.
 
-```cpp
-#include "test_client.h"
-
-#include "if_system_ability_manager.h"
-#include "ipc_debug.h"
-#include "ipc_skeleton.h"
-#include "iservice_registry.h"
-#include "system_ability_definition.h"
-
-namespace OHOS {
-int TestClient::ConnectService()
-{
-    auto saMgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
-    if (saMgr == nullptr) {
-        ZLOGE(LABEL, "get registry fail");
-        return -1;
-    }
+-*dir* next to **d** is the target output folder. For example, if the target output folder is **IIdlTestServiceTs**, run the **idl -gen-ts -d IIdlTestServiceTs -c IIdlTestServiceTs/IIdlTestService.idl** command in the folder where the executable file is located. The interface file, stub file, and proxy file are generated in the *dir* directory (**IIdlTestServiceTs** directory in this example) in the execution environment.
 
-    sptr<IRemoteObject> object = saMgr->GetSystemAbility(IPC_TEST_SERVICE);
-    if (object != nullptr) {
-        ZLOGE(LABEL, "Got test Service object");
-        testService_ = (new (std::nothrow) IdlTestServiceProxy(object));
-    }
+> **NOTE**: The generated interface class file name must be the same as that of the .idl file. Otherwise, an error occurs during code generation.
 
-    if (testService_ == nullptr) {
-        ZLOGE(LABEL, "Could not find Test Service!");
-        return -1;
-    }
-
-    return 0;
-}
+For example, for an .idl file named **IIdlTestService.idl** and target output directory named **IIdlTestServiceTs**, the directory structure is similar to the following:
 
-void TestClient::StartIntTransaction()
-{
-    if (testService_ != nullptr) {
-        ZLOGE(LABEL, "StartIntTransaction");
-        [[maybe_unused]] int result = 0;
-        testService_->TestIntTransaction(1234, result); // 1234 : test number
-        ZLOGE(LABEL, "Rec result from server %{public}d.", result);
-    }
-}
-
-void TestClient::StartStringTransaction()
-{
-    if (testService_ != nullptr) {
-        ZLOGI(LABEL, "StartIntTransaction");
-        testService_->TestStringTransaction("IDL Test");
-    }
-}
-} // namespace OHOS
 ```
-
-### Development Using TS
-
-#### Creating an IDL File
-
- You can use TS to create IDL files. An example IDL file is as follows:
-
-```ts
-  interface OHOS.IIdlTestService {
-      int TestIntTransaction([in] int data);
-      void TestStringTransaction([in] String data);
-  }
+├── IIdlTestServiceTs  # IDL code output folder
+│   ├── i_idl_test_service.ts  # File generated
+│   ├── idl_test_service_proxy.ts  # File generated
+│   ├── idl_test_service_stub.ts  # File generated
+│   └── IIdlTestService.idl  # Constructed .idl file
+└── idl.exe  # Executable file of IDL
 ```
 
-Run the **./idl -c IIdlTestService.idl -gen-ts -d /data/ts/** command (**-d** indicates the output directory) to generate the interface file, stub file, and proxy file in the **/data/ts** directory in the execution environment. The names of the generated interface class files are the same as that of the IDL file, except that the file name extension is **.ts**. For example, the files generated for the **IIdlTestService.idl** file are **i_idl_test_service.ts**, **idl_test_service_proxy.ts**, and **idl_test_service_stub.ts**.
-
 #### Exposing Interfaces on the Server
 
 The stub class generated by IDL is an abstract implementation of the interface class and declares all methods in the IDL file.
@@ -356,8 +211,8 @@ export default class IdlTestServiceStub extends rpc.RemoteObject implements IIdl
         super(des);
     }
     
-    onRemoteRequest(code: number, data, reply, option): boolean {
-        console.log("onRemoteRequest called, code = " + code);
+    async onRemoteRequestEx(code: number, data, reply, option): Promise<boolean> {
+        console.log("onRemoteRequestEx called, code = " + code);
         switch(code) {
             case IdlTestServiceStub.COMMAND_TEST_INT_TRANSACTION: {
                 let _data = data.readInt();
@@ -433,7 +288,7 @@ export default {
             console.log('ServiceAbility want:' + JSON.stringify(want));
             console.log('ServiceAbility want name:' + want.bundleName)
         } catch(err) {
-            console.log("ServiceAbility error:" + err)
+            console.log('ServiceAbility error:' + err)
         }
         console.info('ServiceAbility onConnect end');
         return new IdlTestImp('connect');
@@ -455,13 +310,13 @@ import featureAbility from '@ohos.ability.featureAbility';
 
 function callbackTestIntTransaction(result: number, ret: number): void {
   if (result == 0 && ret == 124) {
-    console.log("case 1 success ");
+    console.log('case 1 success');
   }
 }
 
 function callbackTestStringTransaction(result: number): void {
   if (result == 0) {
-    console.log("case 2 success ");
+    console.log('case 2 success');
   }
 }
 
@@ -472,17 +327,17 @@ var onAbilityConnectDone = {
     testProxy.testStringTransaction('hello', callbackTestStringTransaction);
   },
   onDisconnect:function (elementName) {
-    console.log("onDisconnectService onDisconnect");
+    console.log('onDisconnectService onDisconnect');
   },
   onFailed:function (code) {
-    console.log("onDisconnectService onFailed");
+    console.log('onDisconnectService onFailed');
   }
 };
 
 function connectAbility: void {
     let want = {
-    	"bundleName":"com.example.myapplicationidl",
-    	"abilityName": "com.example.myapplicationidl.ServiceAbility"
+        bundleName: 'com.example.myapplicationidl',
+        abilityName: 'com.example.myapplicationidl.ServiceAbility'
     };
     let connectionId = -1;
     connectionId = featureAbility.connectAbility(want, onAbilityConnectDone);
@@ -495,7 +350,7 @@ function connectAbility: void {
 
 You can send a class from one process to another through IPC interfaces. However, you must ensure that the peer can use the code of this class and this class supports the **marshalling** and **unmarshalling** methods. OpenHarmony uses **marshalling** and **unmarshalling** to serialize and deserialize objects into objects that can be identified by each process.
 
-To create a class that supports the sequenceable type, perform the following operations:
+**To create a class that supports the sequenceable type, perform the following operations:**
 
 1. Implement the **marshalling** method, which obtains the current state of the object and serializes the object into a **Parcel** object.
 2. Implement the **unmarshalling** method, which deserializes the object from a **Parcel** object.
@@ -529,137 +384,3 @@ export default class MySequenceable {
     private str;
 }
 ```
-
-## How to Develop for Interworking Between C++ and TS
-
-### TS Proxy and C++ Stub Development
-
-#### C++ Service Object
-
-1. Use C++ to construct an IDL file and run commands to generate interfaces, stub files, and proxy files.
-
-2. Create a service object, inherit the interface class defined in the C++ stub file, and implement the methods in the class. An example is as follows:
-
-   ```cpp
-   class IdlTestServiceImpl : public IdlTestServiceStub {
-   public:
-       IdlTestServiceImpl() = default;
-       virtual ~IdlTestServiceImpl() = default;
-   
-       ErrCode TestIntTransaction(int _data, int& result) override
-       {
-       	result = 256;
-       	return ERR_OK;
-       }
-   
-       ErrCode TestStringTransaction(const std::string& _data) override
-       {
-       	return ERR_OK;
-       }
-   };
-   ```
-
-#### Native APIs in C++
-
-C++ provides C++ service objects to TS in the format of native APIs. For example, C++ provides a **GetNativeObject** method, which is used to create an **IdlTestServiceImpl** instance. Using the **NAPI_ohos_rpc_CreateJsRemoteObject** method, you can create a JS remote object for the TS application.
-
-```cpp
-NativeValue* GetNativeObject(NativeEngine& engine, NativeCallbackInfo& info)
-{
-    sptr<IdlTestServiceImpl> impl = new IdlTestServiceImpl();
-    napi_value napiRemoteObject = NAPI_ohos_rpc_CreateJsRemoteObject(reinterpret_cast<napi_env>(&engine), impl);
-    NativeValue* nativeRemoteObject = reinterpret_cast<NativeValue*>(napiRemoteObject);
-    return nativeRemoteObject;
-}
-```
-
-#### TS Proxy Object
-
-Use TS to construct an IDL file and run commands to generate interfaces, stub files, and proxy files. An example proxy file is as follows:
-
-```ts
-import {testIntTransactionCallback} from "./i_idl_test_service";
-import {testStringTransactionCallback} from "./i_idl_test_service";
-import IIdlTestService from "./i_idl_test_service";
-import rpc from "@ohos.rpc";
-
-export default class IdlTestServiceProxy implements IIdlTestService {
-    constructor(proxy) {
-        this.proxy = proxy;
-    }
-
-    testIntTransaction(data: number, callback: testIntTransactionCallback): void
-    {
-        let _option = new rpc.MessageOption(rpc.MessageOption.TF_SYNC);
-        let _data = new rpc.MessageParcel();
-        let _reply = new rpc.MessageParcel();
-        _data.writeInt(data);
-        this.proxy.sendRequest(IdlTestServiceProxy.COMMAND_TEST_INT_TRANSACTION, _data, _reply, _option).then(function(result) {
-            if (result.errCode === 0) {
-                let _errCode = result.reply.readInt();
-                if (_errCode != 0) {
-                    let _returnValue = undefined;
-                    callback(_errCode, _returnValue);
-                    return;
-                }
-                let _returnValue = result.reply.readInt();
-                callback(_errCode, _returnValue);
-            } else {
-                console.log("sendRequest failed, errCode: " + result.errCode);
-            }
-        })
-    }
-
-    testStringTransaction(data: string, callback: testStringTransactionCallback): void
-    {
-        let _option = new rpc.MessageOption(rpc.MessageOption.TF_SYNC);
-        let _data = new rpc.MessageParcel();
-        let _reply = new rpc.MessageParcel();
-        _data.writeString(data);
-        this.proxy.sendRequest(IdlTestServiceProxy.COMMAND_TEST_STRING_TRANSACTION, _data, _reply, _option).then(function(result) {
-            if (result.errCode === 0) {
-                let _errCode = result.reply.readInt();
-                callback(_errCode);
-            } else {
-                console.log("sendRequest failed, errCode: " + result.errCode);
-            }
-        })
-    }
-
-    static readonly COMMAND_TEST_INT_TRANSACTION = 1;
-    static readonly COMMAND_TEST_STRING_TRANSACTION = 2;
-    private proxy
-}
-```
-
-#### Interworking Between TS and C++ Applications
-
-1. The TS application invokes the native API to obtain the remote C++ service object.
-2. Construct a TS proxy and transfers the remote C++ service object to it.
-3. Use the TS proxy to call the method declared in the IDL file to implement the interworking between the TS proxy and C++ stub. The following is an example:
-
-```ts
-import IdlTestServiceProxy from './idl_test_service_proxy'
-import nativeMgr from 'nativeManager';
-
-function testIntTransactionCallback(errCode: number, returnValue: number)
-{
-	console.log("errCode: " + errCode + "  returnValue: " + returnValue);
-}
-
-function testStringTransactionCallback(errCode: number)
-{
-	console.log("errCode: " + errCode);
-}
-
-function jsProxyTriggerCppStub()
-{
-	let nativeObj = nativeMgr.GetNativeObject();
-  	let tsProxy = new IdlTestServiceProxy(nativeObj);	
-  	// Call testIntTransaction.
-  	tsProxy.testIntTransaction(10, testIntTransactionCallback);
-  	
-  	// Call testStringTransaction.
-  	tsProxy.testStringTransaction("test", testIntTransactionCallback);
-}
-```

en/application-dev/Readme-EN.md

@@ -2,51 +2,87 @@
 
 - [Application Development Overview](application-dev-guide.md)
 - About OpenHarmony
-    - [OpenHarmony Project](../OpenHarmony-Overview.md)
-    - [Glossary](../glossary.md)
-    - [OpenHarmony Release Notes](../release-notes/Readme.md)
+  - [OpenHarmony Project](../OpenHarmony-Overview.md)
+  - [Glossary](../glossary.md)
+  - [OpenHarmony Release Notes](../release-notes/Readme.md)
 - Quick Start
-    - Getting Started
-        - [Preparations](quick-start/start-overview.md)
-        - [Getting Started with eTS in the Traditional Coding Approach](quick-start/start-with-ets.md)
-        - [Getting Started with eTS in the Low-Code Approach](quick-start/start-with-ets-low-code.md)
-        - [Getting Started with JavaScript in the Traditional Coding Approach](quick-start/start-with-js.md)
-        - [Getting Started with JavaScript in the Low-Code Approach](quick-start/start-with-js-low-code.md)
-    - Development Fundamentals
-        - [Application Package Structure Configuration File (FA Model)](quick-start/package-structure.md)
-        - [Application Package Structure Configuration File (Stage Model)](quick-start/stage-structure.md)
-        - [Resource File Categories](quick-start/basic-resource-file-categories.md)
-        - [SysCap](quick-start/syscap.md)
+  - Getting Started
+    - [Before You Start](quick-start/start-overview.md)
+    - [Getting Started with ArkTS in Stage Model](quick-start/start-with-ets-stage.md)
+    - [Getting Started with ArkTS in FA Model](quick-start/start-with-ets-fa.md)
+    - [Getting Started with JavaScript in FA Model](quick-start/start-with-js-fa.md)
+  - Development Fundamentals
+    - Application Package Fundamentals
+      - [Application Package Overview](quick-start/application-package-overview.md)
+      - Application Package Structure
+        - [Application Package Structure in Stage Model)](quick-start/application-package-structure-stage.md)
+        - [Application Package Structure in FA Model](quick-start/application-package-structure-fa.md)
+      - Multi-HAP Mechanism
+        - [Multi-HAP Design Objectives](quick-start/multi-hap-objective.md)
+        - [Multi-HAP Build View](quick-start/multi-hap-build-view.md)
+        - [Multi-HAP Development, Debugging, Release, and Deployment Process](quick-start/multi-hap-release-deployment.md)
+        - [Multi-HAP Usage Rules](quick-start/multi-hap-rules.md)
+        - [Multi-HAP Operation Mechanism and Data Communication Modes](quick-start/multi-hap-principles.md)
+      - [Application Installation and Uninstallation Process](quick-start/application-package-install-uninstall.md)
+    - Application Configuration Files in Stage Model
+      - [Application Configuration File Overview (Stage Model)](quick-start/application-configuration-file-overview-stage.md)
+      - [app.json5 Configuration File](quick-start/app-configuration-file.md)
+      - [module.json5 Configuration File](quick-start/module-configuration-file.md)
+    - Application Configuration Files in FA Model
+      - [Application Configuration File Overview (FA Model)](quick-start/application-configuration-file-overview-fa.md)
+      - [Internal Structure of the app Tag](quick-start/app-structure.md)
+      - [Internal structure of deviceConfig Tag](quick-start/deviceconfig-structure.md)
+      - [Internal Structure of the module Tag](quick-start/module-structure.md)
+    - [Resource Categories and Access](quick-start/resource-categories-and-access.md)
+  - Learning ArkTS
+    - [Getting Started with ArkTS](quick-start/arkts-get-started.md)
+    - ArkTS Syntax (Declarative UI)
+      - [Basic UI Description](quick-start/arkts-basic-ui-description.md)
+      - State Management
+        - [Basic Concepts](quick-start/arkts-state-mgmt-concepts.md)
+        - [State Management with Page-level Variables](quick-start/arkts-state-mgmt-page-level.md)
+        - [State Management with Application-level Variables](quick-start/arkts-state-mgmt-application-level.md)
+      - [Dynamic UI Element Building](quick-start/arkts-dynamic-ui-elememt-building.md)
+      - [Rendering Control](quick-start/arkts-rendering-control.md)
+      - [Restrictions and Extensions](quick-start/arkts-restrictions-and-extensions.md)
 - Development
-    - [Ability Development](ability/Readme-EN.md)
-    - [UI Development](ui/Readme-EN.md)
-    - [Common Event and Notification](notification/Readme-EN.md)
-    - [Window Manager](windowmanager/Readme-EN.md)
-    - [WebGL](webgl/Readme-EN.md)
-    - [Media](media/Readme-EN.md)
-    - [Security](security/Readme-EN.md)
-    - [Connectivity](connectivity/Readme-EN.md)
-    - [Data Management](database/Readme-EN.md)
-    - [Telephony](telephony/Readme-EN.md)
-    - [Task Management](task-management/Readme-EN.md)
-    - [Device Management](device/Readme-EN.md)
-    - [Device Usage Statistics](device-usage-statistics/Readme-EN.md)
-    - [DFX](dfx/Readme-EN.md)
-    - [Internationalization](internationalization/Readme-EN.md)
-    - [OpenHarmony IDL Specifications and User Guide](IDL/idl-guidelines.md)
-    - [Using Native APIs in Application Projects](napi/Readme-EN.md)
+  - [Application Models](application-models/Readme-EN.md)
+  - [UI Development](ui/Readme-EN.md)
+  - [Notification](notification/Readme-EN.md)
+  - [Window Manager](windowmanager/Readme-EN.md)
+  - [WebGL](webgl/Readme-EN.md)
+  - [Media](media/Readme-EN.md)
+  - [Security](security/Readme-EN.md)
+  - [Connectivity](connectivity/Readme-EN.md)
+  - [Data Management](database/Readme-EN.md)
+  - [File Management](file-management/Readme-EN.md)
+  - [Telephony Service](telephony/Readme-EN.md)
+  - [Task Management](task-management/Readme-EN.md)
+  - [Device Management](device/Readme-EN.md)
+  - [Device Usage Statistics](device-usage-statistics/Readme-EN.md)
+  - [DFX](dfx/Readme-EN.md)
+  - [Internationalization](internationalization/Readme-EN.md)
+  - [Application Test](application-test/Readme-EN.md)
+  - [OpenHarmony IDL Specifications and User Guide](IDL/idl-guidelines.md)
+  - [Native APIs](napi/Readme-EN.md)
 - Tools
-    - [DevEco Studio (OpenHarmony) User Guide](quick-start/deveco-studio-user-guide-for-openharmony.md)
+  - [DevEco Studio (OpenHarmony) User Guide](quick-start/deveco-studio-user-guide-for-openharmony.md)
+  - [Debugging Tools](tools/Readme-EN.md)
 - Hands-On Tutorials
-    - [Samples](https://gitee.com/openharmony/app_samples/blob/master/README.md)
-    - [Codelabs](https://gitee.com/openharmony/codelabs)
+  - [Samples](https://gitee.com/openharmony/applications_app_samples/blob/master/README.md)
+  - [Codelabs](https://gitee.com/openharmony/codelabs)
 - API References
-    - [Component Reference (JavaScript-based Web-like Development Paradigm)](reference/arkui-js/Readme-EN.md)
-    - [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/Readme-EN.md)
-    - APIs
-      -   [JS and TS APIs](reference/apis/Readme-EN.md)
-      -   Native APIs
-          -   [Standard Library](reference/native-lib/third_party_libc/musl.md)
-          -   [Node_API](reference/native-lib/third_party_napi/napi.md)
+  - [SystemCapability](reference/syscap.md)
+  - [SystemCapability List](reference/syscap-list.md)
+  - [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/Readme-EN.md)
+  - [Component Reference (JavaScript-based Web-like Development Paradigm)](reference/arkui-js/Readme-EN.md)
+  - [JS Service Widget UI Components](reference/js-service-widget-ui/Readme-EN.md)
+  - APIs
+    - [ArkTS and JS APIs](reference/apis/Readme-EN.md)
+    - [Error Codes](reference/errorcodes/Readme-EN.md)
+    - Native APIs
+      - [Standard Libraries](reference/native-lib/third_party_libc/musl.md)
+      - [Node_API](reference/native-lib/third_party_napi/napi.md)
+- [FAQs](faqs/Readme-EN.md)
 - Contribution
-    - [How to Contribute](../contribute/documentation-contribution.md)
+  - [How to Contribute](../contribute/documentation-contribution.md)

en/application-dev/ability-deprecated/Readme-EN.md

+# Ability Development
+
+> **NOTE**<br/>
+> This folder is deprecated. Read [Application Models](../application-models/Readme-EN.md) instead.
+
+- [Ability Framework Overview](ability-brief.md)
+- [Context Usage](context-userguide.md)
+- FA Model
+  - [FA Model Overview](fa-brief.md)
+  - [Page Ability Development](fa-pageability.md)
+  - [Service Ability Development](fa-serviceability.md)
+  - [Data Ability Development](fa-dataability.md)
+  - [FA Widget Development](fa-formability.md)
+- Stage Model
+  - [Stage Model Overview](stage-brief.md)
+  - [Ability Development](stage-ability.md)
+  - [Service Extension Ability Development](stage-serviceextension.md)
+  - [Ability Continuation Development](stage-ability-continuation.md)
+  - [Ability Call Development](stage-call.md)
+  - [Stage Widget Development](stage-formextension.md)
+- Other
+  - [WantAgent Development](wantagent.md)
+  - [Ability Assistant Usage](ability-assistant-guidelines.md)
+  - [ContinuationManager Development](continuationmanager.md)
+  - [Test Framework Usage](ability-delegator.md)

en/application-dev/ability-deprecated/ability-assistant-guidelines.md

+# Ability Assistant Usage
+
+The ability assistant enables you to start applications, atomic services, and test cases and debug applications. By using this tool, you can send commands in the hdc shell to perform various system operations, such as starting abilities, forcibly stopping processes, and printing ability information.
+
+## Query-related Commands
+
+- **help**
+
+  Displays help information for the ability assistant.
+
+  **Return value**
+
+  Returns the help information.
+
+  **Method**
+
+  ```
+  aa help
+  ```
+
+## Ability-related Commands
+
+- **start**
+
+  Starts an ability.
+
+  | Name     | Description                  |
+  | --------- | -------------------------- |
+  | -h/--help | Help information.                |
+  | -d        | Device ID. This parameter is optional.   |
+  | -a        | Ability name. This parameter is mandatory.|
+  | -b        | Bundle name. This parameter is mandatory. |
+  | -D        | Debugging mode. This parameter is optional.      |
+
+  **Return value**
+
+  Returns "start ability successfully." if the ability is started; returns "error: failed to start ability." otherwise.
+
+  **Method**
+
+  ```
+  aa start [-d <device-id>] -a <ability-name> -b <bundle-name> [-D]
+  ```
+  
+- **stop-service**
+
+  Stops a Service ability.
+
+  | Name     | Description                |
+  | --------- | ------------------------ |
+  | -h/--help | Help information.              |
+  | -d        | Device ID. This parameter is optional.   |
+  | -a        | Ability name. This parameter is mandatory.|
+  | -b        | Bundle name. This parameter is mandatory. |
+
+  **Return value**
+
+  Returns "stop service ability successfully." if the Service ability is stopped; returns "error: failed to stop service ability." otherwise.
+
+  **Method**
+
+  ```
+  aa stop-service [-d <device-id>] -a <ability-name> -b <bundle-name>
+  ```
+  
+- **dump**
+
+  Prints ability-related information.
+
+  | Name             | Level-2 Parameter            | Description                                                    |
+  | ----------------- | -------------------- | ------------------------------------------------------------ |
+  | -h/--help         | -                    | Prints help information.                                                  |
+  | -a/--all          | -                    | Prints ability information in all missions.                                |
+  | -l/--mission-list | type (All logs are printed if this parameter is left unspecified.)| Prints mission stack information.<br>The following values are available for **type**:<br>- NORMAL <br>- DEFAULT_STANDARD<br>- DEFAULT_SINGLE<br>- LAUNCHER |
+  | -e/--extension    | elementName          | Prints extended component information.                                          |
+  | -u/--userId       | UserId               | Prints stack information of a specified user ID. This parameter must be used together with other parameters. <br/>Example commands: aa **dump -a -u 100** and **aa dump -d -u 100**.|
+  | -d/--data         | -                    | Prints Data ability information.                                          |
+  | -i/--ability      | AbilityRecord ID     | Prints detailed information about a specified ability.                                   |
+  | -c/--client       | -                    | Prints detailed ability information. This parameter must be used together with other parameters. <br/>Example commands: **aa dump -a -c** and **aa dump -i 21 -c**.|
+  
+  **Method**
+  
+  ```
+  aa dump -a
+  ```
+  ![aa-dump-a](figures/aa-dump-a.PNG)
+  ```
+  aa dump -l
+  ```
+  ![aa-dump-l](figures/aa-dump-l.PNG)
+  ```
+  aa dump -i 12
+  ```
+  ![aa-dump-i](figures/aa-dump-i.PNG)
+- **force-stop**
+
+  Forcibly stops a process based on the bundle name.
+
+  **Return value**
+
+  Returns "force stop process successfully." if the process is forcibly stopped; returns "error: failed to force stop process." otherwise.
+
+  **Method**
+
+  ```
+  aa force-stop <bundle-name>
+  ```

en/application-dev/ability-deprecated/ability-brief.md

+# Ability Framework Overview
+
+Ability is the basic abstraction of applications in OpenHarmony.
+
+Each ability is an application component that provides an independent service and is the minimum unit for the system to schedule an application. An application can contain one or more **Ability** instances.
+
+The ability framework model has two forms:
+
+- FA model, which is available for application development using API version 8 and earlier versions. In the FA model, there are PageAbility, ServiceAbility, DataAbility, and FormAbility.
+- Stage model, which is introduced since API version 9. In the stage model, there are two classes: UIAbility and ExtensionAbility. ExtensionAbility is further extended to ServiceExtensionAbility, FormExtensionAbility, DataShareExtensionAbility, and more.
+
+Starting from API version 9, the stage model is recommended.
+
+The stage model is designed to make it easier to develop complex applications in the distributed environment. The table below lists the design differences between the two models.
+
+| Item          | FA Model                                                      | Stage Model                                               |
+| -------------- | ------------------------------------------------------------ | -------------------------------------------------------- |
+| Application component development mode      | Web-like development                    | Object-oriented development            |
+| Engine instance      | Each **Ability** instance exclusively occupies a VM instance.              | Multiple **Ability** instances share a VM instance.      |
+| Intra-process object sharing| Not supported                                                    | Supported                                                  |
+| Bundle description file    | The **config.json** file is used to describe the HAP and component information. Each component must use a fixed file name.| The **module.json5** file is used to describe the HAP and component information. The entry file name can be specified.|
+| Component          | Four types of components are provided: PageAbility (used for UI page display), ServiceAbility (used to provide services), DataAbility (used for data sharing), and FormAbility (used to provide widgets).| Two types of components are provided: UIAbility (used for UI page display) and ExtensionAbility (scenario-based service extension).  |
+
+In addition, the following differences exist in the development process:
+
+* Different ability types
+
+  ![favsstage](figures/favsstage.png)
+
+* Different ability lifecycles
+
+  ![lifecycle](figures/lifecycle.png)
+
+For details about the two models, see [FA Model Overview](fa-brief.md) and [Stage Model Overview](stage-brief.md).

en/application-dev/ability-deprecated/ability-delegator.md

+# Test Framework Usage
+
+## Overview
+The delegator test framework provides a self-test environment for OpenHarmony applications. Using this framework, you can start an ability, schedule its lifecycle, listen for its state changes, run a shell command, and print the test result.
+
+## Constraints
+
+The APIs provided by the test framework can be used only in the test HAP. They take effect only after the test framework is started.
+
+
+## Starting the Test Framework
+
+The test framework can be started in either of the following ways:
+
+- Method 1: Run the `aa test` command.
+- Method 2: Use DevEco Studio.
+
+### Running aa test
+
+To start the test framework, specify the **TestRunner** and the package name or module name of the HAP where the **TestRunner** is located.
+
+An example command in the FA model is as follows:
+
+```javascript
+aa test -b BundleName -p com.example.myapplicationfaets -s unittest OpenHarmonyTestRunner -s class ActsAbilityTest -w 20
+```
+
+An example command in the stage model is as follows:
+```javascript
+aa test -b BundleName -m com.example.myapplicationfaets -s unittest OpenHarmonyTestRunner -s class ActsAbilityTest -w 20
+```
+| Parameter           | Mandatory| Description                                                    |
+| --------------- | -------- | ------------------------------------------------------------ |
+| -b              | Yes      | Bundle name of the HAP where the **TestRunner** is located.             |
+| -p              | Yes      | Package name of the HAP where the **TestRunner** is located. This parameter is used by the FA model.             |
+| -m              | Yes      | Module name of the HAP where the **TestRunner** is located. This parameter is used by the stage model.           |
+| -s unittest     | Yes      | Name of the **TestRunner** to be used. The TestRunner name must be the same as the file name.  |
+| -w              | No      | Timeout interval of a test case, in seconds. If this parameter is not specified or is set to a value less than or equal to **0**, the test framework exits only after **finishTest** is invoked.|
+| -s \<key>\<value> | No      | **-s** can be followed by any key-value pair obtained through **AbilityDelegatorArgs.parameters**. For example, in **-s classname myTest**, **-s classname** is the key and **myTest** is the value.|
+| -D              | No      | Debug mode for starting the tested application.|
+| -h              | No      | Help information.|
+
+### Using DevEco Studio
+
+For details about how to use DevEco Studio to start the test framework, see [OpenHarmony Test Framework](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-openharmony-test-framework-0000001263160453#section1034420367508).
+
+## Introduction to TestRunner
+
+**TestRunner** is the entry class of the test framework test process. When the test process is started, the system calls related APIs in **TestRunner**. You need to inherit this class and override the **onPrepare** and **onRun** APIs. When creating an application template, DevEco Studio initializes the default **TestRunner** and starts the default **TestAbility** in the **onRun** API. You can modify the test code of **TestAbility** or override **onPrepare** and **onRun** in **TestRunner** to implement your own test code. For details, see [TestRunner](../reference/apis/js-apis-application-testRunner.md).
+
+## Introduction to AbilityDelegatorRegistry
+
+**AbilityDelegatorRegistry** is the **AbilityDelegator** repository class provided by the test framework. You can use **AbilityDelegatorRegistry** to obtain an **AbilityDelegator** instance and the input and generated parameters **AbilityDelegatorArgs** during the test. You can use **AbilityDelegator** to invoke the function set provided by the test framework for testing and verification. For details, see [AbilityDelegatorRegistry](../reference/apis/js-apis-application-abilityDelegatorRegistry.md).
+
+## Introduction to AbilityDelegatorArgs
+
+**AbilityDelegatorArgs** is a test parameter class provided by the test framework. You can use **AbilityDelegatorArgs** to obtain the parameters passed and generated during the test. For details, see [AbilityDelegatorArgs](../reference/apis/js-apis-inner-application-abilityDelegatorArgs.md).
+
+## Introduction to AbilityMonitor
+
+**AbilityMonitor** is provided by the test framework for binding to and listening for abilities. You can use **AbilityMonitor** to bind to an **Ability** instance and add **AbilityMonitor** to the listening list. When **AbilityMonitor** is bound to an ability, the creation and lifecycle changes of the ability will trigger the related callback in **AbilityMonitor**. You can test and verify the ability in these callbacks. For details, see [AbilityMonitor](../reference/apis/js-apis-inner-application-abilityMonitor.md).
+
+**Example**
+
+```javascript
+import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry';
+
+function onAbilityCreateCallback(data) {
+    console.info("onAbilityCreateCallback");
+}
+
+var monitor = {
+    abilityName: "abilityname",
+    onAbilityCreate: onAbilityCreateCallback
+}
+
+var abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+abilityDelegator.addAbilityMonitor(monitor).then(() => {
+    console.info("addAbilityMonitor promise");
+});
+```
+
+## Introduction to AbilityDelegator
+
+**AbilityDelegator** is a main function class of the test framework. It provides the functions of starting an ability, obtaining an **Ability** instance, scheduling the ability lifecycle, listening for the ability state, and printing test results.
+
+**Modules to Import**
+
+```javascript
+import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry';
+```
+
+```javascript
+var abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+```
+
+### Starting an Ability and Listening for the Ability State
+
+Use **AbilityDelegator** and **AbilityMonitor** to start an ability, obtain an **Ability** instance, and listen for the ability state.
+
+**Example**
+
+```javascript
+var abilityDelegator;
+var ability;
+var timeout = 100;
+
+function onAbilityCreateCallback(data) {
+    console.info("onAbilityCreateCallback");
+}
+
+var monitor = {
+    abilityName: "abilityname",
+    onAbilityCreate: onAbilityCreateCallback
+}
+
+abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+abilityDelegator.waitAbilityMonitor(monitor, timeout, (err, data) => {
+    ability = data;
+    console.info("waitAbilityMonitor callback");
+});
+
+var want = {
+    bundleName: "bundleName",
+    abilityName: "abilityName"
+};
+abilityDelegator.startAbility(want, (err, data) => {
+    console.info("startAbility callback");
+});
+```
+
+### Scheduling the Ability Lifecycle
+
+**AbilityDelegator** provides APIs to display and schedule the ability lifecycle and supports the foreground and background. It works with **AbilityMonitor** to listen for the ability lifecycle. For details, see [AbilityDelegator](../reference/apis/js-apis-inner-application-abilityDelegator.md).
+
+### Running a Shell Command
+
+**AbilityDelegator** provides APIs to run shell commands in the test environment.
+
+**Example**
+
+```javascript
+var abilityDelegator;
+var cmd = "cmd";
+abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+abilityDelegator.executeShellCommand(cmd, (err, data) => {
+    console.info("executeShellCommand callback");
+});
+```
+
+### Printing Log Information
+
+**AbilityDelegator** provides APIs for printing log information. You can call any API in the test code to print process logs to the unit test console.
+
+**Example**
+
+```javascript
+var abilityDelegator;
+var msg = "msg";
+
+abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+abilityDelegator.print(msg, (err) => {
+    console.info("print callback");
+});
+```
+
+### Finishing the Test and Printing Log Information
+
+**AbilityDelegator** provides the APIs for actively finishing the test. You can call any API in test code to finish the test and print logs to the unit test console.
+
+**Example**
+
+```javascript
+var abilityDelegator;
+var msg = "msg";
+
+abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
+abilityDelegator.finishTest(msg, 0, (err) => {
+    console.info("finishTest callback");
+});
+```

en/application-dev/ability-deprecated/context-userguide.md

+# Context Usage
+
+## Context Overview
+
+**Context** provides the capability of obtaining contextual information of an application.
+
+The OpenHarmony application framework has two models: Feature Ability (FA) model and stage model. Correspondingly, there are two sets of context mechanisms. **application/BaseContext** is a common context base class. It uses the **stageMode** attribute to specify whether the context is used for the stage model.
+
+- FA model 
+  
+  Only the methods in **app/Context** can be used for the context in the FA model. Both the application-level context and ability-level context are instances of this type. If an ability-level method is invoked in the application-level context, an error occurs. Therefore, you must pay attention to the actual meaning of the **Context** instance.
+  
+- Stage model 
+  
+  The stage model has the following types of contexts: **application/Context**, **application/ApplicationContext**, **application/AbilityStageContext**, **application/ExtensionContext**, **application/AbilityContext**, and **application/FormExtensionContext**. For details about these contexts and how to use them, see [Context in the Stage Model](#context-in-the-stage-model).
+
+![contextIntroduction](figures/contextIntroduction.png)
+
+## Context in the FA Model
+
+Only the methods in **app/Context** can be used for the context in the FA model.
+
+The FA model has only one context definition. All capabilities in the context are provided through methods. The context uses these methods to extend the capabilities of the FA.
+
+**d.ts statement**
+
+https://gitee.com/openharmony/interface_sdk-js/blob/master/api/app/context.d.ts
+
+**Example**
+
+```javascript
+import featureAbility from '@ohos.ability.featureAbility'
+export default {
+  onCreate() {
+    // Obtain the context and call related APIs.
+    let context = featureAbility.getContext();
+    context.getBundleName((data, bundleName)=>{
+      console.info("ability bundleName:" + bundleName)
+    });
+    console.info('Application onCreate')
+  },
+  onDestroy() {
+    console.info('Application onDestroy')
+  },
+}
+```
+
+### Common Context-related Methods in the FA Model
+The following context-related methods are available in the FA model:
+```javascript
+setDisplayOrientation(orientation: bundle.DisplayOrientation, callback: AsyncCallback<void>): void
+setDisplayOrientation(orientation: bundle.DisplayOrientation): Promise<void>;
+```
+The methods are used to set the display orientation of the current ability.
+
+**Example**
+
+```javascript
+import featureAbility from '@ohos.ability.featureAbility'
+import bundle from '@ohos.bundle';
+
+export default {
+  onCreate() {
+    // Obtain the context and call related APIs.
+    let context = featureAbility.getContext();
+    context.setDisplayOrientation(bundle.DisplayOrientation.LANDSCAPE).then(() => {
+        console.log("Set display orientation.")
+    })
+    console.info('Application onCreate')
+  },
+  onDestroy() {
+    console.info('Application onDestroy')
+  },
+}
+```
+
+## Context in the Stage Model
+
+The following describes the contexts provided by the stage model in detail.
+
+### application/Context
+
+**application/Context** is the base class context. It provides basic application information, such as **resourceManager**, **applicationInfo**, **cacheDir**, and **area**. It also provides basic application methods such as **createModuleContext**.
+
+**d.ts statement**
+
+https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/Context.d.ts
+
+### application/ApplicationContext
+
+**application/ApplicationContext** is an application-level context. In addition to the capabilities provided by the base class context, the application-level context provides **registerAbilityLifecycleCallback** and **unregisterAbilityLifecycleCallback** to monitor the ability lifecycle in a process.
+
+**How to Obtain**
+
+Obtain the context by calling **context.getApplicationContext()** in **Ability**.
+
+**Example**
+
+```javascript
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+var lifecycleid;
+
+export default class EntryAbility extends UIAbility {
+    onCreate() {
+        console.log("EntryAbility onCreate")
+        let AbilityLifecycleCallback  =  {
+            onAbilityCreate(ability){
+                console.log("AbilityLifecycleCallback onAbilityCreate ability:" + JSON.stringify(ability));        
+            },
+            onWindowStageCreate(ability, windowStage){
+                console.log("AbilityLifecycleCallback onWindowStageCreate ability:" + JSON.stringify(ability)); 
+                console.log("AbilityLifecycleCallback onWindowStageCreate windowStage:" + JSON.stringify(windowStage));           
+            },
+            onWindowStageActive(ability, windowStage){
+                console.log("AbilityLifecycleCallback onWindowStageActive ability:" + JSON.stringify(ability)); 
+                console.log("AbilityLifecycleCallback onWindowStageActive windowStage:" + JSON.stringify(windowStage));           
+            },
+            onWindowStageInactive(ability, windowStage){
+                console.log("AbilityLifecycleCallback onWindowStageInactive ability:" + JSON.stringify(ability));
+                console.log("AbilityLifecycleCallback onWindowStageInactive windowStage:" + JSON.stringify(windowStage));  
+            },
+            onWindowStageDestroy(ability, windowStage){
+                console.log("AbilityLifecycleCallback onWindowStageDestroy ability:" + JSON.stringify(ability));
+                console.log("AbilityLifecycleCallback onWindowStageDestroy windowStage:" + JSON.stringify(windowStage));  
+            },
+            onAbilityDestroy(ability){
+                console.log("AbilityLifecycleCallback onAbilityDestroy ability:" + JSON.stringify(ability));             
+            },
+            onAbilityForeground(ability){
+                console.log("AbilityLifecycleCallback onAbilityForeground ability:" + JSON.stringify(ability));             
+            },
+            onAbilityBackground(ability){
+                console.log("AbilityLifecycleCallback onAbilityBackground ability:" + JSON.stringify(ability));              
+            },
+            onAbilityContinue(ability){
+                console.log("AbilityLifecycleCallback onAbilityContinue ability:" + JSON.stringify(ability));
+            }
+        }
+        // 1. Obtain applicationContext through the context attribute.
+        let applicationContext = this.context.getApplicationContext();
+        // 2. Use applicationContext to register and listen for the ability lifecycle in the application.
+        lifecycleid = applicationContext.registerAbilityLifecycleCallback(AbilityLifecycleCallback);
+        console.log("registerAbilityLifecycleCallback number: " + JSON.stringify(lifecycleid));       
+    },
+    onDestroy() {
+        let applicationContext = this.context.getApplicationContext();
+        applicationContext.unregisterAbilityLifecycleCallback(lifecycleid, (error, data) => {
+            console.log("unregisterAbilityLifecycleCallback success, err: " + JSON.stringify(error));
+        });
+    }
+}
+```
+
+**d.ts statement**
+
+https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/ApplicationContext.d.ts
+
+### application/AbilityStageContext
+
+**application/AbilityStageContext** is the context for the HAP file. In addition to those provided by the base class **application/Context**, this context contains **HapModuleInfo** and **Configuration**.
+
+**How to Obtain**
+
+Obtain the context from the **context** attribute in **AbilityStage**.
+
+**Example**
+
+```javascript
+export default class MyAbilityStage extends AbilityStage {
+  onCreate() {
+    // The context attribute is of the AbilityStageContext type.
+    console.log('HapModuleInfo is ' + this.context.currentHapModuleInfo);
+  }
+}
+```
+
+**d.ts statement**
+
+https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/AbilityStageContext.d.ts
+
+### application/AbilityContext
+
+In the stage model, each ability has a context attribute.
+
+**Ability** provides methods to manage the ability lifecycle, and **AbilityContext** provides methods to operate abilities (such as **startAbility** and **connectAbility**).
+
+**How to Obtain**
+
+Obtain the context from the **context** attribute in **Ability**.
+
+**Example**
+
+```javascript
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+export default class EntryAbility extends UIAbility {
+    onCreate(want, launchParam) {
+        console.log("[Demo] EntryAbility onCreate")
+        globalThis.abilityWant = want;
+    }
+
+    onDestroy() {
+        console.log("[Demo] EntryAbility onDestroy")
+    }
+
+    onWindowStageCreate(windowStage) {
+        // Set the main page for this ability when the main window is created.
+        console.log("[Demo] EntryAbility onWindowStageCreate")
+
+        // Obtain AbilityContext and print the ability information.
+        let context = this.context;
+        console.log("[Demo] EntryAbility bundleName " + context.abilityInfo.bundleName)
+
+        windowStage.loadContent("pages/index", (err, data) => {
+            if (err.code) {
+                console.error('Failed to load the content. Cause:' + JSON.stringify(err));
+                return;
+            }
+            console.info('Succeeded in loading the content. Data: ' + JSON.stringify(data))
+        });
+    }
+
+    onWindowStageDestroy() {
+        // Release the UI related resources when the main window is destroyed.
+        console.log("[Demo] EntryAbility onWindowStageDestroy")
+    }
+
+    onForeground() {
+        // The ability is switched to run in the foreground.
+        console.log("[Demo] EntryAbility onForeground")
+    }
+
+    onBackground() {
+        // The ability is switched to run in the background.
+        console.log("[Demo] EntryAbility onBackground")
+    }
+};
+```
+
+### application/FormExtensionContext
+
+For details, see [FormExtensionContext](../reference/apis/js-apis-inner-application-formExtensionContext.md).
+
+### Obtaining the Context on an ArkTS Page
+
+In the stage model, in the onWindowStageCreate lifecycle of an ability, you can call **SetUIContent** of **WindowStage** to load an ArkTS page. In some scenarios, you need to obtain the context on the page to call related APIs.
+
+**How to Obtain**
+
+Use the API described in the table below to obtain the context associated with an ArkTS page.
+
+| API                               | Description                                                        |
+| :------------------------------------ | :----------------------------------------------------------- |
+| getContext(component: Object): Object | Obtains the **Context** object associated with a component on the page.<br>Since API version 9, this API is supported in ArkTS widgets.|
+
+**Example**
+
+```ts
+// EntryAbility.ts
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+export default class EntryAbility extends UIAbility {
+    onCreate(want, launchParam) {
+        console.log("[Demo] EntryAbility onCreate")
+    }
+
+    onDestroy() {
+        console.log("[Demo] EntryAbility onDestroy")
+    }
+
+    onWindowStageCreate(windowStage) {
+        // Load the index page and pass the current Context object.
+        windowStage.setUIContent(this.context, "pages/index", null)
+    }
+
+    onWindowStageDestroy() {}
+
+    onForeground() {}
+
+    onBackground() {}
+};
+```
+
+```ts
+// pages/index.ets
+import context from '@ohos.app.ability.context'
+
+type Context = context.Context
+
+@Entry
+@Component
+struct Index {
+    build() {
+        Row() {
+            Column() {
+                Text('GetContext')
+                    .fontSize(50)
+                    .fontWeight(FontWeight.Bold)
+                    .onClick(() => {
+                        // Obtain the Context object associated with the current component.
+                        var context : Context = getContext(this) as Context
+                        console.info("CacheDir:" + context.cacheDir)
+                    })
+            }
+            .width('100%')
+        }
+        .height('100%')
+    }
+}
+```
+
+## Common Incorrect Usage
+
+**Error 1: Use globalThis to obtain the context in the stage model.**
+
+**Reason**
+
+In the FA model, each ability instance has a JS VM instance. Therefore, a global ability instance can be obtained from the **global** object of the JS engine. In the stage model, where all the processes of an application share a JS VM instance, there is no global ability instance, and using **globalThis** may cause an error or crash.

en/application-dev/ability-deprecated/continuationmanager.md

+# ContinuationManager Development
+
+> **NOTE**
+>
+> Currently, the **ContinuationManager** module is not available for application development. Its APIs are mainly used to start the device selection module.
+
+## When to Use
+Users are using two or more devices to experience an all-scenario, multi-device lifestyle. Each type of device has its unique advantages and disadvantages specific to scenarios. The ability continuation capability breaks boundaries of devices and enables multi-device collaboration, achieving precise control, universal coordination, and seamless hops of user applications.
+
+As the entry of the ability continuation capability, **continuationManager** is used to start the device selection module for the user to select the target device. After a device is selected, information about the selected device is returned to the user. The user can then initiate cross-device continuation or collaboration based on the device information.
+
+![continuationManager](figures/continuationManager.png)
+
+## Available APIs
+| API                                                                                         | Description|
+| ---------------------------------------------------------------------------------------------- | ----------- |
+| registerContinuation(callback: AsyncCallback\<number>): void | Registers the continuation management service and obtains a token. This API does not involve any filter parameters and uses an asynchronous callback to return the result.|
+| registerContinuation(options: ContinuationExtraParams, callback: AsyncCallback\<number>): void | Registers the continuation management service and obtains a token. This API uses an asynchronous callback to return the result.|
+| registerContinuation(options?: ContinuationExtraParams): Promise\<number> | Registers the continuation management service and obtains a token. This API uses a promise to return the result.|
+| on(type: "deviceSelected", token: number, callback: Callback\<Array\<ContinuationResult>>): void | Subscribes to device connection events. This API uses an asynchronous callback to return the result.|
+| on(type: "deviceUnselected", token: number, callback: Callback\<Array\<ContinuationResult>>): void | Subscribes to device disconnection events. This API uses an asynchronous callback to return the result.|
+| off(type: "deviceSelected", token: number): void | Unsubscribes from device connection events.|
+| off(type: "deviceUnselected", token: number): void | Unsubscribes from device disconnection events.|
+| startContinuationDeviceManager(token: number, callback: AsyncCallback\<void>): void | Starts the device selection module to show the list of available devices. This API does not involve any filter parameters and uses an asynchronous callback to return the result.|
+| startContinuationDeviceManager(token: number, options: ContinuationExtraParams, callback: AsyncCallback\<void>): void | Starts the device selection module to show the list of available devices. This API uses an asynchronous callback to return the result.|
+| startContinuationDeviceManager(token: number, options?: ContinuationExtraParams): Promise\<void> | Starts the device selection module to show the list of available devices. This API uses a promise to return the result.|
+| updateContinuationState(token: number, deviceId: string, status: DeviceConnectState, callback: AsyncCallback\<void>): void | Instructs the device selection module to update the device connection state. This API uses an asynchronous callback to return the result.|
+| updateContinuationState(token: number, deviceId: string, status: DeviceConnectState): Promise\<void> | Instructs the device selection module to update the device connection state. This API uses a promise to return the result.|
+| unregisterContinuation(token: number, callback: AsyncCallback\<void>): void | Deregisters the continuation management service. This API uses an asynchronous callback to return the result.|
+| unregisterContinuation(token: number): Promise\<void> | Deregisters the continuation management service. This API uses a promise to return the result.|
+
+## How to Develop
+1. Import the **continuationManager** module.
+
+    ```ts
+    import continuationManager from '@ohos.continuation.continuationManager';
+    ```
+
+2. Apply for the **DISTRIBUTED_DATASYNC** permission.
+
+    The permission application operation varies according to the ability model in use. In the FA mode, add the required permission in the `config.json` file, as follows:
+
+    ```json
+    {
+        "module": {
+            "reqPermissions": [
+                {
+                    "name": "ohos.permission.DISTRIBUTED_DATASYNC"
+                }
+            ]
+        }
+    }
+    ```
+
+    This permission must also be granted by the user through a dialog box when the application is started for the first time. The sample code is as follows:
+
+    ```ts
+    import abilityAccessCtrl from "@ohos.abilityAccessCtrl";
+    import bundle from '@ohos.bundle';
+    import featureAbility from '@ohos.ability.featureAbility';
+
+    async function requestPermission() {
+        let permissions: Array<string> = [
+            "ohos.permission.DISTRIBUTED_DATASYNC"
+        ];
+        let needGrantPermission: boolean = false;
+        let atManager: abilityAccessCtrl.AtManager = abilityAccessCtrl.createAtManager();
+        let applicationInfo = await bundle.getApplicationInfo('ohos.samples.etsDemo', 0, 100);
+        for (let i = 0; i < permissions.length; i++) {
+            let result = await atManager.verifyAccessToken(applicationInfo.accessTokenId, permissions[i]);
+            // Check whether the permission is granted.
+            if (result == abilityAccessCtrl.GrantStatus.PERMISSION_GRANTED) {
+                needGrantPermission = true;
+                break;
+            }
+        }
+        // If the permission is not granted, call requestPermissionsFromUser to apply for the permission.
+        if (needGrantPermission) {
+            await featureAbility.getContext().requestPermissionsFromUser(permissions, 1);
+        } else {
+            console.info('app permission already granted');
+        }
+    }
+    ```
+
+    In the stage model, add the required permission in the `module.json5` file. The sample code is as follows:
+
+    ```json
+    {
+        "module": {
+            "requestPermissions": [
+                {
+                    "name": "ohos.permission.DISTRIBUTED_DATASYNC"
+                }
+            ]
+        }
+    }
+    ```
+
+    ```ts
+    import abilityAccessCtrl from "@ohos.abilityAccessCtrl";
+    import bundle from '@ohos.bundle';
+
+    async function requestPermission() {
+        let permissions: Array<string> = [
+            "ohos.permission.DISTRIBUTED_DATASYNC"
+        ];
+        let needGrantPermission: boolean = false;
+        let atManger: abilityAccessCtrl.AtManager = abilityAccessCtrl.createAtManager();
+        let applicationInfo = await bundle.getApplicationInfo('ohos.samples.continuationmanager', 0, 100);
+        for (const permission of permissions) {
+            try {
+                let grantStatus = await atManger.verifyAccessToken(applicationInfo.accessTokenId, permission);
+                // Check whether the permission is granted.
+                if (grantStatus === abilityAccessCtrl.GrantStatus.PERMISSION_DENIED) {
+                    needGrantPermission = true;
+                    break;
+                }
+            } catch (err) {
+                console.error('app permission query grant status error' + JSON.stringify(err));
+                needGrantPermission = true;
+                break;
+            }
+        }
+        // If the permission is not granted, call requestPermissionsFromUser to apply for the permission.
+        if (needGrantPermission) {
+            try {
+                // globalThis.context is Ability.context, which must be assigned a value in the MainAbility.ts file in advance.
+                await atManger.requestPermissionsFromUser(globalThis.context, permissions);
+            } catch (err) {
+                console.error('app permission request permissions error' + JSON.stringify(err));
+            }
+        } else {
+            console.info('app permission already granted');
+        }
+    }
+    ```
+
+3. Register the continuation management service and obtain a token.
+
+    The sample code is as follows:
+
+    ```ts
+    let token: number = -1; // Used to save the token returned after the registration. The token will be used when listening for device connection/disconnection events, starting the device selection module, and updating the device connection state.
+    try {
+        continuationManager.registerContinuation().then((data) => {
+            console.info('registerContinuation finished, ' + JSON.stringify(data));
+            token = data; // Obtain a token and assign a value to the token variable.
+        }).catch((err) => {
+            console.error('registerContinuation failed, cause: ' + JSON.stringify(err));
+        });
+    } catch (err) {
+        console.error('registerContinuation failed, cause: ' + JSON.stringify(err));
+    }
+    ```
+
+4. Listen for the device connection/disconnection state.
+
+    The sample code is as follows:
+
+    ```ts
+    let remoteDeviceId: string = ""; // Used to save the information about the remote device selected by the user, which will be used for cross-device continuation or collaboration.
+
+    try {
+        // The token parameter is the token obtained during the registration.
+        continuationManager.on("deviceSelected", token, (continuationResults) => {
+            console.info('registerDeviceSelectedCallback len: ' + continuationResults.length);
+            if (continuationResults.length <= 0) {
+                console.info('no selected device');
+                return;
+            }
+            remoteDeviceId = continuationResults[0].id; // Assign the deviceId of the first selected remote device to the remoteDeviceId variable.
+
+            // Pass the remoteDeviceId parameter to want.
+            let want = {
+                deviceId: remoteDeviceId,
+                bundleName: 'ohos.samples.continuationmanager',
+                abilityName: 'EntryAbility'
+            };
+            globalThis.abilityContext.startAbility(want).then((data) => {
+                console.info('StartRemoteAbility finished, ' + JSON.stringify(data));
+            }).catch((err) => {
+                console.error('StartRemoteAbility failed, cause: ' + JSON.stringify(err));
+            });
+        });
+    } catch (err) {
+        console.error('on failed, cause: ' + JSON.stringify(err));
+    }
+    ```
+
+    The preceding multi-device collaboration operation is performed across devices in the stage model. For details about this operation in the FA model, see [Page Ability Development](fa-pageability.md).
+
+    You can also instruct the device selection module to update the device connection state. The sample code is as follows:
+
+    ```ts
+    // Set the device connection state.
+    let deviceConnectStatus: continuationManager.DeviceConnectState = continuationManager.DeviceConnectState.CONNECTED;
+
+    // The token parameter is the token obtained during the registration, and the remoteDeviceId parameter is the remoteDeviceId obtained.
+    try {
+        continuationManager.updateContinuationState(token, remoteDeviceId, deviceConnectStatus).then((data) => {
+            console.info('updateContinuationState finished, ' + JSON.stringify(data));
+        }).catch((err) => {
+            console.error('updateContinuationState failed, cause: ' + JSON.stringify(err));
+        });
+    } catch (err) {
+        console.error('updateContinuationState failed, cause: ' + JSON.stringify(err));
+    }
+    ```
+
+    Listen for the device disconnection state so that the user can stop cross-device continuation or collaboration in time. The sample code is as follows:
+
+    ```ts
+    try {
+        // The token parameter is the token obtained during the registration.
+        continuationManager.on("deviceUnselected", token, (continuationResults) => {
+            console.info('onDeviceUnselected len: ' + continuationResults.length);
+            if (continuationResults.length <= 0) {
+                console.info('no unselected device');
+                return;
+            }
+
+            // Update the device connection state.
+            let unselectedDeviceId: string = continuationResults[0].id; // Assign the deviceId of the first deselected remote device to the unselectedDeviceId variable.
+            let deviceConnectStatus: continuationManager.DeviceConnectState = continuationManager.DeviceConnectState.DISCONNECTING; // Device disconnected.
+
+            // The token parameter is the token obtained during the registration, and the unselectedDeviceId parameter is the unselectedDeviceId obtained.
+            continuationManager.updateContinuationState(token, unselectedDeviceId, deviceConnectStatus).then((data) => {
+                console.info('updateContinuationState finished, ' + JSON.stringify(data));
+            }).catch((err) => {
+                console.error('updateContinuationState failed, cause: ' + JSON.stringify(err));
+            });
+        });
+    } catch (err) {
+        console.error('updateContinuationState failed, cause: ' + JSON.stringify(err));
+    }
+    ```
+
+5. Start the device selection module to show the list of available devices on the network.
+
+    The sample code is as follows:
+
+    ```ts
+    // Filter parameters.
+    let continuationExtraParams = {
+        deviceType: ["00E"], // Device type.
+        continuationMode: continuationManager.ContinuationMode.COLLABORATION_SINGLE // Single-choice mode of the device selection module.
+    };
+
+    try {
+        // The token parameter is the token obtained during the registration.
+        continuationManager.startContinuationDeviceManager(token, continuationExtraParams).then((data) => {
+            console.info('startContinuationDeviceManager finished, ' + JSON.stringify(data));
+        }).catch((err) => {
+            console.error('startContinuationDeviceManager failed, cause: ' + JSON.stringify(err));
+        });
+    } catch (err) {
+        console.error('startContinuationDeviceManager failed, cause: ' + JSON.stringify(err));
+    }
+    ```
+
+6. If you do not need to perform cross-device migration or collaboration operations, you can deregister the continuation management service, by passing the token obtained during the registration.
+
+    The sample code is as follows:
+
+    ```ts
+    try {
+        // The token parameter is the token obtained during the registration.
+        continuationManager.unregisterContinuation(token).then((data) => {
+            console.info('unregisterContinuation finished, ' + JSON.stringify(data));
+        }).catch((err) => {
+            console.error('unregisterContinuation failed, cause: ' + JSON.stringify(err));
+        });
+    } catch (err) {
+        console.error('unregisterContinuation failed, cause: ' + JSON.stringify(err));
+    }
+    ```

en/application-dev/ability-deprecated/fa-brief.md

+# FA Model Overview
+
+## Overall Architecture
+
+Ability is the entry for application development in OpenHarmony.
+
+The core of ability development is the processing on ability lifecycle callbacks.
+
+The Feature Ability (FA) model can be used only for application development using API version 8 and earlier versions. In this model, there are PageAbility, ServiceAbility, DataAbility, and FormAbility.  
+- PageAbility implements the ArkUI and provides the capability for interacting with users.
+- ServiceAbility does not have a UI. It runs in the background and provides custom services for other abilities to invoke.
+- DataAbility does not have a UI. It runs in the background and enables other abilities to insert, delete, and query data.
+- FormAbility is used to implement widgets, a new UI display form available on OpenHarmony devices.
+
+> Note: Starting from API version 9, the stage model is recommended for application development.
+
+## Lifecycle
+
+Among all abilities, PageAbility has the most complex lifecycle, because it has a UI and acts as a touchpoint for interacting with users.
+**The following figure shows the lifecycle of PageAbility.**
+
+![fa-pageAbility-lifecycle](figures/fa-pageAbility-lifecycle.png)
+
+The other abilities do not involve foreground and background switch or the **onShow** and **onHide** callbacks.
+You can override the lifecycle callbacks in **app.js** or **app.ets** to process application logic.
+
+The **app.js** file provides only the **onCreate** and **onDestroy** callbacks, and the **app.ets** file provides the callbacks covering the entire lifecycle.
+
+## Process and Thread Model
+
+Each application runs in a process. In the FA model, each ability runs in an independent VM.
+
+When an ability is started, an application process as well as a thread for this ability is created. For an application that has multiple abilities, each ability runs in an independent thread. In the FA model, each ability is bound to an independent VM instance. In this way, abilities are isolated from each other.
+
+![fa-threading-model](figures/fa-threading-model.png)
+
+## Application Package Structure
+
+For details about the project directory structure of the FA model, see [OpenHarmony Project Overview](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-project-overview-0000001218440650#section4154183910141).
+
+For details about how to configure the application package structure of the FA model, see [Application Package Structure Configuration File](../quick-start/application-configuration-file-overview-fa.md).
+
+

en/application-dev/ability-deprecated/fa-dataability.md

+# Data Ability Development
+
+## When to Use
+
+A Data ability helps applications manage access to data stored by themselves and other applications. It also provides APIs for sharing data with other applications either on the same device or across devices.
+
+Data ability providers can customize data access-related APIs such as data inserting, deleting, updating, and querying, as well as file opening, and share data with other applications through these open APIs.
+
+## URI Introduction
+
+A Uniform Resource Identifier (URI) is used to identify a specific data item, such as a table in the database or a file on the disk. URIs used in OpenHarmony comply with the commonly used URI standard. A URI consists of the components:
+
+![fa-dataability-uri](figures/fa-dataability-uri.png)
+
+- **scheme**: name of the scheme used by the Data ability. The value is fixed at **dataability**.
+- **authority**: device ID. To access data on a remote device, set this component to the ID of the remote device. To access data on the local device, leave this component empty.
+- **path**: location of the specific resource to access.
+- **query**: query parameters.
+- **fragment**: subordinate resources to access.
+
+Example URIs:
+
+- Cross-device communication: **dataability://***device_id***/***com.domainname.dataability.persondata***/***person***/***10*
+- Local-device communication: **dataability:///***com.domainname.dataability.persondata***/***person***/***10*
+
+> **NOTE**
+> 
+> In the case of local-device communication, **device_id** is empty, and therefore, there are three slashes (/) after **dataability:**.
+
+## Available APIs
+
+**Table 1** Data ability lifecycle APIs
+|API|Description|
+|:------|:------|
+|onInitialized(info: AbilityInfo): void|Called during ability initialization to initialize the relational database (RDB).|
+|update(uri: string, valueBucket: rdb.ValuesBucket, predicates: dataAbility.DataAbilityPredicates, callback: AsyncCallback\<number>): void|Updates data in the database.|
+|query(uri: string, columns: Array\<string>, predicates: dataAbility.DataAbilityPredicates, callback: AsyncCallback\<ResultSet>): void|Queries data in the database.|
+|delete(uri: string, predicates: dataAbility.DataAbilityPredicates, callback: AsyncCallback\<number>): void|Deletes one or more data records from the database.|
+|normalizeUri(uri: string, callback: AsyncCallback\<string>): void|Normalizes the URI. A normalized URI applies to cross-device use, persistence, backup, and restore. When the context changes, it ensures that the same data item can be referenced.|
+|batchInsert(uri: string, valueBuckets: Array\<rdb.ValuesBucket>, callback: AsyncCallback\<number>): void|Inserts multiple data records into the database.|
+|denormalizeUri(uri: string, callback: AsyncCallback\<string>): void|Converts a normalized URI generated by **normalizeUri** into a denormalized URI.|
+|insert(uri: string, valueBucket: rdb.ValuesBucket, callback: AsyncCallback\<number>): void|Inserts a data record into the database.|
+|openFile(uri: string, mode: string, callback: AsyncCallback\<number>): void|Opens a file.|
+|getFileTypes(uri: string, mimeTypeFilter: string, callback: AsyncCallback\<Array\<string>>): void|Obtains the MIME type of a file.|
+|getType(uri: string, callback: AsyncCallback\<string>): void|Obtains the MIME type matching the data specified by the URI.|
+|executeBatch(ops: Array\<DataAbilityOperation>, callback: AsyncCallback\<Array\<DataAbilityResult>>): void|Operates data in the database in batches.|
+|call(method: string, arg: string, extras: PacMap, callback: AsyncCallback\<PacMap>): void|Calls a custom API.|
+
+
+## How to Develop
+### Creating a Data Ability
+
+1. To meet the basic requirements of the database storage service, implement the **Insert**, **Query**, **Update**, and **Delete** APIs in the **Data** class. The **BatchInsert** and **ExecuteBatch** APIs have already implemented the traversal logic, but not batch data processing.
+
+    The following code snippet shows how to create a Data ability:
+
+   ```javascript
+    import featureAbility from '@ohos.ability.featureAbility'
+    import dataAbility from '@ohos.data.dataAbility'
+    import dataRdb from '@ohos.data.rdb'
+
+    const TABLE_NAME = 'book'
+    const STORE_CONFIG = { name: 'book.db' }
+    const SQL_CREATE_TABLE = 'CREATE TABLE IF NOT EXISTS book(id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT NOT NULL, introduction TEXT NOT NULL)'
+    let rdbStore: dataRdb.RdbStore = undefined
+
+    export default {
+    onInitialized(abilityInfo) {
+        console.info('DataAbility onInitialized, abilityInfo:' + abilityInfo.bundleName)
+        let context = featureAbility.getContext()
+        dataRdb.getRdbStore(context, STORE_CONFIG, 1, (err, store) => {
+            console.info('DataAbility getRdbStore callback')
+            store.executeSql(SQL_CREATE_TABLE, [])
+            rdbStore = store
+        });
+    },
+    insert(uri, valueBucket, callback) {
+        console.info('DataAbility insert start')
+        rdbStore.insert(TABLE_NAME, valueBucket, callback)
+    },
+    batchInsert(uri, valueBuckets, callback) {
+        console.info('DataAbility batch insert start')
+        for (let i = 0;i < valueBuckets.length; i++) {
+            console.info('DataAbility batch insert i=' + i)
+            if (i < valueBuckets.length - 1) {
+                rdbStore.insert(TABLE_NAME, valueBuckets[i], (err: any, num: number) => {
+                    console.info('DataAbility batch insert ret=' + num)
+                })
+            } else {
+                rdbStore.insert(TABLE_NAME, valueBuckets[i], callback)
+            }
+        }
+    },
+    query(uri, columns, predicates, callback) {
+        console.info('DataAbility query start')
+        let rdbPredicates = dataAbility.createRdbPredicates(TABLE_NAME, predicates)
+        rdbStore.query(rdbPredicates, columns, callback)
+    },
+    update(uri, valueBucket, predicates, callback) {
+        console.info('DataAbilityupdate start')
+        let rdbPredicates = dataAbility.createRdbPredicates(TABLE_NAME, predicates)
+        rdbStore.update(valueBucket, rdbPredicates, callback)
+    },
+    delete(uri, predicates, callback) {
+        console.info('DataAbilitydelete start')
+        let rdbPredicates = dataAbility.createRdbPredicates(TABLE_NAME, predicates)
+        rdbStore.delete(rdbPredicates, callback)
+    }
+    };
+   ```
+
+2. Configure the submodule.
+
+   | JSON Field| Description                                                    |
+   | ------------ | ------------------------------------------------------------ |
+   | "name"       | Ability name, corresponding to the **Data** class name derived from **Ability**.                    |
+   | "type"       | Ability type, which is **Data** for a Data ability.                |
+   | "uri"        | URI used for communication.                                             |
+   | "visible"    | Whether the Data ability is visible to other applications. When this parameter is set to **true**, the Data ability can communicate with other applications.|
+
+   **config.json configuration example**
+
+   ```json
+   "abilities":[{
+       "srcPath": "DataAbility",
+       "name": ".DataAbility",
+       "icon": "$media:icon",
+       "srcLanguage": "ets",
+       "description": "$string:description_dataability",
+       "type": "data",
+       "visible": true,
+       "uri": "dataability://ohos.samples.etsdataability.DataAbility"
+    }]
+   ```
+
+### Accessing a Data ability
+#### Development Preparations
+
+Import the basic dependency packages and obtain the URI string for communicating with the Data submodule.
+
+The basic dependency packages include:
+- @ohos.ability.featureAbility
+- @ohos.data.dataAbility
+- @ohos.data.rdb
+
+#### Data Ability API Development
+
+
+1. Create a Data ability helper.
+
+   For details about the APIs provided by **DataAbilityHelper**, see [DataAbilityHelper Module](../reference/apis/js-apis-inner-ability-dataAbilityHelper.md).
+   ```js
+   // Different from the URI defined in the config.json file, the URI passed in the parameter has an extra slash (/), because there is a DeviceID parameter between the second and the third slash (/).
+   import featureAbility from '@ohos.ability.featureAbility'
+   import ohos_data_ability from '@ohos.data.dataAbility'
+   import ohos_data_rdb from '@ohos.data.rdb'
+
+   var urivar = "dataability:///com.ix.DataAbility"
+   var DAHelper = featureAbility.acquireDataAbilityHelper(
+    urivar
+   );
+   ```
+2. Construct RDB data.
+   ```js
+   var valuesBucket = {"name": "gaolu"}
+   var da = new ohos_data_ability.DataAbilityPredicates()
+   var valArray =new Array("value1");
+   var cars = new Array({"batchInsert1" : "value1",});
+   ```
+3. Use **insert** to insert data to the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.insert(
+    urivar,
+    valuesBucket,
+    (error, data) => {
+        console.log("DAHelper insert result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var datainsert = await DAHelper.insert(
+    urivar,
+    valuesBucket
+   );
+   ```
+4. Use **delete** to delete data from the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.delete(
+    urivar,
+    da,
+    (error, data) => {
+        console.log("DAHelper delete result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var datadelete = await DAHelper.delete(
+    urivar,
+    da,
+   );
+   ```
+5. Use **update** to update data in the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.update(
+    urivar
+    valuesBucket,
+    da,
+    (error, data) => {
+        console.log("DAHelper update result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var dataupdate = await DAHelper.update(
+    urivar,
+    valuesBucket,
+    da,
+   );
+   ```
+6. Use **query** to query data in the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.query(
+    urivar,
+    valArray,
+    da,
+    (error, data) => {
+        console.log("DAHelper query result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var dataquery = await DAHelper.query(
+    urivar,
+    valArray,
+    da
+   );
+   ```
+7. Use **batchInsert** to insert data in batches to the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.batchInsert(
+    urivar,
+    cars,
+    (error, data) => {
+        console.log("DAHelper batchInsert result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var databatchInsert = await DAHelper.batchInsert(
+    urivar,
+    cars
+   );
+   ```
+8. Use **executeBatch** to process data in batches in the Data submodule.
+   ```js
+   // Callback mode:
+   DAHelper.executeBatch(
+    urivar,
+    [
+        {
+            uri: urivar,
+            type: featureAbility.DataAbilityOperationType.TYPE_INSERT,
+            valuesBucket: {"executeBatch" : "value1",},
+            predicates: da,
+            expectedCount:0,
+            predicatesBackReferences: null,
+            interrupted:true,
+        }
+    ],
+    (error, data) => {
+        console.log("DAHelper executeBatch result: " + data)
+    }
+   );
+   ```
+   
+   ```js
+   // Promise mode:
+   var dataexecuteBatch = await DAHelper.executeBatch(
+    urivar,
+    [
+        {
+            uri: urivar,
+            type: featureAbility.DataAbilityOperationType.TYPE_INSERT,
+            valuesBucket:
+            {
+                "executeBatch" : "value1",
+            },
+            predicates: da,
+            expectedCount:0,
+            predicatesBackReferences: null,
+            interrupted:true,
+        }
+    ]
+   );
+   ```

en/application-dev/ability-deprecated/fa-pageability.md

+# Page Ability Development
+
+## Overview
+
+### Concepts
+
+The Page ability implements the ArkUI and provides the capability of interacting with developers. When you create an ability in DevEco Studio, DevEco Studio automatically creates template code.
+
+The capabilities related to the Page ability are implemented through the **featureAbility**, and the lifecycle callbacks are implemented through the callbacks in **app.js** or **app.ets**.
+
+### Page Ability Lifecycle
+
+Introduction to the Page ability lifecycle:
+
+The Page ability lifecycle defines all states of a Page ability, such as **INACTIVE**, **ACTIVE**, and **BACKGROUND**.
+
+The following figure shows the lifecycle state transition of the Page ability.
+
+![PageAbility-Lifecycle](figures/page-ability-lifecycle.png)
+
+
+Description of ability lifecycle states:
+
+  - **UNINITIALIZED**: The Page ability is not initialized. This is a temporary state, from which a Page ability changes directly to the **INITIAL** state upon its creation.
+
+  - **INITIAL**: The Page ability is initialized but not running. The Page ability enters the **INACTIVE** state after it is started.
+
+  - **INACTIVE**: The Page ability is visible but does not gain focus.
+
+  - **ACTIVE**: The Page ability runs in the foreground and has focus.
+
+  - **BACKGROUND**: The Page ability runs in the background. After being re-activated, the Page ability enters the **ACTIVE** state. After being destroyed, the Page ability enters the **INITIAL** state.
+
+The following figure shows the relationship between lifecycle callbacks and lifecycle states of the Page ability.
+
+![fa-pageAbility-lifecycle](figures/fa-pageAbility-lifecycle.png)
+
+You can override the lifecycle callbacks provided by the Page ability in the **app.js** or **app.ets** file. Currently, the **app.js** file provides only the **onCreate** and **onDestroy** callbacks, and the **app.ets** file provides the full lifecycle callbacks.
+
+### Launch Type
+
+The ability supports two launch types: singleton and multi-instance.
+
+You can specify the launch type by setting **launchType** in the **config.json** file.
+
+**Table 1** Startup modes
+
+| Launch Type    | Description    |Description            |
+| ----------- | -------  |---------------- |
+| standard    | Multi-instance  | A new instance is started each time an ability starts.|
+| singleton   | Singleton  | The ability has only one instance in the system. If an instance already exists when an ability is started, that instance is reused.|
+
+By default, **singleton** is used.
+
+
+## Development Guidelines
+
+### Available APIs
+
+**Table 2** APIs provided by featureAbility
+
+| API                                             | Description           |
+| --------------------------------------------------- | --------------- |
+| void startAbility(parameter: StartAbilityParameter) | Starts an ability.   |
+| Context getContext():                               | Obtains the application context.|
+| void terminateSelf()                                | Terminates the ability.    |
+| bool hasWindowFocus()                               | Checks whether the ability has focus.   |
+
+
+### Starting a Local Page Ability
+
+**Modules to Import**
+
+```js
+  import featureAbility from '@ohos.ability.featureAbility'
+```
+
+**Example**
+
+```javascript
+  import featureAbility from '@ohos.ability.featureAbility'
+  featureAbility.startAbility({
+      want: {
+          action: "",
+          entities: [""],
+          type: "",
+          deviceId: "",
+          bundleName: "com.example.myapplication",
+          /* In the FA model, abilityName consists of package and ability name. */
+          abilityName: "com.example.entry.secondAbility",
+          uri: ""
+      }
+  });
+```
+
+### Starting a Remote Page Ability
+>NOTE
+>
+>This feature applies only to system applications, since the **getTrustedDeviceListSync** API of the **DeviceManager** class is open only to system applications.
+
+**Modules to Import**
+
+```
+  import featureAbility from '@ohos.ability.featureAbility'
+  import deviceManager from '@ohos.distributedHardware.deviceManager';
+```
+
+**Example**
+```ts
+  function onStartRemoteAbility() {
+  console.info('onStartRemoteAbility begin');
+  let params;
+  let wantValue = {
+      bundleName: 'ohos.samples.etsDemo',
+      abilityName: 'ohos.samples.etsDemo.RemoteAbility',
+      deviceId: getRemoteDeviceId(),
+      parameters: params
+  };
+  console.info('onStartRemoteAbility want=' + JSON.stringify(wantValue));
+  featureAbility.startAbility({
+      want: wantValue
+  }).then((data) => {
+      console.info('onStartRemoteAbility finished, ' + JSON.stringify(data));
+  });
+  console.info('onStartRemoteAbility end');
+  }
+```
+
+Obtain **deviceId** from **DeviceManager**. The sample code is as follows:
+
+```ts
+  import deviceManager from '@ohos.distributedHardware.deviceManager';
+  let dmClass;
+  function getRemoteDeviceId() {
+      if (typeof dmClass === 'object' && dmClass != null) {
+          let list = dmClass.getTrustedDeviceListSync();
+          if (typeof (list) == 'undefined' || typeof (list.length) == 'undefined') {
+            console.log("EntryAbility onButtonClick getRemoteDeviceId err: list is null");
+            return;
+          }
+          console.log("EntryAbility onButtonClick getRemoteDeviceId success:" + list[0].deviceId);
+          return list[0].deviceId;
+      } else {
+          console.log("EntryAbility onButtonClick getRemoteDeviceId err: dmClass is null");
+      }
+  }
+```
+
+In the cross-device scenario, the application must also apply for the data synchronization permission from end users. The sample code is as follows:
+
+```ts
+  import abilityAccessCtrl from "@ohos.abilityAccessCtrl";
+  import bundle from '@ohos.bundle';
+  async function RequestPermission() {
+      console.info('RequestPermission begin');
+      let array: Array<string> = ["ohos.permission.DISTRIBUTED_DATASYNC"];
+      let bundleFlag = 0;
+      let tokenID = undefined;
+      let userID = 100;
+      let  appInfo = await bundle.getApplicationInfo('ohos.samples.etsDemo', bundleFlag, userID);
+      tokenID = appInfo.accessTokenId;
+      let atManager = abilityAccessCtrl.createAtManager();
+      let requestPermissions: Array<string> = [];
+      for (let i = 0;i < array.length; i++) {
+          let result = await atManager.verifyAccessToken(tokenID, array[i]);
+          console.info("verifyAccessToken result:" + JSON.stringify(result));
+          if (result != abilityAccessCtrl.GrantStatus.PERMISSION_GRANTED) {
+              requestPermissions.push(array[i]);
+          }
+      }
+      console.info("requestPermissions:" + JSON.stringify(requestPermissions));
+      if (requestPermissions.length == 0 || requestPermissions == []) {
+          return;
+      }
+      let context = featureAbility.getContext();
+      context.requestPermissionsFromUser(requestPermissions, 1, (data)=>{
+          console.info("data:" + JSON.stringify(data));
+          console.info("data requestCode:" + data.requestCode);
+          console.info("data permissions:" + data.permissions);
+          console.info("data authResults:" + data.authResults);
+      });
+      console.info('RequestPermission end');
+  }
+```
+
+### Lifecycle APIs
+
+**Table 3** Lifecycle callbacks
+
+| API      | Description                                                        |
+| ------------ | ------------------------------------------------------------ |
+| onShow()     | Called when the ability is switched from the background to the foreground. In this case, the ability is visible to users.|
+| onHide()     | Called when the ability is switched from the foreground to the background. In this case, the ability is invisible to users.|
+| onDestroy()  | Called when the ability is destroyed. In this callback, you can make preparations for application exit, such as recycling resources and clearing the cache.|
+| onCreate()   | Called when the ability is created for the first time. You can initialize the application in this callback.|
+| onInactive() | Called when the ability loses focus. An ability loses focus when it is about to enter the background state.|
+| onActive()   | Called when the ability is switched to the foreground and gains focus.     |
+
+**Example**
+
+You need to override the lifecycle callbacks except **onCreate()** and **onDestroy()** in **app.js** or **app.ets**. The **onCreate()** and **onDestroy()** callbacks are automatically generated in the template code provided by DevEco Studio.
+
+```javascript
+export default {
+  onCreate() {
+    console.info('Application onCreate')
+  },
+  onDestroy() {
+    console.info('Application onDestroy')
+  },
+  onShow(){
+    console.info('Application onShow')
+  },
+  onHide(){
+    console.info('Application onHide')
+  },
+  onInactive(){
+    console.info('Application onInactive')
+  },
+  onActive(){
+    console.info('Application onActive')
+  },
+}
+```

en/application-dev/ability-deprecated/fa-serviceability.md

+# Service Ability Development
+
+## When to Use
+A Service ability is used to run tasks in the background, such as playing music or downloading files. It does not provide a UI for user interaction. Service abilities can be started by other applications or abilities and can keep running in the background even after the user switches to another application.
+
+## Lifecycle APIs
+
+**Table 1** Service ability lifecycle APIs
+|API|Description|
+|:------|:------|
+|onStart?(): void|Called to initialize a Service ability when the Service ability is being created. This callback is invoked only once in the entire lifecycle of a Service ability.|
+|onCommand?(want: Want, startId: number): void|Called every time a Service ability is created on the client. You can collect calling statistics and perform initialization operations in this callback.|
+|onConnect?(want: Want): rpc.RemoteObject|Called when another ability is connected to the Service ability.|
+|onDisconnect?(want: Want): void|Called when another ability is disconnected from the Service ability.|
+|onStop?(): void|Called when the Service ability is being destroyed. You should override this callback for your Service ability to clear its resources, such as threads and registered listeners.|
+
+The differences between **onCommand()** and **onConnect()** are as follows:
+ - The **onCommand()** callback is triggered each time the client starts the Service ability by calling **startAbility** or **startAbilityForResult**.
+ - The **onConnect()** callback is triggered each time the client establishes a new connection with the Service ability by calling **connectAbility**.
+
+## How to Develop
+
+### Creating and Registering a Service Ability
+
+1. Override the Service ability-related lifecycle callbacks to implement your own logic for processing interaction requests.
+   
+   ```ts
+    export default {
+        onStart() {
+            console.log('ServiceAbility onStart');
+        },
+        onCommand(want, startId) {
+            console.log('ServiceAbility onCommand');
+        },
+        onConnect(want) {
+            console.log('ServiceAbility OnConnect');
+            // Below lists the implementation of ServiceAbilityStub.
+            return new ServiceAbilityStub('test');
+        },
+        onDisconnect(want) {
+            console.log('ServiceAbility OnDisConnect');
+        },
+        onStop() {
+            console.log('ServiceAbility onStop');
+        }
+    }
+   ```
+   
+2. Register a Service ability.
+
+   Declare the Service ability in the **config.json** file by setting its **type** attribute to **service**.
+   
+   ```json
+    {
+      "module": {
+        "abilities": [
+          {
+            "name": ".ServiceAbility",
+            "type": "service",
+            "visible": true
+            ...
+          }
+        ]
+        ...
+      }
+      ...
+    }
+   ```
+
+
+
+### Starting a Service Ability
+
+The **Ability** class provides the **startAbility()** API for you to start another Service ability by passing a **Want** object.
+
+To set information about the target Service ability, you can first construct a **Want** object with the **bundleName** and **abilityName** parameters specified.  
+
+- **bundleName** specifies the bundle name of the target application.
+- **abilityName** specifies the target ability name.
+
+The following code snippet shows how to start a Service ability running on the local device:
+
+```ts
+import featureAbility from '@ohos.ability.featureAbility'
+
+featureAbility.startAbility(
+    {
+        want:
+        {
+            bundleName: "com.jstest.service",
+            abilityName: "com.jstest.service.ServiceAbility"
+        }
+    }
+).then((err) => {
+    console.log("startService success");
+}).catch (err => {
+    console.log("startService FAILED");
+});
+```
+
+In the preceding code, the **startAbility()** API is used to start the Service ability.
+- If the Service ability is not running, the system initializes the Service ability, and calls **onStart()** and **onCommand()** on the Service ability in sequence.
+- If the Service ability is running, the system directly calls **onCommand()** on the Service ability.
+
+The following code snippet shows how to start a Service ability running on the remote device. For details, see [Connecting to a Remote Service Ability](#connecting-to-a-remote-service-ability).
+
+```ts
+import featureAbility from '@ohos.ability.featureAbility'
+
+featureAbility.startAbility(
+    {
+        want:
+        {
+            deviceId: remoteDeviceId,    // Remote device ID.
+            bundleName: "com.jstest.service",
+            abilityName: "com.jstest.service.ServiceAbility"
+        }
+    }
+).then((err) => {
+    console.log("startService success");
+}).catch (err => {
+    console.log("startService FAILED");
+});
+```
+
+
+### Stopping a Service Ability
+
+  In normal cases, a Service ability can be stopped by itself or by the system.
+   - The Service ability can call **particleAbility.terminateSelf()** to stop itself.
+   - If the application process where the Service ability is located exits, the Service ability is reclaimed along with the process.
+   - If the Service ability is only accessed through **connectAbility()** (the **onCommand()** callback has never been triggered), the system stops the Service ability when the last connection to the Service ability is disconnected.
+
+### Connecting to a Local Service Ability
+
+If a Service ability wants to interact with a Page ability or a Service ability in another application, you must first create a connection. A Service ability allows other abilities to connect to it through **connectAbility()**.
+
+
+You can use either of the following methods to connect to a Service ability:
+
+1. Using the IDL to automatically generate code
+
+    Use OpenHarmony Interface Definition Language (IDL) to automatically generate the corresponding client, server, and **IRemoteObject** code. For details, see [Development Using TS](../IDL/idl-guidelines.md#development-using-ts).
+
+2. Writing code in the corresponding file
+
+    When using **connectAbility()**, pass the **Want** and **ConnectOptions** objects of the target Service ability, where **ConnectOptions** encapsulates the following three callbacks that need to be implemented.
+     - **onConnect()**: callback used for processing when the Service ability is connected.
+     - **onDisconnect()**: callback used for processing when the Service ability is disconnected.
+     - **onFailed()**: callback used for processing when the connection to the Service ability fails.
+
+    The following code snippet shows how to implement the callbacks:
+
+    ```ts
+    import prompt from '@system.prompt'
+    
+    var option = {
+        onConnect: function onConnectCallback(element, proxy) {
+            console.log(`onConnectLocalService onConnectDone`);
+            if (proxy === null) {
+                prompt.showToast({
+                    message: "Connect service failed"
+                });
+                return;
+            }
+            // After obtaining the proxy of the Service ability, the calling ability can communicate with the Service ability.
+            let data = rpc.MessageParcel.create();
+            let reply = rpc.MessageParcel.create();
+            let option = new rpc.MessageOption();
+            data.writeString("InuptString");
+            proxy.sendRequest(0, data, reply, option);
+            prompt.showToast({
+                message: "Connect service success"
+            });
+        },
+        onDisconnect: function onDisconnectCallback(element) {
+            console.log(`onConnectLocalService onDisconnectDone element:${element}`);
+            prompt.showToast({
+                message: "Disconnect service success"
+            });
+        },
+        onFailed: function onFailedCallback(code) {
+            console.log(`onConnectLocalService onFailed errCode:${code}`);
+            prompt.showToast({
+                message: "Connect local service onFailed"
+            });
+        }
+    };
+    ```
+
+    The following code snippet shows how to connect to a local Service ability:
+
+    ```ts
+    import featureAbility from '@ohos.ability.featureAbility'
+    
+    let want = {
+        bundleName: "com.jstest.service",
+        abilityName: "com.jstest.service.ServiceAbility"
+    };
+    let connectId = featureAbility.connectAbility(want, option);
+    ```
+
+    When a Service ability is connected, the **onConnect()** callback is invoked and returns an **IRemoteObject** defining the proxy used for communicating with the Service ability.  OpenHarmony provides the default implementation of **IRemoteObject**. You can inherit **rpc.RemoteObject** to create a custom implementation class for interaction with the Service ability. For details, see the [RPC API Reference](..\reference\apis\js-apis-rpc.md).
+
+    The following code snippet shows how the Service ability returns itself to the calling ability:
+
+    ```ts
+    import rpc from "@ohos.rpc"
+    
+    class ServiceAbilityStub extends rpc.RemoteObject {
+        constructor(des: any) {
+            if (typeof des === 'string') {
+                super(des);
+            } else {
+                console.log("Error, the input param is not string");
+                return;
+            }
+        }
+    
+        onRemoteRequest(code: number, data: any, reply: any, option: any) {
+            console.log("onRemoteRequest called");
+            // Execute the service logic.
+            if (code === 1) {
+                // Sort the input strings.
+                let string = data.readString();
+                console.log(`Input string = ${string}`);
+                let result = Array.from(string).sort().join('');
+                console.log(`Output result = ${result}`);
+                reply.writeString(result);
+            } else {
+                console.log(`Unknown request code`);
+            }
+            return true;
+        }
+    }
+    
+    export default {
+        onStart() {
+            console.log('ServiceAbility onStart');
+        },
+        onCommand(want, startId) {
+            console.log('ServiceAbility onCommand');
+        },
+        onConnect(want) {
+            console.log('ServiceAbility OnConnect');
+            return new ServiceAbilityStub('ServiceAbilityRemoteObject');
+        },
+        onDisconnect(want) {
+            console.log('ServiceAbility OnDisConnect');
+        },
+        onStop() {
+            console.log('ServiceAbility onStop');
+        }
+    }
+    ```
+
+### Connecting to a Remote Service Ability
+
+This feature applies only to system applications. The method of creating a **ConnectOptions** object for connecting to a remote Service ability is similar to that for connecting to a local Service ability. The differences are as follows:
+ - The application must apply for the data synchronization permission from the user.
+ - **Want** of the target Service ability must contain the remote device ID.
+
+> **NOTE**
+>
+> The **getTrustedDeviceList** API of **DeviceManager** is open only to system applications. Currently, only system applications can connect to a remote Service ability.
+>
+> For details about the API definition, see [Device Management](..\reference\apis\js-apis-device-manager.md).
+
+The data synchronization permission is required in the cross-device scenario. Configure the permission in the **config.json** file.
+
+```json
+{
+  ...
+  "module": {
+    ...
+    "reqPermissions": [{
+      "name": "ohos.permission.DISTRIBUTED_DATASYNC"
+    }]
+  }
+}
+```
+
+The **DISTRIBUTED_DATASYNC** permission is user granted. Therefore, your application, when being started, must display a dialog box to request the permission. The sample code is as follows:
+
+```ts
+import abilityAccessCtrl from "@ohos.abilityAccessCtrl"
+import bundle from '@ohos.bundle'
+
+async function RequestPermission() {
+    console.info('RequestPermission begin');
+    let array: Array<string> = ["ohos.permission.DISTRIBUTED_DATASYNC"];
+    let bundleFlag = 0;
+    let tokenID = undefined;
+    let userID = 100;
+    let appInfo = await bundle.getApplicationInfo('ohos.samples.etsDemo', bundleFlag, userID);
+    tokenID = appInfo.accessTokenId;
+    let atManager = abilityAccessCtrl.createAtManager();
+    let requestPermissions: Array<string> = [];
+    for (let i = 0;i < array.length; i++) {
+        let result = await atManager.verifyAccessToken(tokenID, array[i]);
+        console.info("verifyAccessToken result:" + JSON.stringify(result));
+        if (result != abilityAccessCtrl.GrantStatus.PERMISSION_GRANTED) {
+            requestPermissions.push(array[i]);
+        }
+    }
+    console.info("requestPermissions:" + JSON.stringify(requestPermissions));
+    if (requestPermissions.length == 0 || requestPermissions == []) {
+        return;
+    }
+    let context = featureAbility.getContext();
+    context.requestPermissionsFromUser(requestPermissions, 1, (data)=>{
+        console.info("data:" + JSON.stringify(data));
+    });
+    console.info('RequestPermission end');
+}
+```
+
+To obtain the device ID, import the **@ohos.distributedHardware.deviceManager** module, which provides **getTrustedDeviceList** to obtain the remote device ID. For details about how to use the API, see [Device Management](..\reference\apis\js-apis-device-manager.md).
+
+To connect to a remote Service ability, you only need to define **deviceId** in **Want**. The sample code is as follows:
+
+```ts
+import featureAbility from '@ohos.ability.featureAbility'
+
+let want = {
+    deviceId: remoteDeviceId,
+    bundleName: "com.jstest.service",
+    abilityName: "com.jstest.service.ServiceAbility"
+};
+let connectId = featureAbility.connectAbility(want, option);
+```
+
+The other implementations are the same as those for the connection to a local Service ability. For details, see the sample code provided under [Connecting to a Local Service Ability](#connecting-to-a-local-service-ability).

en/application-dev/ability-deprecated/stage-ability-continuation.md

+# Ability Continuation Development
+
+## When to Use
+
+Ability continuation is to continue the current mission of an application, including the UI component state variables and distributed objects, on another device. The UI component state variables are used to synchronize UI data, and the distributed objects are used to synchronize memory data.
+
+## Available APIs
+
+The following table lists the APIs used for ability continuation. For details about the APIs, see [Ability](../reference/apis/js-apis-application-ability.md).
+
+**Table 1** Ability continuation APIs
+
+|API| Description|
+|:------ | :------|
+| onContinue(wantParam : {[key: string]: any}): OnContinueResult | Called by the initiator to store the data required for continuation. The return value indicates whether the continuation request is accepted. The value **AGREE** means that the continuation request is accepted, **REJECT** means that the continuation request is rejected, and **MISMATCH** means a version mismatch.|
+| onCreate(want: Want, param: AbilityConstant.LaunchParam): void; | Called by the target to restore the data and UI page in the multi-instance ability scenario.|
+| onNewWant(want: Want, launchParams: AbilityConstant.LaunchParam): void; | Called by the target to restore the data and UI page in the singleton ability scenario.|
+
+
+
+**Figure 1** Ability continuation development
+
+![continuation_dev](figures/continuation-info.png)
+
+In effect, ability continuation is a cross-device ability startup that carries data. When a continuation action is initiated, the system on device A calls back **onContinue()** of the application. You must implement storage of the current data in this API. Then, the system initiates a cross-device ability startup on device B and transmits the data to device B. The system on device B calls back **onCreate()** or **onNewWant()**. You must implement restoration of the transmitted data in this API.
+
+## How to Develop
+
+The code snippets provided below are all from [Sample](https://gitee.com/openharmony/ability_dmsfwk/tree/master/services/dtbschedmgr/test/samples/continuationManualTestSuite).
+
+### Application Continuation
+
+1. Modify the configuration file.
+
+   - Configure the application to support ability continuation.
+
+     Set the **continuable** field in the **module.json5** file to **true**. The default value is **false**. If this parameter is set to **false**, the application cannot be continued on another device.
+   
+     ```javascript
+     {
+       "module": {
+         "abilities": [
+           {
+             "continuable": true
+           }
+         ]
+       }
+     }
+     ```
+     
+
+
+
+   - Configure the application startup type.
+
+     If **launchType** is set to **standard** in the **module.json5** file, the application is of the multi-instance launch type. During ability continuation, regardless of whether the application is already open, the target starts the application and restores the UI page. If **launchType** is set to **singleton**, the application is of the singleton launch type. If the application is already open, the target clears the existing page stack and restores the UI page. For more information, see "Launch Type" in [Ability Development](./stage-ability.md).
+     
+     Configure a multi-instance application as follows:
+     
+     ```javascript
+     {
+       "module": {
+         "abilities": [
+           {
+             "launchType": "standard"
+           }
+         ]
+       }
+     }
+     ```
+     
+     Configure a singleton application as follows or retain the default settings of **launchType**:
+     
+     ```javascript
+     {
+       "module": {
+         "abilities": [
+           {
+             "launchType": "singleton"
+           }
+         ]
+       }
+     }
+     ```
+     
+     
+     
+   - Apply for the distributed permissions.
+
+     Declare the **DISTRIBUTED_DATASYNC** permission in the **module.json5** file for the application.
+
+     ```javascript
+     "requestPermissions": [
+            {
+                "name": "ohos.permission.DISTRIBUTED_DATASYNC"
+            },
+     ```
+
+     
+
+     This permission must be granted by the user in a dialog box when the application is started for the first time. To enable the application to display a dialog box to ask for the permission, add the following code to **onWindowStageCreate** of the **Ability** class:
+
+     ```javascript
+        requestPermissions = async () => {
+            let permissions: Array<string> = [
+                "ohos.permission.DISTRIBUTED_DATASYNC"
+            ];
+            let needGrantPermission = false
+            let accessManger = accessControl.createAtManager()
+            Logger.info("app permission get bundle info")
+            let bundleInfo = await bundle.getApplicationInfo(BUNDLE_NAME, 0, 100)
+            Logger.info(`app permission query permission ${bundleInfo.accessTokenId.toString()}`)
+            for (const permission of permissions) {
+                Logger.info(`app permission query grant status ${permission}`)
+                try {
+                    let grantStatus = await accessManger.verifyAccessToken(bundleInfo.accessTokenId, permission)
+                    if (grantStatus === PERMISSION_REJECT) {
+                        needGrantPermission = true
+                        break;
+                    }
+                } catch (err) {
+                    Logger.error(`app permission query grant status error ${permission} ${JSON.stringify(err)}`)
+                    needGrantPermission = true
+                    break;
+                }
+            }
+            if (needGrantPermission) {
+                Logger.info("app permission needGrantPermission")
+                try {
+                    await accessManger.requestPermissionsFromUser(this.context, permissions)
+                } catch (err) {
+                    Logger.error(`app permission ${JSON.stringify(err)}`)
+                }
+            } else {
+                Logger.info("app permission already granted")
+            }
+        }
+     ```
+
+
+
+
+2. Implement the **onContinue()** API.
+
+   The **onContinue()** API is called by the initiator to save the UI component state variables and memory data and prepare for continuation. After the application completes the continuation preparation, the system must return either **OnContinueResult.AGREE(0)** to accept the continuation request or an error code to reject the request. If this API is not implemented, the system rejects the continuation request by default.
+
+   Modules to import:
+
+   ```javascript
+   import UIAbility from '@ohos.app.ability.UIAbility';
+   import AbilityConstant from '@ohos.app.ability.AbilityConstant';
+   ```
+
+   To implement ability continuation, you must implement this API and have the value **AGREE** returned.
+
+   You can obtain the target device ID (identified by the key **targetDevice**) and the version number (identified by the key **version**) of the application installed on the target device from the **wantParam** parameter of this API. The version number can be used for compatibility check. If the current application version is incompatible with that on the target device, **OnContinueResult.MISMATCH** can be returned to reject the continuation request.
+
+   Example
+
+   ```javascript
+        onContinue(wantParam : {[key: string]: any}) {
+            Logger.info(`onContinue version = ${wantParam.version}, targetDevice: ${wantParam.targetDevice}`)
+            let workInput = AppStorage.Get<string>('ContinueWork');
+            // Set the user input data into wantParam.
+            wantParam["work"] = workInput // set user input data into want params
+            Logger.info(`onContinue input = ${wantParam["input"]}`);
+            return AbilityConstant.OnContinueResult.AGREE
+        }
+   ```
+
+   
+
+3. Implement the continuation logic in the **onCreate()** or **onNewWant()** API.
+
+   The **onCreate()** API is called by the target. When the ability is started on the target device, this API is called to instruct the application to synchronize the memory data and UI component state, and triggers page restoration after the synchronization is complete. If the continuation logic is not implemented, the ability will be started in common startup mode and the page cannot be restored.
+
+   The target device determines whether the startup is **LaunchReason.CONTINUATION** based on **launchReason** in **onCreate()**.
+   
+   After data restore is complete, call **restoreWindowStage** to trigger page restoration.
+   
+   
+
+   You can also use **want.parameters.version** in the **want** parameter to obtain the application version number of the initiator.
+   
+   Example
+   
+   ```javascript
+    import UIAbility from '@ohos.app.ability.UIAbility';
+    import distributedObject from '@ohos.data.distributedDataObject';
+    
+    export default class EntryAbility extends UIAbility {
+        storage : LocalStorag;
+
+        onCreate(want, launchParam) {
+            Logger.info(`EntryAbility onCreate ${AbilityConstant.LaunchReason.CONTINUATION}`)
+            if (launchParam.launchReason == AbilityConstant.LaunchReason.CONTINUATION) {
+                // Obtain the user data from the want parameter.
+                let workInput = want.parameters.work
+                Logger.info(`work input ${workInput}`)
+                AppStorage.SetOrCreate<string>('ContinueWork', workInput)
+   
+                this.storage = new LocalStorage();
+                this.context.restoreWindowStage(this.storage);
+            }
+        }
+    }
+   ```
+For a singleton ability, use **onNewWant()** to achieve the same implementation.
+
+### Data Continuation
+
+Use distributed objects.
+
+Distributed objects allow cross-device data synchronization like local variables. For two devices that form a Super Device, when data in the distributed data object of an application is added, deleted, or modified on a device, the data for the same application is also updated on the other device. Both devices can listen for the data changes and online and offline states of the other. For details, see [Distributed Data Object Development](../database/database-distributedobject-guidelines.md).
+
+In the ability continuation scenario, the distributed data object is used to synchronize the memory data from the local device to the target device.
+
+- In **onContinue()**, the initiator saves the data to be migrated to the distributed object, calls the **save()** API to save the data and synchronize the data to the target device, sets the session ID, and sends the session ID to the target device through **wantParam**.
+
+  ```javascript
+     import UIAbility from '@ohos.app.ability.UIAbility';
+     import distributedObject from '@ohos.data.distributedDataObject';
+  
+     var g_object = distributedObject.createDistributedObject({data:undefined});
+  
+     export default class EntryAbility extends UIAbility {
+         sessionId : string;
+  
+      onContinue(wantParam : {[key: string]: any}) {
+        Logger.info(`onContinue version = ${wantParam.version}, targetDevice: ${wantParam.targetDevice}`)
+
+        if (g_object.__sessionId === undefined) {
+            this.sessionId = distributedObject.genSessionId()
+            Logger.info(`onContinue generate new sessionId`)
+        }
+        else {
+            this.sessionId = g_object.__sessionId;
+        }
+
+        wantParam["session"] = this.sessionId
+        g_object.data = AppStorage.Get<string>('ContinueStudy');
+        Logger.info(`onContinue sessionId = ${this.sessionId}, name = ${g_object.data}`)
+        g_object.setSessionId(this.sessionId);
+        g_object.save(wantParam.targetDevice, (result, data)=>{
+            Logger.info("save callback");
+            Logger.info("save sessionId " + data.sessionId);
+            Logger.info("save version " + data.version);
+            Logger.info("save deviceId " + data.deviceId);
+        });
+  ```
+
+  
+
+- The target device obtains the session ID from **onCreate()**, creates a distributed object, and associates the distributed object with the session ID. In this way, the distributed object can be synchronized. Before calling **restoreWindowStage**, ensure that all distributed objects required for continuation have been associated.
+
+  ```javascript
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  import distributedObject from '@ohos.data.distributedDataObject';
+  
+  var g_object = distributedObject.createDistributedObject({data:undefined});
+  
+  export default class EntryAbility extends UIAbility {
+      storage : LocalStorag;
+  
+      onCreate(want, launchParam) {
+          Logger.info(`EntryAbility onCreate ${AbilityConstant.LaunchReason.CONTINUATION}`)
+          if (launchParam.launchReason == AbilityConstant.LaunchReason.CONTINUATION) {
+              // Obtain the session ID of the distributed data object from the want parameter.
+              this.sessionId = want.parameters.session
+              Logger.info(`onCreate for continuation sessionId:  ${this.sessionId}`)
+  
+              // Before fetching data from the remote device, reset g_object.data to undefined.
+              g_object.data = undefined;
+              // Set the session ID, so the target will fetch data from the remote device.
+              g_object.setSessionId(this.sessionId);
+  
+              AppStorage.SetOrCreate<string>('ContinueStudy', g_object.data)
+              this.storage = new LocalStorage();
+              this.context.restoreWindowStage(this.storage);
+          }
+  
+      }
+  }
+  ```
+  
+   
+  
+### More Information
+
+1. Timeout
+
+   - If the application to be continued is not installed on the target device, the system checks whether the application can be installed on it and waits for a response for 4 seconds. If no response is received within 4 seconds, the caller receives a timeout error code, which means that the application cannot be installed on the target device. If the application can be installed, the system prompts the consumer to install the application on the target device. The consumer can initiate the continuation again after the installation.
+   -  If the application to be continued has been installed on the target device, the system waits for a response to the continuation request for 20 seconds. If no response is received within 20 seconds, the caller receives a timeout error code, which means that the continuation fails.
+
+2. By default, the system supports page stack information migration, which means that the page stack of the initiator will be automatically migrated to the target device. No adaptation is required.
+
+
+
+### Restrictions
+
+1.   The continuation must be performed between the same ability, which means the same bundle name, module name, and ability name. For details, see [Application Package Structure Configuration File](../quick-start/module-configuration-file.md).
+2.    Currently, the application can only implement the continuation capability. The continuation action must be initiated by the system.
+
+
+
+### Best Practice
+
+For better user experience, you are advised to use the **wantParam** parameter to transmit data smaller than 100 KB and use distributed objects to transmit data larger than 100 KB.

en/application-dev/ability-deprecated/stage-ability.md

+# Ability Development
+## When to Use
+Ability development in the [stage model](stage-brief.md) is significantly different from that in the FA model. The stage model requires you to declare the application package structure in the **module.json5** and **app.json5** files during application development. For details about the configuration file, see [Application Package Structure Configuration File](../quick-start/application-package-structure-stage.md). To develop an ability based on the stage model, implement the following logic:
+- Create an ability that supports screen viewing and human-machine interaction. You must implement the following scenarios: ability lifecycle callbacks, obtaining ability configuration, requesting permissions, and notifying environment changes.
+- Start an ability. You need to implement ability startup on the same device, on a remote device, or with a specified UI page.
+- Call abilities. For details, see [Call Development](stage-call.md).
+- Connect to and disconnect from a Service Extension ability. For details, see [Service Extension Ability Development](stage-serviceextension.md).
+- Continue the ability on another device. For details, see [Ability Continuation Development](stage-ability-continuation.md).
+
+### Launch Type
+An ability can be launched in the **standard**, **singleton**, or **specified** mode, as configured by **launchType** in the **module.json5** file. Depending on the launch type, the action performed when the ability is started differs, as described below.
+
+| Launch Type    | Description    |Action            |
+| ----------- | -------  |---------------- |
+| standard    | Standard mode  | A new instance is started each time an ability starts.|
+| singleton   | Singleton mode  | The ability has only one instance in the system. If an instance already exists when an ability is started, that instance is reused.|
+| specified   | Instance-specific| The internal service of an ability determines whether to create multiple instances during running.|
+
+By default, the singleton mode is used. The following is an example of the **module.json5** file:
+```json
+{
+  "module": {
+    "abilities": [
+      {
+        "launchType": "singleton",
+      }
+    ]
+  }
+}
+```
+## Creating an Ability
+### Available APIs
+The table below describes the APIs provided by the **AbilityStage** class, which has the **context** attribute. For details about the APIs, see [AbilityStage](../reference/apis/js-apis-app-ability-abilityStage.md).
+
+**Table 1** AbilityStage APIs
+|API|Description|
+|:------|:------|
+|onCreate(): void|Called when an ability stage is created.|
+|onAcceptWant(want: Want): string|Called when a specified ability is started.|
+|onConfigurationUpdated(config: Configuration): void|Called when the global configuration is updated.|
+
+The table below describes the APIs provided by the **Ability** class. For details about the APIs, see [Ability](../reference/apis/js-apis-application-ability.md).
+
+**Table 2** Ability APIs
+
+|API|Description|
+|:------|:------|
+|onCreate(want: Want, param: AbilityConstant.LaunchParam): void|Called when an ability is created.|
+|onDestroy(): void|Called when the ability is destroyed.|
+|onWindowStageCreate(windowStage: window.WindowStage): void|Called when a **WindowStage** is created for the ability. You can use the **window.WindowStage** APIs to implement operations such as page loading.|
+|onWindowStageDestroy(): void|Called when the **WindowStage** is destroyed for the ability.|
+|onForeground(): void|Called when the ability is switched to the foreground.|
+|onBackground(): void|Called when the ability is switched to the background.|
+|onNewWant(want: Want, launchParams: AbilityConstant.LaunchParam): void|Called when the ability launch type is set to **singleton**.|
+|onConfigurationUpdated(config: Configuration): void|Called when the configuration of the environment where the ability is running is updated.|
+### Implementing AbilityStage and Ability Lifecycle Callbacks
+To create Page abilities for an application in the stage model, you must implement the **AbilityStage** class and ability lifecycle callbacks, and use the **Window** class to set the pages. The sample code is as follows:
+1. Import the **AbilityStage** module.
+   ```ts
+   import AbilityStage from "@ohos.app.ability.AbilityStage";
+   ```
+2. Implement the **AbilityStage** class. The default relative path generated by the APIs is **entry\src\main\ets\Application\AbilityStage.ts**.
+   ```ts
+   export default class MyAbilityStage extends AbilityStage {
+    onCreate() {
+        console.log("MyAbilityStage onCreate")
+    }
+   }
+   ```
+3. Import the **Ability** module.
+   ```js
+   import UIAbility from '@ohos.app.ability.UIAbility';
+   ```
+4. Implement the lifecycle callbacks of the **UIAbility** class. The default relative path generated by the APIs is **entry\src\main\ets\entryability\EntryAbility.ts**.
+
+   In the **onWindowStageCreate(windowStage)** API, use **loadContent** to set the application page to be loaded. For details about how to use the **Window** APIs, see [Window Development](../windowmanager/application-window-stage.md).
+   ```ts
+   export default class EntryAbility extends UIAbility {
+    onCreate(want, launchParam) {
+        console.log("EntryAbility onCreate")
+    }
+   
+    onDestroy() {
+        console.log("EntryAbility onDestroy")
+    }
+   
+    onWindowStageCreate(windowStage) {
+        console.log("EntryAbility onWindowStageCreate")
+   
+        windowStage.loadContent("pages/index").then(() => {
+            console.log("EntryAbility load content succeed")
+        }).catch((error) => {
+            console.error("EntryAbility load content failed with error: " + JSON.stringify(error))
+        })
+    }
+   
+    onWindowStageDestroy() {
+        console.log("EntryAbility onWindowStageDestroy")
+    }
+   
+    onForeground() {
+        console.log("EntryAbility onForeground")
+    }
+   
+    onBackground() {
+        console.log("EntryAbility onBackground")
+    }
+   }
+   ```
+### Obtaining AbilityStage and Ability Configurations
+Both the **AbilityStage** and **Ability** classes have the **context** attribute. An application can obtain the context of an **Ability** instance through **this.context** to obtain the configuration details.
+
+The following example shows how an application obtains the bundle code directory, HAP file name, ability name, and system language through the **context** attribute in the **AbilityStage** class. The sample code is as follows:
+
+```ts
+import AbilityStage from "@ohos.app.ability.AbilityStage";
+
+export default class MyAbilityStage extends AbilityStage {
+    onCreate() {
+        console.log("MyAbilityStage onCreate")
+        let context = this.context
+        console.log("MyAbilityStage bundleCodeDir" + context.bundleCodeDir)
+
+        let currentHapModuleInfo = context.currentHapModuleInfo
+        console.log("MyAbilityStage hap module name" + currentHapModuleInfo.name)
+        console.log("MyAbilityStage hap module mainAbilityName" + currentHapModuleInfo.mainAbilityName)
+
+        let config = this.context.config
+        console.log("MyAbilityStage config language" + config.language)
+    }
+}
+```
+
+The following example shows how an application obtains the bundle code directory, HAP file name, ability name, and system language through the **context** attribute in the **Ability** class. The sample code is as follows:
+```ts
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+export default class EntryAbility extends UIAbility {
+    onCreate(want, launchParam) {
+        console.log("EntryAbility onCreate")
+        let context = this.context
+        console.log("EntryAbility bundleCodeDir" + context.bundleCodeDir)
+
+        let abilityInfo = this.context.abilityInfo;
+        console.log("EntryAbility ability bundleName" + abilityInfo.bundleName)
+        console.log("EntryAbility ability name" + abilityInfo.name)
+
+        let config = this.context.config
+        console.log("EntryAbility config language" + config.language)
+    }
+}
+```
+### Notifying of Environment Changes
+Environment changes include changes of global configurations and ability configurations. Currently, the global configurations include the system language and color mode. The change of global configurations is generally triggered by configuration items in **Settings** or icons in **Control Panel**. The ability configuration is specific to a single **Ability** instance, including the display ID, screen resolution, and screen orientation. The configuration is related to the display where the ability is located, and the change is generally triggered by the window. Before configuring a project, define the project in the [Configuration](../reference/apis/js-apis-application-configuration.md) class.
+
+For an application in the stage model, when the configuration changes, its abilities are not restarted, but the **onConfigurationUpdated(config: Configuration)** callback is triggered. If the application needs to perform processing based on the change, you can override **onConfigurationUpdated**. Note that the **Configuration** object in the callback contains all the configurations of the current ability, not only the changed configurations.
+
+The following example shows the implementation of the **onConfigurationUpdated** callback in the **AbilityStage** class. The callback is triggered when the system language and color mode are changed.  
+```ts
+import AbilityStage from '@ohos.app.ability.AbilityStage';
+import ConfigurationConstant from '@ohos.app.ability.ConfigurationConstant';
+
+export default class MyAbilityStage extends AbilityStage {
+    onConfigurationUpdated(config) {
+        if (config.colorMode === ConfigurationConstant.ColorMode.COLOR_MODE_DARK) {
+            console.log('colorMode changed to dark')
+        }
+    }
+}
+```
+
+The following example shows the implementation of the **onConfigurationUpdated** callback in the **Ability** class. The callback is triggered when the system language, color mode, or display parameters (such as the direction and density) change.  
+```ts
+import UIAbility from '@ohos.app.ability.UIAbility';
+import ConfigurationConstant from '@ohos.app.ability.ConfigurationConstant';
+
+export default class EntryAbility extends UIAbility {
+    direction : number;
+
+    onCreate(want, launchParam) {
+        this.direction = this.context.config.direction
+    }
+
+    onConfigurationUpdated(config) {
+        if (this.direction !== config.direction) {
+            console.log(`direction changed to ${config.direction}`)
+        }
+    }
+}
+```
+## Starting an Ability
+### Available APIs
+The **Ability** class has the **context** attribute, which belongs to the **AbilityContext** class. The **AbilityContext** class has the **abilityInfo**, **currentHapModuleInfo**, and other attributes as well as the APIs used for starting abilities. For details, see [AbilityContext](../reference/apis/js-apis-ability-context.md).
+
+**Table 3** AbilityContext APIs
+|API|Description|
+|:------|:------|
+|startAbility(want: Want, callback: AsyncCallback\<void>): void|Starts an ability.|
+|startAbility(want: Want, options?: StartOptions): Promise\<void>|Starts an ability.|
+|startAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback\<void>): void|Starts an ability with the account ID.|
+|startAbilityWithAccount(want: Want, accountId: number, options?: StartOptions): Promise\<void>|Starts an ability with the account ID.|
+|startAbilityForResult(want: Want, callback: AsyncCallback\<AbilityResult>): void|Starts an ability with the returned result.|
+|startAbilityForResult(want: Want, options?: StartOptions): Promise\<AbilityResult>|Starts an ability with the returned result.|
+|startAbilityForResultWithAccount(want: Want, accountId: number, callback: AsyncCallback\<AbilityResult>): void|Starts an ability with the execution result and account ID.|
+|startAbilityForResultWithAccount(want: Want, accountId: number, options?: StartOptions): Promise\<AbilityResult>|Starts an ability with the execution result and account ID.|
+### Starting an Ability on the Same Device
+An application can obtain the context of an **Ability** instance through **this.context** and then use the **startAbility** API in the **AbilityContext** class to start the ability. The ability can be started by specifying **Want**, **StartOptions**, and **accountId**, and the operation result can be returned using a callback or **Promise** instance. The sample code is as follows:
+```ts
+let context = this.context
+var want = {
+    "deviceId": "",
+    "bundleName": "com.example.MyApplication",
+    "abilityName": "EntryAbility"
+};
+context.startAbility(want).then(() => {
+    console.log("Succeed to start ability")
+}).catch((error) => {
+    console.error("Failed to start ability with error: "+ JSON.stringify(error))
+})
+```
+
+### Starting an Ability on a Remote Device
+>This feature applies only to system applications, since the **getTrustedDeviceListSync** API of the **DeviceManager** class is open only to system applications.
+In the cross-device scenario, you must specify the ID of the remote device. The sample code is as follows:
+```ts
+let context = this.context
+var want = {
+    "deviceId": getRemoteDeviceId(),
+    "bundleName": "com.example.MyApplication",
+    "abilityName": "EntryAbility"
+};
+context.startAbility(want).then(() => {
+    console.log("Succeed to start remote ability")
+}).catch((error) => {
+    console.error("Failed to start remote ability with error: " + JSON.stringify(error))
+})
+```
+Obtain the ID of a specified device from **DeviceManager**. The sample code is as follows:
+```ts
+import deviceManager from '@ohos.distributedHardware.deviceManager';
+function getRemoteDeviceId() {
+    if (typeof dmClass === 'object' && dmClass != null) {
+        var list = dmClass.getTrustedDeviceListSync();
+        if (typeof (list) == 'undefined' || typeof (list.length) == 'undefined') {
+            console.log("EntryAbility onButtonClick getRemoteDeviceId err: list is null");
+            return;
+        }
+        console.log("EntryAbility onButtonClick getRemoteDeviceId success:" + list[0].deviceId);
+        return list[0].deviceId;
+    } else {
+        console.log("EntryAbility onButtonClick getRemoteDeviceId err: dmClass is null");
+    }
+}
+```
+Request the permission **ohos.permission.DISTRIBUTED_DATASYNC** from consumers. This permission is used for data synchronization. For details about the sample code for requesting permissions, see [abilityAccessCtrl.requestPermissionsFromUse](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9).
+### Starting an Ability with the Specified Page
+If the launch type of an ability is set to **singleton** and the ability has been started, the **onNewWant** callback is triggered when the ability is started again. You can pass start options through the **want**. For example, to start an ability with the specified page, use the **uri** or **parameters** parameter in the **want** to pass the page information. Currently, the ability in the stage model cannot directly use the **router** capability. You must pass the start options to the custom component and invoke the **router** method to display the specified page during the custom component lifecycle management. The sample code is as follows:
+
+When using **startAbility** to start an ability again, use the **uri** parameter in the **want** to pass the page information.
+```ts
+async function reStartAbility() {
+  try {
+    await this.context.startAbility({
+      bundleName: "com.sample.MyApplication",
+      abilityName: "EntryAbility",
+      uri: "pages/second"
+    })
+    console.log('start ability succeed')
+  } catch (error) {
+    console.error(`start ability failed with ${error.code}`)
+  }
+}
+```
+
+Obtain the **want** parameter that contains the page information from the **onNewWant** callback of the ability.
+```ts
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+export default class EntryAbility extends UIAbility {
+  onNewWant(want, launchParams) {
+    globalThis.newWant = want
+  }
+}
+```
+
+Obtain the **want** parameter that contains the page information from the custom component and process the route based on the URI.
+```ts
+import router from '@ohos.router'
+
+@Entry
+@Component
+struct Index {
+  newWant = undefined
+
+  onPageShow() {
+    console.info('Index onPageShow')
+    let newWant = globalThis.newWant
+    if (newWant.hasOwnProperty("uri")) {
+      router.push({ url: newWant.uri });
+      globalThis.newWant = undefined
+    }
+  }
+}
+```

en/application-dev/ability/Readme-EN.md

-# Ability Development
-- [Ability Framework Overview](ability-brief.md)
-- [Context Usage](context-userguide.md)
-- FA Model
-  - [FA Model Overview](fa-brief.md)
-  - [Page Ability Development](fa-pageability.md)
-  - [Service Ability Development](fa-serviceability.md)
-  - [Data Ability Development](fa-dataability.md)
-  - [FA Widget Development](fa-formability.md)
-- Stage Model
-  - [Stage Model Overview](stage-brief.md)
-  - [Ability Development](stage-ability.md)
-  - [Service Extension Ability Development](stage-serviceextension.md)
-  - [Ability Continuation Development](stage-ability-continuation.md)
-  - [Ability Call Development](stage-call.md)
-  - [Stage Widget Development](stage-formextension.md)
-- Other
-  - [WantAgent Development](wantagent.md)
-  - [Ability Assistant Usage](ability-assistant-guidelines.md)
-  - [Test Framework Usage](ability-delegator.md)
-

en/application-dev/ability/ability-brief.md

-# Ability Framework Overview
-
-An ability is the abstraction of a functionality that an application can provide. It is the minimum unit for the system to schedule applications. An application can contain one or more `Ability` instances.
-
-The ability framework model has two forms.
-
-- FA model, which applies to application development using API version 8 and earlier versions. In the FA model, there are Feature Ability (FA) and Particle Ability (PA). The FA supports Page abilities, and the PA supports Service, Data, and Form abilities. 
-- Stage model, which is introduced since API version 9. In the stage model, there are Ability and ExtensionAbility. The ExtensionAbility is further extended to ServiceExtensionAbility, FormExtensionAbility, DataShareExtensionAbility, and more.
-
-The stage model is designed to make it easier to develop complex applications in the distributed environment. The table below lists the design differences between the two models.
-
-| Item          | FA Model                                                      | Stage Model                                               |
-| -------------- | ------------------------------------------------------------ | -------------------------------------------------------- |
-| Development mode     | Web-like APIs are provided. The UI development is the same as that of the stage model.                    | Object-oriented development mode is provided. The UI development is the same as that of the FA model.            |
-| Engine instance      | Each ability in a process exclusively uses a JS VM engine instance.              | Multiple abilities in a process share one JS VM engine instance.      |
-| Intra-process object sharing| Not supported.                                                  | Supported.                                                 |
-| Bundle description file    | The `config.json` file is used to describe the HAP and component information. Each component must use a fixed file name.| The `module.json` file is used to describe the HAP and component information. The entry file name can be specified.|
-| Component          | Four types of components are provided: Page ability (used for UI page display), Service ability (used to provide services), Data ability (used for data sharing), and Form ability (used to provide widgets).| Two types of components are provided: Ability (used for UI page display) and Extension (scenario-based service extension).  |
-
-In addition, the following differences exist in the development process:
-
-* Different ability types
-
-  ![favsstage](figures/favsstage.png)
-
-* Different ability lifecycles
-
-  ![lifecycle](figures/lifecycle.png)
-
-
-For details about the two models, see [FA Model Overview](fa-brief.md) and [Stage Model Overview](stage-brief.md).
-## Samples
-The following sample is provided to help you better understand how to develop abilities:
-- [Intra- and Inter-page Navigation](https://gitee.com/openharmony/codelabs/tree/master/Ability/PageAbility)