A method, system, device and medium for realizing cross-platform electronic document signing

Abstract

This application provides a method for implementing cross-platform electronic document signing. The signatory initiates a contract signing request to the open platform through the application platform. The open platform delivers the signing task to the designated application platform and checks whether the designated application platform has the signing capability. The designated application platform with the signing capability executes the signing task to complete the signing, and synchronizes the signed contract documents to all application platforms connected to the open platform. It is convenient for signatories to complete the signing of electronic contracts and electronic documents on different platforms and different terminals, which greatly solves the dependence of electronic contract document signing on a single platform and a single application system, and provides a variety of application platforms and terminal options.

Description

Technical Field

[0001] The present invention relates to the technical field of computer information processing, and in particular to a method for implementing electronic contract signing across platforms. Background Art

[0002] There are now many electronic contract application platforms on the market, where you can register and complete real-name authentication, apply for electronic seals, initiate and sign electronic contracts, and other functions.

[0003] Electronic contract application platforms are all based on a single platform (a single platform refers to a designated application, and specific functions can only be realized on the designated application and cannot be realized through other applications). For the signing of electronic contracts and electronic documents, for an electronic document, it can only be signed on the designated platform. There is no cross-platform signing capability, and it is impossible to realize cross-platform signing. It is very unfriendly to signing terminals with different signing application modules installed. The same user may need to download multiple application APPs to sign multiple different documents. The signing parties of the same electronic contract must also download the same APP and use the same platform to achieve it, which brings great inconvenience to the user's signing, affects the user experience, and reduces work efficiency.

[0004] Existing electronic contract signing methods in the market are all conducted on a single application platform. For example, the popular YiSignPro and Tencent E-Signature applications. Signing tasks initiated on these applications cannot be signed through other applications and can only be signed on a single designated application.

[0005] Publication number CN115758427A, named "A method, device and equipment for signing an electronic contract", provides a smart contract signing method, including creating a signing task containing the signing template and signatory required for the current business project, configuring the signing template in the signing task, obtaining the configuration information of the signing template, and finally generating the corresponding contract document according to the configuration information of the signing template, and conveying the generated contract document to the signatory for signature according to the signatory in the signing task, thereby realizing the automatic generation and signing of the smart contract and improving the signing efficiency of the smart contract.

[0006] This document also does not address or provide solutions to the problem of signing electronic contracts on different signing application platforms. When an electronic contract involves different signatories, they all need to complete the signing task on the same signing application platform. Summary of the Invention

[0007] Based on the current various electronic document and contract signing application platform products, the existing technology uses a single platform application software to complete the signing. Different signatories of the same document can only sign on the same signing platform. A terminal may need to install multiple signing application APPs. After a signing is completed, these APPs are completely unused, occupying terminal resources and being extremely inconvenient to use.

[0008] In view of this, this application proposes a cross-platform, cross-terminal document and contract signing method, which makes it convenient for signatories to complete electronic contract signing on different platforms and different terminals, and greatly solves the dependence of electronic contract document signing on a single platform and a single application system. At the same time, it provides a variety of application platforms and terminals to choose from, making it more convenient for signatories to complete the signing.

[0009] Based on one aspect of the present application, a method for realizing cross-platform electronic document signing is proposed. Multiple signing application platforms are connected to an open platform. The signing initiator terminal completes its own signing through any signing application platform and initiates a signing delivery request to the open platform. The open platform obtains the signing information to generate a signing task, delivers the signing task to the designated signing application platform, and checks whether the designated signing application platform has the signing capability. The destination address terminal executes the signing task on the designated signing application platform with the signing capability to complete the signing, and synchronizes the signing data to the open platform and all signing application platforms.

[0010] Further preferably, the execution of the signing task specifically includes: the signing initiator terminal calls any signing application platform with signing capabilities to sign at the location to be signed by its own party in the electronic document, and the remaining signatories call the signing application platform with signing capabilities through their respective signing terminals, and complete their respective signatures at the designated location of the electronic document, and embed the signed electronic handwriting into the designated signing location of the electronic document through telegraphic fusion.

[0011] Further preferably, the open platform selects the application platform to be delivered according to the destination address in the signing information, and sends a signing prompt message to the destination address terminal. The destination address terminal calls the signing module through the loaded signing capability application platform to complete the signing, and synchronizes the signing information and signing task number to the open platform and all signing application platforms. For application platforms that do not have signing capabilities, they can only view the signing information and cannot sign the file.

[0012] Further preferably, the multiple signing application platforms are connected to the open platform, the signing application platform applies for a developer account to the open platform, and submits an application for listing after obtaining the developer account, and the application platform that meets the listing requirements is connected to the open platform; the signing application platform sends signing information to the open platform through a network transmission protocol request; connecting the application platform that meets the listing requirements to the open platform includes the open platform obtaining application information of each signing application platform, configuring the signing application platform that initiates the signing task in the signing application platform to obtain the callback interface address of the open platform synchronization information, and if the signing application platform meets the entry requirements, it obtains its own application identifier appid, the random access character accesskey of the application, and the secret key Secret generated by the application from the open platform

[0013] Further preferably, the synchronized data includes the signing task number and signing information, and the signing information includes: basic configuration of all initiated signing documents, including signing location configuration information, signing document information, signatory information, JSON data of the signing document, and various attachments.

[0014] Further preferably, the signing application platform calls the interface for generating the application credential token, passes the appid, accesskey, and secret as parameters to the delivery task interface, generates and returns the application credential token, and when the application platform submits the signing task request, calls the delivery task interface, sets the application credential token to the header information of the signing task request as the credential of the request; after the open platform receives the signing task request, it determines whether the token is valid based on the header information analysis, and if it is valid, continues to parse the delivered application information from the token, and determines the signing application platform that submits the delivery request task based on the appid, as well as the destination terminal and designated signing application platform that need to be delivered.

[0015] According to another aspect of the present application, a system for realizing cross-platform electronic contract signing is proposed, including a signing application platform, an open platform, and a delivery module. Multiple signing application platforms are connected to the open platform. The signing initiator terminal completes its own signing through any signing application platform and initiates a signing delivery request to the open platform. The open platform obtains the signing information to generate a signing task, delivers the signing task to the designated signing application platform, and checks whether the designated signing application platform has the signing capability. The destination address terminal executes the signing task on the designated signing application platform with the signing capability to complete the signing, and synchronizes the signing data to the open platform and all signing application platforms.

[0016] Further preferably, the execution of the signing task specifically includes: the signing initiator terminal calls any signing application platform with signing capabilities to sign at the location to be signed by its own party in the electronic document, and the remaining signatories call the signing application platform with signing capabilities through their respective signing terminals, and complete their respective signatures at the designated location of the electronic document, and embed the signed electronic handwriting into the designated signing location of the electronic document through telegraphic fusion.

[0017] Further preferably, the open platform selects the application platform to be delivered according to the destination address in the signing information, and sends a signing prompt message to the destination address terminal. The destination address terminal calls the signing module through the loaded signing capability application platform to complete the signing, and synchronizes the signing information and signing task number to the open platform and all signing application platforms. For application platforms that do not have signing capabilities, they can only view the signing information and cannot sign the file.

[0018] Further preferably, the multiple signing application platforms are connected to the open platform, the signing application platform applies for a developer account to the open platform, and submits an application for listing after obtaining the developer account, and the application platform that meets the listing requirements is connected to the open platform; the signing application platform sends signing information to the open platform through a network transmission protocol request; connecting the application platform that meets the listing requirements to the open platform includes the open platform obtaining application information of each signing application platform, configuring the callback interface address of the signing application platform that initiates the signing task to obtain the open platform synchronization information, and if the signing application platform meets the entry requirements, obtains its own application identifier appid, the random access character accesskey of the application, and the secret key Secret generated by the application from the open platform.

[0019] Further preferably, the signing application platform calls the interface for generating the application credential token, passes the appid, accesskey, and secret as parameters to the delivery task interface, generates and returns the application credential token, and when the application platform submits the signing task request, calls the delivery task interface, sets the application credential token to the header information of the signing task request as the credential of the request; after the open platform receives the signing task request, it determines whether the token is valid based on the header information analysis, and if it is valid, continues to parse the delivered application information from the token, and determines the signing application platform that submits the delivery request task based on the appid, as well as the destination terminal and designated signing application platform that need to be delivered.

[0020] A signing request task is initiated on any signing application platform, and the signing task is completed on this platform. The signing information is configured and saved in the current signing application platform database. The signing information is then sent to the open platform in JSON file format, and the open platform database stores the signing task information. After selecting the signing application platform to be delivered, the open platform synchronizes the configured signing information and files to the designated signing application platform via HTTP protocol. The designated signing application platform saves the signing task, configuration information, and files in the database, completing the signing task delivery. The open platform obtains application information from each signing application platform, configures a callback address, and the signing application platform submits an application to join the open platform. If the open platform verifies that the application platform is successfully joined, it connects the signing application platform to the open platform control module, generates application information, and configures the signing application platform callback address. The application information includes: application identifier Appid, application random access string Accesskey, and application-generated secret key Secret. If the signing application platform meets the entry requirements, it obtains its own application ID, application random access string, and application-generated secret key from the open platform. Configuring the application callback address includes configuring the callback interface address in the signing application platform for the signing application platform that initiated the signing task to obtain open platform synchronization information.

[0021] The signing application platform sends a signing task request to the development platform via HTTP transmission protocol request; after receiving the signing task request, the open platform sends the signing task information to the designated signing application platform via HTTP; the signing task information includes: the basic configuration of all initiated signing documents, contract signing location configuration information, signing document information, signer information, and JSON data of the signed document; when the signing application platform sends a signing task request to the development platform, it requests the open platform to obtain the calling credential token through the credential interface; the signing application platform uses its own appid and key to publish signing tasks, obtain data, and synchronize.

[0022] Based on another aspect of the present application, an electronic device is proposed, comprising: a processor; and a memory for storing a program, wherein the program comprises instructions, which, when executed by the processor, enable the processor to execute the above-described method for implementing cross-platform electronic contract signing.

[0023] Based on another aspect of the present application, a non-transitory computer-readable storage medium storing computer instructions is proposed, wherein the computer instructions are used to enable the computer to execute the method for implementing cross-platform electronic contract signing according to any one of the above items.

[0024] The cross-platform electronic contract signing system and method proposed in this application enables the signatory to initiate a contract signing request to the open platform through any application platform. The open platform delivers the signing task to the designated application platform, which then executes the signing task and completes the signing. This facilitates the signatory to complete the signing of electronic contracts and electronic documents on different platforms and terminals, greatly solving the dependence of electronic contract document signing on a single platform and a single application system, reducing the terminal load and resource waste, and providing a variety of application platforms and terminals for selection, making it more convenient for the signatory to complete the signing and to conveniently view the signing information and progress. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Further details, features and advantages of the present application are disclosed in the following description of exemplary embodiments in conjunction with the accompanying drawings.

[0026] Figure 1 A schematic block diagram of a cross-platform electronic contract signing system in an exemplary embodiment of the present application;

[0027] Figure 2 Schematic diagram of the cross-platform signing process in an exemplary embodiment of this application;

[0028] Figure 3 A schematic diagram of a cross-platform signing information configuration process in an exemplary embodiment of this application;

[0029] Figure 4 A schematic diagram of a cross-platform signing task implementation process in an exemplary embodiment of the present application;

[0030] Figure 5 An exemplary embodiment of the present application provides an electronic device. DETAILED DESCRIPTION

[0031] The following describes embodiments of the present application in more detail with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are for illustrative purposes only and are not intended to limit the scope of protection of the present application.

[0032] It should be understood that the various steps described in the method embodiments of the present application can be performed in different orders and / or in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0033] As used herein, the term "including" and its variations are open-ended, i.e., "including but not limited to." The term "based on" means "based, at least in part, on." The term "one embodiment" means "at least one embodiment," the term "another embodiment" means "at least one additional embodiment," and the term "some embodiments" means "at least some embodiments." The concepts of "first," "second," etc. mentioned in this application are merely used to distinguish different devices, modules, or units, and are not intended to limit the order or interdependence of the functions performed by these devices, modules, or units.

[0034] It should be noted that the modifications of "one" and "multiple" mentioned in this application are illustrative rather than restrictive. Those skilled in the art should understand that unless otherwise clearly indicated in the context, they should be understood as "one or more".

[0035] The names of the messages or information exchanged between multiple devices in the embodiments of the present application are only used for illustrative purposes and are not used to limit the scope of these messages or information.

[0036] The signatory of a cross-platform contract acts as the initiator of the contract and can also be the recipient. At the same time, the open platform is used for platform entry and task delivery is carried out through the open platform to achieve cross-platform contract signing.

[0037] like Figure 1 Shown is a schematic block diagram of a cross-platform electronic contract signing system in an exemplary embodiment of the present application.

[0038] It includes multiple signing application platforms (such as A, B, C...), open platforms, and delivery modules. Multiple signing application platforms are connected to the open platform. If the signer initiates a contract signing request through platform A, the contract signing request will be sent to the open platform. The open platform obtains the signing information and delivers the signing task to the designated application platform. At the same time, it checks whether the designated application platform has the signing capability. The designated application platform with the signing capability executes the signing task to complete the contract signing, and synchronizes the signed contract documents to the open platform and other application platforms.

[0039] If multiple signatories located in different places and holding different signing terminals need to sign the same electronic contract, the first signatory electronically signs the current document by calling the signing module of the signing application installed on his own terminal. The signing module obtains the electronic handwriting data collected by the signing terminal and embeds the written electronic handwriting into the designated signing position through telegram fusion.

[0040] Signing application platform A initiates a signing request to the open platform. The open platform accepts the signing request and obtains the signing information. Based on the signing information, it delivers the signing task to the designated application platform B or C, etc., checks whether the designated application platform has signing capabilities, and sends a signing reminder to the destination terminals of the remaining signatories. The remaining signatories complete the signing task on the application platform with signing capabilities and synchronize the completed signing information with the open platform and other application platforms. Other signatories use their destination terminals to call the signing module on the application platform with signing capabilities to sign the same electronic document. The signing module obtains the electronic signature handwriting data and embeds the signature handwriting into the designated location of the electronic document through telegram fusion.

[0041] The execution of the signing task specifically includes: for the electronic file that initiates the signing task, the initiating signer first calls any signing application platform to sign at his own signing location, and the remaining signing parties complete their respective signatures at the designated locations of the electronic file through their respective signing application platforms. All signatories under each signing party can sign at the corresponding locations.

[0042] Figure 2 Shown is a schematic diagram of the cross-platform signing process in an exemplary embodiment of the present application.

[0043] The signatory initiates a signing task by calling the signing application module of any signing application platform, saves the signing information, and delivers the signing information to the open platform. The open platform saves the signing information, selects the application platform to be delivered according to the destination address in the signing information, and checks whether the application platform to be delivered has the signing capability. For application platforms that do not have the signing capability, they can only view the signing information but cannot sign the received documents. If the application platform to be delivered has the signing capability, the open platform sends a signing prompt message to the destination address terminal, calls the signing module of the platform through the signing capability application platform owned by the destination address terminal to implement the signing, and displays the electronic signature at the designated signing location through telegraphic fusion. After the destination address terminal completes the signing, the signing information and signing task number are synchronized to the open platform and all signing application platforms.

[0044] The signing information includes: the basic configuration of all initiated signing documents, including signing location configuration information, signing document information, signatory information, JSON data of the signed document, various attachments, etc.

[0045] All application platforms connected to the open platform will synchronize data, including the signing task number and signing information (including: basic configuration of all initiated signing documents, contract signing location configuration information, signing document information, signatory information, JSON data of the signed document, various attachments, etc.).

[0046] Synchronizing data ensures that the data on each signing platform is unified and interoperable; after data synchronization, it is guaranteed that users can view the task information on all signing application platforms connected to the open platform.

[0047] Initiate a task through any signing application platform. After the application platform initiates the task, it will deliver the task to the open platform. It can be delivered to other application platforms through the development platform. At the same time, check whether other application platforms have signing capabilities. If they have signing capabilities, they can sign on this application platform. If they do not have signing capabilities, the application platform will check and cannot sign. The open platform will continue to deliver the signing task to other platforms with signing capabilities, and prompt the terminal to be signed at the destination address to enter the platform with signing capabilities and call the signing module to complete the signing task.

[0048] To determine whether a platform has the signing capability, when the task is initiated, the signature is delivered to the open platform. When the open platform delivers it to other application platforms, when the destination address terminal logs in to the application platform to sign, the signing task information is used to obtain whether the application platform has the signing capability from the signing task information, and whether the signing information contains the platform as the signing application platform to determine whether the application platform can complete the signing operation.

[0049] like Figure 3 Shown is a schematic diagram of the cross-platform information configuration process in an exemplary embodiment of the present application.

[0050] The Open Platform obtains application information based on the signed application modules of each application platform and configures the callback address. The signed application module applies to be registered on the Open Platform. After verification, the signed application platform is connected to the Open Platform and enters the Open Platform console to generate application information (appid, accesskey, secret). Appid is the application identifier, accesskey is the random access string for the application, and secret is the secret key generated by the application.

[0051] Enter the configuration options and configure the application callback address, that is, configure the callback interface address for the current application platform to obtain development platform synchronization information in the application platform.

[0052] Signed application platforms entering the Open Platform must upload their applications to the Open Platform for review. Applications passing content testing can be uploaded to the Open Platform. Content testing includes ensuring there is no illegal content, no application vulnerabilities, and no functional anomalies.

[0053] Initiate a signing task through any signing application platform, deliver the signing task to the open platform, the open platform receives the signing information, and delivers the signing task to the designated application platform to check whether the designated application platform has the signing capability. The signatory signs at the signing unit with signing capability through the destination address terminal to complete the electronic contract signing, and then synchronize the signing data to other platforms.

[0054] The signing application platform sends all the information of the signing task to the development platform through the network transmission protocol HTTP request, including the basic configuration of all initiated signing documents, contract signing location configuration information, signing document information, signatory information, JSON data of the signing document, various attachments, etc.

[0055] After receiving the signing task request, the open platform sends all the signing task information via HTTP to the application system that can accept the task delivery.

[0056] The application platform can enter the open platform by submitting an application. If the application platform meets the entry requirements, it can enter.

[0057] Based on the open platform, various application platforms are integrated into it. The signed application platform applies for a developer account with the development platform. After obtaining a developer account, it submits an application for listing. The open platform then reviews and tests the signed application platform to see if it meets the listing requirements. If so, it is integrated into the open platform. For example, you can review the following information.

[0058] Applying for an Open Platform Developer Account: a) Email: Used for account registration. b) Password: Corresponding account password. c) Company Information: i. Company Name: Uniquely identifies the company on the platform. ii. Social Credit Code: Used to verify the company's legitimacy and credit standing. iii. Legal Representative: Used to verify the company's legal representative's identity. iv. Legal Representative ID Number: Used to verify the legal representative's identity. d) Developer Account Information: i. Account: Email address. ii. Password: iii. Tenant Key: iv. Tenant Secret: Account registration creates a default, unactivated application.

[0059] Each signed application platform that applies for admission sends an admission request, which is verified by the open platform. If the application platform meets the admission requirements, it obtains its own application ID appid, the application's random access string accesskey, and the application-generated secret key secret from the open platform.

[0060] The application platform needs a token as a delivery credential when delivering to the development platform. When the application platform delivers a signing task to the development platform, it obtains the call credential token by calling the credential interface of the open platform using the appid, accesskey, and secret.

[0061] The signing application platform can use its own appid, key, etc. to perform a series of operations such as signing task release, data acquisition, and synchronization.

[0062] For example, if application A is launched on the open platform and obtains its appID, accesskey, and secret from the open platform, it calls the API to generate an application token, passing the appID, accesskey, and secret as parameters to the API. The API then generates and returns an application token.

[0063] When the application platform submits a signing task request, it calls the delivery task interface and sets the generated application credential token into the signing task request header as the request credential. Upon receiving this request, the open platform obtains the token from the header and further analyzes it to determine whether it is valid. If so, it continues to parse the token to extract the application information being delivered. Based on the appID, it determines the signing application platform that submitted the delivery request, as well as the destination terminal and the designated signing application platform.

[0064] If the task delivery is invalid, the task delivery fails.

[0065] like Figure 4 Shown is a schematic diagram of a cross-platform signing implementation process in an exemplary embodiment of the present application.

[0066] The signatory initiates a signature on any signing application platform and completes the document signing on the current platform's signing page, completing their own signing task. They then determine the delivery address and signing application platform of the other signatories, generate the signing task information, and configure the contract signing location, signing document, and signatory information on the signing initiation page. After configuring the signing task information, the signed data is saved in the current application platform's database. The signing task information is then sent to the open platform in the specified JSON file format. The open platform also stores a copy of the signing task data. The development platform selects the application platform to deliver the signature based on the delivery address and the designated signing application platform in the signature task information. The open platform then synchronizes the signature information with the designated signing application platform using the HTTP network protocol, delivering the signature task to the designated signing application platform. The designated signing application platform also saves the data in its own database, enabling delivery to the designated platform.

[0067] Connect to the Open Platform's signing application system, providing interfaces for receiving task delivery and data synchronization. Signing tasks can be posted on any signing application platform connected to the Open Platform, and the signing application platform can be selected to accept the task. The signer then signs the document on the selected application platform. This signing event will also be synchronized to all signing application platforms. The signer can then sign on the platform designated in the signing task delivery, using the destination terminal on a signing-capable application platform.

[0068] After signing is completed, the application platform will synchronize the signing information of the entire task to the development platform, and the open platform can synchronize the data of the application platform through interface callback.

[0069] After signing is completed, each platform will also receive a message that the task has been signed and complete all data synchronization to ensure that users can see the signed task on any application platform connected to the open platform.

[0070] After signing, the application platform will synchronize the entire task's signature information with the development platform. The open platform can then synchronize data with the application platform through interface callbacks. This signature information synchronization ensures data interoperability and unified data across platforms, ensuring that users can view the task information on all application platforms connected to the open platform.

[0071] The exemplary embodiments of the present application further provide an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor. The memory stores a computer program executable by the at least one processor, wherein the computer program, when executed by the at least one processor, causes the electronic device to perform a method according to an embodiment of the present application.

[0072] An exemplary embodiment of the present application further provides a non-transitory computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor of a computer, is used to cause the computer to perform a method according to an embodiment of the present application.

[0073] An exemplary embodiment of the present application further provides a computer program product, including a computer program, wherein when the computer program is executed by a processor of a computer, it is used to cause the computer to perform the method according to the embodiment of the present application.

[0074] refer to Figure 5, a block diagram of an electronic device 300 that can serve as a server or client of the present application will now be described, which is an example of a hardware device that can be applied to various aspects of the present application. The electronic device is intended to represent various forms of digital electronic computer equipment, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0075] like Figure 5 As shown, electronic device 300 includes a computing unit 301, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 302 or a computer program loaded from a storage unit 308 into a random access memory (RAM) 303. RAM 303 may also store various programs and data required for the operation of device 300. Computing unit 301, ROM 302, and RAM 303 are interconnected via a bus 304. An input / output (I / O) interface 305 is also connected to bus 304.

[0076] Multiple components within electronic device 300 are connected to I / O interface 305, including an input unit 306, an output unit 307, a storage unit 308, and a communication unit 309. Input unit 306 can be any type of device capable of inputting information into electronic device 300. Input unit 306 can receive input numeric or character information and generate key signal inputs related to user settings and / or function control of the electronic device. Output unit 307 can be any type of device capable of presenting information and may include, but is not limited to, a display, a speaker, a video / audio output terminal, a vibrator, and / or a printer. Storage unit 308 may include, but is not limited to, a magnetic disk or an optical disk. Communication unit 309 allows electronic device 300 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks and may include, but is not limited to, a modem, a network card, an infrared communication device, a wireless communication transceiver and / or a chipset, such as a Bluetooth device, a WiFi device, a WiMax device, a cellular communication device, and / or the like.

[0077] The computing unit 301 can be any general-purpose and / or specialized processing component with processing and computing capabilities. Some examples of the computing unit 301 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The computing unit 301 performs the various methods and processes described above. For example, in some embodiments, the secure electronic file formation method can be implemented as a computer software program tangibly embodied on a machine-readable medium. In some embodiments, part or all of the computer program can be loaded and / or installed onto the electronic device 300 via the ROM 302 and / or the communication unit 309. In some embodiments, the computing unit 301 can be configured to perform the calculation of file hash values ​​by any other suitable means (e.g., via firmware).

[0078] The program code for implementing the methods of the present application can be written in any combination of one or more programming languages. Such program code can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that when the program code is executed by the processor or controller, the functions / operations specified in the flow charts and / or block diagrams are implemented. The program code can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0079] In the context of this application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or apparatus. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of machine-readable storage media may include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fibers, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0080] As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, apparatus, and / or device (e.g., a magnetic disk, an optical disk, a memory, a programmable logic device (PLD)) for providing machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal. The term "machine-readable signal" refers to any signal for providing machine instructions and / or data to a programmable processor.

[0081] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0082] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network (LAN), a wide area network (WAN), and the Internet.

[0083] Computer systems may include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The client and server relationship arises through computer programs running on the respective computers and having a client-server relationship to each other.

Claims

1. A method for implementing electronic document signing across platforms, characterized in that: Multiple signing application platforms are connected to the open platform. The signing initiator terminal completes its own signing through any signing application platform and initiates a signing delivery request to the open platform. The open platform obtains the signing information to generate a signing task, delivers the signing task to the designated signing application platform, and checks whether the designated signing application platform has the signing capability. The destination address terminal executes the signing task on the designated signing application platform with the signing capability to complete the signing, and synchronizes the signing data to the open platform and all signing application platforms. The execution of the signing task specifically includes: the signing initiator terminal calls any signing application platform with signing capabilities to sign at the position to be signed by the party in the electronic document, and the other signatories call the signing application platform with signing capabilities through their respective signing terminals, complete their respective signatures at the designated positions of the electronic document, and embed the electronic handwriting of the signature into the designated signing position of the electronic document through the electronic text fusion method; The multiple signing application platforms are connected to the open platform, the signing application platform applies for a developer account to the open platform, submits an application listing application after obtaining the developer account, and connects the application platform that meets the listing requirements to the open platform; the signing application platform sends signing information to the open platform by way of a network transmission protocol request; connecting the application platform that meets the listing requirements to the open platform includes the open platform obtaining application information of each signing application platform, configuring the signing application platform that initiates the signing task in the signing application platform to obtain the callback interface address of the open platform synchronization information, and if the signing application platform meets the entry requirements, obtains its own application identifier appid, the random access character accesskey of the application, and the secret key Secret generated by the application from the open platform; The signing application platform calls the interface for generating application credential token, passes appid, accesskey, and secret as parameters to the delivery task interface, generates and returns the application credential token, and when the application platform submits the signing task request, calls the delivery task interface and sets the application credential token to the header information of the signing task request as the credential of the request; after receiving the signing task request, the open platform determines whether the token is valid based on the header information. If valid, continue to parse the delivered application information from the token, and determine the signing application platform that submits the delivery request task based on the appid, as well as the destination terminal and the designated signing application platform that need to be delivered.

2. The method according to claim 1, characterized in that The open platform selects the application platform to be delivered according to the destination address in the signing information, and sends a signing prompt message to the destination address terminal. The destination address terminal calls the signing module through the loaded application platform with signing capability to complete the signing, and synchronizes the signing information and signing task number to the open platform and all signing application platforms. For application platforms that do not have signing capabilities, they can only view the signing information but cannot sign the file.

3. A system for implementing electronic document signing across platforms, characterized in that: It includes a signing application platform, an open platform, and a delivery module. Multiple signing application platforms are connected to the open platform. The signing initiator terminal completes its own signing through any signing application platform and initiates a signing delivery request to the open platform. The open platform obtains the signing information to generate a signing task, delivers the signing task to the designated signing application platform, and checks whether the designated signing application platform has the signing capability. The destination address terminal executes the signing task on the designated signing application platform with the signing capability to complete the signing, and synchronizes the signing data to the open platform and all signing application platforms. The execution of the signing task specifically includes: the signing initiator terminal calls any signing application platform with signing capabilities to sign at the position to be signed by the party in the electronic document, and the other signatories call the signing application platform with signing capabilities through their respective signing terminals, complete their respective signatures at the designated position of the electronic document, and embed the electronic handwriting of the signature into the designated signing position of the electronic document through the electronic text fusion method; The multiple signing application platforms are connected to the open platform, the signing application platform applies for a developer account to the open platform, submits an application listing application after obtaining the developer account, and connects the application platform that meets the listing requirements to the open platform; the signing application platform sends signing information to the open platform through a network transmission protocol request; connecting the application platform that meets the listing requirements to the open platform includes: the open platform obtains application information of each signing application platform, and configures the signing application platform that initiates the signing task in the signing application platform to obtain the callback interface address of the open platform synchronization information. If the signing application platform meets the entry requirements, it obtains its own application identifier appid, the random access character accesskey of the application, and the secret key Secret generated by the application from the open platform; The signing application platform calls the interface for generating application credential token, passes appid, accesskey, and secret as parameters to the delivery task interface, generates and returns the application credential token, and when the application platform submits the signing task request, calls the delivery task interface and sets the application credential token to the header information of the signing task request as the credential of the request; after receiving the signing task request, the open platform determines whether the token is valid based on the header information. If valid, continue to parse the delivered application information from the token, and determine the signing application platform that submits the delivery request task based on the appid, as well as the destination terminal and the designated signing application platform that need to be delivered.

4. The system according to claim 3, characterized in that The open platform selects the application platform to be delivered according to the destination address in the signing information, and sends a signing prompt message to the destination address terminal. The destination address terminal calls the signing module through the loaded application platform with signing capability to complete the signing, and synchronizes the signing information and signing task number to the open platform and all signing application platforms. For application platforms that do not have signing capabilities, they can only view the signing information but cannot sign the file.

5. An electronic device, characterized in that: include: processor; and a memory storing a program, wherein the program includes instructions, which, when executed by the processor, cause the processor to execute the method for implementing cross-platform electronic contract signing according to any one of claims 1-2.

6. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: in, The computer instructions are used to enable the computer to execute the method for implementing cross-platform electronic contract signing according to any one of claims 1-2.

Images