CN115017550B - Electronic contract data processing method and device, computer equipment and medium - Google Patents
Electronic contract data processing method and device, computer equipment and medium Download PDFInfo
- Publication number
- CN115017550B CN115017550B CN202210623125.4A CN202210623125A CN115017550B CN 115017550 B CN115017550 B CN 115017550B CN 202210623125 A CN202210623125 A CN 202210623125A CN 115017550 B CN115017550 B CN 115017550B
- Authority
- CN
- China
- Prior art keywords
- signature
- server
- electronic contract
- service
- request
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
- G06F21/645—Protecting data integrity, e.g. using checksums, certificates or signatures using a third party
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/46—Multiprogramming arrangements
- G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
- G06F9/5005—Allocation of resources, e.g. of the central processing unit [CPU] to service a request
- G06F9/5027—Allocation of resources, e.g. of the central processing unit [CPU] to service a request the resource being a machine, e.g. CPUs, Servers, Terminals
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Computer Security & Cryptography (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Computer And Data Communications (AREA)
Abstract
When an electronic contract signature request is received, a target CA server executing electronic contract signature at this time is selected from a preset CA service loop, the signature service request is sent to the target CA server, and the signature data fed back by the target CA server is received, so that the electronic contract is generated. In the whole process, different target CA servers are selected from the preset CA service loop to provide CA services in parallel, and the efficiency is improved in a parallel processing mode; and because the times of the CA server identification in the preset CA service loop are inversely related to the digital signature cost of the CA server, the CA server with lower digital signature cost provides higher CA service probability, so that the overall electronic contract cost is lower, and the efficient and low-cost electronic contract signing is realized.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for processing electronic contract data, a computer device, a storage medium, and a computer program product.
Background
With the development of technologies such as internet, big data and the like, the digital transformation of enterprises gradually becomes the necessary way to improve competitiveness and realize sustainable development. The electronic contract is an important step of enterprise digital transformation, and the electronic contract is an agreement between two parties or multiple parties for establishing, changing and terminating the property civil right obligation relationship in an electronic form through an electronic information network.
The electronic contract signing is carried out by a third-party CA service provider, chain storage and certification are carried out on contract document data in the whole signing process by adopting a block chain and a timestamp, the data are solidified by utilizing a hash value, and meanwhile, the timestamp technology can accurately record information such as signing time, signing place, signing persons and the like, so that the contract data are not tampered, and the originality and integrity of the contract are maintained.
In a traditional electronic contract, digital signatures are realized by means of an API (application programming interface) interface and the like provided by a business system docking CA (certificate Authority) service provider, and although the electronic contract can be signed, the digital contract cannot be signed efficiently and at low cost.
Disclosure of Invention
In view of the foregoing, it is necessary to provide an efficient and low-cost electronic contract data processing method, apparatus, computer device, storage medium, and computer program product.
In a first aspect, the present application provides an electronic contract data processing method. The method comprises the following steps:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing the signing service request to the target CA server;
receiving signature data fed back by the target CA server, and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In one embodiment, before the responding to the electronic contract signature request and selecting the target CA server performing the electronic contract signature this time according to a preset CA service loopback, the method further includes:
acquiring the digital signature cost of different CA servers;
and combining CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
In one embodiment, the generating a preset CA service loopback by combining CA server identifiers of different CA servers according to the digital signature cost includes:
solving the minimum common multiple of the digital signature cost of different CA servers;
determining the execution times of each CA server in a loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times;
determining the proportion of the CA server identification corresponding to each CA server in a CA service loopback based on the execution times;
and combining different CA server identifications according to the proportion to generate a preset CA service loop.
In one embodiment, after the pushing the signature service request to the target CA server, the method further includes:
and returning the electronic contract signing request when a CA service failure message is sensed, and selecting a target CA server executing the electronic contract signing at this time according to a preset CA service loopback.
In one embodiment, the electronic contract data processing method further includes:
monitoring an electronic contract generating event;
when the electronic contract generating event represents that the contract is failed to generate, marking the target CA server corresponding to the current round as the unavailable state of the CA service to obtain marked data;
and adding the marked data to an event log, returning the response to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
In one embodiment, the extracting signature task data carried in the electronic contract signature request and generating a signature service request according to the signature task data includes:
extracting signature task data carried in the electronic contract signature request;
reading a contract text in the signature task data, and identifying the type of the contract text;
according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information;
and generating a signature service request according to the signature position information and the signature task data.
In a second aspect, the application also provides an electronic contract data processing device. The device comprises:
the request receiving module is used for acquiring an electronic contract signature request;
the response module is used for responding to the electronic contract signature request and selecting a target CA server for executing the electronic contract signature according to a preset CA service loopback;
the data processing module is used for extracting signature task data carried in the electronic contract signature request and generating a signature service request according to the signature task data;
the pushing module is used for pushing the signature service request to the target CA server;
the contract generation module is used for receiving the signature data fed back by the target CA server and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing the signing service request to the target CA server;
receiving signature data fed back by the target CA server, and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing the signing service request to the target CA server;
receiving signature data fed back by the target CA server, and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing the signing service request to the target CA server;
receiving signature data fed back by the target CA server, and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
According to the electronic contract data processing method, the electronic contract data processing device, the computer equipment, the storage medium and the computer program product, when an electronic contract signature request is received, a target CA server for executing electronic contract signature at this time is selected from a preset CA service loop, the signature service request is sent to the target CA server, the signature data fed back by the target CA server is received, and then the electronic contract is generated. In the whole process, different target CA servers are selected from the preset CA service loop to provide CA services in parallel, and the efficiency is improved in a parallel processing mode; and because the times of the CA server identification in the preset CA service loop are inversely related to the digital signature cost of the CA server, the CA server with lower digital signature cost provides higher CA service probability, so that the overall electronic contract cost is lower, and the efficient and low-cost electronic contract signing is realized.
Drawings
FIG. 1 is a diagram of an application environment of a method for processing electronic contract data in one embodiment;
FIG. 2 is a schematic flow chart diagram illustrating a method for processing electronic contract data according to one embodiment;
FIG. 3 is a schematic diagram of a default CA service loopback;
FIG. 4 is a flowchart illustrating a method for processing electronic contract data according to another embodiment;
FIG. 5 is a schematic diagram illustrating a sub-flow of S300 according to an embodiment;
FIG. 6 is a block diagram showing the configuration of an electronic contract data processing apparatus according to an embodiment;
FIG. 7 is a diagram illustrating an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.
The electronic contract data processing method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. The terminal 102 communicates with the server 104 via a network, and the server 104 is connected to a plurality of third-party CA servers, and the plurality of CA servers provide CA services. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104, or may be located on the cloud or other network server. The terminal 102 sends an electronic contract signing request to the server 104, and the server 104 acquires the electronic contract signing request; responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback; extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data; pushing a signature service request to a target CA server of the plurality of CA servers; and receiving the signature data fed back by the target CA server, generating an electronic contract according to the signature data, and feeding back the electronic contract to the terminal 102 by the server 104. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.
In one embodiment, as shown in fig. 2, an electronic contract data processing method is provided, which is described by taking the method as an example applied to the server in fig. 1, and includes the following steps:
s100: and acquiring an electronic contract signature request.
The electronic contract signing request can be uploaded to the server by the terminal, and when the terminal has a requirement for signing the electronic contract, the terminal uploads the electronic contract signing request to the server. Further, after receiving the electronic contract signature request, the server can verify the electronic contract signature request, verify the validity of the electronic contract signature request, and continue the next processing if the electronic contract signature request is valid; if not, the data is discarded. The validity check specifically includes verifying whether the store sub-contract template type and the template version carried in the electronic contract signature request exist and are available, whether an external serial number exists, whether parameter information is complete and legal, and the like. In practical application, if the electronic contract signature request passes verification, the server starts an asynchronous task to generate a contract and returns response information in request processing to a terminal (client); and if the request verification is not passed, returning response information containing specific failure reasons to the terminal (client).
S200: and responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
And the server responds to the electronic contract signing request and selects a CA server for providing the electronic signature service according to a preset CA service loop. Specifically, the preset CA service loopback is a loopback composed of different CA server identifiers, each CA server identifier represents one CA server, each time a target CA server is selected, a single CA server identifier is sequentially selected from the CA service loopback, and the CA server corresponding to the selected CA server identifier is used as the target CA server. In the preset CA service loop, the number of times of occurrence of different CA server identities is inversely related to the digital signature cost of the CA server, i.e., assuming that the digital signature cost of the CA server a is lower than the digital signature cost of the CA server B, the number of times of occurrence of the identity a is greater than the number of times of occurrence of the identity B in the preset CA service loop.
In practical application, the preset CA service loopback is shown in fig. 3, which includes A, B, C three CA server identifiers, these server identifiers are combined into the one CA service loopback, each time an electronic contract signature request is responded, one CA server identifier is sequentially selected from the preset CA service loopback, the CA server corresponding to the CA server identifier is used as a target CA server, for example, in fig. 3, request 0, and CA server a is selected; requesting 1, selecting a CA server B; request 2, select CA Server C; request 3, select CA Server A; … …; and so on. In the embodiment shown in fig. 3, the cost of the digital signature of CA server a is lower than that of CA server B, and the cost of the digital signature of CA server B is lower than that of CA server C, so CA server a appears the most in the entire CA service loop; secondly, a CA server B; the first time CA server C.
S300: and extracting the signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data.
The electronic contract signing request carries signing task data, and the signing task data specifically comprises an electronic contract needing to be signed, a position of the request for signing, a related task serial number, verification information and the like. The signature service request is a request for requesting the CA server to provide the CA service, wherein the server can extract data in the electronic contract signature request, arrange the data according to the CA service request and generate the signature service request so as to send the signature service request to a target CA server in a subsequent process, and the target CA server provides the CA service.
S400: pushing the signature service request to the target CA server.
The server pushes the signature server request to the target CA server, i.e. the target CA server selected by S200 to provide the CA service.
S500: and receiving the signature data fed back by the target CA server, and generating the electronic contract according to the signature data.
The server receives the signature data fed back by the target CA server and generates the electronic contract based on the signature data. The server may also transmit the generated electronic contract to the terminal.
According to the electronic contract data processing method, when an electronic contract signature request is received, a target CA server for executing electronic contract signature at this time is selected from a preset CA service loop, the signature service request is sent to the target CA server, and the signature data fed back by the target CA server is received, so that the electronic contract is generated. In the whole process, different target CA servers are selected from the preset CA service loop to provide CA services in parallel, and the efficiency is improved in a parallel processing mode; and because the times of the CA server identification in the preset CA service loop are inversely related to the digital signature cost of the CA server, the CA server with lower digital signature cost provides higher CA service probability, so that the overall electronic contract cost is lower, and the efficient and low-cost electronic contract signing is realized.
As shown in fig. 4, in one embodiment, before S200, the method further includes:
s120: acquiring digital signature costs of different CA servers;
s140: and combining the CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
The digital signature costs of different CA servers can be obtained by analyzing historical log data of different CA servers and the like, or the servers can actively send inquiry requests, and the different CA servers respond to the inquiry requests and feed back the inquiry requests to inform the servers of the digital signature costs in the historical digital signature operation. And the server combines the CA server identifications of different CA servers in a mode that the occurrence times are inversely related to the digital signature according to the digital signature cost to generate a preset CA service loop.
In one embodiment, combining the CA server identifiers of different CA servers according to the digital signature cost to generate the preset CA service loopback includes: solving the minimum common multiple of the digital signature cost of different CA servers; determining the execution times of each CA server in the loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; based on the execution times, determining the proportion of the CA server identifier corresponding to each CA server in a CA service loop; and combining different CA server identifications according to the proportion to generate a preset CA service loop.
As shown in fig. 3, assume that there are three CA providers a, B, and C currently, and their digital signature cost ratios are a: b: c =2:3:4 (the larger the number is, the higher the cost is), and according to the minimum common multiple 12 among the costs, calculating the simplest allocation ratio A among the CA services: b: c =12/2:12/3:12/4=6:4: then we select to form a CA loop from 6A, 4B, 3C streams [ A, B, C, A, B, C, A, B, A, A ] in turn. A preferred CA service is then selected for the request by counting global digitally signed requests, modulo the size of the CA's loopback. The digital signature cost mentioned above specifically refers to the price at which the CA service is provided.
In one embodiment, after pushing the signature service request to the target CA server, the method further includes: and when a CA service failure message is sensed, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loop.
In practical application, the target CA server selected in this round may generally process the signature service request, that is, may successfully complete the digital signature, but in some abnormal situations (for example, network abnormality, server abnormality, CA server abnormality, etc.), the target CA server selected in this round may not be completed, at this time, the target CA server selected in this round may feed back a CA service failure message, the server returns a response electronic contract signature request, and the target CA server executing the electronic contract signature is selected according to a preset CA service loop, and the target CA server is reselected. Further, since the environmental conditions (e.g., network environment, server abnormality, etc.) may not be improved in a short time, the steps of delaying for a certain time, returning to respond to the electronic contract signature request, and selecting the target CA server that executes the electronic contract signature according to the preset CA service loopback may be performed, for example, the CA service fails due to the network abnormality, and the network environment may have been improved after 3 minutes or 5 minutes, and may be performed normally when a new target CA server selection and subsequent signature processing are restarted.
In one embodiment, the electronic contract data processing method further includes:
monitoring an electronic contract generating event; when an electronic contract generating event represents that contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marked data to the event log, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
When the electronic contract generation event represents that the contract generation fails, the server may mark the target CA server corresponding to the round, for example, add a fault mark, to represent that the target CA server corresponding to the round is in an unavailable state for CA service, to obtain marked data, and the marked data is added to an event log of the server. When all CA servers have fault marks, the probability of successful retry is low, so that frequent retry occurs and the performance of the system is affected, and therefore, the retry is cancelled under the condition that all CA servers have fault marks; and retrying until a next task is triggered when a CA server without a mark exists.
As shown in fig. 5, in one embodiment, S300 includes:
s320: extracting signature task data carried in the electronic contract signature request;
s340: reading a contract text in the signature task data, and identifying the type of the contract text;
s360: according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information;
s380: and generating a signature service request according to the signature position information and the signature task data.
The signature task data refers to task data corresponding to the current electronic contract signature request, and the task data comprises contract texts, wherein different electronic contracts have different contract text types, and different contract text types have different signature positions. Specifically, it can be understood here that digital signature configuration is performed based on task data, and digital signature configuration is colloquially referred to as digital signature location configuration, that is, where a signature is located in a contract document, for a certain type of contract template, in order to enable each CA facilitator to perform digital signature, the digital signature configuration of each CA facilitator needs to be configured, and generally, the CA server has two positioning modes, namely, keyword positioning and location positioning. Keyword positioning: the method is to sign keywords appearing in a contract PDF template according to needs to position. For example, a keyword containing "signature" in the contract PDF template file, the location of "signature" in the contract PDF can be found by the "signature" keyword. Positioning: the contract PDF template is signed according to needs, and each page in the contract PDF template takes the lower left corner as an origin coordinate. From left to right, the positive direction of the x axis is the offset of the x axis, and from bottom to top, the positive direction of the y axis is the offset of the y axis. The position of the PDF template required to be signed is positioned by coordinates (x, y) and the page number.
In practical applications, each CA server provides a CA service that includes the following attributes: name, service provider component name, enabled or not, shutter switch, initial failure event, time of most recent failure, failure flag. The CA service name may be a name of a CA service provider. The service provider component name is the component name of the CA service provider in the Spring container or the name of the Bean, and we can obtain the service provider of the CA service from the Spring container through the component name. Whether the service for the administrator is enabled or disabled for a certain service is enabled, the disabled service will no longer be digitally signed for the contract. The initial failure time is the initial failure time when the CA service continuously fails. The last failure time is the last failure time when there was a continuous failure. When the CA service digital signature fails, if the current CA service has no initial failure time, setting the initial failure time and the latest failure time as the current time; if the current CA service has initial failure time, only the latest failure time is modified. When the CA service has no fault mark, if the time interval between the current fault time and the initial fault time is more than 10 seconds, adding the fault mark for the current CA service and issuing a CA service unavailable event, thereby achieving the purpose that the CA service can only trigger one service unavailable event when the CA service continuously fails for a long time. And when the CA service digital signature is successful, setting the initial failure time and the latest failure time to be null, and clearing the failure mark and issuing a CA service available event in the case of the failure mark. In practical situations, there are many reasons for the occurrence of the failure, for example, a network problem, and therefore it cannot be determined whether the CA service is really available, the failure flag here is merely a means for determining the availability of the current CA service, and if the failure flag is present, it can be said that the availability of the CA service is low, but it cannot be said that the digital signature of the CA service will fail at this time.
In practical applications, the contract information includes the following attribute information: generating a contract ID, source system, template type, template version, parameter information, external serial number, status, and process message. The generated contract ID is the unique identification of the generated contract, and the client can inquire the processing state of the contract in real time according to the contract ID. The source system, the template type, the template version, the parameter information and the external serial number are respectively request information of the client. The status is the processing status of the contract request, and mainly includes ready status, in-process status, successful processing status, failed processing status, and the like. The processing state of the request may also appear dead, which is the state that is in progress, but that is not actually a processing thread, and needs to be handled.
It should be understood that although the various steps in the flowcharts referred to in the embodiments above are shown as indicated by arrows, the steps are not necessarily performed in the order indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the above embodiments may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the order of performing the steps or stages is not necessarily performed, but may be performed alternately or alternately with other steps or at least a part of the steps or stages in other steps.
As shown in fig. 6, the present application also provides an electronic contract data processing apparatus. The device comprises:
a request receiving module 100, configured to obtain an electronic contract signature request;
the response module 200 is configured to respond to the electronic contract signature request, and select a target CA server that executes the electronic contract signature this time according to a preset CA service loopback;
the data processing module 300 is configured to extract signature task data carried in the electronic contract signature request, and generate a signature service request according to the signature task data;
a pushing module 400, configured to push a signature service request to a target CA server;
and a contract generating module 500, configured to receive the signature data fed back by the target CA server, and generate an electronic contract according to the signature data, where a preset CA service loopback consists of loopback identifiers of multiple CA servers, and the occurrence frequency of each CA server identifier is inversely related to the digital signature cost of the CA server.
When receiving an electronic contract signature request, the electronic contract data processing device selects a target CA server for executing the electronic contract signature from a preset CA service loop, sends the signature service request to the target CA server, receives signature data fed back by the target CA server, and further generates the electronic contract. In the whole process, different target CA servers are selected from the preset CA service loop to provide CA services in parallel, and the efficiency is improved in a parallel processing mode; and because the times of occurrence of the CA server identification in the preset CA service loop are inversely related to the digital signature cost of the CA server, the CA server with lower digital signature cost provides higher CA service probability, so that the overall electronic contract cost is lower, and efficient and low-cost electronic contract signing is realized.
In one embodiment, the response module 200 is further configured to obtain the digital signature costs of different CA servers; and combining the CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
In one embodiment, the response module 200 is further configured to find the least common multiple of the digital signature costs of different CA servers; determining the execution times of each CA server in the loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; determining the proportion of the CA server identification corresponding to each CA server in a CA service loop based on the execution times; and combining different CA server identifications according to the proportion to generate a preset CA service loop.
In one embodiment, the contract generating module 500 is further configured to control the response module 200 to re-execute an operation of responding to the electronic contract signing request and selecting a target CA server performing electronic contract signing this time according to a preset CA service loopback when a CA service failure message is sensed.
In one embodiment, the electronic contract data processing apparatus further includes a monitoring module, configured to monitor an electronic contract generation event; when the electronic contract generating event represents that the contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marking data to the event log, controlling the response module 200 to re-execute the operation of responding to the electronic contract signature request, and selecting the target CA server executing the electronic contract signature according to the preset CA service loopback.
In one embodiment, the data processing module 300 is further configured to extract signature task data carried in the electronic contract signature request; reading a contract text in the signature task data, and identifying the type of the contract text; according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information; and generating a signature service request according to the signature position information and the signature task data.
The respective modules in the electronic contract data processing apparatus described above may be implemented in whole or in part by software, hardware, and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and the internal structure thereof may be as shown in fig. 7. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data such as history processing logs. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement an electronic contract data processing method.
Those skilled in the art will appreciate that the architecture shown in fig. 7 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing a signature service request to a target CA server;
receiving signature data fed back by a target CA server, and generating an electronic contract according to the signature data; the preset CA service loop consists of a plurality of CA server identifications which are loop loops, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring digital signature costs of different CA servers; and combining the CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
solving the minimum common multiple of the digital signature cost of different CA servers; determining the execution times of each CA server in the loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; determining the proportion of the CA server identification corresponding to each CA server in a CA service loop based on the execution times; and combining different CA server identifications according to the proportion to generate a preset CA service loop.
In one embodiment, the processor when executing the computer program further performs the steps of:
and when a CA service failure message is sensed, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loop.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
monitoring an electronic contract generating event; when the electronic contract generating event represents that the contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marked data to the event log, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
extracting signature task data carried in the electronic contract signature request; reading a contract text in the signature task data, and identifying the type of the contract text; according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information; and generating a signature service request according to the signature position information and the signature task data.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing a signature service request to a target CA server;
receiving signature data fed back by a target CA server, and generating an electronic contract according to the signature data; the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring digital signature costs of different CA servers; and combining the CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
solving the minimum common multiple of the digital signature cost of different CA servers; determining the execution times of each CA server in the loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; determining the proportion of the CA server identification corresponding to each CA server in a CA service loop based on the execution times; and combining different CA server identifications according to the proportion to generate a preset CA service loop.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
and when a CA service failure message is intercepted, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loop.
In one embodiment, the processor when executing the computer program further performs the steps of:
monitoring an electronic contract generating event; when the electronic contract generating event represents that the contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marked data to the event log, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
extracting signature task data carried in the electronic contract signature request; reading a contract text in the signature task data, and identifying the type of the contract text; according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information; and generating a signature service request according to the signature position information and the signature task data.
In one embodiment, a computer program product is provided, comprising a computer program which, when executed by a processor, performs the steps of:
acquiring an electronic contract signature request;
responding to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing a signature service request to a target CA server;
receiving signature data fed back by a target CA server, and generating an electronic contract according to the signature data; the preset CA service loop consists of a plurality of CA server identifications which are loop loops, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring digital signature costs of different CA servers; and combining the CA server identifications of different CA servers according to the digital signature cost to generate a preset CA service loop, wherein the occurrence times of the different CA server identifications in the preset CA service loop are inversely related to the corresponding digital signature cost.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
solving the minimum common multiple of the digital signature cost of different CA servers; determining the execution times of each CA server in the loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; determining the proportion of the CA server identification corresponding to each CA server in a CA service loop based on the execution times; and combining different CA server identifications according to the proportion to generate a preset CA service loop.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
and when a CA service failure message is sensed, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loop.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
monitoring an electronic contract generating event; when the electronic contract generating event represents that the contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marked data to the event log, returning a response electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loop.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
extracting signature task data carried in the electronic contract signature request; reading a contract text in the signature task data, and identifying the type of the contract text; according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information; and generating a signature service request according to the signature position information and the signature task data.
It should be noted that, the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), magnetic Random Access Memory (MRAM), ferroelectric Random Access Memory (FRAM), phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above examples only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, and these are all within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.
Claims (10)
1. An electronic contract data processing method, characterized by comprising:
acquiring an electronic contract signature request;
responding to the electronic contract signing request, and acquiring the digital signing costs of different CA servers;
solving the minimum common multiple of the digital signature cost of different CA servers;
determining the execution times of each CA server in a loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times;
determining the proportion of the CA server identification corresponding to each CA server in a CA service loopback based on the execution times;
combining different CA server identifications according to the proportion to generate a preset CA service loop; wherein the occurrence times of different CA server identifications in the preset CA service loopback is inversely related to the corresponding digital signature cost;
extracting signature task data carried in the electronic contract signature request, and generating a signature service request according to the signature task data;
pushing the signature service request to a target CA server;
receiving signature data fed back by the target CA server, and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in a loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
2. The method of claim 1, wherein after pushing the signature service request to the target CA server, further comprising:
and returning the electronic contract signing request when a CA service failure message is sensed, and selecting a target CA server executing the electronic contract signing at this time according to a preset CA service loopback.
3. The method of claim 1, further comprising:
monitoring an electronic contract generating event;
when the electronic contract generating event represents that the contract is failed to generate, marking the target CA server corresponding to the current round as the unavailable state of the CA service to obtain marked data;
and adding the marked data to an event log, returning the response to the electronic contract signature request, and selecting a target CA server executing the electronic contract signature according to a preset CA service loopback.
4. The method according to claim 1, wherein the extracting signature task data carried in the electronic contract signature request, and the generating a signature service request according to the signature task data comprises:
extracting signature task data carried in the electronic contract signature request;
reading a contract text in the signature task data, and identifying the type of the contract text;
according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information;
and generating a signature service request according to the signature position information and the signature task data.
5. An electronic contract data processing apparatus, characterized by comprising:
the request receiving module is used for acquiring an electronic contract signature request;
the response module is used for responding to the electronic contract signing request and acquiring the digital signing cost of different CA servers; solving the minimum common multiple of the digital signature cost of different CA servers; determining the execution times of each CA server in a loop according to the minimum common multiple and the digital signature cost of each CA server, wherein the signature time consumption is inversely related to the execution times; based on the execution times, determining the proportion of the CA server identifier corresponding to each CA server in a CA service loopback; combining different CA server identifications according to the proportion to generate a preset CA service loop; wherein the occurrence times of different CA server identifications in the preset CA service loopback is inversely related to the corresponding digital signature cost;
the data processing module is used for extracting signature task data carried in the electronic contract signature request and generating a signature service request according to the signature task data;
the pushing module is used for pushing the signature service request to a target CA server;
the contract generation module is used for receiving the signature data fed back by the target CA server and generating an electronic contract according to the signature data;
the preset CA service loopback consists of a plurality of CA server identifications in loopback, and the occurrence frequency of each CA server identification is inversely related to the digital signature cost of the CA server.
6. The apparatus of claim 5, wherein the detection module comprises: and the contract generation module is also used for controlling the response module to execute the operation of responding to the electronic contract signing request again and selecting the target CA server executing the electronic contract signing this time according to the preset CA service loopback when the CA service failure message is sensed.
7. The apparatus according to claim 5, wherein the electronic contract data processing apparatus further comprises: the monitoring module is used for monitoring an electronic contract generating event; when the electronic contract generating event represents that the contract generation fails, marking a target CA server corresponding to the current round as a CA service unavailable state to obtain marked data; and adding the marked data to the event log, controlling the response module to re-execute the operation of responding to the electronic contract signature request, and selecting the target CA server executing the electronic contract signature according to the preset CA service loopback.
8. The apparatus according to claim 5, wherein the data processing module is further configured to extract the signature task data carried in the electronic contract signature request; reading a contract text in the signature task data, and identifying the type of the contract text; according to the type of the contract text, positioning a preset keyword position or a signature position of a signature page in the contract text to obtain signature position information; and generating a signature service request according to the signature position information and the signature task data.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 4.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 4.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210623125.4A CN115017550B (en) | 2022-06-02 | 2022-06-02 | Electronic contract data processing method and device, computer equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210623125.4A CN115017550B (en) | 2022-06-02 | 2022-06-02 | Electronic contract data processing method and device, computer equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115017550A CN115017550A (en) | 2022-09-06 |
| CN115017550B true CN115017550B (en) | 2023-03-10 |
Family
ID=83072658
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210623125.4A Active CN115017550B (en) | 2022-06-02 | 2022-06-02 | Electronic contract data processing method and device, computer equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115017550B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003223435A (en) * | 2002-01-31 | 2003-08-08 | Canon Inc | Document printing device, document authentication device, document printing method, document authentication method, document authentication system, program, and storage media |
| CN101751643A (en) * | 2008-12-04 | 2010-06-23 | 清华大学 | System and method for protecting security of e-commerce transactions based on e-contracts |
| WO2018000548A1 (en) * | 2016-07-01 | 2018-01-04 | 胡金钱 | Intelligent stamp with locking mechanism |
| CN113285809A (en) * | 2021-05-14 | 2021-08-20 | 福建瑞术信息科技有限公司 | Continuous signature method and system based on electronic signature middleware |
| CN113888115A (en) * | 2021-09-13 | 2022-01-04 | 北京安捷金科信息技术有限公司 | Electronic contract signing method, electronic contract signing system and readable storage medium |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20080141033A1 (en) * | 1995-02-13 | 2008-06-12 | Intertrust Technologies Corporation | Trusted and secure techniques, systems and methods for item delivery and execution |
| US20070300295A1 (en) * | 2006-06-22 | 2007-12-27 | Thomas Yu-Kiu Kwok | Systems and methods to extract data automatically from a composite electronic document |
| US8627066B2 (en) * | 2011-11-03 | 2014-01-07 | Cleversafe, Inc. | Processing a dispersed storage network access request utilizing certificate chain validation information |
| CN111159304A (en) * | 2020-04-01 | 2020-05-15 | 支付宝(杭州)信息技术有限公司 | Data processing method, device, equipment and system based on block chain |
-
2022
- 2022-06-02 CN CN202210623125.4A patent/CN115017550B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| JP2003223435A (en) * | 2002-01-31 | 2003-08-08 | Canon Inc | Document printing device, document authentication device, document printing method, document authentication method, document authentication system, program, and storage media |
| CN101751643A (en) * | 2008-12-04 | 2010-06-23 | 清华大学 | System and method for protecting security of e-commerce transactions based on e-contracts |
| WO2018000548A1 (en) * | 2016-07-01 | 2018-01-04 | 胡金钱 | Intelligent stamp with locking mechanism |
| CN113285809A (en) * | 2021-05-14 | 2021-08-20 | 福建瑞术信息科技有限公司 | Continuous signature method and system based on electronic signature middleware |
| CN113888115A (en) * | 2021-09-13 | 2022-01-04 | 北京安捷金科信息技术有限公司 | Electronic contract signing method, electronic contract signing system and readable storage medium |
Non-Patent Citations (3)
| Title |
|---|
| Efficient Resource Registration and Location Scheme in P2P-SIP, using ID-based Signature;Chang-Hwan Lee等;《网页在线公开：https://ieeexplore.ieee.org/stamp/stamp.jsp?tp=&arnumber=4494139》;20080422;第1-5页 * |
| 一种基于摘要口令加密私钥的数字签名模式;郑丽萍等;《计算机安全》;20080331;第28-30页 * |
| 天津钢管制造有限公司电子商务合同管理平台开发与应用;朱建伟等;《计算机应用与自动化》;20151116;第47-49页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115017550A (en) | 2022-09-06 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3776208B1 (en) | Runtime self-correction for blockchain ledgers | |
| US11018852B2 (en) | Blockchain trust anchor | |
| US11940971B2 (en) | Blockchain implementing reliability database | |
| US20200110824A1 (en) | Blockchain notification board storing blockchain resources | |
| US20220382746A1 (en) | Blockchain notification board storing blockchain resources | |
| US20220138212A1 (en) | Blockchain implementing reliability database | |
| US10567369B2 (en) | Secure token passing via hash chains | |
| TWI726573B (en) | Block chain-based data compression and query method and device and electronic equipment | |
| US11669532B2 (en) | Blockchain implementing reliability database | |
| EP3864816A1 (en) | Blockchain notification board storing blockchain resources | |
| CN108446172B (en) | Data calling method and device, computer equipment and storage medium | |
| CN111865691B (en) | Alarm file distribution method, device, equipment and medium based on artificial intelligence | |
| US10795882B2 (en) | Blockchain-based data compression and searching | |
| CN111488372A (en) | Data processing method, device and storage medium | |
| CN111339551A (en) | Data verification method and related device and equipment | |
| CN115017550B (en) | Electronic contract data processing method and device, computer equipment and medium | |
| CN110908801B (en) | Data processing method and device based on block chain, computer equipment and storage medium | |
| CN111522881A (en) | Service data processing method, device, server and storage medium | |
| CN116010926A (en) | Login authentication method, login authentication device, computer equipment and storage medium | |
| CN115935414A (en) | Block chain based data verification method and device, electronic equipment and storage medium | |
| CN112860755B (en) | Service identifier generation method, device, computer equipment and medium | |
| US11165733B2 (en) | Information processing system to execute a particular workflow in response to receiving mail | |
| CN110442447B (en) | Message queue-based load balancing method and device and computer equipment | |
| CN116528300B (en) | Task issuing method, device, system and communication equipment | |
| CN110209666B (en) | data storage method and terminal equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |