Video signature live contract system and method

Abstract

The present invention relates to a video signature live contract system and method, which includes an identity verification unit that receives an ID card image from a user terminal and verifies the authenticity of the ID card; a contract management unit that provides a real-time video contract screen to the user terminal and records the real-time video contract; a video signature generation unit that generates a video signature using a video captured by the user terminal and signature data received from the user terminal; and a face ID generation unit that generates a face ID using the video captured by the user terminal during the video signature generation process, issues a non-fungible token for the generated face ID, and stores and manages it on a blockchain; and the video signature displays the video captured by the user terminal and the signature data generation process as a video.

Description

[Technical Field]

[0001] The present invention relates to a video signature live contract system and method. [Background technology]

[0002] Recently, due to the impact of COVID-19, business processes in non-face-to-face environments, such as video conferencing and working from home, have become a trend.

[0003] The amendment to the Electronic Signature Act has eliminated the superior position of public certificates (hereinafter referred to as "public personal authentication services"), creating a situation in which a means of personal authentication as strong as public personal authentication services is required. As a result, in order to completely replace signatures in an offline environment with an online environment, technological means that can prove the identity of the signing party are becoming increasingly important.

[0004] In preparation for such a situation, private personal authentication services can be used as an alternative to identity authentication and signatures, but they are not yet powerful enough to completely alleviate the concerns of signing parties. For example, when signing a contract using an electronic document and the signing parties remotely sign electronically using their own user devices, it is difficult for the signing parties to directly experience the reliability of the electronic document and electronic signature, as they must rely on the reliability of the technical means of the electronic signature. Summary of the Invention [Problem to be solved by the invention]

[0005] The present invention provides a video signature live contract system and method that can prevent spoofing that can occur in a non-face-to-face contract process by recording the real-time video contract process on video and providing a video signature function, a video signature encryption function, and a face ID generation function when signing the video, thereby preventing contract repudiation by contract participants and ensuring the reliability and security of the contract.

[0006] The technical problems of the present invention are not limited to the above-mentioned technical problems, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention pertains from the following description. [Means for solving the problem]

[0007] A video signature live contract system according to one embodiment of the present invention includes an identity verification unit that receives an ID card image from a user terminal and verifies the authenticity of the ID card; a contract management unit that provides a real-time video contract screen to the user terminal and records the real-time video contract; a video signature generation unit that generates a video signature using a video captured by the user terminal and signature data received from the user terminal; and a face ID generation unit that generates a face ID using the video captured by the user terminal during the video signature generation process, issues a non-fungible token for the generated face ID, and stores and manages it on a blockchain; and the video signature displays the video captured by the user terminal and the signature data generation process as a video.

[0008] The video signature generation unit displays signature information including the name of the signing participant who generated the signature data and the time when the signature was completed on the video signature screen, and the video signature generation unit can generate a video signature ID, which is identification information for the video signature.

[0009] The video signature generation unit performs encryption and decryption processes for the signature data in conjunction with the user terminal, shares a signature key required for the decryption process from the user terminal, and generates video signature information for the video signature, where the video signature information may include a contract name of the real-time video contract, a generation date of the signature data, and the signature key.

[0010] The system may further include a media conversion unit that converts and saves the contract created when subscribing to real-time video into a document file format and issues a document ID that is identification information for the contract, and the document ID may be saved by mapping it to the video signature ID and face ID created when subscribing to the real-time video.

[0011] The media conversion unit may generate an identification code for the contract and input it into a document file of the contract, and the identification code may be data obtained by encrypting the document ID, the video signature ID, and the face ID.

[0012] The face ID generation unit may store metadata for the non-fungible token of the face ID, and the metadata may include the video signature ID, the document ID, and user information of the user who owns the user terminal.

[0013] The contract management unit may include a log generation module that generates and manages the real-time video contract process and the activity record of the user terminal during the real-time video contract process as log data, and an STT module that interprets voice data received from the user terminal during the real-time video contract process and converts it into text data.

[0014] According to one embodiment, a video signature live contract method includes a system for providing real-time video contract and video signature services to a plurality of user terminals, the system performing user authentication at the request of a first user terminal held by a contract facilitator among the plurality of user terminals; the system transmitting an invitation link to a second user terminal different from the first user terminal at the request of the first user terminal; the system providing a real-time video contract screen to the plurality of user terminals; the system providing a video signature function to at least one of the plurality of user terminals; and the system generating a video signature and a face ID for a contract participant holding at least one of the user terminals. The system generates a video signature using video captured by at least one of the user terminals and signature data received from the at least one of the user terminals, and the system can generate a face ID by analyzing a user's face included in the video captured by the user terminal.

[0015] The system's step of generating a video signature may include a step of displaying signature information on the video signature screen, including the name of the signing participant who generated the signature data and the time when the signature was completed, and a step of generating a video signature ID, which is identification information for the video signature.

[0016] The system may further include a step of inputting a plurality of data including signature data from each of the plurality of user terminals and creating a contract; a step of converting the contract created at the time of the real-time video contract into a document file format and saving it, and issuing a document ID which is identification information for the contract; and a step of mapping the document ID with the video signature ID and the face ID generated at the time of the real-time video contract and saving them.

[0017] The system may further include a step of issuing a non-fungible token for the Face ID and storing and managing it on a blockchain; and a step of storing metadata for the non-fungible token of the Face ID; wherein the metadata may include the video signature ID, the document ID, and user information of the user terminal on which the Face ID was generated.

[0018] The step of the system providing a real-time video contract screen to the plurality of user terminals may include the steps of the system providing a contract template to the plurality of user terminals, and the system displaying a list of multiple contract participants and an input field for each contract participant.

[0019] The system may further include a step of generating and managing the real-time video subscription process and activity records of each of the plurality of user terminals during the real-time video subscription process as log data; and a step of interpreting and converting voice data received from each of the plurality of user terminals during the real-time video subscription process into text data.

[0020] The system may further include a step of recording the real-time video subscription process for the plurality of user terminals and generating video subscription video data; and a step of providing the video subscription video data to at least one of the user terminals.

[0021] The step of the system providing the video contract video data to at least one of the user terminals may include the step of the system receiving personal authentication data and an identification code from at least one of the user terminals, and the step of confirming that the personal authentication data is personal authentication data corresponding to the identification code.

[0022] Specific details of other embodiments are included in the detailed description and drawings. [Effects of the Invention]

[0023] According to the video signature live contract system and method according to the embodiment, the real-time video contract process is recorded on video, and a video signature function, a video signature encryption function, and a face ID generation function at the time of video signing are provided, thereby preventing spoofing that may occur during the non-face-to-face contract process and preventing future contract repudiation by contract participants. Therefore, the system and method are advantageous in ensuring the reliability and security of contracts compared to face-to-face contracts as well as existing non-face-to-face contracts using electronic documents and electronic signatures.

[0024] In addition, the video signature, Face ID, and documents generated during the real-time video contract process can be managed separately on encryption and / or blockchain, which is advantageous in preventing forgery of contracts and increasing the security of contracts.

[0025] The effects of the embodiments of the present invention are not limited to the above-mentioned examples, and various other effects are included in the present specification. [Brief explanation of the drawings]

[0026] [Figure 1] 1 is a schematic diagram illustrating a network configuration of a video signature live contract system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram illustrating a schematic configuration of a user terminal according to an embodiment of the present invention. [Figure 3] 1 is a block diagram illustrating a schematic configuration of a video signature live contract system according to an embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram illustrating a schematic configuration of a contract management unit according to an embodiment of the present invention. [Figure 5] 1 is a flowchart illustrating a video signature live contract method of a video signature live contract system according to an embodiment of the present invention. [Figure 6]1 is a flowchart illustrating a method for providing real-time video contract and video signature services in a video signature live contract system according to an embodiment of the present invention. [Figure 7] 1 is a flowchart illustrating a method for providing video contract video data to a user terminal in a video signature live contract system according to an embodiment of the present invention. [Figure 8] 8 to 12 are exemplary diagrams of screens provided to a user terminal by a video signature live contract system according to an embodiment of the present invention via an application program, application, and / or website, and FIG. 8 is an exemplary diagram showing a screen provided to a user terminal by a video signature live contract system according to an embodiment of the present invention, where the video signature live contract system provides a participant invitation function. [Figure 9] 10 is an exemplary diagram showing a screen in which a video signature live contract system according to an embodiment of the present invention provides a real-time video contract service to a user terminal. [Figure 10] 10 is an exemplary diagram showing a screen in which a video signature live contract system according to an embodiment of the present invention generates and manages log data for a real-time video contract. [Figure 11] 10 is an exemplary diagram illustrating a screen in which a contract created during real-time video contracting is converted into a document form in a video signature live contracting system according to an embodiment of the present invention. [Figure 12] 12 is an exemplary diagram showing a screen on which a video signature live contract system according to an embodiment of the present invention provides video signature data to a user terminal when the user terminal clicks on area A in FIG. 11 . DETAILED DESCRIPTION OF THE INVENTION

[0027] In order to clarify the technical concept of the present invention, preferred embodiments of the present invention will be described in detail below with reference to the accompanying drawings. When describing the present invention, detailed descriptions of related known functions or components will be omitted if it is determined that such descriptions may unnecessarily obscure the gist of the present invention. Components having substantially the same functional configurations among the drawings will be given the same reference numerals and characters whenever possible, even if they are shown in different drawings. For convenience of description, devices and methods will be described together when necessary.

[0028] FIG. 1 is a schematic diagram showing a network configuration of a video signature live contract system according to an embodiment of the present invention.

[0029] Referring to FIG. 1, a network configuration of a video signature live contract system according to an embodiment includes a video signature live contract system 100, a plurality of user terminals 200_1 and 200_2, and a network 300.

[0030] The video signature live contract system 100 (or may be abbreviated as 'system 100') provides an application program, application, and / or website to the user terminal 200, and can provide a video signature live contract service so that the user terminal 200 can perform real-time video contracting and video signing via the provided application program, application, and / or website. A detailed description of the video signature live contract system 100 will be provided with reference to Figures 3 and 4.

[0031] The plurality of user terminals 200_1 and 200_2 may be electronic devices carried by users who use the services provided by the video signature live contract system 100. For example, the user terminal 200 may include a mobile phone, a smartphone, a smart pad, a notebook computer, a digital broadcasting terminal, a personal digital assistant (PDA), a portable multimedia player (PMP), a navigation system, a tablet PC, and various wearable devices such as a smart watch and a smart band. However, the user terminal 200 is not limited thereto and may be various types of electronic devices that have a communication function capable of wireless communication, a camera function, an input function, and are capable of executing images.

[0032] The user terminal 200 can install and run an application program and / or application provided by the video signature live contract system 100, or can connect to a website provided by the video signature live contract system 100 via the network 300. The user terminal 200 can use the video signature live contract service of the video signature live contract system 100 via the application program, application and / or website.

[0033] FIG. 2 is a block diagram showing a schematic configuration of a user terminal according to an embodiment of the present invention.

[0034] Referring to FIG. 2, the user terminal 200 includes a communication unit 210, a camera module 220, a display module 230, an input interface 240, and a data storage module 250.

[0035] The communication unit 210 can perform wired or wireless data communication with the video signature live contract system 100. The communication unit 210 can transmit and receive data to and from the video signature live contract system 100 and other user terminals 200 by using at least one of a wired Internet communication method supporting TCP / IP (Transmission Control Protocol / Internet Protocol) or various wireless communication methods such as WCMDA (Wideband Code Division Multiple Access), LTE (Long Term Evolution), WiBro (Wireless Broadband Internet), and WiFi (Wireless Fidelity).

[0036] The camera module 220 may be built into the user terminal 200, but is not limited to this. As another example, the camera module 220 may be implemented in the form of a webcam and may be connected to the user terminal 200 via a wired or wireless connection. The user terminal 200 may provide the video signature live contract system 100 with images captured in real time via the camera module 220.

[0037] The display module 230 can display a screen provided by the video signature live agreement system 100 on the user terminal 200. In some embodiments, the display module 230 can also include a touch screen panel (TSP), in which case the display module 230 can also serve as the input interface 240.

[0038] The input interface 240 can convert user input into data in cooperation with an input device such as a keyboard, a mouse, a touch pen, or a touch pad. The user terminal 200 can provide the data received through the input interface 240 to the video signature live contract system 100. For example, when a user signs using the display module 230 including a touch screen panel, the input interface 240 can provide the signature data to the video signature live contract system 100.

[0039] The data storage module 250 can store data received from the video signature live contract system 100 and other user terminals 200 via the network 300. For example, the data storage module 250 can store a copy of a contract received from the video signature live contract system 100.

[0040] The network 300 is a communication network through which the video signature live contract system 100 and the multiple user terminals 200 communicate with each other, and can be configured regardless of the communication mode. For example, the network 300 can be configured with various communication networks such as a short-distance communication network (PAN; Personal Area Network), a local area network (LAN; Local Area Network), a metropolitan area network (MAN; Metropolitan Area Network), and a wide area network (WAN; Wide Area Network), but is not limited to these.

[0041] FIG. 3 is a block diagram showing a schematic configuration of a video signature live contract system according to an embodiment of the present invention.

[0042] Referring to FIG. 3, a video signature live contract system 100 according to one embodiment may include a management unit 110, an identity verification unit 120, a template management unit 130, a contract management unit 140, a video signature generation unit 150, a face ID generation unit 160, a media conversion unit 170, an electronic document management unit 180, and a data storage unit 190.

[0043] The management unit 110 can perform wired or wireless data communication with a plurality of user terminals 200_1 and 200_2 via a network 300. For example, the management unit 110 can provide an application program and / or an application to the user terminal 200 and transmit and receive data to and from the user terminal 200 that runs the application program and / or application, but is not limited to this. For example, the management unit 110 can provide a website to the user terminal 200 and transmit and receive data via the website.

[0044] The management unit 110 can control the overall operation of each component of the video signature live contract system 100. The management unit 110 can control and manage the operation of each component when the video signature live contract system 100 provides a video signature live contract service to a plurality of user terminals 200.

[0045] As a specific example, when any user terminal 200 scans an identification code placed on a copy of a contract generated by the system 100 and connects to an application program, application, and / or website provided by the video signature live contract system 100, the management unit 110 requests personal authentication data from the user terminal 200, and when receiving the personal authentication data from the user terminal 200, the management unit 110 provides the personal authentication data to the personal verification unit 120 and requests confirmation of whether the user corresponds to the identification code.

[0046] In addition, the management unit 110 may request the user terminal 200 to sign up as a member for the service in order to provide the video signature live contract service. In this case, the management unit 110 may store user information including a user ID and password registered by the user terminal 200 when signing up as a member in the data storage unit 190. However, the present invention is not limited to this.

[0047] For example, the video signature live contract system 100 can provide a video signature live contract service without a separate membership registration process, and can store personal authentication data received from the user terminal 200 when providing the video signature live contract service and / or user personal authentication data (e.g., Face ID) generated during the provision of the video signature live contract service.

[0048] In this case, the management unit 110 may request the ID card data and / or user authentication data from the user terminal 200 when the user terminal 200 connects to an application program, application, and / or website provided by the video signature live contract system 100. Here, the ID card data may be data extracted from an ID card image received from the user terminal 200 through optical character recognition (OCR).

[0049] When the personal identification unit 120 receives an ID card image from the user terminal 200, it can verify the authenticity of the ID card in conjunction with an external ID card authenticity verification API (Application Programming Interface).

[0050] In this case, the identity verification unit 120 may extract data from the ID card image through optical character recognition and verify the authenticity of the ID card through the external ID card authenticity verification API using the extracted data, but is not limited to this. In some embodiments, the identity verification unit 120 may also verify the authenticity of the ID card through the external ID card authenticity verification API using the ID card image.

[0051] In another embodiment, the identity verification unit 120 can also build its own ID card authenticity verification API to verify the authenticity of the ID card.

[0052] The identity verification unit 120 can perform user authentication based on data received from the user terminal 200. For example, the identity verification unit 120 can verify whether the data received from the user terminal 200 matches the user information of the user using the user terminal 200 (for example, the user ID and password of the contract participant, and / or user terminal information).

[0053] In addition, the identity verification unit 120 may verify whether identity authentication data received from the user terminal 200 matches pre-stored identity authentication data. For example, the identity verification unit 120 may verify whether identity authentication data received from the user terminal 200 matches pre-stored identity authentication data in response to a request from the management unit 110. The pre-stored identity authentication data may include a face ID generated by the face ID generation unit 160 and issued as a non-fungible token (NFT). In addition, the pre-stored identity authentication data may include a user ID and a password registered by the user terminal 200 when signing up as a member for services provided by the system 100.

[0054] The template management unit 130 can store and manage various types of contract templates. For example, the template management unit 130 can store and manage standard contracts for various contracts such as labor contracts, lease contracts, rental contracts, subcontract contracts, agency contracts, and partnership contracts.

[0055] The template management unit 130 can classify and specify input fields for each contract participant on each contract. For example, each contract may include multiple input fields that must be filled in by the contract participants, and the template management unit 130 can classify and specify input fields that must be filled in by the contract participants when the contract is progressing.

[0056] In this specification, the contract participants can be classified into, but are not limited to, a facilitator (or master) who advances the contract, a signing participant who has the authority to sign the contract, an observer, an agent who has been delegated the authority to sign the contract, and a notary public. The facilitator may be any one of the multiple signing participants.

[0057] When providing a plurality of input fields on a contract being created during the contract process, the template management unit 130 may display the input fields separately according to the classified input fields for each contract participant. For example, when the video signature live contract system 100 displays a contract on each user terminal 200, the template management unit 130 may display input fields classified according to the contract participant using each user terminal 200 differently from other input fields.

[0058] Specifically, the template management unit 130 can display input fields classified as contract participants in a different color from other input fields and / or highlight them using a box UI (User Interface), but is not limited to this. In some embodiments, the template management unit 130 can also set input fields other than those classified as contract participants so that the user terminal 200 of the contract participant cannot input into them.

[0059] Furthermore, the template management unit 130 can generate a plurality of contract participant lists on one side of the contract displayed on the user terminal 200, and display the number of input items classified for each contract participant and the number of input items together with the contract participant lists. In this case, the template management unit 130 can provide a function that allows the user terminal 200 to move to the input item classified corresponding to the contract participant when the user terminal 200 selects one of the contract participant lists.

[0060] The template management unit 130 can provide contract generation and editing functions to the user terminal 200. The template management unit 130 provides a plurality of standard contracts, and can provide the user terminal 200 with a function for editing the plurality of standard contracts or support a function for generating a new contract.

[0061] The template management unit 130 can automatically classify and designate input fields for each contract participant on the created or edited contract. However, without being limited thereto, for example, the template management unit 130 can receive classification data for input items for each contract participant from the user terminal 200 during the contract creation and editing process, and classify and designate input fields for each contract participant accordingly.

[0062] If any contract participant delegates authority to another person via the authority management module 144 described below, the template management unit 130 can classify and assign the input fields classified as the delegating contract participant to the contract participant in charge.

[0063] As described above, the template management unit 130 according to one embodiment provides a plurality of standard contracts and contract creation and editing functions, and at the same time, facilitates real-time video contracting by classifying and specifying input fields for each contracting participant. It also supports the function of checking who created each input field when reviewing the created contract at a later date, which is advantageous in increasing the completeness and reliability of the contract.

[0064] When any user terminal 200 connects to an application, application, and / or website provided by the system 100, the template management unit 130 can provide the user terminal 200 with a list of previously subscribed contracts and / or a list of templates previously generated by the user terminal 200. Here, the list of previously subscribed contracts is a real-time video contract made by the user terminal 200 and can include a real-time video contract that is saved with video recording stopped during the contract period. The previously generated template list can include a contract that the user terminal 200 generated via the template management unit 130 before the real-time video contract period begins.

[0065] Furthermore, when the user terminal 200 invites at least one contract participant via the participant invitation module 142, the template management unit 130 can check whether or not a contract has already been concluded between the user who owns the user terminal 200 and the invited contract participant. If a contract has already been concluded, the template management unit 130 can provide the user terminal 200 with a contract template for the already concluded contract.

[0066] The contract management unit 140 can control and manage the real-time video contract. The contract management unit 140 can send and receive data to and from each user terminal 200 of multiple contract participants and create a contract. In addition, the contract management unit 140 can send data received from the user terminal 200 to the video signature generation unit 150 and the face ID generation unit 160, or can link the video signature and face ID generated by the video signature generation unit 150 and the face ID generation unit 160, respectively, with the contract being created.

[0067] Referring to FIG. 4, the contract management unit 140 according to one embodiment may include an input / output interface module 141, a participant invitation module 142, a log generation module 143, an authority management module 144, a video recording module 145, and an STT module 146.

[0068] The input / output interface module 141 can interface with multiple user terminals 200 through application programs, applications, and / or websites provided by the system 100. The input / output interface module 141 can output data such as a real-time video subscription screen to the multiple user terminals 200 or receive data from the multiple user terminals 200.

[0069] The real-time video contract screen provided by the input / output interface module 141 to the user terminal 200 may include multiple user interfaces (UIs). When the user terminal 200 selects (or clicks) one of the multiple user interfaces, the input / output interface module 141 may transmit data or request data to other components of the system 100 to provide a corresponding screen or function.

[0070] For example, if any of the user terminals 200 under contract attaches an ID card image, the input / output interface module 141 can provide the ID card image to the identity verification unit 120. Specific examples of the real-time video contract screen provided to the user terminal 200 by the input / output interface module 141 will be described later with reference to Figures 5 to 12.

[0071] The participant invitation module 142 may provide a contract participant invitation function to the user terminal 200. For example, the participant invitation module 142 may send an invitation link for participating in a video signature live contract to another user terminal 200 in response to a request from the user terminal 200. When providing the invitation link to the invited user terminal 200, the participant invitation module 142 may further provide information such as, but not limited to, the inviter, information about the contract (e.g., the contract name), and the type of contract participant (e.g., the signing participant, observer, agent, notary public, etc.).

[0072] Here, the invitation link may be a link that connects to a contract created by the inviting user terminal 200 via an application program, application, and / or website provided by the system 100. The invitation link may be provided in various forms such as an icon, text, etc.

[0073] The participant invitation module 142 may interface with the contact, email and / or messenger applications of the user terminal 200 via the input / output interface module 141 to provide the user terminal 200 with a contract participant invitation function.

[0074] The participant invitation module 142 can send an email containing the invitation link to the email account of the invited contract participant, or send a text message (SMS) containing the invitation link to the user terminal 200 of the invited contract participant, and / or send a message containing the invitation link via the messenger application.

[0075] In addition, when an application program or application provided by the video signature live contract system 100 is installed on the user terminal 200 of the invited contract participant, the participant invitation module 142 can send a notification pop-up including the invitation link to the user terminal 200 of the contract participant.

[0076] The log generation module 143 can generate and manage the real-time video subscription process, i.e., the start (e.g., start of video recording), stop and completion times of the real-time video subscription, and activity records of each of the multiple user terminals 200 as log data.

[0077] Here, the activity record of each of the plurality of user terminals 200 may include, but is not limited to, the time of invitation, the time of participation, the time of inputting information into an input field for each participant, the time of starting and completing video signature, the time of delegating authority, the time of delegation approval, and the time of accepting authority for each of the plurality of user terminals 200. The activity record means a record of interactions between the plurality of user terminals 200 and the system 100 during the real-time video contract process.

[0078] The log generation module 143 can chronologically list any real-time video subscription process and provide it in real time to each of the multiple user terminals 200. Furthermore, when any real-time video subscription is completed, the log generation module 143 can manage and store multiple log data generated during any real-time video subscription in association with the recorded video and / or the corresponding subscription.

[0079] The authority management module 144 can provide an authority delegation function for contract participants to the user terminal 200. For example, any contract participant can delegate his / her contract authority through the authority management module 144. Here, the contract authority includes, but is not limited to, the authority of the contract participant to sign when making a real-time video contract through the system 100 and the authority to input information into an input field classified for the contract participant.

[0080] When the authority management module 144 receives an authority delegation request from the user terminal 200 via the input / output interface module 141, the authority management module 144 may provide a power of attorney form to the user terminal 200. For example, the authority management module 144 may provide the power of attorney form to the user terminal 200 via the input / output interface module 141 in the form of a pop-up window, but is not limited thereto, and may provide the power of attorney form in various forms.

[0081] The power of attorney form includes information about the principal, including the contract name, the principal's signature, and contact information, and the principal's signature field and information about the authorized agent can be provided as input fields. The information about the authorized agent includes, but is not limited to, the name, relationship to the principal, email address, phone number, and ID card image.

[0082] If the user terminal 200 attaches an image file of the agent's ID card on the power of attorney form, the authority management module 144 can provide the image of the agent's ID card to the identity verification unit 120 and request verification of the authenticity of the ID card.

[0083] When the authority management module 144 receives a request for the principal's signature on the power of attorney form from the user terminal 200 (e.g., when the user terminal 200 clicks on the power of attorney signature field), the authority management module 144 may further provide a signature pop-up window in which the principal can sign via the user terminal 200. In this case, the principal may, but is not limited to, provide a video signature via the user terminal 200. In some embodiments, the principal may use the user terminal 200 to provide an electronic handwritten signature (or drawing signature), or may use a public personal authentication service or a private personal authentication service (e.g., Kakao Pay authentication, PASS app authentication, BankSign, etc.) to sign.

[0084] The authority management module 144 may transmit a delegation approval request to the user terminal 200 of the contract participant other than the delegator who delegated the contract authority. For example, when the delegator completes the creation of the power of attorney, the authority management module 144 may transmit a delegation approval request to the user terminal 200 of the signing participant and facilitator other than the delegator. The delegation approval request may be provided to the user terminal 200 of the signing participant and facilitator other than the delegator in the form of, but is not limited to, a notification pop-up.

[0085] The authority management module 144 may send a contract invitation request to the agent to the participant invitation module 142. For example, the management authority module 144 may send the phone number or email address entered in the letter of attorney along with the contract invitation request to the participant invitation module 142. As a result, the participant invitation module 142 may send an email, message, and / or notification pop-up including an invitation link to the user terminal 200 of the agent. In this case, the participant invitation module 142 may provide authority delegation information along with the invitation link to the user terminal 200 of the agent. The authority delegation information may include the name of the contract delegated by the delegator, the authority, the delegation date, etc.

[0086] In some embodiments, the authority management module 144 may classify a delegator who has delegated his / her contract authority as a visitor, but is not limited to this. In addition, the authority management module 144 may grant and withdraw contract authority of a contract participant in response to a request from the user terminal 200 of the facilitator among the contract participants.

[0087] In this way, the authority management module 144 according to one embodiment provides a contract authority delegation function on the system 100 when a contract is made offline, and stores and manages authority delegation information, thereby making the tedious delegation confirmation process between contract participants more convenient and advantageous in later verifying whether the delegation was made legally.

[0088] The video recording module 145 can record the real-time video contract process in conjunction with the input / output interface module 141. The video recording module 145 can start, stop, and end video recording in response to a request from the user terminal 200 of the presenter. The video recording module 145 can record the video recording time excluding the video recording stop period. The video recording module 145 can store the video contract video data recorded during the real-time video contract process in the data storage unit 190. In this case, the video contract video data can be stored by mapping it with a document ID, a video signature ID, and a face ID generated during the contract process, which will be described later.

[0089] The STT module 146 can receive voice data of multiple contract participants from multiple user terminals 200 during the real-time video contract process in conjunction with the input / output interface module 141, interpret the voice data, and convert it into text data. The STT module 146 can separate the voice data of each of the multiple contract participants and convert it into text data.

[0090] The STT module 146 may operate in conjunction with the video recording module 145 to display the converted text data in synchronization with the recorded video contract video. In this case, the converted text data may be displayed on the recorded video contract video, but is not limited to this. As another example, the converted text data may be provided as a separate video recording from the recorded video contract video.

[0091] The STT module 146 can also generate the converted text data in a document file, and can display the converted text data along with the time at which the audio data was received from the multiple user terminals 200.

[0092] In this way, the STT module 146 according to one embodiment converts the voice data spoken by multiple signing participants during a real-time video contract process into text data and displays it in synchronization with the recorded video contract video, thereby providing convenience for reviewing the dialogue that took place during the video contract even in situations where the voice cannot be heard. In addition, the STT module 146 generates the converted text data as a document file, thereby eliminating the need to review the dialogue through a recorded video during the contract, and has the advantage of being able to use it as a transcript if any problems arise in the future contract.

[0093] Referring again to FIG. 3, the video signature generation unit 150 can generate a video signature in cooperation with the contract management unit 140. For example, when a signing participant with contractual signing authority requests video signature generation during a real-time video contract via the user terminal 200, the video signature generation unit 150 can generate a video signature using a plurality of data received from the user terminal 200 via the input / output interface module 141. Here, the video signature generation request of the user terminal 200 is generated by the user terminal 200 selecting any of the user interfaces (UIs) provided on a screen displayed via the display module 230 of the user terminal 200, but is not limited thereto.

[0094] The video signature generation unit 150 can receive an image captured by the camera module 220 of the user terminal 200 from the input / output interface module 141 and record the captured image. In addition, the video signature generation unit 150 can provide a signature pop-up window in which a signature can be made to the user terminal 200 via the input / output interface module 141. A signing participant can input an electronic handwritten signature or a seal image into the signature pop-up window using his / her own user terminal 200, or can use a public personal authentication service or a private personal authentication service (e.g., Kakao Pay authentication, PASS app authentication, BankSign, etc.).

[0095] When the user terminal 200 signs through the signature pop-up window, the video signature generation unit 150 can receive the signature process in real time through the input / output interface module 141 and record the signature process so as to display it on the video signature screen. Also, when the user terminal 200 completes inputting signature data in the pop-up window, the video signature generation unit 150 can display signature information, including the names of signing participants and the time when the signature was completed, on the video signature screen.

[0096] When the user terminal 200 signs through the pop-up window, the video signature generation unit 150 can perform signature encryption and decryption processes in conjunction with the user terminal 200 to ensure the security and reliability of the signature.

[0097] For example, the video signature generation unit 150 can share a public key, which is a pair of the private key used for the digital signature, with the user terminal 200 and verify whether the digital signature is correct using the public key. The private key and the public key are generated for each digital signature of the user terminal 200, and may be a key pair valid only for that digital signature.

[0098] Specifically, the user terminal 200 can hash the signature data generated in the video signature process, digitally sign the hashed digest using the private key, and then transmit the signature data and the digital signature to the video signature generation unit 150. In this case, the video signature generation unit 150 can decrypt the digital signature with the public key, hash the signature data, and compare the hashed digest with the data (digest) decrypted with the public key for verification.

[0099] However, the electronic signature, encryption, and decryption methods of the user terminal 200 and the video signature generation unit 150 are not limited to this, and any electronic signature, encryption, and decryption method that allows user and message authentication and ensures confidentiality can be applied.

[0100] When the user terminal 200 completes the video signature, the video signature generation unit 150 can encrypt the video signature data and store it in the data storage unit 190, and generate a video signature ID and video signature information for the video signature.

[0101] The video signature ID is data for identifying each video signature, and the video signature ID may be stored in the data storage unit 190 in a manner mapped to the video signature data without being disclosed to the outside. The video signature ID may also be encrypted and stored. In some embodiments, when the video signature generation unit 150 completes the video signature, the face ID generated at the time of the video signature is transmitted from the face ID generation unit 160 (described later), and the video signature ID and the face ID may be combined and stored after hash processing.

[0102] The video signature information includes, but is not limited to, a contract name, a signing participant's name, a digital signature date, a video size (or capacity), and a signature key, which may be the second public key for decrypting the digital signature of the user terminal 200 during the video signature.

[0103] In this manner, the video signature generation unit 150 according to one embodiment generates a video signature at the time of real-time video contract and reflects and stores the signing process of the user terminal 200 in video in real time, thereby enabling contract participants to check their respective signatures in the form of video after the contract, which is advantageous in preventing repudiation by contract participants.

[0104] In addition, the video signature generation unit 150 primarily receives an electronic signature from the user terminal 200 of the signing participant during the real-time video contract process and verifies the authenticity of the signature, and secondarily combines the video signature ID with a face ID generated during the video signature and stored and managed on the blockchain as described below, and then hash processes and stores the combined ID, thereby preventing spoofing that may occur during the non-face-to-face contract process and advantageously increasing the security and reliability of the video signature.

[0105] The face ID generation unit 160, in conjunction with the contract management unit 140, can generate a face ID corresponding to each contract participant of the plurality of user terminals 200. The face ID generation unit 160 can analyze the video images captured by each of the plurality of user terminals 200 received via the input / output interface module 141 during the real-time video contract, and generate a face ID for each of the plurality of signing participants.

[0106] For example, when generating a video signature at the request of the user terminal 200, the face ID generation unit 160 may generate a face ID by analyzing in real time the user's face included in the video received via the input / output interface module 141. The face ID generation unit 160 may extract facial features of the contract participant photographed by the user terminal 200 using a deep learning model and perform deep learning analysis.

[0107] The face ID generation unit 160 may store a dataset for facial images and input the dataset into a deep learning network for sufficient learning. For example, the deep learning model may use a network algorithm to which various deep learning models are applied, such as an inception module-based convolutional neural network (CNN), a deep neural network (DNN), a recurrent neural network (RNN), a restricted Boltzmann machine, a deep belief network (DBN), or a deep Q-network.

[0108] In addition, the face ID generation unit 160 analyzes in real time the video captured by the user terminal 200 while the user terminal 200 is making a video signature and learns through machine learning, thereby improving the recognition rate when the user terminal 200 uses the generated face ID in the future.

[0109] The Face ID generation unit 160 can issue a non-fungible token (or NFT) on a blockchain for the generated Face ID and store it in a blockchain system (not shown). The blockchain system may be a distributed database composed of multiple blocks. For example, the Face ID generation unit 160 can store the generation of the Face ID and a user authentication transaction using the Face ID on the blockchain.

[0110] In addition, the Face ID generation unit 160 may store metadata for the Face ID NFT. In this case, the Face ID generation unit 160 may store the metadata for the Face ID NFT in the data storage unit 190, but is not limited thereto, and may also store it on-chain or in an Inter Planetary File System (IPFS). Here, the metadata for the Face ID NFT may include a video signature ID of the video signature from which the Face ID was generated, the time of generation, user information of the contract participant used (e.g., the user ID and password of the contract participant, user terminal information), and a document (or contract) ID, which will be described later.

[0111] In addition, when a contract participant who participates in the video signature uses an application program, application, and / or user ID when connecting to a website provided by the system 100, the face ID generation unit 160 can store the user ID as metadata of the face ID.

[0112] As such, the face ID generation unit 160 according to one embodiment generates a face ID for each signing participant at the time of video signing and manages it on a blockchain, thereby verifying and certifying the identity of each contract participant through a distributed ledger (blockchain) that cannot be forged, and allowing each contract participant to check their own face ID information. This has the effect of preventing forgery of face IDs used when accessing future contracts, and allowing the history of accessing contracts using face IDs to be checked on the distributed ledger. In addition, the face ID generation unit 160 recognizes the face of each signing participant and generates a face ID at the time of video signing during the real-time video contract process without a separate face ID generation procedure, thereby advantageously providing convenience to the user terminal 200.

[0113] The media conversion unit 170 can convert the contract created during the real-time video contract into a document file format. For example, if the real-time video contract process is interrupted or terminated, or if at least one contract participant delegated their contract authority during the real-time video contract, the media conversion unit 170 can add a power of attorney created via the system 100 to the document file.

[0114] The contract may include at least one video signature, which may be provided as a captured screen and implemented as a hyperlink so that the video signature file is played when the user terminal 200 clicks on the video signature.

[0115] When converting the contract created during the real-time video contract into a document file, the media conversion unit 170 can issue a document ID. Here, the document ID is an ID unique to the contract and can be encrypted and stored. The media conversion unit 170 can provide the contract and the document ID to the electronic document management unit 180.

[0116] In addition, the media conversion unit 170 may generate an identification code for the contract created when subscribing to the real-time video and input it into the document file of the contract. The identification code may be an identification code obtained by encrypting the document ID and at least one video signature ID and / or face ID created when subscribing to the real-time video. The identification code may be realized by a QR code (registered trademark), a barcode, etc.

[0117] The electronic document management unit 180 can map the contract in file format and the document ID with the video signature ID of at least one video signature generated at the time of the contract and at least one face ID, and store them in the data storage unit 190.

[0118] In another embodiment, the electronic document management unit 180 may store the contract in the form of an NFT on the blockchain in a blockchain system. In this case, the electronic document management unit 180 may store at least one video signature ID, at least one face ID, and / or a user ID associated with the contract as metadata for the NFT of the contract.

[0119] When any user terminal 200 connects using an application program, application, and / or website provided by the system 100 through a user ID or a face ID used in a previous contract, the electronic document management unit 180 can provide the user terminal 200 with a template list including at least one contract that is mapped and stored with the user ID and / or the face ID, or that includes the user ID and / or the face ID as metadata.

[0120] The data storage unit 190 can store data (e.g., user information) generated by other components of the video signature live contract system 100 or received from the user terminal 200. The data storage unit 190 can be realized to structure the stored data for efficient processing.

[0121] As described above, when providing a real-time video contract service, the video signature live contract system 100 according to an embodiment records the real-time video contract process on video and provides a video signature function, a video signature encryption function, and a face ID generation function when signing the video. This prevents spoofing that may occur during the non-face-to-face contract process and prevents future contract repudiation by contract participants. Therefore, it is advantageous in ensuring the reliability and security of contracts compared to face-to-face contracts as well as non-face-to-face contracts using existing electronic documents and electronic signatures.

[0122] In addition, the video signature live contract system 100 according to one embodiment is advantageous in preventing forgery of contract documents and increasing the security of contracts by enabling the video signature, face ID, and documents generated during the real-time video contract process to be managed separately on encryption and / or blockchain.

[0123] FIG. 5 is a flowchart illustrating a video signature live contract method of a video signature live contract system according to an embodiment of the present invention.

[0124] 1 to 5, the video signature live contract system 100 can perform user authentication in response to a request from the first user terminal 200_1 (S100).

[0125] When the first user terminal 200_1 runs an application program and application provided by the system 100 or connects via a website, the system 100 can request personal authentication data from the first user terminal 200_1.

[0126] For example, the personal authentication data may be a user ID and a password registered by the first user terminal 200_1 when the first user terminal 200_1 subscribes to a service provided by the system 100. As another example, if the first user terminal 200_1 has previously subscribed to a real-time video contract and a video signature through the system 100, the personal authentication data may be a face ID of the user who owns the first user terminal 200_1, which is generated by the face ID generation unit 160 at the time of the video signature.

[0127] When the system 100 receives the personal authentication data from the first user terminal 200_1, it can be considered that the first user terminal 200_1 has requested user authentication, so that the personal authentication unit 120 can perform user authentication based on the data received from the first user terminal 200_1.

[0128] The identity verification unit 120 may verify whether identity authentication data received from the first user terminal 200_1 matches pre-stored identity authentication data in response to a request from the management unit 110. The pre-stored identity authentication data may include a user ID and a password registered when the first user terminal 200_1 subscribes to a service provided by the system 100, and a face ID generated by the face ID generation unit 160.

[0129] Thereafter, the system 100 can provide a real-time contract screen to the first user terminal 200_1 (S200).

[0130] For example, the input / output interface module 141 of the contract management unit 140 can interface with multiple user terminals 200 via application programs, applications, and / or websites provided by the system 100. The input / output interface module 141 can provide a real-time video contract screen to the user terminals 200.

[0131] The real-time video subscription screen provided by the input / output interface module 141 to the user terminal 200 may include multiple user interfaces (UIs). When the user terminal 200 selects (or clicks) one of the multiple user interfaces, the input / output interface module 141 may transmit data to or request other components of the system 100 to provide a corresponding screen or function. The multiple user interfaces may also include a UI that provides a participant invitation function.

[0132] Next, the system 100 can invite at least one contract participant in response to a request from the first user terminal 200_1 (S300).

[0133] The first user terminal 200_1 may request a contract participant invitation from the system 100. For example, the first user terminal 200_1 may request a contract participant invitation from the system 100 via a UI that provides the participant invitation function included in the real-time video contract screen.

[0134] The participant invitation module 142 may provide a contract participant invitation function to the first user terminal 200_1. As a specific example, the participant invitation module 142 may interface with the input / output interface module 141 to provide a pop-up screen for providing the contract participant invitation function to the first user terminal 200_1, as shown in FIG. 8. In this case, the participant invitation module 142 may interface with a contact, email, and / or messenger application of the user terminal 200 via the input / output interface module 141 to provide the contract participant invitation function to the user terminal 200.

[0135] The participant invitation module 142 can receive from the first user terminal 200_1 either the email address or the phone number of the contract participant to be invited, and information on the type of contract participant (e.g., type such as signing participant, observer, agent, and notary public).

[0136] The participant inviting module 142 may send an invitation link for participating in a video signature live contract to the second user terminal 200_2 in response to a request from the first user terminal 200_1. When providing the invitation link to the invited second user terminal 200_2, the participant inviting module 142 may further provide information such as, but not limited to, the inviter, information about the contract (e.g., the contract name), and the contract participant type.

[0137] Here, the invitation link may be a link connecting to a contract created by the first user terminal 200_1 that invited the user via an application program, application, and / or website provided by the system 100. The invitation link may be provided in various forms such as an icon, text, etc.

[0138] The participant inviting module 142 may send an email containing the invitation link to the email account of the invited contract participant, or may send a text message (SMS) containing the invitation link to the second user terminal 200_2 of the invited contract participant, and / or may send a message containing the invitation link via the messenger application. In addition, if an application program or application provided by the video signature live contract system 100 is installed in the second user terminal 200_2 of the invited contract participant, the participant inviting module 142 may send a notification pop-up containing the invitation link to the second user terminal 200_2.

[0139] Thereby, the at least one contract participant can participate in the real-time video contract provided by the system 100 by using the second user terminal 200_2 owned by the participant.

[0140] Then, the system 100 can check whether or not there is an existing contract (S400).

[0141] The template management unit 130 can check whether or not there is a contract already concluded between the user who owns the first user terminal 200_1 and the invited contract participant. Here, the existing contract may be a real-time video contract concluded by the first user terminal 200_1, or a real-time video contract that is saved in a state where video recording is stopped while a real-time video contract is in progress between the owner of the first user terminal 200_1 and the owner of the second user terminal 200_2, but is not limited thereto.

[0142] If there is no pre-contract, the system 100 may provide a template list to the first user terminal 200_1 (S510). The template list may include a list of various types of contract templates stored and managed by the template management unit 130 and a list of templates pre-generated by the first user terminal 200_1. The pre-generated template list may include a contract generated by the first user terminal 200_1 via the template management unit 130 before the real-time video contract is started.

[0143] In this case, the system 100 can receive a selection from the first user terminal 200_1 for one of the templates in the list, and provide the selected contract template to the multiple user terminals 200 participating in the real-time video contract.

[0144] Conversely, if the existing contract exists, the system 100 can provide a contract template for the existing contract to the multiple user terminals 200 participating in the real-time video contract (S520).

[0145] The system 100 can then start and stop recording the real-time video subscription (S600, S700).

[0146] For example, the video recording module 145 can record a real-time video contract process in conjunction with the input / output interface module 141. The video recording module 145 can start, stop, and end video recording in response to a request from the user terminal 200 of the host. The video recording module 145 can record the video recording time excluding the video recording stop period.

[0147] During the real-time video contract recording process, the system 100 can provide real-time video contract and video signature services to a plurality of user terminals 200. A method of providing real-time video contract and video signature services by the system 100 will be described in detail with reference to FIG.

[0148] 5 illustrates an example in which step S300, in which the system 100 invites another contract participant in response to a request from the first user terminal 200_1, is performed before step S600, in which the system 100 starts recording the real-time video contract, but this is not limiting. For example, the first user terminal 200_1 may invite at least one other contract participant through the system 100 between step S600, in which the system 100 starts recording the real-time video contract, and step S700, in which the system 100 ends recording the real-time video contract.

[0149] The system 100 may also generate and manage log data and text data between step S600 of starting recording for the real-time video subscription and step S700 of ending recording for the real-time video subscription. Here, the text data may be data obtained by interpreting and converting voice data received from a plurality of user terminals 200 into text during the real-time video subscription.

[0150] Specifically, the log generation module 143 can generate and manage the activity records of each of the multiple user terminals 200 during the real-time video subscription process, i.e., the start (e.g., start of video recording), stop, and completion (e.g., end of video recording) of the real-time video subscription, as log data, as shown in FIG. 10.

[0151] Here, the activity record of each of the plurality of user terminals 200 may include, but is not limited to, the time of invitation, the time of participation, the time of inputting information into an input field for each participant, the time of starting and completing video signature, the time of delegating authority, the time of delegation approval, and the time of accepting authority for each of the plurality of user terminals 200. The activity record means a record of interactions between the plurality of user terminals 200 and the system 100 during the real-time video contract process.

[0152] The log generating module 143 can list any real-time video subscription process in chronological order and provide it to each of the multiple user terminals 200 in real time.

[0153] In addition, the STT module 146 can receive voice data of multiple contract participants from multiple user terminals 200 during the real-time video contract process in conjunction with the input / output interface module 141, interpret the voice data, and convert it into text data. The STT module 146 can separate the voice data of each of the multiple contract participants and convert it into text data.

[0154] The STT module 146 may, in conjunction with the video recording module 145, display the converted text data in synchronization with the recorded video contract video. In this case, the converted text data may be displayed on the recorded video contract video, but is not limited to this. As another example, the converted text data may be provided as a separate recording video from the recorded video contract video.

[0155] In some embodiments, the STT module 146 can generate the converted text data as a document file, and the converted text data can be displayed along with the time at which the audio data was received from the plurality of user terminals 200.

[0156] Finally, the system 100 can store a copy of the contract created in the real-time video contract process and provide it to a plurality of user terminals 200 (S800).

[0157] When the real-time video contract process is interrupted or terminated, the media conversion unit 170 may convert the contract created during the real-time video contract into a document file format. For example, the media conversion unit 170 may convert and save the contract into a PDF file format, as illustrated in FIG. 11.

[0158] If at least one contract participant delegates their contract authority during the real-time video contract, the media conversion unit 170 can add the power of attorney created through the system 100 to the document file.

[0159] The contract may include at least one video signature, which may be provided as a captured screen and implemented as a hyperlink so that the video signature file is played when the user terminal 200 clicks on the video signature.

[0160] When converting the contract created during the real-time video contract into a document file, the media conversion unit 170 can issue a document ID. Here, the document ID is identification data of the contract and can be encrypted and stored. The media conversion unit 170 can provide the contract and the document ID to the electronic document management unit 180.

[0161] In addition, the media conversion unit 170 may generate an identification code (B in FIG. 11) for the contract created when subscribing to the real-time video and input it into the document file of the contract. The identification code may be an identification code obtained by encrypting the document ID, at least one video signature ID and / or face ID created when subscribing to the real-time video. The identification code may be realized as a QR code (registered trademark), a barcode, etc.

[0162] The electronic document management unit 180 can map the contract in file format and the document ID with the video signature ID of at least one video signature generated at the time of the contract and at least one face ID, and store them in the data storage unit 190.

[0163] In another embodiment, the electronic document management unit 180 may store the contract in the form of an NFT on the blockchain in a blockchain system. In this case, the electronic document management unit 180 may store at least one video signature ID, at least one face ID, and / or a user ID associated with the contract as metadata for the NFT of the contract.

[0164] In addition, when any of the real-time video contracts is completed, the log generation module 143 can manage and store multiple log data generated during any of the real-time video contracts in conjunction with the recorded video and / or the contract.

[0165] 6 is a flowchart illustrating a method for providing a real-time video contract and a video signature service in a video signature live contract system according to an embodiment of the present invention. FIG. 9 is an exemplary view showing a screen in which a video signature live contract system according to an embodiment of the present invention provides a real-time video contract service to a user terminal.

[0166] 6 and 9, the system 100 can provide a contract participant list (PL) to a plurality of user terminals 200 and display input fields IF1 and IF2 for each contract participant (S610).

[0167] For example, the template management unit 130 may classify and designate input fields for each contract participant on each contract. As a specific example, each contract includes a plurality of input fields that must be filled in by the contract participants, and the template management unit 130 may classify and designate input fields that must be filled in during the contract process based on the type information of the contract participants received from the first user terminal 200_1 in step S300 of inviting at least one contract inviter.

[0168] The template management unit 130 may display input fields classified according to the classified input fields for each contract participant when providing multiple input fields on a contract being created during the contract process to multiple user terminals 200. For example, when the system 100 displays a contract on each user terminal 200, the template management unit 130 may display input fields classified according to the contract participant using each user terminal 200 differently from other input fields.

[0169] As a specific example, the template management unit 130 can display the input fields classified as contract participants in a different color from other input fields, or can highlight them using a box UI (User Interface).

[0170] In FIG. 9, among multiple contract participants who participated in a real-time video contract, the signing participants include “Hong Gil Dong” who uses the first user terminal 200_1 and “ABC” who uses the second user terminal 200_2, and the template management unit 130 classifies the input authority of each of the first input field IF1 and the second input field IF2 into “Hong Gil Dong” and “ABC”, respectively.

[0171] 9, the template management unit 130 can display information about contract participants (e.g., names) who have input authority for each input field IF1, IF2 in the form of a flag on one side of each input field IF1, IF2. This allows each of the multiple contract participants to use their own user terminal 200 to input data into the input field classified and designated for them.

[0172] In some embodiments, the template management unit 130 can also set input fields other than those classified as contract participants so that the user terminal 200 of the contract participant cannot input data.

[0173] In addition, the template management unit 130 can generate a plurality of contract participant lists (PL) on one side of the contract displayed on the user terminal 200, and display the number of input items classified for each contract participant and the number of input items together with the contract participant lists. In this case, the template management unit 130 can also provide a function that allows the user terminal 200 to move to the input items classified corresponding to the contract participant when the user terminal 200 selects one of the contract participant lists.

[0174] Then, the system 100 can provide a signature pop-up window to the user terminal 200 of the signing participant (S620).

[0175] When the system 100 receives a video signature request from a user terminal 200 carried by any signing participant, the system 100 can provide a signature pop-up window to the user terminal 200 .

[0176] Specifically, when a signing participant requests video signature generation during a real-time video contract via the user terminal 200, the video signature generation unit 150 can provide the user terminal 200 with a video signature generation function using a plurality of data received via the input / output interface module 141. Here, the video signature generation request of the user terminal 200 is generated by the user terminal 200 selecting any of the user interfaces (UIs) provided on the screen displayed via the display module 230 of the user terminal 200, but is not limited thereto.

[0177] The video signature generation unit 150 can receive an image captured by the camera module 220 of the user terminal 200 from the input / output interface module 141 and record the captured image. In addition, the video signature generation unit 150 can provide a signature pop-up window for signing to the user terminal 200 via the input / output interface module 141.

[0178] Thereafter, the system 100 can receive signature data from the user terminal 200 that requested the video signature (S630).

[0179] The signature data may be data received from the user terminal 200 via the signature pop-up window. The signing participant may enter an electronic handwritten signature or a seal image into the pop-up window using the user terminal 200, or may sign using a public personal authentication service or a private personal authentication service (e.g., Kakao Pay authentication, PASS app authentication, BankSign, etc.).

[0180] In this process, the video signature generator 150 can share a public key, which is a pair of the private key used for the digital signature, with the user terminal 200 and verify whether the digital signature is valid using the public key. The private key and the public key are generated for each digital signature of the user terminal 200, and may be a key pair valid only for that digital signature.

[0181] For example, the user terminal 200 can hash the signature data generated in the video signature process, encrypt the hashed digest with the private key, and then transmit the signature data and the digital signature to the video signature generation unit 150. In this case, the video signature generation unit 150 can decrypt the digital signature with the public key, hash the signature data, and compare the hashed digest with the data (digest) decrypted with the public key for verification.

[0182] However, the electronic signature, encryption, and decryption methods of the user terminal 200 and the video signature generation unit 150 are not limited to this, and any electronic signature, encryption, and decryption method that is capable of authenticating the user and message, such as an electronic signature using a public key and a symmetric key, and that ensures confidentiality, can be applied.

[0183] In addition, when the user terminal 200 signs through the signature pop-up window, the video signature generation unit 150 can receive the signature process in real time through the input / output interface module 141 and record the signature process so as to display it on the video signature screen. In addition, when the user terminal 200 completes signing in the pop-up window, the video signature generation unit 150 can display signature information, including the names of signing participants and the time when the signature was completed, on the video signature screen.

[0184] The system 100 can then store the video signature data and generate and store a video signature ID and a face ID (S640).

[0185] When generating a video signature at the request of the user terminal 200, the face ID generation unit 160 may generate a face ID by analyzing in real time the video received through the input / output interface module 141. The face ID generation unit 160 may extract facial features of the contract participant photographed by the user terminal 200 using a deep learning model and perform deep learning analysis.

[0186] The face ID generation unit 160 may store a dataset for facial images and input the dataset into a deep learning network for sufficient learning. For example, the deep learning model may use a network algorithm to which various deep learning models are applied, such as an inception module-based convolutional neural network (CNN), a deep neural network (DNN), a recurrent neural network (RNN), a restricted Boltzmann machine, a deep belief network (DBN), or a deep Q-network.

[0187] The Face ID generation unit 160 analyzes in real time the video captured by the user terminal 200 while making a video signature and learns through machine learning, thereby improving the recognition rate when the user terminal 200 uses the generated Face ID in the future.

[0188] The Face ID generation unit 160 may store the generated Face ID in a blockchain system (not shown) in the form of a non-fungible token (or NFT) on the blockchain. The blockchain system may be a distributed database composed of multiple blocks. For example, the Face ID generation unit 160 may store the generation of the Face ID and a user authentication transaction using the Face ID on the blockchain.

[0189] In addition, the Face ID generation unit 160 may store metadata for the Face ID NFT. In this case, the Face ID generation unit 160 may store the metadata for the Face ID NFT in the data storage unit 190, but is not limited thereto, and may also store it on-chain or in an IPFS (Inter Planetary File System). Here, the metadata for the Face ID NFT may include a video signature ID of the video signature from which the Face ID was generated, the time of generation, user information of the contract participant used, and a document (or contract) ID, which will be described later.

[0190] Furthermore, when the user terminal 200 completes the video signature, the video signature generation unit 150 can encrypt the video signature data and store it in the data storage unit 190, and generate a video signature ID and video signature information for the video signature.

[0191] The video signature ID is data for identifying each video signature, and the video signature ID is not disclosed to the outside and can be stored in a manner mapped with the corresponding video signature data in the data storage unit 190. Also, the video signature ID can be encrypted and stored.

[0192] In some embodiments, when the video signature is completed, the video signature generation unit 150 receives the face ID generated during the video signature from the face ID generation unit 160, and can combine the video signature ID and the face ID and store them after hash processing.

[0193] The video signature information includes, but is not limited to, the contract name, the name of the signing participant, the date of the electronic signature, the video size (or volume), and the signature key, which may be the second public key for decrypting the electronic signature of the user terminal 200 during the video signature.

[0194] As described with reference to FIG. 6, the system 100 provides a video signature service to each user terminal 200 of the signing participants among the contract participants, and can end video recording in response to a request to end recording from the first user terminal 200_1 held by the facilitator among the contract participants (S700).

[0195] As described above, when providing a video signature live contract method and real-time video contract service of the video signature live contract system 100 according to an embodiment, the real-time video contract process is recorded on video and a video signature function, a video signature encryption function, and a face ID generation function at the time of video signing are provided, thereby preventing spoofing that may occur during the non-face-to-face contract process and preventing future contract repudiation by contract participants. Therefore, it is advantageous in ensuring the reliability and security of contracts compared to face-to-face contracts as well as existing non-face-to-face contracts using electronic documents and electronic signatures.

[0196] In addition, during the time video contract process, first, an electronic signature is received from the user terminal 200 of the signing participant to verify the authenticity of the signature, and second, the video signature ID is combined with a face ID generated at the time of the video signature and stored and managed on the blockchain, and then hashed and stored, thereby preventing spoofing that may occur during the non-face-to-face contract process and advantageously increasing the security and reliability of the video signature.

[0197] Although not described in detail in FIG. 6, the method for providing real-time video contract and video signature service of the video signature live contract system 100 may further include a step of providing an authority delegation function to multiple user terminals 200.

[0198] For example, the authority management module 144 may provide a contract participant authority delegation function to the user terminal 200. For example, any contract participant may delegate his / her contract authority through the authority management module 144. Here, the contract authority includes, but is not limited to, the authority of the contract participant to sign when making a real-time video contract through the system 100 and the authority to input information into an input field classified for the contract participant.

[0199] When the authority management module 144 receives an authority delegation request from the user terminal 200 via the input / output interface module 141, the authority management module 144 may provide a power of attorney form to the user terminal 200. For example, the authority management module 144 may provide the power of attorney form to the user terminal 200 via the input / output interface module 141 in the form of a pop-up window, but is not limited thereto, and may provide the power of attorney form in various forms.

[0200] The power of attorney form includes information about the principal, including the contract name, the principal's signature, and contact information, and the information about the principal's signature and the authorized agent can be provided in the input field. The information about the authorized agent includes, but is not limited to, the name, relationship to the principal, email address, phone number, and ID card image.

[0201] If the user terminal 200 attaches an image file of the agent's ID card on the power of attorney form, the authority management module 144 can provide the image of the agent's ID card to the identity verification unit 120 and request verification of the authenticity of the ID card.

[0202] When the authority management module 144 receives a request for the principal's signature on the power of attorney form from the user terminal 200 (e.g., when the user terminal 200 clicks on the power of attorney signature field), the authority management module 144 may further provide a signature pop-up window in which the principal can sign via the user terminal 200. In this case, the principal may, but is not limited to, provide a video signature via the user terminal 200. In some embodiments, the principal may use the user terminal 200 to provide an electronic handwritten signature (or drawing signature), or may sign using a public personal authentication service or a private personal authentication service (e.g., Kakao Pay authentication, PASS app authentication, BankSign, etc.).

[0203] The authority management module 144 may transmit a delegation approval request to the user terminal 200 of the contract participant other than the delegator who delegated the contract authority. For example, when the delegator completes the creation of the power of attorney, the authority management module 144 may transmit a delegation approval request to the user terminal 200 of the signing participant and facilitator other than the delegator. The delegation approval request may be provided in the form of a notification pop-up to the user terminal 200 of the signing participant and facilitator other than the delegator, but is not limited thereto.

[0204] The authority management module 144 may send a contract invitation request to the agent to the participant invitation module 142. For example, the management authority module 144 may send the phone number or email address entered in the letter of attorney along with the contract invitation request to the participant invitation module 142. As a result, the participant invitation module 142 may send an email, message, and / or notification pop-up including an invitation link to the user terminal 200 of the agent. In this case, the participant invitation module 142 may provide authority delegation information along with the invitation link to the user terminal 200 of the agent. The authority delegation information may include the name of the contract delegated by the delegator, the authority, the delegation date, etc.

[0205] In some embodiments, the authority management module 144 may classify a delegator who has delegated his / her contract authority as a visitor, but is not limited to this. In addition, the authority management module 144 may grant and withdraw contract authority of a contract participant in response to a request from the user terminal 200 of the facilitator among the contract participants.

[0206] In this way, the authority management module 144 provides a contract authority delegation function for non-face-to-face contracts on the system 100, and by storing and managing authority delegation information, it can make the tedious delegation confirmation process between contract participants more convenient and is advantageous for later confirmation of whether the delegation was made legally.

[0207] 7 is a flowchart illustrating a method for providing video contract video data to a user terminal in a video signature live contract system according to an embodiment of the present invention. FIG. 11 is an example view showing a screen in which a contract created at the time of real-time video contract is converted into a document form in a video signature live contract system according to an embodiment of the present invention.

[0208] Referring to FIG. 7, first, the system 100 may receive a service connection request from the user terminal 200 (S910).

[0209] A written contract (e.g., the contract illustrated in FIG. 11) generated through real-time video contracting can be stored in the user terminal 200 or output in physical form. The user terminal 200 can recognize (or scan) an identification code (B in FIG. 11) on the stored or output contract and connect to an application, application, and / or website provided by the system 100.

[0210] When the user terminal 200 recognizes the identification code (B in FIG. 11), the system 100 can consider that the user terminal 200 has requested a service connection. In addition, the system 100 can receive the identification code (B in FIG. 11) from the user terminal 200, decode the identification code, and confirm the corresponding document ID, video signature ID, and / or face ID.

[0211] Thereafter, the system 100 may request the user terminal 200 to perform personal authentication (S920) and receive personal authentication data from the user terminal 200 (S930).

[0212] For example, the system 100 may request authentication on the application, application, and / or website to which the user terminal 200 has connected by recognizing the identification code (B in FIG. 11). The authentication request from the system 100 to the user terminal 200 may be provided in the form of a pop-up window, but is not limited thereto.

[0213] The user terminal 200 may transmit personal authentication data to the system 100 in response to a personal authentication request from the system 100. Here, the personal authentication data may be a face ID generated during a real-time video contract process for the contract.

[0214] In another embodiment, the personal authentication data may include the user ID and password registered by the user terminal 200 when signing up for a service provided by the system 100, and / or the public personal authentication service and private personal authentication service used when signing an electronic signature.

[0215] Next, the system 100 can check whether the identification code corresponds to the authentication data (S940).

[0216] Specifically, the identity verification unit 120 can perform user authentication based on data received from the user terminal 200. For example, the identity verification unit 120 can verify whether the data received from the user terminal 200 matches the user information of the user using the user terminal 200 (for example, the user ID and password of the contract participant, and / or user terminal information).

[0217] In addition, the identity verification unit 120 can verify whether the identity authentication data received from the user terminal 200 corresponds to the identification code. For example, the identity verification unit 120 can receive facial image data of the user from the user terminal 200 and verify whether the facial image data matches a face ID stored in correspondence with the identification code.

[0218] If the personal authentication data received from the user terminal 200 corresponds to the personal authentication data corresponding to the identification code, the system 100 can provide the video subscription video data to the user terminal 200 (S950).

[0219] For example, the system 100 may provide the user terminal 200 with video subscription video data of a real-time video subscription recorded in response to the identification code via the application, application and / or website.

[0220] If the personal authentication data received from the user terminal 200 does not correspond to the personal authentication data corresponding to the identification code, the system 100 may request authorization confirmation from the user terminal 200 (S960).

[0221] For example, the system 100 may send a message in the form of a notification pop-up to the user terminal 200 informing the user that the user does not have the right to access the video contract video data recorded corresponding to the identification code. However, the system 100 may request the user terminal 200 to confirm the right in various ways.

[0222] In this case, in some embodiments, the system 100 can provide a message in various forms to each user terminal 200 of the contract participants who have access to the video contract video data, informing them of an unauthorized user's attempt to access the video contract video data.

[0223] In addition, when the user terminal 200 clicks on the video signature area (A in FIG. 11) on the contract after connecting to the service, the system 100 can provide video signature data to the user terminal 200. For example, the system 100 can provide the video signature data to the user terminal 200 in the form of a pop-up, and as shown in FIG. 12, the user terminal 200 can play the video signature to check the signing process of the contract participants in a video. In addition, the user terminal 200 can check the video signature information along with the video signature data.

[0224] The present invention has been described in detail above, focusing on preferred embodiments shown in the drawings. These embodiments are merely illustrative and should not be considered as limiting the present invention, and should be considered from an explanatory perspective, not a restrictive one. The true technical scope of protection of the present invention should be determined by the technical spirit of the appended claims, rather than the foregoing description. Although specific terms are used in this specification, they are used merely to explain the concept of the present invention and are not used to limit the meaning or the scope of the present invention as described in the claims. Each step of the present invention does not necessarily have to be performed in the exact order described, but can be performed in parallel, alternatively, or separately. Those skilled in the art to which the present invention pertains will understand that various modifications and other equivalent embodiments are possible without departing from the essential technical spirit of the present invention as described in the claims. Equivalents should be understood to include not only currently known equivalents but also equivalents developed in the future, i.e., all elements invented to perform the same function, regardless of structural relationship.

Claims

1. an identity verification unit that receives an ID card image from the user terminal and verifies the authenticity of the ID card; a contract management unit for providing a real-time video contract screen to the user terminal and recording the real-time video contract; a video signature generation unit that generates a video signature using the video captured by the user terminal and signature data received from the user terminal; and a Face ID generation unit that generates a Face ID using the video captured by the user terminal in the video signature generation process, issues a non-fungible token for the generated Face ID, and stores and manages it on a blockchain; Including, The video signature live contract system is characterized in that the video signature is displayed as a video taken by the user terminal and the signature data generation process.

2. The video signature generation unit Displaying signature information including the name of the signing participant who generated the signature data and the time of signature completion on the video signature screen; The video signature live contract system of claim 1 , wherein the video signature generating unit generates a video signature ID, which is identification information for the video signature.

3. The video signature generation unit The encryption and decryption process for the signature data is performed in conjunction with the user terminal, and a signature key required for the decryption process is shared from the user terminal; 2. The video signature live contract system of claim 1, wherein video signature information for the video signature is generated, and the video signature information includes a contract name of the real-time video contract, a generation date of the signature data, and the signature key.

4. The system further includes a media conversion unit that converts a contract created when making a real-time video contract into a document file format, saves the converted contract, and issues a document ID that is identification information for the contract. The video signature live contract system of claim 2, wherein the document ID is stored in a manner mapped with the video signature ID and the face ID generated at the time of the real-time video contract.

5. the media conversion unit generates an identification code for the contract and inputs it into the document file of the contract; 5. The video signature live contract system according to claim 4, wherein the identification code is data obtained by encrypting the document ID, the video signature ID, and the face ID.

6. The face ID generation unit stores metadata for the non-fungible token of the face ID; 5. The video signature live contract system according to claim 4, wherein the metadata includes the video signature ID, the document ID, and user information of the user who possesses the user terminal.

7. The contract management unit a log generation module that generates and manages the real-time video subscription process and the activity record of the user terminal during the real-time video subscription process as log data; and 2. The video signature live contract system according to claim 1, further comprising an STT module that interprets voice data received from the user terminal during the real-time video contract process and converts the voice data into text data.

8. A video signature live contract method in which a system provides real-time video contract and video signature services to a plurality of user terminals, comprising: the system performing user authentication in response to a request from a first user terminal held by the contract facilitator among the plurality of user terminals; the system sending an invitation link to a second user terminal different from the first user terminal in response to a request from the first user terminal; the system providing a real-time video contract screen to the plurality of user terminals; The system providing a video signature function to at least one of the plurality of user terminals; and The system generates a video signature and a face ID for each contract participant who possesses at least one of the user terminals; Including, the system generates a video signature using video captured by the at least one user terminal and signature data received from the at least one user terminal; The video signature live contract method is characterized in that the system analyzes the user's face contained in the video captured by the user terminal and generates a face ID.

9. The step of the system generating a video signature comprises: displaying signature information including the name of the signing participant who generated the signature data and the time of signature completion on the video signature screen; and generating a video signature ID, which is identification information for the video signature; 9. The video signature live agreement method of claim 8, comprising:

10. a step in which the system receives a plurality of pieces of data including signature data from each of the plurality of user terminals and creates a contract; The system converts and saves the contract created at the time of the real-time video contract into a document file format, and issues a document ID that is identification information of the contract; and The system maps the document ID to the video signature ID generated when subscribing to the real-time video and the face ID, and stores the mapped document ID; 10. The video signature live agreement method of claim 9, further comprising:

11. The system issues a non-fungible token for the FaceID, and stores and manages it on a blockchain; and the system storing metadata for the non-fungible token of the FaceID; further comprising The video signature live contract method of claim 10 , wherein the metadata includes user information of a user terminal on which the video signature ID, the document ID, and the face ID are generated.

12. The system provides a real-time video contract screen to the plurality of user terminals, The system provides a contract template to the plurality of user terminals; and the system displaying a list of multiple contract participants and an input field for each contract participant; 9. The video signature live agreement method of claim 8, comprising:

13. The system generates and manages the real-time video subscription process and the activity records of each of the plurality of user terminals during the real-time video subscription process as log data; and The system interprets and converts voice data received from each of the plurality of user terminals into text data during the real-time video subscription process; 9. The video signature live agreement method of claim 8, further comprising:

14. The system records the real-time video subscription process for the plurality of user terminals and generates video subscription video data; and the system providing the video subscription video data to at least one of the user terminals; 9. The video signature live agreement method of claim 8, further comprising:

15. The step of the system providing the video subscription video data to at least one of the user terminals includes: the system receiving authentication data and an identification code from at least one of the user terminals; and confirming that the personal authentication data corresponds to the identification code; 15. The video signature live agreement method of claim 14, comprising:

Images