1# Account<a name="EN-US_TOPIC_0000001078092678"></a> 2 3- [Introduction](#section11660541593) 4- [Architecture](#section1412183212132) 5- [Directory Structure](#section161941989596) 6- [Usage Guidelines](#section1312121216216) 7- [Repositories Involved](#section1371113476307) 8 9## Introduction<a name="section11660541593"></a> 10 11In a standard system, the Account subsystem supports login status management of distributed cloud accounts, interconnection with vendors' cloud account apps on the device side, and query and update of the cloud account login status. 12 13## Architecture<a name="section1412183212132"></a> 14 15**Figure 1** Account subsystem architecture<a name="fig4460722185514"></a> 16 17 18 19 20## Directory Structure<a name="section161941989596"></a> 21 22``` 23/base/account 24└── os_account # OS account module 25 ├── common # Common basic code 26 ├── interfaces # APIs exposed externally 27 ├── kits # Development framework 28 ├── sa_profile # SA profile 29 ├── services # Service code 30 └── test # Test code 31 └── resource # Test resources 32``` 33 34## Usage Guidelines<a name="section1312121216216"></a> 35 36Using the available classes for managing distributed accounts, you can query and update the account login status, including login, logout, unregistration, and token expiration. 37 38To query and update the login status of a distributed account, you must obtain the required system permission. These APIs are supported only by system apps. 39 40## Repositories Involved<a name="section1371113476307"></a> 41 42**Account subsystem** 43 44account\_os\_account 45 46
