Generating, applying, and verifying voice signatures for digital documents.

Abstract

This disclosure relates to a system, a non-temporary computer-readable medium, and a method for generating and applying a voice signature to a digital document based on receiving an audible acknowledgment of the signature. In particular, in one or more embodiments, the disclosed system generates a field prompt voice file containing prompts for the signable fields in the document. Furthermore, in one or more embodiments, the disclosed system receives an audible acknowledgment in response to the field prompt voice file. In some embodiments, based on the audible acknowledgment, the disclosed system generates a voice signature and applies the voice signature to the signable fields of the digital document.

Description

Technical Field

[0001] (Cross - reference to Related Applications) This application claims the priority and benefit of U.S. Patent Application No. 18 / 302,464, filed on April 18, 2023, which is hereby incorporated by reference in its entirety. (Background Art) In recent years, significant improvements have been made to hardware and software platforms for electronic documents. As a result, the popularity of electronic signature systems has increased significantly. Many existing electronic signature systems provide various methods for using electronic signatures within electronic documents without printing and scanning. For example, some existing electronic signature systems require users to adopt an electronic signature by typing the signature using a physical or digital keyboard. Additionally, some existing electronic signature systems require users to use an input device such as a mouse or touch screen to draw a free - hand version of the signature within a frame.

[0002] Existing systems can record electronic signatures using typed input or touch input, but such systems have many problems regarding the accuracy and flexibility of operation. For example, existing systems capture signature information inaccurately. Specifically, existing systems can receive signature input within the area of a frame and can "clip" any input received outside the area of the frame. Thus, many existing systems cannot capture all of the signature and generate an electronic signature with an incomplete result. To avoid this result, users need to provide the signature slowly and carefully, which can also change the appearance of the signature and lead to an inaccurate version of the digital signature.

[0003] Furthermore, existing systems also lack flexibility because many users lack the physical dexterity or visual ability to enter signatures using common digital input devices such as mice, keyboards, trackpads, or touchscreens. For example, users with hand or arm disabilities, individuals unfamiliar with input devices, or individuals with large hands or fingers generally have difficulty with the existing system's options for entering electronic signatures, particularly within a framed area. In another example, visually impaired users are often unable to provide digital signatures because existing systems cannot generate or provide instructions to the signing device on where, how, or even whether the document requires the user's consent. Moreover, able-bodied users may often find themselves in situations where using computing devices in the way required by existing systems is inconvenient, or in some cases, unsafe. The rigid and inflexible approach of existing systems to generating digital signatures makes it impossible to generate signatures in these situations.

[0004] In addition to these, there are further problems and challenges regarding existing digital signature systems. [Overview of the project]

[0005] Embodiments of the present disclosure provide a system, a non-temporary computer-readable medium, and a method for generating a voice signature of a digital document by generating voice prompts for signable fields in the digital document and receiving and interpreting voice responses, thereby solving one or more of the aforementioned or other problems in the art and / or providing advantages. More specifically, in one or more embodiments, the disclosed system generates a field prompt voice file for a digital document based on the signable fields in the digital document. Thus, in some embodiments, the disclosed system provides the field prompt voice file to a client device and receives a voice response via the client device, which includes an audible acknowledgment of the signable fields. Thus, in one or more embodiments, the disclosed system utilizes the voice response to generate a voice signature. In some embodiments, the disclosed system applies the voice signature to the digital document to generate a signed digital document.

[0006] Further features and advantages of one or more embodiments of the present disclosure are outlined in the following description, some of which may become apparent from that description or may be understood through the implementation of such exemplary embodiments. [Brief explanation of the drawing]

[0007] A more detailed description, using the attached drawings, provides one or more embodiments with additional specificities and details, as briefly described below.

[0008] [Figure 1] Figure 1 shows a diagram of an environment in which a voice signature management system can operate according to one or more embodiments.

[0009] [Figure 2] Figure 2 shows a process for providing audio corresponding to a digital document to a client device, according to one or more embodiments.

[0010] [Figure 3] Figure 3 shows a process for generating and applying a voice signature to a digital document according to one or more embodiments.

[0011] [Figure 4] Figure 4 shows the process of modifying a workflow that provides voice signatures for digital documents based on user commands, according to one or more embodiments.

[0012] [Figure 5] Figure 5 shows a process for applying various types of digital signatures to a digital document according to one or more embodiments.

[0013] [Figure 6] Figure 6 shows an exemplary graphical user interface presenting an exemplary signed digital document including a voice signature, according to one or more embodiments.

[0014] [Figure 7] Figure 7 shows a schematic diagram of a voice signature management system according to one or more embodiments.

[0015] [Figure 8] Figure 8 shows a flowchart of a series of actions for generating and applying a voice signature according to one or more embodiments.

[0016] [Figure 9] Figure 9 shows a block diagram of an exemplary computing device for implementing one or more embodiments of the present disclosure. [Modes for carrying out the invention]

[0017] This disclosure describes one or more embodiments of a voice signature management system that generates and applies voice signatures by generating voice prompts for signable fields in a document and interpreting voice utterances in response to those prompts. For example, in one or more embodiments, the voice signature management system generates a document audio file containing field prompt audio files to be played on a client device to request a voice signature. Furthermore, in one or more embodiments, the voice signature management system receives voice responses to various field prompt audio files. Thus, in some embodiments, the voice signature management system interprets and / or verifies the voice responses to identify audible acknowledgments from the voice responses. Based on the audible acknowledgments in the voice responses, in one or more embodiments, the voice signature management system generates a voice signature and applies it to the corresponding audio field in the digital document.

[0018] As described above, in one or more embodiments, the voice signature management system generates field prompt audio files for a digital document (e.g., an audio file corresponding to a digital document containing a signature field). More specifically, in some embodiments, the voice signature management system provides the digital document to an optical character recognition engine and generates text from the digital document. Furthermore, in one or more embodiments, the voice signature management system recognizes the signable fields within the digital document and generates text prompts corresponding to those signable fields. Thus, in some embodiments, the voice signature management system utilizes a text-to-speech engine to generate field prompt audio files corresponding to the digital document for provision to a client device for signing.

[0019] When a document voice file is provided to a client device, in one or more embodiments, the client device plays the document voice file including at least one field prompt voice file. Further, the client device can detect a voice response to the field prompt voice file and provide the voice response to a voice signature management system. In some embodiments, the voice signature management system can interpret the voice response by detecting the content of the utterance from the voice response. For example, the voice signature management system can extract voice utterance information from the voice response and apply it to a digital document. Further, in some embodiments, the voice signature management system determines whether the voice response includes an approval to sign a signable field.

[0020] In response to the determination that the voice response includes an approval to sign a signable field, in one or more embodiments, the voice signature management system generates a voice signature. Further, in one or more embodiments, the voice signature management system provides the voice signature to a third party that calculates a hash for the voice signature. Further, in some embodiments, the third party system verifies the voice signature and returns the voice signature to the voice signature management system. In one or more alternative embodiments, the voice signature management system can hash and verify the voice signature.

[0021] Further, in some embodiments, the voice signature management system verifies the voice signature using biometric data. For example, in one or more embodiments, the voice signature management system identifies biometric data corresponding to a user account associated with the client device. Further, in some embodiments, the voice signature management system authenticates a voice file including an audible approval for signing a signable field based on the biometric data.

[0022] Furthermore, in some embodiments, the voice signature management system generates a signed digital document by applying a voice signature to a digital document. In some embodiments, the voice signature management system embeds signature data into a digital document. For example, the voice signature management system can embed an audio file including voice approval of the voice signature into a digital document. Further, in one or more embodiments, the voice signature management system modifies a digital document using a visual display of the signature and / or an explanation corresponding to the signature.

[0023] Furthermore, in one or more embodiments, the voice signature management system changes the presentation of an audio file corresponding to a digital document based on various user interactions. For example, in some embodiments, the voice signature management system generates a summary of a digital document based on a user request. Further, or alternatively, the voice signature management system can provide a summary based on determining that a user account corresponding to a client device has already signed a similar document. Further, in some embodiments, the voice signature management system can use voice commands to change the playback of an audio file or to check the digital document or signature status.

[0024] Furthermore, in one or more embodiments, the voice signature management system can generate and apply different types of digital signatures to a digital document. For example, when generating a signed digital document including a voice signature, the voice signature management system can provide the signed digital document to an additional client device. The voice signature management system can receive an indication of user input approving a touch screen-based digital signature from the additional client device. The voice signature management system can generate a signed digital document including both a voice signature and a non-voice digital signature. Thus, the voice signature management system can integrate different signature systems to improve flexibility.

[0025] Furthermore, as described above, in one or more embodiments, the voice signature management system receives information about inputtable fields other than the signature within the digital document. For example, the digital document may include inputtable text fields, dropdown menus, multiple-choice questions, and other informational fields. In one or more embodiments, the voice signature management system generates an audio file of the digital document with voice prompts for these additional fields. Thus, the voice signature management system can receive voice responses to these prompts from a client device. In some embodiments, the voice signature management system converts the voice utterance information from these voice responses into text and applies the text to the digital document by inputting the additional fields based on the converted text.

[0026] Voice signature management systems offer numerous advantages and benefits over existing systems and methods. For example, voice signature management systems improve accuracy compared to existing systems. Specifically, by utilizing audio files to prompt audible confirmation of signature fields, voice signature management systems can generate signed digital documents containing verified voice signatures. Furthermore, by embedding audio files containing voice signature confirmation, voice signature management systems can generate and store high-fidelity information corresponding to the signature. In addition, by verifying voice signatures using biometric data corresponding to the voice in the voice response, voice signature management systems offer improved accuracy in verifying signers compared to existing systems.

[0027] In addition, as mentioned above, existing systems rely on input devices and display systems to perform electronic signature processing. The system described herein overcomes these technical limitations by providing a system that receives accurate and secure digital signatures without relying on visually-based input devices and display systems. For example, a voice signature management system can generate a signature by generating a field prompt voice file and providing it to a client device to request a voice signature. By generating a voice signature and associated metadata, the voice signature management system can provide a secure and accurate signature based on voice utterances from the user. Thus, the system offers improved flexibility in various situations, including for users with physical or visual impairments who can still provide voice utterances for signing. Therefore, the voice signature management system can provide signatures in various situations that are not possible with existing signature systems.

[0028] As demonstrated by the preceding discussion, this disclosure utilizes various terms to describe the features and benefits of a voice signature management system. Further details regarding the meaning of such terms are provided here. For example, as used herein, the term “field prompt voice file” refers to a playable audio corresponding to a digital document. In particular, the term field prompt voice file may refer to an audio file that requests a response to a blank field in a digital document. For example, a field prompt voice file may include an audio file that requests information for a blank field in a digital document, an audio file that requests a user's selection to a multiple-choice question in a digital document, an audio file that requests approval for initialing a digital document, and / or an audio file that requests approval for signing a digital document. In connection with this, as used herein, the term “signatureable field” refers to a portion of a digital document designated for signing. In one or more embodiments, a signatureable field is a field in a digital document corresponding to a signature and / or initials.

[0029] Furthermore, as used herein, the term “voice response” refers to the voice received in response to a field prompt voice file. In particular, the term voice response may include a response consisting of a voice utterance from the user that is captured by a client device and sent to a voice signature management system. For example, a voice response may include an audible acknowledgment or an audible denial in response to a field prompt voice file.

[0030] As used herein, the terms “digital signature,” “electronic signature,” or “signature” refer to any distinctive mark intended as a form of identification or authorization in an electronic document. In particular, the term “signature” may include any digital record, digital drawing, dot, line, curve, or image that an individual or entity intends to adopt as a form of identification or authorization. For example, an individual may often choose to adopt their name, title, initials, or alias, or a distinctive graphic entered using a computer input device, as their “signature.”

[0031] In relation to this, as used herein, the term “voice signature” refers to a digital signature associated with audible approval. For example, in one or more embodiments, a voice signature is associated with an authenticated audio clip approving the signature of a particular signable field. In addition, as used herein, the term “non-voice digital signature” refers to any signature that is not approved by voice or voice utterance. For example, a non-voice digital signature may include a signature that is typed, selected with a mouse or trackpad, or drawn on a touchscreen.

[0032] Furthermore, as used herein, the term “authenticated audio clip” means a recording that has been verified in some way. In particular, the term authenticated audio clip may include a recording of an audio response that includes an audible acknowledgment to sign a signable field in a digital document. In addition, in one or more embodiments, the authenticated audio clip may include a recording that has been verified by a third party based on hashing and / or hashing algorithms. Also, in one or more embodiments, the authenticated audio clip may include a recording of audio that has been verified to match biometric data corresponding to a particular user account.

[0033] Furthermore, as used herein, the term “biometric data” refers to biological measurements or physical characteristics used to identify an individual. In particular, the term biometric data may include data corresponding to identifiable components of a human voice. In one or more embodiments, the biometric data includes the analysis of a voice recording from a biometric algorithm. In some embodiments, the biometric data is associated with a user account and / or user device.

[0034] Further details are provided here in relation to explanatory drawings illustrating embodiments and implementation examples of the persona group system. For example, Figure 1 shows a schematic diagram of an exemplary system 100 in which the voice signature management system 106 operates. As shown in Figure 1, system 100 includes a server 102, a network 108, client devices 110a-110n, and a third-party server 114.

[0035] Although System 100 in Figure 1 is depicted as having a specific number of components, System 100 can have any number of additional or alternative components (e.g., any number of servers, client devices, third-party servers, or other components that communicate with the voice signature management system 106 via the network 108). Similarly, while Figure 1 shows a specific arrangement of Server 102, Network 108, Client devices 110a-110n, and Third-Party Server 114, various additional arrangements are possible.

[0036] Server 102, network 108, client devices 110a-110n, and third-party server 114 are connected to each other directly or indirectly (for example, via network 108, which will be discussed in more detail later in relation to Figure 8) so that they can communicate with one another. Furthermore, server 102, client devices 110a-110n, and third-party server 114 include one or more different computing devices (including one or more computing devices which will be discussed in more detail later in relation to Figure 9).

[0037] As described above, system 100 includes server 102. In one or more embodiments, server 102 generates, stores, receives, and / or transmits data including digital data related to digital documents, field prompt audio files, voice responses, and / or digital signatures. In one or more embodiments, server 102 includes a data server. In some implementations, server 102 includes a communication server or a web hosting server.

[0038] In one or more embodiments, the content distribution system 104 manages the distribution of digital content to client devices (e.g., client devices 110a to 110n). For example, in some examples, the content distribution system 104 distributes and / or manages digital documents. In some implementations, the content distribution system 104 distributes digital documents for display or audio presentation via one or more digital platforms accessed by client devices 110a to 110n.

[0039] In one or more embodiments, the third-party server 114 interacts with the voice signature management system 106 on the network 108 via the server 102. For example, in some implementations, the third-party server 114 hosts a digital platform that performs and / or verifies hashes for digital signatures. Furthermore, in some cases, the third-party server 114 interacts with client devices 110a-110n and provides data relating to the voice signature management system 106, including data relating to digital signatures, including voice signatures.

[0040] Furthermore, in one or more embodiments, client devices 110a to 110n include computing devices that access the digital platform and / or display digital content. For example, client devices 110a to 110n include smartphones, tablets, desktop computers, laptop computers, head-mounted display devices, or other electronic devices. Client devices 110a to 110n include one or more applications (e.g., client application 112) that access the digital platform and / or display digital content, including digital documents. For example, in one or more embodiments, client application 112 includes software applications installed on client devices 110a to 110n. In addition, or alternatively, client application 112 includes a web browser or other application that accesses software applications (and supported by the content distribution system 104) hosted on server 102.

[0041] As an example of implementation, in one or more embodiments, the voice signature management system 106 on server 102 supports the voice signature management system 106 on client device 110n. For example, in some cases, the voice signature management system 106 on server 102 identifies a field prompt audio file corresponding to a digital document for audio presentation to client device 110n. The voice signature management system 106 then communicates the field prompt audio file to the client device 110n via server 102. In some embodiments, based on the playback of the field prompt audio file, the voice signature management system 106 on client device 110n receives and transmits an audio response. In some cases, the voice signature management system 106 on client device 110n further receives and displays the digital document or signed digital document.

[0042] The voice signature management system 106 can be implemented entirely or partially by individual elements of the system 100. In fact, Figure 1 shows that the voice signature management system 106 is implemented with respect to the server 102, but different components of the voice signature management system 106 can be implemented by various devices within the system 100. For example, one or more (or all) components of the voice signature management system 106 may be implemented by a different computing device (e.g., one of the client devices 110a-110n) or by a server other than the server 102 hosting the content distribution system 104 (e.g., a third-party server 114). In fact, as shown in Figure 1, the client devices 110a-110n include the voice signature management system 106. In addition, in some embodiments, one or more components of the client devices 110a-110n are implemented on the server 102. For example, in one or more embodiments, the server 102 implements a client application 112 that utilizes voice commands received via telephone communication from one of the client devices 110a-110n. Exemplary components of the voice signature management system 106 are described below with reference to Figure 9.

[0043] As discussed earlier, the voice signature management system 106 can generate document audio, including the generation of field prompt audio files. More specifically, the voice signature management system 106 can generate field prompt audio files using an optical character recognition engine and a text-to-speech conversion engine. Figure 2 shows an exemplary process for generating and providing field prompt audio files to a client device.

[0044] As shown in Figure 2, the voice signature management system 106 receives a digital document 202. In one or more embodiments, the digital document 202 is a PDF file, a Doc file, a Docx file, a TXT file, a JPEG file, or another document containing text. In some embodiments, the digital document 202 includes one or more inputtable fields corresponding to a signature, initials, or other inputtable information. In one or more embodiments, the digital document 202 includes metadata corresponding to the inputtable fields.

[0045] In some embodiments, the voice signature management system 106 receives digital documents 202 from a client device. In addition, or alternatively, the voice signature management system 106 can retrieve digital documents 202 from a database or other repository. Furthermore, in some embodiments, the voice signature management system 106 can receive digital documents 202 from a third-party system based on a request from a client device.

[0046] As shown in Figure 2, in one or more embodiments, the voice signature management system 106 provides a digital document 202 to the optical character recognition engine 204. In one or more embodiments, the voice signature management system 106 uses the optical character recognition engine 204 to generate text from the digital document 202. In some embodiments, the optical character recognition engine 204 scans the digital document 202 and converts it into binary data.

[0047] Therefore, the optical character recognition engine 204 can analyze the digital document 202 by classifying the content from the digital document as either background or text from the digital document 202. Thus, in one or more embodiments, the optical character recognition engine 204 generates text 206 from the digital document 202 by utilizing pattern matching and feature extraction on the portions identified as text. That is, the optical character recognition engine 204 can determine which portions of the digital document 202 contain text, and then identify which characters the text 206 contains from those portions.

[0048] As shown in Figure 2, the voice signature management system 106 provides text 206 to the text-to-speech engine 208. In one or more embodiments, the text-to-speech engine 208 converts the text 206 into a phoneme representation. Furthermore, in some embodiments, the text-to-speech engine 208 converts the phoneme representation into a waveform that can be output as sound. The voice signature management system 106 can save these sounds as document speech 212, more specifically as field prompt speech files.

[0049] In one or more embodiments, the text-to-speech engine 208 generates a field prompt audio file that includes a voice reading of text 206 from the digital document 202. Furthermore, in some embodiments, the text-to-speech engine 208 generates a field prompt audio file that includes voice prompts describing one or more signable fields and / or one or more inputtable fields in the digital document 202. In addition, the field prompt audio file may include requests to approve, deny, or provide information corresponding to the fields in voice utterances.

[0050] In addition, in one or more embodiments, the text-to-speech engine 208 includes a signature field recognition module 210 that identifies signatureable fields and / or inputtable fields within the digital document 202. In some embodiments, the signature field recognition module 210 identifies multiple underscores or other repeating characters from the text 206 as signatureable or inputtable fields. In addition, in one or more embodiments, the signature field recognition module 210 utilizes metadata from the digital document 202 to flag signatureable or inputtable fields.

[0051] In some embodiments, the signable field recognition module 210 also adds text from metadata associated with the signable field to the text 206 in order to generate document audio 212. As described above, the text-to-speech engine 208 can generate field prompt audio files that include voice utterances of approval, denial, or voice requests providing information, corresponding to signable or inputtable fields in the digital document. In one or more embodiments, the voice signature management system 106 uses text from metadata to generate voice requests.

[0052] In addition, or as an alternative, the voice signature management system 106 can automatically select the language of the field prompt voice file. For example, in one or more embodiments, the voice signature management system 106 can use text 206 to select the voice prompt that best matches the context. More specifically, the voice signature management system 106 can use a natural language processing model on the text preceding a signable or inputtable field to determine the best match among a set of voice prompts for approval, denial, or information via voice utterance. For example, the voice signature management system 106 can identify keywords such as "sign" or "signature" to select a prompt requesting approval for a signature. In this example, the voice signature management system 106 can select a voice prompt containing the text, "Based on the above text in this document, do you agree to sign this field?" and insert it as a field prompt voice file where the corresponding field exists in the digital document 202.

[0053] In addition, in one or more embodiments, the voice signature management system 106 may generate field prompt voice files to request a specific language for approving a field. For example, the voice signature management system 106 may generate a field prompt voice file containing voice information that reads aloud, "Please state your name and agree to the above terms." When processing the voice clip provided in the response, the voice signature management system 106 may determine whether the voice response contains both an acceptance and the correct name associated with the user account corresponding to the user device. For example, the voice signature management system 106 may identify text such as "My name is John Smith and I agree to these terms," ​​or "I am John Smith and I agree to the terms," ​​or similar identification information and acceptance.

[0054] In another example, the voice signature management system 106 can use keywords such as “address,” “date,” or “relationship to applicant” to select prompts related to fields where information can be entered. For example, based on the determination that the text “phone number” exists immediately before a field, the voice signature management system 106 can select a voice prompt containing the text “Please provide your phone number” at the location of the corresponding field in the digital document 202.

[0055] In addition, in one or more embodiments, the signable field recognition module 210 can recognize various types of fields. For example, the signable field recognition module 210 can identify dropdown menus and the text associated with different options within the dropdown menus, multiple-choice questions and their associated options, and checkboxes and their associated text. Based on the identification of the dropdown menus and their corresponding options, in one or more embodiments, the voice signature management system 106 generates voice prompts that present the options. For example, the voice signature management system 106 can determine a dropdown menu containing options for months of the year immediately following the text "Current Month" in a digital document. Based on the identification of the options in the dropdown menus and based on pe, the voice signature management system 106 can identify voice prompts corresponding to question types, such as "Please enter the current month."

[0056] In another example, the voice signature management system 106 can generate custom voice prompts based on a multiple-choice question or a dropdown menu selection. For example, the signable field recognition module 210 can incorporate text into a template for a voice prompt. For instance, the signable field recognition module 210 can identify a multiple-choice question with selectable options next to the text "Sign for yourself" and "Sign on behalf of someone else." Based on the signable field recognition module 210's identification of the text next to the selectable options, the voice signature management system 106 can select a multiple-choice voice prompt template, provide the identified information, and generate a custom voice prompt. For example, the voice signature management system 106 can select a multiple-choice template containing the text "Which applies to you?" and then provide the identified options from the digital document 202. In this example, the voice signature management system 106 can generate a custom voice prompt that includes an audio reading of "Which applies to you? Sign for yourself or Sign on behalf of someone else."

[0057] Furthermore, the voice signature management system 106 can generate custom field prompt voice files and / or custom portions of field prompt voice files for various contexts, field types, and selection types. For example, the voice signature management system 106 can use the signatureable field recognition module 210 to identify various field types and various information corresponding to fields. In addition, the voice signature management system 106 can utilize various templates, and these templates can be matched with various keywords or other text identified from digital documents.

[0058] As shown in Figure 2, the voice signature management system 106 can provide a document audio 212, including a field prompt audio file, to a client device 214 for presentation and signing. In one or more embodiments, the voice signature management system 106 provides the client device 214 with instructions to play the field prompt audio file. Although Figure 2 shows a single client device 214, it will be understood that the voice signature management system 106 can provide field prompt audio files to various client devices, including requests from administrator devices and / or client devices.

[0059] As described above, once a field prompt audio file is provided to the client device, the voice signature management system 106 can receive an audio response via the client device. Furthermore, in one or more embodiments, the voice signature management system 106 generates and applies a voice signature based on the received audio response. Figure 3 shows an exemplary process for generating a voice signature and applying the signature to the generated signed digital document.

[0060] As described above, the client device can play a field prompt audio file and detect an audio response. Furthermore, as shown in Figure 3, the client device 302 can perform an operation 308 to receive and provide an audio response. More specifically, in one or more embodiments, the client device 302 detects and records an audio response during and / or after the presentation of the field prompt audio file. Furthermore, the client device 302 provides the audio response to the audio signature management system 106. For example, in one or more embodiments, the client device 302 records an audio clip and sends it to the audio signature management system 106.

[0061] In one or more embodiments, the voice signature management system 106 performs an operation 310 to verify the voice response. For example, the voice signature management system 106 can authenticate the voice response by converting the voice from the voice clip to text using a speech recognition engine. In addition, the voice signature management system 106 can use a natural language processing model to identify approval, rejection, or information from the voice clip.

[0062] Furthermore, in one or more embodiments, the voice signature management system 106 performs an optional step 312 in which it verifies the voice clip using biometric data. More specifically, in some embodiments, the voice signature management system 106 identifies biometric data associated with a user account corresponding to a client device 302. Thus, in one or more embodiments, the voice signature management system 106 compares the voice clip received from the client device 302 with the biometric data to determine whether the voice in the voice clip corresponds to the biometric data.

[0063] More specifically, in one or more embodiments, the biometric data includes data corresponding to identifiable components of a human voice associated with a user account. In one or more embodiments, the voice signature management system 106 generates biometric data by analyzing a voice clip provided by a client device for biometric data collection. Thus, in one or more embodiments, the voice signature management system 106 verifies the biometric data using a biometric algorithm to determine whether the voice in the voice clip has the same identifiable components as the voice associated with the biometric data.

[0064] Upon interpreting and authenticating the voice response, in one or more embodiments, the voice signature management system 106 generates a voice signature using the authenticated voice clip. More specifically, in one or more embodiments, the voice signature management system 106 encrypts the voice signature using a secret encryption key and an encryption algorithm associated with the client device 302.

[0065] As shown in Figure 3, in one or more embodiments, the voice signature management system 106 performs an operation 313 to embed an authenticated audio clip. For example, in some embodiments, after verifying the audio response, the voice signature management system 106 may generate an authenticated audio clip by clipping a portion of the recording that includes an audible acknowledgment of the signature. Thus, in some embodiments, the voice signature management system 106 embeds the authenticated audio clip, including the audible acknowledgment, into the document. For example, the voice signature management system 106 may embed the authenticated audio clip in the metadata of a PDF.

[0066] Furthermore, as shown in Figure 3, in one or more embodiments, the voice signature management system 106 provides the voice signature to a third-party system 306. In some embodiments, the third-party system 306 performs operation 318, which involves calculating a hash for the digital document and verifying the signature. In addition, or alternatively, in one or more embodiments, the voice signature management system 106 performs operation 318. For example, in one or more embodiments, the third-party system 306 decrypts the voice signature using the public encryption key associated with the client device 302. Furthermore, in some embodiments, the third-party system 306 generates a new hash of the same authenticated voice clip using the same hash algorithm that generated the voice signature. Thus, the third-party system 306 can compare its calculation result with the voice signature to verify that the voice signature originated from the client device 302 and has not been tampered with.

[0067] Furthermore, as shown in Figure 3, the voice signature management system 106 can use voice signatures to generate signed digital documents. In one or more embodiments, the voice signature management system 106 applies a visual representation of the voice signature to the digital document. In some embodiments, the voice signature management system 106 applies an icon or text associated with the client device 302 as the visual representation of the voice signature. Furthermore, in one or more embodiments, the voice signature management system 106 includes a display indicating that the signature is a voice signature and / or was received linguistically from the signer.

[0068] Furthermore, in some embodiments, the voice signature management system 106 generates a signed digital document by applying information from the audio clip to inputtable fields within the signed digital document, as shown in operation 314 of Figure 3. As described above, in one or more embodiments, the voice signature management system 106 utilizes natural language processing to identify language information from the authenticated audio clip and convert the language information into text. The voice signature management system 106 can then input the text into the identified inputtable fields.

[0069] As shown in Figure 3, in one or more embodiments, the voice signature management system 106 performs an optional operation 316 to embed signature data into the signed digital document. More specifically, in one or more embodiments, the voice signature management system 106 embeds an authenticated audio clip into the signed digital document. In various embodiments, the voice signature management system 106 can embed the authenticated audio clip into the signed digital document as various audio file types.

[0070] Furthermore, as shown in Figure 3, the voice signature management system 106 can perform an operation 320 that provides a signed digital document containing a voice signature. In one or more embodiments, the voice signature management system 106 returns the signed digital document to the client device 302. Furthermore, in various embodiments, the voice signature management system 106 can also provide the signed digital document to other client devices, which are one or more client devices selected by the client device 302.

[0071] As described above, in one or more embodiments, the voice signature management system 106 can modify the playback of field prompt audio files. Figure 4 shows the process of modifying the playback of field prompt audio files. As shown in Figure 4, in one or more embodiments, the voice signature management system 106 performs an operation 402 that generates audio that reads text from a digital document. As described above with respect to Figure 2, the voice signature management system 106 can use a text-to-speech engine to generate field prompt audio files that read text from a digital document.

[0072] The voice signature management system 106 can also perform an optional operation 404 that utilizes metadata indicating how to read a field. As described above with respect to Figure 2, the voice signature management system 106 can use a signable field recognition module to determine where a signable field is located in a digital document. Furthermore, the voice signature management system 106 can generate a field prompt voice file by adding text from metadata associated with the signable field to text 206. In one or more embodiments, the voice signature management system 106 generates a field prompt voice file that includes a voice utterance of approval, denial, or informational voice request corresponding to a signable or inputtable field in a digital document. More specifically, in one or more embodiments, the voice signature management system 106 generates a voice request using text from metadata.

[0073] As shown in Figure 4, in one or more embodiments, the voice signature management system 106 can perform an operation 406 to summarize a digital document. In one or more embodiments, the voice signature management system 106 can obtain a summary from metadata associated with the digital document. In addition, or alternatively, the voice signature management system 106 can generate a summary using headlines or keywords from the digital document. For example, the voice signature management system 106 can identify headlines or keywords using a natural language processing model.

[0074] Furthermore, in one or more embodiments, the voice signature management system 106 may insert headings or keywords into the summary template. For example, the voice signature management system 106 may generate a summary from a template that reads, "This is a [Type of Agreement] from [Document Creator] related to [List of Headings and Keywords]." In this example, the summary can be read as, "This is a non-disclosure agreement from ABC Company relating to work scheduled to be completed in January 2023."

[0075] Furthermore, as shown in Figure 4, the voice signature management system 106 can perform an optional operation 408 to determine if a user account has previously signed a similar document. For example, in one or more embodiments, the voice signature management system 106 can compare digital documents and their metadata, including the creator or sender of the digital documents. In one or more embodiments, the voice signature management system 106 can determine a percentage of similarity and mark contracts as similar using similarity thresholds such as 75% or 90%.

[0076] In one or more embodiments, when generating a summary of a digital document, the voice signature management system 106 may include references to similar documents from the past. Furthermore, the voice signature management system 106 may include a summary of the differences between similar documents. For example, the voice signature management system 106 may apply a natural language processing model to the differing parts of the documents to identify dissimilar headings or keywords. Thus, in one or more embodiments, the voice signature management system 106 may include different headings and keywords in the summary. For example, the voice signature management system 106 may generate a summary that states, "This document is similar to the ABC Company NDA you signed last month, however, it specifies work to be completed by February 2023."

[0077] In some embodiments, the voice signature management system 106 can provide a summary in response to receiving a voice utterance request from a user requesting a summary. More specifically, before or during playback by the voice signature management system 106, the voice signature management system 106 can receive an audio clip from a client device containing the voice utterance information, "Please summarize the contract," and provide a summary upon request. In addition, or alternatively, the voice signature management system 106 can provide a summary of a digital document in response to determining that the digital document is similar to one or more digital documents already signed by a user account associated with the client device.

[0078] As shown in Figure 4, the voice signature management system 106 can perform operations 410 to pause, play, or modify a digital document using voice commands. In one or more embodiments, the voice signature management system 106 can receive voice commands corresponding to a digital document from a client device 302. In some embodiments, the voice signature management system 106 can modify the playback of a field prompt audio file based on these voice commands. For example, the voice signature management system 106 can pause, play, rewind, fast forward, skip sections, or otherwise modify the playback of a field prompt audio file.

[0079] Furthermore, in one or more embodiments, the voice signature management system 106 can receive voice commands requesting changes to a digital document. In some embodiments, the voice signature management system 106 can insert text from a voice command as a red line, as a comment, or directly into the digital document. In addition, or alternatively, the voice signature management system 106 can identify references to pre-stored clauses within a voice command. Based on these references, the voice signature management system 106 can insert pre-stored clauses into the digital document.

[0080] In one or more embodiments, the voice signature management system 106 can store pre-saved clauses in a database or other repository. In some embodiments, the voice signature management system 106 can associate pre-saved clauses with titles and / or keywords that can be matched with voice commands to search for pre-saved clauses. For example, the voice signature management system 106 may receive a voice command saying, "Insert a severability clause here." Upon receiving this command, the voice signature management system 106 may query the pre-saved clause database for "severability" and insert a clause titled "Severability Clause."

[0081] In one or more embodiments, the voice signature management system 106 can insert clauses or amendments into a contract at locations indicated by voice commands. For example, the voice signature management system 106 can identify insertion locations by identifying keywords using a natural language processing model. For example, the voice signature management system 106 can identify keywords such as "here," "after this section," "before this section," and "beginning of the document." Thus, based on voice commands, the voice signature management system 106 can insert amendments or pre-saved clauses at predetermined locations within a digital document.

[0082] Furthermore, as shown in Figure 4, the voice signature management system 106 can use voice commands to perform operations 411 that generate digital documents. For example, the voice signature management system 106 can convert recorded voice into text for a digital document. In addition, as described above regarding modifications to existing digital documents, the voice signature management system 106 can insert pre-saved clauses into a new document.

[0083] For example, the voice signature management system 106 can receive a voice command saying, "Create a document from my photo license template with weekend fees and copyright transfer clauses, and send it to John Smith." In response, the voice signature management system 106 can generate a photo license agreement that includes the requested weekend fees and copyright transfer clauses. Furthermore, the voice signature management system 106 can send the generated document to the client device associated with John Smith's user account.

[0084] Furthermore, as shown in Figure 4, in one or more embodiments, the voice signature management system 106 can perform an operation 412 that implements a voice command to check the status of a digital document. For example, the voice signature management system 106 can check and report whether a digital document is signed, sent, or viewed.

[0085] For illustrative purposes, in one or more embodiments, the voice signature management system 106 may receive a voice command via a client device, including the question, "Has the contract been signed by everyone?". Based on an analysis of the content of the voice command, the voice signature management system 106 may identify the signatures applied to the digital document associated with the client device corresponding to the user account. For example, the voice signature management system 106 may determine that four out of five signatures on the digital document have been received. The voice signature management system 106 may then generate and provide a voice clip containing the text, "Four out of five signatories have signed your contract. You are still waiting for John Smith's signature." In additional examples, the voice signature management system 106 may receive and provide responses to voice prompts such as, "What is the current status of contract 5?", "Is the lease agreement completed?", and "What are all the documents signed in the last 10 days?". In response to receiving a voice prompt, the voice signature management system 106 may generate a query and then compare it against the signed documents being processed or completed that are associated with the user account.

[0086] In one or more embodiments, the voice signature management system 106 can apply various signature types to digital documents. Figure 5 shows an exemplary process for managing digital documents using voice signatures and non-voice digital signatures. More specifically, as shown in Figure 5, in one or more embodiments, the voice signature management system 106 can generate a voice signature based on the detection of a voice response 504 by a client device 502. Thus, the voice signature management system 106 can generate a document 506 with a voice signature.

[0087] As shown in Figure 5, the voice signature management system 106 can provide a voice-signed document 506 to a client device 508. As also shown in Figure 5, the client device 508 can use its touchscreen to detect a user interaction 510 to sign the voice-signed document 506. Based on the user interaction 510, the voice signature management system 106 can generate a non-voice digital signature and apply it to the voice-signed document 506. Thus, the voice signature management system 106 can generate a document 520 with both a voice signature and a non-voice digital signature.

[0088] In one or more embodiments, the voice signature management system 106 can receive, store, modify, transmit, and / or otherwise manage documents 520 bearing voice signatures and non-voice digital signatures. For example, in one or more embodiments, the voice signature management system 106 can provide documents 520 bearing voice signatures and non-voice digital signatures to additional client devices for additional signing. Thus, the voice signature management system 106 can integrate various signature types into a single digital document.

[0089] As described above, in one or more embodiments, the voice signature management system 106 can generate a signed digital document that includes a visual representation of the voice signature. Figure 6 shows an example of a client device 600 that presents a signed digital document graphical user interface 602. As shown in Figure 6, the signed digital document graphical user interface 602 includes a digital document having fields 604-610.

[0090] More specifically, the voice signature management system 106 can input fields 604-610 within the signed digital document graphical user interface 602. As described above, the voice signature management system 106 can input initial fields such as field 604 and signature fields such as field 610 based on receiving a voice response that includes an audible acknowledgment to add initials to or sign the fields. Furthermore, the voice signature management system 106 can input information from the voice response into inputtable fields such as fields 606-608.

[0091] For example, field 606 contains the text "123 Main Street". Furthermore, field 608 contains the text "Monthly" selected from a dropdown menu. However, as discussed above, the voice signature management system 106 can input various information into various types of fields based on the voice response.

[0092] As shown in Figure 6, the voice signature management system 106 generates a visual representation of the voice signature in field 610. In one or more embodiments, the voice signature management system 106 generates a visual representation of the voice signature based on user settings and / or user selection of representative signatures. In addition, or alternatively, the voice signature management system 106 can generate a visual representation of the voice signature by rendering the user's name associated with the client device 600 in a handwritten cursive-style font.

[0093] As shown in Figure 6, the voice signature management system 106 can generate a voice indication 612. More specifically, as shown in Figure 6, the voice indication 612 contains the text, "This signature was received by voice utterance." However, it will be understood that the voice signature management system 106 can generate an indication that the voice signature was received by voice in various configurations. As shown in Figure 6, the voice signature management system 106 can apply the indication that the voice signature was received by voice to the digital signature and / or near field 610 on the signed digital document.

[0094] Each component 702-712 of the voice signature management system 106 may include software, hardware, or both. For example, components 702-712 may include one or more instructions stored in a computer-readable storage medium and executable by a processor of one or more computing devices, such as client devices or server devices. When executed by one or more processors, the computer-executable instructions of the voice signature management system 106 may cause a computing device to perform the methods described herein. Alternatively, components 702-712 may include hardware, such as a dedicated processing device for performing a particular function or group of functions. Alternatively, components 702-712 of the voice signature management system 106 may include a combination of computer-executable instructions and hardware.

[0095] Furthermore, the components 702-712 of the voice signature management system 106 may be implemented, for example, as one or more operating systems, as one or more standalone applications, as one or more modules of an application, as one or more plug-ins, as one or more library functions or functions that can be called by other applications, and / or as a cloud computing model. Thus, the components 702-712 may be implemented as standalone applications such as desktop or mobile applications. Furthermore, the components 702-712 may be implemented as one or more web-based applications hosted on a remote server. The components 702-712 may also be implemented as a set of applications or “apps” for mobile devices. As shown in Figure 7, the voice signature management system 106 includes a voice file generator 702, a voice presenter 704, an approval engine 706, a speech recognition engine 707, a voice signature generator 708, a signed digital document generator 710, and a data storage manager 712.

[0096] As shown in Figure 7, the computing device 700 includes an audio file generator 702. In one or more embodiments, the audio file generator 702 generates field prompt audio files corresponding to a digital document. In some embodiments, the audio file generator 702 generates audio files using an optical character recognition algorithm, a speech recognition engine, a text-to-speech engine, and / or metadata from the digital document.

[0097] Furthermore, as shown in Figure 7, the computing device 700 includes a voice presenter 704. In one or more embodiments, the voice presenter 704 distributes field prompt audio files to client devices. Furthermore, in one or more embodiments, the voice presenter provides instructions for playback and presentation ordering of audio files.

[0098] Furthermore, as shown in Figure 7, the computing device 700 includes an approval engine 706. In some embodiments, the approval engine 706 receives an audio response. In one or more embodiments, the approval engine 706 captures an authenticated audio clip containing the audio response. The approval engine 706 can analyze the audio response to identify the content of the audio response that approves, denies, or provides information corresponding to fields in the digital document. Furthermore, in some embodiments, the approval engine 706 uses biometric data to authenticate the audio clip.

[0099] Furthermore, as shown in Figure 7, the client device 700 includes a speech recognition engine 707. In one or more embodiments, the speech recognition engine 707 converts an audio file containing the voice response into text. Thus, in some embodiments, the speech signature management system 106 uses the text to generate signatures, apply commands to navigate between documents, and / or generate documents. Therefore, the approval engine 706, the speech signature generator 708, and / or the signed digital document generator 710 can utilize the text from the speech recognition engine 707.

[0100] Furthermore, as shown in Figure 7, the computing device 700 includes a voice signature generator 708. In one or more embodiments, the voice signature generator 708 applies a visual signature to the digital document. In addition, in some embodiments, the voice signature generator 708 embeds an authenticated voice clip corresponding to the voice signature in the digital document. In one or more embodiments, the voice signature generator 708 provides the voice signature to a third-party system for hashing and / or performs hashing to encrypt the voice signature.

[0101] Furthermore, as shown in Figure 7, the computing device 700 includes a signed digital document generator 710. In some embodiments, the signed digital document generator 710 populates fields in a digital document based on voice responses to field prompt audio files. For illustrative purposes, in one or more embodiments, the signed digital document generator 710 applies a visual signature to a digital document that includes an indication that the signature corresponds to a voice utterance of affirmation.

[0102] Furthermore, as shown in Figure 7, the computing device 700 includes a data storage manager 712. The data storage manager 712 holds data for the voice signature management system 106. The data storage manager 712 (for example, via one or more memory devices) holds data of any type, size, or kind as necessary to perform the functions of the voice signature management system 106. For example, the data storage manager 712 may include digital documents, signed digital documents, field prompt voice files, biometric data, and other data.

[0103] Figures 1 to 7, the corresponding text, and examples provide numerous different methods, systems, devices, and non-temporary computer-readable media of the voice signature management system 106. In addition to the foregoing, one or more embodiments may also be described in relation to flowcharts involving actions to achieve a particular result, as shown in Figure 8. Figure 8 may be performed with more or fewer actions. Furthermore, the actions may be performed in a different order. In addition, the actions described herein may be performed repeatedly, in parallel with each other, or in parallel with different instances of the same or similar actions.

[0104] As described above, Figure 8 shows a flowchart of a series of operations 800 for generating a signed digital document by applying a voice signature, according to one or more embodiments. While Figure 8 shows operations according to one embodiment, alternative embodiments may omit, add, rearrange, and / or modify any of the operations shown in Figure 8. The operations in Figure 8 can be performed as part of a method. Alternatively, a non-temporary computer-readable medium may include instructions that cause a computing device to perform the operations in Figure 8, if executed by one or more processors. In some embodiments, a system may perform the operations in Figure 8.

[0105] As shown in Figure 8, a series of operations 800 includes an operation 802 for generating a field prompt audio file from a digital document. In particular, operation 802 may include generating a field prompt audio file from a digital document that includes a signable field. Specifically, operation 802 may include generating a field prompt audio file from a digital document that includes a signable field, and the field prompt audio file includes audio prompting an audio response to the signable field of the digital document. Furthermore, in one or more embodiments, operation 802 includes providing the digital document to an optical character recognition engine to generate text, and providing the text to a speech engine to generate a field prompt audio file.

[0106] In addition, the sequence of operations 800 includes operation 804 for providing a field prompt audio file for audible presentation. In particular, operation 804 may include providing a field prompt audio file for audible presentation by a client device.

[0107] Furthermore, the sequence of operations 800 includes operation 806 for receiving an audio response to a field prompt audio file, the audio response including an audible acknowledgment. Specifically, operation 806 may include receiving an audio response to a field prompt audio file from a client device, the audio response including an audible acknowledgment for signing a signable field in a digital document.

[0108] Furthermore, the sequence of operations 800 includes an operation 808 for generating a voice signature from a voice response, which includes an approved voice clip approving the signature. In particular, operation 808 may include generating a voice signature from a voice response, which includes an authenticated voice clip approving the signature on a signable field in a digital document. Specifically, operation 808 may include generating a voice signature that includes an authenticated voice clip approving the signature on a signable field in a digital document, based on a determination that the voice response includes an audible acknowledgment. In some embodiments, operation 808 includes identifying biometric data corresponding to a user account associated with the voice signature and authenticating the voice response using the biometric data.

[0109] In addition, the set of operations 800 includes an operation 810 for generating a signed digital document. In particular, operation 810 may include generating a signed digital document by applying a voice signature to the digital document. Specifically, operation 810 may include identifying an additional field in the digital document which includes one of a multiple-choice question or text field, providing an additional field prompt audio file which includes prompts for giving voice utterance information corresponding to the additional field, and converting the voice utterance information to text, and generating a signed digital document further includes populating the additional field based on the text. Furthermore, in one or more embodiments, operation 810 includes embedding an authenticated audio clip approving the signature into the signed digital document. Furthermore, in some embodiments, operation 808 includes generating an indication that the voice signature was received by voice and applying it to the signed digital document.

[0110] In one or more embodiments, the sequence of operations 800 includes, in response to the generation of a signed digital document, providing the signed digital document to an additional client device, receiving a non-voice digital signature from the additional client device, and applying the non-voice digital signature to the signed digital document.

[0111] Embodiments of the present disclosure may include or utilize a dedicated or general-purpose computer, for example, one or more processors and system memory, among other computer hardware, as will be described in more detail below. Embodiments within the scope of the present disclosure also include physical and other computer-readable media for carrying or storing computer-executable instructions and / or data structures. In particular, one or more of the processes described herein may be embodied at least in part in a non-temporary computer-readable medium and implemented as instructions executable by one or more computing devices (e.g., any of the media content access devices described herein). Generally, a processor (e.g., a microprocessor) receives instructions from a non-temporary computer-readable medium (e.g., memory), executes those instructions, and thereby executes one or more processes, including one or more of the processes described herein.

[0112] A computer-readable medium can be any available medium accessible by a general-purpose or dedicated computer system. A computer-readable medium that stores computer-executable instructions is a non-temporary computer-readable storage medium (device). A computer-readable medium that carries computer-executable instructions is a transmission medium. Thus, embodiments of the present disclosure may include, but are not limited to, two distinctly different types of computer-readable mediums: a non-temporary computer-readable storage medium (device) and a transmission medium.

[0113] Non-temporary computer-readable storage media (devices) include RAM, ROM, EEPROM, CD-ROM, solid-state drives ("SSDs") (e.g., based on RAM), flash memory, phase-change memory ("PCM"), other types of memory, other optical disk storage devices, magnetic disk storage devices, or other magnetic storage devices, or any other media that may be used to store desired program code means in the form of computer-executable instructions or data structures and may be accessed by a general-purpose or dedicated computer.

[0114] A “network” is defined as one or more data links that enable the transfer of electronic data between computer systems and / or modules and / or other electronic devices. When information is transferred to or provided to a computer via a network or another communication connection (wired, wireless, or a combination of wired and wireless), the computer appropriately recognizes that connection as a transmission medium. A transmission medium can be used to carry desired program code means in the form of computer-executable instructions or data structures and may include network links and / or data links that can be accessed by a general-purpose or dedicated computer. The above combinations should also be included within the scope of computer-readable media.

[0115] Furthermore, upon reaching various computer system configurations, program code in the form of computer-executable instructions or data structures can be automatically transferred from a transmission medium to a non-temporary computer-readable storage medium (device) (or vice versa). For example, computer-executable instructions or data structures received via a network or data link can be buffered in RAM within a network interface module (e.g., a "NIC") and then ultimately transferred to computer system RAM and / or a non-volatile computer storage medium (device) within the computer system. Therefore, it should be understood that non-temporary computer-readable storage media (devices) can be included in computer system components that also (or primarily) utilize a transmission medium.

[0116] Computer executable instructions include, for example, instructions and data that, when executed by a processor, cause a general-purpose computer, a dedicated computer, or a dedicated processing device to perform a particular function or group of functions. In some embodiments, computer executable instructions are executed by a general-purpose computer to transform that general-purpose computer into a dedicated computer implementing the elements of the Disclosure. Computer executable instructions can be, for example, binaries, intermediate format instructions such as assembly language, or even source code. While the subject matter has been described in language specific to structural features and / or methodological behavior, it should be understood that the subject matter as defined in the appended claims is not necessarily limited to the features or behaviors described above. Rather, the features and behaviors described are disclosed as exemplary forms of implementing the claims.

[0117] Those skilled in the art will understand that the disclosure can be implemented in network computing environments having many types of computer system configurations, including personal computers, desktop computers, laptop computers, message processors, handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, mobile phones, PDAs, tablets, pagers, routers, switches, and the like. The disclosure can also be implemented in distributed system environments in which local and remote computer systems linked over a network (either by wired data links, wireless data links, or a combination of wired and wireless data links) perform tasks. In a distributed system environment, program modules may be located on both local and remote memory storage devices.

[0118] Embodiments of this disclosure may also be implemented in a cloud computing environment. As used herein, the term “cloud computing” refers to a model for enabling on-demand network access to a shared pool of configurable computing resources. For example, cloud computing may be used in the market to provide ubiquitous and convenient on-demand access to a shared pool of configurable computing resources. The shared pool of configurable computing resources can be rapidly provisioned through virtualization, freeing up management effort or service provider interaction, and then scaled accordingly.

[0119] Cloud computing models can comprise a variety of characteristics, such as on-demand self-service, broad network access, resource pooling, rapid scalability, and usage-based services. Cloud computing models can also offer various service models, such as Software-as-a-Service ("SaaS"), Platform-as-a-Service ("PaaS"), and Infrastructure-as-a-Service ("IaaS"). Cloud computing models can be deployed using different deployment models, such as private clouds, community clouds, public clouds, and hybrid clouds. Furthermore, as used herein, the term "cloud computing environment" refers to the environment in which cloud computing is utilized.

[0120] Figure 9 shows a block diagram of an exemplary computing device 900 that may be configured to perform one or more of the processes described above. It will be understood that one or more computing devices, such as computing device 900, may represent the computing devices described above (e.g., server 102, client devices 110a-110n, third-party server 114, client device 214, client device 302, client device 502, client device 508, client device 600, and / or computing device 700). In one or more embodiments, computing device 900 may be a mobile device (e.g., a mobile phone, smartphone, PDA, tablet, laptop, camera, tracker, watch, wearable device, etc.). In some embodiments, computing device 900 may be a non-mobile device (e.g., a desktop computer or another type of client device). Furthermore, computing device 900 may be a server device that includes cloud-based processing and storage capabilities.

[0121] As shown in Figure 9, the computing device 900 may include one or more processors 902, memory 904, storage device 906, input / output interface 908 (or "I / O interface 908"), and communication interface 910 which can be communicatively coupled by a communication infrastructure (e.g., bus 912). Although the computing device 900 is shown in Figure 9, the components shown in Figure 9 are not intended to be limiting. Additional or alternative components may be used in other embodiments. Furthermore, in certain embodiments, the computing device 900 may include fewer components than those shown in Figure 9. The components of the computing device 900 shown in Figure 9 are described in more detail here.

[0122] In certain embodiments, the processor 902 includes hardware for executing instructions, such as instructions that constitute a computer program. To execute instructions, but not limited to, the processor 902 may retrieve (or fetch) instructions from internal registers, internal cache, memory 904, or storage device 906, decode them, and execute them.

[0123] The computing device 900 includes memory 904 coupled to the processor 902. Memory 904 may be used to store data, metadata, and programs for execution by the processor. Memory 904 may include one or more volatile and non-volatile memories, such as random access memory ("RAM"), read-only memory ("ROM"), solid-state disks ("SSD"), flash memory, phase-change memory ("PCM"), and other types of data storage. Memory 904 may be internal or distributed memory.

[0124] The computing device 900 includes a storage device 906 that includes storage for storing data or instructions. The storage device 906 may include, but is not limited to, the non-temporary storage media described above. The storage device 906 may include a hard disk drive (HDD), flash memory, a universal serial bus (USB) drive, or a combination of these or other storage devices.

[0125] As illustrated, the computing device 900 includes one or more I / O interfaces 908, which are provided to allow the user to provide input (such as user strokes), receive output, and otherwise send and receive data to and from the computing device 900. These I / O interfaces 908 may include a mouse, keypad or keyboard, touchscreen, camera, optical scanner, network interface, modem, other known I / O devices, or a combination of such I / O interfaces 908. The touchscreen may be operated with a stylus or a finger.

[0126] The I / O interface 908 may include, but is not limited to, a graphics engine, a display (e.g., a display screen), one or more output drivers (e.g., display drivers), one or more audio speakers, and one or more audio drivers, one or more devices for presenting output to the user. In certain embodiments, the I / O interface 908 is configured to provide graphical data to a display for presentation to the user. The graphical data may represent one or more graphical user interfaces and / or any other graphical content that may serve the role of a particular implementation.

[0127] The computing device 900 may further include a communication interface 910. The communication interface 910 may include hardware, software, or both. The communication interface 910 provides one or more interfaces for communication (e.g., packet-based communication) between the computing device and one or more other computing devices or one or more networks. For example, but not limited to, the communication interface 910 may include a network interface controller (NIC) or network adapter for communicating with Ethernet® or other wired-based networks, or a wireless NIC (WNIC) or wireless adapter for communicating with wireless networks such as Wi-Fi. The computing device 900 may further include a bus 912. The bus 912 may include hardware, software, or both that connect the components of the computing device 900 to each other.

[0128] In the aforementioned specification, the present invention has been described with reference to certain exemplary embodiments. Various embodiments and aspects of the present invention are described with reference to the details discussed herein, and the accompanying drawings illustrate various embodiments. The above description and drawings are illustrative of the present invention and should not be construed as limiting. Numerous specific details are described in order to provide a complete understanding of the various embodiments of the present invention.

[0129] The present invention may be implemented in other specific forms without departing from its spirit or essential features. The embodiments described herein should be considered in all respects to be illustrative and not limiting. For example, the methods described herein may be performed in fewer or more steps / movements, or the steps / movements may be performed in a different order. In addition, the steps / movements described herein may be performed repeatedly, in parallel with one another, or in parallel with different instances of the same or similar steps / movements. Accordingly, the scope of the present invention is indicated not by the foregoing description but by the appended claims. All modifications that fall within the meaning and scope of the equivalents of the claims should be incorporated within the claims.

[0001]

Claims

1. Generating field prompt audio files from digital documents containing signable fields, To provide the field prompt audio file for audible presentation by the client device, Receiving an audio response from the client device to the field prompt audio file, wherein the audio response includes an audible acknowledgment to sign the signable field in the digital document. From the aforementioned voice response, a voice signature is generated that includes an authenticated voice clip approving the signing of the signatureable field in the digital document. The process involves generating a signed digital document by applying the aforementioned voice signature to the digital document, Methods that include...

2. Generating the aforementioned field prompt audio file is, The aforementioned digital document is provided to an optical character recognition engine to generate text, Providing the aforementioned text to the speech engine to generate the field prompt audio file, The method according to claim 1, including the method described in claim 1.

3. Identifying additional fields within the digital document that include one of a multiple-choice question or a text field, To provide an additional field prompt audio file that includes a prompt for providing speech utterance information corresponding to the aforementioned additional field, Converting the aforementioned speech utterance information into text, It further includes, Generating the aforementioned signed digital document further includes entering the aforementioned additional fields based on the aforementioned text, The method according to claim 1.

4. The method according to claim 1, further comprising embedding the authenticated audio clip approving the signature into the signed digital document.

5. Identifying biometric data corresponding to the user account associated with the aforementioned voice signature, Authenticating the voice response using the aforementioned biometric authentication data, The method according to claim 1, further comprising:

6. In response to generating the aforementioned signed digital document, the signed digital document is provided to additional client devices. Receiving non-voice digital signatures from the aforementioned additional client devices, Applying the non-voice digital signature to the signed digital document, The method according to claim 1, further comprising:

7. The method according to claim 1, further comprising generating the signed digital document by generating an indication that the voice signature was received by voice and applying it to the signed digital document.

8. If running on at least one processor, the computer system A field prompt audio file is generated from a digital document containing a signable field, and the field prompt audio file includes audio prompting an audio response to the signable field in the digital document. The client device provides an audio file for audible field prompts. The client device receives an audio response to the field prompt audio file, and the audio response includes an audible acknowledgment to sign the signable field in the digital document. From the aforementioned voice response, an audio signature is generated, which includes an authenticated audio clip approving the signing of the signatureable field in the digital document. A signed digital document is generated by applying the aforementioned voice signature to the digital document. A non-temporary, computer-readable medium that stores instructions for how to operate.

9. When executed by the at least one processor, the computer system The aforementioned digital document is provided to an optical character recognition engine to generate text. The aforementioned text is provided to the speech engine to generate the field prompt audio file. A non-temporary computer-readable medium according to claim 8, further comprising instructions for causing it to operate in such a manner.

10. When executed by the at least one processor, the computer system Identify additional fields in the digital document that include one of a multiple-choice question or a text field, The system provides an additional field prompt audio file that includes a prompt for providing speech utterance information corresponding to the aforementioned additional field. Convert the aforementioned speech utterance information into text. It further includes instructions to make it work in that way, Generating the aforementioned signed digital document further includes entering the aforementioned additional fields based on the aforementioned text, The non-temporary computer-readable medium according to claim 8.

11. The non-temporary computer-readable medium according to claim 8, further comprising, when executed by the at least one processor, instructions causing the computer system to embed the authenticated audio clip approving the signature into the signed digital document.

12. When executed by the at least one processor, the computer system Identify biometric data corresponding to the user account associated with the voice signature, The voice response is authenticated using the aforementioned biometric authentication data. A non-temporary computer-readable medium according to claim 8, further comprising instructions for causing it to operate in such a manner.

13. When executed by the at least one processor, the computer system In response to the generation of the aforementioned signed digital document, the signed digital document is provided to additional client devices. Receiving a non-voice digital signature from the aforementioned additional client device, Apply the non-voice digital signature to the signed digital document. A non-temporary computer-readable medium according to claim 8, further comprising instructions for causing it to operate in such a manner.

14. The non-temporary computer-readable medium according to claim 8, further comprising generating the signed digital document, generating an indication that the voice signature was received by voice, and applying it to the signed digital document.

15. At least one processor, A system comprising at least one non-temporary computer-readable storage medium for storing instructions, wherein when an instruction is executed by the at least one processor, the system Generate field prompt audio files from digital documents containing signable fields. The client device provides an audio file for audible field prompts. The client device receives an audio response to the field prompt audio file, and the audio response includes an audible acknowledgment to sign the signable field in the digital document. Based on the determination that the voice response includes the audible acknowledgment, a voice signature is generated that includes an authenticated voice clip approving the signing of the signatureable field in the digital document. A signed digital document is generated by applying the aforementioned voice signature to the digital document. A system that makes something work in a certain way.

16. When executed by the at least one processor, the system The aforementioned digital document is provided to an optical character recognition engine to generate text. The aforementioned text is provided to the speech engine to generate the field prompt audio file. The system according to claim 15, further comprising instructions to cause it to operate in such a manner.

17. When executed by the at least one processor, the system Identify additional fields in the digital document that include one of a multiple-choice question or a text field, The system provides an additional field prompt audio file that includes a prompt for providing speech utterance information corresponding to the aforementioned additional field. Convert the aforementioned speech utterance information into text. It further includes instructions to make it work in that way, Generating the aforementioned signed digital document further includes entering the aforementioned additional fields based on the aforementioned text, The system according to claim 15.

18. When executed by the at least one processor, the system Identify biometric data corresponding to the user account associated with the voice signature, The voice response is authenticated using the aforementioned biometric authentication data. The system according to claim 15, further comprising instructions to cause it to operate in such a manner.

19. When executed by the at least one processor, the system In response to the generation of the aforementioned signed digital document, the signed digital document is provided to additional client devices. Receiving a non-voice digital signature from the aforementioned additional client device, Apply the non-voice digital signature to the signed digital document. The system according to claim 15, further comprising instructions to cause it to operate in such a manner.

20. The system according to claim 15, further comprising generating an indication that the voice signature was received by voice and applying it to the signed digital document.

Images