Distributed multi-device security collaboration method, device, equipment, medium and product
By automatically determining equipment in the LAN using a trusted operation framework and a security collaborative decision center, multiple devices that are unaware of are achieved, solving the problem of poor user experience caused by user manual configuration, and improving the convenience of secure operation.
Patent Information
- Application Number
- CN202411470408.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-10-21
- Publication Date
- 2024-12-06
AI Technical Summary
When there are multiple devices with security capabilities in the same LAN, users need to manually configure and coordinate security operations, resulting in poor user experience.
The trusted operation framework calls the security collaborative decision center, determines the coordinated equipment from the security resource pool, and flows trusted applications to a trusted container of the equipment with secure operation capabilities to achieve multi-device security without user perception Coordination.
It realizes the free flow of secure collaborative operations, improves the user experience of secure operations, avoids the steps of manual configuration of users, and simplifies the safe operation process.
Smart Images

Figure CN119094239A_ABST
Abstract
Description
Technical Field
[0001] Embodiments of the present invention relate to the field of information security technology, and in particular to a distributed multi-device security collaboration method, apparatus, equipment, medium and product. Background Art
[0002] In today's highly digitalized and networked world, various business scenarios require devices to perform security operations, such as identity authentication, data encryption, etc. Devices without security capabilities cannot complete security operations independently, and devices with security capabilities are expensive and have single functions.
[0003] At present, although devices without security capabilities can perform security business operations with the help of devices with security capabilities, if there are multiple devices with security capabilities in the same local area network, users are required to manually configure the devices with security capabilities to collaborate in security operations, resulting in a poor user experience for security operations. Summary of the invention
[0004] The present invention provides a distributed multi-device security collaboration method, apparatus, equipment, medium and product, which can realize multi-device security collaboration without user perception and improve the user experience of security operations.
[0005] In a first aspect, an embodiment of the present invention provides a distributed multi-device security collaboration method, which is applied to a first device, and the method includes:
[0006] When the client application in the first device calls the corresponding trusted application, loading the trusted application through the trusted execution framework;
[0007] Calling a security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from a plurality of devices corresponding to a security resource pool, wherein the plurality of devices all have security operation capabilities;
[0008] By combining the trusted execution framework with the secure resource pool and the first distributed service, the trusted application is transferred to the trusted container of the second device for execution;
[0009] Obtain the running result in the trusted container of the second device.
[0010] In a second aspect, an embodiment of the present invention provides a distributed multi-device security collaboration device, which is configured on a first device, and the device includes:
[0011] a loading module, configured to load the trusted application through a trusted execution framework when a client application in the first device calls a corresponding trusted application;
[0012] A decision module, configured to call a security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from a plurality of devices corresponding to a security resource pool, wherein the plurality of devices all have security operation capabilities;
[0013] A transfer module, configured to transfer the trusted application to a trusted container of the second device for execution through the trusted execution framework in combination with the security resource pool and the first distributed service;
[0014] The result acquisition module is used to obtain the operation result in the trusted container of the second device.
[0015] In a third aspect, an embodiment of the present invention provides an electronic device, including:
[0016] at least one processor; and
[0017] a memory communicatively connected to the at least one processor; wherein,
[0018] The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method according to the first aspect.
[0019] In a fourth aspect, an embodiment of the present invention provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method described in the first aspect when executed.
[0020] In a fifth aspect, an embodiment of the present invention provides a computer program product, wherein the computer program product comprises a computer program, and when the computer program is executed by a processor, the method as described in the first aspect is implemented.
[0021] The technical solution of the embodiment of the present invention, when a first device without security operation capability needs to perform security operation, the security collaborative decision center can automatically determine the second device that can collaboratively run the trusted application corresponding to the first device among multiple devices with security operation capability corresponding to the security resource pool, and transfer the trusted application to the trusted container of the second device to obtain the operation result. This solution realizes the free flow of security collaborative operation, achieves the effect of multi-device security collaboration without user perception, and improves the user experience of security operation.
[0022] It should be understood that the contents described in this section are not intended to identify the key or important features of the embodiments of the present invention, nor are they intended to limit the scope of the present invention. Other features of the present invention will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.
[0024] Figure 1 is a flow chart of a distributed multi-device security collaboration method provided according to Embodiment 1 of the present invention;
[0025] Figure 2 is a schematic diagram of a system architecture of a first device provided according to Embodiment 1 of the present invention;
[0026] Figure 3 is a schematic diagram of a security resource pool provided according to Embodiment 1 of the present invention;
[0027] Figure 4 is a flowchart of operations included in a second device provided according to Embodiment 2 of the present invention;
[0028] Figure 5 is a schematic diagram of interaction between a first device and a second device provided according to Embodiment 2 of the present invention;
[0029] Figure 6 is a schematic diagram of a single-task multi-device security collaboration provided according to Embodiment 3 of the present invention;
[0030] Figure 7 This is a schematic diagram of a complex task multi-device security collaboration provided according to Embodiment 3 of the present invention;
[0031] Figure 8 This is a schematic diagram of multi-device security collaboration involving a data acquisition device provided in Embodiment 3 of the present invention;
[0032] Fig. 9 2 is a schematic diagram of the structure of a distributed multi-device security collaboration device provided according to Embodiment 4 of the present invention;
[0033] Fig.10 It is a schematic diagram of the structure of an electronic device implementing an embodiment of the present invention. DETAILED DESCRIPTION
[0034] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work should fall within the scope of protection of the present invention.
[0035] It should be noted that the terms "first", "second", etc. in the present invention are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so that the embodiments of the present invention described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0036] Embodiment 1
[0037] Figure 1 This is a flow chart of a distributed multi-device security collaboration method provided according to the first embodiment of the present invention. This embodiment is applicable to the case where the first device implements a security operation through the collaboration of the second device. The method can be executed by a distributed multi-device security collaboration device, which can be implemented in the form of software and / or hardware and integrated in the first device. Further, the first device includes but is not limited to: a computer, a laptop, etc. Figure 1 As shown, the method includes the following S110-S140.
[0038] Figure 2 is a schematic diagram of a system architecture of a first device provided according to Embodiment 1 of the present invention. Figure 2 As shown, the first device includes an application layer and an operating system; the application layer includes a client application and a trusted application; the operating system runs in a non-secure environment, and the operating system includes a trusted operating framework, a security collaborative decision center, a security resource pool, and a first distributed service. Figure 2 The structure shown is Figure 1 The method shown is described as follows:
[0039] S110. When a client application in the first device calls a corresponding trusted application, the trusted application is loaded through a trusted execution framework.
[0040] Among them, the client application (CA) can be an application related to the actual business in the first device, which is an application that can be operated by the user. The trusted application (TA) can be an application used to implement the security operation of the client application. Among them, the security operation can be an operation related to security, which can include but is not limited to security authentication, data encryption, etc., and the security authentication can be authentication of biometric features such as fingerprints and faces.
[0041] The trusted operation framework can provide a unified operation framework and application programming interface (API) for the application layer, including but not limited to: providing a framework service for a trusted execution environment (TEE), providing a framework service for a secure element (SE), and providing an API interface at the overall application level of TA, such as loading, authentication, mutual trust, running, and destroying TA applications. Among them, TEE and SE can be the parts of the device that can provide secure operation capabilities.
[0042] It should be noted that the trusted operation framework in the embodiment of the present invention is independent of the platform. The user does not need to be aware of whether the security operation is executed on the first device or on other devices, nor does the user need to be aware of the differences in the interfaces for security operations provided by different hardware devices, thereby achieving the purpose of shielding the differences between devices and platforms.
[0043] In the first device, when the user operates CA on the application side to trigger a security operation, CA can request the trusted operation framework to execute the corresponding TA, and the trusted operation framework loads TA based on the request and prepares to run TA in a secure environment. It can be understood that when the trusted operation framework loads TA, the trusted operation framework can determine the security operation that TA should perform.
[0044] S120. Calling a security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from a plurality of devices corresponding to a security resource pool, wherein the plurality of devices all have security operation capabilities.
[0045] The security resource pool may be a virtualized collection of security resources of multiple devices with security operation capabilities. Security operation capability refers to the ability to implement security operations. Security resources refer to resources with security operation capabilities, and security resources refer to TEEs or SEs that can be used to collaboratively execute trusted applications.
[0046] Figure 3 FIG. 1 is a schematic diagram of a security resource pool provided according to Embodiment 1 of the present invention, and is an exemplary description of the security resource pool. Figure 3 As shown in the figure, the controller, tablet, notebook, and test box can be devices in the same LAN environment as the first device and have security operation capabilities, that is, multiple devices corresponding to the security resource pool. The security resources of the controller and notebook are TEE, and the security resources of the tablet and test box are SE. The security resources corresponding to each device are virtualized into Figure 3 The security resource pool shown.
[0047] Figure 3 A distributed hardware management framework is also shown, which includes global hardware resource management and a unified hardware abstract interface. Among them, the distributed hardware management framework can be a framework for centralized management and efficient scheduling of hardware resources in a distributed environment, that is, for implementing the management and scheduling of security resources in a security resource pool. Global hardware resource management can be a service for implementing centralized management of security resources in a security resource pool. The unified hardware abstract interface can be an interface for unified calling of security resources in a security resource pool, and the differences between devices and platforms can be shielded when calling through this interface.
[0048] The security collaborative decision center can be a part used to determine the second device that collaboratively runs the trusted application among the multiple devices corresponding to the security resource pool. In this step, the security collaborative decision center is called through the trusted operation framework, and the security collaborative decision center can analyze the security operations that TA should perform, analyze the security operation capabilities of each device in the security resource pool, analyze the load capacity of the multiple devices corresponding to the security resource pool, and analyze the devices that users are accustomed to using among the multiple devices corresponding to the security resource pool. Combined with the above-mentioned analysis of multiple aspects, the algorithm finally determines the second device that collaboratively runs the trusted application among the multiple devices corresponding to the security resource pool.
[0049] In one embodiment, determining a second device for collaboratively running the trusted application from a plurality of devices corresponding to a security resource pool includes:
[0050] Determine the target security operation capability required for the security task to be performed by the trusted application;
[0051] Determining candidate security operation capabilities possessed by each device corresponding to the security resource pool;
[0052] Determining the load capacity of multiple devices corresponding to the security resource pool;
[0053] Determine a target device related to user preferences among a plurality of devices corresponding to the security resource pool;
[0054] Based on the target security operation capability, the candidate security operation capability, the load capability, and the target device, a second device that cooperates with the trusted application is determined.
[0055] The target security operation capability may be the security operation capability required by the security task to be performed by the trusted application. The security task to be performed by the trusted application may be understood as the security operation that the TA should perform. Different security tasks, such as security authentication and data encryption, require different security operation capabilities.
[0056] Among the multiple devices corresponding to the security resource pool, each device has a corresponding security operation capability, namely, a candidate security operation capability. For example, among the multiple devices, the candidate security operation capability of device A is face authentication, and the candidate security operation capability of device B is data encryption.
[0057] The analysis of the load capacity of multiple devices corresponding to the security resource pool can mainly analyze the load capacity of devices among the multiple devices that have the target security operation capability, or can mainly analyze the load capacity of devices among the multiple devices that are performing security operations, which is not limited here.
[0058] The target device may be a device related to the user's preferences among the multiple devices corresponding to the security resource pool, and the device related to the user's preferences may be a device that the user is accustomed to using for security operations. The device that the user is accustomed to using for security operations may be understood as a device that has been used more than a set threshold number of times within a certain period of time.
[0059] Based on the target security operation capability, candidate security operation capability, load capacity and target device, an algorithm can be used to decide the second device that collaboratively runs the trusted application among multiple devices corresponding to the security resource pool. The core of the algorithm decision may be: selecting devices corresponding to candidate security operation capabilities that are consistent with the target security operation capability; making multiple devices in the security resource pool as load balanced as possible; and giving priority to target devices that users are accustomed to using.
[0060] S130: Transfer the trusted application to the trusted container of the second device for execution by combining the trusted execution framework with the security resource pool and the first distributed service.
[0061] Among them, the first distributed service can be a distributed service provided in the first device, and the distributed service can be used to provide data communication and flow capabilities across operating systems. The trusted container can be a secure and isolated operating environment in the second device, which is used to execute trusted applications on the second device to ensure the security of its operation and the isolation of data. The trusted container can be understood as a hardware-independent TA trusted operating environment, which provides API interfaces such as TA application loading, authentication, mutual trust, operation, and destruction in TEE.
[0062] In this step, based on the trusted operation framework determining that the second device is the one that collaboratively runs the trusted application, the secure resource pool can be called through the trusted operation framework, and the secure resource pool can then call the first distributed service to transfer the trusted application through the first distributed service to the trusted container of the second device for execution.
[0063] In one embodiment, the trusted execution framework is combined with the secure resource pool and the first distributed service to transfer the trusted application to the trusted container of the second device for execution, including:
[0064] Calling the hardware operation interface of the security resource pool based on the decision result of the security collaborative decision center through the trusted operation framework, wherein the decision result indicates that the second device is the one that collaboratively runs the trusted application;
[0065] Invoking the first distributed service based on the decision result through the security resource pool;
[0066] The trusted application is transferred to the trusted container of the second device for execution based on the decision result through the first distributed service.
[0067] Through the trusted operation framework, based on the decision result of the security collaborative decision center, that is, the result of collaborative operation of the trusted application as the second device, call Figure 3 The distributed hardware management framework shown provides a unified hardware abstraction interface, and then calls the operation interface exposed by the security resource pool, that is, the hardware operation interface of the security resource pool. Through the security resource pool, the first distributed service is called based on the decision result, and the first distributed service can transfer the trusted application to the trusted container of the second device for operation according to the decision result. Among them, the first distributed service can communicate across devices based on the distributed soft bus that comes with the operating system.
[0068] S140: Obtain the operation result in the trusted container of the second device.
[0069] The running result may be a result generated by the running of the trusted application in the trusted container of the second device, such as a result of security authentication, indicating whether the facial authentication or fingerprint authentication is passed, or a result of data encryption, such as encrypted data.
[0070] In this step, the first device can obtain the operation result in the trusted container of the second device through communication interaction with the second device. For example, the trusted application in the first device can obtain the operation result in the trusted container of the second device, and the trusted application in the first device further returns the operation result to the client application, so that the client application performs corresponding business operations based on the operation result.
[0071] The technical solution of the embodiment of the present invention, when a first device without security operation capability needs to perform security operation, the security collaborative decision center can automatically determine the second device that can collaboratively run the trusted application corresponding to the first device among multiple devices with security operation capability corresponding to the security resource pool, and transfer the trusted application to the trusted container of the second device to obtain the operation result. This solution realizes the free flow of security collaborative operation, achieves the effect of multi-device security collaboration without user perception, and improves the user experience of security operation.
[0072] Embodiment 2
[0073] The embodiment of the present invention is based on the above embodiment 1, and specifically describes the operation of the second device involved in the above embodiment 1. The second device may include but is not limited to: a computer, a notebook computer, etc.
[0074] Figure 4 is a flowchart of operations included in a second device provided according to Embodiment 2 of the present invention, such as Figure 4 As shown, it includes the following S410-S440.
[0075] Figure 5 is a schematic diagram of interaction between a first device and a second device provided according to Embodiment 2 of the present invention, Figure 5 FIG. 1 shows not only the system architecture of the second device, but also the data flow when the first device interacts with the second device. Figure 5 As shown, the second device includes an operating system and a hardware layer; the operating system includes two parts: a non-secure environment and a secure environment; the non-secure environment includes a trusted operating framework, a second distributed service, a secure resource pool, and a secure collaborative decision center; the secure environment includes a trusted container and a trusted operating unit; the hardware layer is the secure resource TEE and SE that the second device can provide. Figure 5 The architecture shown is Figure 4 The operations shown are described as follows, and the contents not fully explained in this embodiment can refer to the above-mentioned embodiment 1.
[0076] S410. Obtain, through a second distributed service in the second device, a trusted application transferred from the first device to the second device.
[0077] The second distributed service may be a distributed service provided in the second device, and the distributed service may be used to provide data communication and flow capabilities across operating systems.
[0078] Depend on Figure 5It can be seen that the first distributed service in the first device can communicate with the second distributed service in the second device. In the case where the trusted application is transferred to the second device through the first distributed service in the first device in S130 of the above-mentioned embodiment 1, this step can use the second distributed service in the second device to perform cross-device communication based on the distributed soft bus provided by the operating system, and obtain the trusted application transferred from the first device to the second device from the first distributed service in the first device.
[0079] S420: Call the trusted container in the second device through the second distributed service in combination with the security resource pool in the second device.
[0080] A trusted container can be a secure and isolated operating environment in the second device, used to execute trusted applications on the second device to ensure the security of its operation and the isolation of data. A trusted container can be understood as a hardware-independent TA trusted operating environment, providing API interfaces such as TA application loading, authentication, mutual trust, operation, and destruction in TEE.
[0081] In this step, when the second distributed service obtains the trusted application, the security resource pool in the second device can be called through the second distributed service, and the security resource pool in the second device then calls the interface provided by the trusted container to load and run the trusted application.
[0082] In one embodiment, calling the trusted container in the second device through the second distributed service in combination with the secure resource pool in the second device includes:
[0083] Calling, through the second distributed service, a hardware operation interface of the security resource pool in the second device;
[0084] The interface for loading and running the trusted application provided by the trusted container is called through the security resource pool in the second device.
[0085] Through the second distributed service, the unified hardware abstraction interface provided by the distributed hardware management framework corresponding to the security resource pool of the second device can be called, and then the local operation interface exposed by the security resource pool of the second device, that is, the hardware operation interface of the security resource pool, can be called. When the security resource pool of the second device receives the call, it calls the interface for loading and running the trusted application provided by the trusted container.
[0086] S430: Run the trusted application through the trusted container to obtain an operation result.
[0087] The running result may be a result generated by the running of the trusted application in the trusted container of the second device, such as a result of security authentication, indicating whether the facial authentication or fingerprint authentication is passed, or a result of data encryption, such as encrypted data.
[0088] In this step, the target security hardware with the target security operation capability in the second device can be called through the trusted container to run the trusted application to obtain the running result. Among them, the target security operation capability can be the security operation capability required for the security task executed by the trusted application. The target security hardware can be the security hardware with the target security operation capability in the second device, such as TEE or SE.
[0089] In one embodiment, running the trusted application through the trusted container to obtain an operation result includes:
[0090] Calling a trusted operating unit in the second device through the trusted container, wherein the trusted operating unit provides a calling interface for target secure hardware in the second device, and the target secure hardware has a target secure operation capability required for a security task executed by the trusted application;
[0091] The trusted execution unit calls the target secure hardware based on the calling interface to execute the trusted application to obtain an execution result.
[0092] The trusted operation unit can be the part of the second device that is responsible for managing and controlling access to the hardware layer. The trusted operation unit can be understood as the hardware adaptation layer of the trusted container, which can shield the interface differences of security hardware such as TEE and SE of different manufacturers and hardware, and can provide API interfaces for the security operations of specific security hardware.
[0093] The trusted container can be used to call the calling interface of the target secure hardware provided by the trusted running unit; the trusted running unit then actually runs the trusted application according to the calling interface of the target secure hardware; when secure operations are required in the trusted application, the interface provided by the software development kit (SDK) of the trusted application is called to perform secure operations and obtain the running results.
[0094] S440: Feedback the operation result to the first device.
[0095] In this step, the second device may feed back the operation result in the trusted container of the second device to the first device through communication interaction with the first device.
[0096] When the second device feeds back the operation result to the first device, the above embodiment S140 can obtain the operation result in the trusted container of the second device through the first device. For example, the trusted application in the first device can obtain the operation result fed back by the second device, and the trusted application in the first device further returns the operation result to the client application, so that the client application performs corresponding business operations based on the operation result.
[0097] The technical solution of the embodiment of the present invention obtains the trusted application transferred from the first device to the second device through the second distributed service in the second device, calls the trusted container through the second distributed service in combination with the security resource pool, runs the trusted application through the trusted container to obtain the running result, and feeds back the running result to the first device. Based on the free flow of secure collaborative operations, this solution automatically cooperates with the first device that does not have the target security operation capability to perform security operations through the second device that has the target security operation capability, achieving the effect of multi-device security collaboration without user perception, and improving the user experience of security operations.
[0098] Embodiment 3
[0099] The embodiment of the present invention is based on the above Figure 5 Based on this, a comprehensive description is given of the operation of the first device in Example 1 and the operation of the second device in Example 2.
[0100] (1) In the first device, when a user operates a client application on the application side to trigger a security operation, the client application in the first device calls a corresponding trusted application, and the trusted execution framework in the first device loads the trusted application and prepares to execute the trusted application in a secure environment.
[0101] (2) In the first device, the security collaborative decision center is called through the trusted operation framework, and the security collaborative decision center performs security task analysis, security resource analysis, device load capacity analysis, and user habit analysis, and determines the second device that collaboratively runs the trusted application from the multiple devices corresponding to the security resource pool. Among them, the security task analysis is to determine the target security operation capability required for the security task to be executed by the trusted application; the security resource analysis is to determine the candidate security operation capability possessed by each device corresponding to the security resource pool; the device load capacity analysis is to determine the load capacity of the multiple devices corresponding to the security resource pool; the user habit analysis is to determine the target device related to the user's preferences among the multiple devices corresponding to the security resource pool; the second device can be determined by comprehensively considering the target security operation capability, candidate security operation capability, load capacity, and target device.
[0102] (3) In the first device, through the trusted operation framework, based on the decision result of the security collaborative decision-making center, that is, the result of collaboratively running the trusted application for the second device, the security resource pool of the first device is called. Specifically, the unified hardware abstract interface provided by the distributed hardware management framework of the security resource pool of the first device is called, and then the hardware operation interface of the security resource pool of the first device is called; through the security resource pool of the first device, the first distributed service is called based on the decision result, and the first distributed service can transfer the trusted application to the second device according to the decision result.
[0103] (4) In the second device, the second distributed service can communicate across devices based on the distributed soft bus provided by the operating system, and obtain the trusted application transferred from the first device to the second device from the first distributed service in the first device.
[0104] (5) In the second device, the security resource pool of the second device is called through the second distributed service. Specifically, a unified hardware abstraction interface provided by the distributed hardware management framework of the security resource pool of the second device is called, and then the hardware operation interface of the security resource pool of the second device is called; through the security resource pool in the second device, an interface for loading and running trusted applications provided by the trusted container is called.
[0105] (6) In the second device, a trusted operating unit in the second device is called through the trusted container. The trusted operating unit provides a calling interface for the target security hardware in the second device. The target security hardware has the target security operation capability required for the security task to be executed by the trusted application. Through the trusted operating unit, the target security hardware is called based on the calling interface to run the trusted application to obtain the running result.
[0106] (7) The second device feeds back the running result to the trusted application in the first device.
[0107] (8) The trusted application in the first device obtains the operation result fed back by the second device, and the trusted application in the first device further returns the operation result to the client application, so that the client application performs corresponding business operations based on the operation result.
[0108] The following are examples of different scenarios:
[0109] Scenario 1: Single-task multi-device security collaboration:
[0110] Figure 6 Schematic diagram of a single-task multi-device security collaboration provided according to Embodiment 3 of the present invention. Figure 6 As shown in the figure, the tablet, controller, notebook, and test box can be devices in the same LAN environment. They form an integrated terminal that can perform distributed capability collaboration. Figure 6In the integrated terminal shown, the tablet is equivalent to the first device in the embodiment of the present invention, and the notebook is equivalent to the second device in the embodiment of the present invention.
[0111] The tablet has no security authentication capability but has security collaborative decision-making capability. When the client application in the tablet calls the corresponding trusted application and needs to perform facial authentication, the trusted application is loaded through the trusted operation framework; the tablet calls the security collaborative decision-making center through the trusted operation framework, and the security collaborative decision-making center performs security task analysis, security resource analysis, device load capacity analysis and user habit analysis to determine that the notebook is the one that collaboratively runs the trusted application; the tablet transfers the trusted application to the notebook through the trusted operation framework in combination with the security resource pool and the first distributed service; the notebook's second distributed service obtains the trusted application; the notebook's second distributed service calls the notebook's trusted container in combination with the notebook's security resource pool; the notebook's trusted container runs the trusted application to obtain the running result; the notebook feeds the running result back to the tablet; the tablet obtains the running result in the notebook's trusted container.
[0112] Through the above process, the client application on the tablet needs to perform facial authentication. When data collection, i.e., facial data to be authenticated, is completed, the facial authentication capability in the notebook can be called through distributed technology to obtain the result of facial authentication and then perform corresponding business operations.
[0113] Scenario 2: Safe collaboration of multiple devices for complex tasks:
[0114] Figure 7 This is a schematic diagram of a complex task multi-device security collaboration provided according to Embodiment 3 of the present invention. This example may be in an industrial high security requirement scenario where strong identity authentication of staff is required, such as simultaneous facial authentication and fingerprint authentication of staff according to business application requirements.
[0115] like Figure 7 As shown in the figure, the small and light devices that need strong identity authentication can be in the same LAN environment as the laptop and the controller. They form an integrated terminal that can perform distributed capability collaboration. Figure 7 In the integrated terminal shown, the small and light device is equivalent to the first device in the embodiment of the present invention, and the notebook and the controller are equivalent to the second device in the embodiment of the present invention.
[0116] Small and light devices do not have strong identity authentication capabilities but have secure collaborative decision-making capabilities. Small and light devices collect facial data and fingerprint data, analyze strong identity authentication tasks, and split them into facial authentication tasks and fingerprint authentication tasks. The following is an explanation based on the split tasks:
[0117] a. Face authentication task
[0118] When the client application in the small and light device calls the trusted application corresponding to the facial authentication task, the trusted application is loaded through the trusted operation framework; the small and light device calls the security collaborative decision-making center through the trusted operation framework, and the security collaborative decision-making center performs security task analysis, security resource analysis, device load capacity analysis and user habit analysis to determine that the notebook is the one that collaboratively runs the trusted application; the small and light device transfers the trusted application to the notebook through the trusted operation framework in combination with the security resource pool and the first distributed service; the second distributed service of the notebook obtains the trusted application; the second distributed service of the notebook calls the trusted container of the notebook in combination with the security resource pool of the notebook; the trusted container of the notebook runs the trusted application to obtain the running result; the notebook feeds back the running result to the small and light device; the small and light device obtains the running result in the trusted container of the notebook.
[0119] b. Fingerprint authentication task
[0120] When the client application in the small and light device calls the trusted application corresponding to the fingerprint authentication task, the trusted application is loaded through the trusted operation framework; the small and light device calls the security collaborative decision-making center through the trusted operation framework, and the security collaborative decision-making center performs security task analysis, security resource analysis, device load capacity analysis and user habit analysis to determine that the controller is the one that collaboratively runs the trusted application; the small and light device transfers the trusted application to the controller through the trusted operation framework in combination with the security resource pool and the first distributed service; the second distributed service of the controller obtains the trusted application; the second distributed service of the controller calls the trusted container of the controller in combination with the security resource pool of the controller; the trusted container of the controller runs the trusted application to obtain the running result; the controller feeds back the running result to the small and light device; the small and light device obtains the running result in the trusted container of the controller.
[0121] Through the above process, the client application on the lightweight device needs to perform strong identity authentication. When the data collection, i.e. the facial data to be authenticated and the fingerprint data to be authenticated, is completed, the facial authentication capability in the notebook can be called through distributed technology to obtain the facial authentication result, and the fingerprint authentication capability in the controller can be called through distributed technology to obtain the fingerprint authentication result, and then the corresponding business operations can be performed.
[0122] Scenario 3: Multi-device security collaboration involving data acquisition equipment:
[0123] Figure 8 Schematic diagram of multi-device security collaboration involving data acquisition equipment according to Embodiment 3 of the present invention. Figure 8 As shown in the figure, the data acquisition equipment, i.e., the camera, controller, tablet, notebook, and test box, can be devices in the same LAN environment. They form an integrated terminal that can perform distributed capability collaboration. Figure 8In the integrated terminal shown, the controller is equivalent to the first device in the embodiment of the present invention, and the notebook is equivalent to the second device in the embodiment of the present invention.
[0124] exist Figure 8 In the example shown, the data acquisition device does not have the ability to make secure collaborative decisions. After collecting data, the data acquisition device transmits the collected data and the facial recognition task to the controller, and the controller and the notebook collaborate to perform the facial recognition task.
[0125] The controller does not have security authentication capabilities but has security collaborative decision-making capabilities. After receiving data transmitted by the data acquisition device and facial authentication tasks, the client application in the controller calls the corresponding trusted application and loads the trusted application through the trusted operation framework; the controller calls the security collaborative decision-making center through the trusted operation framework, and the security collaborative decision-making center performs security task analysis, security resource analysis, device load capacity analysis, and user habit analysis to determine that the notebook is the one that collaboratively runs the trusted application; the controller transfers the trusted application to the notebook through the trusted operation framework in combination with the security resource pool and the first distributed service; the notebook's second distributed service obtains the trusted application; the notebook's second distributed service calls the notebook's trusted container in combination with the notebook's security resource pool; the notebook's trusted container runs the trusted application to obtain the running result; the notebook feeds the running result back to the controller; the controller obtains the running result in the notebook's trusted container.
[0126] Through the above process, after the data acquisition device collects facial data, the collected facial data and facial authentication tasks are transmitted to the controller. The controller can call the facial authentication capability in the notebook through distributed technology to obtain the facial authentication result.
[0127] The technical solution of the embodiment of the present invention is to build a security collaborative decision-making center in the operating system. The security collaborative decision-making center performs security task analysis, security resource analysis, device load capacity analysis and user habit analysis, and automatically determines the device resources most suitable for security operations in the integrated terminal. The user does not need to manually specify a device to perform security operations, thereby achieving the effect of multi-device security collaboration without the user's perception.
[0128] The technical solution of the embodiment of the present invention can meet security requirements by pooling security resources of multiple devices and enabling any device to run security services with the help of a distributed soft bus; a unified security resource abstract interface is provided to applications through a trusted operation framework, so that users are unaware of the differences in security capabilities between devices.
[0129] Embodiment 4
[0130] Fig. 91 is a schematic diagram of the structure of a distributed multi-device security collaboration device according to the fourth embodiment of the present invention. This embodiment is applicable to the case where the first device realizes security operation through the collaboration of the second device. Fig. 9 As shown, the device is configured in the first device, and the specific structure of the device includes:
[0131] A loading module 910, configured to load the trusted application through a trusted execution framework when a client application in the first device calls a corresponding trusted application;
[0132] A decision module 920 is used to call the security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from multiple devices corresponding to the security resource pool, and the multiple devices all have security operation capabilities;
[0133] A transfer module 930, configured to transfer the trusted application to a trusted container of the second device for execution through the trusted execution framework in combination with the security resource pool and the first distributed service;
[0134] The result acquisition module 940 is used to acquire the operation result in the trusted container of the second device.
[0135] The distributed multi-device security collaboration device provided in this embodiment loads the trusted application through the trusted operation framework when the client application in the first device calls the corresponding trusted application through the loading module; the decision module calls the security collaboration decision center through the trusted operation framework to determine the second device that collaborates with the trusted application from multiple devices corresponding to the security resource pool, and the multiple devices all have security operation capabilities; the transfer module transfers the trusted application to the trusted container of the second device for operation through the trusted operation framework in combination with the security resource pool and the first distributed service; the result acquisition module obtains the operation result in the trusted container of the second device. This solution realizes the free flow of secure collaborative operations, achieves the effect of multi-device security collaboration without user perception, and improves the user experience of secure operations.
[0136] Furthermore, the decision module 920 is specifically configured to:
[0137] Determine the target security operation capability required for the security task to be performed by the trusted application;
[0138] Determining candidate security operation capabilities possessed by each device corresponding to the security resource pool;
[0139] Determining the load capacity of multiple devices corresponding to the security resource pool;
[0140] Determine a target device related to user preferences among a plurality of devices corresponding to the security resource pool;
[0141] Based on the target security operation capability, the candidate security operation capability, the load capability, and the target device, a second device that cooperates with the trusted application is determined.
[0142] Furthermore, the circulation module 930 is specifically used for:
[0143] Calling the hardware operation interface of the security resource pool based on the decision result of the security collaborative decision center through the trusted operation framework, wherein the decision result indicates that the second device is the one that collaboratively runs the trusted application;
[0144] Invoking the first distributed service based on the decision result through the security resource pool;
[0145] The trusted application is transferred to the trusted container of the second device for execution based on the decision result through the first distributed service.
[0146] Furthermore, the operations in the second device include:
[0147] Acquire, through a second distributed service in the second device, a trusted application transferred from the first device to the second device;
[0148] Invoke the trusted container in the second device by combining the second distributed service with the security resource pool in the second device;
[0149] Running the trusted application through the trusted container to obtain an operation result;
[0150] The operation result is fed back to the first device.
[0151] Further, running the trusted application through the trusted container to obtain an operation result includes:
[0152] Calling a trusted operating unit in the second device through the trusted container, wherein the trusted operating unit provides a calling interface for target secure hardware in the second device, and the target secure hardware has a target secure operation capability required for a security task executed by the trusted application;
[0153] The trusted execution unit calls the target secure hardware based on the calling interface to execute the trusted application to obtain an execution result.
[0154] Further, calling the trusted container in the second device through the second distributed service in combination with the security resource pool in the second device includes:
[0155] Calling, through the second distributed service, a hardware operation interface of the security resource pool in the second device;
[0156] The interface for loading and running the trusted application provided by the trusted container is called through the security resource pool in the second device.
[0157] The distributed multi-device security collaboration apparatus provided in the embodiment of the present invention can execute the distributed multi-device security collaboration method provided in the embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.
[0158] Embodiment 5
[0159] Fig.10 is a schematic diagram of the structure of an electronic device implementing an embodiment of the present invention. The electronic device, i.e., the first device in the embodiment of the present invention, is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or required herein.
[0160] like Fig.10 As shown, the electronic device 10 includes at least one processor 11, and a memory connected to the at least one processor 11, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., wherein the memory stores a computer program that can be executed by at least one processor, and the processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 to the random access memory (RAM) 13. In the RAM 13, various programs and data required for the operation of the electronic device 10 can also be stored. The processor 11, the ROM 12, and the RAM 13 are connected to each other through a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.
[0161] A number of components in the electronic device 10 are connected to the I / O interface 15, including: an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.
[0162] The processor 11 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any appropriate processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as a distributed multi-device security collaboration method.
[0163] In some embodiments, the distributed multi-device security collaboration method may be implemented as a computer program, which is tangibly contained in a computer-readable storage medium, such as a storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 10 via the ROM 12 and / or the communication unit 19. When the computer program is loaded into the RAM 13 and executed by the processor 11, one or more steps of the distributed multi-device security collaboration method described above may be performed. Alternatively, in other embodiments, the processor 11 may be configured to execute the distributed multi-device security collaboration method in any other appropriate manner (e.g., by means of firmware).
[0164] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), load programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.
[0165] Computer programs for implementing the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the computer program is executed by the processor, the functions / operations specified in the flow chart and / or block diagram are implemented. The computer program may be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.
[0166] In the context of the present invention, a computer-readable storage medium may be a tangible medium that may contain or store a computer program for use by or in combination with an instruction execution system, device or equipment. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, or any suitable combination of the foregoing.
[0167] To provide interaction with a user, the systems and techniques described herein may be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and a pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user may be received in any form (including acoustic input, voice input, or tactile input).
[0168] The systems and techniques described herein may be implemented in a computing system that includes backend components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes frontend components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such backend components, middleware components, or frontend components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.
[0169] A computing system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The client and server relationship is generated by computer programs running on the corresponding computers and having a client-server relationship with each other. The server may be a cloud server, also known as a cloud computing server or cloud host, which is a host product in the cloud computing service system to solve the defects of difficult management and weak business scalability in traditional physical hosts and VPS services.
[0170] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps described in the present invention can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution of the present invention can be achieved, and this document does not limit this.
[0171] The above specific implementations do not constitute a limitation on the protection scope of the present invention. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modification, equivalent substitution and improvement made within the spirit and principle of the present invention should be included in the protection scope of the present invention.
Claims
1. A distributed multi-device security collaboration method, It is characterized in that Applied to a first device, the method includes: When the client application in the first device calls the corresponding trusted application, loading the trusted application through the trusted execution framework; Calling a security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from a plurality of devices corresponding to a security resource pool, wherein the plurality of devices all have security operation capabilities; By combining the trusted execution framework with the secure resource pool and the first distributed service, the trusted application is transferred to the trusted container of the second device for execution; Obtain the running result in the trusted container of the second device.
2. The method according to claim 1, It is characterized in that Determining a second device for collaboratively running the trusted application from a plurality of devices corresponding to the security resource pool includes: Determine the target security operation capability required for the security task to be performed by the trusted application; Determining candidate security operation capabilities possessed by each device corresponding to the security resource pool; Determining the load capacity of multiple devices corresponding to the security resource pool; Determine a target device related to user preferences among a plurality of devices corresponding to the security resource pool; Based on the target security operation capability, the candidate security operation capability, the load capability, and the target device, a second device that cooperates with the trusted application is determined.
3. The method according to claim 1, It is characterized in that The trusted application is transferred to the trusted container of the second device for execution by combining the trusted execution framework with the security resource pool and the first distributed service, including: Calling the hardware operation interface of the security resource pool based on the decision result of the security collaborative decision center through the trusted operation framework, wherein the decision result indicates that the second device is the one that collaboratively runs the trusted application; Invoking the first distributed service based on the decision result through the security resource pool; The trusted application is transferred to the trusted container of the second device for execution based on the decision result through the first distributed service.
4. The method according to claim 1, It is characterized in that The operations in the second device include: Acquire, through a second distributed service in the second device, a trusted application transferred from the first device to the second device; Invoke the trusted container in the second device by combining the second distributed service with the security resource pool in the second device; Running the trusted application through the trusted container to obtain an operation result; The operation result is fed back to the first device.
5. The method according to claim 4, It is characterized in that Running the trusted application through the trusted container to obtain an operation result includes: Calling a trusted operating unit in the second device through the trusted container, wherein the trusted operating unit provides a calling interface for target secure hardware in the second device, and the target secure hardware has a target secure operation capability required for a security task executed by the trusted application; The trusted execution unit calls the target secure hardware based on the calling interface to execute the trusted application to obtain an execution result.
6. The method according to claim 4, It is characterized in that Calling the trusted container in the second device by combining the second distributed service with the security resource pool in the second device includes: Calling, through the second distributed service, a hardware operation interface of the security resource pool in the second device; The interface for loading and running the trusted application provided by the trusted container is called through the security resource pool in the second device.
7. A distributed multi-device security collaboration device, It is characterized in that Configured in a first device, the apparatus comprises: a loading module, configured to load the trusted application through a trusted execution framework when a client application in the first device calls a corresponding trusted application; A decision module, configured to call a security collaborative decision center through the trusted operation framework to determine a second device that collaboratively runs the trusted application from a plurality of devices corresponding to a security resource pool, wherein the plurality of devices all have security operation capabilities; A transfer module, configured to transfer the trusted application to a trusted container of the second device for execution through the trusted execution framework in combination with the security resource pool and the first distributed service; The result acquisition module is used to obtain the operation result in the trusted container of the second device.
8. An electronic device, It is characterized in that include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program executable by the at least one processor, and the computer program is executed by the at least one processor so that the at least one processor can perform the method according to any one of claims 1 to 6.
9. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the method according to any one of claims 1 to 6 when executed.
10. A computer program product, It is characterized in that The computer program product comprises a computer program, which, when executed by a processor, implements the method according to any one of claims 1 to 6.
