Source: http://patents.com/us-9369455.html
Timestamp: 2019-08-25 18:24:04
Document Index: 629412600

Matched Legal Cases: ['Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61', 'Application No. 61']

US Patent # 9,369,455. Computerized method and system for managing an email input facility in a networked secure collaborative exchange environment - Patents.com
United States Patent 9,369,455
Huang , et al. June 14, 2016
Huang; William (Weston, FL), Rozin; Liviu (Bedford, MA), Fieweger; James Andrew (Fairfield, CT)
Intralinks, Inc. (New York, NY)
Family ID: 1000001910382
14/828,896
US 20150358308 A1 Dec 10, 2015
13871593 Apr 26, 2013 9148417
Current CPC Class: H04L 63/08 (20130101); G06F 21/32 (20130101); G06F 21/64 (20130101); G06Q 10/10 (20130101); H04L 9/3231 (20130101); H04L 51/046 (20130101); H04L 63/0407 (20130101); H04L 63/0861 (20130101); H04L 63/104 (20130101); H04L 63/126 (20130101); H04L 65/403 (20130101); H04L 67/306 (20130101); G06F 2221/032 (20130101); G06F 2221/2101 (20130101); G06F 2221/2149 (20130101); H04L 2209/463 (20130101)
Current International Class: G06F 7/04 (20060101); H04L 29/08 (20060101); G06F 21/32 (20130101); G06F 21/64 (20130101); G06Q 10/10 (20120101); H04L 12/58 (20060101); H04L 29/06 (20060101); H04L 9/32 (20060101)
Field of Search: ;726/4,3
7509490 March 2009 Hsu
7752269 July 2010 Chan
8787579 July 2014 Relyea et al.
2004/0133775 July 2004 Callas
2004/0230820 November 2004 Hui Hsu
2006/0053280 March 2006 Kittle
2010/0161961 June 2010 Beigelman
2011/0202756 August 2011 West
2012/0297468 November 2012 Bharadwaj Subramanya
2013/0054514 February 2013 Barrett-Kahn et al.
2014/0235179 August 2014 George et al.
"Cimage Content Lifecycle Management", available at: http://web.archive.org/web/20010205074400/www.cimage.com/products/e31inde- x.html, retrieved on Sep. 23, 2001, 1 page. cited by applicant .
This application is a continuation application of U.S. patent application Ser. No. 13/871,593 filed on Apr. 26, 2013. U.S. patent application Ser. No. 13/871,593 claims the benefit of the following provisional applications: U.S. Patent Application No. 61/639,576 filed Apr. 27, 2012; U.S. Patent Application No. 61/680,115 filed Aug. 6, 2012; U.S. Patent Application No. 61/702,587 filed Sep. 18, 2012; U.S. Patent Application No. 61/715,989 filed Oct. 19, 2012; U.S. Patent Application No. 61/734,890 filed Dec. 7, 2012, and U.S. Patent Application No. 61/783,868 filed Mar. 14, 2013. Each of the above applications is hereby incorporated by reference in its entirety.
1. A method for managing a networked secure collaborative computer data exchange environment, the method comprising: establishing, by a secure exchange server controlled by an intermediate business entity, a user login data authentication procedure that allows at least one of a plurality of users of a plurality of business entities to access the secure exchange server, wherein communications between the secure exchange server and the plurality of users is through a communications network; storing, by the secure exchange server, at least one user login authentication data for each of the plurality of users; receiving content from a first of the plurality of users of a first business entity of the plurality of the business entities; by the secure exchange server, permitting access to the received content for a subset of the plurality of users through an exchange content access facility, wherein the exchange content access facility is managed by at least one business entity of the plurality of business entities; granting, by the exchange server, access to the received content to a second of the plurality of users of a second business entity of the plurality of business entities when the secure exchange server receives from the second of the plurality of users its user login authentication data provided that the second of the plurality of users is one of the subset of the plurality of users; and providing a secure email input facility for accepting non-secure email from outside the exchange into the secure collaborative computer data exchange environment, wherein the non-secure email is received and at least one of the non-secure email and the content delivered thereby is stored as secure content in a location of the secure exchange server related to at least one of the sender of the email, the subject line of the non-secure email, the destination address of the email within the exchange, and the content of the email, wherein the email is automatically associated with an area of content on the exchange server based on at least one of the sender of the email, the subject line of the email, the destination address of the email within the exchange, and the content of the email.
7. A method for managing a networked secure collaborative computer data exchange environment, the method comprising: establishing, by a secure exchange server controlled by an intermediate business entity, a client login data authentication procedure that allows at least one client computing device of a plurality of client computing devices operated by users of a plurality of business entities to access the secure exchange server, wherein communications between the secure exchange server and the plurality of client computing devices is through a communications network; storing, by the secure exchange server, at least one client login authentication data for each of the plurality of client computing devices; receiving content from a first of the plurality of client computing devices operated by a user of a first business entity of the plurality of business entities; by the secure exchange server, permitting access to the received content for a subset of the plurality of computing devices through an exchange content access facility, wherein the exchange content access facility is managed by at least one business entity of the plurality of business entities; granting, by the exchange server, access to the received content to a second of the plurality of client computing devices operated by a user of a second business entity of the plurality of business entity when the secure exchange server receives from the second of the plurality of client computing devices its client login authentication data provided that the second of the plurality of client computing devices is one of the subset of the plurality of computing devices; and providing a secure email input facility for accepting non-secure email from outside the exchange into the secure collaborative computer data exchange environment, wherein the non-secure email is received and at least one of the non-secure email and the content delivered thereby is stored as secure content in a location of the secure exchange server related to at least one of the sender of the email, the subject line of the non-secure email, the destination address of the email within the exchange, and the content of the email; the method further including: providing an electronic signature facility for managing a process of signing the received content by a user of at least one of the subset of the plurality of computing devices, wherein the electronic signature facility provides for secure viewing of the received content as presented to a signing user through a computer display of the signing user's computing device.
FIG. 2 shows further details in connection with the server software that may be readily incorporated in the host server 102, including a community facility 202, amendment voting facility 204, e-signing facility 208, dashboard facility 210, email-in facility 212, viewer facility 214, mobile device interface facility 218, network service facility 220, distribution facility 222, interface facility 224, format conversion facility 228, sign-on facility 230, encryption facility 232, usage facility 234, syndication facility 238, transaction identification facility 240, link facility 242, user authorization facility 244, authorized reader facility 248, authorized editor facility 250, notarization facility 252, multimedia facility 254, comment facility 258, and email facility 260.
Referring to FIG. 4, the amendment voting facility 204 may provide for managing, integrating, and facilitating a process where agency clients executing a transaction (e.g. a syndicated loan) may vote on modifications or amendments to a transaction or transaction content, including an auditable process 402, aggregated vote metrics 404, centralized vote processing 408, and the like. The auditing process 402 may utilize vote documentation, consent forms, signature page tracking, digital distribution, vote collection, and signature page submission, and the like, where the these documents may be fully traceable. The distribution, vote collection and signature page submission may all occur online, speeding the process and better ensuring transparency. Aggregating vote metrics 404 may utilize weighted voting calculations for consent percentage, visualization of responses (e.g. which lenders have done what), and the like, where vote calculations may be weighted by commitment percentage, and where a visual display of user responses may make it easy to see which users have taken action, and what those actions are. Centralized vote processing 408 may include sending reminder alerts, completion of approval tasks, completion of a vote, and the like. Features of the amendment voting facility 404 may include amendment templates for quick configuration and launch, lender voting that includes signature page collection (e.g. with electronic submission of signature pages), task lists for consent, an amendment voting user interface 410 to track progress and statistics (e.g. group tracking, simplified reminders, export for vote tally and reporting), amendments within existing exchanges, and the like.
In embodiments, the amendment voting facility may allow for the naming of an amendment vote, a date for the vote, a vote distribution, inclusion of associated documents, facility for signature providing page submissions, inclusion of instructions to voters, a process of approval, a step for outside counsel to review, and the like. Once the announcement for the vote is sent out, an administrator agent may be able to view the tasks that have gone out, to what individuals and groups, and the status of the voting. Features of the amendment voting facility may include import and export of commitment data, support of amendment vote collection workflow, creation of vote template configurations, configuration of election forms, display of an amendment voting graphical user interface dashboard, configuration of signature pages, access for an administrator to complete tasks, facility for client-specific amendment vote definition, and the like. Import and export may include users ability to populate a deal structure automatically (e.g., from a source file), create a list of lenders groups and tranches commitment information on a new deal exchange, reconcile an existing deal structure, generate reports (e.g. listing commitment amounts for each participant, updating commitments, and the like. Support of amendment vote collection workflow may include support of a plurality of different amendment types and allow users to create process definitions available for run-time execution, and the like, where the different amendment types may include a simple yes-no, a yes-no with signature, consent-no consent, amend and extend, and the like. Amendment vote collection workflow may include specification of due dates and time, collection of election options, distribution of documentation, the ability to edit voting parameters, and the like. Creation of vote template configurations may include support of vote template configuration creation, such as to encapsulate the amendment vote process for document control management, including users setting up owners, monitors, and vote elements once, and reusing for subsequent votes; providing consistent language and instructions and documentation across transactions and votes; setting up vote types that may be adjusted as-needed, and the like. The election form may be configured to allow users to dynamically generate election forms based on group participant relationships (e.g. lenders only having visibility to cases they have access to). Display of an amendment voting dashboard may include view of a list of multiple amendments initiated for a particular transaction, view of details of the process (e.g., list of lenders and their related status such as progress against a task), view of participant contact and additional information, and the like. Configuration of the signature page may include custom text, a logo, and the like, where users may update and maintain their own custom signature pages, such as for all transactions, per transaction, per vote, and the like.
Referring to FIG. 8, the viewer facility 214 may provide for a secure viewing 802 protection of documents from unauthorized viewing, printing, saving, and the like, such as without having to install custom client software (e.g. without installing anything beyond Adobe Flash). Documents in certain formats, such as Microsoft Office products, PDF documents, and the like, may be supported for protection. For example, for a PDF document a security warning may appear that a user is only allowed to view the document. However, if the user tries to print the screen, the screen may distort, such as transitioning to a fuzzy state. In embodiments, the user may need to hold the enter key down to make the document viewable. The user may be able to page up and down, rotate, zoom, and the like. The system may provide for watermarking the document so that if a user is permitted to print screen, the document will print with the watermarking. The viewer facility may also include functions such as viewing annotations 804 in the viewer, connectivity with the e-signing facility 208 (e.g. with a `stamping` tool), document visibility based on face detection, document protection from eavesdroppers (e.g. automatic limitation of document viewing, also referred herein as spotlighting, based on detection of a second face), granular/page level document access reports 808, document protection 810 using facial recognition based encryption, text to voice feature 812 (e.g. such as in Apple.RTM. Ski), hand gesture based controls 814 (e.g. scrolling control based on hand-fist movement), real-time white-boarding 818, secure video chat 820 (e.g. one-on-one, group), and the like. In embodiments, the viewer facility may include an audio comment component, such as to allow a user to input comments into the document through audio dictation, to have the viewer facility play back the comments in audio, to provide audio output for various aspects of the document, and the like.
The methods and systems described herein may be deployed in part or in whole through network infrastructures. The network infrastructure may include elements such as computing devices, servers, routers, hubs, firewalls, clients, personal computers, communication devices, routing devices and other active and passive devices, facilities and/or components as known in the art. The computing and/or non-computing device(s) associated with the network infrastructure may include, apart from other components, a storage medium such as flash memory, buffer, stack, RAM, ROM and the like. The processes, methods, program codes, instructions described herein and elsewhere may be executed by one or more of the network infrastructural elements.
Previous Patent US 9,369,454 | Next Patent US 9,369,456