Third-party electronic signature implementation method and device, equipment and medium

Abstract

The invention relates to the technical field of electronic signature, and discloses a third-party electronic signature implementation method and device, equipment and a medium, and the method comprises the steps: obtaining a third-party signature application request of a to-be-signed task based on a preset external interface; determining a third-party signature system identifier based on the third-party signature application request; based on the third-party signature system identifier, obtaining application information corresponding to the third-party signature application request; and signing the to-be-signed task based on the application information. According to the scheme, through the external interface and the third-party signature system identification, the abstract degree and the conciseness of the programs are improved, the coupling between the programs is reduced, the expansible flexibility is improved, and the integration cost is reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of electronic signatures, and in particular to a method, device, equipment and medium for implementing a third-party electronic signature. Background Art

[0002] With the rapid development of science and technology, the Internet and online office have become a trend, and the use of electronic signatures and electronic contracts by enterprises has gradually become popular. More and more companies have begun to realize the convenience and efficiency of this technology and have plunged into this wave of digitalization.

[0003] In related technologies, in order to realize the digital office of electronic signatures and electronic contracts, due to certain technical barriers to electronic signatures, technical support provided by third-party electronic signature service platforms is usually used. However, there are endless third-party electronic signature system service platform suppliers, and each is handled by its own different business logic. When it comes to multi-scenario application environments, the coupling between the programs may be high due to the different suppliers of the two businesses, which leads to a complex third-party electronic signature service call process and increases the complexity of third-party electronic signatures. Summary of the invention

[0004] In view of this, the present invention provides a method, device, equipment, and medium for implementing a third-party electronic signature to solve the technical problems in the related art of implementing a third-party electronic signature due to high coupling between programs and complex calling process.

[0005] In the first aspect, the present invention provides a method for implementing a third-party electronic signature, the method comprising: based on a preset external interface, obtaining a third-party signature application request for a task to be signed; based on the third-party signature application request, determining a third-party signature system identifier; based on the third-party signature system identifier, obtaining application information corresponding to the third-party signature application request; based on the application information, implementing the signature of the task to be signed.

[0006] In combination with the first aspect, in a possible implementation method of the first aspect, based on the third-party signature system identifier, obtaining application information corresponding to the third-party signature application request, including: verifying the third-party signature system identifier; in response to the third-party signature system identifier passing the verification, obtaining the signature application, file stream and calling method corresponding to the third-party signature application request based on the third-party signature system identifier.

[0007] In combination with the first aspect, in a possible implementation method of the first aspect, in response to the third-party signature system identifier passing the verification, obtaining the signature application, file stream and calling method corresponding to the third-party signature application request based on the third-party signature system identifier, including: in response to the third-party signature system identifier passing the verification, based on the third-party signature system identifier, traversing the preset cache space, and using the preset interface to determine the signature application, file stream and calling method corresponding to the third-party signature application request.

[0008] In combination with the first aspect, in a possible implementation of the first aspect, the method also includes: creating a cache space and a preset interface; based on the preset interface, determining the correspondence between multiple third-party signature system identifiers and signature applications, file streams, and calling methods; based on the correspondence, storing the corresponding third-party signature system identifiers, signature applications, file streams, and calling methods in groups into the cache space.

[0009] In combination with the first aspect, in a possible implementation method of the first aspect, in response to the third-party signature system identifier passing the verification, after obtaining the signature application, file stream and calling method corresponding to the third-party signature application request based on the third-party signature system identifier, it also includes: parsing the third-party signature system identifier to determine the execution command; and forming an execution result based on the preset correspondence between the execution command and the execution result.

[0010] In combination with the first aspect, in a possible implementation of the first aspect, determining the third-party signature system identifier based on the third-party signature application request includes: determining the corresponding configuration file based on the third-party signature application request; determining the third-party signature system identifier based on the configuration file.

[0011] In combination with the first aspect, in a possible implementation of the first aspect, determining the third-party signature system identifier based on the third-party signature application request includes: parsing the third-party signature application request, and determining the third-party signature system identifier contained in the third-party signature application request.

[0012] In the second aspect, the present invention provides a device for implementing a third-party electronic signature, the device comprising: a request acquisition module, used to obtain a third-party signature application request for a task to be signed based on a preset external interface; a determination module, used to determine a third-party signature system identifier based on the third-party signature application request; an information acquisition module, used to obtain application information corresponding to the third-party signature application request based on the third-party signature system identifier; a signature module, used to implement the signature of the task to be signed based on the application information.

[0013] In a third aspect, the present invention provides a computer device, comprising: a memory and a processor, the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for implementing a third-party electronic signature according to the first aspect or any corresponding embodiment thereof by executing the computer instructions.

[0014] In a fourth aspect, the present invention provides a computer-readable storage medium having computer instructions stored thereon, the computer instructions being used to enable a computer to execute the method for implementing a third-party electronic signature according to the first aspect or any corresponding embodiment thereof.

[0015] The technical solution of the present invention has the following advantages: The present invention provides a method, device, equipment, and medium for implementing a third-party electronic signature. The method obtains a third-party signature application request through a preset external interface, and determines a third-party signature system identifier, so as to complete the signature of the task to be signed with the application information corresponding to the third-party signature application request. In this process, a unified external interface is used to obtain the third-party signature application request, determine the third-party signature system identifier, and then obtain the application information through the third-party signature system identifier. The interface parameters and the return data format are defined by a unified interface to complete the implementation of multiple signatures, and the third-party electronic signature program is abstracted as the association between the third-party signature system identifier and the application information, which improves the simplicity of the method, reduces the business logic association between different signature suppliers, and thus improves the simplicity of the method, reduces the coupling between programs, and because the methods are integrated by a unified external interface, the scalability flexibility is improved and the integration cost is reduced. BRIEF DESCRIPTION OF THE DRAWINGS

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

[0017] Figure 1 It is a flowchart of a method for implementing a third-party electronic signature provided according to an embodiment of the present invention; Figure 2 This is a structural block diagram of a device for implementing a third-party electronic signature according to an embodiment of the present invention; Figure 3 It is a schematic diagram of the hardware structure of a computer device according to an embodiment of the present invention. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solution and advantages of the embodiments of the present invention clearer, the technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the described embodiments are part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present invention.

[0019] According to an embodiment of the present invention, an embodiment of a method for implementing a third-party electronic signature is provided. It should be noted that the steps shown in the flowchart of the accompanying drawings can be executed in a computer system such as a set of computer executable instructions, and although a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in an order different from that shown here.

[0020] This embodiment provides a method for implementing a third-party electronic signature. Figure 1 As shown, the method comprises the following steps: S101. Based on a preset external interface, obtain a third-party signature application request for the task to be signed.

[0021] Specifically, the preset external interface refers to a uniformly defined interface, which is recorded as a rest interface. The third-party signature application request for the task to be signed refers to the acquisition request for the task to be signed corresponding to the signature application, file stream and calling method. For example, the server publishes the rest interface to the outside, and the browser client accesses the server through the rest interface, that is, the browser client sends the third-party signature application request for the task to be signed to the server through the rest interface, so that the server calls the corresponding implementation class according to the passed parameters.

[0022] S102: Determine the third-party signature system identifier based on the third-party signature application request.

[0023] Specifically, based on the third-party signature application request, determining the third-party signature system identifier means obtaining the third-party signature system identifier through the third-party signature application request, thereby clarifying the third-party electronic signature system to be used, wherein the third-party signature system identifier refers to the identification information set by the third-party electronic signature system service platform provider, and the identifier can be used to determine which third-party electronic signature system to use.

[0024] Specifically, determining the third-party signature system identifier based on the third-party signature application request includes determining the third-party signature system identifier based on the third-party signature application request in the form of a configuration file; or determining the third-party signature system identifier by parsing the third-party signature application request in the form of data parameter transmission. It should be understood that both methods can determine the third-party signature system identifier, and the difference lies in the transmission method of the third-party signature system identifier, that is, writing it into a configuration file or transmitting it in the form of parameter transmission.

[0025] S103: Based on the third-party signature system identifier, obtain application information corresponding to the third-party signature application request.

[0026] Specifically, based on the third-party signature system identifier, obtaining the application information corresponding to the third-party signature application request means verifying the third-party signature system identifier. After the third-party signature system identifier passes the verification, the preset interface is used to determine the signature application, file flow and calling method, wherein the preset interface refers to the preset calling interface, recorded as SignApplyServices, which defines the signature file FileParams and the signature application information SignApplyParams, and constrains the method transmission and return data types, so that the method defined in the interface is extensible. And when the execution command is included in the third-party signature system identifier, an execution result corresponding to the execution command is formed.

[0027] S104. Based on the application information, the tasks to be signed are signed.

[0028] Specifically, based on the application information, implementing the signature of the task to be signed means returning the determined signature application, file stream, and calling method in the form of constraints, so that the task to be signed obtains the corresponding data and completes the signature of the task.

[0029] The present invention provides a method, device, equipment, and medium for implementing a third-party electronic signature. The method obtains a third-party signature application request through a preset external interface, and determines a third-party signature system identifier, so as to complete the signature of the task to be signed with the application information corresponding to the third-party signature application request. In this process, a unified external interface is used to obtain the third-party signature application request, determine the third-party signature system identifier, and then obtain the application information through the third-party signature system identifier. The interface parameters and the return data format are defined by a unified interface to complete the implementation of multiple signatures, and the third-party electronic signature program is abstracted as the association between the third-party signature system identifier and the application information, which improves the simplicity of the method, reduces the business logic association between different signature suppliers, and thus improves the simplicity of the method, reduces the coupling between programs, and because the methods are integrated by a unified external interface, the scalability flexibility is improved and the integration cost is reduced.

[0030] In an optional implementation, based on the third-party signature system identifier, obtaining application information corresponding to the third-party signature application request includes: Verify the third-party signature system identifier; in response to the third-party signature system identifier passing the verification, obtain the signature application, file flow and calling method corresponding to the third-party signature application request based on the third-party signature system identifier.

[0031] Specifically, verifying the third-party signature system identifier refers to matching and verifying the third-party signature system identifier to determine whether it matches the supplier's correct identifier. When the third-party signature system identifier has a corresponding supplier's correct identifier, the third-party signature system identifier is considered to have passed the verification.

[0032] Specifically, in response to the third-party signature system identifier passing verification, obtaining the signature application, file flow and calling method means that when the third-party signature system identifier passes verification, the signature application, file flow and calling method are determined using the preset interface, wherein the preset interface refers to the preset calling interface SignApplyServices in the above embodiment, thereby obtaining the signature file FileParams and the signature application information SignApplyParams and the calling method through the preset calling interface. Among them, the calling method refers to the implementation class provided by the integrated third-party electronic signature system service platform according to the respective business logic, for example, respectively recorded as SignApplyServicesImpl1, SignApplyServicesImpl2, etc., thereby implementing all methods in the preset calling interface SignApplyServices, and returning the corresponding parameters in the form of a call.

[0033] In an optional implementation, in response to the third-party signature system identifier passing verification, obtaining a signature application, a file stream, and a calling method corresponding to the third-party signature application request based on the third-party signature system identifier includes: In response to the third-party signature system identifier being verified, based on the third-party signature system identifier, the preset cache space is traversed, and the signature application, file stream and calling method corresponding to the third-party signature application request are determined using a preset interface.

[0034] Specifically, in response to the third-party signature system identifier passing the verification, determining the cache space means determining the corresponding cache space when the third-party signature system identifier passes the verification, wherein the cache space is used to store the third-party signature system identifier and the signature application, file stream, and calling method, and there is a corresponding relationship between the third-party signature system identifier and the signature application, file stream, and calling method.

[0035] Specifically, based on the third-party signature system identifier, traversing the cache space, and utilizing the preset interface to determine the signature application, file flow, and calling method means utilizing the correspondence between the third-party signature system identifier and the signature application, file flow, and calling method, traversing the cache space, and determining the signature application, file flow, and calling method corresponding to the third-party signature system identifier. Since the preset interface defines the signature application and file flow, and constrains the calling method, the preset interface returns data that meets the definition and constraints, i.e., the signature application, file flow, and calling method are determined.

[0036] In an optional implementation, the method also includes: creating a cache space and a preset interface; based on the preset interface, determining the correspondence between multiple third-party signature system identifiers and signature applications, file streams, and calling methods; based on the correspondence, storing the corresponding third-party signature system identifiers, signature applications, file streams, and calling methods in groups into the cache space.

[0037] Specifically, based on the preset interface, determining the correspondence between the third-party seal system identifier and the seal application, file flow, and calling method means that since the preset interface defines the seal application and file flow, and constrains the implementation class, the preset interface is used to determine the corresponding seal application, file flow, and calling method with the third-party seal system identifier, thereby forming a correspondence between the third-party seal system identifier and the seal application, file flow, and calling method.

[0038] Specifically, the cache space is represented as Map<String, SignApplyServices> , where map here refers to ConcurrentHashMap, and String here represents the data type of the third-party signature system identifier. Based on the corresponding relationship, the third-party signature system identifier, signature application, file stream, and calling method are stored in the cache space in groups, providing a data basis for subsequent traversal of the cache space and determining the signature application, file stream, and calling method.

[0039] In an optional implementation, in response to the third-party signature system identifier passing verification, after obtaining the signature application, file stream and calling method corresponding to the third-party signature application request based on the third-party signature system identifier using a preset interface, the method further includes: Parse the third-party signature system identifier to determine the execution command; form the execution result based on the preset correspondence between the execution command and the execution result.

[0040] Specifically, parsing the third-party signature system identifier and determining the execution command means that when the execution command is included in the third-party signature system identifier, the corresponding execution command is obtained by parsing the third-party signature system identifier. For example, the execution command may be a log record, and the execution result corresponding to the log record is a log record, thereby forming a log record. It should be understood that including the execution command in the third-party signature system identifier means determining whether the third-party signature system identifier contains the corresponding logical processing operation, and when it is included, determining the corresponding implementation branch according to the third-party signature system identifier, thereby forming an execution result.

[0041] In an optional implementation, determining the third-party signature system identifier based on the third-party signature application request includes: Based on the third-party signature application request, determine the corresponding configuration file; based on the configuration file, determine the third-party signature system identifier.

[0042] Specifically, based on the third-party signature application request, determining the corresponding configuration file means that the third-party signature system identifier is transmitted by writing into the configuration file, thereby determining the third-party signature system identifier in the form of a configuration file, that is, in this method, the third-party signature system identifier is determined by reading the configuration file.

[0043] In an optional implementation, determining the third-party signature system identifier based on the third-party signature application request includes: Parse the third-party signature application request and determine the third-party signature system identifier contained in the third-party signature application request.

[0044] Specifically, parsing the third-party signature application request and determining the third-party signature system identifier corresponding to the third-party signature application request means that the third-party signature system identifier is transmitted by means of parameters, thereby determining the third-party signature system identifier by parsing the third-party signature application request, that is, in this method, the third-party signature system identifier is determined by parsing the third-party signature application request.

[0045] In this embodiment, a third-party electronic signature implementation device is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can implement a combination of software and / or hardware for a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.

[0046] This embodiment provides a third-party electronic signature implementation device, such as Figure 2 As shown, including: The request acquisition module 201 is used to acquire a third-party signature application request for a task to be signed based on a preset external interface. The specific process can be found in the description of step S101 in the above embodiment, which will not be repeated here.

[0047] The determination module 202 is used to determine the third-party signature system identifier based on the third-party signature application request. The specific process can be found in the description of step S102 in the above embodiment, which will not be repeated here.

[0048] The information acquisition module 203 is used to acquire application information corresponding to the third-party signature application request based on the third-party signature system identifier. The specific process can be found in the description of step S103 in the above embodiment, which will not be repeated here.

[0049] The signature module 204 is used to implement the signature of the task to be signed based on the application information. The specific process can be found in the description of step S104 in the above embodiment, which will not be repeated here.

[0050] The implementation device of the third-party electronic signature in this embodiment is presented in the form of a functional unit, where the unit refers to an ASIC (Application Specific Integrated Circuit) circuit, a processor and memory that executes one or more software or fixed programs, and / or other devices that can provide the above functions.

[0051] The embodiment of the present invention also provides a computer device having the above Figure 2 The implementation device of the third-party electronic signature shown in FIG. Figure 3 , Figure 3 is a schematic diagram of the structure of a computer device provided by an optional embodiment of the present invention, such as Figure 3 As shown, the computer device includes: one or more processors 301, memory 302, and interfaces for connecting various components, including high-speed interfaces and low-speed interfaces. Various components utilize different buses to communicate with each other, and can be installed on a common mainboard or installed in other ways as needed. The processor can process the instructions executed in the computer device, including instructions stored in the memory or on the memory to display the graphical information of the GUI on an external input / output device (such as, a display device coupled to the interface). In some optional embodiments, if necessary, multiple processors and / or multiple buses can be used together with multiple memories and multiple memories. Similarly, multiple computer devices can be connected, and each device provides part of the necessary operations (for example, as a server array, a group of blade servers, or a multi-processor system). Figure 3 A processor 301 is taken as an example.

[0052] The processor 301 may be a central processing unit, a network processor or a combination thereof. The processor 301 may further include a hardware chip. The hardware chip may be a dedicated integrated circuit, a programmable logic device or a combination thereof. The programmable logic device may be a complex programmable logic device, a field programmable logic gate array, a general purpose array logic or any combination thereof.

[0053] The memory 302 stores instructions executable by at least one processor 301, so that the at least one processor 301 executes the method shown in the above embodiment.

[0054] The memory 302 may include a program storage area and a data storage area, wherein the program storage area may store an operating system, an application required for at least one function; the data storage area may store data created according to the use of the computer device, etc. In addition, the memory 302 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 optional embodiments, the memory 302 may optionally include a memory remotely arranged relative to the processor 301, and these remote memories may be connected to the computer device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0055] The memory 302 may include a volatile memory, such as a random access memory; the memory may also include a non-volatile memory, such as a flash memory, a hard disk or a solid state drive; the memory 302 may also include a combination of the above types of memory. The computer device also includes a communication interface 303, which is used for the computer device to communicate with other devices or communication networks.

[0056] The embodiment of the present invention also provides a computer-readable storage medium. The method according to the embodiment of the present invention can be implemented in hardware, firmware, or can be implemented as a computer code that can be recorded in a storage medium, or can be implemented as a computer code that is originally stored in a remote storage medium or a non-temporary machine-readable storage medium and will be stored in a local storage medium through a network download, so that the method described herein can be stored in such software processing on a storage medium using a general-purpose computer, a dedicated processor, or programmable or dedicated hardware. Among them, the storage medium can be a magnetic disk, an optical disk, a read-only storage memory, a random access memory, a flash memory, a hard disk or a solid-state hard disk, etc.; further, the storage medium can also include a combination of the above types of memories. It can be understood that a computer, a processor, a microprocessor controller, or programmable hardware includes a storage component that can store or receive software or computer code. When the software or computer code is accessed and executed by a computer, a processor, or hardware, the method shown in the above embodiment is implemented.

[0057] Although the embodiments of the present invention have been described in conjunction with the accompanying drawings, those skilled in the art may make various modifications and variations without departing from the spirit and scope of the present invention, and such modifications and variations are all within the scope defined by the appended claims.

Claims

1. A method for implementing a third-party electronic signature, characterized in that: The method comprises: Based on the preset external interface, obtain the third-party signature application request for the task to be signed; Determine a third-party signature system identifier based on the third-party signature application request; Based on the third-party signature system identifier, obtaining application information corresponding to the third-party signature application request; Based on the application information, the task to be signed is signed.

2. The method according to claim 1, characterized in that The acquiring, based on the third-party signature system identifier, application information corresponding to the third-party signature application request includes: Verify the third-party signature system identification; In response to the third-party signature system identifier passing verification, a signature application, a file stream, and a calling method corresponding to the third-party signature application request are acquired based on the third-party signature system identifier.

3. The method according to claim 2, characterized in that In response to the third-party signature system identifier being verified, obtaining a signature application, a file stream, and a calling method corresponding to the third-party signature application request based on the third-party signature system identifier, including: In response to the third-party signature system identifier being verified, based on the third-party signature system identifier, a preset cache space is traversed, and a preset interface is used to determine a signature application, a file stream, and a calling method corresponding to the third-party signature application request.

4. The method according to claim 3, characterized in that The method also includes: Create cache space and preset interface; Based on the preset interface, determine the correspondence between multiple third-party signature system identifiers and signature applications, file flows, and calling methods; Based on the corresponding relationship, the corresponding third-party signature system identifier, the signature application, the file stream, and the calling method are stored in the cache space as a group.

5. The method according to claim 2, characterized in that: In response to the third-party signature system identifier being verified, after acquiring the signature application, file stream, and calling method corresponding to the third-party signature application request based on the third-party signature system identifier, the method further includes: Parse the third-party signature system identifier and determine the execution command; Based on the preset correspondence between the execution command and the execution result, an execution result is formed.

6. The method according to claim 1, characterized in that The determining of the third-party signature system identifier based on the third-party signature application request includes: Determine a corresponding configuration file based on the third-party signature application request; Based on the configuration file, a third-party signing system identifier is determined.

7. The method according to claim 1, characterized in that The determining of the third-party signature system identifier based on the third-party signature application request includes: The third-party signature application request is parsed to determine the third-party signature system identifier included in the third-party signature application request.

8. A device for implementing a third-party electronic signature, characterized in that: The device comprises: The request acquisition module is used to obtain the third-party signature application request for the task to be signed based on the preset external interface; A determination module, used to determine a third-party signature system identifier based on the third-party signature application request; An information acquisition module, used to acquire application information corresponding to the third-party signature application request based on the third-party signature system identifier; The signature module is used to sign the task to be signed based on the application information.

9. A computer device, characterized in that: include: A memory and a processor, wherein the memory and the processor are communicatively connected to each other, the memory stores computer instructions, and the processor executes the method for implementing a third-party electronic signature according to any one of claims 1 to 7 by executing the computer instructions.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a computer to execute the method for implementing a third-party electronic signature according to any one of claims 1 to 7.

Images