USRE49769E1 - Secure electronic document delivery system - Google Patents

Secure electronic document delivery system Download PDF

Info

Publication number
USRE49769E1
USRE49769E1 US16/850,934 US202016850934A USRE49769E US RE49769 E1 USRE49769 E1 US RE49769E1 US 202016850934 A US202016850934 A US 202016850934A US RE49769 E USRE49769 E US RE49769E
Authority
US
United States
Prior art keywords
recipient
file
computing system
message
authorization
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US16/850,934
Inventor
Stephen Cassar
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Individual
Original Assignee
Individual
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Individual filed Critical Individual
Priority to US16/850,934 priority Critical patent/USRE49769E1/en
Application granted granted Critical
Publication of USRE49769E1 publication Critical patent/USRE49769E1/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/04Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/083Network architectures or network communication protocols for network security for authentication of entities using passwords
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/08Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0853Network architectures or network communication protocols for network security for authentication of entities using an additional device, e.g. smartcard, SIM or a different communication terminal
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/16Implementing security features at a particular protocol layer
    • H04L63/168Implementing security features at a particular protocol layer above the transport layer
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00Network architectures or network communication protocols for network security
    • H04L63/18Network architectures or network communication protocols for network security using different networks or channels, e.g. using out of band channels

Definitions

  • the present invention is in the technical field of electronic file and message delivery. More particularly, the present invention is in the technical field of the secure transmission of links to sensitive electronic documents that are housed in a cloud-based internet environment.
  • the known art does not allow the security provided by the present invention.
  • the present invention provides a solution that requires multiple authentication systems while avoiding storage of documents by third parties.
  • the present invention allows a sender to maintain responsibility of the sender's files while avoiding storing sensitive information on a server or third party computer.
  • the present invention is needed to provide a unique authentication system for sharing documents, information, and messages.
  • the present invention transmits information and data through a network such as the Internet that allows communication between the sender and a server and between a server and the recipient.
  • the system communicates via at least two different messages transmitted through two different communication paths, electronic mail and a messaging service.
  • the two different transmission paths of the communications require the recipient to access two different messages to enable access to the file. Accessing the two different messages requires two separate authentications for accessing the messages. Without accessing both messages, the recipient cannot access the file identified by the sender.
  • the present invention utilizes a computing device, including but not limited to a server, that receives information from the sender.
  • the sender supplies the recipient information and the file information to the server.
  • the sender inputs the information via a web site to be transmitted to the server.
  • Other embodiments may allow the user to input the information into a program or application to transmit and/or access the document.
  • the server stores the file information and the recipient information within the server.
  • the server then sends a first authentication message to the recipient identified in the recipient information.
  • the recipient accesses the first authentication message which causes a second authentication message that includes an authorization code to be sent.
  • the user enters the authorization code to access the document identified by the sender.
  • FIG. 1 is an environmental view showing one embodiment of the present invention
  • FIG. 2 is a flow chart of one embodiment of the present invention.
  • FIG. 5 is a view showing one routine of one embodiment of the present invention.
  • FIG. 7 is a flow chart showing one routine of one embodiment of the present invention.
  • FIG. 8 is a view of an input screen accepting the file information and recipient information
  • FIG. 9 is a view of a confirmation page indicating that the message was sent successfully
  • FIG. 11 is a view of a verification page
  • FIG. 12 is a view of a second authentication message of one embodiment of the present invention showing the authorization code to be entered into the verification page of FIG. 11 .
  • FIG. 1 illustrates a diagram of one embodiment of the document delivery system and authentication system.
  • the document delivery system uses at least one computing device, including but not limited to a server, such as server 100 , potentially more servers 102 , to accept information from both the sender 104 and recipient 106 .
  • the at least one server 100 , 102 also communicates with the recipient to provide information to the recipient, such as the file and/or file location.
  • An additional server 102 may provide the second communication to the recipient.
  • the document delivery system and authentication system of one embodiment of the invention includes at least one computing device such as computing device 104 , 106 , 107 , 109 , having a processor attached to memory, e.g., random access memory (RAM), and electronic storage media such as a hard disk, flash memory, etc.
  • the computing device includes an input device such as a touch screen, a mouse, a track ball, a track pad including the track pads found on Blackberry® phones, a button input system, a keyboard, and/or other known input systems that enable a user to enter information.
  • FIG. 2 shows a flow chart showing one embodiment of the present invention.
  • the sender accesses a website or a program that requests the file information and recipient information at Request Step 108 .
  • the sender 126 identifies whether the document will be a file, a website, or a message. If the document is a file or website, the sender 126 provides document link information, such as a unique resource locator (URL), address information, a web address, identifying the location of the file and/or web site. This link information may refer to storage on the sender's system or another location in which the file or website is located.
  • URL unique resource locator
  • This link information may refer to storage on the sender's system or another location in which the file or website is located.
  • the sender 126 may select to send a message to the recipient.
  • the sender 126 enters the message into sender computing device 104 .
  • the sender computing device 104 securely transmits the message as the file information to the server 100 .
  • the server 100 generates a web page with a document location. The document location created by server 100 is then sent to recipient 128 for accessing the message.
  • the sender 126 also provides recipient information at Step 110 .
  • the recipient information must include recipient contact information for contacting the recipient 128 .
  • the system requires at least one method of contacting the recipient.
  • Another embodiment requires two sets of contact information providing two methods of contacting the recipient.
  • the recipient information could also include the recipient name to personalize the messages sent to the recipient 128 .
  • the sets of recipient contact information may include the recipient's email address and a phone number. Other embodiments may include an additional phone number(s), a pager number, fax number, or other contact information for the recipient 128 .
  • Each set of contact information provides a communication path for contacting the recipient through a transmission delivery.
  • the sender computing device 104 securely transmits the file information and the recipient information to server 100 .
  • the server 100 After receiving the file information and recipient information, the server 100 encrypts the file information and the recipient information at step 114 to be stored.
  • the server 100 then transmits a first authorization message to the recipient using the recipient information.
  • the server 100 sends the first authorization message via a first communication path from a first set of recipient contact information.
  • this first authorization message is transmitted via electronic mail.
  • the first authorization message includes a verification link, such as a URL or web address, sent to the recipient at Step 116 to be accessed at Step 118 .
  • the verification link leads to a verification page, such as a verification website, for entry of an authorization code.
  • the first authorization message may also include instructions informing the recipient 128 that a second authorization message, such as a text message, that provides an authorization code will be sent to the recipient 128 from a second communication path, such as a phone number.
  • the system validates the identity of the recipient at the time the recipient accesses the verification link found in the first authorization message. Accessing the verification link at step 118 provides the first authenication required to access the file as the recipient has proven that recipient has access to the first authorization message. To provide additional security, the document delivery system requires a second authorization level before providing the recipient 128 with access to the file.
  • FIG. 4 shows the process of providing the file information to the system.
  • the system verifies the document type at Document Type Query 130 .
  • the system determines whether a file should be generated depending on the document type. If the user submits file link information as the file information, the system will accept the file link information at Step 132 .
  • the system will eventually forward the file link information provided by the sender to the recipient to access the document.
  • the system provides a method of requiring the user to access two separate authentication messages in order to provide access to a file, including but not limited to a document, file, message, image, other files, etc.
  • One server or multiple servers may transmit the different authentication messages to the users. These authentication messages may be electronic mail or other messages.
  • the use of two different delivery systems authenticates that the user has access to two separate communication systems that should only be accessible to the user. While the use of a web browser viewing a web site has been described above, it is understood that a user could access a program or application for transmitting and receiving the documents.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Information Transfer Between Computers (AREA)

Abstract

The secure electronic document delivery system enables a sender to identify file information and recipient information to be sent to a recipient. The system utilizes an authentication system requiring access to two different authentication messages, both access to electronic mail and access to a message sent to the recipient's phone. The two authentication messages are transmitted via two different communication paths thus requiring the recipient to access two different types of communications. Without accessing both messages, the recipient cannot access the document identified by the sender.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
This application is a Broadening Reissue of U.S. Pat. No. 9,948,627 (previously U.S. application Ser. No. 14/329,918 filed on Jul. 12, 2014) that issued on Apr. 17, 2018 that claims priority to and is a continuation-in-part of U.S. Patent Application No. 61/845,509 filed on Jul. 12, 2013 entitled SECURE ELECTRONIC DOCUMENT DELIVERY SYSTEM which is hereby incorporated by reference.
STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT
Not Applicable.
REFERENCE TO A MICROFICHE APPENDIX
Not Applicable.
RESERVATION OF RIGHTS
A portion of the disclosure of this patent document contains material which is subject to intellectual property rights such as but not limited to copyright, trademark, and/or trade dress protection. The owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office patent files or records but otherwise reserves all rights whatsoever.
BACKGROUND OF THE INVENTION I. Field of the Invention
The present invention is in the technical field of electronic file and message delivery. More particularly, the present invention is in the technical field of the secure transmission of links to sensitive electronic documents that are housed in a cloud-based internet environment.
Conventional methods of electronic document transmission involve emailing a link to the document or file using a standard plain text email. It is difficult to secure these email messages as they are relayed through multiple servers until they reach the intended recipient. Further, these emails are typically stored by each of the servers as the emails are relayed through for a long period of time. These documents are then archived further compromising these sensitive documents to unintended recipients for years.
The known art does not allow the security provided by the present invention. The present invention provides a solution that requires multiple authentication systems while avoiding storage of documents by third parties. Thus, the present invention allows a sender to maintain responsibility of the sender's files while avoiding storing sensitive information on a server or third party computer.
Therefore, the present invention is needed to provide a unique authentication system for sharing documents, information, and messages.
SUMMARY OF THE INVENTION
The present invention utilizes an authentication system implemented in both hardware and software that enables a sender to transmit information, documents, messages, etc. to a recipient. The present invention uses at least one computing device, such as a computer, server, tablet, smart phone, etc., accessible by the sender and the recipient.
The present invention transmits information and data through a network such as the Internet that allows communication between the sender and a server and between a server and the recipient. In one embodiment, the system communicates via at least two different messages transmitted through two different communication paths, electronic mail and a messaging service. The two different transmission paths of the communications require the recipient to access two different messages to enable access to the file. Accessing the two different messages requires two separate authentications for accessing the messages. Without accessing both messages, the recipient cannot access the file identified by the sender.
In one embodiment, the recipient may use a cellular phone capable of receiving messages, such as short message service, Apple's iMessage service, text messaging services, and other messaging services. The system of one embodiment of the present invention sends a message to the recipient that will provide the recipient with information required to access the document.
Software:
The present invention utilizes a computing device, including but not limited to a server, that receives information from the sender. The sender supplies the recipient information and the file information to the server. In one embodiment, the sender inputs the information via a web site to be transmitted to the server. Other embodiments may allow the user to input the information into a program or application to transmit and/or access the document. The server stores the file information and the recipient information within the server. The server then sends a first authentication message to the recipient identified in the recipient information. The recipient accesses the first authentication message which causes a second authentication message that includes an authorization code to be sent. The user enters the authorization code to access the document identified by the sender.
It is an object of the present invention to securely deliver documents and other information to a recipient.
It is another object of the present invention to avoid storage of a document by a third party.
It is another object of the present invention to require multiple authentications for identifying the recipient to confirm that the proper recipient receives the file.
It is another object of the present invention to require multiple communication paths to authenticate the identity of the recipient.
It is another object of the present invention to provide a secure messaging system.
These and other objects and advantages of the present invention, along with features of novelty appurtenant thereto, will appear or become apparent by reviewing the following detailed description of the invention.
BRIEF DESCRIPTION OF THE DRAWINGS
In the following drawings, which form a part of the specification and which are to be construed in conjunction therewith, and in which like reference numerals have been employed throughout wherever possible to indicate like parts in the various views:
FIG. 1 is an environmental view showing one embodiment of the present invention;
FIG. 2 is a flow chart of one embodiment of the present invention;
FIG. 3 is a flow chart showing one routine of one embodiment of the present invention;
FIG. 4 is a flow chart showing one routine of one embodiment of the present invention;
FIG. 5 is a view showing one routine of one embodiment of the present invention;
FIG. 6 is a flow chart showing one routine of one embodiment of the present invention;
FIG. 7 is a flow chart showing one routine of one embodiment of the present invention;
FIG. 8 is a view of an input screen accepting the file information and recipient information;
FIG. 9 is a view of a confirmation page indicating that the message was sent successfully;
FIG. 10 is a view of a first authentication message of one embodiment of the present invention;
FIG. 11 is a view of a verification page; and
FIG. 12 is a view of a second authentication message of one embodiment of the present invention showing the authorization code to be entered into the verification page of FIG. 11 .
DETAILED DESCRIPTION
FIG. 1 illustrates a diagram of one embodiment of the document delivery system and authentication system. The document delivery system uses at least one computing device, including but not limited to a server, such as server 100, potentially more servers 102, to accept information from both the sender 104 and recipient 106. The at least one server 100, 102 also communicates with the recipient to provide information to the recipient, such as the file and/or file location. An additional server 102 may provide the second communication to the recipient.
The document delivery system and authentication system of one embodiment of the invention includes at least one computing device such as computing device 104, 106, 107, 109, having a processor attached to memory, e.g., random access memory (RAM), and electronic storage media such as a hard disk, flash memory, etc. In one embodiment, the computing device includes an input device such as a touch screen, a mouse, a track ball, a track pad including the track pads found on Blackberry® phones, a button input system, a keyboard, and/or other known input systems that enable a user to enter information.
Continuing to refer to FIG. 1 , a user, such as a sender or recipient, accesses the computing device, such as computing devices 104, 106, 107, 109. As stated above, the computing device 104, 106, 107, 109 may be a computer, a smart phone, a tablet pc, or other computer device. In one embodiment, the computing device 104, 106, 107, 109 may be a smart phone or other computing device that can access both servers 100, 102. In another embodiment in which a phone cannot access the Internet, the recipient, such as Recipient B, may need a phone such as Recipient's phone 109 to accept a message and Recipient's computing device 107 for accepting a message. These computing devices 104, 106, 107 can send and receive data from servers 100, 102. The network enables communication between the computing devices 104, 106, 107, phone 109, and servers 100, 102.
FIG. 2 shows a flow chart showing one embodiment of the present invention. In one embodiment, the sender accesses a website or a program that requests the file information and recipient information at Request Step 108. The sender 126 identifies whether the document will be a file, a website, or a message. If the document is a file or website, the sender 126 provides document link information, such as a unique resource locator (URL), address information, a web address, identifying the location of the file and/or web site. This link information may refer to storage on the sender's system or another location in which the file or website is located. By storing the file and/or website on the sender's system, the user maintains control of the files to avoid relying on third party's interests in the sender's file and the security of the third party's system.
In another embodiment, the sender 126 may select to send a message to the recipient. When sending a message, the sender 126 enters the message into sender computing device 104. Instead of sending the message as an email which could be stored in different email servers while being transmitted to the recipient 128, the sender computing device 104 securely transmits the message as the file information to the server 100. The server 100 generates a web page with a document location. The document location created by server 100 is then sent to recipient 128 for accessing the message.
The sender 126 also provides recipient information at Step 110. The recipient information must include recipient contact information for contacting the recipient 128. The system requires at least one method of contacting the recipient. Another embodiment requires two sets of contact information providing two methods of contacting the recipient. The recipient information could also include the recipient name to personalize the messages sent to the recipient 128. The sets of recipient contact information may include the recipient's email address and a phone number. Other embodiments may include an additional phone number(s), a pager number, fax number, or other contact information for the recipient 128. Each set of contact information provides a communication path for contacting the recipient through a transmission delivery.
At Step 112, the sender computing device 104 securely transmits the file information and the recipient information to server 100. After receiving the file information and recipient information, the server 100 encrypts the file information and the recipient information at step 114 to be stored.
The server 100 then transmits a first authorization message to the recipient using the recipient information. The server 100 sends the first authorization message via a first communication path from a first set of recipient contact information. In one embodiment, this first authorization message is transmitted via electronic mail. The first authorization message includes a verification link, such as a URL or web address, sent to the recipient at Step 116 to be accessed at Step 118. In one embodiment, the verification link leads to a verification page, such as a verification website, for entry of an authorization code. The first authorization message may also include instructions informing the recipient 128 that a second authorization message, such as a text message, that provides an authorization code will be sent to the recipient 128 from a second communication path, such as a phone number. Providing such information enables the recipient to confirm that the authorization code was sent by the appropriate source and communication path. The instructions also provide information instructing the recipient of the location at which the authorization code should be entered. The second authorization message may be transmitted through the first communication path or a second communication path from a second set of recipient contact information.
The system validates the identity of the recipient at the time the recipient accesses the verification link found in the first authorization message. Accessing the verification link at step 118 provides the first authenication required to access the file as the recipient has proven that recipient has access to the first authorization message. To provide additional security, the document delivery system requires a second authorization level before providing the recipient 128 with access to the file.
After accessing the verification page from the verification link identified in the first authorization message, the recipient 128 is prompted to enter an authorization code to validate the second authorization level. The recipient 128, when accessing the verification link, accesses a server 100, 102 that activates the transmission of a second authorization message to the recipient 128. The second authorization message is sent from a source that was previously identified in the first authorization message. The recipient may verify the authorization code by comparing the source of the second authorization message to the source identified in the first authorization message. If the sources do not match, the recipient may ignore the authorization code. If the sources match, the recipient enters the authorization code to gain access. The server then provides the recipient with an access link to the file. In one embodiment, the server forwards the recipient to the file identified in the access link.
In one embodiment of the present invention, the first authorization message is sent through a first transmission delivery such as electronic mail. The second authorization message is sent through a second transmission delivery such as a phone messaging system such as short message service, Apple's iMessage service, text messaging services, and other messaging services. The first transmission delivery may be delivered by a different transmission service than the second transmission delivery. Transmitting the authorization messages via different communication paths requires that the recipient accesses two separate messages sent through two different transmissions. Thus, the recipient must authenticate the recipient's identity on two separate occasions. The two separate authentications by the recipient prior to providing access to the file greatly increases the security of the system.
FIG. 3 shows a method of securely sending a file from a sender 126 to a recipient. The sender 126 provides the file information, such as a URL, link, web address, or the message to be delivered via a generated file (the message file), and recipient information 110 to the routine 114. The system encrypts the file information and generates a secure access link that is sent to the recipient 128. The sender 126 provides the file information and recipient information at Step 110. As indicated above, the file information may be in the form of an address, a web address, a URL. The file information may also be a message entered into the system by the sender. The system then generates a message file that includes the message from the sender and creates a link to the document. After receiving the file information and recipient information, the system sends a secure link to the recipient 128 to be accessed by the recipient 128.
FIG. 4 shows the process of providing the file information to the system. The system verifies the document type at Document Type Query 130. The system determines whether a file should be generated depending on the document type. If the user submits file link information as the file information, the system will accept the file link information at Step 132. The system will eventually forward the file link information provided by the sender to the recipient to access the document.
If the user submits a message as the file information, the user may input a message, select a saved message to be sent, and/or type a message. The server accepts the message at Step 134 from the sender 126. The system will then generate a message file at Step 136 that includes the message and provide an access link to the message file to the recipient. The system will then Encrypt the Information (both the recipient information and file information) and generate the Secure Access Link at Step 114.
FIG. 5 shows the routine by which the system encrypts the information and generates a secure access link at Step 114. The system encrypts the File Link Information 144 and Encrypts Recipient's Information 146, 148. In one embodiment, the system encrypts the Recipient's contact information, including but not limited to the Recipient's email address and cell phone number. After encrypting the information, the system stores the encrypted information at Step 150.
FIG. 6 shows the routine by which the recipient 128 accesses the file information. The system has previously sent the first authorization message that includes a secure link. The recipient 128 clicks on the secure link to cause the authentication code to be sent to the recipient via the second authorization message. As previously indicated, the first authorization message is delivered via a different transmission system, such as a different communication path, than the second authorization message. The recipient 128 inputs the authorization code delivered in the second authorization message at the verification page from the verification link identified in the first authorization message. After the recipient 128 enters the proper authorization code, the system provides the recipient with the access link to provide the recipient with the file information and the file identified by the sender 126.
FIG. 7 provides additional information concerning the Authenticate SMS Access Code 138. The recipient 128 clicks the encrypted access link at step 152 that is sent in the first authorization message. The system generates an authorization code that is associated with the recipient and the file information to be sent to the recipient at Step 154. The authorization code is then sent to the recipient 128. The recipient 128 enters the authorization code at the verification page from the verification link provided in the first authorization message. If the authorization code is incorrectly entered at Correct Code Query 156, the system does not allow access to the file. If the correct authorization code is entered at Correct Code Query 156, the system will decrypt the file information at Step 158 to provide the recipient with the file.
The system provides a method of requiring the user to access two separate authentication messages in order to provide access to a file, including but not limited to a document, file, message, image, other files, etc. One server or multiple servers may transmit the different authentication messages to the users. These authentication messages may be electronic mail or other messages. The use of two different delivery systems authenticates that the user has access to two separate communication systems that should only be accessible to the user. While the use of a web browser viewing a web site has been described above, it is understood that a user could access a program or application for transmitting and receiving the documents.
From the foregoing, it will be seen that the present invention is one well adapted to obtain all the ends and objects herein set forth, together with other advantages which are inherent to the structure.
It will be understood that certain features and subcombinations are of utility and may be employed without reference to other features and subcombinations. This is contemplated by and is within the scope of the claims.
As many possible embodiments may be made of the invention without departing from the scope thereof, it is to be understood that all matter herein set forth or shown in the accompanying drawings is to be interpreted as illustrative and not in a limiting sense.

Claims (19)

What is claimed is:
1. A secure electronic document delivery system method for providing a file from a sender's computer system to a recipient via a delivery computing system wherein the user accesses the file via an access link to the file on the sender's computer system, the delivery system method comprising:
the sender storing the file at a first location on the sender's computer system;
the sender submitting an access link that identifies the first location at which the file is stored to the delivery computing system without transferring the file to the delivery computing system, wherein the delivery computing system is denied access to the file at the first location;
the delivery computing system encrypting an the access link identifying the first location of the file to be transmitted to the recipientwherein the sender inputs the access link to the computing system;
the delivery computing system storing the encrypted access link to the first location of the file;
the delivery computing system associating the recipient with an email address for transmitting information to the recipient and a phone number for transmitting information to the recipient;
the delivery computing system transmitting a first authorization message to the recipient via electronic mail, the first authorization message identifying a verification link to a verification page, wherein the verification page requests entry of an authorization code to access the file identified by the access link;
the delivery computing system transmitting a second authorization message to the recipient via a text message to the phone number after the recipient accesses the verification page, the second authorization message providing an the authorization code to the recipient for accessing the file, wherein accessing the verification page triggers initiates the transmission of the text message of the second authorization message with the authorization code to the recipient;
wherein the electronic mail to the recipient of the first authorization message identifies a phone number transmitting the text message of the second authorization message informing the recipient of the authorization code
the delivery computing system providing automatically directing the recipient with to the first location, wherein the recipient accesses the file located at the first location available at the access link at the time the delivery computing system directs the recipient accesses the access link such that the computing system provides access to the file to the recipient without uploading the file to a second location to the first location;
the delivery computing system requiring entry of the authorization code at the verification page wherein entry submission of the authorization code at the verification page automatically directs the recipient from the verification page to the file located at the first location ;
wherein the computing system decrypts the encrypted access link after the recipient enters the authorization code at the verification page for opening the file.
2. The method of claim 1, wherein the delivery computing system automatically forwards the recipient from the verification page to the file located at the access link upon submission of the authorization code at the verification page without requiring additional user input, wherein the access link is different than the verification link.
3. The method of claim 1, wherein the first location provides the file without uploading to a second storage at a second location that is initially accessed by the recipient, wherein the delivery computing system provides the recipient with the file located at the first location without the delivery computing system accessing the file, wherein the verification link is different than the access link.
4. The method of claim 1, wherein the electronic mail to the recipient of the first authorization message identifies a confirmation phone number transmitting the text message of the second authorization message informing the recipient of the authorization code.
5. The method of claim 1, wherein the first authorization message provides the verification link without identifying the location of the file.
6. The method of claim 5, wherein the first authorization message does not provide the file in the electronic mail of the first authorization message.
7. The method of claim 1 further comprising:
a web browser accessing the verification page, wherein the web browser accessing the verification page initiates the transmission of the text message of the second authorization message;
wherein the delivery computing system automatically directs the web browser from the verification page to the first location upon submission of the authorization code to the delivery computer system at the verification page.
8. A secure electronic document delivery method for providing a message from a sender to a recipient via a delivery computing system wherein the recipient accesses the file via an access link, the method comprising:
the delivery computing system providing a text box for input of the message;
the sender submitting the message into the text box to the delivery computing system to be transmitted to the recipient;
the delivery computing system generating a file that provides the message submitted by the sender into the text box;
the delivery computing system associating the recipient with an email address for transmitting the message to the recipient and a phone number for transmitting the message to the recipient;
the delivery computing system emailing a first authorization message to the email address, the first authorization message identifying a verification link to a verification page;
the delivery computing system transmitting a second authorization message to the phone number via a text message after the verification page is accessed, the second authorization message providing an authorization code to the recipient, wherein accessing the verification page initiates the transmission of the second authorization message with the authorization code to the phone number;
the delivery computing system requiring entry of the authorization code at the verification page prior to providing the recipient with access to the file and the message;
the delivery computing system directing the recipient from the verification page to the file and message upon submission of the authorization code into the verification page.
9. The method of claim 8 further comprising:
the delivery computing system providing the recipient with the access link to the file after submission of the authorization code at the verification page.
10. The method of claim 8 wherein the delivery computing system generates and stores the access link to the file such that the delivery computing system provides access to the file and message via automatically forwarding the recipient from the verification page to the access link.
11. The method of claim 8 wherein the first authorization message identifies a phone number from which the text message of the second authorization message providing the authorization code will be delivered to the recipient.
12. The method of claim 8 further comprising:
a web browser requesting information from the verification page, wherein the web browser requesting information from the verification page initiates the transmission of the text message of the second authorization message;
wherein the delivery computing system automatically directs the web browser from the verification page to the file and the message upon submission of the authorization code to the delivery computer system at the verification page.
13. The method of claim 8, wherein the access link to the file identifies a first location of the file, wherein the access link provides the recipient with access to the file located at the first location, wherein the verification link is different than the access link, wherein the verification page automatically directs the recipient to the file and the message after the recipient submits the authorization code at the verification page without requiring additional input from the recipient.
14. A secure electronic document delivery method for providing a file from a sender to a recipient via a delivery computing system wherein the recipient accesses the file via an access link, the method comprising:
the delivery computing system storing the access link identified by the sender, wherein the access link identifies a location to access the file, wherein the sender submits the access link to the delivery computing system;
wherein the delivery computing system is restricted from accessing the file stored at the access link, wherein the delivery computing system cannot access the file stored at the access link;
the delivery computing system associating the recipient with an email address and a telephone number capable of receiving a text message;
the delivery computing system electronically mailing a first authorization message to the recipient via the email address, the first authorization message identifying a verification link to a verification page,
the delivery computing system transmitting a second authorization message to the recipient via the telephone number, the second authorization message providing an authorization code within the second authorization message received at the phone number;
the delivery computing system requiring entry of the authorization code at the verification page prior to directing the recipient from the verification page to the access link to access the file located at the access link;
the delivery computing system automatically directing the recipient from the verification page to the file located at the access link upon submitting the authorization code at the verification page without requiring additional input from the recipient.
15. The method of claim 14 further comprising:
the user submitting the authorization code at the verification page to access the file located at the access link, wherein the access link refers to a location different than the verification page, wherein the verification page directs the recipient to the file automatically after the recipient submits the authorization code at the verification page;
the delivery computing system providing the recipient with the file available at the access link at the time the recipient accesses the access link identified by the sender.
16. The method of claim 14, wherein the verification link transmitted to the recipient in the first authorization message does not identify the access link, wherein the verification link is different than the access link.
17. The method of claim 14, wherein the delivery computing system transmits the second authorization message to the phone number after the verification page identified in the first authorization message is accessed, wherein accessing the verification page initiates the transmission of the second authorization message with the authorization code to the phone number.
18. The method of claim 14 wherein the access link to the file identifies a first location of the file, wherein the access link provides the recipient with access to the file located at the first location, wherein the verification link is different than the access link, wherein the verification page directs the recipient to the file automatically after the recipient submits the authorization code at the verification page.
19. The method of claim 14, wherein the electronic mail to the recipient of the first authorization message identifies a confirmation phone number transmitting the text message of the second authorization message informing the recipient of the authorization code.
US16/850,934 2013-07-12 2020-04-16 Secure electronic document delivery system Active 2034-09-19 USRE49769E1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US16/850,934 USRE49769E1 (en) 2013-07-12 2020-04-16 Secure electronic document delivery system

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US201361845509P 2013-07-12 2013-07-12
US14/329,918 US9948627B1 (en) 2013-07-12 2014-07-12 Secure electronic document delivery system
US16/850,934 USRE49769E1 (en) 2013-07-12 2020-04-16 Secure electronic document delivery system

Related Parent Applications (1)

Application Number Title Priority Date Filing Date
US14/329,918 Reissue US9948627B1 (en) 2013-07-12 2014-07-12 Secure electronic document delivery system

Publications (1)

Publication Number Publication Date
USRE49769E1 true USRE49769E1 (en) 2023-12-26

Family

ID=61872681

Family Applications (2)

Application Number Title Priority Date Filing Date
US14/329,918 Ceased US9948627B1 (en) 2013-07-12 2014-07-12 Secure electronic document delivery system
US16/850,934 Active 2034-09-19 USRE49769E1 (en) 2013-07-12 2020-04-16 Secure electronic document delivery system

Family Applications Before (1)

Application Number Title Priority Date Filing Date
US14/329,918 Ceased US9948627B1 (en) 2013-07-12 2014-07-12 Secure electronic document delivery system

Country Status (1)

Country Link
US (2) US9948627B1 (en)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10489777B2 (en) * 2016-01-05 2019-11-26 Visa International Service Association Universal access to an electronic wallet
US10924931B2 (en) * 2017-05-24 2021-02-16 Microsoft Technology Licensing, Llc External sharing with improved security
US10944752B2 (en) 2017-05-24 2021-03-09 Microsoft Technology Licensing, Llc Transfer of secure external sharing link
CN109040006A (en) * 2018-06-06 2018-12-18 中融万博网络科技有限公司 A kind of secret letter systems approach

Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030208686A1 (en) * 2002-05-06 2003-11-06 Thummalapally Damodar R. Method of data protection
US20060020799A1 (en) * 2004-07-06 2006-01-26 Kemshall Andrew C Secure messaging
WO2012045908A1 (en) * 2010-10-06 2012-04-12 Aplcomp Oy Arrangement and method for accessing a network service
US20140068262A1 (en) * 2012-09-06 2014-03-06 Zixcorp Systems, Inc., Secure Message Forwarding With Sender Controlled Decryption
US20140165153A1 (en) * 2012-12-06 2014-06-12 Airwatch, Llc Systems and Methods for Controlling Email Access
US20140201848A1 (en) * 2013-01-12 2014-07-17 Pro Softnet Corporation Method for Sharing Multiple Data Items Using a Single URL
US8817959B1 (en) * 2013-05-06 2014-08-26 O'Harlan Ltd System for handling messages and distributing information
US9124641B2 (en) * 2012-11-30 2015-09-01 Prakash Baskaran System and method for securing the data and information transmitted as email attachments
US20150271146A1 (en) * 2012-10-24 2015-09-24 Brian Holyfield Methods and systems for the secure exchange of information
US20160308840A1 (en) * 2010-04-19 2016-10-20 Amaani, Llc System and Method of Efficiently Generating and Transmitting Encrypted Documents

Patent Citations (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030208686A1 (en) * 2002-05-06 2003-11-06 Thummalapally Damodar R. Method of data protection
US20060020799A1 (en) * 2004-07-06 2006-01-26 Kemshall Andrew C Secure messaging
US20160308840A1 (en) * 2010-04-19 2016-10-20 Amaani, Llc System and Method of Efficiently Generating and Transmitting Encrypted Documents
WO2012045908A1 (en) * 2010-10-06 2012-04-12 Aplcomp Oy Arrangement and method for accessing a network service
US20140068262A1 (en) * 2012-09-06 2014-03-06 Zixcorp Systems, Inc., Secure Message Forwarding With Sender Controlled Decryption
US20150271146A1 (en) * 2012-10-24 2015-09-24 Brian Holyfield Methods and systems for the secure exchange of information
US9124641B2 (en) * 2012-11-30 2015-09-01 Prakash Baskaran System and method for securing the data and information transmitted as email attachments
US20140165153A1 (en) * 2012-12-06 2014-06-12 Airwatch, Llc Systems and Methods for Controlling Email Access
US20140201848A1 (en) * 2013-01-12 2014-07-17 Pro Softnet Corporation Method for Sharing Multiple Data Items Using a Single URL
US8817959B1 (en) * 2013-05-06 2014-08-26 O'Harlan Ltd System for handling messages and distributing information

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
Phil Underwood, "Tokenless Two Factor Authentication", Oct. 2012 (see attached document). *
Stephen Crick, "Tokenless Authentication", Sep. 2011 (see attached document). *

Also Published As

Publication number Publication date
US9948627B1 (en) 2018-04-17

Similar Documents

Publication Publication Date Title
USRE49769E1 (en) Secure electronic document delivery system
US9590949B2 (en) Confidential message exchange using benign, context-aware cover message generation
US10681081B2 (en) Secure content and encryption methods and techniques
US9531732B2 (en) Computer implemented system and method for authenticating a sender of electronic data to a recipient
US8837739B1 (en) Encryption messaging system
US20100217984A1 (en) Methods and apparatus for encrypting and decrypting email messages
US20160149705A1 (en) Supporting the decryption of encrypted data
US8886941B2 (en) Method and system for generating a secure message as an URL message
US20150271146A1 (en) Methods and systems for the secure exchange of information
US11582205B2 (en) System for sending e-mail and/or files securely
WO2015078376A1 (en) Method and system for secure email
US8898471B2 (en) Method and system for generating a secure message as a URL message
US20210158301A1 (en) Systems and methods for message transmission and retrieval using blockchain
US9049025B1 (en) Method of decrypting encrypted information for unsecure phone
US11805090B1 (en) Method, apparatus, and system for securing electronic messages
JP6472564B1 (en) Data transmission program, data transmission system, and data transmission method
US20220083693A1 (en) Method for certifying transfer and content of a transferred file
WO2021146801A1 (en) Secure data transfer system
JP5417026B2 (en) Password notification device and password notification system
US9118629B2 (en) Method and system for generating a secure message as a URL message
JP2018025913A (en) Program and information processing apparatus
KR20150121742A (en) Subscriber information processing module for subscribing to anonymous house bulletin board

Legal Events

Date Code Title Description
FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO UNDISCOUNTED (ORIGINAL EVENT CODE: BIG.); ENTITY STATUS OF PATENT OWNER: MICROENTITY

FEPP Fee payment procedure

Free format text: ENTITY STATUS SET TO MICRO (ORIGINAL EVENT CODE: MICR); ENTITY STATUS OF PATENT OWNER: MICROENTITY