Cross-CA electronic signature system and method, system construction method, equipment and medium

By designing a cross-CA electronic signature system, using intelligent password keys and certificate chain management modules to achieve mutual recognition and mutual signing among different CA manufacturers, it solves the problem of difficult use of mid-to-cross platforms and multi-CA mutual recognition in the existing technology, and improves transactions Efficiency and user experience.

CN119026184AInactive Publication Date: 2024-11-26CSCEC DIGITAL TECH CO LTD

Patent Information

Application Number
CN202411183161.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-08-27
Publication Date
2024-11-26
Estimated Expiration
Not applicable · inactive patent

AI Technical Summary

Technical Problem

The existing electronic signature technology has problems such as cross-platform use, difficulty in mutual recognition and verification among multi-CA electronic signature service manufacturers, and high maintenance costs of business systems, resulting in low transaction efficiency and waste of resources.

Method used

A cross-CA electronic signature system was designed, which provides a unified signature module and application management module to support different CA manufacturers by identifying intelligent password keys, managing certificate chains and CRL addresses, realizing seal data synchronization and certificate data storage. The mutual recognition and mutual signing of electronic signature service manufacturers adopts the JS package bridge mode to achieve cross-platform calls.

Benefits of technology

It realizes mutual recognition, signing and verification of electronic signatures of different CAs, reduces the difficulty and complexity of the business system's compatibility and adaptability to multiple CAs, supports cross-system platform calls, reduces maintenance costs, and improves user experience and transaction efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119026184A_ABST
    Figure CN119026184A_ABST
Patent Text Reader

Abstract

The invention relates to the technical field of electronic signatures, in particular to a cross-CA electronic signature system, a cross-CA electronic signature method, a system construction method, equipment and a medium, which can realize mutual recognition, mutual signing and mutual verification of different CA electronic signatures used by different service systems, and the service systems do not need to carry out multi-CA compatible adaptation. And the difficulty and the complexity of the multi-CA electronic signature application requirement of the service system are reduced. Mutual recognition, mutual signing and mutual verification of different CA electronic signatures are used, one-time butt joint of a single service system is achieved only by adopting the system, multi-CA compatibility adopts a js packet bridging mode, cross-system platform calling is supported, client packaging and installation of various different system platforms are not needed, upgrading without perception of signature users is not needed, and the system is easy to popularize and use. And realizing interconnection and intercommunication with a CA client provided by a CA electronic signature service manufacturer through a multi-CA compatible js packet.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the technical field of electronic signatures, and in particular to a cross-CA electronic signature system and method, and a system construction method, device and medium. Background Art

[0002] As the country continues to promote the construction of digital government, the promotion and application of electronic signatures has become an indispensable part of the e-government services of governments at all levels and the comprehensive digital transformation of enterprises. Electronic signatures are a form of electronic signatures and follow the "Electronic Signature Law". At the same time, Article 16 of the "Electronic Signature Law" stipulates that if electronic signatures require third-party authentication, the authentication service shall be provided by an electronic authentication service provider established in accordance with the law. Electronic authentication service agencies (third-party service agencies that provide CA electronic signatures) guarantee the authenticity and reliability of the public and private keys owned by all parties involved in the transaction process by issuing digital certificates to all parties involved in the transaction and providing certificate verification services, thereby ensuring the authenticity and reliability of the electronic signatures of all parties involved.

[0003] At present, there are many third-party service agencies that provide CA electronic signatures, including CA certification agencies and CA electronic signature service providers. CA agencies include Shanghai CA, Beijing CA, CFCA, Guangdong CA, etc. CA electronic signature service providers include Dajiaqian, eSign, Anzhengtong, FaDaDa, etc. Third-party service agencies that provide CA electronic signatures divide the market and cannot mutually sign, recognize, or verify each other. Different business systems will access different CA electronic signature software and hardware provided by third-party service agencies according to the needs of the responsible units of the business systems. The same signature user needs to apply for the CA electronic seal connected to the business system when using CA electronic signatures in different business systems. At the same time, the same electronic document requires different signature users to use their own electronic seals. To complete CA electronic signatures, the business system needs to access the software and hardware provided by multiple CA electronic signature service providers, which increases transaction costs and management difficulties, reduces transaction efficiency, and causes a waste of resources caused by software and hardware provided by multiple CA electronic signature service providers with the same functions. Currently, the main implementation solution for multi-CA electronic signature is multi-CA compatibility, which requires the business system to integrate and adapt the CA electronic signature software and hardware provided by different third-party service agencies. It is mostly used in a single business scenario, including multi-CA services in the electronic bidding industry and multi-CA services in the medical and health system. The existing electronic signature technology has the following problems:

[0004] A specific USBkey signature client needs to be created, which cannot be used across platforms. Every time a CA electronic signature service provider is added, the client for multiple CA electronic signatures needs to be repackaged. The business system side needs to be connected and adapted with different CA electronic signature service providers. Every increase or decrease requires changes to the business system, which is labor-intensive, inconvenient, and costly. The electronic signature operation interface is not unified. If it is provided by the business system itself, multiple business systems will need to provide electronic signature operation interfaces separately, which results in a poor user experience for signature users. The business system directly connecting to multiple CA electronic signature service providers has poor maintainability and high maintenance costs. Summary of the invention

[0005] In view of this, the present invention proposes a cross-CA electronic signature system and method, as well as a system construction method, equipment and medium, which can realize the mutual recognition, mutual signing and mutual verification of electronic signatures of different CAs used in different business systems. The business system does not need to perform multi-CA compatibility adaptation, thereby reducing the difficulty and complexity of the multi-CA electronic signature application requirements of the business system.

[0006] To achieve the above object, the technical solution of the present invention is:

[0007] An electronic signature system with cross-CA mutual recognition and signing, including:

[0008] A bridge module for identifying smart password keys of different CA manufacturers, a manufacturer management module for managing basic information of external CA manufacturers, a certificate chain management module for managing certificate chain information, a CRL list management module for managing CRL addresses, a seal data synchronization module, a certificate data synchronization module, an electronic signature user management module for managing basic information of signature users, a seal data storage module, a certificate data storage module, an application management module, an addressing configuration management module, and a unified signature module;

[0009] The seal data storage module receives the seal data synchronized by the seal data synchronization module after the electronic signature user authorizes it;

[0010] The certificate data storage module receives the public key certificate synchronized by the certificate data synchronization module after the electronic signature user authorizes it;

[0011] The application management module manages the identity authentication identifier and related information of the upper-level business application access system, and is used to verify whether the business application system for the electronic signature user's signature operation has the cross-CA electronic signature capability;

[0012] Addressing configuration management module, configure application service type, initiator management and policy configuration management, and realize the relationship management of binding initiator, service type and service provider;

[0013] The unified signature module executes the procedure of different signature users using electronic seals provided by different CA manufacturers to sign the same file across CAs.

[0014] Among them, the CA manufacturer basic information includes the application access qualification information provided when the enterprise applies for registration. The manufacturer management module uses the basic information to associate with the certificate chain, seal information, certificate information and user information provided by the third-party CA organization; the bridging module is a USBKEY signature client bridging module, which is used to identify the signature USBKEY provided by different CA electronic signature service manufacturers. The CA electronic signature service manufacturer submits its own JS package according to the established client access standard. The USBKEY signature client bridging module parses and matches the JS package submitted by the CA electronic signature service manufacturer based on the CA electronic signature service manufacturer information associated in the electronic signature service manufacturer management module, and passes the parsed data to the certificate chain management module and the CRL list management module.

[0015] The certificate chain management module is used to manage the certificate chain information provided by the third-party CA institution used by the external CA electronic signature service provider, and is used to establish a trust relationship between the CAs of the public key infrastructure, and can optionally configure an online certificate status query URL address; wherein the certificate chain information and the online certificate status query URL address are verified according to the data passed by the USBKEY signature client bridge module, and if the verification fails, the signing user is prompted to use the correct CA digital certificate;

[0016] The CRL list management module is used to manage the CRL address provided by the third-party CA organization used by the external CA electronic signature service provider, and is used to verify whether the status of the currently used digital certificate is revoked. At the same time, it receives the data passed by the USBKEY signature client bridge module after the verification by the certificate chain management module. If the verification fails, it prompts the result corresponding to the digital certificate status being expired or revoked;

[0017] After the electronic signature user completes the online authorization consent by manually clicking on the seal data synchronization module, the seal data synchronization module is used to actively pull the electronic seal data that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled electronic seal data in the seal data storage module;

[0018] After the electronic signature user completes the online authorization consent by manually clicking on the certificate data synchronization module, the certificate data synchronization module is used to actively pull the digital certificate information that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled certificate information in the certificate data storage module;

[0019] The basic information of the signature user includes user name, whether it is real name, user nature, user status and registration time. If the signature user is not in the electronic signature user management module, the user is guided to complete the registration.

[0020] Among them, the relationship between each CA electronic signature service vendor and the certificate chain provided by the CA institution used by each CA electronic signature service vendor is established, and a multi-CA mutual recognition and verification trust list model is established to verify the digital certificates used by different CA electronic signature service vendors. Specifically, the relationship between the unique ID of the CA electronic signature service vendor and the unique ID of the CA institution of the CA electronic signature service vendor is configured, and a two-dimensional table based on the trust list model is established.

[0021] The system establishes a unified business application access standard specification interface and a unified signature client to provide unified standard technical services for cross-CA electronic signatures in various scenarios. The standard specification interface includes a client interface and a server interface.

[0022] The client interface includes two parts: one is the signature component js package interface, and the other is the unified signature client interface;

[0023] Among them, the signature component is uniformly encapsulated into the signature component js package of each CA electronic signature service provider in JavaScript mode. The original CA client of each CA electronic signature service provider does not need to be uninstalled or updated. The upper-layer application passes the signature user and business application through the signature component js package interface to address the signature component js package provided by the corresponding CA electronic signature service provider. The signature component js package is interconnected with the CA client used by the CA electronic signature service provider to parse the certificate and seal in the CA client;

[0024] The unified signature client interface includes a file signature interface, a signature acquisition link interface, a signature status query interface, a signature document download interface, a signature service revocation interface, a signature reminder interface, a signature document verification interface, a trigger silent signature interface, a bridge interface, a signature service callback interface, a signature process callback interface, a business type acquisition interface, a batch signature interface, a seat tag interface, a keyword signature interface, a seal authorization verification interface and a certificate verification interface;

[0025] The server interface is aimed at various CA electronic signature service providers and is used for acquiring and verifying seal data and certificate data, including certificate verification interface, signature user synchronization interface, certificate synchronization interface, seal synchronization interface, business type acquisition interface, seal authority query interface, user information query interface and seal usage record synchronization interface.

[0026] The present invention also provides a cross-CA electronic signature method, which is implemented using the system of the present invention and includes the following steps:

[0027] Step 1: Identify the smart password keys of different CA organizations and obtain digital certificates;

[0028] Step 2: parse the issuer information of the user certificate, determine the issuing authority, and verify the validity of the certificate;

[0029] Step 3: The third-party electronic signature service provider synchronizes the seal data and certificate data by pulling or pushing information based on the signature user;

[0030] Step 4, find the matching certificate and the seal data corresponding to the certificate;

[0031] Step 5: Find the private key corresponding to the signature used by the signing user according to the signing service initiator, application system, seal data, and service provider;

[0032] Step 6: Complete the final signature by finding the seal with the corresponding authority for this business according to the addressing rules.

[0033] The present invention also provides a method for constructing an electronic signature system for cross-CA mutual recognition and mutual signing, comprising the following steps:

[0034] Step 1: Establish the relationship between each CA electronic signature service provider and the certificate chain provided by the CA institution used by each CA electronic signature service provider, and establish a multi-CA mutual recognition and mutual verification trust list model to verify the digital certificates used by different CA electronic signature service providers;

[0035] Step 2: Establish the relationship between the signature user and each CA electronic signature service provider, and clarify the binding relationship between the signature user and the CA electronic signature service provider;

[0036] Step 3: At the technical level of each CA electronic signature service provider, formulate unified access standards for mutual recognition and trust of CA digital certificates and unified access standards for mutual signing and verification of electronic seals;

[0037] Step 4: Each CA electronic signature service provider develops a standardized interface for CA digital certificates and electronic seals in accordance with access technology standards;

[0038] Step 5: Develop a cross-CA electronic signature mutual recognition, mutual signing and mutual verification application system to provide unified cross-CA electronic signature application standards and specifications for upper-layer business applications;

[0039] Step 6: Develop a USBKEY signature client bridge module to achieve mutual recognition, mutual signing and mutual verification of signature clients of various CA electronic signature service providers, and be compatible with differences in technology; at the same time, establish unified business application access standards and specifications and a unified signing client to provide unified standard technical services for cross-CA electronic signatures in various scenarios.

[0040] Among them, according to the relationship between the certificate chains provided by the CA institutions used by each CA electronic signature service provider established in step 1 and the multi-CA mutual recognition and verification trust list model, according to the relationship between the signature user and each CA electronic signature service provider established in step 2, the standardized interfaces of CA digital certificates and electronic seals developed by each CA electronic signature service provider in step 4 are integrated according to the access technology standards, and a set of standard interfaces including certificate verification, digital signature, signature verification, and seal stamping functions are generated for the upper-level business applications.

[0041] The present invention also provides an electronic device, comprising a processor and a memory for storing executable instructions of the processor; the processor is used to read the executable instructions from the memory and execute the instructions to implement the method for constructing an electronic signature system with cross-CA mutual recognition and mutual signing as described in the present invention.

[0042] The present invention also provides a computer-readable storage medium, which stores a computer program, and the computer program is used for the method for constructing an electronic signature system with cross-CA mutual recognition and mutual signing as described in the present invention.

[0043] Beneficial effects:

[0044] 1. The system of the present invention realizes the mutual recognition, signing and verification of electronic signatures of different CAs. It only needs to use the system of the present invention to realize one-time docking with a single business system to realize the mutual recognition, signing and verification of electronic signatures across CAs. The business system does not need to perform multi-CA compatibility adaptation. The same task to be signed in the business system supports the relevant parties to use the existing CA electronic signature to complete the electronic signature operation and verification of the task to be signed. The increase or decrease of different CA electronic signature service agencies is not felt by the business system, which reduces the difficulty and complexity of the business system's multi-CA electronic signature application requirements. Multi-CA compatibility adopts js package bridging mode, supports cross-system platform calls, does not need to perform client packaging and installation of various different system platforms, and has no perceived upgrade for signature users. The multi-CA compatible js package is used to achieve interconnection with the CA client provided by the CA electronic signature service provider.

[0045] 2. The system of the present invention includes a USBKEY signature client bridging module, which is used to identify the routing bridge of smart password keys and internal certificate information of smart password keys provided by different CA electronic signature service vendors, and supports cross-platform use. This module is used to identify the signature USBKEY provided by different CA electronic signature service vendors. The CA electronic signature service vendor must submit its own JS package according to the established client access standard method. The USBKEY signature client bridging module parses and matches the JS package submitted by the CA electronic signature service vendor according to the CA electronic signature service vendor information associated in the electronic signature service vendor management module, and passes the parsed data to the certificate chain management module and the CRL list management module to achieve cross-CA.

[0046] 3. The system of the present invention is transparent to the upper-layer business applications and is compatible with the lower-layer CA electronic signature service providers and the CAs they provide. The system does not generate CA electronic signature data internally. The system is only used for data interaction security management and cross-CA electronic signature applications between the upper-layer business application system and the lower-layer CA electronic signature service providers and the CA electronic signature data they provide.

[0047] 4. The system of the present invention establishes the relationship between each CA electronic signature service provider and the certificate chain provided by the CA institution used by each CA electronic signature service provider, and establishes a multi-CA mutual recognition and mutual verification trust list model to verify the digital certificates used by different CA electronic signature service providers; establishes the relationship between the signature user and each CA electronic signature service provider, and clarifies the binding relationship between the signature user and the CA electronic signature service provider; formulates the unified access standard for mutual recognition and mutual trust of CA digital certificates and the unified access standard for mutual signing and mutual verification of electronic seals at the technical upper layer of each CA electronic signature service provider; by formulating the upper-layer application access specification and the lower-layer CA electronic signature service provider access specification, the upper-layer application is connected to the system of the present invention service at one time, and interconnects with the CA client provided by the lower-layer CA electronic signature service provider through the unified signature page internal bridge CA js package, and realizes the mutual recognition, signing and trust of cross-CA electronic signatures of different signature users through the unified signature page, and the unified signature page signs and verifies each other, which is easy to access, easy to expand and has a good experience.

[0048] 5. The system of the present invention provides a signature task to realize the signature task addressing and forwarding private key signature. Specifically, by configuring the relationship between the CA electronic signature service provider and the CA certificate chain, the relationship between the signature user and the CA electronic signature service provider, the relationship between the signature user and the seal, the relationship between the business application system and the CA electronic signature service provider, and the relationship between the business type and the seal, the signature personnel will select the signature medium method on the unified signature page, perform internal addressing through the system and verify the CA information in the medium method, and finally find the private key owned by the user to complete the P1 signature. The cross-CA electronic signature mutual recognition, mutual signing and mutual trust application system will then find the signature user authorization, and the certificate synchronized from the CA electronic signature service provider will complete the P7 signature, and finally complete the signing of the PDF file.

[0049] 6. The method of the present invention is implemented based on the invented system. A single business system can realize the mutual recognition, signing and verification of cross-CA electronic signatures through one docking, without the need for multi-CA compatibility adaptation. The same task to be signed in the business system supports the relevant parties to use the existing CA electronic signature to complete the electronic signature operation and verification of the task to be signed. The increase or decrease of different CA electronic signature service agencies is not noticed by the business system, which reduces the difficulty and complexity of the business system's multi-CA electronic signature application requirements. Multi-CA compatibility adopts the js package bridging mode, supports cross-system platform calls, and does not require client packaging and installation of various different system platforms. There is no perceived upgrade for the signature user, and the multi-CA compatible js package is used to achieve interconnection with the CA client provided by the CA electronic signature service provider. BRIEF DESCRIPTION OF THE DRAWINGS

[0050] Figure 1 The figure is a schematic diagram of the system composition and signature method flow of the present invention.

[0051] Figure 2 Schematic diagram of the overall architecture of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0052] Figure 3 This is a schematic diagram of the technical architecture of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0053] Figure 4 This is a schematic diagram of the functional architecture of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0054] Figure 5 This is a schematic diagram of data flow in the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0055] Figure 6 This is a schematic diagram of the logical deployment architecture of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0056] Figure 7 Schematic diagram of the security architecture of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0057] Figure 8 This is a schematic diagram of the integrated architecture of the physical printing control function of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0058] Fig. 9 This is a schematic diagram of a multi-CA compatible signing client of a mutual signing and mutual recognition platform in an embodiment of the system of the present invention.

[0059] Fig.10 This is a schematic diagram of the calling process of the JS bridge mode of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0060] Fig.11 This is a schematic diagram of the unified certificate method flow on the PC side of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0061] Fig.12 This is a schematic diagram of the unified certificate assistant mode on the mobile phone side of the mutual signing and mutual recognition platform of the system embodiment of the present invention.

[0062] Fig.13 This is a schematic diagram of the unified middleware for server-side certificates of the mutual signing and recognition platform of the system embodiment of the present invention.

[0063] Fig.14 This is a schematic diagram of the overall architecture of the mutual signing and mutual recognition platform pilot application integration access in the system embodiment of the present invention.

[0064] Fig.15 This is a flow chart of the method for constructing an electronic signature system with cross-CA mutual recognition and signing according to the present invention.

[0065] Fig.16 A schematic diagram of the structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0066] The present invention is described in detail below with reference to the accompanying drawings and embodiments.

[0067] The present invention proposes an electronic signature system for cross-CA mutual recognition and mutual signing, the system composition is as follows Figure 1 As shown, including:

[0068] USBKEY signature client bridge module, electronic signature service provider management module, certificate chain management module, CRL list management module, seal data synchronization module, certificate data synchronization module, electronic signature user management module, seal data storage module, certificate data storage module, application management module, addressing configuration management module and unified signature module;

[0069] Among them, the USBKEY signature client bridge module is used to identify the smart password keys of different CA electronic signature service providers and obtain digital certificates; specifically, the digital certificate is obtained through the routing bridge of the certificate information inside the smart password key;

[0070] Among them, the USBKEY signature client bridge module is the key to the system's support for cross-platform use. This module is used to identify the signature USBKEY provided by different CA electronic signature service providers. The CA electronic signature service provider submits its own JS package according to the established client access standard. The USBKEY signature client bridge module parses and matches the JS package submitted by the CA electronic signature service provider according to the CA electronic signature service provider information associated in the electronic signature service provider management module, and passes the parsed data to the certificate chain management module and the CRL list management module. In the present invention, multi-CA compatibility adopts js package bridging mode, supports cross-system platform calls, does not require client encapsulation and installation of various different system platforms, and has no perceived upgrade for signature users. The CA client provided by the CA electronic signature service provider is interconnected and interoperable through multi-CA compatible js packages.

[0071] The electronic signature service provider management module is used to manage the basic information of external CA electronic signature service providers, including the application access qualification information provided when the enterprise applies for registration, and use the basic information to associate with the certificate chain, seal information, certificate information and user information provided by the third-party CA organization.

[0072] The certificate chain management module is used to manage the certificate chain information provided by the third-party CA institution used by the external CA electronic signature service provider, and is used to establish a trust relationship between the certificate issuing authorities (CA) of the public key infrastructure (PKI), and can optionally configure the online certificate status query URL address. The certificate chain information and the online certificate status query URL address are verified according to the data passed by the USBKEY signature client bridge module. If the verification fails, the signing user is prompted to use the correct CA digital certificate.

[0073] The CRL list management module is used to manage the CRL address provided by the third-party CA organization used by the external CA electronic signature service provider, and is used to verify whether the status of the currently used digital certificate is revoked. At the same time, it receives data passed from the USBKEY signature client bridge module after verification by the certificate chain management module. If the verification fails, it prompts that the digital certificate status is expired, revoked, etc.

[0074] After the electronic signature user completes the online authorization consent by manually clicking on the seal data synchronization module, the seal data synchronization module is used to actively pull the electronic seal data that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled electronic seal data in the seal data storage module.

[0075] After the electronic signature user completes the online authorization consent by manually clicking on the certificate data synchronization module, the certificate data synchronization module is used to actively pull the digital certificate information that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled certificate information in the certificate data storage module.

[0076] The electronic signature user management module is used to manage the basic information of the signature user, including user name, whether it is real name, user nature, user status and registration time, etc. If the signature user is not in the electronic signature user management module, the user is guided to complete the registration.

[0077] The seal data storage module is used to receive the seal data information synchronized by the electronic signature user authorization.

[0078] The certificate data storage module is used to receive the public key certificate information synchronized by the electronic signature user authorization.

[0079] The application management module is used to manage the identity authentication identifiers and related information of the upper-level business application access system, and to verify whether the business application system of the electronic signature user's signature operation has the ability to electronically sign across CAs.

[0080] The addressing configuration management module is used to configure application business types, initiator management and policy configuration management, and realize the relationship management of binding initiators, business types and service providers. It can select the address of the signature service provider to be used according to the business type of the user's signature when signing.

[0081] The unified signature module is used to execute the procedure of different signature users using electronic seals provided by different CA electronic signature service providers to sign the same file across CAs.

[0082] In summary, the system of the present invention establishes the relationship between each CA electronic signature service provider and the certificate chain provided by the CA organization used by each CA electronic signature service provider, and establishes a multi-CA mutual recognition and verification trust list model to verify the digital certificates used by different CA electronic signature service providers; establishes the relationship between the signature user and each CA electronic signature service provider, and clarifies the binding relationship between the signature user and the CA electronic signature service provider; formulates the unified access standard for mutual recognition and trust of CA digital certificates and the unified access standard for mutual signing and verification of electronic seals at the technical upper layer of each CA electronic signature service provider; each CA electronic signature service provider develops the standard interface of CA digital certificates and electronic seals in accordance with the access technology standard, and provides the upper-layer business application with a unified cross-CA electronic signature application standard specification through the system of the present invention; and completes the mutual recognition, signing and verification of the signature clients of each CA electronic signature service provider through the USBKEY signature client bridging module, and is compatible with the differences between technologies.

[0083] Among them, the relationship between each CA electronic signature service vendor and the certificate chain provided by the CA institution used by each CA electronic signature service vendor is established, and a multi-CA mutual recognition and verification trust list model is established to verify the digital certificates used by different CA electronic signature service vendors. Specifically, the relationship between the unique ID of the CA electronic signature service vendor and the unique ID of the CA institution of the CA electronic signature service vendor is configured, and a two-dimensional table based on the trust list model is established.

[0084] Establish the relationship between the signature user and each CA electronic signature service provider, and clarify the binding relationship between the signature user and the CA electronic signature service provider. Specifically: establish the relationship between the signature user and the CA electronic signature service provider, and the relationship is synchronized by the signature user synchronization interface to synchronize data from the CA electronic signature service provider to the system of the present invention.

[0085] At the technical level of each CA electronic signature service provider, a unified access standard for mutual recognition and trust of CA digital certificates and a unified access standard for mutual signing and verification of electronic seals are formulated. Specifically: for the business scenarios of CA digital certificates, a unified interface specification for signing, verification, public key export, encryption, decryption, certificate synchronization, certificate parsing, and certificate verification is formulated; for the business scenarios of electronic signatures, a unified interface specification for the use of electronic signatures, synchronized seals, seal authorization verification, and electronic signatures is formulated, and stamping is performed on the cross-platform electronic signature client through the above.

[0086] It can be seen that it is user-friendly for new and old signature users. There is no need to uninstall and install the installed CA certificate client, nor is it necessary to re-upgrade and package the CA certificate client for each additional CA electronic signature user. By formulating a unified signature component interface specification, the CA electronic signature service provider encapsulates according to the signature component interface specification, provides a signature component js library file, and unifies the signature client directory configuration path through the USBKEY signature client bridge module of the system. The upper-level business system calls the unified signature client, and the unified signature client calls the multi-CA compatible bridge API. According to the CA identifier of the transmitted CA electronic signature service, the signature component js package provided by the corresponding CA electronic signature service provider is called, and then the signature component js package provided by each CA electronic signature service provider calls the CA client of each CA electronic signature service provider, and returns the result information such as certificate, public key and signature. The system of the present invention is transparent to the upper-level business application, and is compatible with the lower-level CA electronic signature service provider and the provided CA. The system does not produce CA electronic signature data, and is only used for data interaction security management and cross-CA electronic signature application between the upper-level business application system and the lower-level CA electronic signature service provider and the provided CA electronic signature data.

[0087] Furthermore, the system of the present invention establishes a unified business application access standard specification interface and a unified signature client to provide unified standard technical services for cross-CA electronic signatures in various scenarios. The standard specification interface includes a client interface and a server interface, wherein:

[0088] The client interface includes two parts: one is the signature component js package interface, and the other is the unified signature client interface.

[0089] The signature component is uniformly encapsulated into the signature component js package of each CA electronic signature service provider in JavaScript. The original CA client of each CA electronic signature service provider does not need to be uninstalled or updated. The upper-layer application passes the signature user and business application through the signature component js package interface to address the signature component js package provided by the corresponding CA electronic signature service provider. The signature component js package is interconnected with the CA client used by the CA electronic signature service provider to parse the certificate and seal information in the CA client; specifically, the signature component js package interface includes the getUkList enumeration Ukey media interface, the exportCert export certificate interface, the hash calculation summary interface, the generateRandom random number acquisition interface, the sign digital signature interface, the encryptEnvelope encryption digital envelope interface, the decryptEnvelope decryption digital envelope interface and the exportPublicKey export public key interface, as follows:

[0090] getUkList enumerates the Ukey media interface, which is used to find the UKey media inserted in the current user's computer; exportCert exports the certificate interface, which is used to export the signature certificate according to the media serial number enumerated by getUkList after reading the Ukey media, for certificate validity verification; hash calculates the summary interface, which performs summary calculation on the original task text to be signed, for subsequent digital signatures; generateRandom obtains the random number interface, which is used to generate nonce, salt, initialization vector and key (symmetric key or asymmetric key), which is used when initializing the medium; sign digital signature interface, which can perform P1 signature on the string; encryptEnvelope encrypts the digital envelope interface, which encrypts the data; decryptEnvelope decrypts the digital envelope interface, which decrypts the data; exportPublicKey exports the public key interface, which exports the public key information.

[0091] The unified signature client interface includes a file signature interface, a signature acquisition link interface, a signature status query interface, a signature document download interface, a signature business revocation interface, a signature reminder interface, a signature document verification interface, a trigger silent signature interface, a bridge interface, a signature business callback interface, a signature process callback interface, a business type acquisition interface, a batch signature interface, a seat tag interface, a keyword signature interface, a seal authorization verification interface and a certificate verification interface. Among them, the file signature interface (Create) supports multi-file signature, and supports signatures in the form of coordinate positioning, keyword positioning, and interline stamping. Calling this interface can be used for business signatures. Through the relationship between the CA electronic signature service provider and the certificate chain provided by the CA institution used by each CA electronic signature service provider, as well as the relationship between the signature user and each CA electronic signature service provider, the signature component js package used by the signature user is addressed, and the signature component js package is interconnected with the CA client of the CA electronic signature service provider through the CA electronic signature service provider. The signature certificate is parsed through the exportCert export certificate interface, and mutual recognition is completed based on the certificate chain provided by the CA institution. After the authentication is passed, the sign digital signature interface is called to perform P1 signature on the PDF of the task document to be signed that is passed by the business system. After the P1 signature is completed, the corresponding signature certificate authorized and synchronized in the system is called to perform P7 signature packaging. The packaged P7 signature is synthesized into the signature field specified by the PDF through the PDF rendered by the unified signature client. At the same time, for the same PDF, different certificates parsed by different clients can be used for P1 signature, and then the corresponding signature certificates authorized in the system are called to perform P7 signatures after verification is successful, so as to realize P Mutual signing function on DF; signature acquisition link interface, used to obtain the link interface url, and obtain the computer-side signature link of the current signature user according to the generated signature business serial number. After the signature user receives the signature link interface, it opens the signature operation; signature status query interface (query), according to the generated signature business serial number, query the signature business status, including the signature status of each participant; signature document download interface (download), download the signed PDF document through the generated signature business serial number; signature business revocation interface (revoke), the upper-level business system can root According to the signing business scenario, this interface needs to be called to cancel the signing task of the unfinished signing; Signature urging interface (ugre), the upper-level business system calls this interface to notify the current user to sign to complete the signing process. The same business and the same participant can only be urged to sign once a day; Signature document verification interface (verify), the upper-level business system can use this interface to verify the validity of the signature in the signed document, and return the verification result of each signature and the document validity verification result; Trigger silent signature interface (trigger), the upper-level business system can trigger the silent signature of the corresponding participant through the business serial number and participant id.

[0092] The server interface is aimed at various CA electronic signature service providers and is used for acquiring and verifying seal data and certificate data, including certificate verification interface, signature user synchronization interface, certificate synchronization interface, seal synchronization interface, business type acquisition interface, seal authority query interface, user information query interface and seal usage record synchronization interface.

[0093] The working process of the system of the present invention is described by taking an embodiment of the system of the present invention (electronic signature mutual recognition platform):

[0094] The electronic signature mutual recognition platform of this embodiment adopts CA digital certificates, digital certificate mutual trust and recognition technology, electronic signature technology, cryptographic algorithms (commercial secret algorithms and international general algorithms) and third-party evidence storage on the chain to realize multi-CA compatible clients (PC and mobile phones), unified signing portal, mutual signature and mutual recognition platform external user portal, mutual signature and mutual recognition platform internal user portal and mutual signature and mutual recognition platform management console functions, and at the same time establishes a security management system to avoid application security risks from a system perspective.

[0095] The electronic signature mutual recognition platform adopts a multi-CA mutual trust and mutual recognition standard system, based on the national third-party electronic certification industry electronic certification service standard specification system, taking into account the coordination and docking with the relevant standards of domestic commercial cryptographic algorithms, and combining the current third-party electronic certification service supervision ideas of electronic certification service agencies and the domestic bidding industry's market access mechanism for multi-CA access, to formulate a multi-CA mutual trust and mutual recognition standard specification system, including important standards and specifications such as technical, integrated implementation, compliance testing and management standards and specifications for multi-CA mutual trust and mutual recognition. From the aspects of digital certificate application type, certificate format unification, mutual trust and mutual recognition of electronic signatures, unification of certificate client integration interface, unification of data synchronization interface, and application services and application supervision of certificates and electronic seals, the enterprise's multi-CA mutual trust and mutual recognition standard specification system will be gradually improved. Through the establishment of this system, various information systems of enterprises and CA electronic signature service providers will be guided to standardize the application of passwords and access to the mutual signing and mutual recognition platform to ensure standard unification, mutual trust and mutual recognition, and security sustainability.

[0096] As a service guarantee for the mutual signing and mutual recognition of electronic signatures for enterprise groups’ unified and self-built business systems, the mutual signing and mutual recognition platform undertakes the functions of service provider management, signing personnel management, business addressing management, signing service management, evidence storage management, log audit management, physical printing control management and platform system management. It integrates and adapts with the external signing service provider platform client and server through the access specifications and adapter base interface released by the mutual signing and mutual recognition platform, provides a unified mutual signing page for internal and external users through the mutual signing and mutual recognition portal, and realizes the storage of evidence of the signing process and signing results on the chain through evidence management. The overall architecture of the mutual signing and mutual recognition platform is as follows: Figure 2 As shown, the technical architecture is as follows Figure 3As shown in the figure, the front-end and back-end separation architecture is adopted. The front-end is developed with H5 and VUE3.0 framework to provide a user interaction interface. Load balancing is implemented by Nginx, and the connection is maintained through Keepalive. The back-end is developed with Java Spring Boot JPA Redis Mysql, etc., responsible for data processing and business logic implementation. The entire system runs on a virtual machine server and uses the Kylin V10 operating system, which is highly scalable and flexible.

[0097] The mutual signing and recognition platform of this embodiment can mainly provide unified registration services, real-name authentication services, mutual signing services, mutual recognition services, mutual verification services, evidence storage services, certificate issuance services, data synchronization services, change services and cancellation services to internal users of the enterprise group, external users, centrally built and self-built business systems, and external signing service provider platforms. It can achieve the unified use of digital certificates and seals issued by different CA organizations in the business systems of the group and its subsidiaries, mutual trust, mutual recognition, mutual signing, and mutual verification, and avoid repeated applications for certificates and seals across regions and business systems. At the same time, it provides internal physical seal authorization management functions that meet the needs of the scenario. The overall architecture of the mutual signing and recognition platform is as follows: Figure 4 shown.

[0098] The mutual signing and mutual recognition platform includes external data flow and internal data flow. The external data flow is mainly the data between CA electronic signature service providers and the mutual signing and mutual recognition platform. The data is actively pulled and passively pushed to carry out the flow of data information. The internal data flow is mainly the flow of data information between the mutual signing and mutual recognition platform and the internal network such as the enterprise group master data, 4A, KMS, and the group's unified business application system. Figure 5 shown.

[0099] The mutual signing and mutual recognition platform is deployed with local virtual servers, and the application server adopts dual-machine hot standby mode to ensure the uninterrupted service provided to the outside world. Nginx is deployed on the application server of the mutual signing and mutual recognition platform to achieve load balancing, and Keepalive is deployed to maintain the connection; 3 Redis are deployed in cluster mode, and two file storage servers are deployed for users to store signed files. The two servers are in master-slave mode, and 2 database servers are deployed in master-slave deployment mode, reusing existing password devices for the security protection of important data. The specific deployment architecture is as follows: Figure 6 shown.

[0100] The security standards of the mutual signing and mutual recognition platform are in accordance with the requirements of laws and regulations such as the "Cybersecurity Law", "Personal Information Protection Law", "Cybersecurity Level Protection Regulations", and the "China Construction Co., Ltd. Cybersecurity Operation and Maintenance Management Rules", "China Construction Co., Ltd. Personnel Cybersecurity Management Rules", "China Construction Co., Ltd. Cybersecurity Management Regulations" and other group-related documents. The encryption algorithm is constructed using national encryption standards. The security architecture of the mutual signing and mutual recognition platform is as follows: Figure 7 shown.

[0101] Furthermore, through research and selection, the mainstream physical seal control system and supporting equipment on the market are selected to add physical seal management and physical seal authorization for internal users to the electronic signature mutual recognition platform. Through the open interface of the physical seal control system, the user system based on the mutual signature and mutual recognition platform is connected and secondary functions are developed. A unified physical integrated management function is formed for enterprise groups and their subsidiaries on the mutual signature and mutual recognition platform. The unified authorization control of electronic seals and physical seals is realized through the mutual signature and mutual recognition platform. The physical seal control function integration architecture diagram Figure 8 shown.

[0102] The multi-CA compatible signing client mainly includes PC-side USBKEY certificates, mobile phone certificates, and server-side cloud certificates. It is mainly integrated and packaged in the form of APP and SDK to form CA middleware to read digital certificates of different CA institutions, and use the corresponding user private key to complete the P1 electronic signature of contract documents. Finally, the unified signing page of the mutual signing and recognition platform is integrated with the multi-CA compatible signing client to realize the P7 signature to form a unified signing format and complete the final electronic signature function. Fig. 9As shown. The multi-CA compatible signing client provides two modes, PC and mobile, according to the application scenario and operation entry. By studying the national secret interface specifications such as GM / T 0016 and 0020, the integrated access specification interface of the multi-Ca compatible signing client is formulated in accordance with the existing standard specifications. The client interface mainly refers to the access of the cryptographic device that completes the digital signature at the resource layer, including USBKEY, mobile phone security password module and cloud certificate system. Considering the scope of adaptation, after investigation and research, and taking into full consideration the existing users of the enterprise group and its subsidiaries, the client interface technology of the mutual signing and mutual recognition platform follows the relevant interface specifications of the cryptographic industry (GM / T series: "GMT 0016-2012 Smart Password Key Password Application Interface Specification" - referred to as SKF interface, "GMT 0020-2012 Certificate Application Comprehensive Service Interface Specification" - referred to as SOF interface, "GMT XXXX-XXXX Mobile Terminal Password Module Application Interface Specification" - referred to as SSF interface, "GM / T 0125-2022 "JSON Web Cryptography Application Syntax Specification"). The mutual signing and recognition platform shall formulate the integrated access interface specifications and requirements, and each CA electronic signature manufacturer service provider or third-party CA organization shall complete the adaptation development in accordance with the specifications and requirements formulated by the mutual signing and recognition platform.

[0103] The USBKEY integration docking methods include the multi-CA compatible JS bridging method on the signing page and the unified certificate assistant mode on the PC. In the multi-CA compatible JS bridging method on the signing page, USBKEY integration must fully consider the existing users of China Construction Group and its subsidiaries, avoid uninstalling and reinstalling the PC-side USBKEY certificate client provided by different manufacturers, and avoid the learning cost. A multi-CA compatible JS bridging access method has been developed. Each electronic signature service provider provides the corresponding USBKEY driver software, implements the relevant interface in accordance with the established access interface specification, and packages it into a js library file. After completing the settlement on the mutual signing and mutual recognition platform, it is provided to the platform manager for verification, and then integrated by the platform manager into the multiCaJsBridge.js component of the mutual signing and mutual recognition signing page. The specific calling process is as follows: Fig.10 The details are as follows:

[0104] The Web business system calls multiCaJsBridge.js; multiCaJsBridge.js calls the js method provided by the corresponding CA according to the CA identifier passed in by the business system; the js provided by each CA calls its own certificate client and returns the final result.

[0105] In the unified certificate assistant mode on the PC side, in order to adapt to the differences between various signing platforms, the mutual signing and mutual recognition platforms uniformly abstract the cryptographic calculation functions required for electronic signing and verification into a cryptographic resource interface through the PC-side certificate assistant. Each electronic signature service platform implements the interface according to actual conditions and outputs the C interface DLL.

[0106] The unified certificate assistant on the PC side contains information such as platform ID, user ID, certificate ID, etc., which is used for addressing in the case of multiple keys. The unified certificate method on the PC side is as follows: Fig.11 As shown, the details are as follows:

[0107] Install the unified certificate assistant provided by the mutual signing and recognition platform on the user's PC; the unified certificate assistant on the PC dynamically loads the DLL of each service provider through JS to complete the electronic signature.

[0108] The mobile terminal code scanning signature integration method includes the mobile phone scanning signature method and the mobile phone unified certificate assistant method. In the mobile phone scanning signature method, if the CA electronic signature manufacturer platform has issued a large number of mobile digital certificates and has its own signature code scanning APP, it can also not be integrated and packaged, but it is necessary to implement the interface for generating and signing QR codes. When signing, the mutual signing and mutual recognition platform calls the signing service provider's QR code generation interface to obtain the QR code image and display it to the signing user. The user uses the original mobile phone APP to scan the QR code to complete the signature, and the service provider then returns the signature value to the mutual signing and mutual recognition platform. In the mobile phone unified certificate assistant method, the CA electronic signature manufacturer platform service provider needs to encapsulate the acquisition of random numbers, calculation summary, digital signature and other Java interfaces according to the multi-CA resource layer access interface (DCM) specification defined by the mutual signing and mutual recognition platform, and package the Jar package to the mutual signing and mutual recognition platform for encapsulation in the mobile phone unified certificate assistant client. This method is suitable for new business system access and is applicable in scenarios where there is a need for electronic signatures on mobile APP business systems. The mobile phone unified certificate assistant method is as follows Fig.12 shown.

[0109] The specific method of cloud certificate signature integration is as follows: CA electronic signature vendor platform service providers encapsulate the interface RESTful services such as obtaining random numbers, calculating summaries, and digital signatures according to the multi-CA resource layer access interface (DCM) specification defined by the mutual signing and mutual recognition platform. The unified server-side certificate security middleware is integrated with the cloud certificate system and CA of the electronic signature platform service provider, and provides a unified HTTPS API to the upper-level business application system to realize the cloud certificate signature function. Among them, the server-side certificate unified middleware is as follows Fig.13The specific process is as follows: the electronic signature platform service provider performs unified DCM encapsulation and provides a RESTful interface to the mutual signing and mutual recognition platform; the mutual signing and mutual recognition platform uniformly encapsulates the DCM provided by the electronic signature service provider into a unified server certificate middleware.

[0110] In the platform of the embodiment of the present invention, a pilot access application was carried out with the construction integration platform as the business party, and China Construction e-Signature and Construction Easy Signature as CA electronic signature vendor service providers. First, it was adapted and connected with China Construction e-Signature and Construction Easy Signature in seal service and certificate service, and completed the process of CA electronic signature vendor service providers settling in the mutual signing and mutual recognition platform, USBkey adaptation, mobile phone certificate adaptation, cloud certificate adaptation, and verification of the data authorization flow of the signature platform to the mutual signing and mutual recognition platform data, providing the mutual signing and mutual recognition platform with external electronic signature service capabilities. As the business party, the construction integration platform piloted the activation of electronic signatures on the contract management subsystem. First, it completed the interface joint debugging and business joint debugging with the mutual signing and mutual recognition platform, and issued a joint debugging test report. Finally, it was piloted on the construction integration platform, and the external user portal of the mutual signing and mutual recognition platform, the internal user portal of the mutual signing and mutual recognition platform, the unified signing page of the mutual signing and mutual recognition platform, the mutual signing and mutual recognition platform management console, and the multi-CA compatible signature client were accepted. The overall architecture of the pilot application integrated access is as follows: Fig.14 shown.

[0111] In summary, the mutual signing and mutual recognition platform implementation example of the system of the present invention realizes multi-CA compatibility, and realizes that different CA digital certificates can adapt to each other on a unified platform. Compatibility means that the same business platform can adapt to multiple different CA digital certificates, and the new CA digital certificate can also adapt to the platform; mutual recognition means that different business platforms can adapt to CA digital certificates issued by the same electronic certification agency. On the one hand, this effectively reduces the institutional costs of CA handling and renewal for users to connect to different CA agencies across regions, departments, and multiple business systems, and reduces the burden on market entities; on the other hand, it also simplifies the complexity of user CA certificate management. At present, multi-CA compatibility technology has been widely used in provincial and municipal government services, public transaction resource centers, and government bidding and procurement.

[0112] Furthermore, in the mutual signing and mutual recognition platform of the present invention, a digital certificate mutual trust and mutual recognition technology based on a trust list trust model is adopted. The trust list is a dynamic two-dimensional control list set at the application layer. The table lists the root certificates of the trusted CAs, and each CA itself can be a hierarchical structure or a mesh structure. The trust list can be maintained by the application system, and the list contains the certificate chains of all trusted CA organizations. It does not involve the problems at the CA organization level. The mutual trust and mutual recognition problems of digital certificates are solved by technologies such as the application layer configuration dynamic two-dimensional table control list. It is currently widely used in the medical, electric power, and government affairs industries. A certificate chain configuration management module is added to the mutual signing and mutual recognition platform. The certificate chains in the P7b format provided by different CA organizations can be directly imported through the platform to form a certificate chain library. After the certificate is parsed by the multi-Ca compatible client and the server certificate, the certificate is compared with the certificate chain library information of the mutual signing and mutual recognition platform to determine whether it is credible.

[0113] In addition, in the "Electronic Signature Law of the People's Republic of China", electronic signature refers to the data contained or attached in electronic form in a data message for identifying the identity of the signatory and indicating that the signatory approves the content. The mutual signing and mutual recognition platform uses electronic signature technology to realize the mutual signing of electronic signatures under multiple CAs, formulates the signature data format, and requires that after the CA electronic signature manufacturer service platform is connected, the user's private key first performs P1 signature on the document data, and then uniformly sends the p1 signature to the mutual signing and mutual recognition platform, which completes the P7 signature and finally completes the electronic signature of PDF or OFD.

[0114] The present invention also provides a cross-CA electronic signature method, which is implemented based on the system of the present invention. Figure 1 As shown, the following steps are included:

[0115] Step 1: Identify the smart password keys of different CA organizations and obtain digital certificates;

[0116] Step 2: parse the issuer information of the user certificate, determine the issuing authority, and verify the validity of the certificate;

[0117] Step 3: The third-party electronic signature service provider synchronizes the seal data and certificate data by pulling or pushing information based on the signature user;

[0118] Step 4, find the matching certificate and the seal data corresponding to the certificate;

[0119] Step 5: Find the private key corresponding to the signature used by the signing user according to the signing service initiator, application system, seal data, and service provider;

[0120] Step 6: Complete the final signature by finding the seal with the corresponding authority for this business according to the addressing rules.

[0121] Based on the construction of an innovative electronic signature mutual signing and mutual recognition service system of "product + technology + service + management", in response to the new challenges posed by the group's digitalization to the cross-regional, cross-unit and cross-system applications of electronic signatures, the present invention also provides a method for constructing an electronic signature system with cross-CA mutual recognition and mutual signing. By integrating heterogeneous products with technology, a unified electronic signature service middle platform is constructed. Specifically, through the development of an electronic signature mutual signing and mutual recognition platform and a unified signature client, the group's local multi-CA multi-electronic signature access technology standards and interfaces are formulated using the standard specifications of trust list technology, digital certificate technology, electronic signature technology, electronic signature technology, SM2 / SM3 / SM4 national secret algorithms, and RSA international general algorithms. Based on multi-CA signature clients, electronic signature systems, CA digital certificates, and CA digital Certificate media (USBKEY, smart password module) and other products from multiple manufacturers, multiple service providers and different architectures are integrated and built into a unified electronic signature service platform to solve the difficulty of access to different systems from different manufacturers. The mutual trust and mutual recognition of digital certificates are solved by using technologies such as application layer configuration of dynamic two-dimensional table control lists. On the basis of solving the mutual trust and mutual recognition of digital certificates, electronic signature technology is used for docking. The mutual signing and mutual recognition platform provides a unified signing page to encapsulate the signing page and electronic files of various file formats and various signature methods. The digital signature is implemented by the mutual signing and mutual recognition platform integration call of each signature platform manufacturer. The signature equipment provided by each signature platform manufacturer must support the signature component that encapsulates a unified interface in accordance with the national secret GM / T0016, GM / T0020 and other structural specifications. The mutual signing and mutual recognition platform page realizes mutual signing and mutual authentication of different electronic seals on the same file based on the mutual trust and mutual recognition technology of multi-CA compatible digital certificates and electronic signature technology. Further in-depth analysis of the cross-regional, cross-departmental, and cross-system application requirements of digital electronic signatures of enterprises, unified electronic signature access specifications are formulated on the basis of shielding the underlying differences of equipment from different manufacturers, the technical difficulties of electronic signatures and passwords, and unified business system access interfaces, unified electronic signature pages, and unified electronic signature clients are provided to solve the business systems of enterprise groups and their subsidiaries that require access to multiple CAs or multiple electronic signature service providers and the seal usage requirements of users across units and systems on business systems, and to complete the multi-CA and multi-seal access applications in a simple, fast, correct, and compliant manner. The process of the method for constructing a cross-CA mutual recognition and mutual signing electronic signature system of the present invention is as follows: Fig.15 As shown, the following steps are included:

[0122] Step 1: Establish the relationship between each CA electronic signature service provider and the certificate chain provided by the CA institution used by each CA electronic signature service provider, and establish a multi-CA mutual recognition and mutual verification trust list model to verify the digital certificates used by different CA electronic signature service providers;

[0123] Step 2: Establish the relationship between the signature user and each CA electronic signature service provider, and clarify the binding relationship between the signature user and the CA electronic signature service provider;

[0124] Step 3: At the technical level of each CA electronic signature service provider, formulate unified access standards for mutual recognition and trust of CA digital certificates and unified access standards for mutual signing and verification of electronic seals;

[0125] Step 4: Each CA electronic signature service provider develops a standardized interface for CA digital certificates and electronic seals in accordance with access technology standards;

[0126] Step 5: Develop a cross-CA electronic signature mutual recognition, mutual signing and mutual verification application system to provide unified cross-CA electronic signature application standards and specifications for upper-layer business applications;

[0127] Step 6: Develop a USBKEY signature client bridge module to achieve mutual recognition, mutual signing and mutual verification of signature clients of various CA electronic signature service providers, and be compatible with differences in technology; at the same time, establish unified business application access standards and specifications and a unified signing client to provide unified standard technical services for cross-CA electronic signatures in various scenarios.

[0128] Among them, according to the relationship between the certificate chains provided by the CA institutions used by each CA electronic signature service provider established in step 1 and the multi-CA mutual recognition and verification trust list model, according to the relationship between the signature user and each CA electronic signature service provider established in step 2, the standardized interfaces of CA digital certificates and electronic seals developed by each CA electronic signature service provider in step 4 are integrated according to the access technology standards, and a set of standard interfaces including certificate verification, digital signature, signature verification, and seal stamping functions are generated for the upper-level business applications.

[0129] An embodiment of the present invention further provides an electronic device, Fig.16The structure of the electronic device provided by the embodiment of the present invention is shown. For example, the electronic device 160 may include a processor 161, a memory 162 and a transmission device 163. The processor is used to execute the cross-CA electronic signature system construction method mentioned in the above embodiment, wherein the processor and the memory may be connected by a bus or other means, taking the bus connection as an example. The transmission device may be connected to the processor and the memory by wire or wirelessly. The memory, as a non-transient computing device readable storage medium, may be used to store non-transient software programs, non-transient computing device executable programs and modules, such as program instructions / modules corresponding to the cross-CA electronic signature system construction method in the embodiment of the present application. The processor executes various functional applications and data processing of the processor by running the non-transient software programs, instructions and modules stored in the memory, that is, the cross-CA electronic signature system construction method in the above method embodiment is implemented. The memory may include a program storage area and a data storage area, wherein the program storage area may store an operating system and an application required by at least one function; the data storage area may store data created by the processor, etc. In addition, the memory may include a high-speed random access memory, and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and a combination thereof. The one or more modules are stored in the memory, and when executed by the processor, the cross-CA electronic signature system construction method in the embodiment is executed.

[0130] As another aspect, the present application also provides a computing device readable storage medium, which may be the computing device readable storage medium included in the apparatus described in the above embodiment; or it may be a computing device readable storage medium that exists independently and is not assembled into the device. The computing device readable storage medium may be a tangible storage medium, such as a random access memory (RAM), a memory, a read-only memory (ROM), an electrically programmable ROM, an electrically erasable programmable ROM, a register, a floppy disk, a hard disk, a removable storage disk, a CD-ROM, or any other form of storage medium known in the technical field. The computing device readable storage medium stores one or more programs, and the programs are used by one or more processors to execute the cross-CA electronic signature system construction method described in the present application.

[0131] In summary, the above are only preferred embodiments of the present invention and are not intended to limit the protection scope of the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the protection scope of the present invention.

Claims

1. An electronic signature system with cross-CA mutual recognition and signing, characterized in that: include: A bridge module for identifying smart password keys of different CA manufacturers, a manufacturer management module for managing basic information of external CA manufacturers, a certificate chain management module for managing certificate chain information, a CRL list management module for managing CRL addresses, a seal data synchronization module, a certificate data synchronization module, an electronic signature user management module for managing basic information of signature users, a seal data storage module, a certificate data storage module, an application management module, an addressing configuration management module, and a unified signature module; The seal data storage module receives the seal data synchronized by the seal data synchronization module after the electronic signature user authorizes it; The certificate data storage module receives the public key certificate synchronized by the certificate data synchronization module after the electronic signature user authorizes it; The application management module manages the identity authentication identifier and related information of the upper-level business application access system, and is used to verify whether the business application system for the electronic signature user's signature operation has the cross-CA electronic signature capability; Addressing configuration management module, configure application service type, initiator management and policy configuration management, and realize the relationship management of binding initiator, service type and service provider; The unified signature module executes the procedure of different signature users using electronic seals provided by different CA manufacturers to sign the same file across CAs.

2. The system according to claim 1, characterized in that The CA manufacturer basic information includes the application access qualification information provided when the enterprise applies for registration. The manufacturer management module uses the basic information to associate with the certificate chain, seal information, certificate information and user information provided by the third-party CA organization; the bridging module is a USBKEY signature client bridging module, which is used to identify the signature USBKEY provided by different CA electronic signature service manufacturers. The CA electronic signature service manufacturer submits its own JS package according to the established client access standard. The USBKEY signature client bridging module parses and matches the JS package submitted by the CA electronic signature service manufacturer based on the CA electronic signature service manufacturer information associated in the electronic signature service manufacturer management module, and passes the parsed data to the certificate chain management module and the CRL list management module.

3. The system according to claim 2, characterized in that The certificate chain management module is used to manage the certificate chain information provided by the third-party CA organization used by the external CA electronic signature service provider, and is used to establish a trust relationship between the CAs of the public key infrastructure, and can optionally configure an online certificate status query URL address; wherein the certificate chain information and the online certificate status query URL address are verified according to the data transmitted by the USBKEY signature client bridge module, and if the verification fails, the signing user is prompted to use the correct CA digital certificate; The CRL list management module is used to manage the CRL address provided by the third-party CA organization used by the external CA electronic signature service provider, and is used to verify whether the status of the currently used digital certificate is revoked. At the same time, it receives the data passed by the USBKEY signature client bridge module after the verification by the certificate chain management module. If the verification fails, it prompts the result corresponding to the digital certificate status being expired or revoked; After the electronic signature user completes the online authorization consent by manually clicking on the seal data synchronization module, the seal data synchronization module is used to actively pull the electronic seal data that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled electronic seal data in the seal data storage module; After the electronic signature user completes the online authorization consent by manually clicking on the certificate data synchronization module, the certificate data synchronization module is used to actively pull the digital certificate information that the CA electronic signature service provider has processed for the electronic signature user, and store the pulled certificate information in the certificate data storage module; The basic information of the signature user includes user name, whether it is real name, user nature, user status and registration time. If the signature user is not in the electronic signature user management module, the user is guided to complete the registration.

4. The system according to claim 2 or 3, characterized in that Establish the relationship between each CA electronic signature service vendor and the certificate chain provided by the CA institution used by each CA electronic signature service vendor, and establish a multi-CA mutual recognition and verification trust list model to verify the digital certificates used by different CA electronic signature service vendors. Specifically: configure the unique ID relationship between the CA electronic signature service vendor and the unique ID relationship of the CA institution of the CA electronic signature service vendor, and establish a two-dimensional table based on the trust list model.

5. The system according to claim 2 or 3, characterized in that: The system establishes a unified business application access standard specification interface and a unified signature client to provide unified standard technical services for cross-CA electronic signatures in various scenarios. The standard specification interface includes a client interface and a server interface. The client interface includes two parts: one is the signature component js package interface, and the other is the unified signature client interface; Among them, the signature component is uniformly encapsulated into the signature component js package of each CA electronic signature service provider in JavaScript mode. The original CA client of each CA electronic signature service provider does not need to be uninstalled or updated. The upper-layer application passes the signature user and business application through the signature component js package interface to address the signature component js package provided by the corresponding CA electronic signature service provider. The signature component js package is interconnected with the CA client used by the CA electronic signature service provider to parse the certificate and seal in the CA client; The unified signature client interface includes a file signature interface, a signature acquisition link interface, a signature status query interface, a signature document download interface, a signature service revocation interface, a signature reminder interface, a signature document verification interface, a trigger silent signature interface, a bridge interface, a signature service callback interface, a signature process callback interface, a business type acquisition interface, a batch signature interface, a seat tag interface, a keyword signature interface, a seal authorization verification interface and a certificate verification interface; The server interface is aimed at various CA electronic signature service providers and is used for acquiring and verifying seal data and certificate data, including certificate verification interface, signature user synchronization interface, certificate synchronization interface, seal synchronization interface, business type acquisition interface, seal authority query interface, user information query interface and seal usage record synchronization interface.

6. A cross-CA electronic signature method, characterized in that: The method is implemented by a system as claimed in any one of claims 1 to 5, comprising the following steps: Step 1: Identify the smart password keys of different CA organizations and obtain digital certificates; Step 2: parse the issuer information of the user certificate, determine the issuing authority, and verify the validity of the certificate; Step 3: The third-party electronic signature service provider synchronizes the seal data and certificate data by pulling or pushing information based on the signature user; Step 4, find the matching certificate and the seal data corresponding to the certificate; Step 5: Find the private key corresponding to the signature used by the signing user according to the signing service initiator, application system, seal data, and service provider; Step 6: Complete the final signature by finding the seal with the corresponding authority for this business according to the addressing rules.

7. A method for constructing an electronic signature system with cross-CA mutual recognition and signing, characterized in that: The steps include: Step 1: Establish the relationship between each CA electronic signature service provider and the certificate chain provided by the CA institution used by each CA electronic signature service provider, and establish a multi-CA mutual recognition and mutual verification trust list model to verify the digital certificates used by different CA electronic signature service providers; Step 2: Establish the relationship between the signature user and each CA electronic signature service provider, and clarify the binding relationship between the signature user and the CA electronic signature service provider; Step 3: At the technical level of each CA electronic signature service provider, formulate unified access standards for mutual recognition and trust of CA digital certificates and unified access standards for mutual signing and verification of electronic seals; Step 4: Each CA electronic signature service provider develops a standardized interface for CA digital certificates and electronic seals in accordance with access technology standards; Step 5: Develop a cross-CA electronic signature mutual recognition, mutual signing and mutual verification application system to provide unified cross-CA electronic signature application standards and specifications for upper-layer business applications; Step 6: Develop a USBKEY signature client bridge module to achieve mutual recognition, mutual signing and mutual verification of signature clients of various CA electronic signature service providers, and be compatible with differences in technology; at the same time, establish unified business application access standards and specifications and a unified signing client to provide unified standard technical services for cross-CA electronic signatures in various scenarios.

8. The method according to claim 7, characterized in that Based on the relationship between the certificate chains provided by the CA institutions used by each CA electronic signature service provider established in step 1 and the multi-CA mutual recognition and verification trust list model, and based on the relationship between the signature user and each CA electronic signature service provider established in step 2, integrate the standard interfaces of CA digital certificates and electronic seals developed by each CA electronic signature service provider in step 4 in accordance with the access technology standards, and generate a set of standard interfaces for upper-level business applications that include certificate verification, digital signature, signature verification, and seal stamping functions.

9. An electronic device, characterized in that: The electronic device includes a processor and a memory for storing executable instructions of the processor; the processor is used to read the executable instructions from the memory and execute the instructions to implement the method for constructing an electronic signature system for cross-CA mutual recognition and mutual signing as described in claim 7 or 8 above.

10. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and the computer program is used to execute the method for constructing an electronic signature system for mutual recognition and signing across CAs as described in claim 7 or 8 above.

Citation Information

Patent Citations

  • Method for realizing interconnection and intercommunication of multiple CA digital certificates and multiple electronic signatures

    CN116132069A

  • Platform and method for mutual signing and mutual recognizing of electronic signatures

    CN117390693A

  • Method for securely using digital signatures in a commercial cryptographic system

    US5659616A

Cited By

  • Cross-node electronic contract signing method and system based on distributed trust framework

    CN120811781A