1# Component Startup Rules (FA Model) 2 3 4Component startup refers to the behavior of starting or connecting to an application component. 5 6 7- Start the PageAbility and ServiceAbility. For example, you can use **startAbility()**. 8 9- Connect to the ServiceAbility and DataAbility. For example, you can use **connectAbility()** and **acquireDataAbilityHelper()**. 10 11 12To deliver a better user experience, the system restricts the following behavior: 13 14 15- A background application randomly displays a dialog box, such as an ad pop-up. 16 17- Background applications wake up each other. This type of behavior occupies system resources and increases power consumption, or even causes system frozen. 18 19- A foreground application randomly redirects to another application, for example, redirecting to the payment page of another application. This type of behavior poses security risks. 20 21 22In view of this, the system formulates a set of component startup rules, as follows: 23 24 25- **Before starting a component of another application, verify the visible field of the target component.** 26 - This rule applies only to cross-application scenarios. 27 - If the **visible** field of the target component is **false**, verify the **ohos.permission.START_INVISIBLE_ABILITY** permission, which is available only for system applications. 28 - For details about the **visible** field, see [Internal Structure of the abilities Attribute](../quick-start/module-structure.md#internal-structure-of-the-abilities-attribute). 29 30- **Before starting a component of a background application, verify the BACKGROUND permission.** 31 > **NOTE** 32 > 33 > Applications developed using the SDK of API version 8 or earlier are not restricted by this restriction when starting the ServiceAbility or DataAbility. 34 35 - An application is considered as a foreground application only when the application process gains focus or its UIAbility component is running in the foreground. 36 - Verify the **ohos.permission.START_ABILITIES_FROM_BACKGROUND** permission, which is available only for system applications. 37 38- **Before starting the ServiceAbility or DataAbility component of an application, verify the AssociateWakeUp field of the target application.** 39 - This rule applies only to cross-application scenarios. 40 - This rule is valid only when the target component is ServiceAbility or DataAbility. 41 - The ServiceAbility and DataAbility of an application can be accessed by other applications only when **AssociateWakeUp** of the target application is set to **true**. 42 - The **AssociateWakeUp** field can be configured only for preset applications. For other applications, this field is set to **false** by default. 43 44 45> **NOTE** 46> 1. Component startup control has been implemented since v3.2 Release. 47> 48> 2. The new component startup rules are more strict than the original ones. Get familiar with the new startup rules to prevent service exceptions. 49 50 51 52 53## Intra-Device Component Startup Rules 54 55 The rules for starting components on the same device vary in the following scenarios: 56 57- Starting a PageAbility 58 59- Starting a ServiceAbility or DataAbility 60 61 62 63 64## Inter-Device Component Startup Rules 65 66 The rules for starting components on a different device vary in the following scenarios: 67 68- Starting a PageAbility 69 70- Starting a ServiceAbility 71 72 73
