WO2018019187A1 - 一种订立电子合同的方法及服务器 - Google Patents

一种订立电子合同的方法及服务器 Download PDF

Info

Publication number
WO2018019187A1
WO2018019187A1 PCT/CN2017/093921 CN2017093921W WO2018019187A1 WO 2018019187 A1 WO2018019187 A1 WO 2018019187A1 CN 2017093921 W CN2017093921 W CN 2017093921W WO 2018019187 A1 WO2018019187 A1 WO 2018019187A1
Authority
WO
WIPO (PCT)
Prior art keywords
contract
signing
information
identifier
picture
Prior art date
Application number
PCT/CN2017/093921
Other languages
English (en)
French (fr)
Inventor
陆舟
于华章
Original Assignee
飞天诚信科技股份有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 飞天诚信科技股份有限公司 filed Critical 飞天诚信科技股份有限公司
Priority to US16/307,167 priority Critical patent/US10977432B2/en
Publication of WO2018019187A1 publication Critical patent/WO2018019187A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/18—Legal services
    • G06Q50/188—Electronic negotiation
    • 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
    • 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
    • G06F40/00—Handling natural language data
    • G06F40/10—Text processing
    • G06F40/166—Editing, e.g. inserting or deleting
    • G06F40/171—Editing, e.g. inserting or deleting by use of digital ink
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
    • G06V30/40—Document-oriented image-based pattern recognition
    • G06V30/41—Analysis of document content
    • G06V30/413—Classification of content, e.g. text, photographs or tables
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • G06Q50/16—Real estate
    • G06Q50/167—Closing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
    • G06V30/10—Character recognition
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06V—IMAGE OR VIDEO RECOGNITION OR UNDERSTANDING
    • G06V30/00—Character recognition; Recognising digital ink; Document-oriented image-based pattern recognition
    • G06V30/40—Document-oriented image-based pattern recognition

Definitions

  • the invention relates to a method and a server for establishing an electronic contract, belonging to the field of electronic commerce.
  • the object of the present invention is to provide a method and a server for entering into an electronic contract.
  • signing an electronic contract the two parties to the transaction avoid the limitation of time and place, provide a convenient and quick signing method, and reduce waste of resources.
  • the risk of economic loss caused by the tampering of the electronic contract during the transmission process is avoided, that is, the what is seen and signed is achieved.
  • an aspect of the present invention provides a method of establishing an electronic contract, specifically comprising:
  • Step A1 The first client sends a contract document to the server.
  • Step A2 The server converts the contract document into a contract picture, and generates a contract identifier associated with the contract document and the contract picture, and sends the contract identifier and the contract picture to the first client;
  • step A2 may be: the server converts the contract document into a contract picture according to a preset conversion relationship, generates a contract identifier, and generates a picture identifier corresponding to each contract picture, and the contract identifier is associated with the contract document and all contract pictures, and the contract is The logo, the picture identifier, and the contract picture are sent to the first client;
  • Step A3 The first client generates signature location information according to the signing location set by the creator on the contract picture; and associates the contract identifier, the signing location information, and the signer identity information input by the creator to the server;
  • Step A3 specifically includes:
  • Step 301 The first client sends the signer input signer information to the server.
  • the signing party information includes: the signing party identity information and the signing party code, or the signing party identity information and authentication method, or the signing party identity information, the signing party code and the authentication method;
  • Step 302 The server generates a signer identifier associated with the signer information, and sends the signer identifier to the second client.
  • Step 303 The second client receives the signing location corresponding to the signing party identity information, and generates signing location information according to the signing location set by the creator on the contract picture; the contract identifier and the signing location information associated with the contract identifier Corresponding to the signer ID associated with the signer identity information and transmitting to the server;
  • generating the signing location information according to the signing location set by the creator on the contract picture comprises: generating the signing location information according to the picture identifier of the contract picture and the coordinate information of the signing location where the signing location information is located.
  • step A4 the server sends the contract identifier, the contract picture, and the signing party location information to the second client according to the signer identity information;
  • identity information of the signatory is specifically the signing party's contact information
  • Step A4 specifically includes:
  • Step 101 The server sends a signing reminder including the contract identifier to the second client according to the signing party contact information.
  • Step 102 The second client receives the trigger information of the signing party to sign the reminder, and sends the contract identifier to the server.
  • Step 103 The server obtains the signing location information and the contract picture according to the contract identifier and the signing party contact manner, and sends the contract picture and the signing location information to the second client.
  • the signing party identity information is specifically a username of the signing party login application system
  • Step A4 specifically includes:
  • Step 201 The second client starts the application system, receives the username and password entered by the signing party, and sends the username and password to the server.
  • Step 202 After determining, by the server, the identity of the signing party according to the user name and the password, the server obtains the signing location information and the contract identifier according to the username, and sends the contract identifier, the contract picture and the signing location information associated with the contract identifier to the second client.
  • the signing party information includes a signing party code
  • Step A4 specifically includes:
  • Step 401 The server determines whether there is a signing order according to the signing party code in the signer information, if yes, step 403 is performed, otherwise step 402 is performed;
  • Step 402 The server sends the contract identifier to all second clients according to the signer identity information in the plurality of signer information.
  • Step 403 The server obtains the signer information according to the signing party coding order as the current signer information, according to the signing party in the current signing party information.
  • the information sends the contract identification, the contract picture and the signing party location information to the second client;
  • the server further includes: the server determines whether there is any signator information that has not been obtained, and if yes, returns to step 403, otherwise ends.
  • the signing party information includes an authentication method:
  • the authentication mode may be: face identity authentication or real name identity authentication or fingerprint identity authentication or short message identity authentication.
  • the method further comprises:
  • Step 501 The server obtains an authentication mode from the signer information, and sends an authentication page link to the second client according to the authentication mode.
  • Step 502 The second client loads and displays the identity authentication page according to the authentication page link, receives the identity authentication information input by the signing party, and sends the identity authentication information to the server.
  • Step 503 The server determines, according to the identity authentication information, whether the identity of the signing party is legal. If yes, step A4 is performed. Otherwise, the identity authentication failure reminder is sent to the second client, and the process ends.
  • the second client displays the signing position on the contract picture according to the signing location information, and receives the signing picture uploaded by the signing party or the signing picture sent by the server; sending the contract image of the contract picture to the server, if receiving The signed picture uploaded by the signing party also needs to send the signed picture to the server;
  • Step A6 The server acquires the contract document according to the contract identifier, and writes the signed image into the contract document according to the signed location information.
  • a digital certificate corresponding to the signer identity information is pre-stored in the server;
  • the method further includes: the server acquiring the digital certificate according to the signer identity information, and writing the digital certificate into the contract document.
  • the method further comprises:
  • Step 601 the server determines whether the contract document format is a preset format, if yes, step A2 is performed, otherwise step 602 is performed;
  • Step 602 The server determines whether the contract document format can be converted into a preset format, and the server converts the contract document into a preset format, and performs step A2. Otherwise, sending the contract document format to the first client does not support the reminder.
  • first client and the second client may be the same client.
  • a server for entering an electronic contract comprising:
  • An identifier generating module configured to receive a contract document sent by the first client, convert the contract document into a contract picture, and generate a contract identifier associated with the contract document and the contract picture;
  • the identity generation module specifically includes:
  • a fifth receiving submodule configured to receive a contract document sent by the first client
  • a first conversion submodule configured to convert the contract document received by the fifth receiving submodule into a contract picture according to a preset conversion relationship
  • the identifier generation sub-module is used to generate a contract identifier and a picture identifier; the contract identifier is associated with the contract document and all contract pictures, and each contract picture corresponds to one picture identifier.
  • the signing location information received by the first receiving module specifically includes: a picture identifier of the contract picture where the signing location is located and coordinate information of the signing position.
  • a first sending module configured to send the contract identifier and the contract picture generated by the identifier generating module to the first client
  • a first receiving module configured to receive a contract identifier, a signing location information, and a signing party identity information sent by the first client;
  • the first receiving module specifically includes:
  • a third receiving submodule configured to receive a contract identifier, a signing location information, and a signing party information sent by the first client, and generate a signing party identifier associated with the signing party information
  • the signing party information includes: the signing party identity information and the signing party code, or the signing party identity information and authentication method, or the signing party identity information, the signing party code and the authentication method;
  • a fourth sending submodule configured to send the signer identifier received by the third receiving submodule to the first client
  • the fourth receiving submodule is specifically configured to receive the contract identifier, the signing party identifier, and the signing location information sent by the first client.
  • the second sending module is configured to send the contract identifier, the contract picture and the signing party location information associated with the contract identifier to the second client according to the signer identity information received by the first receiving module;
  • the signer identity information received by the first receiving module 13 is specifically a signing party contact mode
  • the second sending module specifically includes:
  • a first sending submodule configured to send, by the signing party contact information received by the first receiving module, a signing reminder including a contract identifier to the second client;
  • a first receiving submodule configured to receive a contract identifier sent by the second client
  • the second sending submodule is configured to obtain the signing location information and the contract picture according to the contract identifier and the signing party contact information received by the first receiving submodule, and send the contract picture and the signing location information to the second client.
  • the signer identity information received by the first receiving module is specifically a username of the signing party login application system
  • the second sending module specifically includes:
  • a second receiving submodule configured to receive a username and a password sent by the second client
  • a first determining submodule configured to determine, according to the username and password received by the first receiving module, whether the identity of the signing party is legal;
  • a third sending submodule configured to: when the first determining submodule determines that the signing party identity is legal, obtain the signing location information and the contract identifier according to the user name, and send the contract identifier, the contract picture and the signing location information associated with the contract identifier to Second client.
  • the third party receiving submodule receives the signing party information, the signing party identity information and the signing party code, or the signing party identity information, the signing party code, and the authentication mode;
  • the second sending module specifically includes:
  • a second determining submodule configured to determine, according to the signing party code in the signing party information, whether there is a signing order
  • a fifth sending submodule configured to send, by the second determining submodule, the contract identifier to all the second clients according to the signing party identity information in the signing party information when determining that there is no signing sequence;
  • a first obtaining submodule configured to: when the second determining submodule determines that there is a signing order, obtain the signing party information according to the signing party encoding order as the current signing party information; and further, the first determining module determines that the signing party has not been obtained yet Obtaining signer information as current signator information according to the signing party coding order;
  • a sixth sending submodule configured to send the contract identifier, the contract picture, and the signing party location information to the second client according to the signer identity information in the current signer information acquired by the first obtaining submodule;
  • the server further includes: a first determining module, configured to determine whether there is any signator information that has not been obtained.
  • the signer information received by the third receiving submodule includes: the signing party information includes: the signing party identity information and the authentication mode, or the signing party identity information, the signing party code, and the authentication mode;
  • the server also includes:
  • a third sending module configured to obtain an authentication mode from the signer information received by the third receiving submodule, and send an authentication page link to the second client according to the authentication mode;
  • a second determining module configured to receive identity authentication information sent by the second client, and determine, according to the identity authentication information, whether the identity of the signing party is legal;
  • a second sending module specifically configured to: when the second determining module determines that the signing party is legal, the contract image and the contractor location information associated with the contract identifier according to the signer identity information received by the first receiving module Sent to the second client;
  • the fourth sending module is configured to send an identity authentication failure reminder to the second client if the second determining module determines that the signing party identity is invalid.
  • the authentication mode in the signer information received by the third receiving submodule is specifically face identity authentication or real name identity authentication or fingerprint identity authentication or short message identity authentication.
  • the second receiving module is configured to receive a contract identifier sent by the second client, and is further configured to receive a contract identifier and a signature picture sent by the second client;
  • a signing module configured to: if the second receiving module receives the contract identifier, write the signed image pre-stored in the server to the contract document associated with the contract identifier according to the signed location information, if the second receiving module receives the contract identifier and the signed image Write the signed image pre-stored in the server to the contract document.
  • the server further comprises:
  • a storage module configured to store a digital certificate corresponding to the identity information of the signatory
  • the digital certificate writing module is configured to obtain a digital certificate in the storage module according to the identity information of the signing party, and write the digital certificate into the contract document obtained by the signing module.
  • server further includes:
  • a third receiving module configured to receive a contract verification picture sent by the second client
  • a third determining module configured to obtain a contract document according to the contract identifier received by the second receiving module, compare the contract verification image received by the third receiving module with the contract document, and determine whether the content is consistent;
  • the third determining module can include:
  • a fourth determining sub-module configured to determine whether a resolution of the contract verification picture received by the third receiving module is greater than a preset value
  • a fifth determining sub-module configured to determine, by the fifth determining sub-module, that the resolution of the contract verification image received by the third receiving module is greater than a preset value, and comparing the contract verification image received by the third receiving module with the contract document, and determining Whether the content is consistent;
  • the eighth sending submodule is configured to: when the fifth determining submodule determines that the resolution of the contract verification picture received by the third receiving module is not greater than a preset value, sending a contract verification picture unqualified reminder to the second client.
  • the signing module is specifically configured to: when the third judging module determines that the contract verification picture is consistent with the content of the contract document, write the signed picture received by the second receiving module to the contract document acquired by the third judging module according to the signing position information;
  • the third determining module may further include:
  • the sixth determining sub-module is configured to perform optical character recognition on the contract verification picture received by the third receiving module, perform character count on the recognized text, and determine whether the number of words in the contract verification picture is greater than a preset value;
  • a seventh determining sub-module configured to determine, by the sixth determining sub-module, that the number of words in the contract verification picture received by the third receiving module is greater than a preset value, and comparing the contract verification picture received by the third receiving module with the contract document, Determine whether the content is consistent;
  • a ninth sending submodule configured to: when the seventh determining submodule determines that the number of words in the contract verification picture received by the third receiving module is not greater than a preset value, sending a contract verification picture unqualified reminder to the second client;
  • the sixth sending module is configured to: when the third determining module determines that the contract verification picture is inconsistent with the content of the contract document, send a contract tampering reminder to the second client.
  • the parties to the transaction avoid the limitation of time and place when signing the contract, providing a convenient and quick signing method, and reducing waste of resources, thereby avoiding the economy caused by the falsification of the electronic contract in the transmission process.
  • the risk of loss is achieved by what you see and what you sign.
  • Embodiment 1 is a flow chart of a method for entering an electronic contract according to Embodiment 1 of the present invention
  • Embodiment 2 is a flow chart of a method for creating an electronic contract according to Embodiment 2 of the present invention.
  • FIG. 3 is a flowchart of a method for signing an electronic contract according to Embodiment 2 of the present invention.
  • Embodiment 4 is a contract picture before the creation side sets the signing position in Embodiment 2 of the present invention.
  • FIG. 5 is a setting page after the creation side sets the signing position in Embodiment 2 of the present invention.
  • FIG. 7 is a contract picture of the completion of the signing of Zhang San in the second embodiment of the present invention.
  • FIG. 8 is a picture of a contract after all signatories have signed up in Embodiment 2 of the present invention.
  • FIG. 9 is a block diagram of a server for entering an electronic contract according to Embodiment 3 of the present invention.
  • a method for establishing an electronic contract specifically includes:
  • Step A1 The first client sends a contract document to the server.
  • Step A2 The server converts the contract document into a contract picture, and generates a contract identifier associated with the contract document and the contract picture, and sends the contract identifier and the contract picture to the first client;
  • step A2 may be: the server converts the contract document into a contract picture according to a preset conversion relationship, generates a contract identifier, and generates a picture identifier corresponding to each contract picture, and the contract identifier is associated with the contract document and all contract pictures, and the contract is The logo, the picture identifier, and the contract picture are sent to the first client;
  • Step A3 The first client generates signature location information according to the signing location set by the creator on the contract picture; and associates the contract identifier, the signing location information, and the signer identity information input by the creator to the server;
  • Step A3 specifically includes:
  • Step 301 The first client sends the signer input signer information to the server.
  • the signing party information includes: the signing party identity information and the signing party code, or the signing party identity information and authentication method, or the signing party identity information, the signing party code and the authentication method;
  • Step 302 The server generates a signer identifier associated with the signer information, and sends the signer identifier to the second client.
  • Step 303 The second client receives the signing location corresponding to the signing party identity information, and generates signing location information according to the signing location set by the creator on the contract picture; the contract identifier and the signing location information associated with the contract identifier Corresponding to the signer ID associated with the signer identity information and transmitting to the server;
  • generating the signing location information according to the signing location set by the creator on the contract picture comprises: generating the signing location information according to the picture identifier of the contract picture and the coordinate information of the signing location where the signing location information is located.
  • Step A4 The server sends the contract identifier, the contract picture, and the signing party location information to the second client according to the identity information of the signatory;
  • identity information of the signatory is specifically the signing party's contact information
  • Step A4 specifically includes:
  • Step 101 The server sends a signing reminder including the contract identifier to the second client according to the signing party contact information.
  • Step 102 The second client receives the trigger information of the signing party to sign the reminder, and sends the contract identifier to the server.
  • Step 103 The server obtains the signing location information and the contract picture according to the contract identifier and the signing party contact manner, and sends the contract picture and the signing location information to the second client.
  • signing party identity information is specifically the username of the signing party to log in to the application system
  • Step A4 specifically includes:
  • Step 201 The second client starts the application system, receives the username and password entered by the signing party, and sends the username and password to the server.
  • Step 202 After determining, by the server, the identity of the signing party according to the user name and the password, the server obtains the signing location information and the contract identifier according to the username, and sends the contract identifier, the contract picture and the signing location information associated with the contract identifier to the second client.
  • the signing party information includes a signing party code
  • Step A4 specifically includes:
  • Step 401 The server determines whether there is a signing order according to the signing party code in the signer information, if yes, step 403 is performed, otherwise step 402 is performed;
  • Step 402 The server sends the contract identifier to all second clients according to the signer identity information in the plurality of signer information.
  • Step 403 The server obtains the signer information as the current signer information according to the signing party coding order, and sends the contract identifier, the contract picture, and the signing party location information to the second client according to the signer identity information in the current signer information;
  • the server further includes: the server determines whether there is any signator information that has not been obtained, and if yes, returns to step 403, otherwise ends.
  • the signing party information includes an authentication method:
  • the authentication mode may be: face identity authentication or real name identity authentication or fingerprint identity authentication or short message identity authentication.
  • step A3 before step A4, the method further includes:
  • Step 501 The server obtains an authentication mode from the signer information, and sends an authentication page link to the second client according to the authentication mode.
  • Step 502 The second client loads and displays the identity authentication page according to the authentication page link, receives the identity authentication information input by the signing party, and sends the identity authentication information to the server.
  • Step 503 The server determines, according to the identity authentication information, whether the identity of the signing party is legal. If yes, step A4 is performed. Otherwise, the identity authentication failure reminder is sent to the second client, and the process ends.
  • Step A5 The second client displays the signing position on the contract picture according to the signing location information, and receives the signing picture uploaded by the signing party or the signing picture sent by the server; and sends the contract image of the contract picture to the server, if the signing party is received
  • the uploaded signed image also needs to send the signed image to the server;
  • Step A6 The server acquires the contract document according to the contract identifier, and writes the signed image into the contract document according to the signed location information.
  • a digital certificate corresponding to the signer identity information is pre-stored in the server;
  • the method further includes: the server acquiring the digital certificate according to the signer identity information, and writing the digital certificate into the contract document.
  • the method further comprises:
  • Step 601 the server determines whether the contract document format is a preset format, if yes, step A2 is performed, otherwise step 602 is performed;
  • Step 602 The server determines whether the contract document format can be converted into a preset format, and the server converts the contract document into a preset format, and performs step A2. Otherwise, sending the contract document format to the first client does not support the reminder.
  • first client and the second client may be the same client.
  • a method for creating an electronic contract specifically includes:
  • Step 701 The first client starts the application system, and receives login request information input by the creator.
  • the login request information includes a username and a password.
  • Step 702 The first client sends login request information to the server.
  • the login request information sent by the client to the server is specifically ⁇ "username", “zhangsan@ftsafe.com", “passwd”: "123456” ⁇ , the username username is zhangsan@ftsafe.com, and the password passwd is 123456.
  • Step 703 The server determines, according to the received login request information, whether the identity of the created party is legal. If yes, step 705 is performed, otherwise step 704 ends.
  • the server retrieves the database according to the obtained creation name zhangsan@ftsafe.com and password 123456. If the database has the same information, the identity authentication succeeds, otherwise the identity authentication fails and ends.
  • Step 704 The server sends the authentication failure information to the first client, and ends.
  • Step 705 The server sends the authentication success information to the first client.
  • Step 706 The first client receives the contract document uploaded by the creator, the signing party code set by the creator, the signing party identity information, and the authentication mode, and generates signer information according to the signing party code, the signing party identity information, and the authentication mode.
  • Step 706 is further configured to: the client receives the pre-saved unsigned contract document selected by the creator, the signing party code set by the creator, the signing party identity information, and the authentication mode, and generates according to the signing party code, the signing party identity information, and the authentication mode. Signatory information.
  • the signing code is used to mark the signing order of the signing party.
  • Signatory identity information including email address, real name and mobile number.
  • the authentication method includes any one or combination of multiple authentication methods such as SMS, face, fingerprint, and real name.
  • the creation party can set a signing party or a plurality of signing parties.
  • the first client generates two signing party information: [ ⁇ "number”: “1” , "email”: “zhangsan@ftsafe.com”, “realname”: “Zhang San”, “authtype”: “1”, “phonesn”: “18201331111” ⁇ , ⁇ "number”:”2",”email”:"lisi@ftsafe.com”,”realname”:" ⁇ ",”authtype”:"0”,”phonesn”:”18201332222” ⁇ ].
  • the signature code number is used to identify the signing order of the signing party, the signature code number is 1, indicating that the current signing party is the first signing contract; the email address email is test@ftsafe.com; the real name real name is Zhang San; the authentication method
  • the authtype is used to identify the signing party's authentication mode.
  • a plurality of signing party identity authentication modes such as a short message, a face, a fingerprint, and a real name, are provided.
  • the authentication mode authtype is 0, the sign does not need to perform the signer identity authentication;
  • the authentication mode authtype is 1, the sign is authenticated by the sender.
  • the authentication mode authtype is 2
  • the sign is authenticated by the face.
  • the authentication mode authtype is 3, the sign is authenticated by the real name.
  • the mobile phone number phonesn is 18201331111.
  • the contract document in this embodiment 2 is specifically:
  • Party A (hereinafter referred to as Party A)
  • Party A will lease the house located at No. 201, Building 9, Street Garden Community, Beijing Xueyuan Road, to Party B for residence.
  • the lease term is from January 1, 2016 to December 31, 2016, for 12 months.
  • the monthly rent of the house is RMB 2,000, which is settled by month/quarter/year.
  • Party B shall bear the water, electricity, heating, gas, telephone, property and other expenses incurred by Party B. At the end of the lease, Party B shall pay the arrears.
  • Party B agrees to pay 2,000 yuan as a deposit. When the contract is terminated, it will be used as a rent.
  • the rental period of the house is from January 1, 2016 to December 31, 2016. During this period, if either party requests to terminate the contract, it must notify the other party three months in advance and pay the penalty of the total rent of the other party for 2000; if Party A transfers the house, Party B has the right of first refusal.
  • Step 707 The first client sends the contract document and the signing party information to the server.
  • Step 708 The server receives and saves the contract document and the signing party information sent by the first client, converts the contract document into a contract picture, and generates identification information; generates a signing party identifier according to the signing party information, and generates according to the signing party identifier and the identifier information. First response data.
  • the identifier information includes a contract identifier, a document identifier, a page number identifier, and a picture identifier.
  • a contract uniquely corresponds to a contract identifier; each contract can contain one contract document or multiple contract documents, each contract document uniquely corresponds to one document identifier; each page of the contract document corresponds to a page number identifier.
  • the server converts the contract document into a contract picture by page, and each contract picture uniquely corresponds to one picture identifier.
  • the identifier information generated by the server according to the received contract document is specifically: the contract identifier is 1, the document identifier is 1, the page number identifier is 1, and the picture identifier is 1.
  • the identification information is the only serial number generated by the server.
  • the first response data is as follows:
  • the contract information contractinfo includes: the contract unique identifier contractid is 1.
  • the signer addressees include: the signer ID addresseeid is 1; the real name realname is Zhang San; and the email address email is zhangsan@ftsafe.com.
  • the document information docinfo includes: the document identifier docid is 1; the page identifier pageid is 1; the page width pagewidth is 500; the page height pageheight is 400; and the image identifier imgid is 1.
  • Step 708 further includes: the server receives the contract document sent by the first client, and determines whether the contract document format is a preset format or can be converted into a preset format by obtaining a file name suffix of the contract document, if not a preset format, and Converting to a preset format prompts that the current format is not supported; if the received contract document format is a preset format, the current contract document is saved and the contract document is converted into a contract picture; if the received contract document format is not a preset format and can be Converting to a preset format converts the contract document to a preset format, and saves the converted contract document and converts the converted contract document into a contract picture.
  • the preset format is PDF format
  • the format that can be converted into a PDF format is TXT, XLS, PPT, DOC, and the like.
  • the server obtains the suffix of the received contract document to determine whether the contract document format is PDF format or can be converted into a PDF format. If the received contract document format is not a PDF format and cannot be converted into a PDF format, the prompt is not Support the current format; if the received contract document format is PDF, save the current contract document, and call the pdfToImg method to convert the contract document into a contract picture; if the contract document format is not PDF format and is TXT, XLS, PPT, DOC Any one of the formats calls the Msoffice interface to convert the contract document into a contract document in PDF format, saves the contract document in PDF format, and calls the pdfToImg method to convert the contract document in PDF format into a contract picture. Converting to a contract picture prevents secondary modifications to the contract document.
  • the format of the current contract document is DOC format
  • the server calls the Msoffice interface to convert the contract document into a contract document in PDF format, saves the contract document in PDF format, and calls the pdfToImg method to convert the contract document in PDF format into a contract picture.
  • Step 709 The server returns the first response data to the first client.
  • Step 710 The first client loads and displays the contract picture according to the first response data, and receives the signature type and signature location information correspondingly set by the creator according to different signator information, and according to the identification information, the signing party identifier, the signature location information, and The signature type generates a signature attribute.
  • the first client loads and displays the contract picture according to the first response data, that is, the contract party sets the contract picture before the signing position, as shown in FIG. 4 .
  • the signature type that the creator can select includes a signature, a signature, a date, a company name, and the like.
  • the signature location information specifically includes: a distance of the signature picture relative to the top of the page, a distance of the signature picture relative to the left end of the page, a width of the signature picture, a height of the signature picture, a document in which the signature picture is located, a page number, and the like.
  • Figure 5 shows the setting page after the founder sets the signing position.
  • the signature position of Zhang San is set to the position shown by the signing box of Party B in FIG. 5
  • the signing position of Li Si is the position shown by the signing box of Party A shown in FIG. 5.
  • the first client generates the signature attribute according to the contract identifier, the signer identifier, the signature type, and the signature location information, specifically:
  • the signature attribute includes: the document identifier docid where the signature image is located is 1; the page number identifier of the signature image is 1; the signer userid is Zhang 3; the distance of the signature image relative to the top of the page is 100 mm; the signature image is relative to The left side of the page has a left of 30 mm; the signature image has a width of 25 mm; the signature image height has a height of 20 mm; the signature type fieldtype is sign, indicating that the signature type is a signature; and the contract image is in a contract identifier of 1.
  • Step 711 The first client sends the signature attribute to the server.
  • Step 712 The server saves the signature attribute.
  • Step 713 The server determines, according to the signing party code, whether there is a signing sequence, if yes, step 717 is performed, otherwise step 714 is performed.
  • the server obtains the signing party code from any one of the signer information, determines whether the signing party code is 0, and if there is no signing order, otherwise there is a signing order;
  • the server obtains "number” from the signer information: "1"; a value of 1 for the signing party code "number" indicates that there is a signing order.
  • Step 714 The server sends a signing reminder to all signing parties according to the signing party information, and waits to receive the signing information.
  • the server obtains an email address from the signing party information, and sends a signing reminder to the signing party through the email address. You can also get the mobile number from the signing party information and send a signing reminder to the signing party via SMS.
  • Step 715 The server determines whether the signing information returned by all signing parties is received within a preset time. If yes, step 716 is performed, otherwise the process ends.
  • Step 716 The server sends a signing completion reminder to the first client.
  • Step 717 The server acquires a signing party information as the current signing party information according to the signing party coded data, and sends a signing reminder to the corresponding signing party client according to the current signing party information, waiting to receive the signing information.
  • the server acquires a signing party information according to the signing party coding order, and sends a signing reminder to the signing party according to the signing party identity information in the signing party information.
  • the server sends a signing reminder to the signing party whose identity information is zhangsan@ftsafe.
  • Step 718 The server determines whether the signing information is received within the preset time. If yes, step 719 is performed, otherwise the process ends.
  • Step 719 The server determines whether there is any signator information that has not been obtained, and if yes, returns to step 717; otherwise, step 720 is performed.
  • Step 720 The server sends a signing completion reminder to the first client.
  • Figure 8 shows the contract picture displayed after all signatories have signed up.
  • the method of signing the electronic contract specifically includes:
  • Step 801 The second client receives a trigger signal that the signing party starts to sign the contract.
  • Step 802 The second client sends the signatory identity information and the contract identifier to the server.
  • the signing party identity information is specifically a signing party contact mode.
  • Steps 801-802 can be:
  • the server sends the signing information of the signing party contact and the signing reminder to the server.
  • Steps 801-802 can be:
  • Step 901 The second client starts the application system, receives the username and password entered by the signing party, and sends the username and password to the server.
  • the username may be the signing party identity information in the signing party information, that is, one of an email address, a real name, and a mobile phone number;
  • Step 902 The server determines, according to the received username and password, whether the identity of the signing party is legal, and sends the authentication success information to the second client, and performs step 903. Otherwise, the server sends the authentication failure information to the second client, and ends.
  • Step 903 The second client receives the trigger information of the signing party for the unsigned contract, and sends the contract identifier of the unsigned contract to the server, and step 803 is performed.
  • Step 803 The server obtains the corresponding signer information as the current signer information according to the signer identity information, obtains the authentication mode from the current signer information, and determines whether the signer needs to perform identity authentication according to the authentication mode. If yes, step 804 is performed, otherwise, the process is performed. Step 809.
  • the email address sent by the second client to the server is zhangsan@ftsafe.com;
  • the signer information obtained according to the email address is: ⁇ "number”:"1", “email”:"zhangsan@ftsafe.com” , "realname”: “Zhang San”, “authtype”: “1”, “phonesn”: "18201331111” ⁇ , obtain “authtype”: "1” from the signer information;
  • the authentication mode authtype is 1.
  • the server determines that the signing party performs face authentication.
  • the email address sent by the second client to the server is lisi@ftsafe.com
  • the signer information obtained according to the email address is: ⁇ "number”:"2
  • "email”:"lisi@ftsafe.com ","realname”:" ⁇ "
  • authtype "0"
  • phonesn "18201332222” ⁇
  • step 809 is directly performed.
  • Step 804 The server generates second response data according to the authentication mode.
  • the face authentication page link is used as the second response data.
  • Step 805 The server sends the second response data to the second client.
  • Step 806 The second client loads and displays the identity authentication page according to the second response data, and receives identity authentication information input by the signing party.
  • the signing party loads and displays the face authentication page according to the face authentication page link, and receives the face information input by the signing party.
  • Step 807 The second client sends identity authentication information to the server.
  • Step 808 The server determines, according to the identity authentication information, whether the identity of the signing party is legal. If yes, step 809 is performed, otherwise the process ends.
  • the server searches in the database according to the identity authentication information. If the database has the same information as the identity authentication information, the signer identity authentication succeeds, otherwise the signer identity authentication fails and ends.
  • Step 809 The server acquires a corresponding signature attribute according to current signator information.
  • the server acquires the signer identifier according to the current signer information, and obtains the corresponding signature attribute according to the signer identifier and the contract identifier.
  • Step 810 The server sends a signature attribute to the second client.
  • the server further sends a signing party picture generated by the server according to the signing party identity information to the second client.
  • Step 811 The second client displays the contract signing page according to the signature attribute, receives the signed picture input by the signing party, and generates the signing information according to the contract identifier and the signed picture in the signature attribute.
  • the second client displays the contract signing page according to the signature attribute, that is, the contract signing page before Zhang San signed the contract is as shown in FIG. 6 .
  • the second client displays the contract picture and highlights the location based on the signature attribute.
  • the second client receives the signing picture newly set by the signing party or selects to use the signing picture delivered by the server; if the signing party selects to use the previously signed signature picture, the returned data is empty, and if the signing party newly sets the signing information, the returned image
  • the signature data is a newly set signature picture.
  • the signature information in the second embodiment may include a signature, a signature, an identity card number, a date of signature, and a company name.
  • the method further includes: the second client receiving the selection information of whether the signing party signs the contract, and waiting to receive the signer if receiving the confirmation information If the signed signature image is received, the refusal information is returned to the server; the server sets the current contract document to the refusal status, and no longer sends a signature reminder to other signing parties, and ends.
  • Step 812 The second client sends the signing information to the server.
  • the signing information returned by the second client is specifically: ⁇ "signimg":"","contractid":""1" ⁇ , where the signature signimg is empty, indicating that the signing party chooses to use the previously signed signature picture; the contract Identifies the contractid as 1.
  • Step 813 The server receives the signing information, obtains the contract document and the contract picture according to the contract identifier in the signing information, and writes the signature picture to the contract document and the contract picture according to the signature location information in the signature attribute.
  • the signing party since the signing party selects the signed picture delivered by the server, for example, a signature picture or a signature picture, etc.; when the returned signed picture is empty, the signed picture saved by the server by default is written into the contract document.
  • the signature attribute is specifically: "content”:[ ⁇ "docid”:”1",”pageid”:”1”,”signset”:[ ⁇ addresseeid”:”1”,”fieldtype”:"sign ",”top”:”100”,”left”:”70”,”width”:"25”,”height”:”20”],”contractid”:""1” ⁇ , then write the signature picture On the page corresponding to the contract document with contract identifier 1, document identifier 1, and page identifier 1, the specific position of the current page is 100 mm from the top of the page, and the distance from the left end of the page is 70 mm. In the area, the width of the signature picture is 25mm, and the height of the signature picture is 20mm.
  • Figure 7 is a picture of the contract after the completion of the signing of Zhang San
  • Figure 8 is a picture of the contract after the signing of all signatories.
  • Step 814 The server acquires the digital certificate pre-stored in the server according to the signer identifier in the signature attribute, and writes the digital certificate into the contract document.
  • a digital signature is stored in the server, and each signer identifier corresponds to a digital certificate, and the server can obtain a corresponding digital certificate according to the signer information.
  • the contract document format is specifically in the PDF format, and the server signs the document content summary value of the contract document in the PDF format, and writes the signature value and the digital certificate into the contract document.
  • the method further includes:
  • Step S1 The server receives the contract verification information sent by the second client.
  • the contract verification information is that the signing party photographs the contract picture displayed by the second client to obtain the contract verification information and uploads, and the second client sends the contract verification information to the server.
  • Step S2 The server compares the received contract verification information with the contract document to determine whether the content is consistent. If yes, step 811 is performed; otherwise, the sending contract is tamper-evident and ends.
  • the contract picture received by the OCR is compared with the electronic contract uploaded by the founder.
  • OCR Optical Character Recognition
  • OCR is a process of determining the shape of a picture by detecting a dark, bright mode, and then translating the shape into computer text by a character recognition method.
  • the server further includes the resolution of the picture acquired by the server and determines whether the resolution of the picture obtained by the signing party is greater than a preset value. If yes, step S2 is performed; otherwise, the re-shooting contract prompt is sent to the signing party.
  • the server further includes: performing OCR identification on the contract picture, performing character count on the recognized text, and determining whether the number of words in the contract picture is greater than a preset value, and if the number of words in the contract picture is greater than a preset value, Step S2 is performed, otherwise a re-shooting contract prompt is sent to the signing party.
  • step S1 OCR identification is sequentially performed according to the order of reception of the contract pictures, and if the plurality of contract verification information is consistent with the contract content, the signed picture input by the signing party is received, otherwise the process ends.
  • a server that enters into an electronic contract including:
  • the identifier generating module 11 is configured to receive a contract document sent by the first client, convert the contract document into a contract picture, and generate a contract identifier associated with the contract document and the contract picture;
  • the identity generation module specifically includes:
  • a fifth receiving submodule configured to receive a contract document sent by the first client
  • a first conversion submodule configured to convert the contract document received by the fifth receiving submodule into a contract picture according to a preset conversion relationship
  • the identifier generation sub-module is used to generate a contract identifier and a picture identifier; the contract identifier is associated with the contract document and all contract pictures, and each contract picture corresponds to one picture identifier.
  • the signing location information received by the first receiving module specifically includes: a picture identifier of the contract picture where the signing location is located and coordinate information of the signing position.
  • the first sending module 12 is configured to send the contract identifier and the contract picture generated by the identifier generating module 11 to the first client;
  • the first receiving module 13 is configured to receive the contract identifier, the signing location information, and the signing party identity information sent by the first client.
  • the first receiving module 13 specifically includes:
  • a third receiving submodule configured to receive a contract identifier, a signing location information, and a signing party information sent by the first client, and generate a signing party identifier associated with the signing party information
  • the signing party information includes: the signing party identity information and the signing party code, or the signing party identity information and authentication method, or the signing party identity information, the signing party code and the authentication method;
  • a fourth sending submodule configured to send the signer identifier received by the third receiving submodule to the first client
  • the fourth receiving submodule is specifically configured to receive the contract identifier, the signing party identifier, and the signing location information sent by the first client.
  • the second sending module 14 is configured to send the contract identifier, the contract picture and the signing party location information associated with the contract identifier to the second client according to the signer identity information received by the first receiving module 13;
  • the signer identity information received by the first receiving module 13 is specifically a signing party contact mode
  • the second sending module 14 specifically includes:
  • a first sending submodule configured to send a signing reminder including the contract identifier to the second guest according to the signing party contact information received by the first receiving module 13 Account
  • a first receiving submodule configured to receive a contract identifier sent by the second client
  • the second sending submodule is configured to obtain the signing location information and the contract picture according to the contract identifier and the signing party contact information received by the first receiving submodule, and send the contract picture and the signing location information to the second client.
  • the signer identity information received by the first receiving module 13 is specifically a username of the signing party login application system
  • the second sending module 14 specifically includes:
  • a second receiving submodule configured to receive a username and a password sent by the second client
  • a first determining sub-module configured to determine, according to the username and password received by the first receiving module 13, whether the identity of the signing party is legal;
  • a third sending submodule configured to: when the first determining submodule determines that the signing party identity is legal, obtain the signing location information and the contract identifier according to the user name, and send the contract identifier, the contract picture and the signing location information associated with the contract identifier to Second client.
  • signer information received by the third receiving submodule includes: signing party identity information and signing party code, or signing party identity information, signing party code, and authentication mode;
  • the second sending module 14 specifically includes:
  • a second determining submodule configured to determine, according to the signing party code in the signing party information, whether there is a signing order
  • a fifth sending submodule configured to send, by the second determining submodule, the contract identifier to all the second clients according to the signing party identity information in the signing party information when determining that there is no signing sequence;
  • a first obtaining submodule configured to: when the second determining submodule determines that there is a signing order, obtain the signing party information according to the signing party encoding order as the current signing party information; and further, the first determining module determines that the signing party has not been obtained yet Obtaining signer information as current signator information according to the signing party coding order;
  • a sixth sending submodule configured to send the contract identifier, the contract picture, and the signing party location information to the second client according to the signer identity information in the current signer information acquired by the first obtaining submodule;
  • the server further includes: a first determining module, configured to determine whether there are any signator information that has not been obtained.
  • the signer information received by the third receiving submodule includes: the signing party information includes: the signing party identity information and the authentication mode, or the signing party identity information, the signing party code, and the authentication mode;
  • the server also includes:
  • a third sending module configured to obtain an authentication mode from the signer information received by the third receiving submodule, and send an authentication page link to the second client according to the authentication mode;
  • a second determining module configured to receive identity authentication information sent by the second client, and determine, according to the identity authentication information, whether the identity of the signing party is legal;
  • the second sending module 14 is specifically configured to: when the second determining module determines that the signing party is legal, the contract picture and the contract picture and the signing party associated with the contract identifier according to the signer identity information received by the first receiving module 13 The location information is sent to the second client;
  • the fourth sending module is configured to send an identity authentication failure reminder to the second client if the second determining module determines that the signing party identity is invalid.
  • the authentication mode in the signer information received by the third receiving submodule is specifically face identity authentication or real name identity authentication or fingerprint identity authentication or short message identity authentication.
  • the second receiving module 15 is configured to receive a contract identifier sent by the second client, and is further configured to receive a contract identifier and a signature image sent by the second client.
  • the signing module 16 is configured to, if the second receiving module 15 receives the contract identifier, write the signed picture pre-stored in the server to the contract document associated with the contract identifier according to the signing location information, if the second receiving module 15 receives the contract identifier and Signing the picture writes the signed image pre-stored in the server to the contract document.
  • the server further comprises:
  • a storage module configured to store a digital certificate corresponding to the identity information of the signatory
  • the digital certificate writing module is configured to obtain a digital certificate in the storage module according to the identity information of the signing party, and write the digital certificate into the contract document obtained by the signing module.
  • server further includes:
  • a third receiving module configured to receive a contract verification picture sent by the second client
  • a third determining module configured to obtain a contract document according to the contract identifier received by the second receiving module, compare the contract verification image received by the third receiving module with the contract document, and determine whether the content is consistent;
  • the third determining module can include:
  • a fourth determining sub-module configured to determine whether a resolution of the contract verification picture received by the third receiving module is greater than a preset value
  • a fifth determining sub-module configured to determine, by the fifth determining sub-module, that the resolution of the contract verification image received by the third receiving module is greater than a preset value, and comparing the contract verification image received by the third receiving module with the contract document, and determining Whether the content is consistent;
  • the eighth sending submodule is configured to: when the fifth determining submodule determines that the resolution of the contract verification picture received by the third receiving module is not greater than a preset value, sending a contract verification picture unqualified reminder to the second client.
  • the signing module is specifically used by the third judging module to determine that the contract verification picture is consistent with the contract document content according to the signing location information
  • the signed image received by the receiving module is written into the contract document acquired by the third determining module;
  • the third determining module may further include:
  • the sixth determining sub-module is configured to perform optical character recognition on the contract verification picture received by the third receiving module, perform character count on the recognized text, and determine whether the number of words in the contract verification picture is greater than a preset value;
  • a seventh determining sub-module configured to determine, by the sixth determining sub-module, that the number of words in the contract verification picture received by the third receiving module is greater than a preset value, and comparing the contract verification picture received by the third receiving module with the contract document, Determine whether the content is consistent;
  • the ninth sending sub-module is configured to: when the seventh determining sub-module determines that the number of words in the contract verification picture received by the third receiving module is not greater than a preset value, sending a contract verification picture unqualified reminder to the second client
  • the sixth sending module is configured to: when the third determining module determines that the contract verification picture is inconsistent with the content of the contract document, send a contract tampering reminder to the second client.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Security & Cryptography (AREA)
  • Tourism & Hospitality (AREA)
  • General Engineering & Computer Science (AREA)
  • Bioethics (AREA)
  • Software Systems (AREA)
  • Computer Hardware Design (AREA)
  • Human Resources & Organizations (AREA)
  • Strategic Management (AREA)
  • Economics (AREA)
  • Technology Law (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Primary Health Care (AREA)
  • Artificial Intelligence (AREA)
  • Computer Vision & Pattern Recognition (AREA)
  • Audiology, Speech & Language Pathology (AREA)
  • Computational Linguistics (AREA)
  • Multimedia (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种订立电子合同的方法，包括：服务器接收第一客户端发送的合同文档，将所述合同文档转换成合同图片，并生成与所述合同文档和所述合同图片相关联的合同标识，将所述合同标识和所述合同图片发送给所述第一客户端；服务器接收第一客户端发送的合同标识、签署位置信息和签署方身份信息；并根据所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；服务器接收第二客户端发送的所述合同标识和签署图片；并根据所述签署位置信息将签署图片写入与所述合同标识相关联的合同文档。本发明通过签署电子合同，避免了时间地点的限制，方便，快捷，并且减少了资源浪费，实现了所见即所签。

Description

一种订立电子合同的方法及服务器 技术领域
本发明涉及一种订立电子合同的方法及服务器，属于电子商务领域。
背景技术
传统合同一般以当事人签字或者盖章的方式形成，合同的签订受到了时间、地点等的多重限定，并且纸质合同造成了资源浪费。随着电子技术的发展，传统合同正逐渐被电子合同所取代，电子合同是双方或者多方当事人之间通过电子信息网络以电子的形式达成的设立、变更、终止财产性民事权利义务关系的协议。电子合同具有使用方便，传输效率高，不受时间地点的限制等优点。但是，由于互联网的开放性，电子合同在传输过程中必然会存在安全性问题，电子合同在传输过程中容易被截取或篡改，对合同双方的交易安全构成了很大的威胁。
发明内容
本发明的目的是提供一种订立电子合同的方法及服务器，其通过签署电子合同，交易双方签署合同时避免了由于时间地点的限制，提供了方便，快捷的签署方式，并且减少了资源浪费，避免了由于电子合同在传输过程中篡改而造成经济损失的风险，即实现了所见即所签。
为此，本发明的一个方面，提供了一种订立电子合同的方法，具体包括：
步骤A1、第一客户端向服务器发送合同文档；
步骤A2、服务器将合同文档转换成合同图片，并生成与合同文档和合同图片相关联的合同标识，向第一客户端发送合同标识和合同图片；
优选地，步骤A2可以为：服务器将合同文档根据预设转换关系转换成合同图片，生成合同标识、每个合同图片对应生成一个图片标识，合同标识与合同文档和所有合同图片相关联，将合同标识、图片标识和合同图片发送给第一客户端；
步骤A3、第一客户端根据创建方在合同图片上设置的签署位置生成签署位置信息；将合同标识、签署位置信息和创建方输入的签署方身份信息建立对应关系并发送给服务器；
步骤A3具体包括：
步骤301：第一客户端将创建方输入签署方信息发送给服务器；
签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
步骤302、服务器生成与签署方信息相关联的签署方标识；并签署方标识发送给第二客户端；
步骤303、第二客户端接收创建方根据签署方身份信息对应设置的签署位置，根据创建方在合同图片上设置的签署位置生成签署位置信息；将与合同标识相关联的合同标识、签署位置信息和与签署方身份信息相关联的签署方标识建立对应关系并发送给服务器；
优选地，根据创建方在合同图片上设置的签署位置生成签署位置信息具体包括：根据签署位置信息所在合同图片的图片标识和签署位置的坐标信息生成签署位置信息。
优选地，步骤A4、服务器根据签署方身份信息将合同标识、合同图片、签署方位置信息发送给第二客户端；
若签署方身份信息具体为签署方联系方式；
步骤A4具体包括：
步骤101、服务器根据签署方联系方式将包含合同标识的签署提醒发送至第二客户端；
步骤102、第二客户端接收签署方对签署提醒的触发信息，将合同标识发送给服务器；
步骤103、服务器根据合同标识和签署方联系方式获取签署位置信息和合同图片，将合同图片和签署位置信息发送给第二客户端。
优选地，若签署方身份信息具体为签署方登录应用系统的用户名；
步骤A4具体包括：
步骤201、第二客户端启动应用系统，接收签署方输入的用户名和密码，将用户名和密码发送给服务器；
步骤202、服务器根据用户名和密码判定签署方身份合法后，根据用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给第二客户端。
进一步地，若签署方信息包括签署方编码；
步骤A4具体包括：
步骤401：服务器根据签署方信息中的签署方编码判断是否有签署顺序，是则执行步骤403，否则执行步骤402；
步骤402、服务器根据多个签署方信息中的签署方身份信息将合同标识发送给所有第二客户端；
步骤403、服务器根据签署方编码顺序获取签署方信息作为当前签署方信息，根据当前签署方信息中的签署方身 份信息将合同标识、合同图片和签署方位置信息发送给第二客户端；
步骤A6之后还包括：服务器判断是否还有未被获取过的签署方信息，是则返回步骤403，否则结束。
优选地，若签署方信息包括认证方式：
具体地，认证方式可以为：人脸身份认证或实名身份认证或指纹身份认证或短信身份认证。
优选地，步骤A3之后，步骤A4之前还包括：
步骤501、服务器从签署方信息中获取认证方式，根据认证方式向第二客户端发送认证页面链接；
步骤502、第二客户端根据认证页面链接加载并显示身份认证页面，接收签署方输入的身份认证信息，并将身份认证信息发送给服务器；
步骤503、服务器根据身份认证信息判断签署方身份是否合法，是则执行步骤A4，否则向第二客户端发送身份认证失败提醒，结束。
优选地，步骤A5、第二客户端根据签署位置信息在合同图片上显示签署位置，并接收签署方上传的签署图片或服务器下发的签署图片；将合同图片的合同标识发送给服务器，若接收到签署方上传的签署图片则还需将签署图片发送给服务器；
步骤A6、服务器根据合同标识获取合同文档，并根据签署位置信息将签署图片写入合同文档。
优选地，服务器中预存有与签署方身份信息对应的数字证书；
步骤A6之后还包括：服务器根据签署方身份信息获取数字证书，将数字证书写入合同文档。
优选地，步骤A1之后，步骤A2之前还包括：
步骤601、服务器判断合同文档格式是否是预设格式，是则执行步骤A2，否则执行步骤602；
步骤602、服务器判断合同文档格式是否可以转换成预设格式，是则服务器将合同文档转换为预设格式，执行步骤A2，否则向第一客户端发送合同文档格式不支持提醒。
需要说明的是，第一客户端与第二客户端可以为同一个客户端。
根据本发明的另外一个方面，提供了一种订立电子合同的服务器，包括：
标识生成模块，用于接收第一客户端发送的合同文档，将合同文档转换成合同图片，并生成与合同文档和合同图片相关联的合同标识；
标识生成模块具体包括：
第五接收子模块，用于接收第一客户端单发送的合同文档；
第一转换子模块，用于将第五接收子模块接收到的合同文档根据预设转换关系转换成合同图片；
标识生成子模块，用于生成合同标识、图片标识；合同标识与合同文档和所有合同图片相关联，每个合同图片对应一个图片标识。
优选地，第一接收模块接收到的签署位置信息具体包括：签署位置所在合同图片的图片标识和签署位置坐标信息。
第一发送模块，用于将标识生成模块生成的合同标识和合同图片发送给第一客户端；
第一接收模块，用于接收第一客户端发送的合同标识、签署位置信息和签署方身份信息；
第一接收模块，具体包括：
第三接收子模块，用于接收第一客户端发送的合同标识、签署位置信息和签署方信息，并生成与签署方信息相关联的签署方标识；
签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
第四发送子模块，具体用于将第三接收子模块接收到的签署方标识发送给第一客户端；
第四接收子模块，具体用于接收第一客户端发送的合同标识、签署方标识和签署位置信息。
优选地，第二发送模块，用于根据第一接收模块接收到的签署方身份信息将合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；
若第一接收模块13接收到的签署方身份信息具体为签署方联系方式；
第二发送模块，具体包括:
第一发送子模块，用于根据第一接收模块接收到的签署方联系方式将包含合同标识的签署提醒发送至第二客户端；
第一接收子模块，用于接收第二客户端发送的合同标识；
第二发送子模块，用于根据第一接收子模块接收到的合同标识和签署方联系方式获取签署位置信息和合同图片，将合同图片和签署位置信息发送给第二客户端。
优选地，第一接收模块接收到的签署方身份信息具体为签署方登录应用系统的用户名；
第二发送模块，具体包括:
第二接收子模块，用于接收第二客户端发送的用户名和密码；
第一判断子模块，用于根据第一接收模块接收到的用户名和密码判断签署方身份是否合法；
第三发送子模块，用于若第一判断子模块判定签署方身份合法时，根据用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给第二客户端。
优选地，若第三接收子模块接收到的签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息、签署方编码和认证方式；
第二发送模块，具体包括：
第二判断子模块，用于根据签署方信息中的签署方编码判断是否有签署顺序；
第五发送子模块，用于第二判断子模块判定没有签署顺序时根据签署方信息中的签署方身份信息将合同标识发送给所有第二客户端；
第一获取子模块，用于第二判断子模块判定有签署顺序时根据签署方编码顺序获取签署方信息作为当前签署方信息；还用于第一判断模块判定还有未被获取过的签署方信息时根据签署方编码顺序获取签署方信息作为当前签署方信息；
第六发送子模块，用于根据第一获取子模块获取到的当前签署方信息中的签署方身份信息将合同标识、合同图片和签署方位置信息发送给第二客户端；
优选地，服务器还包括：第一判断模块，用于判断是否还有未被获取过的签署方信息。
第三接收子模块接收到的签署方信息包括：签署方信息包括：签署方身份信息和认证方式，或者签署方身份信息、签署方编码和认证方式；
服务器还包括：
第三发送模块，用于从第三接收子模块接收到的签署方信息中获取认证方式，根据认证方式向第二客户端发送认证页面链接；
第二判断模块，用于接收第二客户端发送的身份认证信息，根据身份认证信息判断签署方身份是否合法；
第二发送模块，具体用于若第二判断模块判定签署方身份合法时用于根据第一接收模块接收到的签署方身份信息将合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；
第四发送模块，用于若第二判断模块判定签署方身份不合法时向第二客户端发送身份认证失败提醒。
具体地，第三接收子模块接收到的签署方信息中的认证方式具体为人脸身份认证或实名身份认证或指纹身份认证或短信身份认证。
优选地，第二接收模块，用于接收第二客户端发送的合同标识，还用于接收第二客户端发送的合同标识和签署图片；
签署模块，用于若第二接收模块接收到合同标识则根据签署位置信息将服务器中预存的签署图片写入与合同标识相关联的合同文档，若第二接收模块接收到合同标识和签署图片则将服务器中预存的签署图片写入合同文档。
优选地，服务器还包括：
存储模块，用于存储与签署方身份信息对应的数字证书；
数字证书写入模块，用于根据签署方身份信息在存储模块中获取数字证书，将数字证书写入签署模块获取到的合同文档。
进一步地，服务器还包括：
第三接收模块，用于接收第二客户端发送的合同验证图片；
第三判断模块，用于根据第二接收模块接收到的合同标识获取合同文档，将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第三判断模块可以包括：
第四判断子模块，用于判断第三接收模块接收的合同验证图片的分辨率是否大于预设值；
第五判断子模块，用于第五判断子模块判定第三接收模块接收的合同验证图片的分辨率大于预设值则将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第八发送子模块，用于第五判断子模块判定第三接收模块接收的合同验证图片的分辨率不大于预设值时向第二客户端发送合同验证图片不合格提醒。
相应地，签署模块，具体用于第三判断模块判定合同验证图片与合同文档内容一致时根据签署位置信息将第二接收模块接收到的签署图片写入第三判断模块获取到的合同文档；
第三判断模块还可以包括：
第六判断子模块，用于对第三接收模块接收的合同验证图片进行光学字符识别，将识别得到的文字进行字数统计，判断合同验证图片中的字数是否大于预设值；
第七判断子模块，用于第六判断子模块判定第三接收模块接收的合同验证图片中的字数大于预设值时则将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第九发送子模块，用于第七判断子模块判定第三接收模块接收的合同验证图片中的字数不大于预设值时向第二客户端发送合同验证图片不合格提醒；以及
第六发送模块，用于第三判断模块判定合同验证图片与合同文档内容不一致时向第二客户端发送合同被篡改提醒。
根据本发明，通过签署电子合同，交易双方签署合同时避免了由于时间地点的限制，提供了方便，快捷的签署方式，并且减少了资源浪费，避免了由于电子合同在传输过程中篡改而造成经济损失的风险，即实现了所见即所签。
附图说明
为了更清楚的说明本发明，下面将对附图作简单的介绍，显而易见地，下面描述中的附图仅仅是本发明的一些实施例，对于本领域的技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1为本发明实施例1中提供的一种订立电子合同的方法流程图
图2为本发明实施例2中提供的一种创建电子合同的方法流程图。
图3为本发明实施例2中提供的一种签署电子合同的方法流程图。
图4为本发明实施例2中创建方设置签署位置前的合同图片。
图5为本发明实施例2中创建方设置签署位置后的设置页面。
图6为本发明实施例2中张三签署合同前的合同签署页面。
图7为本发明实施例2中张三签署完成后的合同图片。
图8为本发明实施例2中所有签署方均签署完成后的合同图片。
图9为本发明实施例3中提供的一种订立电子合同的服务器的方框图。
具体实施方式
下面将结合本发明的附图，对本发明的实施例进行清楚、完整地描述。显然所描述的实施例仅仅是本发明一部分实施例，而不是全部的实施例。基于本发明中的实施例，本领域的技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本发明保护的范围。
实施例1：
如图1所示，一种订立电子合同的方法具体包括：
步骤A1、第一客户端向服务器发送合同文档；
步骤A2、服务器将合同文档转换成合同图片，并生成与合同文档和合同图片相关联的合同标识，向第一客户端发送合同标识和合同图片；
优选地，步骤A2可以为：服务器将合同文档根据预设转换关系转换成合同图片，生成合同标识、每个合同图片对应生成一个图片标识，合同标识与合同文档和所有合同图片相关联，将合同标识、图片标识和合同图片发送给第一客户端；
步骤A3、第一客户端根据创建方在合同图片上设置的签署位置生成签署位置信息；将合同标识、签署位置信息和创建方输入的签署方身份信息建立对应关系并发送给服务器；
步骤A3具体包括：
步骤301：第一客户端将创建方输入签署方信息发送给服务器；
签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
步骤302、服务器生成与签署方信息相关联的签署方标识；并签署方标识发送给第二客户端；
步骤303、第二客户端接收创建方根据签署方身份信息对应设置的签署位置，根据创建方在合同图片上设置的签署位置生成签署位置信息；将与合同标识相关联的合同标识、签署位置信息和与签署方身份信息相关联的签署方标识建立对应关系并发送给服务器；
优选地，根据创建方在合同图片上设置的签署位置生成签署位置信息具体包括：根据签署位置信息所在合同图片的图片标识和签署位置的坐标信息生成签署位置信息。
步骤A4、服务器根据签署方身份信息将合同标识、合同图片、签署方位置信息发送给第二客户端；
若签署方身份信息具体为签署方联系方式；
步骤A4具体包括：
步骤101、服务器根据签署方联系方式将包含合同标识的签署提醒发送至第二客户端；
步骤102、第二客户端接收签署方对签署提醒的触发信息，将合同标识发送给服务器；
步骤103、服务器根据合同标识和签署方联系方式获取签署位置信息和合同图片，将合同图片和签署位置信息发送给第二客户端。
若签署方身份信息具体为签署方登录应用系统的用户名；
步骤A4具体包括：
步骤201、第二客户端启动应用系统，接收签署方输入的用户名和密码，将用户名和密码发送给服务器；
步骤202、服务器根据用户名和密码判定签署方身份合法后，根据用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给第二客户端。
进一步地，若签署方信息包括签署方编码；
步骤A4具体包括：
步骤401：服务器根据签署方信息中的签署方编码判断是否有签署顺序，是则执行步骤403，否则执行步骤402；
步骤402、服务器根据多个签署方信息中的签署方身份信息将合同标识发送给所有第二客户端；
步骤403、服务器根据签署方编码顺序获取签署方信息作为当前签署方信息，根据当前签署方信息中的签署方身份信息将合同标识、合同图片和签署方位置信息发送给第二客户端；
步骤A6之后还包括：服务器判断是否还有未被获取过的签署方信息，是则返回步骤403，否则结束。
优选地，若签署方信息包括认证方式：
具体地，认证方式可以为：人脸身份认证或实名身份认证或指纹身份认证或短信身份认证。
步骤A3之后，步骤A4之前还包括：
步骤501、服务器从签署方信息中获取认证方式，根据认证方式向第二客户端发送认证页面链接；
步骤502、第二客户端根据认证页面链接加载并显示身份认证页面，接收签署方输入的身份认证信息，并将身份认证信息发送给服务器；
步骤503、服务器根据身份认证信息判断签署方身份是否合法，是则执行步骤A4，否则向第二客户端发送身份认证失败提醒，结束。
步骤A5、第二客户端根据签署位置信息在合同图片上显示签署位置，并接收签署方上传的签署图片或服务器下发的签署图片；将合同图片的合同标识发送给服务器，若接收到签署方上传的签署图片则还需将签署图片发送给服务器；
步骤A6、服务器根据合同标识获取合同文档，并根据签署位置信息将签署图片写入合同文档。
优选地，服务器中预存有与签署方身份信息对应的数字证书；
步骤A6之后还包括：服务器根据签署方身份信息获取数字证书，将数字证书写入合同文档。
优选地，步骤A1之后，步骤A2之前还包括：
步骤601、服务器判断合同文档格式是否是预设格式，是则执行步骤A2，否则执行步骤602；
步骤602、服务器判断合同文档格式是否可以转换成预设格式，是则服务器将合同文档转换为预设格式，执行步骤A2，否则向第一客户端发送合同文档格式不支持提醒。
需要说明的是，第一客户端与第二客户端可以为同一个客户端。
实施例2：
如图2所示，一种创建电子合同的方法具体包括：
步骤701、第一客户端启动应用系统，接收创建方输入的登录请求信息。
本实施例2中，登录请求信息包括用户名和密码。
步骤702、第一客户端向服务器发送登录请求信息。
例如，客户端发送给服务器的登录请求信息具体为{"username","zhangsan@ftsafe.com","passwd":"123456"}，用户名username为zhangsan@ftsafe.com，密码passwd为123456。
步骤703、服务器根据接收到的登录请求信息判断创建方身份是否合法，是则执行步骤705，否则执行步骤704结束。
服务器根据获取的创建方名zhangsan@ftsafe.com和密码123456在数据库中进行检索，如果数据库中有相同的信息则创建方身份验证成功，否则创建方身份验证失败，结束。
步骤704、服务器向第一客户端发送认证失败信息，结束。
步骤705、服务器向第一客户端发送认证成功信息。
步骤706、第一客户端接收创建方上传的合同文档、创建方设置的签署方编码、签署方身份信息和认证方式，根据签署方编码、签署方身份信息和认证方式生成签署方信息。
步骤706还可以为：客户端接收创建方选择的预先保存的未签署合同文档、创建方设置的签署方编码、签署方身份信息和认证方式，根据签署方编码、签署方身份信息和认证方式生成签署方信息。
具体地，签署方编码，用于标志签署方的签署顺序。
签署方身份信息，具体包括邮箱地址、真实姓名和手机号码。
认证方式，具体包括短信、人脸、指纹以及实名等多种认证方式的任意一个或组合。
创建方可设定一个签署方也可设定多个签署方，本实施例2中有两个签署方，第一客户端生成两条签署方信息具体为：[{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"1","phonesn": "18201331111"},{"number":"2","email":"lisi@ftsafe.com","realname":"李四","authtype":"0","phonesn":"18201332222"}]。
张三的签署方信息具体如下：{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"1","phonesn":"18201331111"}
其中，签名编码number用于标识签署方的签署顺序，签名编码number为1，表示当前签署方为第一个签署合同；邮箱地址email为test@ftsafe.com；真实姓名realname为张三；认证方式authtype，用于标识签署方的认证方式，本实施例2中提供短信、人脸、指纹以及实名等多种签署方身份认证方式，当认证方式authtype为0时标志不需要进行签署方身份认证；当认证方式authtype为1时标志通过短信进行签署方身份认证；当认证方式authtype为2时标志通过人脸进行签署方身份认证，当认证方式authtype为3时标志通过实名进行签署方身份认证。手机号码phonesn为18201331111。
本实施例2中的合同文档具体为：
租房合同
出租方：(以下简称甲方)
承租方：(以下简称乙方)
甲、乙双方就房屋租赁事宜，达成如下协议：
一、甲方将位于北京市学院路街道花园小区9号楼201号的房屋出租给乙方居住使用，租赁期限自2016年1月1日至2016年12月31日，计12个月。
二、本房屋月租金为人民币2000元，按月/季度/年结算。
三、乙方租赁期间，水费、电费、取暖费、燃气费、电话费、物业费以及其它由乙方居住而产生的费用由乙方负担。租赁结束时，乙方须交清欠费。
四、乙方同意预交2000元作为保证金，合同终止时，当作房租冲抵。
五、房屋租赁期为，从2016年1月1日至2016年12月31日。在此期间，任何一方要求终止合同，须提前三个月通知对方，并偿付对方总租金2000的违约金；如果甲方转让该房屋，乙方有优先购买权。
甲方：_____________     乙方：_____________
步骤707、第一客户端将合同文档和签署方信息发送给服务器。
步骤708、服务器接收并保存第一客户端发送的合同文档和签署方信息，将合同文档转换成合同图片，并生成标识信息；根据签署方信息生成签署方标识，根据签署方标识和标识信息生成第一响应数据。
本实施中，标识信息包括合同标识，文档标识，页码标识和图片标识。
一个合同唯一对应一个合同标识；每个合同可以包含一个合同文档也可以包含多个合同文档，每个合同文档唯一对应一个文档标识；合同文档的每一页都对应一个页码标识。
服务器将合同文档按页转换成合同图片，每个合同图片唯一对应一个图片标识。
例如，本实施例2中，服务器根据接收到的合同文档生成的标识信息具体为：合同标识为1，文档标识为1，页码标识为1，图片标识为1。标识信息均为服务器生成的唯一自增的序列号。
服务器中根据签署方信息：{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"1","phonesn":"18201331111"}生成签署方标识为1；根据签署方信息：{"number":"2","email":"lisi@ftsafe.com","realname":"李四","authtype":"0","phonesn":"18201332222"}生成签署方标识为2。
第一响应数据具体如下：
{"contractinfo":{"contractid":"1"},"addressees":[{"addresseeid":"1","realname":"张三","email":"zhangsan@ftsafe.com"},{"addresseeid":"2","realname":"李四","email":"lisi@ftsafe.com"}]"docinfo":[{"docid":"1","pageid":"1","pagewidth":"500","pageheight":"400","imgid":"1"}]}；
其中，合同信息contractinfo包括：合同唯一标识contractid为1。签署方信息addressees包括：签署方标识addresseeid为1；真实姓名realname为张三；邮箱地址email为zhangsan@ftsafe.com。文档信息docinfo包括：文档标识docid为1；页面标识pageid为1；页面宽度pagewidth为500；页面高度pageheight为400；图片标识imgid为1。
步骤708还包括：服务器接收第一客户端发送的合同文档，并通过获取合同文档的文件名后缀判断合同文档格式是否是预设格式或可以转换为预设格式，若不是预设格式且不可以转换为预设格式则提示不支持当前格式；若接收到的合同文档格式为预设格式则保存当前合同文档并将合同文档转换为合同图片；若接收到的合同文档格式不是预设格式且可以转换成预设格式，则将合同文档转换为预设格式，并保存转换后的合同文档并将转换后的合同文档转换为合同图片。
本实施例2中预设格式为PDF格式，可以转换为PDF格式的格式有TXT、XLS、PPT、DOC等格式。
本实施例2中，服务器获取接收到的合同文档的后缀判断合同文档格式是否为PDF格式或可以转换为PDF格式，若接收到的合同文档格式不是PDF格式且不可以转换为PDF格式则提示不支持当前格式；若接收到的合同文档格式为PDF格式则保存当前合同文档，并调用pdfToImg方法将合同文档转换为合同图片；若接收到合同文档格式不是PDF格式且是TXT、XLS、PPT、DOC格式的任意一种则调用Msoffice接口将合同文档转换为PDF格式的合同文档，保存PDF格式的合同文档，并调用pdfToImg方法将PDF格式的合同文档转换为合同图片。转换成合同图片可以防止对合同文档的二次修改。
例如：当前合同文档的格式为DOC格式，服务器调用Msoffice接口将合同文档转换为PDF格式的合同文档，保存PDF格式的合同文档，并调用pdfToImg方法将PDF格式的合同文档转换为合同图片。
步骤709、服务器向第一客户端返回第一响应数据。
步骤710、第一客户端根据第一响应数据加载并显示合同图片，接收创建方根据不同的签署方信息对应设置的签名类型和签名位置信息，并根据标识信息、签署方标识、签名位置信息和签名类型生成签名属性。
本实施例2中，第一客户端根据第一响应数据加载并显示合同图片，即创建方设置签署位置前的合同图片，如图4所示。
本实施例2中，创建方可以选择的签名类型包括签名、签章、日期、公司名称等。签名位置信息具体包括：签名图片相对于页面顶端的距离、签名图片相对于页面左端的距离、签名图片宽度、签名图片高度以及签名图片所处的文档，页数等信息。
图5为创建方设置签署位置后的设置页面。例如，张三的签名位置设置为图5中乙方的签署方框所示的位置，李四的签署位置为图5所示的甲方的签署方框所示的位置。相应地，第一客户端根据合同标识、签署方标识、签名类型和签名位置信息生成签名属性具体为：
{"content":[{"docid":"1","pageid":"1","signset":[{addresseeid":"1","fieldtype":"sign","top":"100","left":"70","width":"25","height":"20"},{addresseeid":"2","fieldtype":"seal","top":"100","left":"30","width":"25","height":"20"}]}],"contractid":""1"}。
其中签名属性包括：签名图片所处的文档标识docid为1；签名图片所处的页码标识为1；签署人标识userid为张三；签名图片相对于页面顶端的距离top为100mm；签名图片相对于页面左端的距离left为30mm；签名图片宽度width为25mm；签名图片高度height为20mm；签署类型fieldtype为sign，表明签署类型为签名；签名图片所处的合同标识contractid为1。
步骤711、第一客户端将签名属性发送给服务器。
步骤712、服务器保存签名属性。
步骤713、服务器根据签署方编码判断是否有签署顺序，是则执行步骤717，否则执行步骤714。
具体地，服务器从任意一个签署方信息中获取签署方编码，判断签署方编码是否为0，是则没有签署顺序，否则有签署顺序；
例如，服务器从签署方信息中获取"number":"1"；签署方编码"number"所对应的值为1则表明有签署顺序。
步骤714、服务器根据签署方信息向所有签署方发送签署提醒，等待接收签署信息。
具体地，服务器从签署方信息中获取邮箱地址，通过邮箱地址向签署方发送签署提醒。还可以从签署方信息中获取手机号码，通过短信方式给签署方发送签署提醒。
步骤715、服务器判断是否在预设时间内接收到所有签署方返回的签署信息，是则执行步骤716，否则结束。
步骤716、服务器向第一客户端发送签署完成提醒。
步骤717、服务器根据签署方编码数据顺序获取一个签署方信息作为当前签署方信息，根据当前签署方信息给相应地签署方客户端发送签署提醒，等待接收签署信息。
具体地，服务器根据签署方编码顺序获取一个签署方信息，根据签署方信息中的签署方身份信息给签署方发送签署提醒。
例如，获取到的当前签署方信息为{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"0","phonesn":"18201331111"}，则服务器给签署方身份信息为zhangsan@ftsafe的签署方发送签署提醒。
步骤718、服务器判断是否在预设时间内接收到签署信息，是则执行步骤719，否则结束。
步骤719、服务器判断是否还有未被获取过的签署方信息，是则返回步骤717，否则执行步骤720。
步骤720、服务器向第一客户端发送签署完成提醒。
如图8所示为所有签署方均签署完成后显示的合同图片。
如图3所示，若当前签署方为张三，签署电子合同的方法具体包括：
步骤801、第二客户端接收签署方开始签署合同的触发信号。
步骤802、第二客户端向服务器发送签署方身份信息和合同标识。
本实施例2中，签署方身份信息具体为签署方联系方式。
步骤801-802可以为：
若第二客户端接收到签署方对签署提醒的触发信息，则向服务器发送签署方联系方式和签署提醒中的合同标识。
步骤801-802可以为：
步骤901、第二客户端启动应用系统，接收签署方输入的用户名和密码，将用户名和密码发送给服务器；
具体地，用户名可以为签署方信息中的签署方身份信息，即邮箱地址、真实姓名、手机号码之一；
步骤902、服务器根据接收到的用户名和密码判断签署方身份是否合法，向第二客户端发送认证成功信息，执行步骤903，否则向第二客户端发送认证失败信息，结束；
步骤903、第二客户端接收到签署方对未签署合同的触发信息，将未签署合同的合同标识发送给服务器，执行步骤803。
步骤803、服务器根据签署方身份信息获取相应地签署方信息作为当前签署方信息，从当前签署方信息获取认证方式，根据认证方式判断签署方是否需要进行身份认证，是则执行步骤804，否则执行步骤809。
例如，第二客户端向服务器发送的邮箱地址为zhangsan@ftsafe.com；根据邮箱地址获取到的签署方信息为：{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"1","phonesn":"18201331111"}，从签署方信息中获取"authtype":"1"；认证方式authtype为1。服务器判定签署方进行人脸认证。
又如，第二客户端向服务器发送的邮箱地址为lisi@ftsafe.com,根据邮箱地址获取到的签署方信息为：{"number":"2","email":"lisi@ftsafe.com","realname":"李四","authtype":"0","phonesn":"18201332222"}],从签署方信息中获取"authtype":"0"；认证方式authtype为0，服务器判定不需要进行身份认证，则直接步骤809。
步骤804、服务器根据认证方式生成第二响应数据。
若服务器判定签署方需要进行人脸认证则将人脸认证页面链接作为第二响应数据。
步骤805、服务器向第二客户端发送第二响应数据。
步骤806、第二客户端根据第二响应数据加载并显示身份认证页面，并接收签署方输入的身份认证信息。
例如：签署方根据人脸认证页面链接加载并显示人脸认证页面，并接收签署方输入的人脸信息。
步骤807、第二客户端向服务器发送身份认证信息。
步骤808、服务器根据身份认证信息判断签署方身份是否合法，是则执行步骤809，否则结束。
服务器在数据库中根据身份认证信息进行检索，如果数据库中有与身份认证信息相同的信息则签署方身份认证成功，否则签署方身份认证失败，结束。
步骤809、服务器根据当前签署方信息获取对应的签名属性
具体地，服务器根据当前签署方信息获取签署方标识，根据签署方标识和合同标识获取对应的签名属性。
若当前签署方信息具体为{"number":"1","email":"zhangsan@ftsafe.com","realname":"张三","authtype":"1","phonesn":"18201331111"}]，根据当前签署方信息获取到的签署方标识为1，获取签署方标识为1的签名属性具体为：{"content":[{"docid":"1","pageid":"1","signset":[{addresseeid":"1","fieldtype":"sign","top":"100","left":"70","width":"25","height":"20"],"contractid":""1"}
步骤810、服务器向第二客户端发送签名属性。
优选地，步骤801中还包括：服务器向第二客户端下发服务器根据签署方身份信息生成的签署方图片。
步骤811、第二客户端根据签名属性显示合同签署页面，接收签署方输入的签署图片，根据签名属性中的合同标识和签署图片生成签署信息。
若当前签署方为张三，第二客户端根据签名属性显示合同签署页面，即张三签署合同前的合同签署页面如图6所示。第二客户端显示合同图片，并根据签名属性高亮签署位置。第二客户端接收签署方新设置签署图片或者选择使用服务器下发的签署图片；若签署方选择使用之前已设置的的签名图片则返回的数据为空，若签署方新设置签署信息则返回的签署数据为新设置的签名图片，本实施例2中签署信息可以包括签名、签章、身份证号码、签署日期和公司名称。
优选地，第二客户端根据签名属性显示签署页面之后，接收签署方输入的签名数据之前还包括：第二客户端接收签署方是否签署合同的选择信息，若接收到确认信息则等待接收签署人输入的签署图片，若接收签署方的拒签信息则将拒签信息返回服务器；服务器设置当前合同文档为拒签状态，不再向其他签署方发送签署提醒，结束。
步骤812、第二客户端向服务器发送签署信息。
例如，第二客户端返回的签署信息具体为：{"signimg":"","contractid":""1"}，其中签名signimg为空，表明签署方选择使用之前已设置的签名图片；合同标识contractid为1。
步骤813、服务器接收签署信息，根据签署信息中的合同标识获取合同文档和合同图片，根据签名属性中的签名位置信息将签名图片写入到合同文档和合同图片。
本实施例2中，由于签署方选择了服务器下发的签署图片，例如签名图片或签章图片等；则返回的签署图片为空时，服务器默认保存的签署图片写入合同文档。
例如，签名属性具体为具体为："content":[{"docid":"1","pageid":"1","signset":[{addresseeid":"1","fieldtype":"sign","top":"100","left":"70","width":"25","height":"20"],"contractid":""1"}，则将签名图片写入合同标识contractid为1、文档标识为1、页面标识为1的合同文档对应的页面上，在当前页面的具体位置是距离相对于页面顶端的距离为100mm，相对于页面左端的距离为70mm的区域内，且签名图片的宽度为25mm，签名图片的高度为20mm。图7为张三签署完成后的合同图片，图8为所有签署方均签署完成后的合同图片。
步骤814、服务器根据签名属性中的签署方标识获取服务器中预存的数字证书，将数字证书写入合同文档。
服务器中保存有数字签名，每个签署方标识对应一个数字证书，服务器可以根据签署方信息获取对应的数字证书。本实施例2中合同文档格式具体为PDF格式，服务器针对PDF格式的合同文档正文内容摘要值进行签名，并将签名值和数字证书写入合同文档。
优选地，步骤811中第二客户端根据签名属性显示合同签署页面之后，接收签署方输入的签署图片之前还包括：
步骤S1、服务器接收第二客户端发送的合同验证信息。
合同验证信息为签署方对第二客户端显示的合同图片进行拍照得到合同验证信息并上传，第二客户端向服务器发送合同验证信息。
步骤S2、服务器将接收到的合同验证信息与合同文档进行比对，判断内容是否一致，是则执行步骤811，否则发送合同被篡改提醒，结束。
本实施例2通过OCR将收到的合同图片与创建方上传的电子合同进行比对。OCR(光学字符识别，Optical Character Recognition)是将图片内容通过检测暗、亮的模式确定其形状，然后用字符识别方法将形状翻译成计算机文字的过程。
进一步地，步骤S2之前还包括服务器获取图片的分辨率并判断签署方拍照得到的图片的分辨率是否大于预设值，是则执行步骤S2，否则向签署方发送重新拍摄合同提示。
进一步地，步骤S2之前还包括，服务器对合同图片进行OCR识别，将识别得到的文字进行字数统计，判断合同图片中的字数是否大于预设值，若合同图片中的字数大于预设值，则执行步骤S2，否则向签署方发送重新拍摄合同提示。
进一步地，若步骤S1中接收到多个合同验证信息，则根据合同图片的接收顺序依次进行OCR识别，若多个合同验证信息与合同内容一致，则接收签署方输入的签署图片，否则结束。
实施例3：
一种订立电子合同的服务器，包括：
标识生成模块11，用于接收第一客户端发送的合同文档，将合同文档转换成合同图片，并生成与合同文档和合同图片相关联的合同标识；
标识生成模块具体包括：
第五接收子模块，用于接收第一客户端单发送的合同文档；
第一转换子模块，用于将第五接收子模块接收到的合同文档根据预设转换关系转换成合同图片；
标识生成子模块，用于生成合同标识、图片标识；合同标识与合同文档和所有合同图片相关联，每个合同图片对应一个图片标识。
第一接收模块接收到的签署位置信息具体包括：签署位置所在合同图片的图片标识和签署位置坐标信息。
第一发送模块12，用于将标识生成模块11生成的合同标识和合同图片发送给第一客户端；
第一接收模块13，用于接收第一客户端发送的合同标识、签署位置信息和签署方身份信息；
第一接收模块13，具体包括：
第三接收子模块，用于接收第一客户端发送的合同标识、签署位置信息和签署方信息，并生成与签署方信息相关联的签署方标识；
签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
第四发送子模块，具体用于将第三接收子模块接收到的签署方标识发送给第一客户端；
第四接收子模块，具体用于接收第一客户端发送的合同标识、签署方标识和签署位置信息。
第二发送模块14，用于根据第一接收模块13接收到的签署方身份信息将合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；
若第一接收模块13接收到的签署方身份信息具体为签署方联系方式；
第二发送模块14，具体包括:
第一发送子模块，用于根据第一接收模块13接收到的签署方联系方式将包含合同标识的签署提醒发送至第二客 户端；
第一接收子模块，用于接收第二客户端发送的合同标识；
第二发送子模块，用于根据第一接收子模块接收到的合同标识和签署方联系方式获取签署位置信息和合同图片，将合同图片和签署位置信息发送给第二客户端。
第一接收模块13接收到的签署方身份信息具体为签署方登录应用系统的用户名；
第二发送模块14，具体包括:
第二接收子模块，用于接收第二客户端发送的用户名和密码；
第一判断子模块，用于根据第一接收模块13接收到的用户名和密码判断签署方身份是否合法；
第三发送子模块，用于若第一判断子模块判定签署方身份合法时，根据用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给第二客户端。
若第三接收子模块接收到的签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息、签署方编码和认证方式；
第二发送模块14，具体包括：
第二判断子模块，用于根据签署方信息中的签署方编码判断是否有签署顺序；
第五发送子模块，用于第二判断子模块判定没有签署顺序时根据签署方信息中的签署方身份信息将合同标识发送给所有第二客户端；
第一获取子模块，用于第二判断子模块判定有签署顺序时根据签署方编码顺序获取签署方信息作为当前签署方信息；还用于第一判断模块判定还有未被获取过的签署方信息时根据签署方编码顺序获取签署方信息作为当前签署方信息；
第六发送子模块，用于根据第一获取子模块获取到的当前签署方信息中的签署方身份信息将合同标识、合同图片和签署方位置信息发送给第二客户端；
服务器还包括：第一判断模块，用于判断是否还有未被获取过的签署方信息。
第三接收子模块接收到的签署方信息包括：签署方信息包括：签署方身份信息和认证方式，或者签署方身份信息、签署方编码和认证方式；
服务器还包括：
第三发送模块，用于从第三接收子模块接收到的签署方信息中获取认证方式，根据认证方式向第二客户端发送认证页面链接；
第二判断模块，用于接收第二客户端发送的身份认证信息，根据身份认证信息判断签署方身份是否合法；
第二发送模块14，具体用于若第二判断模块判定签署方身份合法时用于根据第一接收模块13接收到的签署方身份信息将合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；
第四发送模块，用于若第二判断模块判定签署方身份不合法时向第二客户端发送身份认证失败提醒。
具体地，第三接收子模块接收到的签署方信息中的认证方式具体为人脸身份认证或实名身份认证或指纹身份认证或短信身份认证。
第二接收模块15，用于接收第二客户端发送的合同标识，还用于接收第二客户端发送的合同标识和签署图片；
签署模块16，用于若第二接收模块15接收到合同标识则根据签署位置信息将服务器中预存的签署图片写入与合同标识相关联的合同文档，若第二接收模块15接收到合同标识和签署图片则将服务器中预存的签署图片写入合同文档。
优选地，服务器还包括：
存储模块，用于存储与签署方身份信息对应的数字证书；
数字证书写入模块，用于根据签署方身份信息在存储模块中获取数字证书，将数字证书写入签署模块获取到的合同文档。
进一步地，服务器还包括：
第三接收模块，用于接收第二客户端发送的合同验证图片；
第三判断模块，用于根据第二接收模块接收到的合同标识获取合同文档，将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第三判断模块可以包括：
第四判断子模块，用于判断第三接收模块接收的合同验证图片的分辨率是否大于预设值；
第五判断子模块，用于第五判断子模块判定第三接收模块接收的合同验证图片的分辨率大于预设值则将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第八发送子模块，用于第五判断子模块判定第三接收模块接收的合同验证图片的分辨率不大于预设值时向第二客户端发送合同验证图片不合格提醒。
相应地，签署模块，具体用于第三判断模块判定合同验证图片与合同文档内容一致时根据签署位置信息将第二接 收模块接收到的签署图片写入第三判断模块获取到的合同文档；
第三判断模块还可以包括：
第六判断子模块，用于对第三接收模块接收的合同验证图片进行光学字符识别，将识别得到的文字进行字数统计，判断合同验证图片中的字数是否大于预设值；
第七判断子模块，用于第六判断子模块判定第三接收模块接收的合同验证图片中的字数大于预设值时则将第三接收模块接收到的合同验证图片与合同文档进行比对，判断内容是否一致；
第九发送子模块，用于第七判断子模块判定第三接收模块接收的合同验证图片中的字数不大于预设值时向第二客户端发送合同验证图片不合格提醒
第六发送模块，用于第三判断模块判定合同验证图片与合同文档内容不一致时向第二客户端发送合同被篡改提醒。
以上所述的实施例只是本发明较优选地具体实施方式，本领域的技术人员在本发明技术方案范围内进行的通常变化和替换都应包含在本发明的保护范围内。

Claims (22)

  1. 一种订立电子合同的方法，其特征在于，包括：
    步骤B1、服务器接收第一客户端发送的合同文档，将所述合同文档转换成合同图片，并生成与所述合同文档和所述合同图片相关联的合同标识，将所述合同标识和所述合同图片发送给所述第一客户端；
    步骤B2、服务器接收第一客户端发送的合同标识、签署位置信息和签署方身份信息，根据所述签署方身份信息将所述合同标识、合同图片、签署方位置信息发送给第二客户端；以及
    步骤B3、服务器接收第二客户端发送的所述合同标识；若服务器还接收到第二客户端发送的签署图片则根据所述签署位置信息将签署图片写入与所述合同标识相关联的合同文档，若没有接收到第二客户端发送的签署图片则将服务器中预存的签署图片写入合同文档。
  2. 如权利要求1所述的方法，其特征在于，
    所述步骤B2中服务器接收到的所述签署方身份信息具体为签署方联系方式；
    所述根据所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端具体包括：
    步骤801、所述服务器根据签署方联系方式将包含合同标识的签署提醒发送至所述第二客户端；以及
    步骤802、服务器接收第二客户端发送的合同标识，并根据所述合同标识和所述签署方联系方式获取签署位置信息和合同图片，将合同图片和签署位置信息发送给所述第二客户端。
  3. 如权利要求1所述的方法，其特征在于，
    所述步骤B2中服务器接收到的所述签署方身份信息具体为签署方登录应用系统的用户名；
    所述根据所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端具体包括：服务器接收第二客户端发送的用户名和密码，根据用户名和密码判定签署方身份合法后，根据所述用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给所述第二客户端。
  4. 如权利要求1所述的方法，其特征在于，所述步骤B2具体包括：
    步骤901、服务器接收第一客户端发送的合同标识、签署位置信息和签署方身份信息；并生成与所述签署方信息相关联的签署方标识，将签署方标识发送给第一客户端；以及
    所述签署方信息包括签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
    步骤902、服务器接收第一客户端发送的合同标识、签署方标识和签署位置信息。
  5. 如权利要求4所述的方法，其特征在于，
    所述签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息、签署方编码和认证方式；
    所述根据所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端具体包括：
    步骤A01：服务器根据签署方信息中的签署方编码判断是否有签署顺序，是则执行步骤A03，否则执行步骤A02；
    步骤A02、所述服务器根据所述多个签署方信息中的签署方身份信息将所述合同标识发送给所有第二客户端；
    步骤A03、所述服务器根据所述签署方编码顺序获取签署方信息作为当前签署方信息，根据当前签署方信息中的签署方身份信息将所述合同标识、合同图片和签署方位置信息发送给第二客户端；以及
    所述步骤B3之后还包括：所述服务器判断是否还有未被获取过的签署方信息，是则返回步骤A03，否则结束。
  6. 如权利要求4所述的方法，其特征在于，
    所述签署方信息包括：签署方身份信息和认证方式，或者签署方身份信息、签署方编码和认证方式；
    所述步骤B2之后，步骤B3之前还包括：
    步骤B01、所述服务器从签署方信息中获取认证方式，根据所述认证方式向第二客户端发送认证页面链接；
    步骤B02、所述服务器接收第二客户端发送的身份认证信息，根据所述身份认证信息判断签署方身份是否合法，是则执行步骤B3，否则向所述第二客户端发送身份认证失败提醒，结束。
  7. 如权利要求1所述的方法，其特征在于，所述步骤B1具体为：所述服务器将所述合同文档根据预设转换关系转换成合同图片，生成合同标识、每个合同图片对应生成一个图片标识，所述合同标识与所述合同文档和所有合同图片相关联，将所述合同标识、所述图片标识和所述合同图片发送给所述第一客户端；以及
    所述服务器接收到的签署方位置信息具体包括：所述签署位置所在合同图片的图片标识和签署位置的坐标信息。
  8. 如权利要求1所述的方法，其特征在于，包括：
    所述服务器中预存有与所述签署方身份信息对应的数字证书；以及
    所述步骤B3之后还包括：所述服务器根据所述签署方身份信息获取所述数字证书，将所述数字证书写入所述合同文档。
  9. 如权利要求1所述的方法，其特征在于，所述B2之后，所述步骤B3之前还包括：
    步骤D01、服务器接收第二客户端发送的合同验证图片；以及
    步骤D02、服务器根据合同标识获取合同文档，将所述合同验证图片与所述合同文档进行比对，判断内容是否一致，是则执行步骤B3，否则向第二客户端发送合同被篡改提醒，结束。
  10. 如权利要求9所述的方法，其特征在于，所述步骤D01之后，步骤D02之前还包括：服务器判断所述合同验证图片的分辨率是否大于预设值，是则执行步骤D02，否则向第二客户端发送合同验证图片不合格提醒。
  11. 如权利要求9所述的方法，其特征在于，所述步骤D01之后，步骤D02之前还包括：对所述合同验证图片进行光学字符识别，将识别得到的文字进行字数统计，判断合同验证图片中的字数是否大于预设值，是则执行步骤D02，否则向第二客户端发送合同验证图片不合格提醒。
  12. 一种订立电子合同的服务器，其特征在于，包括：
    标识生成模块，用于接收第一客户端发送的合同文档，将所述合同文档转换成合同图片，并生成与所述合同文档和所述合同图片相关联的合同标识；
    第一发送模块，用于将标识生成模块生成的所述合同标识和所述合同图片发送给所述第一客户端；
    第一接收模块，用于接收所述第一客户端发送的合同标识、签署位置信息和签署方身份信息；
    第二发送模块，用于根据所述第一接收模块接收到的所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；
    第二接收模块，用于接收所述第二客户端发送的所述合同标识，还用于接收所述第二客户端发送的所述合同标识和签署图片；以及
    签署模块，用于若所述第二接收模块接收到所述合同标识则根据所述签署位置信息将服务器中预存的签署图片写入与所述合同标识相关联的合同文档，若所述第二接收模块接收到所述合同标识和签署图片则将服务器中预存的签署图片写入合同文档。
  13. 如权利要求12所述的服务器，其特征在于，
    所述第一接收模块接收到的所述签署方身份信息具体为签署方联系方式；
    所述第二发送模块，具体包括:
    第一发送子模块，用于根据所述第一接收模块接收到的签署方联系方式将包含合同标识的签署提醒发送至所述第二客户端；
    第一接收子模块，用于接收所述第二客户端发送的合同标识；
    第二发送子模块，用于根据所述第一接收子模块接收到的合同标识和所述签署方联系方式获取签署位置信息和合同图片，将所述合同图片和所述签署位置信息发送给所述第二客户端。
  14. 如权利要求12所述的服务器，其特征在于，
    所述第一接收模块接收到的所述签署方身份信息具体为签署方登录应用系统的用户名；
    所述第二发送模块，具体包括:
    第二接收子模块，用于接收第二客户端发送的用户名和密码；
    第一判断子模块，用于根据所述第一接收模块接收到的所述用户名和密码判断签署方身份是否合法；
    第三发送子模块，用于当所述第一判断子模块判定所述签署方身份合法时，根据所述用户名获取签署位置信息和合同标识，将合同标识、与合同标识相关联的合同图片和签署位置信息发送给所述第二客户端。
  15. 如权利要求12所述的服务器，其特征在于，
    所述第一接收模块，具体包括：
    第三接收子模块，用于接收第一客户端发送的合同标识、签署位置信息和签署方信息，并生成与所述签署方信息相关联的签署方标识；
    所述签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息和认证方式，或签署方身份信息、签署方编码和认证方式；
    第四发送子模块，具体用于将所述第三接收子模块接收到的所述签署方标识发送给第一客户端；
    第四接收子模块，具体用于接收第一客户端发送的合同标识、签署方标识和签署位置信息。
  16. 如权利要求15所述的服务器，其特征在于，
    所述第三接收子模块接收到的所述签署方信息包括：签署方身份信息和签署方编码，或签署方身份信息、签署方编码和认证方式；
    所述第二发送模块，具体包括：
    第二判断子模块，用于根据签署方信息中的签署方编码判断是否有签署顺序；
    第五发送子模块，用于所述第二判断子模块判定没有签署顺序时根据所述签署方信息中的签署方身份信息将所述合同标识发送给所有第二客户端；
    第一获取子模块，用于所述第二判断子模块判定有签署顺序时根据所述签署方编码顺序获取签署方信息作为当前签署方信息；还用于第一判断模块判定还有未被获取过的签署方信息时根据所述签署方编码顺序获取签署方信息作为 当前签署方信息；
    第六发送子模块，用于根据第一获取子模块获取到的所述当前签署方信息中的签署方身份信息将所述合同标识、合同图片和签署方位置信息发送给第二客户端；以及
    所述服务器还包括：第一判断模块，用于判断是否还有未被获取过的签署方信息。
  17. 如权利要求15所述的服务器，其特征在于，
    所述第三接收子模块接收到的所述签署方信息包括：所述签署方信息包括：签署方身份信息和认证方式，或者签署方身份信息、签署方编码和认证方式；
    所述服务器还包括：
    第三发送模块，用于从所述第三接收子模块接收到的签署方信息中获取认证方式，根据所述认证方式向第二客户端发送认证页面链接；
    第二判断模块，用于接收第二客户端发送的身份认证信息，根据所述身份认证信息判断签署方身份是否合法；
    所述第二发送模块，具体用于若所述第二判断模块判定签署方身份合法时用于根据所述第一接收模块接收到的所述签署方身份信息将所述合同标识、与合同标识相关联的合同图片和签署方位置信息发送给第二客户端；以及
    第四发送模块，用于若所述第二判断模块判定签署方身份不合法时向第二客户端发送身份认证失败提醒。
  18. 如权利要求12所述的服务器，其特征在于，所述标识生成模块具体包括：
    第五接收子模块，用于接收第一客户端单发送的合同文档；
    第一转换子模块，用于将所述第五接收子模块接收到的所述合同文档根据预设转换关系转换成合同图片；
    标识生成子模块，用于生成合同标识、图片标识；所述合同标识与所述合同文档和所有合同图片相关联，每个合同图片对应一个图片标识；以及
    所述第一接收模块接收到的签署位置信息具体包括：签署位置所在合同图片的图片标识和签署位置坐标信息。
  19. 如权利要求12所述的服务器，其特征在于，包括
    存储模块，用于存储与所述签署方身份信息对应的数字证书；以及
    数字证书写入模块，用于根据所述签署方身份信息在存储模块中获取数字证书，将所述数字证书写入所述签署模块获取到的所述合同文档。
  20. 如权利要求12所述的服务器，其特征在于，所述标识生成模块具体包括：
    第六接收子模块，用于接收第一客户端发送的合同文档；
    第二判断子模块，用于判断所述第六接收子模块接收到的合同文档格式是否是预设格式；
    第三判断子模块，用于若所述第二判断子模块判定合同文档格式不是预设格式则判断所述合同文档格式是否可以转换成所述预设格式；
    第二转换子模块，用于若所述第二判断子模块判定合同文档格式是预设格式则将所述所述合同文档转换成合同图片；还用于若所述第三判断子模块盘判定所述合同文档格式可以转换成所述预设格式则将所述合同文档转换为所述预设格式；并将转换格式后的合同文档转换成合同图片；以及
    第七发送子模块，用于所述第三判断子模块盘判定所述合同文档格式不可以转换成所述预设格式时向第一客户端发送合同文档格式不支持提醒。
  21. 如权利要求12所述的服务器，其特征在于，还包括：
    第三接收模块，用于接收第二客户端发送的合同验证图片；
    第三判断模块，用于根据所述第二接收模块接收到的合同标识获取合同文档，将所述第三接收模块接收到的所述合同验证图片与所述合同文档进行比对，判断内容是否一致；
    所述签署模块，具体用于所述第三判断模块判定所述合同验证图片与所述合同文档内容一致时根据签署位置信息将所述第二接收模块接收到的签署图片写入所述第三判断模块获取到的所述合同文档；以及
    第六发送模块，用于所述第三判断模块判定所述合同验证图片与所述合同文档内容不一致时向第二客户端发送合同被篡改提醒。
  22. 如权利要求21所述的服务器，其特征在于，第三判断模块具体包括：
    第六判断子模块，用于对所述第三接收模块接收的所述合同验证图片进行光学字符识别，将识别得到的文字进行字数统计，判断合同验证图片中的字数是否大于预设值；
    第七判断子模块，用于所述第六判断子模块判定所述第三接收模块接收的所述合同验证图片中的字数大于预设值时则将所述第三接收模块接收到的所述合同验证图片与所述合同文档进行比对，判断内容是否一致；以及
    第九发送子模块，用于所述第七判断子模块判定所述第三接收模块接收的所述合同验证图片中的字数不大于预设值时向第二客户端发送合同验证图片不合格提醒。
PCT/CN2017/093921 2016-07-25 2017-07-21 一种订立电子合同的方法及服务器 WO2018019187A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/307,167 US10977432B2 (en) 2016-07-25 2017-07-21 Method for concluding electronic contracts and server

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201610592410.9A CN106295405B (zh) 2016-07-25 2016-07-25 一种订立电子合同的方法及服务器
CN201610592410.9 2016-07-25

Publications (1)

Publication Number Publication Date
WO2018019187A1 true WO2018019187A1 (zh) 2018-02-01

Family

ID=57652417

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2017/093921 WO2018019187A1 (zh) 2016-07-25 2017-07-21 一种订立电子合同的方法及服务器

Country Status (3)

Country Link
US (1) US10977432B2 (zh)
CN (1) CN106295405B (zh)
WO (1) WO2018019187A1 (zh)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109472686A (zh) * 2018-10-12 2019-03-15 深圳壹账通智能科技有限公司 合同签订方法、装置及终端设备
CN109472545A (zh) * 2018-10-12 2019-03-15 重庆君子签科技有限公司 基于本地部署的签约系统
CN111724155A (zh) * 2019-03-22 2020-09-29 北京沃东天骏信息技术有限公司 电子合同管理方法与装置
CN114024723A (zh) * 2021-10-22 2022-02-08 富途网络科技(深圳)有限公司 基于esop系统的线上签署方法及装置、设备、介质

Families Citing this family (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106295405B (zh) * 2016-07-25 2019-02-12 飞天诚信科技股份有限公司 一种订立电子合同的方法及服务器
CN107133777A (zh) * 2017-04-25 2017-09-05 飞天诚信科技股份有限公司 一种电子合同的创建、签署方法及系统
ES2937783T3 (es) * 2017-09-21 2023-03-31 Lleidanetworks Serveis Telematics Sa Método de certificación de un contrato electrónico para identificación electrónica y servicios de confianza (eidas)
CN107579990A (zh) * 2017-09-26 2018-01-12 北京华云智汇科技有限公司 合同管理方法及服务器
CN107527215A (zh) * 2017-09-28 2017-12-29 山西特信环宇信息技术有限公司 一种基于生物识别技术的电子合同系统及操作方法
CN108595938B (zh) * 2018-03-15 2020-08-25 兴业数字金融服务（上海）股份有限公司 基于结构化控件的电子合同应用范围拓展方法及系统
CN109325729B (zh) * 2018-08-21 2023-09-29 平安科技（深圳）有限公司 一种生成电子合同的方法及服务器
CN110245911A (zh) * 2018-09-11 2019-09-17 爱信诺征信有限公司 电子合同签署方法及其装置、系统
CN109636681A (zh) * 2018-10-16 2019-04-16 深圳壹账通智能科技有限公司 合同生成方法、装置、设备及存储介质
CN110061844B (zh) * 2019-03-13 2023-05-30 深圳壹账通智能科技有限公司 基于区块链的电子签名方法、电子装置及可读存储介质
CN110245220B (zh) * 2019-05-05 2022-03-11 深圳法大大网络科技有限公司 电子文件签署方法、装置及服务器、存储介质
CN110427602A (zh) * 2019-07-26 2019-11-08 杭州尚尚签网络科技有限公司 一种基于模板的快速、安全的创建和发送电子合同的方法
CN110991978A (zh) * 2019-10-14 2020-04-10 安徽继远软件有限公司 一种基于第三方公证的电子合约签署方法及系统
CN111127580B (zh) * 2019-12-30 2023-08-15 北京天威诚信电子商务服务有限公司 自定义签章生成方法、计算机工具、签约方法及系统
CN111464555B (zh) * 2020-04-14 2021-10-15 江苏慧世联网络科技有限公司 一种基于客户端屏幕录像的文件签署确认方法以及业务服务器、认证服务器和客户端
CN111581653A (zh) * 2020-04-30 2020-08-25 平安科技（深圳）有限公司 合同文签方法、装置、设备及计算机可读存储介质
CN111698451B (zh) * 2020-06-17 2022-07-08 北京天威诚信电子商务服务有限公司 基于视频会议的电子合同签署方法、平台及系统
CN112347452B (zh) * 2020-11-10 2023-08-04 上海祺鲲信息科技有限公司 电子合同签署的方法、电子设备及存储介质
CN112488735A (zh) * 2020-12-07 2021-03-12 上海汉图科技有限公司 一种合同签署方法、装置和电子设备
CN112231771B (zh) * 2020-12-11 2021-03-23 浙江数秦科技有限公司 一种基于区块链的电子合同在线签署及保全方法
CN113961124B (zh) * 2021-09-27 2024-02-27 上海联影医疗科技股份有限公司 医学图像显示方法、装置、计算机设备和存储介质
HUP2100403A1 (hu) 2021-11-24 2023-05-28 Otp Bank Nyrt Dokumentumhitelesítõ rendszer és eljárás
CN114095180A (zh) * 2021-11-29 2022-02-25 深圳市电子商务安全证书管理有限公司 数字证书管理方法、装置及介质
CN114612269B (zh) * 2022-05-11 2022-09-13 山东国盾网信息科技有限公司 基于电子签名技术的电子劳动合同平台

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102622568A (zh) * 2011-01-28 2012-08-01 阿里巴巴集团控股有限公司 订单文件中订单标识信息的识别方法、系统及装置
CN105787741A (zh) * 2016-02-17 2016-07-20 林慕新 基于手机客户端的电子合同签署系统及其使用方法
CN106295405A (zh) * 2016-07-25 2017-01-04 飞天诚信科技股份有限公司 一种订立电子合同的方法及服务器

Family Cites Families (12)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CA2428665C (en) * 2000-12-14 2010-12-21 Silanis Technology Inc. Web-based method and system for applying a legally enforceable signature on an electronic document
US9460346B2 (en) * 2004-04-19 2016-10-04 Google Inc. Handheld device for capturing text from both a document printed on paper and a document displayed on a dynamic display device
US20070203854A1 (en) 2006-02-28 2007-08-30 Karamchedu Murali M Electronic contracting
NZ586128A (en) * 2007-12-14 2013-06-28 Routeone Llc Electronically capturing the signatures of a customer, vendor and finance source for the production of an electronic contract
US8955137B2 (en) * 2012-12-21 2015-02-10 State Farm Mutual Automobile Insurance Company System and method for uploading and verifying a document
US20170063551A1 (en) * 2014-07-25 2017-03-02 Snapfile Ltd. System and method for securely managing integrity-verifiable and authenticable information
WO2016043197A1 (ja) * 2014-09-16 2016-03-24 新日鉄住金ソリューションズ株式会社 管理システム、携帯端末装置、管理方法、情報処理方法及びプログラム
US20160224528A1 (en) * 2015-01-30 2016-08-04 Technology Happens LLC Method and System for Collaborative, Streaming Document Sharing with Verified, On-Demand, Freestyle Signature Process
CN105095168B (zh) * 2015-07-17 2019-06-04 北京奇虎科技有限公司 一种合同文档的自动生成方法和装置
US20170116669A1 (en) * 2015-10-21 2017-04-27 Built Technologies, Inc. Real estate construction loan management system with field inspector interface and geotag verification
CN105635169B (zh) * 2016-01-26 2019-04-19 江苏慧世联网络科技有限公司 一种基于互联网的电子合同签署方法
US10546053B2 (en) * 2016-05-18 2020-01-28 Citrix Systems, Inc. Semi-automated field placement for electronic forms

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN102622568A (zh) * 2011-01-28 2012-08-01 阿里巴巴集团控股有限公司 订单文件中订单标识信息的识别方法、系统及装置
CN105787741A (zh) * 2016-02-17 2016-07-20 林慕新 基于手机客户端的电子合同签署系统及其使用方法
CN106295405A (zh) * 2016-07-25 2017-01-04 飞天诚信科技股份有限公司 一种订立电子合同的方法及服务器

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109472686A (zh) * 2018-10-12 2019-03-15 深圳壹账通智能科技有限公司 合同签订方法、装置及终端设备
CN109472545A (zh) * 2018-10-12 2019-03-15 重庆君子签科技有限公司 基于本地部署的签约系统
CN111724155A (zh) * 2019-03-22 2020-09-29 北京沃东天骏信息技术有限公司 电子合同管理方法与装置
CN114024723A (zh) * 2021-10-22 2022-02-08 富途网络科技(深圳)有限公司 基于esop系统的线上签署方法及装置、设备、介质
CN114024723B (zh) * 2021-10-22 2024-01-16 富途网络科技(深圳)有限公司 基于esop系统的线上签署方法及装置、设备、介质

Also Published As

Publication number Publication date
US20190147027A1 (en) 2019-05-16
CN106295405A (zh) 2017-01-04
US10977432B2 (en) 2021-04-13
CN106295405B (zh) 2019-02-12

Similar Documents

Publication Publication Date Title
WO2018019187A1 (zh) 一种订立电子合同的方法及服务器
CN108881290B (zh) 基于区块链的数字证书使用方法、系统及存储介质
US6789193B1 (en) Method and system for authenticating a network user
US8549303B2 (en) Apparatus, system and method for electronically signing electronic transcripts
CN106067849B (zh) 一种适用于pdf文档的数字签名方法及装置
JP2004537822A (ja) 認証電子文書管理システム及び方法
CN110445771B (zh) 基于区块链的交互记录取证方法、装置、介质及服务器
US20110219074A1 (en) Method and device for intercommunicating address book information between different networks
WO2019174354A1 (zh) 认证方法及装置
WO2020042508A1 (zh) 一种基于区块链的理赔事件的处理方法、系统及电子设备
US7689900B1 (en) Apparatus, system, and method for electronically signing electronic transcripts
KR20000049674A (ko) 웹 사이트를 이용한 전자서명 제공 및 인증 방법
CN111914231A (zh) 基于区块链的身份验证方法、系统、设备及存储介质
CN113129008B (zh) 数据处理方法、装置、计算机可读介质及电子设备
KR101951270B1 (ko) 메신저 인증 서버를 이용한 문서 발송 시스템 및 그 방법
CN109829276B (zh) 一种基于fido协议身份认证的电子发票统一管理方法及系统
CN110222077A (zh) 基于区块链的证明方法及系统
KR101359512B1 (ko) 온라인 전자 서명을 위한 인증 시스템 및 방법
CN109658041A (zh) 文件的生成装置及其生成方法、设备和可读存储介质
JP2009031849A (ja) 電子申請用証明書発行システムおよび電子申請受付システム、並びにそれらの方法およびプログラム
CN114444130A (zh) 基于区块链的电子证书互信互认平台
JP2004514216A (ja) 立証資料の格納による認証サービス方法及びシステム
KR101044518B1 (ko) 휴대폰의 ｓｍｓ를 이용하여 문서의 서명 또는 제품의 진위를 인증하는 인증 시스템 및 인증 방법
US11971929B2 (en) Secure signing method, device and system
CN113128951B (zh) 一种基于企业链码的电子合同管理方法及系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 17833490

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17833490

Country of ref document: EP

Kind code of ref document: A1