BR112014010096B1 - METHOD TO FACILITATE ELECTRONIC SUBSCRIPTIONS ON A CUSTOMER DEVICE WHICH IS OPERATED BY A SUBSCRIBER - Google Patents

Abstract

mobile solution for importing and signing documents with electronic signatures by third parties. The present invention relates to techniques for an electronic document signature initiated by the subscriber through an electronic signature service using a mobile device or other client device. Exemplary embodiments provide an electronic signature service ("ESS") configured to facilitate the creation, storage, and management of documents and corresponding electronic signatures. In some embodiments, when a signing user receives a hard copy (e.g., paper) of the signed document, the signer may capture an image of the signed document with a camera of a mobile device. the subscriber can then import the captured image into ess for signature, storage, and/or transmission to other parties.

Description

PRIORITY CLAIM

[0001] This application claims the benefit of US Provisional Application Serial Number No. 61/552,359, filed October 27, 2011. This application is also a partial continuation of US Patent Application Serial Number No. 13/595,876, filed August 27, 2012, which claims the benefit of US Provisional Application Serial No. 61/527,406, filed August 25, 2011.

FIELD OF INVENTION

[0002] The present description relates to methods and systems for electronic signatures, and more particularly to methods and systems for facilitating subscriber-initiated electronic lectron signature using a mobile device or other client device, such as by capturing a image of an lectron with an lectr from the mobile device and then importing the image as an lectron with an electron signature into an lectron of an electronic signature for signature and storage.

BACKGROUND

[0003] An existing approach to electronic signatures provides an application for "stamping" the electronic signature to a mobile device. The signature app allows a user to open a document, bypass it for signature and "stamp" a signature or other data on the document and return it via email. This approach suffers from several disadvantages. As an example, it only works with specific software applications for mobile devices and the subscription process is performed entirely in software on the mobile device. As such, the document must be manually moved from the email message into the device, manipulated, and then returned to the device for email distribution.

[0004] Likewise to produce such an application for multiple devices or platforms it is necessary that a largely redundant application is created for each platform and then only for those platforms that have enough capacity to actually handle PDFs. Not all platforms or devices can really handle tasks like file conversion, file presentation, signature capture management and placement and security. The inability of mobile devices to universally perform all such necessary functions severely limits the expansion of electronic signature services, particularly in the context of the mobile device.

[0005] Furthermore, such an application does not handle the case where a user receives a hard copy of a document. For example, if a user receives a paper copy of a contract, there is no convenient way for the user to import that document into their mobile device and attach an electronic signature. The inability of mobile devices to handle physical documents still limits the expansion of electronic signature services.

BRIEF DESCRIPTION OF THE DRAWINGS

[0006] Preferred and alternative examples of the present invention are described in detail below with reference to the following drawings:

[0007] Figure 1 illustrates an exemplary block diagram of an exemplary modality of an electronic signature service;

[0008] Figures 2A-2E illustrate user interface screens according to exemplary embodiments;

[0009] Figure 3 is a flow diagram of an exemplary electronic signature client process and;

[0010] Figure 4 is a block diagram of an exemplary computing system for implementing an electronic signature service according to an exemplary modality.

DETAILED DESCRIPTION

[0011] The modalities described here provide enhanced network and computer-based systems and methods for mobile devices and other client devices to facilitate electronic document signature. Exemplary modalities provide an electronic signature service (“ESS”) configured to facilitate the creation, storage, and management of documents and corresponding electronic signatures. Using at least some of the techniques described above, a user ("subscriber") can efficiently import a paper-signed document into the ESS with a client device that has or is communicatively coupled to a camera or other capture device. image (eg a scanner). First, the subscriber captures an image (eg, taking a photo) of the document signed on paper. Then, using a browser or other client module running on the client device, the subscriber can import the captured image into the ESS. The subscriber can also access, review and sign the document via the mobile device either before or after the document is imported into the ESS. After signing the document, the subscriber can use the client device to have the ESS provide access to the signed document to a recipient, such as having the ESS email or otherwise transmit the signed document to the recipient.

[0012] Figure 1 illustrates an exemplary block diagram of an exemplary modality of an electronic signature service. In particular, Figure 1 depicts an ESS 110 used by a sending user 10 and a subscribing user 11 to facilitate an electronic signature of a signed document.

[0013] In the illustrated scenario, sender 10 transmits a document (eg a contract or agreement) to subscriber 11, where it is received as paper document 19. Document transmission may include sending the document via email or courier service. In other embodiments, the document may be transmitted at least in part in electronic form, such as by transmitting the document via a fax machine/network (not shown) to subscriber 11, where it is reproduced as paper document 19 As another example, sender 10 may use sender's client device 160 to send an email with the document included as an attachment to the email. The transmitted document can be in any format, such as PDF, Microsoft Word, HTML, text or the like. Upon receipt of the email or electronic transmission, subscriber 11 or some other third party then prints the transmitted document as paper document 19.

[0014] Subscriber 11 may then use subscriber's client device 161 to import the document into the ESS 110. In the illustrated embodiment, subscriber's client device 161 includes a camera 162 and client logic 163 (e.g., a browser Web, email reader, a plug-in, a mobile app). In other embodiments, the subscriber's client device 161 is communicatively coupled to a separate camera or other input device (eg, a scanner) operable to capture an image of the paper document 19. The subscriber 11 drives the client logic 163 to direct the camera 162 to capture an image of the paper document 19. The image data of the captured document is then stored or buffered on the subscriber's client device 161 as a bitmap, compressed image (eg, JPEG, GIF), PDF file or the like. Subscriber 11 can then review the image data of the captured document (eg to determine image quality), modify the image data (eg by adding additional pages of the paper document 19 captured by camera 162, by adding subscription data) or the like.

[0015] When the user is satisfied that the paper document 19 was successfully captured by the camera 162, the user causes the client logic 163 to import the image data of the document captured by the camera 162 to the ESS 110, where it is securely stored as an electronic document 20. The ESS 110 can also convert the imported image data into a standard or preferred format for storage within the ESS 110. For example, if the captured image data is transmitted to the ESS 110 As a bitmap or other image file, data can be converted to or embedded within a PDF file by the ESS 110.

[0016] Once the document image data is imported into the ESS 110 and securely stored as the document 20, the subscriber 11 can use the client device 161 to interact with the ESS 110 and perform various signature-related operations electronics. For example, subscriber 11 can access and review the document by presenting and navigating the document using logic 163, a browser, or some other client logic running on client device 161. Once subscriber 11 has reviewed and/or modified the document at its discretion, it can provide the signature data which is then securely stored by the ESS 110 as signature data 21 in association with the document 20. Note that in some embodiments, the subscriber 11 can provide signature data in a later time, such as after document 19 has been captured by camera 162, but before the captured image data is imported into the ESS 110. In such cases, signature data may be transmitted from the subscriber's client device 161 during ( or at approximately the same time as) importing the document's image data into the ESS 110.

[0017] Once the subscriber 11 has signed the document 20, the subscriber 11 can have the ESS 110 provide access to the signed document 20 to a recipient. For example, subscriber 11 can return the signed document to sender 10 or some other recipient. Different approaches to providing access to signed documents are contemplated. In the illustrated embodiment, the subscriber 11 can have the ESS 110 notify the sender 10, such as having the ESS 110 transmit (e.g., in an email) a URL, link or other identifier of the document 20 to the client device sender 160. The sender 10 may then use a browser or other client logic running on the sender's client device 160 to access the signed document in the ESS 110. Such an approach may be advantageous for sensitive documents that may preferably not be , transmitted within an email or through some other possibly insecure transmission facility. In other embodiments, the ESS 110 may transmit the signed document 20 via an email, fax or other transmission mechanism.

[0018] Note that the scenario described with respect to Figure 1 can be modified in several ways. For example, different users can perform the import and signature operations described with respect to subscriber 11 in Figure 1. For example, a first user can use a client device (eg, mobile phone) to capture an image of a signed document and then importing the captured image into the ESS 110. The first user can then request (via the ESS 110) that a Second user provide a signature, such as having the ESS 110 send an email including a link that can be used by the second user to review and sign the stored document with electronic signature.

[0019] Also note that at least some of the techniques described can be employed in a context where the client device does not include or otherwise use a camera. For example, the sender 10 may use the sender's client device 160 to transmit a signed document (e.g., an agreement or contract) to the subscriber's client device 161. For example, the sender 10 may transmit an email that includes an document with signature (for example, as an attachment or in the body of the email by itself). Next, subscriber 11 can use logic 163 on subscriber's client device 161 to import the document received with signature into the ESS 110 for secure storage and signature. In an email-based modality, logic 163 can be or include a plug-in or extension for an email client or other type of email reader. As another example, subscriber 11 may initially receive a signed document from a website, such as when accessing a website that originates or otherwise facilitates bank loans, credit card accounts or the like. Upon receipt of the document (for example, in a web browser of the subscriber's client device 161), the subscriber 11 can use logic 163 to import the document into the ESS 110 for secure storage and signing. In such an embodiment, the logic 163 can be or include a plug-in running in the context of a web browser.

[0020] The ESS 110 may provide other or additional functions. For example, the ESS 110 can provide or facilitate intelligent form-filling operations. In one embodiment, when subscriber 11 repeatedly uses the ESS 110 to electronically sign documents, the ESS 110 tracks the form data (eg, names, addresses, telephone numbers) provided by subscriber 11, such that the forms within the Signed documents can be automatically populated with data elements, thereby increasing the efficiency of the signing process.

[0021] In some embodiments, the ESS 110 provides electronic identification cards ("ID") that represent user identities. An ID can include or operate as a container for information about a corresponding user, including personal information (eg name, address), a signature, security settings (eg regarding sharing personal information). In some cases, the ESS 110 makes it easy to create an ID for a user based on authentication information or credentials related to a social network (eg Facebook, Twitter) or other system (eg public email system). For example, the user can use credentials for their account on a social network (eg username and password) to establish an ID card managed by the ESS 110, thus eliminating the need to create yet another set of credentials that are specific to the ESS 110.

[0022] Typically, subscriber client device 161 is a mobile device, such as a smart phone, tablet computer, personal digital assistant, or the like. However, the techniques can be equally applied in other contexts and/or other types of computing devices, including desktop computers, kiosk systems, and the like. In particular, some modalities provide a module (eg plugin, widget, extension) configured to perform some of the techniques described in the context of a desktop email client (eg Outlook), a hosted email service (eg Google Mail, Yahoo! Mail, Hotmail), or another application. In addition, the techniques can generally be deployed (eg as a signature module) in the context of any web-based information or e-commerce service that has a need to obtain an electronic signature from a user (eg to obtain approval of the terms and conditions to enter to establish buy/sell agreements, etc.).

[0023] In some embodiments, all or most functions can be performed with a thin client (eg, a web browser) running on the client device 161, such that none or minimal special purpose software needs to be installed on the client device 161 to perform or access the full spectrum of subscription services provided by the ESS 110. In this way, the techniques described overcome many of the limitations of known approaches to facilitating electronic signatures on mobile devices. For example, in a familiar approach, a customer must install a special-purpose signature app (a “signature app”) on a mobile phone to attach electronic signatures to documents. Unfortunately, this app is distinct from the email client on the mobile phone, in that the user must manually move a received document within the signing app, attach a signature, move the signed document back to the email client, and then transmit the document signed for a recipient. Such processing can be inefficient, complex, and uninteresting to the user. Also, many signature apps do not include features such as document conversion, so they are unable to attach signatures to many common document formats. Furthermore, the diversity of mobile phone platforms (eg iPhone, Android, Blackberry) means developing and supporting different applications for each platform. The techniques described, on the other hand, are largely platform independent, as core functionality is provided by the ESS 110, but accessed from multiple clients using standard web browsers.

[0024] In addition, US patent application no. 13/595,876, filed August 27, 2012 and entitled “MOBILE SOLUTION FOR SIGNING AND RETENTION OF THIRD PARTY DOCUMENTS,” further describes modalities of an ESS configured to facilitate electronic signatures via a mobile device or other client devices and is incorporated by reference herein in its entirety. The techniques described herein can be used in combination with one or more of those described in U.S. Patent Application No. 13/595,876.

[0025] Figures 2A-2E illustrate user interface screens according to exemplary embodiments. The illustrated UI screens can be displayed by client software running on a subscriber's client device, such as the client logic 163 described above.

[0026] Figure 2A illustrates a login screen 200 presented by a client device operated by a subscriber or other user. The screen 200 can be provided by a client mobile device, such as a smart phone or tablet computer. In other embodiments, screen 200 may be part of a file selector/browser or desktop computer system. Screen 200 displays a user name input control 201, a password input control 202, and a control signal 203. After the subscriber provides a username and password respectively through controls 201 and 202, the subscriber selects the control 203 to initiate an authentication session with the ESS.

[0027] Screen 200 also includes controls (eg links) for retrieving a forgotten password 204, creating a new account 205, or logging in using social network credentials 206. Upon selection control 205, the subscriber will be brought up to an account creation screen. The subscriber will be asked to enter their email address, name, password and password confirmation and agree to the terms and conditions of the ESS. If everything goes successfully, a new account will be created for the subscriber. In some modalities, the subscriber will be sent an activation email informing the subscriber that an account has been created and asking the subscriber to click on the included link to activate the account.

[0028] Upon selection of control 206, the subscriber will be asked to provide their credentials to a social network (eg Facebook, Google+, Twitter) or other information service (eg a free online email service). If the user does not have an account with the ESS that is associated with the provided credentials, the user will be prompted to create an account, as discussed above. If the user does not have an account associated with the ESS, an authenticated session will be initiated (provided the correct credentials are provided).

[0029] Figure 2B illustrates a browser screen of document 210. Screen 210 is typically displayed after successful login, as discussed above. Screen 210 displays indicators of documents available for signing on or through the client device. In the illustrated example, screen 210 includes control 211, which identifies a document that is available for signature. The document can be stored on the client device or elsewhere (eg in the ESS). The control includes keys to sign or delete the corresponding document. If a user selects the subscribe key, a subscribe screen will be presented, as discussed with reference to Figure 2E, below.

[0030] The screen 210 also includes a tabs control 212 that includes tabs for accessing different screens of client software on the client device. The control 212 includes a My Documents 213 tab for accessing the 210 screen, a Capture tab 214 for accessing an image capture screen 220 (figures 2C and 2D), and an Identity tab 215 for managing an electronic card of ID as discussed with reference to Figure 1, above.

[0031] Figure 2C illustrates an image capture screen 220. The image capture screen 220 facilitates capturing and importing an image of a paper document as described here. The screen includes a take photo control 221 and an existing photo selection control 222. Upon selection of control 221, the subscriber will be presented with the user interface for the camera or other image capture device of or associated with the client device. The subscriber can then take one or more photos of a document signed on paper.

[0032] Upon selection of control 222, the subscriber will be presented with a photo browser to select one or more photos previously taken and stored on the client device. The browser can be a custom browser adapted to the subscription software or a native or standard photo browser provided by the client device. Once the user has captured and/or selected photos of the document signed on paper, screen 220 will display the selected photos as discussed with reference to the 2D figure below.

[0033] Figure 2D illustrates the image capture screen 220 after the subscriber has selected one or more photos to import as a document with electronic signature. The 220 screen now includes a 223 tray control that shows thumbnail images of the subscriber's selected photos. In this example, the subscriber has selected three photos, here tagged as photos 1, 2, and 3. The subscriber can manipulate the photos such as rearranging, resizing, cropping, adjusting brightness or contrast, or the like. Also visible now is a 224 finish control, which can be selected by the subscriber when they have arranged and/or manipulated the photos at their discretion. Upon selection of completion control 224, selected photos are transmitted to the ESS for secure storage as an electronically signed document. In other embodiments, transmission of photos may be delayed until after the subscriber has attached a signature, such as via a signature screen described with reference to Figure 2E, below.

[0034] Figure 2E illustrates a signature screen 230. The signature screen 230 is presented in response to an indication that a user wishes to sign a document. For example, screen 230 may be presented in response to a user selection of the Subscribe key from control 211 (figure 2A) or completion control 224 (figure 2D).

[0035] Signature screen 230 displays a document with signature 233 and includes a menu bar 231. Document with signature 233 is a copy or other presentation of the images captured and imported by the subscriber, as discussed above. Menu bar 231 includes an Add control, a Finish control, and a More Options control. The Add control, when selected, displays a menu 232 of signature elements. Signature elements include a signature, signer's initials, signer's name, date signed, text, and checkbox. By selecting one of the signature elements, the user/subscriber can insert (eg drag and drop) the corresponding element within the document with signature 233. In this example, the subscriber has selected and dragged a signature element 234 over document 233. Signature element 234 is an active control, which can be selected (eg tapped, clicked) by the subscriber to associate his signature with the document 233.

[0036] When the user receives and signs document 233, the user selects the End control from menu 231. The End control causes a signature gathered via signature element 234 to be securely stored in association with document 233 by the ESS 110 The Finalize control may also provide options or otherwise access functions for the provision of the signed document 233 to one or more recipients. For example, the Finalize control can automatically invoke an email client on the subscriber's client device. The email client can be automatically prepopulated with a message that includes a copy of (eg as an attachment) and/or reference to (eg URL) signed document 233.

[0037] Note that although the example in figures 2A-2E is described in relation to a “subscriber” that imports and signs a document, the illustrated scenario can include multiple distinct users. For example, a first user (an “importer”) can capture an image of a document signed on paper and import it as described with reference to figures 2C and 2D. The importing user can then email or otherwise transmit the signed document to a second user (“subscriber”), who then uses a user interface such as the one shown in Figure 2E to sign the document.

[0038] Figure 3 is a flowchart of an exemplary electronic signature client process. The illustrated process can be performed, for example, by logic 163 running on subscriber client device 161.

[0039] The process starts at block 302, where it captures an image of a document signed with a camera on a client device. As shown in Figure 1, subscriber client device 161 typically includes a camera 162 that is used to capture an image (eg, taking a picture) of a hard copy (eg, paper) of the signed document. In other embodiments, subscriber client device 161 may be coupled to a scanner, separate camera, or other image capture device that can be used to capture an image of the signed document.

[0040] In block 304, the process causes the captured image to be stored in a remote electronic signature service as an electronically signed document. Subscriber client device 161 includes logic 163 that updates, imports, or otherwise transmits the captured image to the electronic signature service, where it is securely stored.

[0041] In block 306, the process causes an electronic signature to be stored in association with the stored electronic signature document. Typically, logic 163 will be operated by the user to “attach” a signature to the document. Attaching a signature may include transmitting an indication that the user has registered (possibly with other data such as date, subscription form and the like) with the electronic signature service, thereby causing the electronic signature service to store with security the subscriber's signature in association with the document.

[0042] Figure 4 is a block diagram of an exemplary computing system for implementing an electronic signature service according to an exemplary modality. In particular, Figure 4 shows a computing system 100 that can be used to implement an ESS 110.

[0043] Note that one or more general purpose or special purpose computing systems/devices may be used to implement the ESS 110. In addition, computing system 100 may comprise one or more distinct computing systems/devices and may span distributed locations. In addition, each block shown may represent one or more such blocks, as appropriate for a specific modality, or may be combined with other blocks. Likewise, the ESS 110 can be implemented in software, hardware, firmware, or some combination to achieve the capabilities described here. In addition, the implementation techniques described here can also be used to implement other aspects, including client logic 163 of subscriber client device 161.

[0044] In the embodiment shown, the computing system 100 comprises a computer memory ("memory") 101, a display 102, one or more Central Processing Units ("CPU") 103, Input/Output devices 104 (per eg keyboard, mouse, CRT or LCD display and the like), other computer readable media 105 and network connections 106 connected to a network 150. The ESS 110 is shown housed in memory 101. In other embodiments, some part of the contents , some or all of the components of the ESS 110 may be stored in and/or transmitted via other computer readable media 105. The components of the ESS 110 preferably run on one or more CPUs 103 and facilitate mobile electronic signature processes , described here. Other code or programs 130 (for example, an administrative interface, a web server and the like) and potentially other data repositories, such as data repository 120, also reside in memory 101 and are preferably executed in one or more CPUs 103. It should be noted that one or more of the components in Figure 4 may not be present in any particular implementation. For example, some embodiments may not provide other computer readable media 105 or a display 102.

[0045] The ESS 110 includes a service manager 111, a user interface manager (“UI”) 112, an electronic signature service application program interface (“API”) 113, and a service data store of electronic signature 115.

[0046] The ESS 110, through service manager 111 and related logic, generally performs electronic signature related functions for or on behalf of users operating a sender client device 160 and/or a subscriber client device 161. In in one embodiment, a subscriber operating the subscriber's client device 161 imports (eg, transmits, transfers data, sends) a document to be electronically signed into the ESS 110. As described above, importing a document may include capturing of an image of a paper document, and then transmitting the captured image from the client device 161 to the ESS 110. The ESS stores the document securely in the data repository 115. Secure storage of the document may include the use of cryptographic techniques to detect document manipulation, such as generating hashes, message digests, or the like. The subscriber operating the subscriber's client device 161 may then access, review, and sign the document stored by the ESS 110. In some embodiments, the ESS 110 transmits images or some other representation of the document to the subscriber's client device 161, which in turn transmits an indication of the subscriber's signature (or intent to subscribe) to the ESS 110. The ESS 110 then securely stores the subscriber's signature in association with the document in data repository 115. After signing the document , the subscriber using the subscriber's client device 161 can have the ESS 110 provide the signed document to one or more recipients, such as via email, fax, or other mechanism.

[0047] The service manager 111 may perform other or additional functions, such as intelligent form filling as discussed above. Likewise, the service manager 111 may provide (e.g. transmit) code modules that can be installed on the subscriber's client device 161 and which are configured to integrate the subscriber's client device 161 with the ESS 110. As an example , the code module can be a mobile application (eg, app) that installs on the subscriber's client device 161. As another example, the code module can extend the functionality of an email client or other application by adding of a control (eg key, menu item, widget) that is configured to import, in response to selection or activation by a user, documents received on the ESS 110.

[0048] The UI manager 112 provides a view and a control that facilitates user interaction with the ESS 110 and its various components. For example, the UI manager 112 can provide interactive access to the ESS 110, such that users can download or download documents for signature, review and modify documents, transmit or otherwise provide signed documents to recipients, and the like. In some embodiments, access to UI manager functionality 112 may be provided through a web server, possibly running as one of the other programs 130. In such embodiments, a user operating a web browser (or other client) running on one of the client devices 160 or 161 can interact with the ESS 110 through the UI manager 112.

[0049] API 113 provides programmatic access to one or more functions of the ESS 110. For example, API 113 may provide a programmatic interface to one or more functions of the ESS 110 that can be invoked by one of the other 130 programs or some another module. In this way, API 113 facilitates the development of third-party software, such as user interfaces, plug-ins, news feeds, adapters (eg for integrating ESS 110 functions into web applications), and similar. In addition, API 113 may be in at least some modality invoked or otherwise accessed through remote entities, such as the third party system 165, to access various functions of the ESS 110. For example, an email service hosted on running on system 165 can provide access to the electronic signature functionality of the ESS 110 through API 113. As another example, an e-commerce site (eg, webshop) running on system 165 can provide access to the electronic signature functionality of the ESS 110 via API 113, such as by providing a configured signature/widget control, when selected by a user, to initiate an electronic signature process, as described here.

[0050] Data repository 115 is used by other modules of the ESS 110 to store and/or communicate information. The ESS 110 components use data repository 115 to record various types of information, including documents, signatures, tracked document entries, and the like. Although the components of the ESS 110 are described as communicating primarily through data repository 115, other communication mechanisms are contemplated, including message passing, function calls, pipes, sockets, shared memory, and the like.

[0051] The ESS 110 interacts through network 150 with client devices 160 and 161 and third-party systems 165. Network 150 can be any combination of one or more media (e.g., twisted pair, coax, fiber optic, frequency of radio), hardware (eg, routers, switches, repeaters, transceivers), and one or more protocols (eg, TCP/IP, UDP, Ethernet, Wi-Fi, WiMAX) that facilitate communication between humans and/or devices located remotely. In some embodiments, network 150 can be or include multiple distinct channels or communication mechanisms (e.g., cable or wireless). Client devices 160 and 161 include personal computers, laptop computers, smart phones, personal digital assistants, tablet computers, kiosk systems, and the like. Third party systems 165 and client devices 160 and 161 may be or include computing systems and/or devices constituted in a manner similar to that of computing system 100, and thus may also include displays, CPUs, other I/O devices ( eg a camera), network connections or the like.

[0052] In an exemplary embodiment, the components/modules of the ESS 110 are implemented using standard programming techniques. For example, the ESS 110 can be implemented as a “native” executable run on the CPU 103, with one or more static or dynamic libraries. In other embodiments, the ESS 110 can be implemented as instructions processed by a virtual machine that execute like one of the other programs 130. In general, a range of programming languages known in the art can be employed to implement such exemplary embodiments. , including representative implementations of various programming language paradigms, including but not limited to object-oriented ones (eg Java, C++, C#, Visual Basic.NET, Smalltalk, and the like), functional (eg ML, Lisp , Scheme, and the like), procedural (eg, C, Pascal, Ada, Modula, and the like), scripting (eg, Perl, Ruby, Python, JavaScript, VBScript, and the like), and declarative ( for example, SQL, Prolog, and the like).

[0053] The modalities described above may also use proprietary or well-known synchronous or asynchronous client server computing techniques. Likewise, the various components can be implemented using more monolithic programming techniques, for example as an executable execution on a single CPU computer system, or alternatively decomposed using a variety of structuring techniques known in the art, including among others multiprogramming , multiple execution, client-server or peer-to-peer, execution on one or more computer systems, each having one or more CPUs. Some modalities can run concurrently and asynchronously and communicate using message passing techniques. Equivalent synchronous modalities are also supported. Likewise, other functions could be implemented and/or performed by each component/module and in different orders and by different components/modules, still achieving the desired functions.

[0054] In addition, interfaces to data stored as part of the ESS 110, such as in data repository 118, can be available by standard mechanisms such as through C, C++, C#, and Java APIs; libraries for accessing files, databases, or other data repositories; through scripting languages such as XML; or through Web servers, FTP servers, or other types of servers that provide access to stored data. Data repository 118 may be implemented as one or more database systems, file systems, or any other technique for storing such information or any combination of the above, including implementations using distributed computing techniques.

[0055] Different configurations and locations of programs and data are contemplated for the use of techniques described here. A variety of distributed computing techniques are suitable for implementing the components of the illustrated modalities in a distributed manner including among others TCP/IP, RPC, RMI, HTTP, Web Services sockets (XML-RPC, JAX-RPC, SOAP, and the like). Other variations are possible. Likewise, other functionality could be provided by each component/module or existing functionality could be distributed among the components/modules in different ways, still achieving the functions described here.

[0056] In addition, in certain embodiments, some or all of the components of the ESS 110 may be implemented or provided in other ways, such as at least partially in firmware and/or hardware, including but not limited to one or more application-specific integrated circuits (“ASICs”), standard integrated circuits, controllers that execute appropriate instructions and including microcontrollers and/or embedded controllers, field-programmable gate arrays (“FPGAs”), complex programmable logic devices (“CPLDs”), and the like. Some or all of the system components and/or data structures may also be stored as content (eg as executable or other computer-readable software instructions or structured data) on a computer-readable medium (eg, as a disk hard drive; a memory; a computer network or wireless cellular network or other data transmission medium; or a portable article to be read by an appropriate disk drive or through an appropriate connection such as a DVD or device of flash memory) in order to enable or configure the computer-readable medium and/or one or more computer systems or associated devices to perform or otherwise use or provide the contents to perform at least some of the techniques described. Some or all of the components and/or data structures may be stored in a non-transient manner on tangible non-transient storage media. Some or all of the system components and data structures may also be stored as data signals (for example, being encoded as part of a carrier wave or included as part of an analog or digital propagated signal) on a variety of transmission media computer readable, which are then transmitted, including over wireless and wired/cable media, and may take a variety of forms (eg, as part of a single or multiplexed analog signal or as multiple packets or frames discrete digital Such computer program products can also take other forms in other modalities. Consequently, the modalities of this description can be practiced with other computer system configurations.

[0057] It should be apparent to those skilled in the art that many more modifications than those already described are possible without departing from the inventive concepts here. The subject of the invention, therefore, should not be restricted except in the spirit of the appended claims. Furthermore, in interpreting both the descriptive report and the claims, all terms must be interpreted as broadly as possible consistent with the context. In particular, the terms "includes", "including", "comprises" and "comprising" shall be interpreted as referring to the elements, components or steps in a non-exclusive manner, indicating that the referenced elements, components, or steps may be present or be used or combined with other elements, components or steps that are not expressly referenced. Where the description and/or written claims refer to at least one selected from the group consisting of A, B, C .... and N, the text is to be interpreted as requiring at least one element from the group (A, B, C...N) instead of A plus N or B plus N, etc.

[0058] All of the above references, including US Provisional Application No. 61/527406, filed August 25, 2011, entitled “MOBILE SOLUTION FOR THE SIGNATURE AND RETENTION OF THIRD PARTY DOCUMENTS”; US Provisional Application No. 61/552,359, filed on October 27, 2011, entitled “MOBILE SOLUTION FOR THE IMPORT AND SIGNATURE OF DOCUMENTS WITH ELECTRONIC SIGNATURE BY THIRD PARTIES”; and US Patent No. 13/595,876, filed August 27, 2012, entitled “MOBILE SOLUTION FOR THE SIGNATURE AND RETENTION OF THIRD PARTY DOCUMENTS” are hereby incorporated by reference in their entirety. Where a definition or use of a term in an incorporated reference is inconsistent with or contrary to the definition or use of that term provided herein, the definition or use of that term provided herein is sovereign.

[0059] Although the preferred embodiment of the invention has been illustrated and described, as noted above, many changes can be made without departing from the spirit and scope of the invention. Consequently, the scope of the invention is not limited by the description of the preferred embodiment. Rather, the invention is to be fully determined by reference to the following claims.

Claims (10)

1. Method to facilitate electronic signatures on a client device that is operated by a subscriber, and which is communicatively coupled to a camera, to capture the image of a signed document, characterized by the fact that it comprises: - storing the captured image in a remote electronic signature service; - associate the image stored in the remote electronic signature service with the subscriber's electronic signature; - display, in the user interface, a menu of signature options to add to the converted electronic signature document; - generate , in response to the signature selection, an electronic signature control on the converted document to receive the subscriber's electronic signature; - capture, in response to the generated electronic signature control, the electronic signature of the subscriber associated with the converted electronic signature document; e- transmit the subscriber's electronic signature to the remote electronic signature service, to be stored, in association with the converted electronic signature document, in the remote electronic signature service. 2. Method according to claim 1, characterized in that the image capture of a signed document includes the camera image data, representing at least one page of a signed document. 3. Method according to claim 1, characterized in that the captured image of the first page of a signed document further comprises: - capturing the image representing a second page of the signed document; - storing the captured image in a service electronic signature as part of a converted electronic signature document. 4. Method according to claim 1, characterized in that the remote electronic signature service provides access to the stored electronic signature document. 5. Method according to claim 4, characterized in that the remote electronic signature service transmits to a recipient a message that includes a copy of the document with an electronic signature. 6. Method according to claim 4, characterized in that the message transmitted by the remote electronic signature service includes a link that can be used by the recipient to view the electronically signed document and/or the associated electronic signature of the subscriber. 7. Method according to claim 1, characterized in that the capture of the image of the signed document includes the capture of the image of the paper document. 8. Method according to claim 1, characterized in that, through a web browser, through the client device, you can access the document with electronic signature stored in the remote electronic signature service and associate it with the electronic signature of the subscriber. 9. Method according to claim 1, characterized in that it provides for the automatic completion of the form fields in the document with electronic signature based on the entries of previous forms made by the subscriber. 10. Computer-readable memory characterized by the fact that it contains a set of instructions that, when executed, perform the method as defined in any one of claims 1 to 9.

Images