CN117785330A

CN117785330A - Protocol signing method, device, electronic equipment and storage medium

Info

Publication number: CN117785330A
Application number: CN202311870190.8A
Authority: CN
Inventors: 左灿; 赵亚利; 戴雨文
Original assignee: Shenzhen Futu Network Technology Co Ltd
Current assignee: Shenzhen Futu Network Technology Co Ltd
Priority date: 2023-12-29
Filing date: 2023-12-29
Publication date: 2024-03-29

Abstract

The invention discloses a protocol signing method, a device, electronic equipment and a storage medium, which are applied to a trust management platform server, wherein the method comprises the following steps: a protocol creation request is sent to a protocol server, and the protocol creation request is used for indicating the protocol server to generate a protocol file to be signed carrying a digital certificate and a protocol link corresponding to the protocol file to be signed based on the protocol creation request; receiving a protocol link of the protocol file to be signed returned by the protocol server; and sending the protocol link to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link. The technical scheme provided by the embodiment of the disclosure reduces the time cost of signing the protocol and improves the efficiency of signing the protocol.

Description

Protocol signing method, device, electronic equipment and storage medium

Technical Field

The disclosure belongs to the technical field of information processing, and particularly relates to a protocol signing method, a device, electronic equipment and a storage medium.

Background

In the related art, in the process of processing protocol files on a trust management platform server, because more protocol files are needed to be signed by clients among various processing flows, the protocol files are needed to be signed by trust management staff offline and the clients, but in the process of actually signing the protocol files, more protocol files are needed to be signed, the protocol file signing process consumes a great deal of manpower and time cost, and the signing efficiency of the protocol files is lower.

Disclosure of Invention

The embodiment of the disclosure provides a scheme to solve the problems that in the related art, a document signing process consumes a great deal of manpower and time cost, and the document signing efficiency is low.

In a first aspect, the present disclosure provides a method of signing a protocol, applied to a trust management platform server, the method comprising:

a protocol creation request is sent to a protocol server, and the protocol creation request is used for indicating the protocol server to generate a protocol file to be signed carrying a digital certificate and a protocol link corresponding to the protocol file to be signed based on the protocol creation request;

receiving a protocol link of the protocol file to be signed returned by the protocol server;

and sending the protocol link to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link.

In a second aspect, the present disclosure provides a method for signing a protocol, applied to a protocol server, the method comprising:

receiving a protocol creation request sent by a trust management platform server;

generating a protocol link of a protocol file to be signed based on the protocol creation request;

The protocol link is fed back to the trust management platform server, so that the trust management platform server sends the protocol link to a client corresponding to a protocol signing party;

receiving an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generating an agreement document signing page according to the agreement document to be signed, and sending the agreement document signing page to the client;

and acquiring the signing information of the agreement signing party through the agreement document signing page, and generating a signed agreement document according to the signing information and the agreement document to be signed.

In a third aspect, the present disclosure provides a protocol signing apparatus for application to a trust management platform server, the apparatus comprising:

the system comprises a first sending unit, a second sending unit and a second sending unit, wherein the first sending unit is used for sending a protocol creation request to a protocol server, and the protocol creation request is used for indicating the protocol server to generate a to-be-signed protocol file carrying a digital certificate and a protocol link corresponding to the to-be-signed protocol file based on the protocol creation request;

the first receiving unit is used for receiving the protocol link of the protocol file to be signed returned by the protocol server;

The first sending unit is further configured to send the protocol link to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link.

In a fourth aspect, the present disclosure provides a protocol signing apparatus applied to a protocol server, the apparatus comprising:

the second receiving unit is used for receiving the protocol creation request sent by the trust management platform server;

the generation unit is used for generating a protocol file to be signed and a protocol link of the protocol file to be signed based on the protocol creation request;

the second sending unit is used for feeding back the protocol link to the trust management platform server, so that the trust management platform server sends the protocol link to a client corresponding to a protocol signing party;

the second receiving unit is further used for receiving an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generating an agreement document signing page according to the agreement document to be signed, and sending the agreement document signing page to the client;

and the acquisition unit is used for acquiring the signing information of the agreement signing party through the agreement document signing page and generating a signed agreement document according to the signing information and the agreement document to be signed.

In a fifth aspect, the present disclosure provides an electronic device comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform any of the methods of the first aspect or possible implementation manners of the first aspect, and any of the methods of the second aspect or possible implementation manners of the second aspect, via execution of the executable instructions.

In a sixth aspect, the presently disclosed embodiments provide a computer readable storage medium having stored thereon a computer program which when executed by a processor implements any of the methods of the first aspect or possible implementations of the first aspect, and any of the methods of the second aspect or possible implementations of the second aspect.

The technical scheme provided by the disclosure is applied to a trust management platform server, and a protocol creation request is sent to a protocol server, wherein the protocol creation request is used for indicating the protocol server to generate a protocol file to be signed carrying a digital certificate and a protocol link corresponding to the protocol file to be signed based on the protocol creation request; receiving a protocol link of the protocol file to be signed returned by the protocol server; and sending the protocol link to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link. According to the technical scheme provided by the embodiments of the disclosure, trusted service personnel are not required to sign files with clients offline, so that the labor and time cost is greatly reduced, and the signing efficiency of protocol files is improved.

Drawings

In order to more clearly illustrate the embodiments of the present disclosure or the technical solutions in the related art, a brief description will be given below of the drawings required for the embodiments or the related technical descriptions, and it is obvious that the drawings in the following description are some embodiments of the present disclosure, and other drawings may be obtained according to the drawings without any inventive effort for a person of ordinary skill in the art. In the drawings:

FIG. 1 is a flow chart of a method for signing a protocol according to an embodiment of the present disclosure;

FIG. 2 is a schematic diagram of a protocol configuration page according to an embodiment of the present disclosure;

FIG. 3 is a schematic diagram of a signing page of a protocol file according to one embodiment of the present disclosure;

FIG. 4 is a flowchart of a second method for signing a protocol according to an embodiment of the present disclosure;

FIG. 5 is a flowchart of a third method for signing a protocol according to an embodiment of the present disclosure;

FIG. 6 is a schematic diagram of a signing device according to an embodiment of the present disclosure;

FIG. 7 is a schematic diagram of another signing device according to an embodiment of the present disclosure;

fig. 8 is a schematic structural diagram of an electronic device according to an embodiment of the disclosure.

Detailed Description

Embodiments of the present disclosure are described in detail below, examples of which are illustrated in the accompanying drawings. The embodiments described below by referring to the drawings are exemplary and intended for the purpose of explaining the present disclosure and are not to be construed as limiting the present disclosure.

The terms first and second and the like in the description, the claims and the drawings of embodiments of the disclosure are used for distinguishing between similar objects and not necessarily for describing a particular sequential or chronological order. It is to be understood that the data so used may be interchanged where appropriate such that embodiments of the disclosure described herein may be capable of implementation in sequences other than those illustrated or described herein, for example. Furthermore, the terms "comprises," "comprising," and "having," and any variations thereof, are intended to cover a non-exclusive inclusion, such that a process, method, system, article, or apparatus that comprises a list of steps or elements is not necessarily limited to those steps or elements expressly listed but may include other steps or elements not expressly listed or inherent to such process, method, article, or apparatus.

The protocol signing method provided by the embodiment of the disclosure can be run on a terminal device or a server. The terminal device may be a local terminal device. The server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, basic cloud computing services such as big data and artificial intelligent platforms.

With the development of science and technology, a great number of protocol files which need to be signed by users are faced in daily life and work, and the signing of the protocol files is a vital ring in the information processing technology; in the related art, in the process of processing protocol files on a trust management platform server, because more protocol files need to be signed by clients among various processing flows, the protocol files need to be signed by trust management personnel in a line with the clients, and the more protocol files need to be signed, a great deal of manpower and time cost are consumed in the signing process of the protocol files, and the signing efficiency of the protocol files is lower.

Taking the example that the protocol signing method is applied to the protocol signing in the application program of the financial platform, various protocol files related to financial products can be provided in the application program of the financial platform: protocol files such as investment willingness books, asset injection files, board resolution files, disclaimers for asset allocation, etc. When creating a to-be-signed agreement document required by a user, a trust management platform server needs to send an agreement creation request to an agreement server, the agreement server creates an agreement link of the to-be-signed agreement document after receiving the agreement creation request, sends the agreement link to the trust management platform server, and sends the agreement link to a client corresponding to an agreement signing party through the trust management platform server, and finally the client signs the to-be-signed agreement document through the agreement link.

The following describes the technical scheme of the present disclosure and how the technical scheme of the present disclosure solves the above technical problems in detail with specific embodiments. The following embodiments may be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments. Embodiments of the present disclosure will be described below with reference to the accompanying drawings.

Fig. 1 is a flow chart of a method for signing a protocol according to an exemplary embodiment of the present disclosure, which may be applied to various devices having a data processing function. Taking the example that the method is applied to a trust management platform server, the scheme at least comprises the following steps S101-S103:

s101, sending a protocol creation request to a protocol server.

In some embodiments, the protocol creation request is used to instruct the protocol server to generate a to-be-signed protocol file carrying a digital certificate and a protocol link corresponding to the to-be-signed protocol file based on the protocol creation request.

In some embodiments, the digital certificate refers to a digital certificate that identifies the identity information of the communicating parties in the internet communication. In an embodiment of the present disclosure, the digital certificate of the to-be-signed agreement document refers to an identification of the to-be-signed agreement document.

In some embodiments, the digital certificate may be one or a combination of numbers, letters, graphics, or text, which will not be described in detail herein.

In some embodiments, the protocol creation request includes a protocol template file and protocol configuration information of the protocol file to be signed. The protocol configuration information at least comprises a protocol file name, a protocol file type, a signing expiration date, protocol signing party information and editing information of a protocol template file, and specifically, the editing information of the protocol template file can comprise signing position information signed by a protocol signing party in a protocol, signing date display position of signing date and the like.

In other embodiments, the protocol configuration information further includes a custom field. The custom field may be a filled-in signing party, a prompt value, etc. In fact, when the protocol signing party signs the to-be-signed protocol file, the signing party can sign the to-be-signed protocol file, and also can write text, date, number or document prompt and the like signed by the protocol signing party, and the specific process is not repeated here.

The protocol file types comprise an investment willingness book, an asset injection file, a board resolution file, an asset allocation disclaimer file and the like.

In some embodiments, the sending a protocol creation request to a protocol server includes steps S11-S13:

s11, acquiring a protocol template file, and displaying a protocol configuration page corresponding to the protocol template file on the trust management platform server. Specifically, the protocol configuration page is shown as 2.

S12, acquiring the protocol configuration information of the protocol template file through the protocol configuration page.

Specifically, taking the to-be-signed agreement document as the investment willingness book as an example, as shown in an agreement configuration page of fig. 2, the name of the to-be-signed agreement document is 'incentive equity unified management service validation function', the document type of the to-be-signed agreement document is the investment willingness book, the signing expiration date is 2024.01.31, and the signing party information includes a signing party 1: platform personnel, sign the subject: futiia, mailbox: futiia.

In some embodiments, the signing entity contained in the signing party information may be one or more.

And S13, transmitting a protocol creation request to a protocol server according to the protocol template file and the protocol configuration information.

After receiving the protocol creation request sent by the trust management platform server, the protocol server generates a new protocol file to be signed based on a protocol template file and protocol configuration information carried by the protocol creation request, and generates a digital certificate and a corresponding protocol link for the protocol file to be signed. It will be appreciated that the digital certificate may be used to verify the integrity of the agreement document to be signed on the one hand, and the signing party of the agreement on the other hand; specifically, the protocol server may calculate the information of the protocol signing party in the protocol configuration information according to a preset digital signature algorithm to obtain a target hash value; and then, carrying out hash operation on text content of the to-be-signed protocol file based on the target hash value, generating target abstract information of the to-be-signed protocol file, and then generating a digital certificate by the protocol server according to the target abstract information of the to-be-signed protocol file, wherein a preset digital signature algorithm is agreed in advance for the protocol server and the trust management platform server, the target abstract information is used for checking the integrity of the to-be-signed protocol file, and the corresponding target hash value is acquired by the protocol signing party and used for carrying out hash operation on the to-be-signed protocol file, so that the signing party which obtains the object of the to-be-signed protocol file and corresponds to the identity information of the protocol signing party can open the to-be-signed protocol file, and the safety of the file is ensured.

Taking a to-be-signed protocol file as an example of a board-of-board resolution file, a user sends a protocol creation request corresponding to the board-of-board resolution file to the protocol server through the trust management platform server, wherein the request comprises a board-of-board resolution file corresponding protocol template file and protocol configuration information, and then the protocol server generates a protocol link corresponding to the board-of-board resolution file and the board-of-board resolution file carrying a digital certificate based on the board-of-board resolution file corresponding protocol template file and the protocol configuration information.

S102, receiving the protocol link of the protocol file to be signed returned by the protocol server.

After the protocol server generates the protocol file to be signed and the corresponding protocol link, the protocol server can return the protocol link of the protocol file to be signed to the trust management platform server, so that the protocol file to be signed does not need to be frequently transmitted between the protocol server and the trust management platform server, and the protocol transmission efficiency and the security are improved. In some embodiments, the protocol server may be an independent physical server, a server cluster or a distributed system formed by a plurality of physical servers, or a cloud server providing cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDNs, and basic cloud computing services such as big data and artificial intelligence platforms.

And S103, the protocol link is sent to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link.

The client is mainly referred to as a trust management platform client, and can be installed on the electronic equipment used by the protocol signing party. The client receives the protocol link sent by the trust management platform server, and the protocol signing party can sign the protocol file to be signed on the client through the protocol link. Specifically, the client sends a signing request to the agreement server through the agreement link, the agreement server responds to the signing request, generates an agreement document signing page according to the agreement document to be signed corresponding to the agreement link, and sends the agreement document signing page to the client so as to acquire signing information of an agreement signing party through the agreement document signing page, and further generates a signed agreement document according to the signing information and the agreement document to be signed; further, after the signed agreement document is generated, hash operation can be performed on the text content (carrying the signed information) of the signed agreement document again according to the target hash value corresponding to the information of the signing party of the agreement, the summary information of the signed agreement document is generated, and then the agreement server generates the digital certificate from the summary information of the signed agreement document.

In some embodiments, after the protocol link is sent to the client corresponding to the protocol signer, the method includes steps S21-S22:

s21, receiving signing success information of the to-be-signed protocol file returned by the protocol server, and sending a first protocol file downloading request to the protocol server, so that the protocol server feeds back the signed protocol file corresponding to the to-be-signed protocol file based on the protocol file downloading request.

Specifically, taking a to-be-signed protocol file as an example of a board-to-board resolution file, when the trust management platform server receives the information that the board-to-board resolution file sent by the protocol server is signed successfully, the trust management platform server sends a download request corresponding to the signed board-to-board resolution file to the protocol server, and after the protocol server receives the download request, the signed board-to-board resolution file is queried based on the download request and the signed board-to-board resolution file is sent to the trust management platform server.

In some implementations, the protocol file to be signed and the signed protocol file are mainly PDF format files, and may also be files in other formats, which may be set according to practical situations.

S22, receiving and storing the signed protocol file.

Specifically, taking a to-be-signed protocol file as an board resolution file, after receiving the signed board resolution file sent by the protocol server, the trusted management platform server stores the signed board resolution file in a local server of the trusted management platform server, so as to facilitate a protocol signing party to obtain the corresponding signed board resolution file.

In some embodiments, the method further comprises steps S31-S34:

s31, receiving a second protocol file downloading request sent by a client corresponding to the protocol signing party.

In some embodiments, the second protocol file download request includes a protocol file identification and a protocol signer identification.

The protocol file identifier may be one or a combination of numbers, letters, graphics or characters, which will not be described herein.

The identity information of the signing party may be one or a combination of numbers, letters, graphics or characters, which will not be described herein.

In order to facilitate the protocol signing party to acquire the self-signed file, the identity of the protocol signing party is stored in the trust management platform server, and the acquisition efficiency of acquiring the signed file can be improved by storing the identity of the protocol signing party in advance.

S32, obtaining the signed protocol file corresponding to the protocol file identification in the second protocol file downloading request.

In some embodiments, the protocol creation request is further used to instruct the protocol server to generate a first file identifier of the protocol file to be signed based on the protocol creation request, and feed back the first file identifier to the trust management platform server, and the method further includes S321-S32:

s321, comparing a protocol file identifier in the second protocol file downloading request with a plurality of first file identifiers;

s322, obtaining the signed protocol file corresponding to the first file identification identical to the protocol file identification in the second protocol file downloading request.

In this embodiment, by unifying an agreement document to be signed, an agreement document identification of the signed agreement document, the efficiency of the agreement signer and the platform (trust management platform server) party to obtain the signed agreement document can be greatly improved in the following.

And S33, verifying the identity information of the protocol signing party according to the digital certificate of the signed protocol file and the protocol signing party identifier in the second protocol file downloading request.

In some embodiments, verifying the identity information of the protocol signing party based on the digital certificate of the signed protocol file and the protocol signing party identification in the second protocol file download request comprises: the trusted management platform server firstly obtains file content corresponding to the signed protocol file, calculates a protocol signing party identifier according to a preset digital signature algorithm to obtain a reference hash value, and then carries out hash operation on text content of the signed protocol file by the reference hash value to generate the reference abstract information; furthermore, according to the reference abstract information of the signed protocol file and the digital certificate (namely the target abstract information) of the signed protocol file, the identity information of the protocol signing party is verified; specifically, the verification of the identity information of the signing party of the protocol can be realized through the following formula:

the Ver represents the verification result of the identity information of the protocol signing party, when the ver=1, the verification of the identity information of the protocol signing party is passed, the signing party corresponding to the information of the protocol signing party carried by the second protocol file downloading request is the signing party of the protocol file to be signed, when the Ver is not equal to 1, the verification of the identity information of the protocol signing party is not passed, and the signing party corresponding to the information of the protocol signing party carried by the second protocol file downloading request is the signing party of the protocol file not to be signed; xi represents reference summary information; yi represents target digest information; i=1, 2, …, n i denotes a character identifier, and n denotes the number of characters.

And S34, if the identity information of the protocol signing party passes verification, the signed protocol file is sent to a client corresponding to the protocol signing party, so that the client displays the signed protocol file.

The technical scheme provided by the disclosure is applied to a trust management platform server, and a protocol creation request is sent to a protocol server, wherein the protocol creation request is used for indicating the protocol server to generate a protocol file to be signed carrying a digital certificate and a protocol link corresponding to the protocol file to be signed based on the protocol creation request; receiving a protocol link of the protocol file to be signed returned by the protocol server; and sending the protocol link to a client corresponding to a protocol signing party, so that the client signs the protocol file to be signed through the protocol link. According to the technical scheme, the trusted service personnel are not required to sign the file with the client in an off-line manner, so that the labor and time cost is greatly reduced, meanwhile, the transmission of the protocol file between the trusted management platform server and the trusted management platform server client is not required, the transmission efficiency and the security of the protocol file are improved, and the signing efficiency of the protocol file is improved.

Fig. 4 is a flowchart of a protocol signing method according to an exemplary embodiment of the present disclosure, which may be applied to various devices having a data processing function. Taking the application of the method to a protocol server as an example, the scheme at least includes the following steps S2201-S205:

s201, receiving a protocol creation request sent by a trust management platform server.

In some embodiments, the protocol creation request includes a protocol template file and protocol configuration information of the protocol file to be signed. The protocol configuration information at least comprises a protocol file name, a protocol file type, a signing expiration date, information of a protocol signing party and editing information of a protocol template file, and specifically, the editing information of the protocol template file can comprise signing position information signed by the protocol signing party in a protocol, signing date display position information of signing date and the like.

S202, generating a protocol file to be signed and a protocol link of the protocol file to be signed based on the protocol creation request.

In some embodiments, the generating the to-be-signed protocol file and the protocol link of the to-be-signed protocol file based on the protocol creation request further comprises: and generating the protocol file to be signed and the digital certificate of the protocol file to be signed according to the protocol template file and the protocol configuration information of the protocol file to be signed.

Specifically, taking editing information of a protocol template file as an example, generating the protocol file to be signed according to the protocol template file and the protocol configuration information of the protocol template file to be signed may include adjusting the protocol template file based on the editing information to generate the protocol file to be signed, for example, the editing information may include signing position information signed by a protocol signing party in a protocol, signing date display position information of signing date, and the protocol server may determine corresponding first position information in the protocol template file according to the signing position information, determine corresponding first position coordinates and second position coordinates in the protocol template file according to the signing date display position information, and further generate a signature component in the first position coordinates in the protocol template file and generate a date component in the second position coordinates to obtain the protocol file to be signed.

After the to-be-signed agreement document is generated, the agreement server can also generate a digital certificate corresponding to the to-be-signed agreement document according to the to-be-signed agreement document and the agreement signing party information in the agreement configuration information, wherein the digital certificate can be used for verifying the integrity of the to-be-signed agreement document on the one hand and verifying the identity information of the agreement signing party on the other hand. Specifically, the protocol server may calculate the information of the protocol signing party in the protocol configuration information according to a preset digital signature algorithm to obtain a target hash value; and then carrying out hash operation on the text content of the protocol file to be signed based on the target hash value, generating target abstract information of the protocol file to be signed, and further generating a digital certificate by the protocol server according to the target abstract information of the protocol file to be signed.

And S203, feeding back the protocol link to the trust management platform server, so that the trust management platform server sends the protocol link to a client corresponding to a protocol signing party.

S204, receiving an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generating an agreement document signing page according to the agreement document to be signed, and sending the agreement document signing page to the client.

After receiving an agreement signing request sent by a client corresponding to an agreement signing party, determining a corresponding agreement document to be signed according to an agreement link, and rendering the agreement document to be signed to an agreement document signing page; specifically, generating the protocol file signing page according to the protocol file to be signed may include, based on obtaining an initial protocol file page corresponding to the protocol file rendering to be signed, generating a signature component on the initial protocol file page according to the first position coordinates, and generating a date component on the initial protocol file page according to the second position coordinates and the timestamp information, to obtain the protocol file signing page.

Further, the protocol server may further verify the identity information of the current protocol signing party corresponding to the protocol signing request, specifically, the protocol server may first obtain the file content corresponding to the protocol file to be signed, and calculate the protocol signing party information carried by the protocol signing request according to a preset digital signature algorithm to obtain a reference hash value, and further perform hash operation on the text content of the protocol file to be signed with reference hash value to generate the reference abstract information; and verifying the information of the protocol signing party carried by the protocol signing request according to the reference abstract information of the protocol file to be signed and the digital certificate of the protocol file to be signed (namely the target abstract information), if the verification is passed, the signing party corresponding to the information of the protocol signing party carried by the protocol signing request is the signing party of the protocol file to be signed, the protocol file to be signed is complete, and the protocol server generates a protocol file signing page according to the protocol file to be signed and sends the protocol file signing page to the client corresponding to the protocol signing party.

S205, the signing information of the agreement signing party is obtained through the agreement document signing page, and a signed agreement document is generated according to the signing information and the agreement document to be signed.

The signing information of the agreement signing party mainly refers to signing information and/or signing time information of the agreement signing party, specifically may be official seal image information of the agreement signing party, or may be signing image information of the agreement signing party, which is not limited herein.

Taking a to-be-signed agreement document as an incentive share unified management service confirmation function as an example, as shown in fig. 3, the agreement link is sent to the client in a mail form (as shown in the left drawing of fig. 3), the agreement signer enters an agreement document signing page of the incentive share unified management service confirmation function by clicking a ' signing ' function button (as shown in the right drawing of fig. 3), the agreement signer can perform signing operation on a ' signing part ' component in the agreement document signing page through the client, after the signing operation is completed, the agreement document signing page obtains a signature image of the signing operation corresponding to the agreement signer through the ' signing part ' component, loads the signature image into a ' signing part ' in the agreement document signing page, and loads the signature image into position coordinates corresponding to the ' signing part ' component in the incentive share unified management service confirmation function agreement document, and finally, the signed agreement document can be generated based on the signature image corresponding to the ' signing part and time stamp information corresponding to the signing date component.

In some implementations, after the generating the signed agreement document from the signing information and the agreement document to be signed, further comprising: and updating the digital certificate of the protocol file to be signed according to the signing information to obtain the digital certificate of the signed protocol file.

The to-be-signed agreement document carries a digital certificate, which is an identification of the to-be-signed agreement document, so that after the to-be-signed agreement document is signed, a signed agreement document is generated, the digital certificate of the signed agreement document needs to be updated in order to distinguish the to-be-signed agreement document from the signed agreement document, and the digital certificate of the to-be-signed agreement document needs to be updated according to the signing information in order to ensure the uniqueness of the signed agreement document to an agreement signing party, so as to obtain the digital certificate of the signed agreement document. Specifically, the protocol server may perform hash operation on the text content of the signed protocol file (which already carries the signing information) according to the target hash value, generate the summary information of the signed protocol file, and further update the digital certificate with the summary information of the signed protocol file.

The following provides a specific embodiment for further explaining the protocol signing scheme in the present scheme, as shown in fig. 5, and specifically includes the following steps:

S301, the trust management platform server sends a protocol creation request to a protocol server.

S302, the protocol server generates a to-be-signed protocol file carrying a digital certificate and a protocol link corresponding to the to-be-signed protocol file based on the protocol creation request.

And S303, the protocol server sends the protocol link of the protocol file to be signed to the trust management platform server.

And S304, the trust management platform server sends the protocol link to a client corresponding to the protocol signing party.

And S305, the client sends a signing request to the protocol server through the protocol link.

In this embodiment, the agreement signing party triggers the signing function by clicking on the agreement link in the client and sends a signing request to the agreement server, thereby causing the agreement server to generate an agreement document signing page according to the agreement document to be signed and the signing request.

And S306, the agreement server generates an agreement document signing page according to the agreement document to be signed and the signing request.

S307, the protocol server sends the protocol file signing page to the client.

In actual operation, the protocol file signing page is displayed in the client, i.e. the client displays the protocol file signing page in the protocol server.

And S308, the client acquires the signing information of the agreement signing party through the agreement document signing page, and generates a signed agreement document according to the signing information and the agreement document to be signed.

S309, the protocol server saves the signed protocol file.

The technical scheme provided by the disclosure is applied to a protocol server and used for receiving a protocol creation request sent by a trust management platform server; generating a protocol link of a protocol file to be signed based on the protocol creation request; the protocol link is fed back to the trust management platform server, so that the trust management platform server sends the protocol link to a client corresponding to a protocol signing party; receiving an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generating an agreement document signing page according to the agreement document to be signed, and sending the agreement document signing page to the client; and acquiring the signing information of the agreement signing party through the agreement document signing page, and generating a signed agreement document according to the signing information and the agreement document to be signed. According to the technical scheme provided by the embodiments of the disclosure, a trusted service person does not need to manually generate the protocol file to be signed, and the trusted service person does not need to sign the file with a client offline, so that the labor and time cost is greatly reduced, and the signing efficiency of the protocol file is improved.

FIG. 6 is a schematic diagram of a protocol signing device according to an exemplary embodiment of the present disclosure;

the device is applied to a trust management platform server and comprises: a first transmitting unit 401 and a first receiving unit 402;

a first sending unit 401, configured to send a protocol creation request to a protocol server, where the protocol creation request is used to instruct the protocol server to generate a to-be-signed protocol file carrying a digital certificate and a protocol link corresponding to the to-be-signed protocol file based on the protocol creation request;

a first receiving unit 402, configured to receive a protocol link of the to-be-signed protocol file returned by the protocol server;

the first sending unit 401 is further configured to send the protocol link to a client corresponding to a protocol signing party, so that the client signs the to-be-signed protocol file through the protocol link.

In some embodiments, the protocol creation request includes a protocol template file and protocol configuration information of the protocol file to be signed;

the sending a protocol creation request to a protocol server, the apparatus further configured to:

acquiring a protocol template file, and displaying a protocol configuration page corresponding to the protocol template file on the trust management platform server;

Acquiring protocol configuration information of the protocol template file through the protocol configuration page;

and transmitting a protocol creation request to a protocol server according to the protocol template file and the protocol configuration information.

In some embodiments, the apparatus is further to:

receiving signing success information of the to-be-signed protocol file returned by the protocol server, and sending a first protocol file downloading request to the protocol server, so that the protocol server feeds back the signed protocol file corresponding to the to-be-signed protocol file based on the protocol file downloading request;

the signed protocol file is received and saved.

In some embodiments, the apparatus is further to:

receiving a second protocol file downloading request sent by a client corresponding to the protocol signing party, wherein the second protocol file downloading request comprises a protocol file identifier and a protocol signing party identifier;

acquiring a signed protocol file corresponding to a protocol file identifier in the second protocol file downloading request;

verifying the identity information of the protocol signing party according to the digital certificate of the signed protocol file and the protocol signing party identifier in the second protocol file downloading request;

And if the identity information of the protocol signing party passes the verification, the signed protocol file is sent to the client corresponding to the protocol signing party, so that the client displays the signed protocol file.

FIG. 7 is a schematic diagram of another protocol signing device according to an exemplary embodiment of the present disclosure;

the device is applied to a protocol server and comprises: a second receiving unit 501, a generating unit 502, a second transmitting unit 503, and an acquiring unit 504;

A second receiving unit 501, configured to receive a protocol creation request sent by a trust management platform server;

a generating unit 502, configured to generate a to-be-signed protocol file and a protocol link of the to-be-signed protocol file based on the protocol creation request;

a second sending unit 503, configured to feed back the protocol link to the trust management platform server, so that the trust management platform server sends the protocol link to a client corresponding to a protocol signing party;

the second receiving unit 501 is further configured to receive an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generate an agreement document signing page according to the agreement document to be signed, and send the agreement document signing page to the client;

and an obtaining unit 504, configured to obtain, through the agreement document signing page, signing information of an agreement signing party, and generate a signed agreement document according to the signing information and the agreement document to be signed.

the generating a to-be-signed protocol file and a protocol link to the to-be-signed protocol file based on the protocol creation request, the apparatus further configured to:

And generating the protocol file to be signed and the digital certificate of the protocol file to be signed according to the protocol template file and the protocol configuration information of the protocol file to be signed.

In some embodiments, after the generating of the signed agreement document from the signing information and the agreement document to be signed, the device is further to:

and updating the digital certificate of the protocol file to be signed according to the signing information to obtain the digital certificate of the signed protocol file.

It should be understood that apparatus embodiments and method embodiments may correspond with each other and that similar descriptions may refer to the method embodiments. To avoid repetition, no further description is provided here. Specifically, the apparatus may perform the above method embodiments, and the foregoing and other operations and/or functions of each module in the apparatus are respectively for corresponding flows in each method in the above method embodiments, which are not described herein for brevity.

The apparatus of the embodiments of the present disclosure are described above in terms of functional modules with reference to the accompanying drawings. It should be understood that the functional module may be implemented in hardware, or may be implemented by instructions in software, or may be implemented by a combination of hardware and software modules. Specifically, each step of the method embodiments in the embodiments of the present disclosure may be implemented by an integrated logic circuit of hardware in a processor and/or an instruction in software form, and the steps of the method disclosed in connection with the embodiments of the present disclosure may be directly implemented as a hardware decoding processor or implemented by a combination of hardware and software modules in the decoding processor. Alternatively, the software modules may be located in a well-established storage medium in the art such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, and the like. The storage medium is located in a memory, and the processor reads information in the memory, and in combination with hardware, performs the steps in the above method embodiments.

Fig. 8 is a schematic block diagram of an electronic device provided by an embodiment of the present disclosure, which may include:

a memory 601 and a processor 602, the memory 601 being adapted to store a computer program and to transfer the program code to the processor 602. In other words, the processor 602 may call and run a computer program from the memory 601 to implement the methods in the embodiments of the present disclosure.

For example, the processor 602 may be used to perform the method embodiments described above in accordance with instructions in the computer program.

In some embodiments of the present disclosure, the processor 602 may include, but is not limited to:

a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components, or the like.

In some embodiments of the present disclosure, the memory 601 includes, but is not limited to:

volatile memory and/or nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous Link DRAM (SLDRAM), and Direct memory bus RAM (DR RAM).

In some embodiments of the present disclosure, the computer program may be partitioned into one or more modules that are stored in the memory 601 and executed by the processor 602 to perform the methods provided by the present disclosure. The one or more modules may be a series of computer program instruction segments capable of performing the specified functions, which are used to describe the execution of the computer program in the electronic device.

As shown in fig. 8, the electronic device may further include:

a transceiver 603, the transceiver 603 being connectable to the processor 602 or the memory 601.

The processor 602 may control the transceiver 603 to communicate with other devices, and in particular, may send information or data to other devices or receive information or data sent by other devices. The transceiver 603 may include a transmitter and a receiver. The transceiver 603 may further include antennas, the number of which may be one or more.

It will be appreciated that the various components in the electronic device are connected by a bus system that includes, in addition to a data bus, a power bus, a control bus, and a status signal bus.

The present disclosure also provides a computer storage medium having stored thereon a computer program which, when executed by a computer, enables the computer to perform the method of the above-described method embodiments. Alternatively, embodiments of the present disclosure also provide a computer program product comprising instructions which, when executed by a computer, cause the computer to perform the method of the method embodiments described above.

When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, produces a flow or function, in whole or in part, according to embodiments of the present disclosure. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, fiber optic, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a digital video disc (digital video disc, DVD)), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.

Those of ordinary skill in the art will appreciate that the various illustrative modules and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In the several embodiments provided in the present disclosure, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, and for example, the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or modules, which may be in electrical, mechanical, or other forms.

The modules illustrated as separate components may or may not be physically separate, and components shown as modules may or may not be physical modules, i.e., may be located in one place, or may be distributed over a plurality of network elements. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment. For example, functional modules in various embodiments of the present disclosure may be integrated into one processing module, or each module may exist alone physically, or two or more modules may be integrated into one module.

The foregoing is merely a specific embodiment of the disclosure, but the protection scope of the disclosure is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the disclosure, and it should be covered in the protection scope of the disclosure. Therefore, the protection scope of the present disclosure shall be subject to the protection scope of the claims.

Claims

1. A method of signing a protocol as applied to a trust management platform server, the method comprising:

2. The method of claim 1, wherein the protocol creation request includes a protocol template file and protocol configuration information of the protocol file to be signed;

the sending a protocol creation request to a protocol server includes:

3. The method according to claim 1, wherein the method further comprises:

The signed protocol file is received and saved.

4. A method according to claim 3, characterized in that the method further comprises:

5. A method of signing a protocol, applied to a protocol server, the method comprising:

6. The method of claim 5, wherein the protocol creation request includes a protocol template file and protocol configuration information of the protocol file to be signed;

the generating the to-be-signed protocol file and the protocol link of the to-be-signed protocol file based on the protocol creation request includes:

7. The method of claim 6, wherein after generating a signed agreement document from the signing information and the agreement document to be signed, further comprising:

8. A protocol signing device for application to a trust management platform server, the device comprising:

9. A protocol signing device for application to a protocol server, said device comprising:

The second receiving unit is further configured to receive an agreement signing request sent by a client corresponding to the agreement signing party based on the agreement link, generate an agreement document signing page according to the agreement document to be signed, and send the agreement document signing page to the client;

10. An electronic device, comprising:

a processor; and

a memory for storing executable instructions of the processor;

wherein the processor is configured to perform the method of any of claims 1-7 via execution of the executable instructions.

11. A computer readable storage medium, on which a computer program is stored, characterized in that the computer program, when being executed by a processor, implements the method of any of claims 1-7.