Source: https://patents.google.com/patent/US10097661B2/en
Timestamp: 2019-04-24 08:28:43+00:00

Document:
The size of attachments to an electronic message are examined before the message is sent to determine if the attachments exceed a size threshold. When the size of the attachments exceed the threshold, one or more of the attachments are uploaded to a shared location that is accessible to the recipients of the message. A link replaces each attachment that was uploaded to the shared location. Permissions are automatically set at the shared location such that each of the recipients of the message are able to access the uploaded attachment.
This application is a continuation of and claims priority to application Ser. No. 13/096,910, now U.S. Pat. No. 9,137,185, filed Apr. 28, 2011, entitled UPLOADING ATTACHMENT TO SHARED LOCATION AND REPLACING WITH A LINK and is hereby incorporated in its entirety by reference.
Users routinely attempt to send large attachments using electronic messages. Many message gateways limit the size of an attachment that may be delivered/received. The message including the attachments is not delivered when the size of an attachment or collection of attachments exceeds these limits. The sender of the message containing the attachment may or may not be notified that the message was not delivered.
FIG. 7 shows a process for automatically downloading content that is associated with a received message that includes a link to an uploaded attachment.
Referring now to FIG. 1, an illustrative computer environment for a computer 100 utilized in the various embodiments will be described. The computer environment shown in FIG. 1 includes computing devices that each may be configured as a mobile computing device (e.g. phone, tablet, net book, laptop), server, a desktop, or some other type of computing device and includes a central processing unit 5 (“CPU”), a system memory 7, including a random access memory 9 (“RAM”) and a read-only memory (“ROM”) 10, and a system bus 12 that couples the memory to the central processing unit (“CPU”) 5.
A basic input/output system containing the basic routines that help to transfer information between elements within the computer, such as during startup, is stored in the ROM 10. The computer 100 further includes a mass storage device 14 for storing an operating system 16, messaging application(s) 24, Web Browser 25, and attachment manager 26 which will be described in greater detail below.
Computer 100 operates in a networked environment using logical connections to remote computers through a network 18, such as the Internet. The computer 100 may connect to the network 18 through a network interface unit 20 connected to the bus 12. The network connection may be wireless and/or wired. The network interface unit 20 may also be utilized to connect to other types of networks and remote computer systems. The computer 100 may also include an input/output controller 22 for receiving and processing input from a number of other devices, including a keyboard, mouse, or electronic stylus (not shown in FIG. 1). Similarly, an input/output controller 22 may provide input/output to a display screen 23, a printer, or other type of output device.
As mentioned briefly above, a number of program modules and data files may be stored in the mass storage device 14 and RAM 9 of the computer 100, including an operating system 16 suitable for controlling the operation of a computer, such as the WINDOWS PHONE 7®, WINDOWS 7®, or WINDOWS SERVER® operating system from MICROSOFT CORPORATION of Redmond, Wash. The mass storage device 14 and RAM 9 may also store one or more program modules. In particular, the mass storage device 14 and the RAM 9 may store one or more application programs, including one or more messaging application(s) 24 and Web browser 25.
A user interface 15 is used by a user to interact with applications and documents. Messaging application(s) 24 may be one or more different messaging applications. For example, computer 100 may include an email application, an Instant Messaging (IM) application, an SMS, MMS application, a real-time information network (e.g. Twitter® interface), a social networking application, and the like. According to an embodiment, messaging application 24 is an email application, such as MICROSOFT OUTLOOK®. The messaging application(s) may be client based and/or web based. For example, a network based message service 17 may be used, such as: MICROSOFT WINDOWS LIVE or some other network based email and messaging service.
Network share 27 is configured to store content (e.g. documents, spreadsheet, Web content, and the like) that are accessible to one or more users through IP network 18. For example, network share 27 may store content that is accessible by users located at one or more locations.
Attachment manager 26 is configured to upload attachments that exceed a size threshold and replace the attachment with a link in the message. The term “link” refers to an address that represents a location of content. For example, a link may be in the form of a Uniform Resource Locator (URL) that specifies a network location of where the attachment/content is stored. Clicking the link generally retrieves the content that is pointed to by the link. Attachment manager 26 may be located externally from an application, e.g. messaging application 24, as shown or may be a part of an application. Further, all/some of the functionality provided by attachment manager 26 may be located internally/externally from a messaging application.
According to an embodiment, attachment manager 26 is configured to present linked content and/or attachments in an attachment area of an electronic message for easier access than having to locate the link within the body of the message. Attachment manager 26 automatically determines the size of attachments to an electronic message before the message is sent. When the size of the attachments exceed the predetermined threshold, one or more of the attachments are uploaded to a shared location that is accessible to the recipients of the message. A link replaces each attachment within the message that was uploaded to the shared location. Attachment manager 26 automatically sets the permissions of the attachment(s) at the shared location such that each of the recipients of the message are able to access the uploaded attachment(s). The attachments may be many different types of content, such as word processing documents, spreadsheets, slides, website content and the like. When the message is delivered to the recipient, the attachment that is addressed by the link may be automatically downloaded and included with the display of the link or in place of the link within the message. More details regarding the attachment manager are disclosed below.
FIG. 2 shows a system for uploading attachments that exceed a threshold to a shared location and replacing the uploaded attachment with a link within the message. As illustrated, system 200 includes computing device 1 (210), computing device 2 (220), network share(s) 230 and messaging service 240.
The computing devices may be any type of computing device that is configured to perform the operations relating to sending and receiving electronic messages that include attachments and links to content. For example, some of the computing devices may be: mobile computing devices (e.g. cellular phones, tablets, smart phones, laptops, and the like); desktop computing devices and servers. Some computing devices may be arranged to provide an online service (e.g. messaging service 240 that is configured for sending and receiving electronic messages), some may be arranged as data shares, some may be arranged in local networks, some may be arranged in networks accessible through the Internet, and the like.
The computing devices are coupled through network 18. Network 18 may be many different types of networks. For example, network 18 may be an IP network, a carrier network for cellular communications, and the like. Generally, network 18 is used to transmit data between computing devices, such as computing device 1, computing device 2, network share 230 and messaging service 240.
Computing device 1 includes messaging application 212 and user interface 216. As illustrated, computing device 1 is used by a user to interact with electronic messages, content in a network share (e.g. attachment 232) and the like.
User interface (UI) 216 is used to interact with an application and content, such as messaging application 212 and attachment(s) 232. One or more user interfaces of one or more types may be used to interact with the content. For example, UI 216 may include the use of a context menu, a menu within a menu bar, a menu item selected from a ribbon user interface, a graphical menu, and the like. Generally, UI 216 is configured such that a user may easily interact with content and electronic messages. For example, a user may simply select an option within UI 216 to automatically upload and permission an attachment that exceeds a predetermined size to a shared location. UI 216 may also be used to set permissions for the attachment at the shared location and to access the attachment and/or link to the attachment.
Upon receipt of the message, the recipient of the message may access the uploaded attachment using the link within the received message. According to an embodiment, the attachment is downloaded to the recipient's device automatically. The link to the attachment may/may not be removed from the message when the attachment is downloaded. For example, upon receipt of the message including the link to the attachment, attachment manager 26 may automatically download the attachment, remove the link from the message and attach the downloaded attachment to the message. In this way, the recipient receives the message as if the attachment was delivered with the message.
Messaging application 212 may be a client based application, such as an email application, an Instant Messaging Application, a social media application, and the like. Generally, messaging application 212 is used to send and receive electronic messages of one or more types. A network based messaging service 240 may be used in addition to messaging application 212 or instead of one or more of the different messaging applications. For example, a web interface may be used to access messaging service 240.
Messaging service 240 may be used to process electronic messages between one or more computing devices, such as computing device 1 and computing device 2. Messaging service 240 may be configured to process different message types, such as SMS, MMS, email, messages for social networks and the like. Messaging service 240 may be configured with the functionality of attachment manager 26 and one or more message types may be used to communicate the electronic messages including links to the uploaded attachment(s).
Computing device 2 includes one or more applications, such as a web browser (222) that may be configured to access a messaging service, such as a web based email service and to interact with content. For example, a web browser may be used to access messaging service 240 and create an electronic message including one or more attachments.
Attachment manager 26 is configured to detect any attachments to an electronic message and determine when one or more of the attachments is to be uploaded to a network share based on a size of the attachments. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, pictures, videos, website content and the like. Attachment manager 26 determines if one or more or a combination of attachments exceed a predetermined size threshold. According to an embodiment, the predetermined size threshold is based on a size restriction of a message gateway that sets a maximum size limitation for an electronic message (e.g. 1 MB, 5 MB, 10 MB . . . ). The predetermined size threshold may be configured by an authorized user (e.g. system administrator). When one or more of the attachments exceed the threshold, attachment manager 26 is configured to upload one or more of the attachments. For example, all/portion of the attachments may be uploaded to the shared location and removed from the message such that the size of the message when it is sent is below the threshold. When one attachment or a combination of the attachments exceed the threshold, each attachment to the message is uploaded to the shared location. Each attachment that is uploaded is replaced with a link to the attachment at the shared location within the message. According to an embodiment, the link(s) are placed within an attachment area of the electronic message such that when a user receives the message the links to the uploaded attachments are easily locatable. A single link may also be used to address all of the attachments that were uploaded to the shared location (e.g. the link may point to a folder containing the uploaded attachments). The attachments may be uploaded before the message is sent and/or after the message is sent. According to an embodiment, the attachments are uploaded before a message is sent such that any errors in uploading the attachment to the shared location may be presented to the sender of the electronic message before the message is sent.
According to an embodiment, any attachments that were uploaded due to the size exceeding the threshold are automatically downloaded and included within the attachment area before the user receiving the message views the message. For example, upon receipt of the message, the linked attachment may be automatically downloaded and included with the message. All/some of the linked content may be automatically downloaded. The links to the attachments may/may not be removed from the message after the attachments are downloaded.
FIGS. 3-5 show exemplary electronic messages where an attachment is uploaded to a shared location and replaced with a link within the message. FIGS. 3-5 are for exemplary purpose and are not intended to be limiting.
FIG. 3 shows a display of an electronic message including an attachment. As illustrated, message 300 comprises a To: field, a Cc: field, a Subject field, an Attached field that includes attachment 310; body of the message 314 and upload option 320. More or fewer fields may be included with the electronic message.
The electronic message may be accessed a number of ways. For example, a web browser may access an electronic mail service, an email application on a computing device may be configured to send/receive emails from one or more different services, and the like.
When electronic message is created, attachment 310 is included with the message. The attachments may be to any type of content, such as word processing documents, spreadsheets, slides, websites and the like. Generally, the attachment may be to any type of content that is accessible by a computing device.
FIG. 4 shows a display of an electronic message including a link to an attachment that has been uploaded to a shared location. As illustrated, message 400 comprises a To: field, a Cc: field, a Subject field, an Attached field that includes link to attachment 410; body of the message 314 and change option 320. More or fewer fields may be included with the electronic message.
When one or more of the attachments are uploaded to a shared location, change option 430 may be used to make changes relating to the attachment. For example, a user may select change option to change the permissions for access to the uploaded attachment at the shared location. For example, some of the recipients may have permissions set that allow them read/write access, other recipients may only have read access. Permissions may also be set to control the forwarding of the attachment/link to the attachment (e.g. prevent an unauthorized user from receiving the attachment and/or a link to the attachment).
According to an embodiment, the link to the uploaded content (410) is located within an attachment area of the message such that the user does not have to search for the linked content within the body of the electronic message.
The attachment area may be located within many different areas of the display. Generally, the attachment area is located such that the display of the attached area remains visible even though the body of the message is scrolled to change the view of the message. A graphical indicator, such as an icon, may be displayed within the attachment area near the link to provide additional information relating to the attachment. The graphical indicator may be selected to indicate a type of the content and/or other characteristics relating to the linked content. For example, a document icon may be used to show the content is a document, a web icon may be used for web content, a spreadsheet icon may be used for spreadsheets, a picture icon may be used for pictures, a message icon may be used for messages, an online service icon may be used to show where the attachment has been uploaded (e.g. a video service icon to indicate that the attachment has been uploaded to video service 1, a picture service icon . . . ) and the like.
FIG. 5 shows a display of an electronic message within a Web browser including a link to content. As illustrated, Web browser 502 shows a message that includes a link 510 to content that has been automatically uploaded. In the current example, change option 520 provides the sender with the one or more menu options that relate to the attachment that was uploaded due to size limitations (e.g. setting permissions, changing default shared locations for one or more message types, removing an attachment from a shared location, and the like).
FIGS. 6 and 7 shows an illustrative process for uploading attachments that exceed a threshold to a shared location and automatically downloading attachments in a received message. When reading the discussion of the routines presented herein, it should be appreciated that the logical operations of various embodiments are implemented (1) as a sequence of computer implemented acts or program modules running on a computing system and/or (2) as interconnected machine logic circuits or circuit modules within the computing system. The implementation is a matter of choice dependent on the performance requirements of the computing system implementing the invention. Accordingly, the logical operations illustrated and making up the embodiments described herein are referred to variously as operations, structural devices, acts or modules. These operations, structural devices, acts and modules may be implemented in software, in firmware, in special purpose digital logic, and any combination thereof.
FIG. 6 illustrates a process for uploading attachments that exceed a threshold to a shared location.
After a start block, process 600 moves to operation 610, where the electronic message is accessed. The electronic message may be any electronic message that includes the ability to attach content. According to an embodiment, the electronic messages are email messages. Other messages may also be used attachments, such as SMS, MMS, Instant Messages, social network messages, and the like.
Flowing to operation 620, any attachments that are associated with the electronic message are detected. According to an embodiment, the detection occurs before the message is sent. A size of the attachment(s) is also determined.
Moving to operation 630, a determination is made as to what attachments are to be uploaded based on determining that the size of the attachments exceed a predetermined size threshold. According to an embodiment, the predetermined size threshold is based on a size limitation for delivery of an electronic message (e.g. 1 MB, 5 MB, 10 MB . . . ). The predetermined size threshold may be configured by a user (e.g. system administrator). When one or more of the attachments exceed the threshold, attachment manager 26 is configured to upload one or more of the attachments. For example, all/portion of the attachments may be uploaded to the shared location such that when the uploaded attachments are removed from the message, the size of the message is below the threshold. According to an embodiment, if any one attachment is uploaded, each attachment within the message is uploaded.
Transitioning to operation 640, the determined attachments are uploaded to one or more shared locations. The attachments may be uploaded to shared locations based on different criteria. For example, a shared location may be selected based on a type of the attachment (e.g. video attachments to a shared location that hosts videos, picture attachments to a shared location that hosts pictures, documents to a shared location that hosts documents, and the like.) A shared location may also be selected based on shared locations that are selected by the sender and/or one or more of the recipients. For example, each recipient may have configured preferences indicating a desired shared location. The attachment may be uploaded to more than one shared location (e.g. the attachment is uploaded to each recipient's configured shared location).
Flowing to operation 650, permissions for accessing the uploaded attachments are set such that each recipient is able to access the uploaded attachment. According to an embodiment, the attachment is set to read/write permission for each recipient of the message. A user may change these permissions by accessing a change option within the electronic message and/or by accessing the shared location where the attachment is uploaded.
Moving to operation 660, the attachments within the message are replaced with links that may be used to access each of the uploaded attachments.
Transitioning to operation 670, the electronic message is sent to the recipients.
After a start block, process 700 moves to operation 710, where the electronic message is received. The electronic message may be any electronic message that includes a link to an attachment that was uploaded to a shared location. According to an embodiment, the electronic messages are email messages. Other messages may also include links, such as SMS, MMS, Instant Messages, social network messages, and the like. The message may be received by a client based application and/or a Web based application.
Flowing to operation 720, any links to uploaded attachments within the electronic message are detected. A link may be associated with an uploaded attachment using different methods. For example, the link itself may contain information that indicates the content that the link addresses was uploaded due to a size limitation. According to an embodiment, the links are detected before the received message is viewed.
Moving to operation 730, the attachment may be automatically downloaded. According to an embodiment, the content is automatically downloaded and displayed within the attachment area of the electronic message before the user receiving the message views the message.
Transitioning to operation 740, the links to the content that is automatically downloaded are replaced with an attachment of the content.
Flowing to operation 750, the electronic message is displayed with the attachment with the electronic message. When a user views the message, the attachment may be opened.
sending the electronic message in response to receiving the request to send the electronic message.
2. The method of claim 1, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a word processing document.
3. The method of claim 1, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a video.
4. The method of claim 1, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to at least one of: a first shared location when the type of the attachment is a picture; and a second shared location when the type of the attachment is a word processing document.
5. The method of claim 1, wherein the predetermined size threshold is based on a size restriction of a message gateway.
6. The method of claim 1, further comprising displaying a graphical menu within the electronic message that comprises an option for sending a link to the attachment in place of the attachment and an option for managing permissions of the attachment.
8. The computer-readable storage device of claim 7, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a word processing document.
9. The computer-readable storage device of claim 7, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a video.
10. The computer-readable storage device of claim 7, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to at least one of: a first shared location when the type of the attachment is a picture; and a second shared location when the type of the attachment is a word processing document.
11. The computer-readable storage device of claim 7, wherein the predetermined size threshold is based on a size restriction of a message gateway.
12. The computer-readable storage device of claim 7, further comprising displaying a graphical menu within the electronic message that comprises an option for sending a link to the attachment in place of the attachment and an option for managing permissions of the attachment.
13. The computer-readable storage device of claim 7, wherein setting the permissions for the attachment at the shared location such that the recipient is able to access the attachment comprises determining each recipient of the message and setting a default set of permissions for each of the recipients.
inserting a link to the attachment at the shared location.
15. The system of claim 14, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a word processing document.
16. The system of claim 14, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to a particular shared location based on whether or not the type of the attachment is a video.
17. The system of claim 14, wherein determining the shared location to upload the attachment based on the type of the attachment comprises setting the shared location to at least one of: a first shared location when the type of the attachment is a picture; and a second shared location when the type of the attachment is a word processing document.
"Final Office Action Issued in U.S. Appl. No. 13/096,854", dated Jul. 23, 2018, 25 Pages.
"Office Action Issued in Korean Patent Application No. 10-2013-7028223", dated Jul. 17, 2018, 9 Pages.
"Office Action Issued in Korean Patent Application No. 10-2013-7028430", dated Jun. 28, 2018, 08 Pages.
"Office Action Issued in Korean Patent Application No. 10-2013-7029294", dated May 28, 2018, 05 Pages.
AU: Office Action Issued in Australian Patent Application No. 2012253808, dated Sep. 16, 2016, 3 Pages.
Australian Notice of Allowance in Application 2012253808, dated Nov. 28, 2016, 2 pages.
Australian Office Action Full Examination Report Issued in Patent Application No. 2012253808, dated Jul. 9, 2016, 3 Pages.
Canadian Office Action in Application 2835323, dated Jan. 25, 2018, 4 pages.
Chinese Decision on Reexamination in Application 201280020342.9, dated Mar. 30, 2018 15 pages.
Chinese Notice of Allowance in Application 201280020430.9, dated Aug. 29, 2017, 4 pages.
Chinese Notice of Allowance in Application 201280021905.6, dated Mar. 27, 2018, 4 pages.
Chinese Notice of Allowance in Application 201280021954.X, dated Dec. 22, 2016, 4 pages.
Chinese Office Action and Search Report Issued in Chinese Patent Application No. 201280020368.3, dated Dec. 2, 2015, 14 pgs.
Chinese Office Action and Search Report Issued in Chinese Patent Application No. 201280020441.7, dated Dec. 15, 2015, 18 Pages.
Chinese Office Action and Search Report Issued in Patent Application No. 201280021905.6, dated Dec. 2, 2015, 14 pgs.
Chinese Office Action dated Dec. 29, 2015 in Appln No. 201280021954.x, 16 pgs.
Chinese Office Action dated Feb. 1, 2016 in Appln No. 201280020342.9, 12 pgs.
Chinese Office Action dated Mar. 4, 2016 in Appln No. 201280020430.9, 11 pgs.
Chinese Office Action in Application 201280020342.9, dated Sep. 29, 2017, 11 pages.
Chinese Office Action in Application 201280020368.3, dated Nov. 6, 2017, 10 pages.
Chinese Office Action in Application 201280020368.8, dated Apr. 8, 2018, 18 pages.
Chinese Office Action in Application 201280020430.9, dated Feb. 27, 2017, 8 pages.
Chinese Office Action in Application 201280020441.7, dated Jan. 25, 2017, 10 pages.
Chinese Office Action in Application 201280020441.7, dated Jun. 2, 2017, 9 pages.
Chinese Office Action in Application 201280020441.7, dated May 4, 2018, 8 pages.
Chinese Office Action in Application 201280021905.6, dated Sep. 19, 2017, 9 pages.
Chinese Office Action Issued in Patent Application No. 201280020342.9, dated Aug. 1, 2016, With English translation. 10 pages.
Chinese Office Action Issued in Patent Application No. 201280021905.6, dated Jul. 1, 2016, With English translation. 10 pgs.
Chinese Second Office Action and Search Report Issued in Chinese Patent Application No. 201280020368.3, dated Aug. 5, 2016, 10 pages. With English Translation.
Chinese Second Office Action dated Aug. 29, 2016 in Application No. 201280021954.x, 5 pages.
Chinese Second Office Action Issued in Chinese Patent Application No. 201280020441.7, dated Aug. 1, 2016, 14 Pages. With English Translation.
Decouchant et al.; "Griffon: A Cooperative, Structured, Distributed Document Editor"; 1993; http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.51.759&rep=repl&type=pdf; 28 pages.
Devendorf, G.; "Outlook putting attachments in Sharepoint"; Feb. 13, 2008; http://my.advisor.com/blog/garydev.nsf/d6plinks/GDEF-7BSUA2; 5 pages.
Edholm, Y.; "Email Attachments: The Scourge of the Network"; Jul. 21, 2008; solutions-daily.com; http://www.solutions-daily.com/dsp_getFeaturesDetails.cfm?CID=691; 3 pg.s.
Egnyte.co; "Cloud File Server Features-Complete List"; accessed Dec. 30, 2010, at http://www.egnyte.co.uk/file-server/online-file-server-features.html; 5 pgs.
Egnyte.co; "Cloud File Server Features—Complete List"; accessed Dec. 30, 2010, at http://www.egnyte.co.uk/file-server/online-file-server-features.html; 5 pgs.
European Communication in Application 12777074.1, dated Oct. 16, 2017, 7 pages.
European Extended Search Report in Application 12776501.4, dated Jun. 6, 2018, 7 pages.
European Office Action in Application 12777397.6, dated Jan. 3, 2018, 6 pages.
European Office Action Issued in Application No. 12777397.6 , dated Mar. 3, 2016, 6 pgs.
European Office Action Issued in Application No. 12782951.3 , dated Aug. 17, 2016, 6 pages.
European Summons in Application 12782951.3, dated Feb. 13, 2018, 7 pages.
Gigaom.com; "How to Use Adobe Acrobat for Online Document Reviews"; Retrieved Date: Jan. 4, 2010; http://gigaom.com/collaboration/how-to-use-adobe-acrobat-for-online-document-reviews/; 8 pgs.
Harmoni.ie; "harmon.ie for SharePoint"; accessed Apr. 1, 2011 at http://harmon.ie/SharePoint/Product/Features/CollaborateUsingDocuments; 3 pgs.
Hsieh, H., et al.; "Activity Links: Supporting Communication and Reflection about Action"; Center for the Study of Digital Libraries and Dept. of Computer Science, Texas A&M University, USA; HT '05 Sep. 6-9, 2005, Salzburg, AT; 10 pgs.
Japanese Notice of Allowance in Application 2014-510385, dated Oct. 13, 2016, 4 pages.
Japanese Notice of Allowance Issued in Patent Application No. 2014-508169, dated Jul. 12, 2016, 3 Pages. Without English Translation.
Japanese Notice of Allowance Issued in Patent Application No. 2014-508170, dated Sep. 13, 2016, 3 Pages.
Japanese Notice of Allowance Issued in Patent Application No. 2014-508171, dated Aug. 4, 2016, 4 Pages.
Japanese Office Action in Application 2014-510384, dated Oct. 13, 2016, 6 pages.
Japanese Office Action Issued in Patent Application No. 2014-508168, dated Mar. 23, 2016, 8 Pages.
Japanese Office Action Issued in Patent Application No. 2014-508169, dated Feb. 10, 2016, 11 Pages.
Japanese Office Action Issued in Patent Application No. 2014-508170, dated Mar. 22, 2016, 5 Pages.
Japanese Office Action Issued in Patent Application No. 2014-508171, dated Mar. 11, 2016, 6 Pages.
Japanese Office Action Issued in Patent Application No. 2014-510384, dated May 9, 2016, 6 Pages.
Japanese Office Action Issued in Patent Application No. 2014-510385, dated May 30, 2016, With english translation. 9 Pages.
Japaneses Notice of Allowance in Application 2014-510384, dated Mar. 31, 2017, 3 page. (No English Translation.).
Jatowt, A., et al.; "Change Summarization in Web Collections"; University of Tokyo, Japan; 2004; accessed on or about Jan. 4, 2010 at http://citeseerx.ist.psu.edu/viewdoc/download?doi=10.1.1.73.7999&rep=rep1&type-pdf; 10 pgs.
JP: Notice of Allowance Issued in Japanese Patent Application No. 2014-508171, dated Aug. 4, 2016, 4 Pages.
JP: Office Action Issued in Japanese Patent Application No. 2014-508168, dated Oct. 7, 2016, 8 Pages.
Korean Notice of Allowance in Application 10-2013-7029310, dated May 21, 2018, 4 pages.
Korean Office Action in Application 10-2013-702827, dated Oct. 23, 2017, 11 pages.
Korean Office Action in Application 10-2013-7028277, dated Apr. 30, 2018, 5 pages.
Korean Office Action in Application 10-2013-7028280, dated May 21, 2018, 14 pages.
Korean Office Action in Application 10-2013-7028280, dated Oct. 21, 2017, 11 pages.
Korean Office Action in Application 10-2013-7028430, dated May 14, 2018, 8 pages.
Korean Office Action in Application 10-2013-7028430, dated Oct. 23, 2017, 11 pages.
Korean Office Action in Application 10-2013-7029294, dated Oct. 23, 2017, 10 pages.
Korean Office Action in Application 10-2013-7029310, dated Nov. 28, 2017, 7 pages.
Lenahan, T.; "5 New Google Docs Features You Might Have Missed"; Apr. 6, 2010; http://www.makeuseof.com/tag/5-google-docs-features-making/; 9 pgs.
Masternewmedia.com; "How to Send Large Files without Email"; Last updated: Jan. 6, 2011; retrieved Jan. 7, 2011, from http://www.masternewmedia.org/how_to_send_large_files_without_email/; 3 pgs.
Masternewmedia.org; "Collaborative Document Review Online: PleaseReview"; Retrieved Date: Jan. 4, 2010; http://www.masternewmedia.org/news/2005/06/02/collaborative_document_review_online_pleasereview.htm; 4 pgs.
McCoy, J., et al.; "SharePoint Workspace and the Office Document Cache"; Mar. 12, 2010-Sep. 29, 2010; retrieved Dec. 30, 2010, at http://blogs.msdn.com/b/sharepoint_workspace_development_team/archive/2010/03/12/sharepoint-workspace-and-the-office-document-cache.aspx; 2 pgs.
Microsoft Support; "Attachment Manager for Outlook"; accessed Jan. 7, 2011, at http://assistmyteam.com/downloads/manuals/AttachmentManager.pdf; 14 pgs.
Microsoft Support; "OL2000: Changing from Local Delivery to Server and Offline"; Oct. 8, 2003, rev. 1.0; accessed Jan. 7, 2011 at http://support.microsoft.com/kb/197651; 4 pgs.
Microsoft Support; "You may receive an ‘Outlook blocked access to the following potentially unsafe attachments’ message in Outlook"; Last Review: May 13, 2010; http://support.microsoft.com/kb/829982; 7 pgs.
Microsoft; "Going beyond e-mail: Collaborating with Office"; Retrieved Date: Jan. 4, 2010; http://office.microsoft.com/en-us/outlook-help/going-beyond-e-mail-collaborating-with-office-HA001017429.aspx; 10 pgs.
Notice of Allowance dated Jun. 15, 2015, issued in U.S. Appl. No. 12/963,091, 28 pgs.
Office Action dated Jan. 5, 2016, issued in U.S. Appl. No. 13/096,899, 19 pgs.
Office Action dated Jan. 9, 2013, issued in U.S. Appl. No. 12/963,091.
Office Action dated Jun. 16, 2014, issued in U.S. Appl. No. 12/963,091, 22 pgs.
Office Action dated Nov. 23, 2015, issued in U.S. Appl. No. 13/096,936, 21 pgs.
Office Action dated Sep. 21, 2015, issued in U.S. Appl. No. 13/102,875, 53 pgs.
Office Action dated Sep. 25, 2014, issued in U.S. Appl. No. 12/963,091, 24 pgs.
Office Action dated Sep. 7, 2012, issued in U.S. Appl. No. 12/963,0919.
Office Action Issued in Chinese Patent Application No. 201280020342.9, dated Oct. 31, 2016, 11 Pages.
Office Action Issued in Chinese Patent Application No. 201280020368.3, dated Dec. 27, 2016, 10 Pages.
Office Action Issued in Chinese Patent Application No. 201280021905.6, dated Nov. 29, 2016, 11 Pages.
Office-Addins.com; "Attachments Processor for Microsoft Outlook"; accessed Jan. 6, 2011, at http://www.-office-addins.com/-outlook-addins/attachments-processor.html; 3 pgs.
phpBB-Free and Open Source Forum Software; "Display last edited time information"; accessed Jan. 6, 2011, at http://www.phpbb.com/community/viewtopic.php?f=46&t=589514; 7 pgs.
phpBB—Free and Open Source Forum Software; "Display last edited time information"; accessed Jan. 6, 2011, at http://www.phpbb.com/community/viewtopic.php?f=46&t=589514; 7 pgs.
Re@DNotify, How to forward emails "As Attachments", Retrieved on Jul. 2, 2009 by the WayBack Machine, 7 pages.
Redline-Software.com; "Outlook Connector for MDaemon"; accessed Jan. 6, 2011, at http://www.redline-software.com/eng/support/docs/mdaemon/c6s4.php; 7 pgs.
RSBR.de; "Outlook Attachment Sniffer"; accessed Jan. 6, 2011, at http://www.rsbr.de/Software/OASniffer/index.htm; 2 pgs.
Russian Notice of Allowance in Application 2013149178, dated Jun. 15, 2017, 17 pages.
Russian Office Action Issued in Patent Application No. 2013149178, dated May 20, 2016, 8 Pages. No English Translation.
Russian Office Action Issued in Patent Application No. 2013149178, dated May 20, 2016, With English Translation. 9 Pages.
Second Office Action and Search Report Issued in Chinese Patent Application No. 201280020430.9, dated Nov. 1, 2016, 11 Pages.
Sharepoint Development; "How to show last modified workflow date in a column on the main list page"; Jul. 31, 2009-Aug. 4, 2009; accessed Jan. 6, 2011, at http://www.sharepointdev.net/sharepoint--design-customization/how-to-show-last-modified-workflow-date--in-a-column-on-the-main-list-page-5094.shtml; 4 pgs.
Taiwan Office Action and Search Report Issued in Taiwan Patent Application No. 101110617, dated Jul. 26, 2016, 7 Pages.
Taiwan Office Action and Search Report Issued in Taiwan Patent Application No. 101110617, dated Mar. 21, 2016, 6 Pages.
Taiwanese Notice of Allowance in Application 101110617, dated Nov. 16, 2016, 4 pages.
Thapa, S.; "Microsoft SharePoint 2010-Features and Benefits"; Dec. 1, 2010; EzineMark.com; 3 pgs.
Thapa, S.; "Microsoft SharePoint 2010—Features and Benefits"; Dec. 1, 2010; EzineMark.com; 3 pgs.
The Daily Reviewer; "Outlook Shared Attachment as Hyperlink"; accessed Dec. 30, 2010, at http://thedailyreviewer.com/windowsapps/view/outlook-shared-attachment-as-hyperlink-11367085; 5 pgs.
Toyoko Abe et al.; "Object Bulletin Board for Group Cooperative Work" printed in a collection of papers (1997-2006 Version 1.1) presented at DICOMO symposium sponsored by Information Processing Society of Japan on Aug. 31, 2006 (pp. 513-518) (DVD-ROM), 8 pages.
Troost et al., Internet Engineering Task Force, RFC 2183 dated Aug. 1997, 12 pgs. available at: www.rfc-editor.org/rfc/rfc2183.txt (from advisory Action dated Dec. 3, 2014).
U.S. Appl. No. 12/963,091, entitled Shared Attachments, filed Dec. 8, 2010.
U.S. Appl. No. 13/096,830, Notice of Allowance dated Nov. 8, 2013, 8 pages.
U.S. Appl. No. 13/096,854, Advisory Action dated Dec. 3, 2014, 5 pages.
U.S. Appl. No. 13/096,854, Office Action dated Dec. 28, 2017, 29 pages.
U.S. Appl. No. 13/096,854, Office Action dated Jan. 11, 2017, 39 pgs.
U.S. Appl. No. 13/096,854, Office Action dated Jun. 29, 2017, 29 pages.
U.S. Appl. No. 13/096,854, Office Action dated May 2, 2016, 35 pgs.
U.S. Appl. No. 13/096,869, Advisory Action dated Dec. 3, 2014, 4 pages.
U.S. Appl. No. 13/096,880, Advisory Action dated Jul. 27, 2015, 5 pages.
U.S. Appl. No. 13/096,880, Advisory Action dated Oct. 15, 2015, 4 pages.
U.S. Appl. No. 13/096,880, Advisory Action dated Sep. 18, 2015, 3 pages.
U.S. Appl. No. 13/096,880, Office Action dated Feb. 19, 2016, 19 pgs.
U.S. Appl. No. 13/096,880, Office Action dated Jun. 14, 2017, 13 pages.
U.S. Appl. No. 13/096,880, Office Action dated Oct. 25, 2016, 20 pgs.
U.S. Appl. No. 13/096,899, Office Action dated Aug. 15, 2017, 24 pages.
U.S. Appl. No. 13/096,899, Office Action dated Mar. 19, 2018, 20 pages.
U.S. Appl. No. 13/096,899, Office Action dated Sep. 26, 2016, 36 pages.
U.S. Appl. No. 13/096,936, Office Action dated Mar. 22, 2016, 20 pgs.
U.S. Appl. No. 13/102,431, Notice of Allowance dated Jan. 27, 2015, 2 pages.
U.S. Appl. No. 13/102,431, Notice of Allowance dated Oct. 14, 2014, 6 pages.
U.S. Appl. No. 13/102,875, Office Action dated Apr. 20, 2016, 22 pgs.
U.S. Appl. No. 13/102,875, Office Action dated Jul. 5, 2017, 19 pages.
U.S. Appl. No. 13/102,875, Office Action dated Mar. 16, 2018, 18 pages.
U.S. Appl. No. 13/102,875, Office Action dated Nov. 14, 2016, 27 pgs.
U.S. Appl. No. 14/188,666, Notice of Allowance dated Apr. 20, 2017, 6 pages.
U.S. Appl. No. 14/188,666, Office Action dated Feb. 26, 2016, 77 pgs.
U.S. Appl. No. 14/188,666, Office Action dated Oct. 25, 2016, 24 pgs.
U.S. Appl. No. 14/188,666, Supplemental Notice of Allowance dated Jul. 11, 2017, 2 pages.
U.S. Appl. No. 14/188,666, Supplemental Notice of Allowance dated Jul. 26, 2017, 2 pages.
U.S. Appl. No. 14/887,086, entitled Shared Attachments, filed Oct. 19, 2015.
U.S. Appl. No. 14/887,086, Notice of Allowance dated Jun. 6, 2018, 7 pages.
U.S. Appl. No. 14/887,086, Office Action dated Jan. 26, 2018, 19 pages.
U.S. Appl. No. 14/887,086, Office Action dated Oct. 6, 2017, 16 pages.
Vogel et al., "Consistency Control for Synchronous and Asynchronous Collaboration Based on Shared Objects and Activities"; Computer Supported Copperative Work (CSCW); Kluwer Academic Publishers, vol. 13, No. 5-6; Dec. 1, 2004; pp. 573-602.
Wikipedia, Message, http://en.wikipedia.org/wiki1Message retrieved Jan. 9, 2014, p. 1-2.

References: Application No. 10
 Application No. 10
 Application No. 10
 Application No. 2012253808
 Application No. 2012253808
 Application No. 201280020368
 Application No. 201280020441
 Application No. 201280021905
 Application No. 201280020342
 Application No. 201280021905
 Application No. 201280020368
 Application No. 201280021954
 Application No. 201280020441
 Application No. 12777397
 Application No. 12782951
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 2014
 Application No. 201280020342
 Application No. 201280020368
 Application No. 201280021905
 Application No. 2013149178
 Application No. 2013149178
 Application No. 201280020430
 Application No. 101110617
 Application No. 101110617