Method and system for service hot upgrade of iterative cipher machine

By adopting an iterative hot upgrade method for cryptographic machines, and utilizing business firmware virtual machines and cryptographic card drivers, the problems of limited application scope and multi-version management during the upgrade process of cryptographic devices are solved, achieving seamless and efficient upgrades, and improving system flexibility and user experience.

CN118916064APending Publication Date: 2024-11-08BEIJING SANSEC TECH DEV
View PDF 6 Cites 0 Cited by

Patent Information

Application Number
CN202411405149.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-10
Publication Date
2024-11-08

AI Technical Summary

Technical Problem

Existing technologies have limitations in application scope during the upgrade of cryptographic devices, making it difficult to adapt to the requirements of high security, low interruption rate and coexistence of multiple versions, and also resulting in high administrator dependence.

Method used

An iterative cryptographic machine service hot upgrade method is adopted, which dynamically loads multiple versions of business firmware through a business firmware virtual machine. Combining encryption and signature verification, it supports the coexistence of multiple versions and completes the encryption operation through the cryptographic card driver. The client application does not need to be restarted during the upgrade process.

Benefits of technology

It enables the upgrading of cryptographic devices without service interruption, supports the coexistence of multiple versions, improves the flexibility of upgrades and user experience, and reduces the workload of operation and maintenance.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118916064A_ABST
    Figure CN118916064A_ABST
Patent Text Reader

Abstract

The invention discloses an iterative cipher machine service hot upgrade method and system, and the method comprises the steps: dynamically loading a plurality of versions of business firmware in a business firmware virtual machine, and receiving an access request of a client containing the version information of the requested business firmware; performing encryption and signature verification on the uploaded new firmware through the business firmware management program, loading the firmware to a business firmware virtual machine after the verification is passed, and calling the business firmware of the corresponding version according to the access request or a preset strategy; calling the password card through the password card driving program to complete encryption operation; in the upgrading process, the client application program communicates with the password device server, the upgrading operation can be completed without restarting the application, and the whole process has no perception on the client application. According to the method, the service is not interrupted in the upgrading process, multi-version password service coexistence is supported, the upgrading flexibility is improved, more upgrading scene requirements are met, the user experience is improved, and the operation and maintenance workload is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of information security technology of cryptographic device clusters, and more specifically to a method and system for iterative cryptographic machine service hot upgrade. Background Art

[0002] At present, in the field of information security, cryptographic devices such as cryptographic machines, encryption machines, SSL VPN gateways, and financial data cryptographic machines are the core technologies to ensure data security. However, in the process of upgrading traditional cryptographic services, it is often necessary to stop the service, resulting in system interruption or restart. This not only affects the user experience, but also increases the workload of operation and maintenance.

[0003] The emergence of hot upgrade technology has alleviated this problem. Hot upgrade refers to updating the system without interrupting the service. The client does not need to restart the application, and the upgrade process is transparent to the user. However, existing hot upgrade technologies are mostly used in cloud computing environments or the financial field, mainly solving the upgrade problem of multiple services or process groups. Although these solutions are effective in their respective fields, they do not fully consider the special needs of cryptographic services, especially the coexistence and flexible management of multiple versions of cryptographic services.

[0004] Although the existing technology can achieve hot upgrade, it still has the following problems:

[0005] In different scenarios, the application scope of existing technologies is limited, and it is difficult to adapt to the requirements of cryptographic equipment for high security, low interruption rate and coexistence of multiple versions.

[0006] Existing solutions have deficiencies in multi-version management and policy flexibility, and the upgrade process is highly dependent on administrators. Summary of the invention

[0007] In view of this, the present invention provides a method and system for iterative hot upgrade of cryptographic machine services, which can solve the problem of limited application scope of cryptographic devices in different scenarios. The present invention can upgrade the cryptographic service without stopping the service, support the coexistence of multiple versions of cryptographic services, and flexibly configure and manage different versions of cryptographic firmware through the business firmware virtual machine.

[0008] In order to achieve the above object, the present invention adopts the following technical solution:

[0009] In a first aspect, an embodiment of the present invention provides an iterative cryptographic machine service hot upgrade method, which is applied to information interaction between a client and a cryptographic device server, wherein the cryptographic device server configures a business firmware virtual machine; the specific steps include:

[0010] S10, dynamically loading multiple versions of business firmware in the business firmware virtual machine, including: an old version of business firmware and a new version of business firmware; the business firmware is used to process business logic;

[0011] S20, receiving an access request from a client application, wherein the access request includes requested service firmware version information;

[0012] S30, encrypting and signing the uploaded new firmware through the business firmware management program, loading the firmware into the business firmware virtual machine after the verification is passed, and calling the corresponding version of the business firmware according to the client's access request or preset policy;

[0013] S40, the corresponding version of the business firmware is selected, and the cryptographic card is called by the cryptographic card driver to complete the encryption operation;

[0014] S50. During the upgrade process, the client application communicates with the cryptographic device server, and the upgrade operation can be completed without restarting the application. The client application is unaware of the entire process.

[0015] Furthermore, the step S10 also includes: when the service firmware virtual machine storage space reaches an upper limit, automatically uninstalling the oldest version of the service firmware to release space for loading new firmware.

[0016] Furthermore, the step S20 also includes: when the access request of the client does not specify a firmware version, automatically selecting a default firmware version for processing according to a preset policy.

[0017] Furthermore, the step S30 further includes:

[0018] According to the upgrade requirements, the business firmware management program decides whether to retain or uninstall the old version of the firmware according to the preset policy; or modifies the preset policy for the operation of the business firmware.

[0019] In a second aspect, an embodiment of the present invention further provides a system for iterative cryptographic machine service hot upgrade, comprising: a client, a cryptographic device server, and a cryptographic card;

[0020] Wherein, the cryptographic device server includes: a business firmware virtual machine, a business firmware management module and a cryptographic card driver;

[0021] The business firmware virtual machine is used to dynamically load multiple versions of business firmware, including: old versions of business firmware and new versions of business firmware; the business firmware is used to process business logic;

[0022] The client is used to send an access request of the client application to the cryptographic device server; the access request includes the requested service firmware version information;

[0023] The business firmware management module is used to encrypt and verify the signature of the uploaded new firmware. After the verification is passed, the firmware is loaded into the business firmware virtual machine, and the corresponding version of the business firmware is called according to the client's access request or preset policy;

[0024] The password card driver module is used to call the password card to complete the encryption operation according to the selected corresponding version of the service firmware;

[0025] During the upgrade process, the client application communicates with the password device server, and the upgrade operation can be completed without restarting the application. The entire process is unaware of the client application.

[0026] Furthermore, the business firmware virtual machine is also used to automatically uninstall the oldest version of the business firmware when the business firmware virtual machine storage space reaches an upper limit to release space for loading new firmware.

[0027] Furthermore, the password device server also includes:

[0028] The firmware operation policy module is used to automatically select a default firmware version for processing according to a preset policy when the client's access request does not specify a firmware version.

[0029] Furthermore, the service firmware management module is also used to decide whether to retain or uninstall the old version of the firmware according to the upgrade requirements through the service firmware management program according to the preset policy; or to modify the preset policy for the operation of the service firmware.

[0030] It can be seen from the above technical solution that compared with the prior art, the present invention has the following advantages:

[0031] The service is not interrupted during the upgrade process and supports the coexistence of multiple versions of cryptographic services, which improves the flexibility of upgrades and meets the needs of more upgrade scenarios. At the same time, it improves the user experience of the cryptographic service upgrade process and reduces the workload of operation and maintenance. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.

[0033] Figure 1 A flow chart of the method for hot upgrading of iterative cryptographic machine services provided by the present invention.

[0034] Figure 2 This is a schematic diagram of the iterative cryptographic machine service hot upgrade system provided by the present invention. DETAILED DESCRIPTION

[0035] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions 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 are within the scope of protection of the present invention.

[0036] Embodiment 1:

[0037] The embodiment of the present invention discloses a method for hot upgrading of iterative cryptographic machine services. Hot upgrading means updating the system without stopping the service, so that users and application programs will not feel the impact of the upgrading process.

[0038] The core concept of the present invention is to manage and run multiple versions of cryptographic firmware through a "virtual machine". Each firmware contains business logic, and the virtual machine will select and run the appropriate firmware version according to the version requested by the client. When the business firmware actually performs cryptographic operations, it calls the cryptographic card through the cryptographic card driver to complete the operation. The administrator can dynamically load or unload the firmware to ensure that the system can flexibly support the coexistence of multiple versions.

[0039] When updating the firmware, administrators can upload the new firmware and configure the upgrade policy without restarting the network service. Client applications can use the latest firmware version without knowing it. This makes the entire upgrade process efficient and imperceptible to users, reduces the workload of operation and maintenance, and improves the flexibility of the system.

[0040] The invention provides an iterative cryptographic machine service hot upgrade method, which is applied to the information interaction between the client and the cryptographic device server, wherein the cryptographic device server is configured with a business firmware virtual machine; Figure 1 As shown, the specific steps include:

[0041] S10, dynamically loading multiple versions of business firmware in the business firmware virtual machine, including: an old version of the business firmware and a new version of the business firmware; the business firmware is used to process business logic; when the storage space of the business firmware virtual machine reaches an upper limit, the oldest version of the business firmware is automatically uninstalled to free up space for loading the new firmware;

[0042] S20, receiving an access request from a client application, wherein the access request includes requested service firmware version information; when the client access request does not specify a firmware version, automatically selecting a default firmware version for processing according to a preset policy.

[0043] S30. Encrypt and verify the signature of the uploaded new firmware through the business firmware management program. After the verification is passed, the firmware is loaded into the business firmware virtual machine, and the corresponding version of the business firmware is called according to the client's access request or preset policy; according to the upgrade requirements, the business firmware management program decides whether to retain or uninstall the old version of the firmware according to the preset policy; or modifies the preset policy for the operation of the business firmware.

[0044] S40, the corresponding version of the business firmware is selected, and the cryptographic card is called by the cryptographic card driver to complete the encryption operation;

[0045] S50. During the upgrade process, the client application communicates with the cryptographic device server, and the upgrade operation can be completed without restarting the application. The client application is unaware of the entire process.

[0046] Through the iterative cryptographic machine service hot upgrade method of the present invention, the upgrade process no longer interrupts the service, which significantly improves the user experience. At the same time, the method supports the coexistence of multiple versions of cryptographic firmware, meeting the needs of multiple scenarios. Administrators can flexibly configure upgrade strategies, greatly reducing the complexity and workload of system operation and maintenance. A simplified cryptographic machine service hot upgrade scenario will be used as an example to demonstrate the actual implementation steps of the process.

[0047] like Figure 2 As shown, the invention provides an iterative cryptographic machine service hot upgrade method, involving the following components:

[0048] Password card: performs core encryption operations.

[0049] Password card driver: connects the password card with the business firmware and is responsible for calling the password card to perform encryption operations.

[0050] Business firmware: contains cryptographic algorithms and business logic, which can be loaded or unloaded dynamically.

[0051] Business firmware manager: used to upload, configure, manage business firmware, and determine which firmware is available.

[0052] Business firmware running virtual machine: responsible for managing and running multiple versions of business firmware without stopping services.

[0053] Firmware operation policy storage module: saves the firmware operation policy to ensure the flexibility of upgrade.

[0054] Network service module: communicates with the client, processes requests and forwards them to the business firmware virtual machine.

[0055] The relationship between the components is described as follows:

[0056] The business firmware virtual machine can dynamically load or unload business firmware. The business firmware virtual machine selects which firmware to call to complete the operation according to the firmware version and firmware operation policy specified in the client request. The administrator loads or unloads the business firmware through the business firmware management program. The administrator can also configure the firmware operation policy through the business firmware management program. The method of the present invention encrypts and signs the business firmware to ensure the confidentiality and integrity of the firmware. The network service module receives the request of the client application. After receiving the request, the network service module communicates with the business firmware operation virtual machine through the system communication bus. When the business firmware actually performs cryptographic operations, it calls the cryptographic card through the cryptographic card driver to complete it. The business firmware only contains business logic, and the basic core key operation is still completed in the cryptographic card.

[0057] by Figure 2 For example, the business firmware running virtual machine supports the operation and management of 4 business firmwares. The business firmware storage space is limited and cannot support an unlimited number of firmwares running. Figure 2 As shown, the firmware is fully loaded with 4. If you want to load a new firmware, you need to uninstall one of them. Generally, uninstall the oldest version, such as Figure 2 As shown, version 1 of the business firmware is uninstalled. The client application can specify which version of the firmware program to use in the configuration file. The firmware version information is sent to the network service module along with the request data. The administrator can also configure the firmware operation policy through the business firmware management program, such as only allowing the use of the latest version of the firmware program. In this way, even if the client specifies the version, only the latest version of the firmware can be used for cryptographic operations, and the firmware reset configuration takes precedence.

[0058] The service firmware update process is described as follows:

[0059] 1. R&D personnel complete demand development, compile and package business firmware, encrypt and sign the firmware, and release business firmware;

[0060] 2. The operation and maintenance administrator downloads the new business firmware and uses the business firmware management program to upload the business firmware;

[0061] 3. The business firmware management program decrypts the uploaded business firmware and verifies the signature. After the decryption and signature verification are passed, the business firmware management program loads the new business firmware into the business firmware running virtual machine firmware storage area;

[0062] 4. Based on the actual upgrade requirements, the operation and maintenance administrator decides whether to delete or retain the old version of the firmware, or to modify the business firmware operation strategy and decide which business firmware can be called;

[0063] The client application communicates with the network service module. The upgrade process does not restart the network service module, and the client application does not need to be restarted, so the upgrade process is imperceptible to the user.

[0064] The business call process is described as follows:

[0065] 1. Modify the client firmware version configuration to determine which version of the business firmware is used for operation, or do not configure it and let the firmware operation strategy determine which version of the firmware is used;

[0066] 2. SDK reads the version information of the firmware version configuration. When the application APP makes a call request, SDK automatically adds the firmware version information to the request;

[0067] 3. The network service module receives the request from the client application and forwards it to the business firmware running virtual machine through the system communication bus.

[0068] 4. The business firmware running virtual machine calls the corresponding version of the business firmware according to the firmware version and firmware running strategy in the request;

[0069] 5. When the business firmware performs cryptographic operations, it calls the cryptographic card through the cryptographic card driver to complete the operation. After the operation is completed, the result is returned to the client application through the original path;

[0070] For example, suppose there is a banking system that relies on a cryptographic machine for data encryption and decryption operations. Currently the system is running version 1 of the cryptographic service firmware. The system needs to be upgraded to version 2 of the cryptographic firmware to introduce a new encryption algorithm without interrupting ongoing transactions in the process.

[0071] Specific steps for hot upgrade:

[0072] 1. Prepare new firmware

[0073] R&D staff: R&D staff first developed a new version 2 cryptographic firmware based on business needs, adding a stronger encryption algorithm. After development, the R&D staff packaged the firmware and encrypted and signed it with a dedicated key to ensure the security and integrity of the firmware.

[0074] 2. Upload new firmware

[0075] Operation and maintenance administrator: The administrator logs in to the system and uses the business firmware manager to upload version 2 of the cryptographic firmware to the system. During the upload process, the business firmware manager decrypts the firmware and verifies the signature to ensure that it has not been tampered with.

[0076] 3. Load new firmware

[0077] Business firmware manager: After verification, the business firmware manager loads version 2 firmware into the business firmware virtual machine in the system. The virtual machine supports the coexistence of multiple versions, so at this time, both version 1 and version 2 of the cryptographic firmware exist in the system.

[0078] 4. Set the upgrade strategy

[0079] Administrator: The administrator uses the Business Firmware Manager to configure operational policies to determine how the new firmware is used. In this example, the administrator decides:

[0080] Existing client transactions continue to use version 1 firmware to ensure that service is not affected during the upgrade process.

[0081] All new client transactions will use version 2 firmware by default and benefit from the new encryption algorithm.

[0082] 5. Continue normal service

[0083] Client Application: The client application continues to operate normally and issues encrypted requests through the network service module. The current request is based on different strategies:

[0084] Old transaction requests (already in transaction) still use version 1 firmware.

[0085] New transactions require firmware version 2.

[0086] The network service module passes the request to the business firmware virtual machine through the system communication bus, and the virtual machine calls the corresponding version of the firmware according to the version information in the request and the configured policy.

[0087] 6. Uninstall old firmware (optional)

[0088] Administrator: After a period of time, the administrator decides to uninstall the version 1 firmware because all clients have already transitioned to version 2. Through the business firmware management program, the administrator uninstalls the version 1 firmware to free up system resources.

[0089] 7. No interruption during the whole process

[0090] During the entire upgrade process, the network service module and client application do not need to be restarted, the client will not feel any impact, and all upgrades are imperceptible to users.

[0091] In this embodiment, it can be seen that the following technical advantages are achieved:

[0092] Coexistence of multiple versions: The business firmware virtual machine can support loading multiple versions of firmware at the same time, ensuring that there is no need to stop services during upgrades.

[0093] Policy flexibility: Administrators can flexibly configure operation policies through the firmware management program to ensure smooth service transition.

[0094] Security: The firmware upload and loading process is encrypted and signed to ensure the integrity and confidentiality of the firmware.

[0095] Automatically uninstall the oldest version: After a new version of firmware is uploaded and runs for a period of time, the administrator can choose to uninstall the old version of firmware to free up storage space.

[0096] The key to hot upgrade is smooth transition and coexistence of multiple versions. During the whole process, the service is not interrupted, the client application does not need to be restarted, and the user experience is not affected.

[0097] Embodiment 2:

[0098] Based on the same inventive concept, the present invention also provides a system for iterative cryptographic machine service hot upgrade, including: a client, a cryptographic device server and a cryptographic card; and the method of Example 1 can be executed.

[0099] Among them, the cryptographic device server includes: a business firmware virtual machine, a business firmware management module and a cryptographic card driver module;

[0100] The business firmware virtual machine is used to dynamically load multiple versions of business firmware, including: old versions of business firmware and new versions of business firmware; the business firmware is used to process business logic;

[0101] The client is used to send an access request of the client application to the cryptographic device server; the access request includes the requested service firmware version information;

[0102] The service firmware management module is used to encrypt and verify the signature of the uploaded new firmware. After the verification is passed, the firmware is loaded into the service firmware virtual machine, and the corresponding version of the service firmware is called according to the client's access request or preset policy. It is also used to decide whether to retain or uninstall the old version of the firmware according to the preset policy through the service firmware management program according to the upgrade requirements; or to modify the preset policy for the operation of the service firmware.

[0103] The password card driver module is used to call the password card to complete the encryption operation according to the selected version of the business firmware; during the upgrade process, the client application communicates with the password device server, and the upgrade operation can be completed without restarting the application. The entire process is unaware of the client application.

[0104] In addition, the business firmware virtual machine is also used to automatically uninstall the oldest version of the business firmware when the business firmware virtual machine storage space reaches the upper limit to release space for loading new firmware.

[0105] In one embodiment, the cryptographic device server further includes:

[0106] The firmware operation policy module is used to automatically select a default firmware version for processing according to a preset policy when the client's access request does not specify a firmware version.

[0107] Taking the iterative upgrade of the service firmware of the cryptographic device server as an example, the specific upgrade includes the following:

[0108] Step 1: Initialize the business firmware virtual machine

[0109] First, configure the business firmware virtual machine on the cryptographic device server. The virtual machine is responsible for dynamically loading and unloading different versions of business firmware, and automatically unloading the oldest version of firmware when storage space is limited. During initialization, the virtual machine has pre-loaded several firmware versions, such as version 1.0, 1.1, and 1.2.

[0110] Step 2: Load the new version of the service firmware

[0111] The R&D staff developed and packaged a new version of the business firmware version 2.0, which uses a more advanced encryption algorithm. Before uploading the new firmware, the R&D staff encrypted and signed the firmware to ensure the security of the firmware during transmission and deployment.

[0112] The operation and maintenance administrator uploads the version 2.0 firmware to the cryptographic device server through the business firmware management program. During the upload process, the management program will first decrypt and verify the signature of the firmware to ensure the integrity and authenticity of the firmware. After the verification is passed, the business firmware management program loads the firmware into the business firmware virtual machine.

[0113] Step 3: Dynamically uninstall the oldest version of firmware

[0114] Since the virtual machine has limited firmware storage space, it has already stored versions 1.0, 1.1, and 1.2, and cannot directly load the new firmware version 2.0. At this time, the virtual machine will automatically uninstall the oldest version 1.0 firmware according to the preset uninstall policy to free up space and ensure that version 2.0 can be successfully loaded.

[0115] Step 4: Receive client request and select firmware

[0116] The client application initiates a service request through the SDK, which contains the firmware version number. If the client specifies a version, such as requesting version 1.2, the network service module will forward the request to the service firmware virtual machine, which will call the corresponding firmware according to the firmware version number in the request.

[0117] If the client does not specify a version, the system selects the latest version of the firmware according to the preset policy. For example, when the client does not specify a version, the system can prioritize the use of version 2.0 firmware to ensure the use of the most advanced encryption algorithm.

[0118] Step 5: Business firmware processes the request

[0119] In the business firmware virtual machine, the selected business firmware will be responsible for processing the client's business logic. The actual encryption operation is completed by the business firmware calling the password card through the password card driver. For example, version 2.0 firmware may need to call encryption keys of different lengths or use different encryption algorithms. The password card driver calls the password card to adjust the key length and operation mode according to the encryption requirements of the firmware, and finally completes the encryption operation.

[0120] Step 6: No perception of the upgrade process

[0121] During the upgrade process, the client application does not need to be restarted, and the system continues to process requests from the client through the network service module. When the client application initiates a request, it can use the currently loaded firmware version for encryption operations and will not be aware of the firmware version upgrade or uninstall process.

[0122] For example, when a user submits a transaction request, even if the background system is performing an iterative update of the firmware version, the user can still complete the transaction normally, and the upgrade is transparent and imperceptible to the user.

[0123] Among them, the policy configuration of firmware version management:

[0124] System administrators can configure firmware version management policies through the business firmware management program according to actual business needs. For example: only allow clients to call the latest version of firmware (such as version 2.0), even if the client requests the older version 1.2; retain multiple firmware versions and call a specific version based on client requests to test the performance of different firmware versions in different client environments.

[0125] In actual applications, administrators can also set the validity period of the version according to the security policy. When the firmware version expires, the virtual machine will automatically uninstall the old version to ensure that the system always uses the safe and latest firmware for encryption operations.

[0126] Among them, the firmware version upgrade process:

[0127] The R&D personnel develop a new business firmware version 3.0 and upload it to the system through the business firmware management program. After the firmware is uploaded, the system will upgrade according to the following steps:

[0128] The hypervisor decrypts and verifies the signature of the firmware;

[0129] After verification, the version 3.0 firmware is loaded into the virtual machine;

[0130] The virtual machine decides to uninstall the oldest version (such as version 1.1) according to the preset policy to free up space for the new firmware;

[0131] The network service module continues to process client requests and calls the latest version 3.0 firmware for encryption operations.

[0132] During the entire upgrade process, the system does not need to stop service and the client application is unaware of the upgrade, ensuring business continuity.

[0133] Through the present invention, the cryptographic device server can perform iterative hot upgrades of business firmware without interrupting services. Through dynamic loading, version management, firmware encryption, signature verification and other technical means, efficient and secure cryptographic service upgrades are achieved, improving system availability and user experience.

[0134] In this specification, each embodiment is described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the embodiments can be referred to each other. For the device disclosed in the embodiment, since it corresponds to the method disclosed in the embodiment, the description is relatively simple, and the relevant parts can be referred to the method part.

[0135] The above description of the disclosed embodiments enables one skilled in the art to implement or use the present invention. Various modifications to these embodiments will be apparent to one skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Therefore, the present invention will not be limited to the embodiments shown herein, but rather to the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for iterative cryptographic machine service hot upgrade, characterized in that: Applied to information interaction between a client and a cryptographic device server, the cryptographic device server is configured with a business firmware virtual machine; The specific steps include: S10, dynamically loading multiple versions of business firmware in the business firmware virtual machine, including: an old version of business firmware and a new version of business firmware; the business firmware is used to process business logic; S20, receiving an access request from a client application, wherein the access request includes requested service firmware version information; S30, encrypting and signing the uploaded new firmware through the business firmware management program, loading the firmware into the business firmware virtual machine after the verification is passed, and calling the corresponding version of the business firmware according to the client's access request or preset policy; S40, the corresponding version of the business firmware is selected, and the cryptographic card is called by the cryptographic card driver to complete the encryption operation; S50. During the upgrade process, the client application communicates with the cryptographic device server, and the upgrade operation can be completed without restarting the application. The client application is unaware of the entire process.

2. The method for iterative cryptographic machine service hot upgrade according to claim 1, characterized in that: The step S10 also includes: when the service firmware virtual machine storage space reaches an upper limit, automatically uninstalling the oldest version of the service firmware to release space for loading new firmware.

3. The method for iterative cryptographic machine service hot upgrade according to claim 1, characterized in that: The step S20 also includes: when the access request of the client does not specify a firmware version, automatically selecting a default firmware version for processing according to a preset policy.

4. The method for iterative cryptographic machine service hot upgrade according to claim 1, characterized in that: The step S30 further includes: According to the upgrade requirements, the business firmware management program decides whether to retain or uninstall the old version of the firmware according to the preset policy; or modifies the preset policy for the operation of the business firmware.

5. A system for iterative cryptographic machine service hot upgrade, characterized in that: include: Client, cryptographic device server and cryptographic card; Wherein, the cryptographic device server includes: a business firmware virtual machine, a business firmware management module and a cryptographic card driver module; The business firmware virtual machine is used to dynamically load multiple versions of business firmware, including: old versions of business firmware and new versions of business firmware; the business firmware is used to process business logic; The client is used to send an access request of the client application to the cryptographic device server; the access request includes the requested service firmware version information; The business firmware management module is used to encrypt and verify the signature of the uploaded new firmware. After the verification is passed, the firmware is loaded into the business firmware virtual machine, and the corresponding version of the business firmware is called according to the client's access request or preset policy; The password card driver module is used to call the password card to complete the encryption operation according to the selected corresponding version of the service firmware; During the upgrade process, the client application communicates with the password device server, and the upgrade operation can be completed without restarting the application. The entire process is unaware of the client application.

6. The system for iterative cryptographic machine service hot upgrade according to claim 5, characterized in that: The business firmware virtual machine is also used to automatically uninstall the oldest version of the business firmware when the business firmware virtual machine storage space reaches an upper limit to release space for loading new firmware.

7. The system for iterative cryptographic machine service hot upgrade according to claim 5, characterized in that: The password device server also includes: The firmware operation policy module is used to automatically select a default firmware version for processing according to a preset policy when the client's access request does not specify a firmware version.

8. The system for iterative cryptographic machine service hot upgrade according to claim 5, characterized in that: The service firmware management module is also used to decide whether to retain or uninstall the old version of the firmware according to the upgrade requirements through the service firmware management program according to the preset policy; or to modify the preset policy for the operation of the service firmware.

Citation Information

Patent Citations

  • Software upgrading and degrading method based on label list

    CN112650515A

  • Application cipher machine architecture and system

    CN115455403A

  • Natural language-driven client application program non-inductive upgrading method and system

    CN118034742A

  • System and method for calling cipher card by KVM (Keyboard Video Mouse) virtualized cipher machine

    CN118153080A

  • Host, password service management method, storage medium, and program

    CN118606925A