CN111967010B - Trusted service method, trusted service device, trusted service equipment and storage medium - Google Patents
Trusted service method, trusted service device, trusted service equipment and storage medium Download PDFInfo
- Publication number
- CN111967010B CN111967010B CN201910419223.4A CN201910419223A CN111967010B CN 111967010 B CN111967010 B CN 111967010B CN 201910419223 A CN201910419223 A CN 201910419223A CN 111967010 B CN111967010 B CN 111967010B
- Authority
- CN
- China
- Prior art keywords
- trusted
- trusted hardware
- hardware
- information
- operating system
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 48
- 230000005540 biological transmission Effects 0.000 claims description 26
- 238000012546 transfer Methods 0.000 claims description 5
- JBWKIWSBJXDJDT-UHFFFAOYSA-N triphenylmethyl chloride Chemical compound C=1C=CC=CC=1C(C=1C=CC=CC=1)(Cl)C1=CC=CC=C1 JBWKIWSBJXDJDT-UHFFFAOYSA-N 0.000 claims 4
- 238000004590 computer program Methods 0.000 description 13
- 238000010586 diagram Methods 0.000 description 10
- 230000006870 function Effects 0.000 description 10
- 238000012545 processing Methods 0.000 description 8
- 238000001514 detection method Methods 0.000 description 5
- 230000008569 process Effects 0.000 description 5
- 230000004044 response Effects 0.000 description 4
- 238000005516 engineering process Methods 0.000 description 3
- 230000003993 interaction Effects 0.000 description 2
- 238000005259 measurement Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 230000008859 change Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/50—Monitoring users, programs or devices to maintain the integrity of platforms, e.g. of processors, firmware or operating systems
- G06F21/57—Certifying or maintaining trusted computer platforms, e.g. secure boots or power-downs, version controls, system software checks, secure updates or assessing vulnerabilities
Landscapes
- Engineering & Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
- Stored Programmes (AREA)
Abstract
The embodiment of the application provides a trusted service method, equipment and a storage medium, wherein the method comprises the following steps: receiving a trusted service call request sent by an application program; acquiring calling information of the trusted hardware currently in an online state; the operating system is invoked based on the invocation information to control trusted hardware currently in an online state through the operating system to respond to the trusted service invocation request. In the embodiment of the application, the trusted hardware management component on the computing device can support the calling of multiple types of trusted hardware, so that the types of trusted services which can be provided by the computing device are rich, different trusted service requirements can be met, and the trusted service quality can be further effectively improved.
Description
Technical Field
The present application relates to the field of trusted technologies, and in particular, to a trusted service method, apparatus, device, and storage medium.
Background
The trusted computing base is based on security, and the main idea of the trusted computing base is to introduce bottom trusted hardware on the computing platform, and improve the security of the computing platform through trusted services provided by the bottom trusted hardware.
Currently, the trusted platform module TPM is a type of bottom trusted hardware with wider application, however, there are many limitations on trusted services that the TPM can provide, and the increasingly complex trusted service requirements cannot be met, resulting in poor quality of trusted services.
Disclosure of Invention
Aspects of the present application provide a trusted service method, apparatus, device, and storage medium to improve the quality of trusted service.
The embodiment of the application provides a trusted service method, which comprises the following steps:
Receiving a trusted service call request sent by an application program;
Acquiring call information corresponding to the trusted hardware currently in an online state;
and calling an operating system based on the calling information so as to control the trusted hardware currently in an online state to respond to the trusted service calling request through the operating system.
The embodiment of the application also provides a computing device, which comprises a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for running the trusted hardware management component for:
Receiving a trusted service invocation request sent by the application program;
Acquiring call information corresponding to the trusted hardware currently in an online state;
and calling the operating system based on the calling information so as to control the trusted hardware currently in an online state to respond to the trusted service calling request through the operating system.
The embodiment of the application also provides a trusted service method, which comprises the following steps:
Receiving a trusted service call request of an application program, wherein the trusted service call request comprises type information of trusted hardware expected to be called by the application program;
Determining target trusted hardware matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application program;
and calling the target trusted hardware to respond to the trusted service calling request.
The embodiment of the application also provides a trusted service method, which comprises the following steps:
Determining the type information of the trusted hardware expected to be called based on the type of the currently operated service;
Generating a trusted service call request according to the type information of the trusted hardware expected to be called;
And sending the trusted service call request to a trusted hardware management component so that the trusted hardware management component can call an operating system according to the trusted service call request, and controlling target trusted hardware matched with the type information to respond to the trusted service call request through the operating system.
The embodiment of the application also provides a computing device, which comprises a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for running the trusted hardware management component for:
Receiving a trusted service call request of an application program, wherein the trusted service call request comprises type information of trusted hardware expected to be called by the application program;
Determining target trusted hardware matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application program;
and calling the target trusted hardware to respond to the trusted service calling request.
The embodiment of the application also provides a computing device, which comprises a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for executing the application for:
Determining the type information of the trusted hardware expected to be called based on the type of the currently operated service;
Generating a trusted service call request according to the type information of the trusted hardware expected to be called;
And sending the trusted service call request to a trusted hardware management component so that the trusted hardware management component can call an operating system according to the trusted service call request, and controlling target trusted hardware matched with the type information to respond to the trusted service call request through the operating system.
Embodiments of the present application also provide a computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the aforementioned trusted service method.
In the embodiment of the application, under the condition that the application program sends out the trusted service call request, the trusted hardware management component on the computing device can acquire the call information of the trusted hardware in the online state on the computing device and call the trusted hardware in the online state as required. Accordingly, in this embodiment, the trusted hardware management component on the computing device may support the invocation of multiple types of trusted hardware, which makes the types of trusted services that may be provided by the computing device abundant, and may satisfy different trusted service requirements, so as to effectively improve the trusted service quality.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this specification, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute a limitation on the application. In the drawings:
FIG. 1 is a schematic diagram of a computing device according to an embodiment of the present application;
FIG. 2 is a flow chart of a trusted service method according to another embodiment of the present application;
FIG. 3 is a schematic diagram of another computing device according to a further embodiment of the present application;
FIG. 4 is a flow chart of another trusted service method according to another embodiment of the present application;
Fig. 5 is a flow chart of a trusted service method according to another embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the application without making any inventive effort, are intended to be within the scope of the application.
Currently, the quality of trusted service is poor. To solve this technical problem, in some embodiments of the present application: under the condition that the application program sends out the trusted service call request, a trusted hardware management component on the computing device can acquire call information of the trusted hardware on the computing device in an online state and call the trusted hardware in the online state as required. Accordingly, in this embodiment, the trusted hardware management component on the computing device may support the invocation of multiple types of trusted hardware, which makes the types of trusted services that may be provided by the computing device abundant, and may satisfy different trusted service requirements, so as to effectively improve the trusted service quality.
The following describes in detail the technical solutions provided by the embodiments of the present application with reference to the accompanying drawings.
Fig. 1 is a schematic structural diagram of a computing device according to an embodiment of the present application. As shown in fig. 1, the computing device includes: a memory 10 and a processor 20. Wherein the memory 10 has stored therein an application 11, a trusted hardware management component 12 and an operating system; the processor 20 is coupled to the memory 10 and is operable to execute the trusted hardware management component 12.
In this embodiment, in terms of physical implementation, the computing device may be a terminal device such as a personal computer, a smart phone, a tablet computer, or may be a server device such as a conventional server, a cloud host, or a virtual center. This embodiment is not limited thereto. The server device mainly includes a processor 20, a hard disk, a memory, a system bus, and the like, and is similar to a general computer architecture.
In practice, the trusted hardware interface may be configured on the computing device, and the trusted hardware 30 may be assembled to the computing device through the trusted hardware interface. The trusted hardware interfaces may be one or more, and a single trusted hardware interface may support a single type of trusted hardware 30, and may be compatible with multiple types of trusted hardware 30.
Based on this, in the present embodiment, at the hardware level, the computing device may support the assembly of multiple types of trusted hardware 30. The computing device may support assembled trusted hardware 30 including at least trusted platform module TPM (Trusted Platform Module) and trusted platform control module TPCM (Trusted Platform Control Module). Of course, the present embodiments are not so limited, and the computing device may also support the assembly of other types of trusted hardware, which is not intended to be exhaustive.
In practice, a user may determine the type of trusted hardware that is installed on a computing device as desired. For example, a TPCM may be assembled on a computing device when the user plans to use the computing device for processing financial transactions. For another example, a TPM may be assembled on a computing device when the user plans to use the computing device for processing on-point traffic. In addition, the user may also replace trusted hardware installed on the computing device as desired, which is not limited in this embodiment.
Based on the hardware architecture on the computing device, in this embodiment, the processor 20 may run the trusted hardware management component 12 for:
receiving a trusted service invocation request sent by the application program 11;
acquiring call information corresponding to the trusted hardware 30 currently in an online state;
the operating system is invoked based on the invocation information to control the trusted hardware 30, currently in an online state, by the operating system to respond to the trusted service invocation request.
For ease of description, the following description will be presented in terms of a trusted hardware management component 12, but it should be understood that the following technical details are actually generated by the processor 20 running the trusted hardware management component 12.
In practice, the trusted hardware management component 12, upon receiving a trusted service invocation request from the application 11, may detect the type information of the trusted hardware 30 currently on-line on the computing device. The on-line state refers to a state that the trusted hardware is plugged into the trusted hardware plug-in interface and a subsequent in-use state. That is, while the trusted hardware remains in the plugged state of the trusted hardware plug interface described above, it may be determined that the trusted hardware is in an online state.
For example, when a TPCM is assembled on a computing device, the trusted hardware management component 12 may detect that the type of trusted hardware 30 currently on-line on the computing device is a TPCM; when a TPM is assembled on a computing device, trusted hardware management component 12 may detect that the type of trusted hardware 30 currently on-line on the computing device is a TPM.
On the basis of determining the type information of the trusted hardware 30 currently in an on-line state on the computing device, the trusted hardware management component 12 may select call information corresponding to the type information of the trusted hardware 30 currently in an on-line state from a preset call information set. The preset call information set contains call information corresponding to each of multiple types of trusted hardware which can be supported by the computing equipment. The call information includes, but is not limited to, a command transfer interface and a trusted hardware driver.
Accordingly, the trusted hardware management component 12 may obtain call information for the trusted hardware 30 that is in an online state. Of course, the implementation manner of acquiring the call information of the trusted hardware 30 in the online state in this embodiment is not limited to this, and for example, the call information corresponding to the trusted hardware 30 may be determined in real time according to the open port condition of the trusted hardware 30 and the operating system in the online state.
Based on the call information, the trusted hardware management component 12 may call an operating system, which, under the invocation of the trusted hardware management component 12, may control trusted hardware 30 currently in an online state on the computing device to provide trusted services for the application 11. The trusted services include, but are not limited to, integrity measurement and reporting services, authentication services, encryption and decryption services, and the like, which are not limited in this embodiment.
In this embodiment, in the case where the application 11 issues a trusted service invocation request, the trusted hardware management component 12 on the computing device may obtain invocation information of the trusted hardware 30 on the computing device that is in an online state, and make an on-demand invocation of the trusted hardware 30 that is in an online state. Accordingly, in this embodiment, the trusted hardware management component 12 on the computing device may support the invocation of multiple types of trusted hardware, which makes the types of trusted services that may be provided by the computing device abundant, and may satisfy different trusted service requirements, so as to effectively improve the trusted service quality.
In the above or below embodiments, the trusted hardware management component 12 may query the operating system for current hardware information; determining whether the trusted hardware 30 in an online state exists currently according to the current hardware information; if so, the type information of the trusted hardware 30 currently in an online state is obtained from the current hardware information.
In this embodiment, the trusted hardware management component 12 may query the current hardware information of the operating system through a query interface provided by the operating system. The current hardware information of the operating system includes information of the trusted hardware 30 currently in an online state on the computing device, and of course, includes information of other hardware running on the computing device, which is not detailed herein because it is not related to the present technical solution. In addition, the current hardware information of the operating system may be obtained by the operating system performing hardware detection on the computing device according to an existing hardware detection scheme, which is not described in detail herein.
In practical application, when the TPM is assembled on the computing device, the current hardware information of the operating system contains the information of the TPM; when the TPCM is assembled on the computing device, the current hardware information of the operating system will contain the information of the TPCM; and when trusted hardware is not assembled on the computing device, the current hardware information of the operating system will not contain any information of the trusted hardware. Accordingly, the trusted hardware management component 12 may determine whether trusted hardware is currently being deployed on the computing device based on current hardware information of the operating system.
If it is determined that the trusted hardware 30 currently in an online state exists on the computing device, the type information of the trusted hardware 30 currently in an online state may be read from the current hardware information of the operating system.
If it is determined that the trusted hardware 30 currently in the online state does not exist on the computing device, the detection of the type information and subsequent operations of the trusted hardware 30 currently in the online state, that is, the response to the trusted service invocation request issued by the application 11, is no longer performed. In this case, trusted hardware management component 12 may output an alert prompt to provision application 11 and/or a user of the computing device to obtain a status that the computing device is unable to provide trusted services.
Of course, the implementation of detecting the type information of the trusted hardware 30 currently in the online state is not limited thereto, and other implementations may be used to detect the type information of the trusted hardware 30 currently in the online state in this embodiment. For example, the trusted hardware management component 12 may detect heartbeat information on the aforementioned trusted hardware interface and, if heartbeat information is detected, obtain from the heartbeat information type information of the trusted hardware 30 that is currently in an online state. This embodiment is not limited thereto.
In the above or below embodiments, the trusted hardware management component 12 may be provided with the functionality of a dynamic link library. Accordingly, the trusted hardware management component 12 may generate a call command to the trusted hardware 30 currently in an online state based on the trusted service invocation request.
In this embodiment, the trusted hardware management component 12, upon receiving the trusted service invocation request issued by the application 11, may refine the trusted service invocation request into invocation commands for the trusted hardware based on its dynamic link library function. For example, when the trusted invocation request is to obtain content from trusted hardware, the trusted hardware management server may refine the trusted invocation request into invocation commands to read the configuration of the trusted hardware, read the storage space of the trusted hardware, and so on.
In addition, the trusted hardware management component 12 may also have the processing function of selecting call information. If the trusted hardware management component 12 determines that the trusted hardware 30 currently in the on-line state is a TPM, then call information matching the TPM may be selected from preset call information, where the selected call information includes at least the TPM command transmission interface (TPM Command Transmission Interface) and the TPM driver. If the trusted hardware 30 currently in the on-line state is determined to be a TPCM, call information matching the TPCM may be selected from preset call information, where the selected call information will include at least the TPCM command transmission interface (TPCM Command Transmission Interface) and the TPCM driver.
Further, the trusted hardware management component 12 may also have interaction functionality with an operating system. The trusted hardware management component 12 may transmit the foregoing call command to the operating system through the command transmission interface, so that the operating system may run the trusted hardware driver according to the call command to drive the trusted hardware 30 currently in an online state to provide the trusted service for the application 11.
For example, if the trusted hardware 30 currently on the computing device is a TPM, the trusted hardware management component 12 may transmit the call instruction to the TPM resource manager through the TPM command transmission interface, and after performing a resource management operation such as ordering the call instruction, the TPM resource manager may transmit the call instruction to the operating system, and the operating system may run the TPM driver to drive the TPM to provide the trusted service when receiving the call instruction.
For another example, if the trusted hardware 30 currently on the computing device is a TPCM, the trusted hardware management component 12 may transmit the call instruction to the TPCM resource manager through the TPCM command transmission interface, where the TPCM resource manager may transmit the call instruction to the operating system after performing a resource management operation such as ordering the call instruction, and the operating system may run the TPCM driver to drive the TPCM to provide the trusted service when receiving the call instruction.
In this embodiment, the trusted hardware-based management component 12 may detect the type of trusted hardware actually assembled on the computing device, and may flexibly switch the call information used to implement the call to multiple types of trusted hardware that may be assembled on the computing device.
Fig. 2 is a flow chart of a method for providing a trusted service according to another embodiment of the present application. As shown in fig. 2, the method includes:
200. Receiving a trusted service call request sent by an application program;
201. Acquiring call information corresponding to the trusted hardware currently in an online state;
202. The operating system is invoked based on the invocation information to control trusted hardware currently in an online state through the operating system to respond to the trusted service invocation request.
In an alternative embodiment, step 201 includes:
detecting type information of trusted hardware currently in an online state;
and selecting call information corresponding to the type information of the trusted hardware currently in the online state from a preset call information set.
In an alternative embodiment, the step of detecting type information of the trusted hardware currently in an online state includes:
Inquiring current hardware information of an operating system;
determining whether trusted hardware in an online state exists currently according to the current hardware information;
If the type information exists, the type information of the trusted hardware currently in the online state is obtained from the current hardware information.
In an alternative embodiment, the trusted hardware currently in an online state is a trusted platform module TPM or a trusted platform control module TPCM.
In an alternative embodiment, the call information includes a command transmission interface and a trusted hardware driver; step 202, including:
generating a calling command of the trusted hardware currently in an online state according to the trusted service calling request;
And transmitting a calling command to the operating system through the command transmission interface so that the operating system can operate the trusted hardware driver according to the calling command to drive the trusted hardware currently in an online state to provide trusted service for the application program.
It should be noted that, for the technical details mentioned or not mentioned in the embodiments of the trusted service method, reference should be made to the description in the embodiments of the computing device, which is not described in detail here for the sake of brevity, but this should not cause a loss of protection scope of the present application.
Accordingly, embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed is capable of implementing the steps of the method embodiments described above that may be performed by a trusted hardware management component.
Fig. 3 is a schematic structural diagram of another computing device according to another embodiment of the present application. As shown in fig. 3, the computing device includes a memory 40 and a processor 50.
Wherein the memory 40 has stored therein an application 41, a trusted hardware management component 42 and an operating system 43. Processor 50 is coupled to memory 40 for running application 41, trusted hardware management component 42, and operating system 43.
In this embodiment, in terms of physical implementation, the computing device may be a terminal device such as a personal computer, a smart phone, a tablet computer, or may be a server device such as a conventional server, a cloud host, or a virtual center. This embodiment is not limited thereto. The server device mainly includes a processor 50, a hard disk, a memory, a system bus, and the like, and is similar to a general computer architecture.
In practice, the trusted hardware interface may be configured on the computing device, and the trusted hardware 60 may be assembled onto the computing device through the trusted hardware interface. The trusted hardware interface can be one or more, and a single trusted hardware interface can support single type of trusted hardware, and of course, multiple types of trusted hardware can be compatible.
Based on this, in the present embodiment, at the hardware level, the computing device may support the assembly of multiple types of trusted hardware 60. The computing device may support assembled trusted hardware 60 including at least trusted platform module TPM (Trusted Platform Module) and trusted platform control module TPCM (Trusted Platform Control Module). Of course, the present embodiments are not so limited, and the computing device may also support the assembly of other types of trusted hardware 60, which is not intended to be exhaustive.
In this embodiment, multiple types of trusted hardware 60 may be simultaneously assembled on a computing device. For example, a TPM and a TPCM may be assembled simultaneously on a computing device. Of course, other types of trusted hardware 60 may also be provided on the computing device, which is not limited in this embodiment.
Based on the hardware architecture on the computing device, in this embodiment, the processor 50 may run an application 41 for:
Determining the type information of the trusted hardware expected to be called based on the type of the currently operated service;
generating a trusted service call request according to the type information of the trusted hardware expected to be called;
The trusted service invocation request is sent to the trusted hardware management component 42 for the trusted hardware management component 42 to invoke the operating system 43 in accordance with the trusted service invocation request to control, by the operating system 43, the target trusted hardware 60 matching the type information to respond to the trusted service invocation request.
The processor 50 may also run a trusted hardware management component 42 for:
Receiving a trusted service invocation request of the application program 41, wherein the trusted service invocation request comprises type information of trusted hardware expected to be invoked by the application program 41;
determining target trusted hardware 60 matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application 41;
The target trusted hardware 60 is invoked in response to a trusted service invocation request.
For ease of description, the following description will be made in terms of application 41 and trusted hardware management component 42, but it should be understood that the following technical details are actually generated by processor 50 running application 41 or trusted hardware management component 42.
For the application 41, the type information of the trusted hardware that is desired to be invoked may be determined according to the type of service it is running. Wherein the type of service may be characterized in terms of a service type code. In this embodiment, the format of the service type code is not limited, and the service type code may be a series of numbers, a combination of letters and numbers, or the like. The service type code may be carried in the program code of the service that the application 41 is running, although the application 41 may determine the type of service it is running from other sources. In this embodiment, the types of services executed by the application 41 include, but are not limited to, e-commerce services, financial services, game services, and the like.
Based on the type of service that the application 41 is running, the application 41 may determine the type information of the trusted hardware that it desires to invoke. The functions, components or interfaces and the like of the different types of trusted hardware are not identical, so that the trusted services provided by the different types of trusted hardware are not identical, and accordingly, the application 41 can determine the type information of the trusted hardware which is expected to be invoked according to the requirements of the running business on the trusted services. For example, if the type of service currently being run is a phone service, then it may be determined that a TPM call is desired. For another example, if the type of service currently being run is a financial service, it may be determined that it is desirable to invoke the TPCM.
After determining the type information of the trusted hardware that it is desired to invoke, the application 41 may generate a trusted hardware invocation request based on the type information of the trusted hardware that it is desired to invoke, and send the trusted hardware invocation request to the trusted hardware management component 42.
For trusted hardware management component 42, the type information of the trusted hardware currently on-line on the computing device may be detected upon receipt of a trusted service invocation request issued by application 41. The on-line state refers to a state that the trusted hardware is plugged into the trusted hardware plug-in interface and a subsequent in-use state. That is, while the trusted hardware remains in the plugged state of the trusted hardware plug interface described above, it may be determined that the trusted hardware is in an online state.
As mentioned previously, in this embodiment, multiple types of trusted hardware may be simultaneously assembled on the computing device, and thus the trusted hardware management component 42 will detect multiple trusted hardware in an online state. For example, when a TPM and a TPCM are concurrently assembled on a computing device, trusted hardware management component 42 may detect that trusted hardware on the computing device in an online state includes the TPM and the TPCM.
Based on this, the trusted hardware management component 42 may determine, from the plurality of trusted hardware in the online state, the target trusted hardware 60 that matches the type information based on the type information of the trusted hardware that the application 41 desires to invoke. For example, when the application 41 desires to invoke a TPM, the trusted hardware management component 42 may determine the TPM as the target trusted hardware 60. For another example, when the application 41 desires to invoke a TPCM, the trusted hardware management component 42 may determine the TPCM as the target trusted hardware 60.
In a special case, there may not be any trusted hardware in the online state among the plurality of trusted hardware on the computing device, where the trusted hardware management device may output an alarm prompt to supply the application 41 and/or the user of the computing device to obtain a situation that the computing device cannot provide the trusted service, and no longer perform the invoking operation on the trusted hardware, that is, no longer respond to the trusted service invoking request issued by the application 41. Of course, the trusted hardware management device may also select one trusted hardware from the plurality of trusted hardware in an online state as the target trusted hardware 60, where the selected target trusted hardware 60 may not meet the expectations of the application 41, and the trusted hardware management component 42 may continue to execute the call operation on the target trusted hardware 60 according to the selection result, or may send the selection result to the application 41, and execute the call operation on the target trusted hardware 60 after acquiring the determination of the application 41. The present embodiment is not limited in this regard.
Based on the determined target trusted hardware 60, the trusted hardware management component 42 may invoke the target trusted hardware 60 in response to the trusted service invocation request of the application 41.
In this embodiment, in the case where the application 41 issues a trusted service invocation request, the trusted hardware management component 42 on the computing device may detect multiple trusted hardware devices on the computing device that are online, and invoke the trusted hardware devices on demand as desired by the application 41. Accordingly, in this embodiment, the trusted hardware management component 42 on the computing device may support the invocation of multiple types of trusted hardware, which makes the types of trusted services that may be provided by the computing device rich, and may satisfy the diversified trusted service requirements of the application 41, so as to effectively improve the quality of the trusted service.
In the above or below embodiments, the trusted hardware management component 42 may select call information corresponding to the type information of the target trusted hardware 60 from a preset call information set; operating system 43 is invoked based on the invocation information to control the target trusted hardware 60 to respond to the trusted service invocation request by operating system 43.
The preset call information set contains call information corresponding to each of multiple types of trusted hardware which can be supported by the computing equipment. The call information includes, but is not limited to, a command transfer interface and a trusted hardware driver.
Based on the invocation information, the trusted hardware management component 42 may invoke the operating system 43, and the operating system 43 may control trusted hardware on the computing device that is currently online to provide trusted services for the application 41 under the invocation of the trusted hardware management component 42. The trusted services include, but are not limited to, integrity measurement and reporting services, authentication services, encryption and decryption services, and the like, which are not limited in this embodiment.
In this embodiment, the trusted hardware management component 42 may have the function of a dynamic link library. Accordingly, the trusted hardware management component 42 may generate a call command for the trusted hardware currently in an online state based on the trusted service invocation request.
In this embodiment, the trusted hardware management component 42, upon receiving the trusted service invocation request issued by the application 41, may refine the trusted service invocation request into invocation commands for the trusted hardware based on its dynamic link library function. For example, when the trusted invocation request is to obtain content from trusted hardware, the trusted hardware management server may refine the trusted invocation request into invocation commands to read the configuration of the trusted hardware, read the storage space of the trusted hardware, and so on.
In addition, the trusted hardware management component 42 may also have the processing function of selecting call information. If the trusted hardware management component 42 determines that the trusted hardware that the application 41 desires to call is a TPM, then call information matching the TPM may be selected from preset call information, where the selected call information will include at least the TPM command transfer interface (TPM Command Transmission Interface) and the TPM driver. If it is determined that the trusted hardware that the application 41 desires to call is a TPCM, call information matching the TPCM may be selected from preset call information, in which case the selected call information will include at least the TPCM command transfer interface (TPCM Command Transmission Interface) and the TPCM driver.
Further, the trusted hardware management component 42 may also have interaction functionality with the operating system 43. The trusted hardware management component 42 may transmit the foregoing call command to the operating system 43 through the command transmission interface, so that the operating system 43 may run the trusted hardware driver according to the call command to drive the trusted hardware currently in the online state to provide the application 41 with the trusted service.
For example, if it is determined that the target trusted hardware 60 is a TPM, the trusted hardware management component 42 may transmit the call instruction to the TPM resource manager through the TPM command transmission interface, and after performing a resource management operation such as ordering the call instruction, the TPM resource manager may transmit the call instruction to the operating system 43, and the operating system 43 may run the TPM driver to drive the TPM to provide the trusted service when receiving the call instruction.
For another example, if it is determined that the target trusted hardware 60 is a TPCM, the trusted hardware management component 42 may transmit the call instruction to the TPCM resource manager through the TPCM command transmission interface, where the TPCM resource manager may transmit the call instruction to the operating system 43 after performing a resource management operation such as ordering the call instruction, and the operating system 43 may operate the TPCM driver to drive the TPCM to provide the trusted service when receiving the call instruction.
In this embodiment, based on the type information of the trusted hardware that the trusted hardware management component 42 can expect to call, the call information used in the process of calling the trusted hardware is flexibly switched, so as to call the trusted hardware that meets the expectations of the application 41 to provide the trusted service for the application 41.
In the above or below embodiments, the trusted hardware management component 42 may query the current hardware information of the operating system 43; determining whether trusted hardware in an online state exists currently according to the current hardware information; if the type information exists, the type information of the trusted hardware currently in the online state is obtained from the current hardware information.
In this embodiment, the trusted hardware management component 42 may query the current hardware information of the operating system 43 through a query interface provided by the operating system 43. The current hardware information of the operating system 43 includes information of trusted hardware currently on the computing device, and of course, includes information of other hardware running on the computing device, which is not described in detail herein because it is not related to the present technical solution. In addition, the current hardware information of the operating system 43 may be obtained by the operating system 43 performing hardware detection on the computing device according to an existing hardware detection scheme, which is not described in detail herein.
In practical applications, when the computing device is equipped with the TPM and the TPCM, the current hardware information of the operating system 43 will include the information of the TPM; when the TPCM is assembled on the computing device, the current hardware information of the operating system 43 will contain the information of the TPCM; and when trusted hardware is not assembled on the computing device, the current hardware information of operating system 43 will not contain any information of the trusted hardware. Accordingly, the trusted hardware management component 42 may determine whether trusted hardware is currently being deployed on the computing device based on current hardware information of the operating system 43.
If it is determined that trusted hardware currently in an online state exists on the computing device, the type information of the trusted hardware currently in an online state may be read from the current hardware information of the operating system 43. Based on multiple types of trusted hardware being concurrently assembled on the computing device, the trusted hardware management component 42 may read from the current hardware information of the operating system 43 type information for the multiple trusted hardware in an online state.
Of course, the implementation manner of detecting the type information of the trusted hardware currently in the online state is not limited thereto, and in this embodiment, other implementation manners may also be used to detect the type information of the trusted hardware currently in the online state. For example, the trusted hardware management component 42 may detect heartbeat information on the aforementioned trusted hardware interface and, if heartbeat information is detected, obtain type information for the trusted hardware that is currently online from the heartbeat information. This embodiment is not limited thereto.
Fig. 4 is a flow chart of another trusted service method according to another embodiment of the present application. As shown in fig. 4, the method includes:
400. Receiving a trusted service call request of an application program, wherein the trusted service call request comprises type information of trusted hardware expected to be called by the application program;
401. determining target trusted hardware matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application program;
402. The target trusted hardware is invoked in response to a trusted service invocation request.
In an alternative embodiment, step 402 includes:
selecting call information corresponding to the type information of the target trusted hardware from a preset call information set;
the operating system is invoked based on the invocation information to control the target trusted hardware to respond to the trusted service invocation request by the operating system.
In an alternative embodiment, the call information includes a command transmission interface and a trusted hardware driver; the steps of calling the operating system based on the calling information to control the target trusted hardware to respond to the trusted service calling request through the operating system include:
Generating a call command for the target trusted hardware according to the trusted service call request;
And transmitting the calling command to the operating system through the command transmission interface so that the operating system can operate the trusted hardware driver according to the calling command to drive the target trusted hardware to provide the trusted service for the application program.
In an alternative embodiment, the target trusted hardware is a trusted platform module TPM or a trusted platform control module TPCM.
It should be noted that, for the technical details mentioned or not mentioned in the embodiments of the trusted service method, reference should be made to the description of the trusted hardware management component in the embodiments of the computing device, which is not described in detail herein for the sake of brevity, but this should not be construed as a loss of the protection scope of the present application.
Accordingly, embodiments of the present application also provide a computer readable storage medium storing a computer program, where the computer program when executed is capable of implementing the steps of the method embodiments described above that may be performed by a trusted hardware management component.
Fig. 5 is a flow chart of a trusted service method according to another embodiment of the present application. As shown in fig. 5, the method includes:
500. generating a trusted service call request according to the type information of the trusted hardware expected to be called;
501. and sending the trusted service call request to the trusted hardware management component, so that the trusted hardware management component can call the operating system according to the trusted service call request, and the trusted hardware management component can respond to the trusted service call request by controlling the target trusted hardware matched with the type information through the operating system.
In an alternative embodiment, the trusted hardware that is desired to be invoked is a trusted platform module TPM or a trusted platform control module TPCM.
In an alternative embodiment, step 500 includes:
if the type of the currently running service is a mobile service, determining that the TPM is expected to be invoked.
In an alternative embodiment, step 500 includes:
if the type of the currently operated business is a financial business, determining that the TPCM is expected to be invoked.
It should be noted that, for the technical details mentioned or not mentioned in the embodiments of the trusted service method, reference should be made to the description of the application program in the embodiments of the computing device, which is not described in detail herein for the sake of brevity, but this should not be construed as a loss of the protection scope of the present application.
It should be noted that, in some of the above embodiments and the flows described in the drawings, a plurality of operations appearing in a specific order are included, but it should be clearly understood that the operations may be performed out of the order in which they appear herein or performed in parallel, the sequence numbers of the operations such as 201, 202, etc. are merely used to distinguish between the various operations, and the sequence numbers themselves do not represent any order of execution. In addition, the flows may include more or fewer operations, and the operations may be performed sequentially or in parallel.
Accordingly, the present application also provides a computer readable storage medium storing a computer program, where the computer program is executed to implement the steps executable by an application program in the above method embodiments.
It will be appreciated by those skilled in the art that embodiments of the present invention may be provided as a method, system, or computer program product. Accordingly, the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
The foregoing is merely exemplary of the present application and is not intended to limit the present application. Various modifications and variations of the present application will be apparent to those skilled in the art. Any modification, equivalent replacement, improvement, etc. which come within the spirit and principles of the application are to be included in the scope of the claims of the present application.
Claims (15)
1. A trusted service method, comprising:
Receiving a trusted service call request sent by an application program;
detecting type information of trusted hardware currently in an online state;
Selecting call information corresponding to the type information of the trusted hardware currently in an online state from a preset call information set, wherein the call information comprises a command transmission interface and a trusted hardware driver;
and calling an operating system based on the calling information so as to control the trusted hardware currently in an online state to respond to the trusted service calling request through the operating system.
2. The method of claim 1, wherein detecting the type information of the trusted hardware currently in an online state comprises:
Inquiring current hardware information of an operating system;
Determining whether trusted hardware in an online state exists currently according to the current hardware information;
and if the type information exists, acquiring the type information of the trusted hardware currently in the online state from the current hardware information.
3. The method of claim 1, wherein the trusted hardware currently in an online state is a trusted platform module, TPM, or a trusted platform control module, TPCM.
4. The method of claim 1, wherein invoking an operating system based on the invocation information to control the trusted hardware currently in an online state by the operating system to respond to the trusted service invocation request comprises:
Generating a calling command for the trusted hardware currently in an online state according to the trusted service calling request;
and transmitting the calling command to an operating system through the command transmission interface so that the operating system can operate the trusted hardware driver according to the calling command to drive the trusted hardware currently in an online state to provide trusted service for the application program.
5. A computing device comprising a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for running the trusted hardware management component for:
Receiving a trusted service invocation request sent by the application program;
detecting type information of trusted hardware currently in an online state;
Selecting call information corresponding to the type information of the trusted hardware currently in an online state from a preset call information set, wherein the call information comprises a command transmission interface and a trusted hardware driver;
and calling the operating system based on the calling information so as to control the trusted hardware currently in an online state to respond to the trusted service calling request through the operating system.
6. A trusted service method, comprising:
Receiving a trusted service call request of an application program, wherein the trusted service call request comprises type information of trusted hardware expected to be called by the application program;
Determining target trusted hardware matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application program;
selecting call information corresponding to the type information of the target trusted hardware from a preset call information set, wherein the call information comprises a command transmission interface and a trusted hardware driver;
and calling an operating system based on the calling information so as to control the target trusted hardware to respond to the trusted service calling request through the operating system.
7. The method of claim 6, wherein the call information includes a command transfer interface and a trusted hardware driver; the calling the operating system based on the calling information to control the target trusted hardware to respond to the trusted service calling request through the operating system comprises the following steps:
generating a call command for the target trusted hardware according to the trusted service call request;
And transmitting the calling command to an operating system through the command transmission interface so that the operating system can operate the trusted hardware driver according to the calling command to drive the target trusted hardware to provide trusted service for the application program.
8. The method of claim 6, wherein the target trusted hardware is a trusted platform module, TPM, or a trusted platform control module, TPCM.
9. A trusted service method, comprising:
Determining the type information of the trusted hardware expected to be called based on the type of the currently operated service;
Generating a trusted service call request according to the type information of the trusted hardware expected to be called;
the trusted service call request is sent to a trusted hardware management component, so that the trusted hardware management component calls an operating system according to the trusted service call request, and the target trusted hardware matched with the type information is controlled by the operating system to respond to the trusted service call request;
The trusted hardware management component selects calling information corresponding to the type information from a preset calling information set, wherein the calling information comprises a command transmission interface and a trusted hardware driver; and calling an operating system based on the calling information.
10. The method of claim 9, wherein the trusted hardware desired to be invoked is a trusted platform module, TPM, or a trusted platform control module, TPCM.
11. The method of claim 9, wherein determining the type information of the trusted hardware that is desired to be invoked based on the type of the currently running service comprises:
if the type of the currently operated service is a mobile service, determining that the TPM is expected to be invoked.
12. The method of claim 9, wherein determining the type information of the trusted hardware that is desired to be invoked based on the type of the currently running service comprises:
and if the type of the currently operated business is a financial business, determining that the TPCM is expected to be invoked.
13. A computing device comprising a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for running the trusted hardware management component for:
Receiving a trusted service call request of an application program, wherein the trusted service call request comprises type information of trusted hardware expected to be called by the application program;
Determining target trusted hardware matched with the type information from a plurality of trusted hardware in an online state according to the type information of the trusted hardware expected to be called by the application program;
selecting call information corresponding to the type information of the target trusted hardware from a preset call information set, wherein the call information comprises a command transmission interface and a trusted hardware driver;
and calling an operating system based on the calling information so as to control the target trusted hardware to respond to the trusted service calling request through the operating system.
14. A computing device comprising a memory and a processor;
the memory stores an application program, a trusted hardware management component and an operating system;
the processor is coupled to the memory for executing the application for:
Determining the type information of the trusted hardware expected to be called based on the type of the currently operated service;
Generating a trusted service call request according to the type information of the trusted hardware expected to be called;
the trusted service call request is sent to a trusted hardware management component, so that the trusted hardware management component calls an operating system according to the trusted service call request, and the target trusted hardware matched with the type information is controlled by the operating system to respond to the trusted service call request;
The trusted hardware management component selects calling information corresponding to the type information from a preset calling information set, wherein the calling information comprises a command transmission interface and a trusted hardware driver; and calling an operating system based on the calling information.
15. A computer-readable storage medium storing computer instructions that, when executed by one or more processors, cause the one or more processors to perform the trusted service method of any of claims 1-4 or 6-12.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910419223.4A CN111967010B (en) | 2019-05-20 | 2019-05-20 | Trusted service method, trusted service device, trusted service equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201910419223.4A CN111967010B (en) | 2019-05-20 | 2019-05-20 | Trusted service method, trusted service device, trusted service equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111967010A CN111967010A (en) | 2020-11-20 |
| CN111967010B true CN111967010B (en) | 2024-05-24 |
Family
ID=73358391
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201910419223.4A Active CN111967010B (en) | 2019-05-20 | 2019-05-20 | Trusted service method, trusted service device, trusted service equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111967010B (en) |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183413A (en) * | 2007-12-14 | 2008-05-21 | 西安电子科技大学 | Architecture of trusted platform module and method for providing service thereof |
| CN101226577A (en) * | 2008-01-28 | 2008-07-23 | 南京大学 | Method for protecting microkernel OS integrality based on reliable hardware and virtual machine |
| CN101957900A (en) * | 2010-10-26 | 2011-01-26 | 中国航天科工集团第二研究院七○六所 | Credible virtual machine platform |
| CN102063591A (en) * | 2011-01-07 | 2011-05-18 | 北京工业大学 | Methods for updating PCR (Platform Configuration Register) reference values based on trusted platform |
| CN102063592A (en) * | 2011-01-07 | 2011-05-18 | 北京工业大学 | Credible platform and method for controlling hardware equipment by using same |
| CN104903865A (en) * | 2012-12-03 | 2015-09-09 | 国际商业机器公司 | Restoring a previous version of a virtual machine image |
| CN106649164A (en) * | 2016-12-29 | 2017-05-10 | 南威软件股份有限公司 | Hardware interface management method |
| CN107066885A (en) * | 2016-10-11 | 2017-08-18 | 深圳市华威世纪科技股份有限公司 | Cross-platform credible middleware realizes system and implementation method |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8259948B2 (en) * | 2007-12-29 | 2012-09-04 | Intel Corporation | Virtual TPM key migration using hardware keys |
| US9870475B2 (en) * | 2014-06-25 | 2018-01-16 | Intel Corporation | Hardware configuration reporting systems |
-
2019
- 2019-05-20 CN CN201910419223.4A patent/CN111967010B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101183413A (en) * | 2007-12-14 | 2008-05-21 | 西安电子科技大学 | Architecture of trusted platform module and method for providing service thereof |
| CN101226577A (en) * | 2008-01-28 | 2008-07-23 | 南京大学 | Method for protecting microkernel OS integrality based on reliable hardware and virtual machine |
| CN101957900A (en) * | 2010-10-26 | 2011-01-26 | 中国航天科工集团第二研究院七○六所 | Credible virtual machine platform |
| CN102063591A (en) * | 2011-01-07 | 2011-05-18 | 北京工业大学 | Methods for updating PCR (Platform Configuration Register) reference values based on trusted platform |
| CN102063592A (en) * | 2011-01-07 | 2011-05-18 | 北京工业大学 | Credible platform and method for controlling hardware equipment by using same |
| CN104903865A (en) * | 2012-12-03 | 2015-09-09 | 国际商业机器公司 | Restoring a previous version of a virtual machine image |
| CN107066885A (en) * | 2016-10-11 | 2017-08-18 | 深圳市华威世纪科技股份有限公司 | Cross-platform credible middleware realizes system and implementation method |
| CN106649164A (en) * | 2016-12-29 | 2017-05-10 | 南威软件股份有限公司 | Hardware interface management method |
Non-Patent Citations (1)
| Title |
|---|
| 云环境下可信服务器平台关键技术研究;刘刚;吴保锡;张尧;;信息安全研究;20170405(04);全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111967010A (en) | 2020-11-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3668009B1 (en) | Network service lifecycle management method and device | |
| EP3432549A1 (en) | Method and apparatus for processing user requests | |
| EP3618352B1 (en) | Virtual machine management | |
| CN110909373B (en) | Access control method, equipment, system and storage medium | |
| CN107104923B (en) | Account binding and service processing method and device | |
| CN110442610A (en) | The method, apparatus of load balancing calculates equipment and medium | |
| CN107861691B (en) | Load balancing method and device of multi-control storage system | |
| CN113467970B (en) | Cross-security-area resource access method in cloud computing system and electronic equipment | |
| CN114363334B (en) | Cloud system, network configuration method, device and equipment of cloud desktop virtual machine | |
| EP4006725A1 (en) | Virtual machine migration processing and strategy generation method, apparatus and device, and storage medium | |
| CN112217873B (en) | Device sharing method, related device and storage medium | |
| CN113296896B (en) | Distributed transaction processing method, device and equipment | |
| CN111967010B (en) | Trusted service method, trusted service device, trusted service equipment and storage medium | |
| US11071151B2 (en) | Methods and apparatuses for connecting a wireless access point through an application in a user equipment | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN108920277B (en) | Service execution system, method and device and service isolation system | |
| US10742802B2 (en) | Methods and devices for verifying a communication number | |
| CN114513535A (en) | Data transmission system, method, device and equipment | |
| CN111814014B (en) | Information interaction method, device and storage medium | |
| CN111435320B (en) | Data processing method and device | |
| CN109246034B (en) | Method and equipment for allocating flow resources for mobile equipment | |
| CN113051143A (en) | Detection method, device, equipment and storage medium for service load balancing server | |
| CN112749149A (en) | Database switching method and device | |
| CN112291287A (en) | Cloud platform-based containerized application network flow control method and device and storage medium | |
| CN116662623B (en) | Method, device, equipment and medium for accessing menu information |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |