WO2022199672A1

WO2022199672A1 - Access control method for precise permission revocation, related apparatus, and system

Info

Publication number: WO2022199672A1
Application number: PCT/CN2022/082869
Authority: WO
Inventors: 任兵飞; 毛哲文
Original assignee: 华为技术有限公司
Priority date: 2021-03-26
Filing date: 2022-03-24
Publication date: 2022-09-29
Also published as: CN115130132A

Abstract

An access control method for precise permission revocation, a related apparatus, and a system. In the method, a subject device may send an access request to an object device; a user grants permission information required by the access request, and the object device may create a first proxy and grant the permission required by the access request to the first proxy; and then the object device may respond to the access request by means of the first proxy, and may revoke the permission granted to the first proxy or terminate the first proxy to revoke the permission obtained by the object device. The present solution can ensure that the object device obtains an accurate permission and allows for precise and flexible revocation of the permission according to needs, thereby protecting data security of the object device in the process of resource invocation.

Description

Access control method, related device and system for accurately revoking authority

This application claims the priority of the Chinese patent application with the application number 202110327079.9 and the application title "Access Control Method, Relevant Device and System for Precise Revocation of Authority" filed with the China Patent Office on March 26, 2021, and, in 2022 The priority of the Chinese patent application filed with the Chinese Patent Office on March 04 with the application number of 202210211570.X and the application title of "Access Control Method, Relevant Device and System for Precise Revocation of Authority", the entire contents of which are incorporated by reference in this application middle.

technical field

The present application relates to the field of computer and communication technologies, and in particular, to an access control method, related device and system for accurately revoking authority.

Background technique

In a stand-alone scenario including a single device, various applications (application, APP) in the device can call each other, and can access various resources in the device. With the development of smart terminals, there are more and more types and quantities of devices in the user's life, and the distributed scenario where each device is interconnected is gradually being realized. In distributed scenarios, devices share resources with each other, such as shared computing power, storage resources, network resources, etc., which will become a future trend.

In order to protect user privacy, related technologies require that the called electronic device must obtain permission to access sensitive information, and can access the sensitive information only after the permission check is passed.

During the calling process, how to ensure that the called electronic device obtains accurate permissions, and can revoke the permissions as needed, so as to protect data security in the electronic device and protect user privacy, is a problem that needs to be solved urgently.

SUMMARY OF THE INVENTION

The present application provides an access control method, a related device and a system for accurately revoking authority, which can ensure that the object device obtains the accurate authority, and can accurately revoke the authority as required, so as to protect the data security in the object device.

In the first aspect, an embodiment of the present application provides an access control method for accurately revoking authority, and the method is applied to a communication system including a first device and a second device, where a callee is installed in the first device, and a callee is installed in the second device. A first caller is installed, the callee and the first caller are an application program APP or a functional component, the APP is a program entity that implements multiple functions, and the functional component is a program entity that implements a single function.

The method of the first aspect includes: the second device sends a first access request and first permission information to the first device, where the first access request is used by the first caller to invoke the callee to access the first resource in the first device, The first permission information indicates the first permission, and the first permission includes the permission to invoke the callee and/or the permission to access the first resource; the first device grants the first permission to the first agent in response to the first access request, Grant the callee the right to access the first agent, which is a service, process or thread; the first device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent ; the first device terminates the first agent, or the first device revokes the first authority possessed by the first agent.

In the method of the first aspect, the first device may be referred to as a guest device, and the second device may be referred to as a subject device.

Implementing the method provided in the first aspect, the object device accesses the first resource through the first proxy, avoiding directly granting the permission required by the access request to the callee, even if the callee passes the permission obtained by itself to other When the callee executes the above method, the permission of the secondary transfer will also be invalid, so as to achieve the purpose of accurately revoking the permission. In addition, through the first agent, the object device does not need to store a large amount of authority delegation information, which saves the storage resources of the object device.

In addition, in the method provided in the first aspect, the subject device applies to the user for the permission required for the access request, regardless of whether the object device or the callee has the authorization conditions, as long as the subject device or the caller has the authorization conditions, the object device will Ability to obtain the permissions required to access the request. This ensures that the access request initiated by the caller can be successfully responded, realizes the resource call between devices, and meets the actual needs of the user.

With reference to the first aspect, in some embodiments, the first device may revoke the permission required by the access request transmitted by the second device in any of the following cases:

1. If the first authority information also indicates the validity period of the first authority, if the validity period is valid once, the first device terminates the first agent or revokes the first authority possessed by the first agent after finishing accessing the first resource; if the validity period is If valid within the first time or within the first area, the first device terminates the first agent or revokes the first agent after the first time when the first permission information is received, or when it is located in a non-first area first authority.

2. The first device terminates the first agent or revokes the first authority possessed by the first agent after finishing accessing the first resource, or after finishing accessing the first resource for a second time.

Through the second method, the object device can revoke the permission after successfully responding to the access request, without the need to revoke the permission by passing the aging information, which avoids the situation that the permission has been invalidated before the resource call is completed, so as to realize the actual The user needs to accurately revoke the purpose of the permission.

In conjunction with the first aspect, in some embodiments, the first device may grant access to the first agent to the first instance of the callee, and run the first instance to access the first agent.

In the above embodiment, the communication system further includes a third device, where a second caller is installed in the third device, and the second caller is an APP or a functional component. The third device may send a second access request and second permission information to the first device, where the second access request is used by the second caller to call the callee to access the first resource, the second permission information indicates the second permission, the second The permission includes the permission to invoke the callee and/or the permission to access the first resource; the first device, in response to the second access request, grants the second permission to the second agent, and grants the permission to access the second agent to the callee The second instance of , the second agent is a service, process or thread; the first device runs the second instance, accesses the second agent, and accesses the first resource through the second authority possessed by the second agent; wherein the first instance, The second instance is a process or thread running in random access memory RAM, the second instance is different from the first instance, and the second instance and the first instance are isolated from each other.

Through the above embodiments, the object device provides services for multiple callers with multiple instances, and the permission obtained by the subject device can be granted to the revocation agent corresponding to the callee's instance created for the caller. In this way, it can be ensured that the authority of a caller will only be granted to the revocation agent corresponding to the instance, which can avoid the problems of authority mixing and authority expansion, thereby ensuring data security in the object device and preventing data abuse and leakage.

With reference to the first aspect, in some embodiments, before the first device grants the permission to access the first agent to the first instance of the callee, the first device may also create the first instance in response to the first access request.

With reference to the first aspect, in some embodiments, the first agent includes: a first routing agent and a first revocation agent; the first routing agent and the first revocation agent are services, processes or threads. The first device may grant the first authority to the first revocation agent, and grant the authority to access the first routing agent to the callee. In addition, the first device may run the callee, access the first revocation proxy through the first routing proxy, and access the first resource through the first authority possessed by the first revocation proxy. Furthermore, the first device may terminate the first routing agent and/or the first revocation agent, or the first device may revoke the first authority possessed by the first revocation agent.

In the previous embodiment, if the first device further includes the second agent, and the second agent includes the first routing agent and the first withdrawal agent, the first routing agent and the second routing agent may be combined into the same agent. This can reduce resource consumption in the first device.

With reference to the first aspect, in some embodiments, before granting the first authority to the first agent in response to the first access request, the first device may create the first agent in response to the first access request.

With reference to the first aspect, in some embodiments, the first permission specifically includes: the permission of the second device to invoke the callee, and/or the permission of the second device to access the first resource; and/or the permission of the first caller to invoke The rights of the callee, and/or the rights of the first caller to access the first resource.

Through the previous implementation, if the permission required by the access request includes the information of the subject device and/or the caller, the user can obtain more detailed and detailed information about the permission required by the access request received by the current object device, thereby Decide whether to grant this permission. In this way, it can be ensured that the user can perform the authorization operation after fully understanding the permissions required for the access request, which can avoid user misoperation or misauthorization, and ensure data security in the object device.

In combination with the first aspect, in some embodiments, the second device may directly send the permission information required by the first access request while sending the first access request to the first device based on a capability-based access control technology to the first device. For example, permission information required for the first access request granted by the user may be carried in the first access request. In this way, the time overhead caused by the permission synchronization in the centralized permission management mechanism can be avoided, and the efficiency of resource invocation can be improved.

With reference to the first aspect, in some embodiments, before sending the first permission information to the first device, the second device may output prompt information, where the prompt information is used to prompt the first permission; the second device may respond to the received user operation , and send the first permission information to the first device. In this way, the user can grant the first permission by entering a user action on the second device.

In combination with the previous embodiment, the operations received by the second device include one or more of the following: a user operation acting on the display screen, a preset face image, a preset fingerprint, a preset voice command, or User actions on the keys.

In the second aspect, the embodiments of the present application provide an access control method for accurately revoking permissions, the method is applied to an electronic device, where a callee is installed in the electronic device, the callee is an application program APP or a functional component, and the APP is an implementation A program entity with multiple functions, and a functional component is a program entity that implements a single function.

The method of the second aspect includes: the electronic device receives a first access request and first permission information sent by the second device, where the first access request is used by the first caller in the second device to invoke the callee to access the electronic device the first resource, the first permission information indicates the first permission, and the first permission includes the permission to call the callee, and/or the permission to access the first resource; the first caller is an APP or a functional component; the electronic device responds to For the first access request, the first authority is granted to the first agent, and the authority to access the first agent is granted to the callee, and the first agent is a service, process or thread; the electronic device runs the callee, accesses the first agent, and passes The first authority possessed by the first agent accesses the first resource; the electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent.

Implementing the method provided in the second aspect, the first device accesses the first resource through the first agent, avoiding directly granting the permission required by the access request to the callee, even if the callee passes the permission obtained by itself to the callee twice. For other callees, if the above method is executed, the permission of the secondary transfer will also be invalid, so as to achieve the purpose of accurately revoking the permission. In addition, through the first agent, the first device does not need to store a large amount of authority delegation information, which saves the storage resources of the first device.

In addition, in the method provided by the second aspect, the subject device applies to the user for the permission required for the access request, regardless of whether the object device or the callee has the authorization conditions, as long as the subject device or the caller has the authorization conditions, the object device will Ability to obtain the permissions required to access the request. This ensures that the access request initiated by the caller can be successfully responded, realizes the resource call between devices, and meets the actual needs of the user.

In the method provided in the second aspect, for various operations performed by the electronic device, reference may be made to the relevant description on the first device side in the method provided in the first aspect, and details are not repeated here.

In a third aspect, an embodiment of the present application provides an access control method for accurately revoking permissions, the method is applied to an electronic device, where a first caller and a callee are installed in the electronic device, and the first caller and the callee are Application program APP or functional component, APP is a program entity that implements multiple functions, and a functional component is a program entity that implements a single function.

The method of the third aspect includes: the electronic device generates a first access request, and obtains a first permission, where the first access request is used by the first caller to call the callee to access the first resource in the electronic device, and the first permission includes calling the authority of the callee, and/or the authority to access the first resource; the electronic device, in response to the first access request, grants the first authority to the first agent, and grants the authority to access the first agent to the callee; the electronic device runs The callee accesses the first agent and accesses the first resource through the first authority possessed by the first agent; the electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent.

By implementing the method provided by the third aspect, the electronic device can revoke the authority accurately and flexibly through the first agent.

In the first aspect or the second aspect or any one of the above embodiments, the operations performed by the first device or the second device or the third device, in the method provided in the third aspect, are all performed by the same electronic device, and , the interaction between the second device or the third device and the third device may be omitted. For details, reference may be made to the foregoing related description, which will not be repeated here.

In a fourth aspect, embodiments of the present application provide an electronic device, including: a memory and one or more processors; the memory is coupled to the one or more processors, and the memory is used to store computer program codes, and the computer program codes include computer instructions , one or more processors invoke computer instructions to cause the electronic device to perform the method of the second aspect or any one of the embodiments of the second aspect.

In a fifth aspect, an embodiment of the present application provides an electronic device, including: a memory and one or more processors; the memory is coupled to the one or more processors, and the memory is used to store computer program codes, and the computer program codes include computer instructions , one or more processors invoke computer instructions to cause the electronic device to perform the method of the third aspect or any one of the embodiments of the third aspect.

In a sixth aspect, an embodiment of the present application provides a communication system, including a first device and a second device, where the first device is configured to execute the method of the second aspect or any one of the implementation manners of the second aspect.

In a seventh aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions, when the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method of the second aspect or any one of the embodiments of the second aspect.

In an eighth aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a computer, causes the computer to execute the method of the second aspect or any one of the implementation manners of the second aspect.

In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, including instructions, when the instructions are executed on an electronic device, the electronic device causes the electronic device to perform the method of the third aspect or any one of the embodiments of the third aspect.

In a tenth aspect, an embodiment of the present application provides a computer program product, which when the computer program product runs on a computer, enables the computer to execute the third aspect or the method of any implementation manner of the third aspect.

Implementing the technical solutions provided in this application, the subject device can send an access request for invoking the callee to the object device, and transmit the permission information required by the access request granted by the user to the object device, and the object device can create the first access request. proxy, and grant the first proxy the permissions required by the access request. Afterwards, the guest device can respond to the access request through the first proxy. In addition, the object device can revoke the authority obtained by the object device by revoking the authority granted to the first agent, or terminating the first agent. This solution can ensure that the object device obtains the accurate permission, and can revoke the permission precisely and flexibly according to the needs, so as to protect the data security in the object device.

Description of drawings

FIG. 1A and FIG. 1B are schematic diagrams of a permission checking method, respectively;

FIG. 2A is a schematic structural diagram of a communication system 10 provided by an embodiment of the present application;

FIG. 2B is a distributed scenario provided by an embodiment of the present application;

3A is a hardware structure diagram of an electronic device provided by an embodiment of the present application;

3B is a software structure diagram of an electronic device provided by an embodiment of the present application;

4 is a flowchart of an access control method for accurately revoking authority provided by an embodiment of the present application;

5A-5C are a set of user interfaces implemented on the main device 200 provided by the embodiment of the present application;

5D-5F are a set of user interfaces implemented on the main device 300 provided by the embodiment of the present application;

6A is a schematic diagram of creating an agent and granting authority according to an embodiment of the present application;

6B is another schematic diagram of creating an agent and granting authority provided by an embodiment of the present application;

7A is a software structure diagram of a main device provided by an embodiment of the present application;

FIG. 7B is a software structure diagram of an object device provided by an embodiment of the present application;

FIG. 8 is a flow chart of a single electronic device implementing an access control method based on a binder according to an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be described clearly and in detail below with reference to the accompanying drawings. Wherein, in the description of the embodiments of the present application, unless otherwise specified, “/” means or, for example, A/B can mean A or B; “and/or” in the text is only a description of an associated object The association relationship indicates that there can be three kinds of relationships, for example, A and/or B can indicate that A exists alone, A and B exist at the same time, and B exists alone. In addition, in the description of the embodiments of this application , "plurality" means two or more than two.

Hereinafter, the terms "first" and "second" are only used for descriptive purposes, and should not be construed as implying or implying relative importance or implying the number of indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments of the present application, unless otherwise specified, the "multiple" The meaning is two or more.

The term "user interface (UI)" in the following embodiments of this application is a medium interface for interaction and information exchange between an application program or an operating system and a user, which realizes the internal form of information and the form acceptable to the user. conversion between. The user interface is the source code written in a specific computer language such as java and extensible markup language (XML). A commonly used form of user interface is a graphical user interface (GUI), which refers to a user interface related to computer operations that is displayed graphically. It can be text, icons, buttons, menus, tabs, text boxes, dialog boxes, status bars, navigation bars, widgets, and other visual interface elements displayed on the display screen of the electronic device.

In a distributed system including multiple electronic devices, if the electronic device being accessed does not have the authorization conditions, or the called application does not have the authorization conditions, the electronic device cannot obtain the permission to access resources granted by the user, so it cannot Implementing resource calls in stand-alone devices or between devices cannot meet the actual needs of users. The electronic device has authorization conditions means that the electronic device supports one or more authorization methods for user authorization. The authorization methods may include but are not limited to: pop-up box authorization, fingerprint verification authorization, face verification authorization, voice command authorization, button authorization, etc., which are not limited here. The fact that the application does not have authorization conditions means that the application cannot use various authorization methods provided by the electronic device. For example, when an app does not provide a user interface, the app does not support pop-up authorization.

Referring to FIG. 1A , in a stand-alone device or a distributed system including multiple electronic devices, a centralized authority management mechanism can be used, that is, an access control module (ie, authority management service) can perform resource calls on the access policy and authorization status. Same management. Specifically, when an application (eg APP1 ) calls another application (eg APP2 ), APP2 will verify through the access control module whether the APP1 has the permission required to access the corresponding resource, which will generate additional time overhead. In addition, when making resource calls across devices, the device where APP1 is located needs to send the access policy and the user's authorization status to the device where APP2 is located separately, which takes a lot of time.

Referring to FIG. 1B , the resource invocation based on the cloud service platform adopts a capability-based access control technology. Specifically, when the service caller requests to access the service provided by the cloud service platform, it directly transfers the permission required to access the service to the service entity, so as to provide the service entity with access to the corresponding resources and return the access result. In this way, the permission check can be performed directly by the service entity, and there is no need to perform additional permission verification through the access control module, which reduces the time overhead. In addition, after the service caller passes the permission to the service entity, there is a problem that it is difficult to revoke. On the one hand, when the service caller passes the authority to the service entity, it also passes the aging information. This method may cause the permission to be invalid before the resource call is completed, so the invalidation can accurately revoke the permission according to the actual needs. On the other hand, the cloud service platform needs to record a large amount of authority delegation information, which wastes storage resources. Moreover, the service entity may transfer the acquired authority twice. The cloud service platform cannot accurately revoke the authority according to the authority delegation information. revokes the permission owned by all service entities that have obtained the permission.

In order to solve the above problem, the following embodiments of the present application provide an access control method for accurately revoking authority, and the access control method can be applied to a stand-alone device or a distributed system including multiple electronic devices.

When the method is applied to a distributed system, the subject device sends an access request for invoking the callee to the object device, and transmits the permission information required by the access request granted by the user to the object device, and the object device can create a proxy module , and grant the callee the permission to access the proxy module, and grant the proxy module the permission required for the access request. The object device can create and run an instance of the callee, and respond to the access request initiated by the subject device through the proxy module. Afterwards, when the permission required by the access request needs to be revoked, the object device can revoke the permission granted to the proxy module, or can terminate the proxy module.

Through the above method, the subject device and the caller apply to the user for the permissions required by the access request. Regardless of whether the object device or the callee has the authorization conditions, as long as the subject device or the caller has the authorization conditions, the object device can obtain the access request. required permissions. This ensures that the access request initiated by the caller can be successfully responded, realizes the resource call between devices, and meets the actual needs of the user.

In addition, the object device responds to the access request by creating a proxy module, and the callee's instance and the proxy module directly perform the permission check in the process again, without the need for additional permission verification through the access control module, reducing the time overhead.

In addition, by creating a proxy module, the object device can revoke the permissions required for the access request accurately and flexibly. The object device can revoke the permission required by the access request after obtaining the access result, and does not need to revoke the permission by passing the aging information, which avoids the situation that the permission has been invalidated before the resource call is completed. Through the proxy module, the object device does not need to store a large amount of authority delegation information, and even if the object device transmits the acquired authority twice, the method provided by this embodiment of the present application can recover all the rights owned by the instance that has acquired the authority. Permission to achieve precise revocation.

In some embodiments, when the subject device sends the access request, it can use the capability-based access control technology to directly send the permission information required by the access request to the object device, avoiding the permission in the centralized permission management mechanism Time overhead caused by synchronization.

In the following embodiments of the present application, the proxy module may be an application program, a service, or an instance, a process, or a thread. A process is an execution of an application on a computer. A thread is a single sequential flow of control in the execution of an application. A process can contain multiple threads.

In some embodiments, the proxy module may specifically include a routing proxy and a revocation proxy, which is not limited in this embodiment of the present application. Specifically, the object device may grant the right to access the routing proxy to the callee, and grant the right required for the access request to the revocation proxy. The object device can create and run an instance of the callee, find the corresponding revocation proxy through the routing proxy, and respond to the access request initiated by the subject device through the revocation proxy. Afterwards, when the authority required by the access request needs to be revoked, the guest device can revoke the authority granted to the revocation agent, and can also terminate the revocation agent and/or the routing agent.

When the object device obtains multiple access requests, it can create different routing agents and revocation agents respectively, and a pair of routing agents and revocation agents are used to respond to one access request. In other embodiments, when the object device acquires multiple access requests, it can create one routing proxy and multiple revocation proxies, and the routing proxy cooperates with each revocation proxy to respond to each access request.

In some embodiments, when an object device receives access requests for invoking the same callee sent by multiple subject devices, the object device may create multiple instances of the callee, and one instance of the callee is used for Responds to an access request initiated by a caller. The object device can grant the authority obtained by the caller in the subject device to the proxy module corresponding to the instance of the callee created for the caller. In this way, the object device provides services for multiple callers in the form of multiple instances, which can ensure that the authority of one caller will only be given to the proxy module corresponding to the instance, which can avoid the problems of mixed use of authority and authority expansion, so as to ensure that the object Data security in the device to prevent data abuse and leakage.

When the access control method provided by the embodiment of the present application is applied to a stand-alone device, after the electronic device generates multiple access requests for invoking the callee in the process of running the caller, the electronic device can obtain the required access request granted by the user. permissions. Afterwards, the electronic device can create a proxy module, grant the callee the right to access the proxy module, and grant the proxy module the rights required for the access request. The electronic device can create and run an instance of the callee, and respond to the access request through the proxy module. Afterwards, when the authority required by the access request needs to be revoked, the electronic device can revoke the authority granted to the proxy module, and can also terminate the proxy module.

In a stand-alone device, the caller in the electronic device applies to the user for the permission required by the access request. Regardless of whether the callee has the authorization conditions, as long as the caller has the authorization conditions, the electronic device can obtain the required access request. permissions. Thus, it is ensured that the access request initiated by the caller can be successfully responded, and the resource call in the stand-alone device can be realized to meet the actual needs of the user.

Moreover, by creating a proxy module, the electronic device can revoke the permission required for the access request accurately and flexibly. In addition, the proxy module can directly perform permission verification without additional access control modules, which can avoid the time overhead caused by permission verification. For details, please refer to the relevant description when implementing the access control method in a distributed system.

In some embodiments, when the electronic device obtains multiple access requests for calling the same callee, it can create multiple instances of the callee, and one instance of the callee is used to respond to the access initiated by one caller ask. The electronic device may grant the authority acquired by the caller to the proxy module corresponding to the instance of the callee created for the caller. In this way, in the form of providing services for multiple callers with multiple instances, it can ensure that the authority of one caller will only be given to the proxy module corresponding to the instance, which can avoid the problems of mixed use of authority and enlargement of authority, thus ensuring that the data security to prevent data abuse and leakage.

In the following embodiments of the present application, an instance is an APP or a functional component in a running state. An instance can refer to a process or a thread.

Instances are isolated from each other. Electronic devices allocate physical addresses in random access memory (RAM) to different instances on a per-process basis. When the electronic device needs to run the instance, it will find the space corresponding to the instance in the RAM according to the virtual address, and run the instance in the space. The virtual address is mapped with the physical address assigned to the instance by the electronic device, and the mapping relationship is stored in the controller of the electronic device. That is to say, the instance uses the virtual address to find the actual storage location of the memory data. Under such a mechanism, different instances can only access the physical address corresponding to their own virtual address through their own virtual addresses, that is, they cannot access the physical space of each other in RAM, so the instances are isolated from each other.

For the definitions of the subject device, the object device, the caller, and the callee, reference may be made to the related descriptions in the following embodiments.

In the following, the communication system provided by the embodiments of the present application is first introduced.

As shown in FIG. 2A , an embodiment of the present application provides a communication system 10 . The communication system 10 includes a plurality of electronic devices. Communication system 10 may also be referred to as distributed system 10 .

The multiple electronic devices included in the distributed system 10 are all intelligent terminal devices, which may be of various types, and the specific types of the multiple electronic devices are not limited in this embodiment of the present application. For example, the plurality of electronic devices include cell phones, and may also include tablet computers, desktop computers, laptop computers, handheld computers, notebook computers, smart screens, wearable devices, augmented reality (AR) devices, virtual Virtual reality (VR) devices, artificial intelligence (AI) devices, car devices, smart headsets, game consoles, and can also include Internet of things (IOT) devices or smart home devices such as smart water heaters, smart Lighting, smart air conditioners, etc. Not limited to this, the plurality of devices in the distributed system 10 may also include non-portable terminal devices such as a laptop with a touch-sensitive surface or a touch panel, a desktop computer with a touch-sensitive surface or a touch panel, and the like Wait.

When a plurality of electronic devices in the distributed system 10 are devices deployed in a home, the distributed system 10 may also be referred to as a home distributed system.

Multiple electronic devices in the distributed system 10 can be connected by logging into the same account. For example, multiple electronic devices can log in to the same Huawei account and connect and communicate remotely through the server.

Multiple electronic devices in the distributed system 10 can also log in to different accounts, but are connected in a binding manner. After an electronic device logs in to an account, the device management application can bind and log in to other electronic devices with different accounts or not logged in, and then these electronic devices can communicate with each other through the device management application.

Multiple electronic devices in the distributed system 10 may also establish connections by scanning two-dimensional codes, touching by near field communication (NFC), searching for Bluetooth devices, etc., which is not limited here.

In general, the communication connections established between the plurality of electronic devices in the distributed system 10 may include, but are not limited to, wired connections, wireless connections such as bluetooth (BT) connections, wireless local area networks (WLANs) ) such as wireless fidelity point to point (Wi-Fi P2P) connections, near field communication (NFC) connections, infrared (IR) connections, and remote connections (such as connection) and so on.

In addition, multiple electronic devices in the distributed system may also be connected and communicate in combination with any of the foregoing manners, which is not limited in this embodiment of the present application.

Multiple electronic devices in the distributed system 10 may be configured with different software operating systems (operating systems, OS), including but not limited to

and many more. in,

For Huawei's Hongmeng system.

The multiple electronic devices may also be configured with the same software operating system, for example, they may be configured with the same software operating system.

The software systems in multiple electronic devices are

, the distributed system 10 can be regarded as a hyperterminal.

In this embodiment of the present application, each device in the distributed system 10 may install a traditional application program (application, APP), such as a camera application, a gallery application, a setting application, and the like. In subsequent embodiments, the traditional APP may be referred to as APP for short.

In addition, the distributed system 10 provided by the embodiments of the present application may install distributed applications (distributed applications). The distributed application may be a system application or a third-party application, which is not limited here. System applications refer to applications provided or developed by manufacturers of electronic equipment, and third-party applications refer to applications provided or developed by manufacturers of non-electronic equipment. The manufacturer of the electronic device may include the manufacturer, supplier, provider or operator of the electronic device, and the like. A manufacturer may refer to a manufacturer that processes and manufactures electronic equipment with self-made or purchased parts and raw materials. The supplier may refer to the manufacturer that provides the complete machine, raw material or parts of the electronic equipment. The operator may refer to a manufacturer responsible for the distribution of the electronic device.

Unlike APPs that contain multiple abilities, distributed applications support deployment in units of a single ability. A distributed application consists of one or more functional components.

A functional component is the smallest capability unit that can run independently in an electronic device, and is a concept of abstract encapsulation of a single capability. APP integrates multiple functions, and functional components take each function as a separate service-based basic capability and exist independently. That is, a functional component is a program entity that implements a single function.

Each functional component can be downloaded, installed and run independently. Multiple functional components forming the same distributed application may be deployed in the same electronic device in the distributed system 10, or may be deployed in different electronic devices.

The functional component is only a word used in this embodiment, and the meaning it represents has been recorded in this embodiment, and its name does not constitute any limitation to this embodiment. In addition, in some other embodiments of the present application, functional components may also be referred to as system components, system services, business functions, and other terms. Subsequent embodiments of the present application are collectively described as "functional components".

by

For example,

Functional components in can include the following two categories:

(1) feature ability, FA.

FA is a functional component that contains one or several sets of UI, which can provide the ability to interact with the user. For example, a navigation interface in a map application, a video call interface in an instant messaging application, etc., can be implemented as FA.

In some embodiments, the FA is developed based on the MVVM (model-view-view-model) model, which separates the view UI and business logic, and deploys the business logic code and the view UI code separately. For example, an electronic device can integrate business logic code with other APPs and install it, while view UI code can be installed on other electronic devices. The device where the view UI code is located can communicate with the device where the business logic code is located to obtain the data needed to display the UI.

FA supports the ability of page templates, such as Empty Ability, Login Ability, Setting Ability, etc. FA adopts scripting language (javascript, JS) to provide declarative development mode, adopts HTML-like and cascading style sheet (CSS) declarative programming language as the development language of page layout and page style, and supports ECMAScript standard JS Language provides page business logic.

FA has the capabilities of free installation, independent operation, cross-device UI migration, and cross-device binary migration. FA also has the characteristics of multi-terminal deployment and distributed execution.

FA can call AA or APP to realize more and more complex functions.

(2) particle ability, PA.

PA is a functional component without UI, which can provide support for FA. For example, PA can provide computing power as a background service, or provide data access capability as a data warehouse. For example, beauty functions, positioning functions, audio and video encoding and decoding functions, etc., can be encapsulated as PA.

PA also has the characteristics of multi-terminal deployment and distributed execution. PAs only have dependencies on system services and do not have dependencies on other PAs.

PA actually encapsulates the realization of remote virtualization, remote invocation, PA management, cross-platform compatibility, security, etc., and opens up cross-device service enablement and arousal to developers for other devices to invoke the computing power of this device and coordinate with other devices. The device does the computing work. PA supports Service Ability, Data Ability, etc. Service Ability is used to provide the ability to run tasks in the background. Data Ability is used to provide a unified data access abstraction to the outside world.

PA can call FA or APP to realize more and more complex functions.

It can be understood that "FA" and "PA" are only a word used in this embodiment, and in some other embodiments of this application, they may also be referred to as other nouns. For example, "PA", "FA" may also be referred to as other terms such as atomic capability (AA), atomic application, meta-capability, atomic service, characteristic capability, and the like.

Multiple functional components composing a distributed application may be developed or provided by the same developer, or may be developed or provided by multiple developers separately, which is not limited here. Different developers jointly develop functional components, which can improve the development efficiency of distributed applications.

In the embodiments of the present application, the functional components provide externally standardized interfaces for invocation. APP can call functional components. In some cases, functional components can also call other functional components or APPs. In addition, the called functional component can also continue to call another functional component or APP, so the multi-level call method can be called chain call.

After each device in the distributed system 10 establishes a communication connection, each device will synchronize the functional component information and APP information of other devices in the distributed system. Specifically, each device can synchronize the names of the functional components installed by itself and the APP to other devices, so as to subsequently call functional components such as FA and PA of other devices in the distributed system 10 . In some other embodiments, each device may also synchronize its own device identification, device type, etc. to other devices in the distributed system.

Referring to FIG. 2B, FIG. 2B exemplarily shows a possible distributed distance teaching business scenario.

As shown in FIG. 2B , the distributed system includes electronic devices such as smart phones, tablet computers, and smart screens. The various devices in the distributed system are connected to each other in pairs. Smartphones, tablets, and smart screens can be configured with different software operating systems (OS), for example, smartphones and tablets can be configured

system, smart screen can be configured

system.

"Online Classroom" is installed in the smartphone. "Online Classroom" is an application program installed in an electronic device to provide teachers and students with various functions required for remote classes, and the name of the program is not limited in this embodiment of the present application. "Online Classroom" may include the following functional components: blackboard functional components, whiteboard functional components, audio and video codec functional components, and network connection functional components. Among them, the blackboard functional components and the whiteboard functional components belong to the FA, and the audio and video codec functional components and the network connection functional components belong to the PA. The blackboard function component provides the function of teaching courses remotely. The Whiteboard feature component provides the ability to answer questions remotely. The audio and video codec function components provide video and audio codec functions.

On the teacher's side, when the teacher uses the "online classroom" on the smartphone, the blackboard functional components can be migrated or switched to the smart screen, so as to explain the course on the smart screen.

On the student side, when students use Online Classroom on their smartphones, they can migrate or switch the whiteboard functionality to a tablet to answer questions on the tablet.

Migrating or switching functional components from one device A to another device B can include the following two types: 1. UI migration. When the FA's view UI and business logic are separated, when device A can run business logic code, device B can be triggered to run the view UI code, and the user seems to have migrated functional components from device A to device B. 2, the overall migration. The overall migration means that after device B downloads and installs the functional component from device A or from the network, it runs the functional component and provides corresponding functions.

In this remote teaching business scenario, the "online classroom" is the caller, and the whiteboard functional component in the tablet computer and the blackboard functional component in the smart screen are the callee.

FIG. 2B also shows another possible distributed video call service scenario.

As shown in FIG. 2B, the smartphone may also be installed with other distributed applications, such as instant messaging applications. Instant messaging applications can provide video calls, voice calls, and other communication features. The instant messaging application may include the following functional components: video calling functional components, audio and video codec functional components, and network connection functional components.

When a user uses an instant messaging application on a smartphone, the video calling function component of the application can be migrated or switched to the smart screen, so that the camera and display screen of the smart screen can be used to make video calls.

The blackboard functional component in the above-mentioned "online classroom" and the video calling functional component in the instant messaging application may be the same functional component. That is to say, the functional component in the smart screen can be called separately by the "online classroom" and instant messaging applications installed on the smart phone.

In this video call service scenario, the instant messaging application is the caller, and the video call functional component (ie, the video call functional component) in the smart screen is the callee.

It should be noted that the service scenario shown in FIG. 2B is only used to assist in describing the technical solutions of the embodiments of the present application. In an actual business scenario, the distributed system shown in FIG. 2B may include more terminal devices, more or less functional components may be deployed in each device, and each distributed application may include more or less functional components .

Through the distributed system 10 shown in FIG. 2A and the distributed scenario shown in FIG. 2B , the software and hardware capabilities of different devices can be integrated to realize an intelligent full-scene experience.

In some embodiments, after each device in the distributed system 10 establishes a communication connection, each device will synchronize functional component information and APP information of other devices in the distributed system. Specifically, each device can synchronize the names of the functional components and APPs installed by itself to other devices, so that the APPs, functional components, etc. of other devices can be called in the distributed system 10 later.

In subsequent embodiments of the present application, the party that initiates the invocation of the functional component or the APP may be referred to as the invoker. The caller can be, for example, APP, FA or PA. The initial initiator of the entire call chain can be called the first caller. The first caller can be, for example, an APP or an FA. For example, the call chain is: APP1 calls PA1, PA1 calls PA2, PA2 calls FA1, then APP1 is the first caller. For another example, the call chain is: FA1 calls PA1, PA1 calls PA2, then FA1 is the first caller.

In the whole call chain, the middle called party and the last called party can be called the callee. The callee can be, for example, APP, FA or PA.

In some embodiments of the present application, the caller may also be referred to as a subject application, and the callee may also be referred to as an object application.

In the call chain, the caller, and the callee, can be deployed in the same electronic device or in different electronic devices.

The device where the caller is located is called the subject device, and the device where the callee is located is called the object device.

The application referred to in the following embodiments of the present application may include an APP or a functional component.

In the distributed system 10 provided by the embodiment of the present application:

After the main device generates an access request for invoking the callee in the object device, it can request the user to grant the permission required by the access request, and then send the access request and the permission information required by the access request granted by the user to the object equipment.

After receiving the access request sent by the subject device, the guest device can create a proxy module, grant the proxy module the authority required by the access request, and grant the callee the access rights to the proxy module. The object device can create and run an instance of the callee, and respond to the access request initiated by the subject device through the proxy module. Afterwards, when the permission required by the access request needs to be revoked, the object device can revoke the permission granted to the proxy module, or can terminate the proxy module.

In some embodiments, when an object device receives access requests for invoking the same callee sent by multiple subject devices, the object device may create multiple instances of the callee, and one instance of the callee is used for Responds to an access request initiated by a caller.

In some embodiments, when the subject device and the object device are the same electronic device, the electronic device can obtain the access granted by the user after generating multiple access requests for invoking the callee in the process of running the caller. Request the required permissions. Afterwards, the electronic device can create a proxy module, grant the callee the right to access the proxy module, and grant the proxy module the rights required for the access request. The electronic device can create and run an instance of the callee, and respond to the access request through the proxy module. Afterwards, when the authority required by the access request needs to be revoked, the electronic device can revoke the authority granted to the proxy module, and can also terminate the proxy module.

In some embodiments, when the subject device and the object device are the same electronic device, if the electronic device obtains multiple access requests for invoking the same callee, the electronic device may create multiple instances of the callee , an instance of a callee used to respond to an access request initiated by a caller.

For the specific implementation of the operations performed by each electronic device in the distributed system 10, reference may be made to the related descriptions of the subsequent method embodiments, which are not repeated here.

Referring to FIG. 3A , FIG. 3A is a schematic diagram of a hardware structure of an electronic device provided by an embodiment of the present application. The electronic device may be any electronic device in the distributed system 10 shown in FIG. 2A . The electronic device may be a subject device, a guest device, or a subject device and an object device at the same time.

As shown in FIG. 3A , the electronic device may include a processor 110 , an external memory interface 120 , an internal memory 121 , a universal serial bus (USB) interface 130 , a charge management module 140 , a power management module 141 , and a battery 142 , Antenna 1, Antenna 2, Mobile Communication Module 150, Wireless Communication Module 160, Audio Module 170, Speaker 170A, Receiver 170B, Microphone 170C, Headphone Interface 170D, Sensor Module 180, Key 190, Motor 191, Indicator 192, Camera 193 , a display screen 194, and a subscriber identification module (subscriber identification module, SIM) card interface 195 and the like. The sensor module 180 may include a pressure sensor 180A, a gyroscope sensor 180B, an air pressure sensor 180C, a magnetic sensor 180D, an acceleration sensor 180E, a distance sensor 180F, a proximity light sensor 180G, a fingerprint sensor 180H, a temperature sensor 180J, a touch sensor 180K, and ambient light. Sensor 180L, bone conduction sensor 180M, etc.

It can be understood that the structures illustrated in the embodiments of the present application do not constitute a specific limitation on the electronic device. In other embodiments of the present application, the electronic device may include more or less components than shown, or combine some components, or separate some components, or arrange different components. The illustrated components may be implemented in hardware, software, or a combination of software and hardware.

The processor 110 may include one or more processing units, for example, the processor 110 may include an application processor (application processor, AP), a modem processor, a graphics processor (graphics processing unit, GPU), an image signal processor (image signal processor, ISP), controller, video codec, digital signal processor (digital signal processor, DSP), baseband processor, and/or neural-network processing unit (neural-network processing unit, NPU), etc. Wherein, different processing units may be independent devices, or may be integrated in one or more processors.

The controller can generate an operation control signal according to the instruction operation code and timing signal, and complete the control of fetching and executing instructions.

A memory may also be provided in the processor 110 for storing instructions and data. In some embodiments, the memory in processor 110 is cache memory. This memory may hold instructions or data that have just been used or recycled by the processor 110 . If the processor 110 needs to use the instruction or data again, it can be called directly from the memory. Repeated accesses are avoided and the latency of the processor 110 is reduced, thereby increasing the efficiency of the system.

The wireless communication function of the electronic device can be implemented by the antenna 1, the antenna 2, the mobile communication module 150, the wireless communication module 160, the modulation and demodulation processor, the baseband processor, and the like.

Antenna 1 and Antenna 2 are used to transmit and receive electromagnetic wave signals. Each antenna in an electronic device can be used to cover a single or multiple communication frequency bands. Different antennas can also be reused to improve antenna utilization. For example, the antenna 1 can be multiplexed as a diversity antenna of the wireless local area network. In other embodiments, the antenna may be used in conjunction with a tuning switch.

The mobile communication module 150 can provide a wireless communication solution including 2G/3G/4G/5G etc. applied on the electronic device. The mobile communication module 150 may include at least one filter, switch, power amplifier, low noise amplifier (LNA) and the like. The mobile communication module 150 can receive electromagnetic waves from the antenna 1, filter and amplify the received electromagnetic waves, and transmit them to the modulation and demodulation processor for demodulation. The mobile communication module 150 can also amplify the signal modulated by the modulation and demodulation processor, and then turn it into an electromagnetic wave for radiation through the antenna 1 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the processor 110 . In some embodiments, at least part of the functional modules of the mobile communication module 150 may be provided in the same device as at least part of the modules of the processor 110 .

The modem processor may include a modulator and a demodulator. Wherein, the modulator is used to modulate the low frequency baseband signal to be sent into a medium and high frequency signal. The demodulator is used to demodulate the received electromagnetic wave signal into a low frequency baseband signal. The demodulator then transmits the demodulated low-frequency baseband signal to the baseband processor for processing. The low frequency baseband signal is processed by the baseband processor and passed to the application processor. The application processor outputs sound signals through audio devices (not limited to the speaker 170A, the receiver 170B, etc.), or displays images or videos through the display screen 194 . In some embodiments, the modem processor may be a stand-alone device. In other embodiments, the modem processor may be independent of the processor 110, and may be provided in the same device as the mobile communication module 150 or other functional modules.

The wireless communication module 160 can provide applications on electronic devices including wireless local area networks (WLAN) (such as wireless fidelity (Wi-Fi) networks), bluetooth (BT), global navigation satellite system (global navigation satellite system, GNSS), frequency modulation (frequency modulation, FM), near field communication technology (near field communication, NFC), infrared technology (infrared, IR) and other wireless communication solutions. The wireless communication module 160 may be one or more devices integrating at least one communication processing module. The wireless communication module 160 receives electromagnetic waves via the antenna 2 , demodulates and filters the electromagnetic wave signals, and sends the processed signals to the processor 110 . The wireless communication module 160 can also receive the signal to be sent from the processor 110 , perform frequency modulation on it, amplify it, and convert it into electromagnetic waves for radiation through the antenna 2 .

In some embodiments, the antenna 1 of the electronic device is coupled with the mobile communication module 150, and the antenna 2 is coupled with the wireless communication module 160, so that the electronic device can communicate with the network and other devices through wireless communication technology. The wireless communication technology may include global system for mobile communications (GSM), general packet radio service (GPRS), code division multiple access (CDMA), broadband Code Division Multiple Access (WCDMA), Time Division Code Division Multiple Access (TD-SCDMA), Long Term Evolution (LTE), BT, GNSS, WLAN, NFC , FM, and/or IR technology, etc. The GNSS may include global positioning system (global positioning system, GPS), global navigation satellite system (global navigation satellite system, GLONASS), Beidou navigation satellite system (beidou navigation satellite system, BDS), quasi-zenith satellite system (quasi -zenith satellite system, QZSS) and/or satellite based augmentation systems (SBAS).

The electronic device realizes the display function through the GPU, the display screen 194, and the application processor. The GPU is a microprocessor for image processing, and is connected to the display screen 194 and the application processor. The GPU is used to perform mathematical and geometric calculations for graphics rendering. Processor 110 may include one or more GPUs that execute program instructions to generate or alter display information.

Display screen 194 is used to display images, videos, and the like. Display screen 194 includes a display panel. The display panel can be a liquid crystal display (LCD), an organic light-emitting diode (OLED), an active-matrix organic light-emitting diode or an active-matrix organic light-emitting diode (active-matrix organic light). emitting diode, AMOLED), flexible light-emitting diode (flex light-emitting diode, FLED), Miniled, MicroLed, Micro-oLed, quantum dot light-emitting diode (quantum dot light emitting diodes, QLED) and so on. In some embodiments, the electronic device may include 1 or N display screens 194 , where N is a positive integer greater than 1.

The electronic device can realize the shooting function through the ISP, the camera 193, the video codec, the GPU, the display screen 194 and the application processor.

The ISP is used to process the data fed back by the camera 193 . For example, when taking a photo, the shutter is opened, the light is transmitted to the camera photosensitive element through the lens, the light signal is converted into an electrical signal, and the camera photosensitive element transmits the electrical signal to the ISP for processing, and converts it into an image visible to the naked eye. ISP can also perform algorithm optimization on image noise, brightness, and skin tone. ISP can also optimize the exposure, color temperature and other parameters of the shooting scene. In some embodiments, the ISP may be provided in the camera 193 .

Camera 193 is used to capture still images or video. The object is projected through the lens to generate an optical image onto the photosensitive element. The photosensitive element can be a charge coupled device (CCD) or a complementary metal-oxide-semiconductor (CMOS) phototransistor. The photosensitive element converts the optical signal into an electrical signal, and then transmits the electrical signal to the ISP to convert it into a digital image signal. The ISP outputs the digital image signal to the DSP for processing. DSP converts digital image signals into standard RGB, YUV and other formats of image signals. In some embodiments, the electronic device may include 1 or N cameras 193 , where N is a positive integer greater than 1.

A digital signal processor is used to process digital signals, in addition to processing digital image signals, it can also process other digital signals. For example, when the electronic device selects the frequency point, the digital signal processor is used to perform Fourier transform on the frequency point energy, etc.

Video codecs are used to compress or decompress digital video. An electronic device may support one or more video codecs. In this way, the electronic device can play or record videos in various encoding formats, such as: moving picture experts group (moving picture experts group, MPEG) 1, MPEG2, MPEG3, MPEG4 and so on.

The NPU is a neural-network (NN) computing processor. By drawing on the structure of biological neural networks, such as the transfer mode between neurons in the human brain, it can quickly process the input information, and can continuously learn by itself. Through the NPU, applications such as intelligent cognition of electronic devices can be realized, such as image recognition, face recognition, speech recognition, text understanding, etc.

The internal memory 121 may include one or more random access memories (RAM) and one or more non-volatile memories (NVM).

Random access memory can include static random-access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronization Dynamic random access memory (double data rate synchronous dynamic random access memory, DDR SDRAM, such as fifth-generation DDR SDRAM is generally referred to as DDR5 SDRAM), etc.; non-volatile memory can include disk storage devices, flash memory (flash memory).

The random access memory can be directly read and written by the processor 110, and can be used to store executable programs (eg, machine instructions) of an operating system or other running programs, and can also be used to store data of users and application programs.

The non-volatile memory can also store executable programs and store data of user and application programs, etc., and can be loaded into the random access memory in advance for the processor 110 to directly read and write.

The external memory interface 120 can be used to connect an external non-volatile memory to expand the storage capacity of the electronic device. The external non-volatile memory communicates with the processor 110 through the external memory interface 120 to realize the data storage function. For example, save music, video, etc. files in external non-volatile memory.

The electronic device can implement audio functions through the audio module 170, the speaker 170A, the receiver 170B, the microphone 170C, the headphone jack 170D, and the application processor. Such as music playback, recording, etc.

The audio module 170 is used for converting digital audio information into analog audio signal output, and also for converting analog audio input into digital audio signal. Audio module 170 may also be used to encode and decode audio signals. In some embodiments, the audio module 170 may be provided in the processor 110 , or some functional modules of the audio module 170 may be provided in the processor 110 .

Speaker 170A, also referred to as a "speaker", is used to convert audio electrical signals into sound signals. The electronic device can listen to music through the speaker 170A, or listen to a hands-free call.

The receiver 170B, also referred to as "earpiece", is used to convert audio electrical signals into sound signals. When the electronic device answers a call or a voice message, the voice can be received by placing the receiver 170B close to the human ear.

The microphone 170C, also called "microphone" or "microphone", is used to convert sound signals into electrical signals. When making a call or sending a voice message, the user can make a sound by approaching the microphone 170C through a human mouth, and input the sound signal into the microphone 170C. The electronic device may be provided with at least one microphone 170C. In other embodiments, the electronic device may be provided with two microphones 170C, which can implement a noise reduction function in addition to collecting sound signals. In other embodiments, the electronic device can also be provided with three, four or more microphones 170C to collect sound signals, reduce noise, identify sound sources, and implement directional recording functions.

The fingerprint sensor 180H is used to collect fingerprints. Electronic devices can use the collected fingerprint characteristics to unlock fingerprints, access application locks, take photos with fingerprints, and answer incoming calls with fingerprints.

The keys 190 include a power-on key, a volume key, and the like. Keys 190 may be mechanical keys. It can also be a touch key. The electronic device may receive key input and generate key signal input related to user settings and function control of the electronic device.

Motor 191 can generate vibrating cues.

The indicator 192 can be an indicator light, which can be used to indicate the charging state, the change of the power, and can also be used to indicate a message, a missed call, a notification, and the like.

The pressure sensor 180A is used to sense pressure signals, and can convert the pressure signals into electrical signals. In some embodiments, the pressure sensor 180A may be provided on the display screen 194 .

Touch sensor 180K, also called "touch device". The touch sensor 180K may be disposed on the display screen 194 , and the touch sensor 180K and the display screen 194 form a touch screen, also called a “touch screen”. The touch sensor 180K is used to detect a touch operation on or near it. The touch sensor can pass the detected touch operation to the application processor to determine the type of touch event. Visual output related to touch operations may be provided through display screen 194 . In other embodiments, the touch sensor 180K may also be disposed on the surface of the electronic device, which is different from the location where the display screen 194 is located.

When the electronic device shown in FIG. 3A is the main device:

The mobile communication module 150 or the wireless communication module 160 can be used to establish a communication connection with other electronic devices (eg, object devices) in the distributed system 10. For the specific manner of establishing a communication connection, reference may be made to the relevant description in FIG. 2A .

The mobile communication module 150 or the wireless communication module 160 can also be used to receive the function component information and APP information synchronized with other electronic devices after establishing a communication connection with other electronic devices.

The display screen 194, the fingerprint sensor 180H, the camera 193, the audio module 170, the button 190 and other modules can be used to provide various authorization methods, so that after the main device generates an access request for invoking the callee in the object device, request the user Grant the required permissions for this access request. The processor 110 may acquire the permission required by the access request granted by the user in response to the user operation received by the above-mentioned several modules.

The mobile communication module 150 or the wireless communication module 160 can also be used to send the access request and the permission information granted by the user to the object device.

The display screen 194 can also be used to display the user interface displayed on the main device provided by the subsequent embodiments.

The internal memory 121 may be used to store functional component information and APP information synchronized by other electronic devices in the distributed system 10 .

The internal memory 121 can also be used to store the calling relationship between the caller in the subject device and the callee in the object device. The calling relationship includes: the calling relationship ID, the information of the caller, and the information of the callee. For the specific content of the calling relationship, reference may be made to related descriptions in subsequent embodiments.

When the electronic device shown in Figure 3A is a guest device:

The mobile communication module 150 or the wireless communication module 160 can be used to establish a communication connection with other electronic devices (eg, main device) in the distributed system 10. For the specific manner of establishing a communication connection, please refer to the relevant description of FIG. 2A .

The mobile communication module 150 or the wireless communication module 160 can also be used to synchronize functional component information and APP information with other electronic devices after establishing a communication connection with other electronic devices.

The mobile communication module 150 or the wireless communication module 160 may also be configured to receive an access request sent by one or more main devices for invoking the same callee, and receive the required permissions for the access request granted by the user sent by the main device information.

The processor 110 may be configured to create multiple instances of the callee in response to received access requests sent by multiple subject devices, and one instance of the callee is used to respond to an access request initiated by a caller.

The processor 110 may be configured to create a proxy module, grant the callee the right to access the proxy module, and grant the proxy module the permission required to access the request. The processor 110 can create and run an instance of the callee, and respond to the access request initiated by the main device through the proxy module. Afterwards, when it is necessary to revoke the authority required by the access request, the processor 110 can revoke the authority granted to the proxy module, and can also terminate the proxy module.

In some embodiments, the processor 110 may create multiple instances of the callee when the object device receives access requests sent by multiple subject devices for invoking the same callee, and one instance of the callee uses In response to an access request initiated by a caller. The processor 110 may grant the authority acquired by the caller in the subject device to the callee instance created for the caller.

The display screen 194 can also be used to display the user interface displayed on the object device provided by the subsequent embodiments.

The internal memory 121 may be used to store permission information, aging information, and the like required for the access request sent by each main device.

The internal memory 121 can also be used to store the calling relationship between the callee in the object device and the caller in the main device. The invocation relationship includes: the invocation relationship ID, the instance information of the callee, and the information of each caller who invoked the instance. For the specific content of the calling relationship, reference may be made to related descriptions in subsequent embodiments.

When the electronic device shown in FIG. 3A is the main device and the object device at the same time, the operations performed by each module in the above-mentioned main device and the object device are all performed by the electronic device, and the communication steps between the main device and the object device can be omitted. . For operations performed by each module in the electronic device, reference may be made to the foregoing related descriptions, which are not repeated here.

Referring to FIG. 3B , FIG. 3B is a schematic diagram of a software structure of an electronic device provided by an embodiment of the present application. The electronic device may be any electronic device in the distributed system 10 shown in FIG. 2A . The electronic device may be a subject device, a guest device, or a subject device and an object device at the same time.

The software systems of electronic devices can all adopt a layered architecture, an event-driven architecture, a microkernel architecture, a microservice architecture, or a cloud architecture. Exemplarily, the software system of the electronic device includes but is not limited to

Linux or other operating systems.

The layered architecture divides the software into several layers, and each layer has a clear role and division of labor. Layers communicate with each other through software interfaces. In some embodiments, the Android system is divided into four layers, which are, from top to bottom, an application layer, an application framework layer, an Android runtime (Android runtime) and a system library, and a kernel layer.

The application layer can include a series of application packages.

As shown in FIG. 3B, the application package may include APP, such as camera, gallery, calendar, call, map, navigation, WLAN, Bluetooth, music, video, short message and other applications. The application layer may also include functional components such as FA, PA, and so on.

The application framework layer provides an application programming interface (application programming interface, API) and a programming framework for applications in the application layer. The application framework layer includes some predefined functions.

As shown in Figure 3B, the application framework layer may include a window manager, a content provider, a view system, a telephony manager, a resource manager, a notification manager, and the like.

A window manager is used to manage window programs. The window manager can get the size of the display screen, determine whether there is a status bar, lock the screen, take screenshots, etc.

Content providers are used to store and retrieve data and make these data accessible to applications. The data may include video, images, audio, calls made and received, browsing history and bookmarks, phone book, etc.

The view system includes visual controls, such as controls for displaying text, controls for displaying pictures, and so on. View systems can be used to build applications. A display interface can consist of one or more views. For example, the display interface including the short message notification icon may include a view for displaying text and a view for displaying pictures.

The phone manager is used to provide the communication function of the electronic device. For example, the management of call status (including connecting, hanging up, etc.).

The resource manager provides various resources for the application, such as localization strings, icons, pictures, layout files, video files and so on.

The notification manager enables applications to display notification information in the status bar, which can be used to convey notification-type messages, and can disappear automatically after a brief pause without user interaction. For example, the notification manager is used to notify download completion, message reminders, etc. The notification manager can also display notifications in the status bar at the top of the system in the form of graphs or scroll bar text, such as notifications of applications running in the background, and notifications on the screen in the form of dialog windows. For example, text information is prompted in the status bar, a prompt sound is issued, the electronic device vibrates, and the indicator light flashes.

Android Runtime includes core libraries and a virtual machine. Android runtime is responsible for scheduling and management of the Android system.

The core library consists of two parts: one is the function functions that the java language needs to call, and the other is the core library of Android.

The application layer and the application framework layer run in virtual machines. The virtual machine executes the java files of the application layer and the application framework layer as binary files. The virtual machine is used to perform functions such as object lifecycle management, stack management, thread management, safety and exception management, and garbage collection.

A system library can include multiple functional modules. For example: surface manager (surface manager), media library (Media Libraries), 3D graphics processing library (eg: OpenGL ES), 2D graphics engine (eg: SGL), etc.

The Surface Manager is used to manage the display subsystem and provides a fusion of 2D and 3D layers for multiple applications.

The media library supports playback and recording of a variety of commonly used audio and video formats, as well as still image files. The media library can support a variety of audio and video encoding formats, such as: MPEG4, H.264, MP3, AAC, AMR, JPG, PNG, etc.

The 3D graphics processing library is used to implement 3D graphics drawing, image rendering, compositing, and layer processing.

2D graphics engine is a drawing engine for 2D drawing.

The kernel layer is the layer between hardware and software. The kernel layer contains at least display drivers, camera drivers, audio drivers, and sensor drivers.

Based on the distributed system 10 shown in FIG. 2A, the hardware structure of the electronic device shown in FIG. 3A, and the software structure of the electronic device shown in FIG.

Referring to FIG. 4 , FIG. 4 is a schematic flowchart of an access control method for accurately revoking authority provided by an embodiment of the present application. The method shown in FIG. 4 is described by taking the subject device calling resources in the object device as an example.

As shown in Figure 4, the method may include the following steps:

S101, a connection is established between the object device and the main device, and the number of the main device is one or more.

The number of the object device is one, and the object device can be any electronic device in the distributed system 10 .

The number of main devices may be one or multiple. The main device can be any electronic device in the distributed system 10 .

The embodiments of the present application do not limit the manner in which the object device and the subject device establish a communication connection. For example, the communication connection can be established by logging in to the same account, binding the device, scanning a two-dimensional code, and the like. The embodiment of this application does not limit the type of communication connection established between the subject device and the object device, for example, it may include wired connection, wireless connection such as Bluetooth connection, Wi-Fi P2P connection, NFC connection, IR connection, and remote connection, etc. Wait. For details, refer to the related description in FIG. 2A .

In some embodiments, after the connection between the guest device and the host device is established, the guest device can send the information of the function components installed by itself and the APP information, such as identification and the like, to the host device. The functional components or APPs that can be called are declared or defined by the developer during the development phase. The available-for-calling here only means that the functional components or APPs can be called by the caller, not that they are open or authorized to be called by a certain device.

In some embodiments, after a connection is established between the guest device and the host device, the guest device may send capability information open to the host device to the host device, where the capability information indicates the APP and functional components that the guest device opens to the host device for invocation , resources, etc. Here, the capability information open to the main device means that the corresponding APP, functional components, and resources can be called by the main device. The capability of the object device to be opened to the main device can be preset by the object device or set by the user. For example, electronic devices can open APPs or functional components with low confidentiality or low sensitivity to other devices. For example, electronic devices can open camera applications, gallery applications, etc. to other devices, but not banking applications. equipment. The capabilities of the object device open to different subject devices may be the same or different, and there is no restriction here.

S102, the subject device generates an access request, where the access request is used by the caller in the subject device to call the callee in the object device to access the first resource.

In this embodiment of the present application, a caller is installed in the subject device, and a callee is installed in the object device. Both the caller and the callee can be an APP or a functional component. For the definitions of APP and functional components, please refer to the foregoing related descriptions.

The access request generated by the main device may include: the identifier of the caller, the identifier of the callee, and the identifier of the first resource. In some embodiments, the access request may further include: the identity of the subject device and the identity of the object device.

The identifier of the subject device or the object device may be a device type, a device model, a device name, etc., which is not limited in this embodiment of the present application. The device type here can be viewed from the function of the device, for example, it may include a mobile phone, a tablet computer, a smart headset, an IOT device, or a smart home device, and so on.

The identifier of the caller and the identifier of the callee can be the application identifier (APP ID).

In this embodiment of the present application, the first resource may be a software resource or a hardware resource. The hardware resources may include, for example, a camera, a fingerprint sensor, an audio device, a display screen, a motor, a flash, and the like provided by the device. The software resources may include, for example, memory resources, computing capabilities (such as beauty algorithm capabilities, audio and video encoding and decoding capabilities), network capabilities, positioning functions, and the like possessed by the device. The first resource may include one or more resources, which is not limited here.

In some cases, the identity of the callee and the identity of the first resource may be the same. For example, when the first resource is a camera, the identifier of the callee may also be the identifier of the camera, which is used to indicate that the callee is a camera application.

In this embodiment of the present application, each access request corresponds to an initiating device (ie, a main device) of the access request, a caller, a callee, and a first resource to be accessed. The callee and the first resource corresponding to different access requests are the same, and the main device and the caller corresponding to different access requests may be different.

In some embodiments, the main device may generate the access request in response to the received user operation during the process of running the caller.

Hereinafter, the subject device 200 and the subject device 300 each generate an access request for the object device 100 as an example for description. The main device 200 can be a tablet computer, the main device 300 can be a smart screen, and the object device 100 can be a smart phone.

FIG. 5A exemplarily shows the user interface 51 provided by the “Gallery” in the main device 200 . "Gallery" is a picture management application installed on the electronic device, and may also be called "album", and the name of the application is not limited in this embodiment. "Gallery" supports users to perform various operations on pictures stored on electronic devices or cloud servers, such as browsing, editing, deleting, and selecting.

As shown in FIG. 5A , the user interface 51 displays: a status bar 501 , a back key 502 , a page indicator 503 , a picture 504 , and one or more device options 505 .

The status bar 501 may include: one or more signal strength indicators of Wi-Fi signals, battery status indicators, time indicators, and the like.

The return key 502 is used to return to the previous page provided by the "Gallery".

The page indicator 503 is used to indicate that the current page is a page provided by "Gallery". The page indicator 503 may be implemented as text such as the text "Gallery", an icon or other form.

The picture 504 may be a picture stored in the main device 200 or a cloud server. The picture 504 may be captured by the main device 200, or downloaded by the main device 200 from the network, or shared from other devices.

One or more device options 505 may correspond to devices in the distributed system 10 that may provide image processing capabilities to meet the image processing needs of the main device 200, such as smartphones and the like. Device options 505 may be implemented as images, icons, text, etc., without limitation.

As shown in FIG. 5A , the main device 200 can detect the user operation acting on the device option 505 and, in response to the user operation, generate an access request, which is used for the “Gallery” application in the main device 200 to call the device Option 505 corresponds to the image processing functional component (FA) and image processing resources in the smartphone 1 (ie, the object device 100 ).

FIG. 5D exemplarily shows the user interface 52 provided by the “Gallery” in the main device 300 . As shown in FIG. 5D , displayed in the user interface 52 are: a status bar, a back key, a page indicator, a picture 508 , and one or more device options 509 .

Status bar, back key, page indicator, picture 508, one or more device options 509, can refer to the relevant description in FIG. 5A.

As shown in FIG. 5D , the main device 300 can detect the user operation acting on the device option 509, for example, the user selects the device option 509 through the remote control, and generates an access request in response to the user operation. The access request The “Gallery” application used in the main device 300 invokes the image processing functional component (FA) and image processing resources in the smartphone 1 (ie, the object device 100 ) corresponding to the device option 505 .

In other embodiments, the subject device may also autonomously generate an access request for the object device in the process of running the caller in some cases. For example, each time the subject device makes a video call, it may generate an access request for the instant messaging application in the subject device to call the video call functional component and camera resources in the smart screen (ie, the object device 100 ) by default.

In some embodiments, after generating the access request, the subject device may further query whether the object device has granted the access authority to the callee and/or the first resource in the access request to the subject device. If so, proceed to the next steps. In this way, it can be ensured that the subject device can initiate an access request within the scope of the capability of the object device to be opened to the subject device, and will not initiate an access request outside the open capability range, which can increase the probability of the access request being responded to and reduce the number of devices between devices. of ineffective communication.

In other embodiments, the main device may also directly perform subsequent steps after generating the access request.

S103, the main device requests the user to grant the authority required by the access request generated by the main device.

In some embodiments, after the main device generates the access request, S103 may be directly performed.

In other embodiments, after the main device generates the access request, it may perform S103 on the premise that the callee and/or the first resource is a sensitive resource. In this way, it can be ensured that the user's authorization can be obtained when the sensitive resources in the object device are accessed, thereby ensuring the security of the user's data. Sensitive resources may refer to resources that will pose a greater risk to user privacy after being leaked, such as resources whose privacy level is higher than a threshold. Sensitive resources may include hardware resources, software resources, and stored data in electronic devices. Hardware resources may include, for example, cameras, audio devices, display screens, and the like. The software resources may include, for example, memory resources, computing capabilities (such as beauty algorithm capabilities, audio and video codec capabilities), network capabilities, positioning functions, high-confidential APPs (such as banking APPs), and the like. Stored data may include, for example, stored user information, photos, videos, passwords that the user logs into the application, and the like.

In some other embodiments of the present application, the main device may also perform S103 first, and then perform S102, that is, the main device may first request the user to grant the permission, and then generate the access request after obtaining the permission.

When the electronic device supports one or more authorization methods for user authorization, the electronic device has authorization conditions. When the caller supports one or more authorization methods for user authorization, the caller has authorization conditions.

The authorization methods may include but are not limited to: pop-up box authorization, fingerprint verification authorization, face verification authorization, voice command authorization, button authorization, etc., which are not limited here.

Whether an electronic device has authorization conditions and the types of supported authorization methods depend on the hardware and/or software configuration of the electronic device. For example, supporting pop-up authorization requires the electronic device to configure the display. Fingerprint authentication and authorization are supported, and the electronic device needs to be equipped with a fingerprint sensor. Support face authentication authorization, which requires electronic devices to be equipped with cameras and face recognition algorithms. Supports voice command authorization, requires electronic devices to be equipped with microphones or other sound pickup devices. Button authorization is supported, and physical buttons need to be configured on the electronic device.

Whether the caller has authorization conditions depends on the function of the caller itself. For example, when the caller can provide a user interface, the caller can support pop-up authorization. For another example, when the caller can call the fingerprint sensor, the caller can support fingerprint authentication and authorization.

The permissions required for the access request generated by the subject device include: the permission to invoke the callee in the object device, and/or the permission to access the first resource in the object device.

In some embodiments, the authority required for the access request specifically includes: the authority of the subject device to invoke the callee in the object device and/or to access the first resource.

In some embodiments, the permission required by the access request specifically includes: the caller's permission to invoke the callee in the object device and/or to access the first resource.

In some embodiments, the permission required by the access request specifically includes: the caller in the subject device calls the callee in the object device and/or the permission to access the first resource.

In S103, the subject device may use an authorization method supported by both the subject device and the caller during the process of running the caller to request the user to grant the permission required by the access request generated by itself. The different authorization methods are described below.

When the main device supports pop-up authorization, prompt information can be output on the display screen, and the prompt information is used to prompt the permission required for the access request. After that, the main device can detect the user operation acting on the display screen, and in response to the user operation, obtain the permission required for the access request.

Referring to FIG. 5B , FIG. 5B exemplarily shows the displayed user interface 51 when the main device 200 uses the pop-up box authorization to request user authorization.

User interface 51 displays window 506 . The window 506 includes: prompt information 506a, controls 506b, and controls 506c. The prompt information 506a is used to prompt the user to grant the authority required by the access request generated by the main device 200 . The prompt information 506a can be, for example, the text ""Gallery" needs to access your image processing resources, after authorization, the following applications will use this permission: Image Processing Function Component (FA)", where "Gallery" indicates the caller, " The image processing functional component (FA)" indicates the callee, and the "image processing resource" indicates that the first resource is a camera resource. Combining with the device provided by the current user interface 51 and the device option 505 selected by the user in FIG. In some other embodiments, the prompt information 506a may include information of the subject device and the object device.

That is, the prompt information 506a is used to prompt the user to grant the “Gallery” application in the subject device 200 the right to call the image processing function (FA) in the smartphone 1 (ie, the object device 100 ) to access image processing resources.

Not limited to the form shown in the prompt information 506a, the specific content of the prompt information 506a depends on the authority required for the access request, which is not limited here.

The control 506b can be used to monitor the user operation, and the main device 200, in response to the user operation, learns that the permission required by the access request generated by the main device 200 cannot be obtained currently.

The control 506c can be used to monitor the user operation. In response to the user operation, the main device 200 successfully acquires the permission required by the access request generated by the main device 200, and the validity period of the permission is one time. That is, the permission required by the access request acquired by the main device 200 is valid once, and after the access request is responded, the main device 200 no longer has the permission.

The control 506d can be used to monitor the user operation, and the main device 200 successfully acquires the permission required by the access request generated by the main device 200 in response to the user operation, and the time limit of the permission is permanent. That is, the authority required for the access request acquired by the main device 200 is permanently valid.

As shown in FIG. 5B , the main device 200 receives the user operation acting on the control 506c, and obtains the permission of the “Gallery” in the main device 200 to call the image processing functional component (FA) in the object device 100 and access the image processing resources, And the time limit of this permission is valid once.

Referring to FIG. 5E , FIG. 5E exemplarily shows the displayed user interface 52 when the main device 300 uses the pop-up box authorization to request user authorization. For the window 510 included in the user interface 52, reference may be made to the window 506 in the user interface 51 shown in FIG. 5B , and details are not described here.

As shown in FIG. 5E , the main device 300 can receive a user operation acting on the control 510a. In response to the user operation, the main device 300 successfully obtains the permission required by the access request generated by the main device 300, and the validity period of the permission is for perpetual.

When the main device supports fingerprint authentication and authorization, the user's fingerprint can be collected by the fingerprint sensor, and the collected fingerprint can be compared with the preset fingerprint. If the two fingerprints are consistent, the main device has obtained the permission required for the access request. In some embodiments, the main device may preset multiple fingerprints, and when different preset fingerprints are collected, obtain permissions required for access requests with different time-limits.

When the main device supports face authentication and authorization, it can collect the user's face image through the camera, and compare the collected face image with the preset face image. If the two are consistent, the main device obtains the access request. required permissions.

When the main device supports voice command authorization, it can collect the voice command input by the user through a microphone, receiver or other sound pickup device, and compare the collected voice command with the preset voice command. The device obtains the permissions required for the access request. In some embodiments, the main device may preset multiple voice commands, and acquire permissions required for access requests with different time-limits when different preset voice commands are collected.

When the main device supports key authorization, the user's pressing operation can be collected through physical keys. If a preset pressing operation (such as one pressing operation, long pressing operation, two consecutive pressing operations, etc.) The device obtains the permissions required for the access request. In some embodiments, the main device may preset multiple pressing operations, and acquire permissions required for access requests with different time periods when different preset pressing operations are collected.

In the embodiment of the present application, when the subject device requests the user to grant the permission required by the access request generated by the subject device, if the permission required by the access request includes the information of the subject device and/or the caller, the user can learn about the current object More granular and detailed information about the permissions required by the access request received by the device to decide whether to grant the permission. In this way, it can be ensured that the user can perform the authorization operation after fully understanding the permissions required for the access request, which can avoid user misoperation or misauthorization, and ensure data security in the object device.

It can be seen that, in S103, the subject device may, in response to the received user operation, obtain the permission granted by the user required for the access request generated by the subject device, and the permission granted by the user may be time-sensitive. The time limit of the permission can include various, not limited to the one-time effective and permanent effective as shown in the above-mentioned FIG. 5B or FIG. 5E, and there may be more situations, such as effective within one week, effective within one month, within the first area Effective and so on, there is no restriction here.

In some embodiments, the main device may perform S103 after each access request is generated. In other embodiments, after generating the access request, the main device may first determine whether the main device has the permission required by the access request, and if not, apply for the permission to the user through S103, which can reduce the number of users between the main and guest devices. It can improve the efficiency of calling resources across devices in a distributed system.

Through S103, the subject device and the caller apply to the user for the permission required by the access request. Regardless of whether the object device or the callee has the authorization conditions, as long as the subject device or the caller has the authorization conditions, the object device can obtain the access request. required permissions. This ensures that the access request initiated by the caller can be successfully responded, realizes the resource call between devices, and meets the actual needs of the user.

S104, the subject device sends the generated access request and the permission information required by the access request granted by the user to the object device.

In this embodiment of the present application, the permission information indicates one or more of the following: whether the main device obtains the permission required by the access request, the permission required for the access request obtained by the main device, the permission obtained by the main device the time limit.

In some embodiments, the subject device may directly send the permission information required by the access request to the object device while sending the access request to the object device based on the capability (capability) access control technology. For example, permission information required by the access request granted by the user may be carried in the access request. In this way, the time overhead caused by the permission synchronization in the centralized permission management mechanism can be avoided, and the efficiency of resource invocation can be improved.

In some embodiments, the subject device may send the access request and the permission information required by the access request granted by the user to the guest device, respectively.

Executing the above S103-S104 can ensure that the main device initiates the access request after acquiring the permission required by the access request, which can ensure the security of the entire calling process.

In other embodiments of the present application, the subject device may first send an access request to the guest device, and after receiving the access request, the guest device may directly send an authorization to the subject device after confirming that it does not have the authority required for the access request. request, the authorization request is used to request the user to apply for the permission required by the access request. Afterwards, the subject device may perform the operation of S103 in response to the authorization request, and send the permission information required by the access request granted by the user to the object device. That is to say, the subject device can apply to the user for the permission required by the access request under the trigger of the object device, without actively applying for the permission required by the access request from the user itself.

In some embodiments, the subject device may find the object device corresponding to the access request according to the stored calling relationship, and send the access request and the acquired permission information required by the access request to the object device.

In some embodiments, after the subject device performs S104, the permission information obtained by the callee in the object device may also be recorded or stored.

In optional step S105, the object device creates multiple instances of the callee in response to the received access request.

Specifically, after receiving multiple access requests, the object device can activate different instances according to one or more of the following: the caller, the main device, the developer of the caller, the account of the user to which the caller belongs or the main device, etc. . When one or more of the above are different, the object device may enable different callee instances to provide services for the corresponding callers.

For example, if the application identified as "ID2" in the main device 200 and the application identified as "ID3" in the main device 300 call the application identified as "ID1" in the object device 100, the object device 100 can create two instances, Serves two callers separately.

For another example, the application identified as "ID3" in the main device 300 and the application identified as "ID4" in the main device 400 call the application identified as "ID1" in the object device 100 at the same time, because the developers of the two callers are the same , the object device 100 can create an instance to serve two callers at the same time.

In some embodiments, if there is an instance of the callee that provides services for the caller in the subject device in the object device, that is, the object device has created the instance before, the object device does not need to perform S105 to recreate the instance. If there is no instance of the callee serving the caller in the subject device in the guest device, the guest device performs S105 to create the instance.

Referring to the examples in FIGS. 5A and 5D above, after the object device 100 receives the access requests sent by the main device 200 and the main device 300, it will create two instances of image processing functional components (FA), which are the main device 200 and the main device 300 respectively. The main device 300 provides the service.

In some embodiments, the callee may be pre-installed in the guest device. In other embodiments, the guest device may download and install the callee from the network after receiving the access request sent by the guest device, or directly download and install the callee from the subject device.

When the object device creates an instance of the callee, it can assign a user ID (user ID, UID) and a process identifier (PID) to the instance. In some embodiments, the guest device may assign different UIDs to different instances of the callee. In some embodiments, the guest device may assign different PIDs to different instances of the callee. Therefore, the guest device can distinguish different instances of the same callee by UID or PID.

In some embodiments, after creating the instance of the callee, the object device may save the calling relationship composed of the caller and the instance of the callee. For the specific content of the calling relationship, please refer to the related description below. The object device can also synchronize part of the content of the call relationship, such as the call relationship ID, the UID and PID of the callee instance created for the caller in the main device, to the main device, so that the main device can store the call relationship. .

In some embodiments, after receiving the permission information sent by the subject device, the guest device may further record or store the permission information.

In some embodiments, the object device may query whether the permission to access the callee and/or the first resource is open to the subject device, and only execute the subsequent steps if yes. In this way, invalid communication between host and guest devices can be reduced, and the efficiency of resource invocation can be improved.

In optional step S106, the object device is an instance of the callee, and a routing proxy and a revocation proxy are created.

In this embodiment of the present application, the routing agent and the revocation agent may be an application program, a service, or an instance, a process, or a thread.

In some embodiments, the object device may correspondingly create a routing proxy and a revocation proxy for each instance of the callee, and at the same time, grant the right to access the routing proxy to the instance of the callee, and request the access The required permissions are granted to the revocation agent. For example, referring to FIG. 6A, FIG. 6A shows a situation where the object device 100 creates an instance and routes and revokes the proxy, and grants the instance and each proxy corresponding permissions. As shown in the figure, the object device 100 has created two instances of the image processing functional component (FA), and created a routing agent and a revocation agent for each of the two instances.

In other embodiments, the object device may create a corresponding revocation proxy for each instance of the callee, but the two instances share a routing proxy. That is, routing agents can be reused. In this way, the overhead in the object device can be reduced, and the efficiency of resource access can be improved. Referring to FIG. 6B, FIG. 6B shows another case where the object device 100 creates an instance, routes and revokes the proxy, and grants the instance and each proxy the corresponding authority.

In this embodiment of the present application, the routing proxy and the revocation proxy may be created by the system of the object device, or may be created by the object device through the callee, which is not limited here. Furthermore, the guest device can create the routing proxy and the revocation proxy by following the identity of the caller, for example, using the UID of the caller passed by the subject device to create the two proxies. The system of the object device creates the routing proxy and the revocation proxy, which can prevent the callee from obtaining the permission required by the access request, thereby avoiding permission expansion or permission abuse, and can further protect the data security in the electronic device.

In some embodiments, if a routing proxy and a revocation proxy corresponding to the instance of the callee exist in the guest device, the guest device does not need to perform S106 to recreate the routing proxy and the revocation proxy. If the routing proxy and the revocation proxy corresponding to the instance of the callee do not exist in the guest device, the guest device may perform S106 to create the routing proxy and the revocation proxy.

In some embodiments, routing proxies and revocation proxies corresponding to the same callee instance may be combined into one proxy.

Through S106, the object device can create multiple instances of the callee, create revocation proxies for each instance, and grant permissions required by each access request to different revocation proxies, such that a revocation proxy can only obtain one access request For the required permissions, the problems of permission mixing and permission expansion are avoided through mutually isolated revocation agents, which can ensure the data security in the object device and prevent data abuse and leakage.

S107, the object device grants the permission to access the routing proxy to the instance of the callee, and grants the permission required for the access request to the revocation proxy.

After S107 is executed, the routing proxy corresponding to the instance of the same callee can access the corresponding revocation proxy, and at the same time, the instance of the callee cannot access the revocation proxy. That is to say, the access path in this embodiment of the present application can only be the instance of the callee-routing proxy-revocation proxy-first resource.

S108, the object device runs an instance of the callee, accesses a routing proxy corresponding to the instance, finds a revocation proxy corresponding to the instance through the routing proxy, and accesses the first resource through the revocation proxy.

Specifically, since the instance of the callee has the right to access the routing proxy, the object device running the instance of the callee can access the routing proxy. After that, the object device finds the revocation proxy corresponding to the instance of the callee through the routing proxy. Since the revocation proxy has the permission required for the access request, the object device can access the first resource through the revocation proxy. When the permission required for the access request includes the permission to invoke the callee, it can be considered that the permission includes the permission to invoke the callee to perform various operations, and therefore also includes the permission to access the first resource.

It can be seen that when S108 is executed, the object device grants the callee's instance, the routing proxy, and the revocation proxy's respective permissions, and when responding to the access request, the callee's instance, routing proxy, and revocation proxy directly perform permission checks, without the need for Additional permission verification is performed through the access control module, which reduces the time overhead.

In the embodiment of the present application, different revocation agents are isolated from each other, so there is no situation in which the rights possessed by the revocation agents are mixed and the rights are enlarged.

In some embodiments, the object device responds to the access request to access the first resource, which may specifically include one or more of the following:

1. The object device runs an instance of the callee created for the caller, and accesses the first resource to perform a series of operations, such as displaying a video call interface through a display screen, capturing images through a camera, performing computing operations, image processing, and obtaining location information and many more.

2. The object device sends the access result of accessing the first resource to the main device, for example, the image captured by the camera is sent to the main device, so that the main device can send it to the other end device that has a video call with it, and for example, the calculation result, The obtained location information is sent to the main device and so on.

3. The object device receives the data sent by the main device, uses the data to access the first resource, and performs a series of operations. For example, the object device may receive an image sent by the main device and collected by the device at the other end of the video call, and display the image on the video call interface of the display screen.

Here, the operation performed by the object device to access the first resource in response to the access request may be determined by the object device by default, or determined by the user on the object device side, or determined by the access request sent by the main device side. make restrictions.

Exemplarily, referring to FIG. 5C , FIG. 5C is the user interface 51 displayed after the host device 200 receives the access result of the object device 100 accessing the first resource. The main device 200 can first send the picture 504 in FIG. 5A to the object device 100, and the picture 504 can be carried in the access request, and then the object device 100 can run the image processing function component created for the “Gallery” in the main device 200 (FA), and access the image processing resource in the object device 100 through the specific operation in S107 , and send the access result of the image processing resource processing the picture 504 to the main device 200 . As shown in FIG. 5C , the host device 200 may display a picture 506 obtained after processing by the object device 100 according to the access result in the user interface 51 . Obviously, the definition of the picture 506 is higher than that of the picture 504 in FIG. 5A . The processing of adjusting the sharpness of the picture 504 by the object device 100 may be selected by the user on the object device side on the object device, or executed by default on the object device. In some embodiments, prompt information 507 may also be displayed in the user interface 51 for prompting the resource invocation result.

Similarly, referring to FIG. 5F , FIG. 5F is the user interface 52 displayed by the host device 300 after receiving the access result of the object device 100 accessing the first resource. The host device 300 can first send the picture 508 in FIG. 5D to the object device 100, and the picture 508 can be carried in the access request, and then the object device 100 can run the image processing function component created for the “Gallery” in the host device 300 (FA), and access the image processing resource in the object device 100 through the specific operation in S107 , and send the access result of the image processing resource processing the picture 508 to the main device 300 . As shown in FIG. 5F , the host device 300 may display the picture 511 obtained by the object device 100 after processing according to the access result in the user interface 52 . Obviously, compared with the picture 508 in FIG. 5D , the image of the person in the picture 511 has undergone a slimming and shaping process. The slimming and shaping process performed by the object device 100 on the character image in the picture 508 may be selected by the user on the object device side on the object device, or executed by default on the object device. In some embodiments, prompt information 512 may also be displayed in the user interface 52 for prompting the resource invocation result.

S109, the object device revokes the permission required by the access request.

In this embodiment of the present application, the guest device may revoke the permission required by the access request transmitted by the subject device in any of the following cases:

1. If the authorization information transmitted by the subject device includes the time limit information, the object device can revoke the rights required for the access request according to the time limit indicated by the time limit information.

For example, if the aging information indicates that it is valid for one time, the object device can revoke the permission required by the access request after successfully responding to the access request, that is, after finishing accessing the first resource. For example, in the examples of FIGS. 5A-5C, after receiving the access request sent by the subject device 200, the object device 100 may immediately revoke the permission required by the access request after responding to the access request.

For another example, if the indication of the aging information is valid within the first time, the object device may revoke the permission required for the access request after receiving the first time of the aging information.

For another example, if the aging information indicates that it is valid in the first area, the object device may revoke the permission required by the access request when it is not located in the first area.

2. After successfully responding to the access request, that is, after finishing accessing the first resource, the object device can revoke the permission required by the access request according to its own permission revocation policy.

For example, the permission revocation policy in the object device may include, but is not limited to: immediately revoke the permission required for the access request, revoke the permission required for the access request after a second time after successfully responding to the access request, and the instance of the callee exceeds the preset value. When the first resource in the object device is not accessed for a long time, the permission required for the access request is revoked, or the permission required for the access request is revoked when other conditions are met, and so on.

Specifically, in this embodiment of the present application, the object device can revoke the permissions required by the access request by using any one or more of the following:

1. The guest device revokes the permissions required for the access request granted to the revocation agent.

After the guest device withdraws the permissions required for the access request granted to the revocation proxy, the revocation proxy cannot continue to access the first resource, and the instance of the callee and the routing proxy cannot access the first resource through the revocation proxy. To achieve the purpose of withdrawing permissions.

2. The guest device terminates the routing proxy and/or revokes the proxy.

Terminating the routing proxy and/or withdrawing the proxy may mean that the object device completely clears the relevant data of the routing proxy and/or the withdrawing proxy, and the routing proxy and/or the withdrawing proxy no longer exists in the object device. In this way, the instance of the subsequent callee cannot access the first resource through the routing proxy and the revocation proxy, so the purpose of reclaiming the authority can be achieved.

In this embodiment of the present application, the first resource is accessed through the routing proxy and the revocation proxy, so as to avoid directly granting the permission required by the access request to the instance of the callee, even if the instance of the callee transmits its own permission twice For other callees, after executing the above S108, the permission of the secondary transmission will also be invalid, so as to achieve the purpose of accurately revoking the permission. In addition, through the routing proxy and the revocation proxy, the object device does not need to store a large amount of authority delegation information, which saves the storage resources of the object device.

In the method shown in Figure 4, the guest device can also manage the life cycle of the callee's instance created for the caller in the subject device. In some embodiments, the object device can stop running or destroy the instance after running the instance and successfully respond to the access request, or it can stop running or destroy the instance after a preset time has elapsed, and it can also stop running or destroy the instance after the running instance has passed the When the resource in the object device is not accessed for a certain period of time, stop running or destroy the instance. Stopping the running instance means that the instance still exists in the guest device, but the instance is not running. Destroying an instance means that the object device deletes all data related to the instance, and the instance no longer exists in the object device.

In the access control method shown in Figure 4:

A guest device (eg, guest device 100 ) may be referred to as a first device, one host device (eg, host device 200 ) may be referred to as a second device, and another host device (eg, host device 300 ) may be referred to as a third device .

The caller in the second device, such as the "Gallery" in the main device 200, can be referred to as the first caller, and the caller in the third device, such as the "Gallery" in the main device 300, can be referred to as the second caller By.

The access request sent by the second device to the first device may be referred to as a first access request. The access request sent by the third device to the first device may be referred to as a second access request. The permission required by the first access request may be referred to as the first permission. The authority required by the second authority information may be referred to as the second authority.

The permission information sent by the second device to the first device may be referred to as first permission information. The permission information sent by the third device to the first device may be referred to as second permission information.

The instance of the callee executed by the first device in response to the first access request may be referred to as the first instance. The instance of the callee executed by the first device in response to the second access request may be referred to as the second instance.

The routing proxy and the revocation proxy run by the first device in response to the first access request may be referred to as the first routing proxy and the first revocation proxy, respectively. When the first routing agent and the first revocation agent are combined into one agent, the agent may be referred to as the first agent.

The routing proxy and the revocation proxy run by the first device in response to the second access request may be referred to as the second routing proxy and the second revocation proxy, respectively. When the second routing agent and the second revocation agent are combined into one agent, the agent may be referred to as the second agent.

Not limited to the distributed system exemplified above, the method shown in FIG. 4 can also be applied to a single electronic device. For example, one or more callers and callees are installed in the electronic device, and the electronic device is both a subject device and an object device. The electronic device may generate one or more access requests for invoking the same callee, where the access request is for the caller to invoke the callee to access the first resource in the electronic device. For the generation timing and manner of the access request, reference may be made to the relevant description of the main device generating the access request in S102 of FIG. 4 . After the electronic device generates the access request, S103-S109 in the method shown in FIG. 4 may be executed, the difference is that the communication process between the object device and the subject device in FIG. 4 may be omitted.

In addition, the electronic device can create a routing proxy and a revocation proxy through the caller or the system, which can prevent the callee from obtaining the permission required for the access request, thereby avoiding permission expansion or permission abuse, and protecting the data in the electronic device. Safety. And, the electronic device can create the routing proxy and the revocation proxy by using the identity of the caller, for example, can use the UID of the caller to create the two proxies.

For how a single electronic device executes the access control method provided by the embodiment of the present application, reference may be made to the related description in FIG. 4 , and details are not repeated here.

Referring to FIG. 8 , FIG. 8 exemplarily shows a simple process for a single electronic device to implement the access control method provided by the embodiment of the present application based on the binder. As shown in FIG. 8 , the electronic device includes a user space and a kernel space, the user space includes a caller (for example, APP1 ) and a callee (for example, APP2 ), and the kernel space includes a binder driver.

As shown in Figure 8, the process may include the following steps:

1. APP1 informs the system to create or APP1 creates and revokes the routing proxy, and stipulates that the routing proxy can only be accessed through the P2 authority.

2. APP1 requests to call APP2.

3. The binder driver passes the P2 authority to the routing agent by processing the command, and passes the P1 authority to the revocation agent. The P1 permission is the permission required when APP1 requests to call APP2, and the permission is used to access the first resource.

4. APP2 responds to the request of APP1 and initiates a request for calling the first resource.

5. The system (such as the application scheduling management module) starts the routing agent according to the request of APP2. Because APP2 already has P2 permissions, it can start the routing agent.

6. The routing proxy directly forwards the request initiated by APP2 to the revocation proxy.

7. The revocation agent calls the first resource. Since the revocation agent already has the P1 authority, the first resource can be called.

After finishing calling the first resource, APP1 can request the system to delete or APP1 delete the revocation proxy and/or routing proxy, or can withdraw the P1 permission of the revocation proxy through the binder driver, and the permission can be revoked.

In a distributed system, permissions can also be granted and revoked based on binders in a manner similar to that in FIG. 8 , and the detailed implementation will not be repeated here.

In a stand-alone device, the electronic device can revoke the permissions required for the access request accurately and flexibly through the routing proxy and the revocation proxy. For details, please refer to the relevant description when implementing the access control method in a distributed system.

When the access control method for precise revocation of permissions provided by the embodiments of the present application is executed in a stand-alone device, one caller in the electronic device may be called the first caller, and the other caller may be called the second caller. The access request for invoking the callee and accessing the first resource, which is generated when the electronic device runs the first caller, may be referred to as the first access request. The access request for invoking the callee and accessing the first resource, which is generated when the electronic device runs the second caller, may be referred to as a second access request. The permission required by the first access request may be referred to as the first permission. The authority required by the second authority information may be referred to as the second authority.

The instance of the callee executed by the electronic device in response to the first access request may be referred to as the first instance. The instance of the callee executed by the third device in response to the second access request may be referred to as the second instance.

The routing proxy and the revocation proxy run by the electronic device in response to the first access request may be referred to as the first routing proxy and the first revocation proxy, respectively. When the first routing agent and the first revocation agent are combined into one agent, the agent may be referred to as the first agent.

The routing proxy and the revocation proxy executed by the electronic device in response to the second access request may be referred to as the second routing proxy and the second revocation proxy, respectively. When the second routing agent and the second revocation agent are combined into one agent, the agent may be referred to as the second agent.

Referring to FIG. 7A , FIG. 7A is a schematic diagram of a software structure of a main device provided by an embodiment of the present application. The main device may be the main device 200 or the main device 300 in the embodiment of FIG. 4 .

As shown in FIG. 7A , the main device may include the following modules: an application information management module, a permission application module, a permission delegation module, a call relationship management module, and a call relationship library. in:

The application information management module is used to manage the information of each APP and functional components installed in the main device, such as names and so on. The application information management module is also used to synchronize the information of the APP and functional components of the local machine to other devices, and simultaneously receive the information of the APP and functional components synchronized by other devices (eg, object devices).

The permission application module is used to apply to the user for the permission required for the access request when the subject device generates an access request for invoking the callee in the object device.

The authority delegation module is used to send the authority information applied by the authority application module to the object device according to the calling relationship. In some embodiments, the permission delegation module is configured to send the permission information applied for by the permission application module and the access request generated by the subject device to the object device at the same time.

The calling relationship management module is responsible for maintaining the calling relationship composed of the caller and the callee instance that provides services for the caller, and stores it in the calling relationship library.

The call relationship library is used to store the call relationship composed of the caller and the callee instance. The invocation relationship includes: the invocation relationship ID, the instance information of the callee, and the information of each caller who invoked the instance.

The call relationship ID can be assigned by the subject device. For the same invocation relationship, the object device and the main device can share the same invocation relationship ID, and the invocation relationship ID can be carried in the access request sent to the object device, which is allocated by the main device and sent to the object device.

The instance information of the callee may include one or more of the following: the device ID (device ID) of the object device, the APP ID of the callee, the UID and PID of the instance. The PID is the identity identifier of the instance, and when the electronic device runs an instance, a unique PID is assigned to the instance. PID and UID can be synchronized from the guest device to the host device.

The caller information includes the caller's application ID (APP ID), and may also include one or more of the following: the device ID of the main device (device ID), the caller's developer signature, the caller's user ID (user ID, UID), the account (account ID) of the subject device. in:

APP ID, used to identify the APP or functional component.

device ID, used to identify the device. The device ID may be, for example, the name of the device, a serial number, a media access control (media access control, MAC) address, and the like.

Developer signature, used to identify the developer.

UID, used to identify the user to which the APP or functional component belongs. Usually, the electronic device will assign different UIDs to different installed apps or functional components to distinguish them. In some embodiments, the electronic device may assign the same UID to each APP or functional component developed by the same developer. The same APP or functional component may have different UIDs in different electronic devices.

account ID, used to identify the user currently logged in to the electronic device, for example, a Huawei account.

FIG. 7A is only a schematic example, and the main device provided in this embodiment of the present application may further include more or less modules, which is not limited here.

Each module in the main device mentioned in FIG. 7A may be located in the application layer, application framework layer, system service layer, kernel layer, etc. in the electronic device shown in FIG. 3B , which is not limited here.

Referring to FIG. 7B , FIG. 7B is a schematic diagram of a software structure of a guest device provided by an embodiment of the present application. The guest device may be the guest device 100 in the embodiment of FIG. 4 .

As shown in FIG. 7B, the object device may include the following modules: application information management module, instance management module, authority delegation module, routing proxy management module, revocation proxy management module, delegation revocation management module, invocation relationship management module, invocation relationship management module library. in:

The application information management module is used to manage the information of each APP and functional component installed in the object device, such as the name and so on. The application information management module is also used for synchronizing the information of the APP and functional components of the machine to other devices, and at the same time receiving the information of the APP and functional components synchronized by other devices (such as the main device).

The instance management module is responsible for dynamically enabling the instance of the callee according to the information of the caller and providing services for the caller. Specifically, the instance management module can enable different callee instances for different callers. The instance management module is also used to manage the life cycle of each instance, such as starting, stopping, destroying, restarting, and so on.

The authorization delegation module is used to receive the authorization information required by the access request sent by the main device. And grant the permission to access the proxy module to the callee, and grant the permission required for the access request to the proxy module. The proxy module may include revocation proxies and routing proxies.

The routing agent management module is used to create routing agents. In some embodiments, the routing proxy management module may create different routing proxies in response to different access requests. In other embodiments, the routing proxy management module may create a routing proxy for responding to all access requests obtained by the object device.

The revocation proxy management module is used to create revocation proxies. In some embodiments, the revocation proxy management module may create different revocation proxies in response to different access requests.

The delegated revocation management module is used for revoking the authority granted to the revocation agent, or terminating the revocation agent and/or the routing agent, when the object device needs it.

The call relationship library is used to store the call relationship composed of the caller and the callee instance. The invocation relationship includes: the invocation relationship ID, the instance information of the callee, and the information of each caller who invoked the instance. For the specific content of the calling relationship, reference may be made to the relevant description of the main device in FIG. 7A .

FIG. 7B is only a schematic example, and the object device provided in this embodiment of the present application may further include more or less modules, which is not limited here.

Each module in the object device mentioned in FIG. 7B may be located in the application layer, application framework layer, system service layer, kernel layer, etc. in the electronic device shown in FIG. 3B , which is not limited here.

The various embodiments of the present application can be arbitrarily combined to achieve different technical effects.

In the above-mentioned embodiments, it may be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented in software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. The computer program instructions, when loaded and executed on a computer, result in whole or in part of the processes or functions described herein. The computer may be a general purpose computer, special purpose computer, computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions may be downloaded from a website site, computer, server or data center Transmission to another website site, computer, server, or data center by wire (eg, coaxial cable, optical fiber, digital subscriber line) or wireless (eg, infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available media integrations. The usable media may be magnetic media (eg, floppy disks, hard disks, magnetic tapes), optical media (eg, DVDs), or semiconductor media (eg, solid state disks (SSDs)), and the like.

Those of ordinary skill in the art can understand that all or part of the processes in the methods of the above embodiments can be implemented. The process can be completed by instructing the relevant hardware by a computer program, and the program can be stored in a computer-readable storage medium. When the program is executed , which may include the processes of the foregoing method embodiments. The aforementioned storage medium includes: ROM or random storage memory RAM, magnetic disk or optical disk and other mediums that can store program codes.

In a word, the above descriptions are merely examples of the technical solutions of the present application, and are not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made according to the disclosure of this application shall be included within the protection scope of this application.

Claims

An access control method for accurately revoking authority, characterized in that the method is applied to a communication system including a first device and a second device, the first device is installed with a callee, and the second device is installed There is a first caller, the callee and the first caller are an application program APP or a functional component, the APP is a program entity that implements multiple functions, and the functional component is a program entity that implements a single function;

The method includes:

The second device sends a first access request and first permission information to the first device, where the first access request is used by the first caller to call the callee to access the first device the first resource, the first permission information indicates the first permission, and the first permission includes the permission to invoke the callee, and/or the permission to access the first resource;

In response to the first access request, the first device grants the first authority to a first agent, and grants the authority to access the first agent to the callee, where the first agent is a service, a process or thread;

The first device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent;

The first device terminates the first agent, or the first device revokes the first authority possessed by the first agent.
The method according to claim 1, wherein the first permission information further indicates the time limit of the first permission, and the time limit is any one of the following: valid once, valid within a first time, or valid within a first time valid in one area;

The first device terminates the first agent, or the first device revokes the first authority possessed by the first agent, specifically including:

If the time limit is valid for one time, after the first device finishes accessing the first resource, the first device terminates the first agent or revokes the first authority possessed by the first agent;

If the time limit is valid within the first time or within the first area, the first device may, after receiving the first time of the first permission information, or at the When it is not in the first area, the first agent is terminated or the first authority possessed by the first agent is revoked.
The method according to claim 1, wherein the first device terminates the first agent, or the first device revokes the first authority possessed by the first agent, specifically comprising:

After the first device finishes accessing the first resource, or after finishing accessing the first resource for a second time, the first device terminates the first agent or revokes the first agent provided by the first agent. permissions.
The method according to any one of claims 1-3, wherein,

The first device granting the permission to access the first agent to the callee specifically includes: the first device granting the permission to access the first agent to the first instance of the callee;

The first device running the callee and accessing the first agent specifically includes: the first device running the first instance and accessing the first agent;

The communication system further includes a third device, and a second caller is installed in the third device, and the second caller is the APP or the functional component; the method further includes:

the third device sends a second access request and second permission information to the first device, where the second access request is used by the second caller to call the callee to access the first resource, The second permission information indicates a second permission, and the second permission includes the permission to invoke the callee, and/or the permission to access the first resource;

the first device, in response to the second access request, grants the second permission to a second proxy, grants access to the second proxy to a second instance of the callee, the second proxy for a service, process or thread;

The first device runs the second instance, accesses the second agent, and accesses the first resource through the second authority possessed by the second agent;

Wherein, the first instance and the second instance are processes or threads running in random access memory RAM, the second instance is different from the first instance, the second instance and the first instance isolated from each other.
The method of claim 4, wherein before the first device grants the first instance of the callee access to the first agent, the method further comprises:

The first device creates the first instance in response to the first access request.
The method according to any one of claims 1-5, wherein the first agent comprises: a first routing agent and a first withdrawing agent; the first routing agent and the first withdrawing agent are services , process or thread;

The first device grants the first permission to the first agent, and grants the permission to access the first agent to the callee, which specifically includes: the first device grants the first permission to the first agent. a revocation proxy, granting the callee access to the first routing proxy;

The first device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent, specifically including: the first device running The callee accesses the first revocation proxy through the first routing proxy, and accesses the first resource through the first authority possessed by the first revocation proxy;

The first device terminates the first proxy, or the first device revokes the first authority possessed by the first proxy, which specifically includes: the first device terminates the first routing proxy and/or Or the first revocation agent, or the first device revokes the first authority possessed by the first revocation agent.
The method according to any one of claims 1-6, wherein before the first device grants the first permission to the first agent in response to the first access request, the method further comprises:

The first device creates the first proxy in response to the first access request.
The method according to any one of claims 1-7, wherein the first authority specifically includes:

the permission of the second device to invoke the callee, and/or the permission of the second device to access the first resource;

and / or,

The right of the first caller to invoke the callee, and/or the right of the first caller to access the first resource.
The method according to any one of claims 1-8, wherein the sending, by the second device, the first access request and the first permission information to the first device specifically includes:

The second device sends a first access request to the first device, where the first access request carries first permission information.
The method according to any one of claims 1-9, wherein before the second device sends the first permission information to the first device, the method further comprises:

the second device outputs prompt information, where the prompt information is used to prompt the first permission;

The second device receives a user operation.
An access control method for accurately revoking permissions, characterized in that the method is applied to an electronic device, and a callee is installed in the electronic device, and the callee is an application program APP or a functional component, and the APP is A program entity that realizes multiple functions, and the functional component is a program entity that realizes a single function;

The method includes:

The electronic device receives a first access request and first permission information sent by the second device, where the first access request is used by a first caller in the second device to call the callee to access The first resource in the electronic device, the first permission information indicates a first permission, and the first permission includes the permission to invoke the callee, and/or the permission to access the first resource; the The first caller is the APP or the functional component;

The electronic device, in response to the first access request, grants the first authority to a first agent, and grants the callee the authority to access the first agent, where the first agent is a service, a process or thread;

The electronic device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent;

The electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent.
The method according to claim 11, wherein the first permission information further indicates the time limit of the first permission, and the time limit is any one of the following: valid once, valid within a first time, or valid within a first time valid in one area;

The electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent, specifically including:

If the time limit is valid for one time, the electronic device terminates the first agent or revokes the first authority possessed by the first agent after the electronic device finishes accessing the first resource;

If the time limit is valid within the first time or within the first area, the electronic device may, after receiving the first time of the first permission information, or at a non- In the first area, the first agent is terminated or the first authority possessed by the first agent is revoked.
The method according to claim 11, wherein the electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent, specifically comprising:

The electronic device terminates the first agent or revokes the first authority possessed by the first agent after ending access to the first resource, or after finishing accessing the first resource for a second time. .
The method according to any one of claims 11-13, wherein,

The electronic device granting the right to access the first agent to the callee specifically includes: the electronic device granting the right to access the first agent to the first instance of the callee;

The electronic device running the callee and accessing the first agent specifically includes: the electronic device running the first instance and accessing the first agent;

The method also includes:

The electronic device receives a second access request and second permission information sent by a third device, where the second access request is used by a second caller in the third device to call the callee to access the The first resource, the second permission information indicates a second permission, and the second permission includes the permission to call the callee, and/or the permission to access the first resource; the second caller is the APP or the functional component;

The electronic device, in response to the second access request, grants the second authority to a second agent, and grants the authority to access the second agent to a second instance of the callee, where the second agent is services, processes or threads;

The electronic device runs the second instance, accesses the second agent, and accesses the first resource through the second authority possessed by the second agent;

Wherein, the first instance and the second instance are processes or threads running in random access memory RAM, the second instance is different from the first instance, the second instance and the first instance isolated from each other.
The method of claim 14, wherein before the electronic device grants the first instance of the callee access to the first agent, the method further comprises:

The electronic device creates the first instance in response to the first access request.
The method according to any one of claims 11-15, wherein the first agent comprises: a first routing agent and a first withdrawal agent; the first routing agent and the first withdrawal agent are services , process or thread;

The electronic device grants the first authority to the first agent, and grants the callee the authority to access the first agent, specifically including: the electronic device grants the first authority to the first revocation an agent, granting the callee the right to access the first routing agent;

The electronic device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent, specifically including: the electronic device running the The callee accesses the first revocation proxy through the first routing proxy, and accesses the first resource through the first authority possessed by the first revocation proxy;

The electronic device terminates the first proxy, or the electronic device revokes the first authority possessed by the first proxy, specifically including: the electronic device terminates the first routing proxy and/or the electronic device The first revocation agent, or the electronic device revokes the first authority possessed by the first revocation agent.
The method according to any one of claims 11-16, wherein before the electronic device grants the first authority to the first agent in response to the first access request, the method further comprises:

The electronic device creates the first proxy in response to the first access request.
The method according to any one of claims 11-17, wherein the first authority specifically includes:

the permission of the second device to invoke the callee, and/or the permission of the second device to access the first resource;

and / or,

The right of the first caller to invoke the callee, and/or the right of the first caller to access the first resource.
The method according to any one of claims 11-18, wherein the electronic device receives the first access request and the first permission information sent by the second device, and specifically includes:

The electronic device receives a first access request sent by the second device, where the first access request carries first permission information.
An access control method for accurately revoking authority, characterized in that the method is applied to an electronic device, wherein a first caller and a callee are installed in the electronic device, and the first caller and the callee are installed in the electronic device. is an application program APP or a functional component, the APP is a program entity that implements multiple functions, and the functional component is a program entity that implements a single function; the method includes:

The electronic device generates a first access request and acquires a first permission, the first access request is used by the first caller to call the callee to access the first resource in the electronic device, the The first permission includes the permission to invoke the callee, and/or the permission to access the first resource;

The electronic device, in response to the first access request, grants the first authority to a first agent, and grants the callee the authority to access the first agent;

The electronic device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent;

The electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent.
The method according to claim 20, wherein the first authority has a time limit, and the time limit is any one of the following: valid once, valid for a first time, or valid in a first area;

The electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent, specifically including:

If the time limit is valid for one time, the electronic device terminates the first agent or revokes the first authority possessed by the first agent after the electronic device finishes accessing the first resource;

If the time limit is valid within the first time or within the first area, the electronic device may, after receiving the first time of the first permission information, or at a non- In the first area, the first agent is terminated or the first authority possessed by the first agent is revoked.
The method according to claim 20, wherein the electronic device terminates the first agent, or the electronic device revokes the first authority possessed by the first agent, specifically comprising:

The electronic device terminates the first agent or revokes the first authority possessed by the first agent after ending access to the first resource, or after finishing accessing the first resource for a second time. .
The method according to any one of claims 20-22, wherein a second caller is further installed in the electronic device, and the second caller is the APP or the functional component;

The electronic device granting the right to access the first agent to the callee specifically includes: the electronic device granting the right to access the first agent to the first instance of the callee;

The electronic device running the callee and accessing the first agent specifically includes: the electronic device running the first instance and accessing the first agent;

The method also includes:

The electronic device generates a second access request, and acquires a second permission, the second access request is used by the second caller to call the callee to access the first resource, and the second permission includes the right to invoke the callee, and/or the right to access the first resource;

The electronic device, in response to the second access request, grants the second authority to a second agent, and grants the authority to access the second agent to a second instance of the callee, where the second agent is services, processes or threads;

The electronic device runs the second instance, accesses the second agent, and accesses the first resource through the second authority possessed by the second agent;

Wherein, the first instance and the second instance are processes or threads running in random access memory RAM, the second instance is different from the first instance, the second instance and the first instance isolated from each other.
The method of claim 23, wherein before the electronic device grants the first instance of the callee access to the first agent, the method further comprises:

The electronic device creates the first instance in response to the first access request.
The method according to any one of claims 20-24, wherein the first agent comprises: a first routing agent and a first withdrawing agent; the first routing agent and the first withdrawing agent are services , process or thread;

The electronic device grants the first authority to the first agent, and grants the callee the authority to access the first agent, specifically including: the electronic device grants the first authority to the first revocation an agent, granting the callee the right to access the first routing agent;

The electronic device runs the callee, accesses the first agent, and accesses the first resource through the first authority possessed by the first agent, specifically including: the electronic device running the The callee accesses the first revocation proxy through the first routing proxy, and accesses the first resource through the first authority possessed by the first revocation proxy;

The electronic device terminates the first proxy, or the electronic device revokes the first authority possessed by the first proxy, specifically including: the electronic device terminates the first routing proxy and/or the electronic device The first revocation agent, or the electronic device revokes the first authority possessed by the first revocation agent.
The method according to any one of claims 20-25, wherein before the electronic device grants the first permission to the first agent in response to the first access request, the method further comprises:

The electronic device creates the first proxy in response to the first access request.
The method according to any one of claims 20-26, wherein the first authority specifically includes:

the permission of the electronic device to invoke the callee, and/or the permission of the electronic device to access the first resource;

and / or,

The permission of the first caller to invoke the callee, and/or the permission of the first caller to access the first resource.
The method according to any one of claims 20-27, wherein before the electronic device acquires the first permission, the method further comprises:

The electronic device outputs prompt information, where the prompt information is used to prompt the first authority;

The electronic device receives a user operation.
An electronic device, characterized in that it comprises: a memory and one or more processors; the memory is coupled to the one or more processors, and the memory is used to store computer program codes, and the computer program codes include Computer instructions invoked by the one or more processors to cause the electronic device to perform the method of any of claims 11-19 or 20-28.
A computer-readable storage medium comprising instructions, characterized in that, when the instructions are executed on an electronic device, the electronic device is caused to perform the method according to any one of claims 11-19 or 20-28 .
A computer program product, characterized in that, when the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 11-19 or 20-28.
A communication system, characterized in that the communication system comprises: a first device and a second device, wherein the first device is configured to execute the method according to any one of claims 11-19.