Electronic signature method, system and device based on file scheduling distribution and storage medium

Abstract

The application belongs to the technical field of electronic signature, and discloses an electronic signature method, system, device and storage medium based on file scheduling distribution. The method comprises the following steps: an electronic file signature node is registered to an electronic file signature scheduling center; the electronic file signature scheduling center maintains a node table according to the registration condition; the electronic file signature scheduling center receives a batch file signing request initiated by a client, splits the batch file, and determines the scores of each electronic file signature node according to the node table; the best electronic file signature node of each split single file is determined based on the scores; finally, the single file is distributed to the corresponding best electronic file signature node for processing to complete the signature. Through the above signature scheduling distribution mode, the problem that a large number of files are signed slowly in a single node due to a request submission is solved, the device resources are effectively utilized, and the signature experience and efficiency are improved.

Description

Technical Field

[0001] This invention relates to the field of electronic signature technology, and in particular to an electronic signature method, system, device and storage medium based on file scheduling and distribution. Background Technology

[0002] In current engineering document review and bidding processes, there is a need to complete the signing of a large number of existing documents in the system at once. The current approach to handling large-scale document signing is to sign one document at a time and then proceed to the next in a loop, or to initiate a batch of document signing tasks at once. However, the service backend also processes these documents sequentially, and it is still necessary to wait for each document to be processed.

[0003] This electronic signature method suffers from severe waiting issues, which slows down the review and processing speed of various processes and also results in periods of service idleness.

[0004] The above content is only used to help understand the technical solution of the present invention and does not represent an admission that the above content is prior art. Summary of the Invention

[0005] The main objective of this invention is to provide an electronic signature method, system, device, and storage medium based on file scheduling and distribution, aiming to solve the technical problems of serious waiting situations in current electronic signature methods, which reduce the review and processing speed of various processes and also result in some service idle situations.

[0006] To achieve the above objectives, the present invention provides an electronic signature method based on file scheduling and distribution, the electronic signature method based on file scheduling and distribution comprising the following steps:

[0007] Receive the registration message issued by the electronic document signing node cluster, and update the node table according to the registration message;

[0008] Receive a batch file signing request sent by the client, and in response to the signing request, split the batch file into individual files;

[0009] Based on the node table and the business data of each individual file, the target electronic document signing node corresponding to each individual file in the electronic document signing node cluster is determined, and each individual file is distributed to the corresponding target electronic document signing node.

[0010] Obtain the original signature text and business routing identifier data fed back by each target electronic document signature node, and send the original signature text and the business routing identifier data to the client;

[0011] The system receives encapsulated data from the client, parses the encapsulated data to determine the target electronic document signing node corresponding to each signing result, and sends the target electronic document signing node in response to the signing completion request sent by the client. The target electronic document signing node merges the signing result with the corresponding single document based on the signing completion request to complete the electronic signature of each single document. The encapsulated data consists of the signing result and the business routing identifier data, and the signing result is obtained by the client signing the original signature text.

[0012] In some embodiments, before receiving the registration message issued by the electronic document signing node cluster and updating the node table according to the registration message, the method further includes:

[0013] When the signing service is started, the electronic document signing node cluster reads the physical hardware information of the current device and the configuration information related to the node to generate a registration message. The registration message is sent to the electronic document signing scheduling center based on the UPD communication method. After a preset period of time, the physical hardware information of the current device and the configuration information related to the node are read again to generate a new registration message.

[0014] In some embodiments, the node table is used to record data information of each electronic document signing node. The data information includes at least the unique identifier of the service node, the node's registration address, server hardware information, the number of file tasks currently being processed by the service, the total size of the electronic files being processed by the tasks, CPU configuration, and memory configuration information. The node table is updated in real time based on the registration message, and the load data related to the node table is updated based on the signing status of each electronic document signature.

[0015] In some embodiments, the method further includes:

[0016] After distributing each single file to the corresponding target electronic document signing node, the number of processing tasks, the size of the processed files, and the acceptance time of the corresponding electronic document signing node service in the node table are updated.

[0017] After obtaining the original signature text and business routing identifier data returned by each target electronic document signing node, the number of processing tasks and the size of the processed files of the corresponding electronic document signing node service in the node table are updated again to complete the update of the load data of the node table.

[0018] In some embodiments, determining the target electronic document signing node corresponding to each single file in the electronic document signing node cluster based on the node table and the business data of each single file includes:

[0019] For any single file, obtain the file size of each electronic document signing node in the electronic document signing node cluster and the file size processed by each electronic document signing node;

[0020] Based on the node table, obtain the available disk space, memory capacity, number of CPU cores, and number of task threads being processed for each electronic document signature node;

[0021] The score of each electronic document signing node is calculated based on the file size of each electronic document signing node in the single file input electronic document signing node cluster, the file size processed by each electronic document signing node, the available disk space, the memory capacity, the number of CPU cores, and the number of task threads being processed.

[0022] The electronic document signature node with the highest score is selected as the target electronic document signature node for the single file.

[0023] In some embodiments, calculating the score of each electronic document signing node based on the file size of each electronic document signing node in the single file input electronic document signing node cluster, the file size processed by each electronic document signing node, the available disk space, the memory capacity, the number of CPU cores, and the number of task threads being processed includes:

[0024] The disk coefficient score is calculated by combining a preset disk ratio coefficient with the file size of each electronic document signing node in the electronic document signing node cluster, the file size processed by each electronic document signing node, and the available disk space.

[0025] The memory coefficient score is calculated by combining a preset memory ratio coefficient with the file size of each electronic document signing node in the electronic document signing node cluster, the file size processed by each electronic document signing node, and the memory capacity.

[0026] The CPU coefficient score is calculated by combining the file size of each electronic document signing node in the electronic document signing node cluster based on the single file input, the file size processed by each electronic document signing node, the number of CPU cores, and the number of task threads being processed.

[0027] The total score is calculated by combining the preset ratio coefficients of each electronic document signing node with the disk coefficient score, the memory coefficient score, and the CPU coefficient score.

[0028] Accordingly, the step of selecting the electronic document signing node with the highest score as the target electronic document signing node for the single file includes:

[0029] The electronic document signature node with the highest total score is selected as the target electronic document signature node for the individual document.

[0030] In some embodiments, the business routing identification data is used to identify the electronic document signing node corresponding to the signing of the distributed single document. The business routing identification data is obtained by concatenating the identifier of the electronic document signing node, the task identifier of the electronic document signing node, and the contract document identifier of the single document and then performing Hex encoding.

[0031] Furthermore, to achieve the above objectives, the present invention also proposes an electronic signature system based on file scheduling and distribution, which includes: a client, an electronic document signature scheduling center, and an electronic document signature node cluster;

[0032] The electronic document signature scheduling center is used to receive the registration message issued by the electronic document signature node cluster and update the node table according to the registration message;

[0033] The electronic document signing scheduling center is used to receive batch file signing requests sent by the client, and in response to the signing requests, split the batch files into individual files;

[0034] The electronic document signature scheduling center is used to determine the target electronic document signature node corresponding to each single file in the electronic document signature node cluster based on the node table and the business data of each single file, and to distribute each single file to the corresponding target electronic document signature node.

[0035] The electronic document signature scheduling center is used to obtain the original signature text and business routing identifier data fed back by each target electronic document signature node, and send the original signature text and the business routing identifier data to the client.

[0036] The electronic document signature scheduling center is used to receive the encapsulated data fed back by the client, parse the encapsulated data to determine the target electronic document signature node corresponding to each signing result, and send the target electronic document signature node in response to the signing completion request sent by the client. The target electronic document signature node merges the signature result with the corresponding single document based on the signing completion request to complete the signing of the electronic signature of each single document. The encapsulated data consists of the signing result and the business routing identifier data, and the signing result is obtained by the client signing the original signature text.

[0037] Furthermore, to achieve the above objectives, the present invention also proposes an electronic signature device based on file scheduling and distribution, the electronic signature device based on file scheduling and distribution comprising: a memory, a processor, and an electronic signature program based on file scheduling and distribution stored on the memory and executable on the processor, the electronic signature program based on file scheduling and distribution being configured to implement the steps of the electronic signature method based on file scheduling and distribution as described above.

[0038] Furthermore, to achieve the above objectives, the present invention also proposes a storage medium storing a file-based scheduling and distribution electronic signature program, which, when executed by a processor, implements the steps of the file-based scheduling and distribution electronic signature method described above.

[0039] This invention receives registration messages from an electronic document signing node cluster and updates the node table based on these messages; it receives batch file signing requests from clients and, in response to these requests, splits the batch files into individual files; it determines the target electronic document signing nodes for each individual file in the cluster based on the node table and the business data of each individual file, and distributes each individual file to its corresponding target electronic document signing node; it obtains the original signature text and business routing identifier data from each target electronic document signing node and sends these text and data to the client; it receives encapsulated data from the client, parses the encapsulated data to determine the target electronic document signing node for each signing result, and, in response to the client's signing completion request, sends the data to the target electronic document signing node; each target electronic document signing node merges the signing result with the corresponding individual file based on the signing completion request to complete the electronic signature of each individual file. This signature scheduling and distribution method solves the problem of slow signing caused by a single node processing a large batch of files submitted for signing in a single request, effectively utilizing device resources and improving the signing experience and efficiency. Attached Figure Description

[0040] Figure 1 This is a flowchart illustrating the first embodiment of the electronic signature method based on file scheduling and distribution according to the present invention.

[0041] Figure 2 This is a sequence diagram of the overall batch signature business in the electronic signature method based on file scheduling and distribution of the present invention;

[0042] Figure 3 This is a schematic diagram of the system architecture in the electronic signature method based on file scheduling and distribution of the present invention;

[0043] Figure 4This is a timing diagram of node table updates in the electronic signature method based on file scheduling and distribution of the present invention;

[0044] Figure 5 This is a schematic diagram of the signature node registration message structure in the electronic signature method based on file scheduling and distribution of the present invention;

[0045] Figure 6 This is a schematic diagram of the node table structure in the electronic signature method based on file scheduling and distribution of the present invention;

[0046] Figure 7 This is a structural block diagram of the first embodiment of the electronic signature system based on file scheduling and distribution of the present invention.

[0047] The realization of the objective, functional features and advantages of the present invention will be further explained in conjunction with the embodiments and with reference to the accompanying drawings. Detailed Implementation

[0048] It should be understood that the specific embodiments described herein are for illustrative purposes only and are not intended to limit the scope of the invention.

[0049] This invention provides an electronic signature method based on file scheduling and distribution, referring to... Figure 1 , Figure 1 This is a flowchart illustrating the first embodiment of an electronic signature method based on file scheduling and distribution according to the present invention.

[0050] In this embodiment, the electronic signature method based on file scheduling and distribution includes the following steps:

[0051] Step S10: Receive the registration message issued by the electronic document signing node cluster, and update the node table according to the registration message.

[0052] In this embodiment, the executing entity is an electronic signature device based on file scheduling and distribution. This electronic signature device based on file scheduling and distribution has functions such as data processing, data communication, and program execution. The electronic signature device based on file scheduling and distribution can be a computer terminal device or other network device, or other devices with similar functions. This embodiment does not limit the scope of such devices.

[0053] It should be noted that the current method for handling large-volume document signing is to sign one document at a time and then move on to the next, or to initiate a batch of document signing tasks at once. However, the service backend also processes these documents sequentially, and it is still necessary to wait for each document to be processed. This electronic signature method has serious waiting issues, which reduces the review and processing speed of various processes and also results in some service idle periods.

[0054] To address the aforementioned technical issues, this embodiment receives a registration message from the electronic document signing node cluster and updates the node table based on the registration message; receives a batch file signing request from the client and, in response to the signing request, splits the batch files into individual files; determines the target electronic document signing node corresponding to each individual file in the electronic document signing node cluster based on the node table and the business data of each individual file, and distributes each individual file to the corresponding target electronic document signing node; obtains the original signature text and business routing identifier data fed back by each target electronic document signing node, and sends the original signature text and the business routing identifier data to the client; receives encapsulated data fed back by the client, parses the encapsulated data to determine the target electronic document signing node corresponding to each signing result, and, in response to the signing completion request sent by the client, sends the target electronic document signing node; and, through each target electronic document signing node, merges the signing result with the corresponding individual file based on the signing completion request to complete the electronic signature of each individual file. This signature scheduling and distribution method solves the problem of slow signing caused by a single node processing a large batch of files submitted for signing in a single request, effectively utilizing device resources and improving the signing experience and efficiency. Specifically, it can be implemented as follows.

[0055] In this specific implementation, the overall technical solution is first described. Specifically, the user uses a mobile terminal or PC client to select the documents to be signed in batches, applies the signing coordinate template, and initiates a batch document signing request. The electronic document signature scheduling center receives the batch document signing request, parses the request file list, and constructs the batch document business requests into individual single-file business data messages. Based on the signature node table, it calculates the optimal processing node for each business and distributes the business data messages to the designated electronic document signature nodes for processing. In this embodiment, the above method is implemented using an electronic signature system based on file scheduling and distribution. This system consists of a client, an electronic document signature scheduling center, and an electronic document signature node cluster. The specific interaction process among the three can be referred to... Figure 2 As shown, the specific system architecture can be found by referring to... Figure 3 As shown.

[0056] In the specific implementation, the electronic document signing node cluster automatically registers. When the signing service starts, the electronic document signing node cluster reads the physical hardware information of the current device and the configuration information related to the node to generate a registration message. The registration message is sent to the electronic document signing scheduling center based on the UPD communication method. After a preset period of time, the cluster rereads the physical hardware information of the current device and the configuration information related to the node to generate a new registration message.

[0057] It should be noted that UPD communication is a stateless transport protocol. Compared to TCP, which lacks mechanisms such as handshakes, acknowledgments, windowing, retransmissions, and congestion control, UPD communication improves the processing efficiency of electronic signatures. The preset period can be set to 30 seconds, meaning that every 30 seconds, the physical hardware information of the current device and the node's configuration information are reread to generate a new registration message. Furthermore, if the electronic document signature scheduling center does not receive a registration message for more than 3 minutes, the node will be removed from the list.

[0058] After receiving the registration message, the electronic document signature scheduling center can update the node table using this message. This node table records the data information of each electronic document signing node, including at least the unique identifier of the service node, the node's registration address, server hardware information, the number of file tasks currently being processed, the total size of the electronic files being processed, CPU configuration, and memory configuration information. The node table is updated in real time based on the registration message, and the load data related to the node table is updated based on the signing status of each electronic document signature. The node table update process can be referenced... Figure 4 As shown, after an electronic document signing node starts, it periodically generates and constructs registration data packets, for example every 30 seconds. The generation of these data packets relies on the node's device information. After constructing the packet, the node sends it to the registration center via the UDP protocol. UDP is used because it is a stateless transport protocol, lacking mechanisms like handshakes, acknowledgments, windowing, retransmissions, and congestion control compared to TCP, making it very fast for data transmission and well-suited for this type of data packet. Upon receiving the registration packet, the scheduling center parses and processes it according to the agreed-upon data packet format to obtain the relevant node's basic device information. After completion, the data is updated in the node table maintained by the scheduling center. Simultaneously, the scheduling center sends signing task packets to the nodes, updating the node load information in the node table based on the task details and file size. Once the node completes processing, the scheduling center, upon receiving the completion message, updates the load table, releasing the previous load data for the task. The data in this node table allows us to obtain the device information, configuration details, and load status of all nodes in the system, facilitating optimal distribution and scheduling of electronic file tasks during the scheduling process.

[0059] Furthermore, in this embodiment, the message structure of the registration message is a byte array. The specific byte data is defined as follows: version identifier (1 byte); message type (2 bytes); timestamp (8 bytes); node number (16 bytes); node name (64 bytes); node IP address (4 bytes); node port address (2 bytes); node software version (2 bytes); node ratio coefficient (2 bytes); number of CPU cores (2 bytes); CPU ratio coefficient (2 bytes); memory capacity (16 bytes); memory ratio coefficient (2 bytes); available disk space (16 bytes); disk ratio coefficient (2 bytes). For details, please refer to... Figure 5 As shown.

[0060] Furthermore, the registration information contained in the node table can be referenced. Figure 6As shown, the specific content includes the following: Node Number: A unique number used to identify the node; Node Name: Identifies the node; Node Address: Records the node's access address, used for access by the scheduling center; Node Software Version: Records the software version number of the node's electronic signature service. If the version is too old or incompatible, related task messages will not be forwarded to the node; Node Ratio System: This parameter is manually configured when a node goes online. The larger the value, the higher the task ratio assigned to the node. If set to 0, the node will not receive task messages. It is usually used to reduce the ratio system when preparing to take the service offline, so that the scheduling center will no longer send tasks to the node; CPU Cores: Records the number of CPU cores on the node machine. Generally, the more cores, the more task messages received; CPU Ratio Coefficient: Configures the CPU ratio. If the CPU performance is good, this parameter can be increased. Generally, with the same number of CPU cores, the larger the ratio coefficient, the more task messages received; Memory Capacity: Records the CPU memory information on the node machine. Generally, the larger the memory capacity, the more task messages received; Memory Ratio Coefficient: Configures the memory ratio. If memory performance is good, this parameter can be increased. Generally, with the same memory capacity, a larger ratio coefficient will result in a larger number of received task messages. Disk available space: Records the available disk space on the node machine. Generally, a larger available disk space will result in a larger number of received task messages. Disk ratio coefficient: Configures the disk ratio. If disk performance is good (e.g., using a solid-state drive), this parameter can be increased. With the same available disk space, a larger ratio coefficient will result in a larger number of received task messages. Synchronization time point: Records the most recent synchronization time of this node. If a node does not receive a synchronization message within a specified time, the configuration center will determine that the node service is abnormal and suspend task message distribution to this node. Number of tasks in processing: Records the number of tasks currently being processed on the node, reflecting the task load information of this node. If the processing load is too high, the number of received task messages will decrease. Total size of files being processed: Records the total size of tasks currently being processed on the node, reflecting the total amount of file data being processed by the node's tasks. If the amount of data being processed is too large, the number of received task messages will decrease.

[0061] The node table is updated by first distributing each single file to the corresponding target electronic document signing node, then updating the number of processing tasks, the size of the processed files, and the receiving time of the corresponding electronic document signing node service in the node table; and then updating the number of processing tasks and the size of the processed files of the corresponding electronic document signing node service in the node table again after obtaining the original signature text and business routing identifier data fed back by each target electronic document signing node, so as to complete the update of the load data of the node table.

[0062] Step S20: Receive a batch file signing request sent by the client, and in response to the signing request, split the batch file into individual files.

[0063] It should be noted that, in order to improve the processing efficiency of electronic signatures for batch files, this embodiment first needs to split the batch files into multiple single files.

[0064] Step S30: Based on the node table and the business data of each single file, determine the target electronic document signing node corresponding to each single file in the electronic document signing node cluster, and distribute each single file to the corresponding target electronic document signing node.

[0065] After being split into individual files, each file is then distributed to its corresponding target electronic document signing node. This method enables the synchronous invocation of multiple electronic document signing nodes, allowing for simultaneous electronic signature processing using multiple electronic document signing nodes.

[0066] Furthermore, in this embodiment, the process of determining the target electronic document signing node specifically involves, for any single file, obtaining the file size of each electronic document signing node in the single file input electronic document signing node cluster and the file size processed by each electronic document signing node; obtaining the available disk space, memory capacity, number of CPU cores, and number of task threads being processed for each electronic document signing node based on the node table; calculating the score of each electronic document signing node based on the file size of each electronic document signing node in the single file input electronic document signing node cluster, the file size processed by each electronic document signing node, the available disk space, the memory capacity, the number of CPU cores, and the number of task threads being processed; and selecting the electronic document signing node with the highest score as the target electronic document signing node corresponding to the single file. The calculation of the score of each electronic document signing node based on the file size of each electronic document signing node in the single file input electronic document signing node cluster, the file size processed by each electronic document signing node, the available disk space, the memory capacity, the number of CPU cores, and the number of task threads being processed includes:

[0067] A disk coefficient score is calculated by combining a preset disk ratio coefficient with the file size of each electronic document signing node in the electronic document signing node cluster, the file size processed by each electronic document signing node, and the available disk space. A memory coefficient score is calculated by combining a preset memory ratio coefficient with the file size of each electronic document signing node in the electronic document signing node cluster, the file size processed by each electronic document signing node, and the memory capacity. A CPU coefficient score is calculated by combining the file size of each electronic document signing node in the electronic document signing node cluster, the file size processed by each electronic document signing node, the number of CPU cores, and the number of task threads being processed. A total score is calculated by combining the preset ratio coefficient of each electronic document signing node with the disk coefficient score, the memory coefficient score, and the CPU coefficient score. The electronic document signing node with the highest total score is selected as the target electronic document signing node for the single file.

[0068] It should be noted that the above parameters are defined as follows: the input file size is FSPPr, the number of threads currently processing tasks on the node is P, the file size being processed by the node is FSPEx, the number of CPU cores on the node is C, the memory capacity of the node is M, the available disk space on the node is D, the CPU ratio of the node is Kc (between 1 and 0), the memory ratio of the node is Km (between 1 and 0), the disk ratio of the node is Kd (between 1 and 0), and the ratio of the node is Ks (between 1 and 0).

[0069] The formula for calculating the disk coefficient score λd is:

[0070]

[0071] The formula for calculating the memory score λm is:

[0072]

[0073] The formula for calculating the CPU coefficient score λc is:

[0074]

[0075] The formula for calculating the total score λ of a node is:

[0076] λ=(λd*Kd+λm*Km+λc*Kc)*Ks

[0077] The above function Rag is defined as Rag(min,x,max), which takes three parameters: min,x, andmax. The range of values ​​set by min and max is used. If the value of x is less than the value of min, the function returns min; if the value of x is greater than the value of max, the function returns max; if the value is between min and max, the function returns x.

[0078] Furthermore, electronic document signatures correspond to specific physical machines. By obtaining data from the document and load information table, the score of the document task is calculated on each machine. The machine with the highest score is the best processing machine. If all machine scores are lower than or equal to 0, it means that the current machine is overloaded and not suitable for calculation. If all machine scores are lower than or equal to 0, it means that there are no suitable computing machines in the system and machine expansion is required.

[0079] Step S40: Obtain the original signature text and business routing identifier data fed back by each target electronic document signing node, and send the original signature text and the business routing identifier data to the client.

[0080] In the specific implementation, after the target electronic document signing node signs, it will first send the original signature to the electronic document signing scheduling center. The electronic document signing scheduling center will then send the original signature and business routing identification data to the client. The business routing identification data is used to identify the electronic document signing node corresponding to the signing of the distributed single document. The business routing identification data is obtained by concatenating the identifier of the electronic document signing node, the task identifier of the electronic document signing node, and the contract document identifier of the single document and then performing Hex encoding.

[0081] It should be noted that after receiving the electronic document signing task message, the electronic document signing node parses the message document, reads the file data of the single file from the file service based on the contract ID data provided in the message, and performs electronic signature processing on the file by combining coordinate information, signature image, signature certificate, etc., calculates the original signature text, and returns it to the electronic document signing scheduling center.

[0082] Step S50: Receive the encapsulated data fed back by the client, parse the encapsulated data to determine the target electronic document signing node corresponding to each signing result, and send the target electronic document signing node in response to the signing completion request sent by the client. The target electronic document signing node merges the signing result with the corresponding single document based on the signing completion request to complete the signing of the electronic signature of each single document.

[0083] In the specific implementation, after the client receives the original signature text and business routing identifier data, the original signature text of each single document in the batch is signed using the corresponding cryptographic device to obtain the signature result. Then, the signature result and business routing identifier data of each single document are encapsulated and a completion processing request is sent to the electronic document signature scheduling center. The electronic document signature scheduling center parses the encapsulated data corresponding to the completion processing request to obtain the target electronic document signature node corresponding to each signature result. Then, the signature result returned by the client is sent to the target electronic document signature node. Finally, the target electronic document signature node merges the signature result with the single document to complete the electronic signature processing.

[0084] In this embodiment, a registration message is received from the electronic document signing node cluster, and the node table is updated according to the registration message; a batch file signing request is received from the client, and the batch files are split into individual files in response to the signing request; the target electronic document signing node corresponding to each individual file in the electronic document signing node cluster is determined based on the node table and the business data of each individual file, and each individual file is distributed to the corresponding target electronic document signing node; the signature original text and business routing identifier data fed back by each target electronic document signing node are obtained, and the signature original text and the business routing identifier data are sent to the client; the encapsulation data fed back by the client is received, the encapsulation data is parsed to determine the target electronic document signing node corresponding to each signing result, and the target electronic document signing node is sent in response to the signing completion request sent by the client; the signing result is merged with the corresponding individual file by each target electronic document signing node based on the signing completion request to complete the electronic signature of each individual file. Through the above signature scheduling and distribution method, the problem of slow signing caused by a large batch of files being signed in a single request and processed by a single node is solved, effectively utilizing device resources and improving the signing experience and efficiency.

[0085] Furthermore, this embodiment of the invention also proposes a storage medium storing an electronic signature program based on file scheduling and distribution, wherein when the electronic signature program based on file scheduling and distribution is executed by a processor, it implements the steps of the electronic signature method based on file scheduling and distribution as described above.

[0086] Reference Figure 7 , Figure 7 This is a structural block diagram of the first embodiment of the electronic signature system based on file scheduling and distribution of the present invention.

[0087] like Figure 7 As shown, the electronic signature system based on file scheduling and distribution proposed in this embodiment of the invention includes: a client 10, an electronic document signature scheduling center 20, and an electronic document signature node cluster 30;

[0088] The electronic document signature scheduling center 20 is used to receive the registration message issued by the electronic document signature node cluster 30, and update the node table according to the registration message.

[0089] The electronic document signing scheduling center 20 is used to receive the batch file signing request sent by the client 10, and in response to the signing request, split the batch file into individual files.

[0090] The electronic document signature scheduling center 20 is used to determine the target electronic document signature node corresponding to each single file in the electronic document signature node cluster 30 based on the node table and the business data of each single file, and to distribute each single file to the corresponding target electronic document signature node.

[0091] The electronic document signature scheduling center 20 is used to obtain the original signature text and business routing identifier data fed back by each target electronic document signature node, and send the original signature text and the business routing identifier data to the client 10.

[0092] The electronic document signature scheduling center 20 is used to receive the encapsulated data fed back by the client 10, parse the encapsulated data to determine the target electronic document signature node corresponding to each signing result, and send the target electronic document signature node in response to the signing completion request sent by the client 10. The target electronic document signature node merges the signature result with the corresponding single document based on the signing completion request to complete the signing of the electronic signature of each single document. The encapsulated data consists of the signing result and the business routing identifier data. The signing result is obtained by the client 10 signing the original signature text.

[0093] In this embodiment, a registration message is received from the electronic document signing node cluster, and the node table is updated according to the registration message; a batch file signing request is received from the client, and the batch files are split into individual files in response to the signing request; the target electronic document signing node corresponding to each individual file in the electronic document signing node cluster is determined based on the node table and the business data of each individual file, and each individual file is distributed to the corresponding target electronic document signing node; the signature original text and business routing identifier data fed back by each target electronic document signing node are obtained, and the signature original text and the business routing identifier data are sent to the client; the encapsulation data fed back by the client is received, the encapsulation data is parsed to determine the target electronic document signing node corresponding to each signing result, and the target electronic document signing node is sent in response to the signing completion request sent by the client; the signing result is merged with the corresponding individual file by each target electronic document signing node based on the signing completion request to complete the electronic signature of each individual file. Through the above signature scheduling and distribution method, the problem of slow signing caused by a large batch of files being signed in a single request and processed by a single node is solved, effectively utilizing device resources and improving the signing experience and efficiency.

[0094] In some embodiments, when the signing service is started, the electronic document signing node cluster 30 reads the physical hardware information of the current device and the configuration information related to the node to generate a registration message, sends the registration message to the electronic document signing scheduling center 20 based on the UPD communication method, and rereads the physical hardware information of the current device and the configuration information related to the node to generate a new registration message every preset period.

[0095] In some embodiments, the node table is used to record data information of each electronic document signing node. The data information includes at least the unique identifier of the service node, the node's registration address, server hardware information, the number of file tasks currently being processed by the service, the total size of the electronic files being processed by the tasks, CPU configuration, and memory configuration information. The node table is updated in real time based on the registration message, and the load data related to the node table is updated based on the signing status of each electronic document signature.

[0096] In some embodiments, the electronic document signature scheduling center 20 is used to update the number of processing tasks, the size of the processed files, and the acceptance time of the corresponding electronic document signature node service in the node table after distributing each single file to the corresponding target electronic document signature node;

[0097] The electronic document signature scheduling center 20 is used to update the number of processing tasks and the size of the processed files of the corresponding electronic document signature node service in the node table after obtaining the original signature text and business routing identification data fed back by each target electronic document signature node, so as to complete the update of the load data of the node table.

[0098] In some embodiments, the electronic document signature scheduling center 20 is used to obtain, for any single file, the file size of each electronic document signature node in the electronic document signature node cluster and the file size processed by each electronic document signature node;

[0099] Based on the node table, obtain the available disk space, memory capacity, number of CPU cores, and number of task threads being processed for each electronic document signature node;

[0100] The score of each electronic document signing node is calculated based on the file size of each electronic document signing node in the single file input electronic document signing node cluster 30, the file size processed by each electronic document signing node, the available disk space, the memory capacity, the number of CPU cores, and the number of task threads being processed.

[0101] The electronic document signature node with the highest score is selected as the target electronic document signature node for the single file.

[0102] In some embodiments, the electronic document signature scheduling center 20 is used to calculate a disk coefficient score by combining a preset disk ratio coefficient and based on the file size of each electronic document signature node in the electronic document signature node cluster 30 for the single file input, the file size processed by each electronic document signature node, and the available disk space.

[0103] The memory coefficient score is calculated by combining a preset memory ratio coefficient with the file size of each electronic document signing node in the electronic document signing node cluster 30, the file size processed by each electronic document signing node, and the memory capacity.

[0104] The CPU coefficient score is calculated by combining the file size of each electronic document signing node in the electronic document signing node cluster 30 based on the single file input, the file size processed by each electronic document signing node, the number of CPU cores, and the number of task threads being processed.

[0105] The total score is calculated by combining the preset ratio coefficients of each electronic document signing node with the disk coefficient score, the memory coefficient score, and the CPU coefficient score.

[0106] Accordingly, the step of selecting the electronic document signing node with the highest score as the target electronic document signing node for the single file includes:

[0107] The electronic document signature node with the highest total score is selected as the target electronic document signature node for the individual document.

[0108] In some embodiments, the business routing identification data is used to identify the electronic document signing node corresponding to the signing of the distributed single document. The business routing identification data is obtained by concatenating the identifier of the electronic document signing node, the task identifier of the electronic document signing node, and the contract document identifier of the single document and then performing Hex encoding.

[0109] This application also provides an electronic signature device based on file scheduling and distribution, including a processor, a communication interface, a memory, and a communication bus. The processor, communication interface, and memory communicate with each other through the communication bus. The memory is used to store the electronic signature program based on file scheduling and distribution. When the processor executes the program stored in the memory, it implements the above-mentioned electronic signature method based on file scheduling and distribution.

[0110] The communication bus mentioned in the above-mentioned electronic signature device based on file scheduling and distribution can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc.

[0111] The communication interface is used for communication between the aforementioned file-based electronic signature device and other devices.

[0112] The memory may include random access memory (RAM) or non-volatile memory (NVM), such as at least one disk storage device. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor.

[0113] The processors mentioned above can be general-purpose processors, including central processing units (CPUs), network processors (NPs), etc.; they can also be digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components.

[0114] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable system. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid state disk (SSD)).

[0115] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0116] The various embodiments in this specification are described in a related manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on describing the differences from other embodiments. In particular, the system embodiments are basically similar to the method embodiments, so the description is relatively simple; relevant parts can be referred to the descriptions of the method embodiments.

[0117] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

[0118] It should be understood that the above are merely illustrative examples and do not constitute any limitation on the technical solutions of the present invention. In specific applications, those skilled in the art can make settings as needed, and the present invention does not impose any restrictions on this.

[0119] It should be noted that the workflow described above is merely illustrative and does not limit the scope of protection of this invention. In practical applications, those skilled in the art can select some or all of the workflow to achieve the purpose of this embodiment according to actual needs, and no restrictions are imposed here.

[0120] In addition, for technical details not described in detail in this embodiment, please refer to the electronic signature method based on file scheduling and distribution provided in any embodiment of the present invention, which will not be repeated here.

[0121] Furthermore, it should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or system that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or system. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or system that includes that element.

[0122] The sequence numbers of the above embodiments of the present invention are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0123] Through the above description of the embodiments, those skilled in the art can clearly understand that the methods of the above embodiments can be implemented by means of software plus necessary general-purpose hardware platforms. Of course, they can also be implemented by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium (such as read-only memory (ROM) / RAM, magnetic disk, optical disk) and includes several instructions to cause a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the various embodiments of the present invention.

[0124] The above are merely preferred embodiments of the present invention and do not limit the scope of the patent. Any equivalent structural or procedural transformations made based on the description and drawings of the present invention, or direct or indirect applications in other related technical fields, are similarly included within the scope of patent protection of the present invention.

[0125] It is understood that the system provided in the embodiments of the present invention corresponds to the method provided in the embodiments of the present invention, and the explanation, examples and beneficial effects of the relevant content can be referred to the corresponding parts of the above methods.

Claims

1. An electronic signature method based on file dispatch distribution, characterized in that, The method comprises: receiving a registration message issued by an electronic file signature node cluster, and updating a node table according to the registration message; receiving a signing request of a batch of files sent by a client, and splitting the batch of files into individual files in response to the signing request; determining target electronic file signature nodes corresponding to the individual files in the electronic file signature node cluster based on the node table and service data of the individual files, and distributing the individual files to the target electronic file signature nodes; obtaining signature original texts and service routing identification data fed back by the target electronic file signature nodes, and sending the signature original texts and the service routing identification data to the client; receiving encapsulation data fed back by the client, determining target electronic file signature nodes corresponding to signing results by analyzing the encapsulation data, and sending the target electronic file signature nodes in response to a signing completion request sent by the client, wherein the encapsulation data is composed of the signing results and the service routing identification data, the signing results are obtained by signing the signature original texts by the client, and the signing results and the corresponding individual files are merged by the target electronic file signature nodes based on the signing completion request to complete the electronic signature of the individual files; wherein the determination of the target electronic file signature nodes corresponding to the individual files in the electronic file signature node cluster based on the node table and the service data of the individual files comprises: for any single file, obtaining file sizes of the single file input into each electronic file signature node in the electronic file signature node cluster and file sizes processed by each electronic file signature node; obtaining available disk space, memory capacity, CPU core number and number of task threads being processed corresponding to each electronic file signature node based on the node table; calculating scores of each electronic file signature node according to the file sizes of the single file input into each electronic file signature node in the electronic file signature node cluster, the file sizes processed by each electronic file signature node, the available disk space, the memory capacity, the CPU core number and the number of task threads being processed; taking an electronic file signature node with the highest score as the target electronic file signature node corresponding to the single file; wherein the calculation of the scores of each electronic file signature node according to the file sizes of the single file input into each electronic file signature node in the electronic file signature node cluster, the file sizes processed by each electronic file signature node, the available disk space, the memory capacity, the CPU core number and the number of task threads being processed comprises: calculating a disk coefficient score in combination with a preset disk proportion coefficient and according to the file sizes of the single file input into each electronic file signature node in the electronic file signature node cluster, the file sizes processed by each electronic file signature node and the available disk space; The memory coefficient score is calculated in combination with the preset memory proportion coefficient and according to the file size of each electronic file signature node in the single file input electronic file signature node cluster, the file size processed by each electronic file signature node, and the memory capacity; The CPU coefficient score is calculated in combination with the file size of each electronic file signature node in the single file input electronic file signature node cluster, the file size processed by each electronic file signature node, the CPU core number, and the number of task threads being processed; The total score is calculated in combination with the preset proportion coefficient of each electronic file signature node and according to the disk coefficient score, the memory coefficient score, and the CPU coefficient score; Correspondingly, the electronic file signature node with the highest score is taken as the target electronic file signature node corresponding to the single file. The electronic file signature node with the highest total score is taken as the target electronic file signature node corresponding to the single file.

2. The electronic signature method based on file dispatch distribution according to claim 1, wherein, Before the receiving electronic file signature node cluster updates the node table according to the registration message, the method further comprises: When the signing service is started, the electronic file signature node cluster reads the physical hardware information of the current device and the configuration information related to the node to generate a registration message, sends the registration message to the electronic file signature scheduling center based on the UPD communication mode, and reads the physical hardware information of the current device and the configuration information related to the node again at a preset interval to generate a new registration message.

3. The electronic signature method based on file dispatch distribution according to claim 1, wherein, The node table is used to record the data information of each electronic file signature node, wherein the data information at least includes a unique identifier of a service node, a registration address of the node, server hardware information, the number of file tasks being processed in the current service, the total size of data electronic files processed by the task, CPU configuration, and memory configuration information. The node table is updated in real time based on the registration message, and the load data related to the node table is updated based on the signing situation of each electronic file signature.

4. The electronic signature method based on file dispatch distribution according to claim 3, wherein, The method further comprises: After each single file is distributed to the corresponding target electronic file signature node, the number of processing tasks, the size of files processed, and the acceptance time of the corresponding electronic file signature node in the node table are updated; After the signature original text and the business routing identification data fed back by each target electronic file signature node are obtained, the number of processing tasks and the size of files processed by the corresponding electronic file signature node in the node table are updated again to complete the update of the load data of the node table.

5. The electronic signature method based on file dispatch distribution according to claim 1, wherein, The business routing identification data is used to identify the electronic file signature node corresponding to the signing of the distributed single file, and the business routing identification data is obtained by splicing and Hex encoding the identifier of the electronic file signature node, the task identifier of the electronic file signature node, and the contract file identifier of the single file.

6. An electronic signature system based on file dispatch distribution, characterized by, The electronic signature system based on file scheduling and distribution is applied to the electronic signature method based on file scheduling and distribution as claimed in any one of claims 1 to 5, and comprises a client, an electronic file signature scheduling center and an electronic file signature node cluster. The electronic file signature scheduling center is configured to receive a registration message issued by the electronic file signature node cluster and update a node table according to the registration message. The electronic file signature scheduling center is configured to receive a signing request of batch files sent by the client and split the batch files into individual single files in response to the signing request. The electronic file signature scheduling center is configured to determine target electronic file signature nodes corresponding to the individual single files in the electronic file signature node cluster based on the node table and service data of the individual single files, and distribute the individual single files to the corresponding target electronic file signature nodes. The electronic file signature scheduling center is configured to obtain signature original texts and service routing identification data fed back by the individual target electronic file signature nodes, and send the signature original texts and the service routing identification data to the client. The electronic file signature scheduling center is configured to receive encapsulation data fed back by the client, determine target electronic file signature nodes corresponding to individual signing results by analyzing the encapsulation data, and send the target electronic file signature nodes in response to a signing completion request sent by the client, so as to complete the electronic signature of the individual single files by merging the signing results and the corresponding single files based on the signing completion request through the individual target electronic file signature nodes, wherein the encapsulation data is composed of the signing results and the service routing identification data, and the signing results are obtained by signing the signature original texts by the client.

7. An electronic signature device based on file dispatch distribution, characterized by, The electronic signature device based on file scheduling and distribution comprises a memory, a processor and an electronic signature program based on file scheduling and distribution stored on the memory and executable on the processor, and the electronic signature program based on file scheduling and distribution is configured to implement the steps of the electronic signature method based on file scheduling and distribution as claimed in any one of claims 1 to 5.

8. A storage medium, characterized by The storage medium stores an electronic signature program based on file scheduling and distribution, and the electronic signature program based on file scheduling and distribution implements the steps of the electronic signature method based on file scheduling and distribution as claimed in any one of claims 1 to 5 when executed by the processor.

Images