Users routinely send links to documents and other content to users for viewing. A user receiving the message finds the link within the message and then uses the link to access the content. A user may forward the message containing the link to other users that may not be authorized to access the linked content.
This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
A permission manager detects when an electronic message including one or more links is forwarded to another recipient. For example, an author may send a message that has permissions set that allow access to the linked content for the recipient, that is then forwarded by the recipient to another recipient. The permission manager detects when the message including the link is forwarded and sends a notification to the author indicating that the message was forwarded to another recipient. A notification may also be sent to the recipient who received the forwarded message indicating that the author has been notified that the recipient is not authorized to access the linked content within the forwarded message. The author may set the permissions for accessing the linked content from permission options that are displayed with the notification message sent by the permission manager. Once the permissions are set, the permission manager may send a notification to the recipient of the forwarded message with information relating to the set permissions.
Referring now to the drawings, in which like numerals represent like elements, various embodiment will be described. In particular,
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Other computer system configurations may also be used, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. Distributed computing environments may also be used where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Referring now to
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 permission manager 26 which will be described in greater detail below.
The mass storage device 14 is connected to the CPU 5 through a mass storage controller (not shown) connected to the bus 12. The mass storage device 14 and its associated computer-readable media provide non-volatile storage for the computer 100. Although the description of computer-readable media contained herein refers to a mass storage device, such as a hard disk or CD-ROM drive, the computer-readable media can be any available media that can be accessed by the computer 100.
By way of example, and not limitation, computer-readable media may comprise computer storage media and communication media. Computer storage media includes volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer-readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, Erasable Programmable Read Only Memory (“EPROM”), Electrically Erasable Programmable Read Only Memory (“EEPROM”), flash memory or other solid state memory technology, CD-ROM, digital versatile disks (“DVD”), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computer 100.
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
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. Links that are included within electronic messages may access content within network share 27 when the link is used.
Permission manager 26 is configured to set permissions for a link that is forwarded in an electronic message. Permission 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 permission manager 26 may be located internally/externally from a messaging application.
Permission manager 26 is configured to detect when an electronic message including one or more links is forwarded to a recipient that is not an original recipient of 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 content is stored. Selecting the link generally retrieves the content that is pointed to by the link. An author may send a message to a recipient that has permissions allowing the recipient to access to the linked content. The recipient of the original message may forward the message to another recipient that may/may not be authorized to access the linked content. Permission manager 26 detects when the message including the link is forwarded and sends a notification to the author indicating that the message was forwarded to another recipient. A notification may also be sent to the recipient who received the forwarded message from permission manager 26 indicating that the author has been notified that the recipient is not authorized to access the linked content within the forwarded message. The author may set the permissions for the recipients receiving the forwarded message by accessing permission options that are displayed with the notification message that was sent from permission manager 26. Once the permissions are set, permission manager 26 may send a notification to the recipient of the forwarded message with information relating to the set permissions. More details regarding the permission manager are disclosed below.
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 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, computing device 3, 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. content 232) and the like.
User interface (UI) 216 is used to interact with an application and content, such as messaging application 212 and content 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 that creates new electronic messages that include one or more links to content.
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 permission manager 26 and one or more message types may be used to communicate the electronic messages including links to content.
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 an electronic message through an email service and then access content 232 stored in network share 230.
One or more network shares (e.g. Network share 230) may be used to store content. The content may be any type of content that is linked within a message, such as word processing documents, spreadsheets, slides, website content and the like. Network share 230 is accessible by the computing devices that interact with the content. The network share may be associated with an online service that supports online access/interaction with content.
Computing device 3 (225) is configured as a mail server. For example, messaging application 212 on computing device 1 may be used to create a message that includes a link that is to be sent to one or more recipients. When the user sends the message, computing device 3 may be configured to perform various mail processing actions and to deliver the message to the one or more recipients. As illustrated, computing device 3 includes functionality of permission manager 26. According to an embodiment, computing device 3 (mail server) using permission manager 26 determines when a message including a link is forwarded to another recipient.
Permission manager 26 is configured to detect any links to content that are included within an electronic message that is forwarded. The links may be to any type of content, such as word processing documents, spreadsheets, slides, website content and the like. Generally, the link may be to any type of content that is accessible by a computing device. Permission manager 26 is configured to detect when an electronic message including one or more links is forwarded to a recipient that is not an original recipient of the message. Permission managers on different computing devices and/or networks may be configured to communicate information between them. For example, permission manager 26 on computing device 3 may communicate to the permission manager on messaging service 240 to provide/obtain information about sent/forwarded messages that includes links. The permission manager may store permission settings for links within a central data store, such as network share 230.
Permission manager 26 detects when the message including the link is forwarded and sends a notification to the author indicating that the message was forwarded to another recipient. Permission manager 26 may also be configured to determine when the link is sent as an attachment that was included in the message sent by the author. A notification may also be sent to the recipient who received the forwarded message from permission manager 26 indicating that the author has been notified that the recipient is not authorized to access the linked content within the forwarded message. The author may set the permissions for accessing the link from permission options that are displayed with the notification message that was sent from permission manager 26. Once the permissions are set, permission manager 26 may send a notification to the recipient of the forwarded message with information relating to the set permissions.
The electronic message may be accessed and composed using one or more messaging applications. 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 being composed, a link to content 310 is included with the message. The links may be to any type of content, such as word processing documents, spreadsheets, slides, websites and the like. Generally, the link may be to any type of content that is accessible by a computing device. According to an embodiment, any links to content that are included within the body of the message are displayed as linked content within an attachment area (e.g. Attached: field) such that when a user receiving the message accesses the message the linked content is viewable within an attachment area that is associated with the electronic message. In this way, the user does not have to search for the linked content within the body of the electronic message that may contain many different responses. The link that is contained within the body of the message may/may not be left within the body of the message.
A graphical indicator, such as an icon, may be displayed within the attachment area near the link. 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, and the like. An indicator may also be displayed that shows that the icon represents content that is linked within the body of the message. Other indicators may also be used to show other information (e.g. an indicator to show that the linked content is/is not authorized for a recipient).
Change permission option 315 provides different options for setting access permissions for the recipients of the message including link 310. For example, the author may select change permission option 315 to change the permission options for the recipients (Dan, Paul, Tim) to access the linked content that is pointed to by link 310. As illustrated, option menu 320 includes options for setting the permissions for read/write, read, write, allow forwarding, and other options. The allowed forwarding option allows the author to automatically permission recipients for forwarded messages that receive the link in a forwarded message. For example, when the allow forward option is selected, the permissions for the linked content are automatically set to allow access for each of the recipients who receive a forwarded message that includes the links from one of the original recipients.
According to an embodiment, a default set of permissions (e.g. read/write) are automatically set for any links that are included within an original message that is created by the author. Permission settings may be obtained using different menu/menu options. For example, menu 330 shows a selection for each recipient of the original message 300. Upon selection of one of the recipients from menu 330, option menu 335 is displayed that may be used to change the permissions for the selected recipient.
Menu 340 provides an option to modify the group to which the permissions apply. Selecting the modify group option 340 displays option menu 345 that allows a user to add a user from a group, remove a user from the group and set default permissions for the group. According to an embodiment, the original group is based on the recipients in the message (e.g. message 300). The author may add one or more other users to the group. For example, even though the message is only being sent to a first group of recipients, there may be other users who are on the same team that are authorized to view the linked content.
As illustrated, message 400 includes link 310 within the body of the message 400. An author creates message 400 that includes link 310 that is addressed to three recipients (Dan, Paul, Tim). A recipient of the message (e.g. Dan) determines to forward message 400 including link 310 to two additional recipients (Jed, Tom).
When message 400 is forwarded within message 450, the permission manager determines that message 400 has been forwarded to another recipient that includes a link. In response to detecting that message 400 is forwarded, the permission manager sends a notification to the author of message 400.
As illustrated, message 500 shows the author that a link was forwarded to another recipient. A notification message (e.g. message 500) may/may not be delivered to the author for authorized recipients of the link. For example, when a recipient of the forwarded message is already authorized to access the linked content, a notification message may not be sent to the author.
When one or more of the recipients are not authorized to access the linked content, message 500 may include permission option 510 that provides menu options for setting permissions for the recipients of the authorized message. For example, selecting permission option 510 displays options 520 that may be selected to set the permission for the link for each of the unauthorized recipients to read/write, read, write, deny access or some other option. Permission settings for the unauthorized users may be obtained using different menu/menu options.
For example, menu display 530 shows a selection for each recipient of the forwarded message 400 that is unauthorized. Upon selection of one of the recipients from menu 530, option menu 535 is displayed that may be used to change the permissions for the selected recipient.
Menu display 540 provides an option to set the permissions for each member of a group to the linked content and to set the permissions for one of the recipients. For example, when to which the permissions apply. Selecting the set group option 540 displays option menu 545 allows a user to set the permission for the group from read/write, read, write or deny.
As illustrated, message 600 provides notification 620 to the unauthorized recipients that the author has been notified that the recipients do not currently have access to the link and that the author is being requested to set the permissions for each of the unauthorized recipients.
Message 650 provides a notification to a recipient of the message that permissions have been set. For example, notification 660 may provide the recipient with the permissions that were set for the recipient by the author (e.g. read permission in the current example).
After a start block, process 700 moves to operation 710, where an author composes, permissions and sends an electronic message including a link. The electronic message may be any type of electronic message that includes a link. 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. According to an embodiment, a default set of permissions (e.g. read/write) are automatically set for any links for each of the recipients that are included within an original message that is created by the author. The permissions for the links may also be individually configured and/or more users may be authorized to access the linked content that are not recipients of the original message.
Flowing to operation 720, any links that are forwarded in a message to a recipient are detected. For example, when a message is forwarded by a messaging system, the message may be automatically parsed to detect the links. The links may be contained anywhere within a thread of the electronic message (e.g. within a first reply to a message, a third reply and the original message).
Moving to operation 730, a notification message is sent to the author of the original message including the link that the link was forwarded to another recipient. The recipient may/may not be authorized to access the content. The determination of whether the recipient is authorized may be made by the messaging system. For example, the messaging system may access a network share to determine permissions for one or more recipients. According to an embodiment, the author sets the conditions on when to receive notifications for recipients receiving a forwarded message that are authorized to access the content. When one or more of the recipients is not authorized to access the linked content, the notification message includes permission options for setting permissions to the linked content for the recipients of the authorized message. For example, the author may permission the recipients as a group and/or individually (e.g. read/write, read, write, deny).
Transitioning to operation 740, a notification message is sent to a recipient of the forwarded message including the link that indicates that the author has been notified of the forwarding of the link and that the author has been requested to set the permission for the recipient to access the linked content.
Flowing to operation 750, permission settings are received from the author. According to an embodiment, the permission settings are set within a reply message. In this way, the settings may be made while the author is offline and when the author goes online again, the permission settings are sent within the reply message to the permission manager. When the author is online, the permission settings may be sent directly to the permission manager in response to selecting a permission option within the displayed permission options.
Moving to operation 760, a message is sent to a recipient of the forwarded message when the permissions for the recipient to access the linked content have been received from the author.
The process then flows to an end block and returns to processing other actions.
The above specification, examples and data provide a complete description of the manufacture and use of the composition of the invention. Since many embodiments of the invention can be made without departing from the spirit and scope of the invention, the invention resides in the claims hereinafter appended.
Number | Name | Date | Kind |
---|---|---|---|
5355472 | Lewis | Oct 1994 | A |
5787480 | Scales et al. | Jul 1998 | A |
5864870 | Guck | Jan 1999 | A |
5903723 | Beck | May 1999 | A |
6219818 | Freivald et al. | Apr 2001 | B1 |
6275850 | Beyda et al. | Aug 2001 | B1 |
6314425 | Serbinis et al. | Nov 2001 | B1 |
6397261 | Erldridge et al. | May 2002 | B1 |
6405225 | Apfel | Jun 2002 | B1 |
6493758 | McLain | Dec 2002 | B1 |
6533822 | Kupiec | Mar 2003 | B2 |
6687741 | Ramaley et al. | Feb 2004 | B1 |
6718368 | Ayyadurai | Apr 2004 | B1 |
6763496 | Hennings et al. | Jul 2004 | B1 |
6782423 | Nakayama et al. | Aug 2004 | B1 |
6839741 | Tsai | Jan 2005 | B1 |
6883009 | Yoo | Apr 2005 | B2 |
6948131 | Neven | Sep 2005 | B1 |
6954934 | Kumar | Oct 2005 | B2 |
6978276 | Demsky et al. | Dec 2005 | B2 |
7003551 | Malik | Feb 2006 | B2 |
7028075 | Morris | Apr 2006 | B2 |
7054905 | Hanna et al. | May 2006 | B1 |
7089287 | Bellotti et al. | Aug 2006 | B2 |
7107518 | Ramaley et al. | Sep 2006 | B2 |
7113948 | Jhingan et al. | Sep 2006 | B2 |
7127670 | Bendik | Oct 2006 | B2 |
7130885 | Chandra et al. | Oct 2006 | B2 |
7143091 | Charnock et al. | Nov 2006 | B2 |
7178099 | Meyer et al. | Feb 2007 | B2 |
7194514 | Yen et al. | Mar 2007 | B1 |
7290034 | Budd et al. | Oct 2007 | B2 |
7353232 | Kalucha et al. | Apr 2008 | B1 |
7392280 | Rohall et al. | Jun 2008 | B2 |
7401291 | Ramaley et al. | Jul 2008 | B2 |
7409394 | Lee | Aug 2008 | B2 |
7409424 | Parker | Aug 2008 | B2 |
7424543 | Rice, III | Sep 2008 | B2 |
7424676 | Carlson et al. | Sep 2008 | B1 |
7444382 | Malik | Oct 2008 | B2 |
7509386 | Miyashita | Mar 2009 | B2 |
7536440 | Budd et al. | May 2009 | B2 |
7546352 | Sukadev et al. | Jun 2009 | B1 |
7565409 | Heilbron et al. | Jul 2009 | B2 |
7580982 | Owen et al. | Aug 2009 | B2 |
7593943 | Clarke et al. | Sep 2009 | B2 |
7650387 | Foo | Jan 2010 | B2 |
7730082 | Sah et al. | Jun 2010 | B2 |
7752269 | Chan et al. | Jul 2010 | B2 |
7783711 | LeVasseur et al. | Aug 2010 | B2 |
7783972 | Camps et al. | Aug 2010 | B2 |
7814425 | O'Shaugnessy et al. | Oct 2010 | B1 |
7840642 | Naick et al. | Nov 2010 | B2 |
7908332 | Malik | Mar 2011 | B2 |
7917591 | Vakkalanka | Mar 2011 | B2 |
7970850 | Callanan | Jun 2011 | B1 |
8108464 | Rochelle et al. | Jan 2012 | B1 |
8140975 | Lemay et al. | Mar 2012 | B2 |
8145707 | Thayer et al. | Mar 2012 | B2 |
8176123 | Wang et al. | May 2012 | B1 |
8185591 | Lewis | May 2012 | B1 |
8196029 | Rucker | Jun 2012 | B1 |
8458269 | Friedman et al. | Jun 2013 | B2 |
8682989 | Meisels et al. | Mar 2014 | B2 |
8965983 | Costenaro et al. | Feb 2015 | B2 |
9137185 | Costenaro et al. | Sep 2015 | B2 |
9165285 | Schultz et al. | Oct 2015 | B2 |
20010051991 | Beyda et al. | Dec 2001 | A1 |
20010054073 | Ruppert et al. | Dec 2001 | A1 |
20020016818 | Kirani et al. | Feb 2002 | A1 |
20020059384 | Kaars | May 2002 | A1 |
20020062356 | Clarke et al. | May 2002 | A1 |
20020065892 | Malik | May 2002 | A1 |
20020107931 | Singh et al. | Aug 2002 | A1 |
20020129056 | Conant et al. | Sep 2002 | A1 |
20020133633 | Kumar | Sep 2002 | A1 |
20020138586 | Paleiov et al. | Sep 2002 | A1 |
20020143691 | Ramaley et al. | Oct 2002 | A1 |
20020174010 | Rice | Nov 2002 | A1 |
20030028528 | Christensen et al. | Feb 2003 | A1 |
20030028600 | Parker | Feb 2003 | A1 |
20030055907 | Stiers | Mar 2003 | A1 |
20030112273 | Hadfield et al. | Jun 2003 | A1 |
20030131062 | Miyashita | Jul 2003 | A1 |
20040034688 | Dunn | Feb 2004 | A1 |
20040068545 | Daniell et al. | Apr 2004 | A1 |
20040103044 | Vandewater et al. | May 2004 | A1 |
20040158607 | Coppinger et al. | Aug 2004 | A1 |
20040186894 | Jhingan et al. | Sep 2004 | A1 |
20040243672 | Markki et al. | Dec 2004 | A1 |
20040261082 | Steere et al. | Dec 2004 | A1 |
20050010799 | Kelley et al. | Jan 2005 | A1 |
20050033813 | Bhogal et al. | Feb 2005 | A1 |
20050044492 | Ramaley et al. | Feb 2005 | A1 |
20050060382 | Spector | Mar 2005 | A1 |
20050091289 | Shappell et al. | Apr 2005 | A1 |
20050114672 | Duncan et al. | May 2005 | A1 |
20050122345 | Kim et al. | Jun 2005 | A1 |
20050166154 | Wilson et al. | Jul 2005 | A1 |
20050188026 | Hilbert et al. | Aug 2005 | A1 |
20050251443 | Chan | Nov 2005 | A1 |
20050289221 | Steele | Dec 2005 | A1 |
20060004819 | Claudatos et al. | Jan 2006 | A1 |
20060020673 | Sorge et al. | Jan 2006 | A1 |
20060031309 | Luoffo et al. | Feb 2006 | A1 |
20060075046 | Yozell-Epstein et al. | Apr 2006 | A1 |
20060095527 | Malik | May 2006 | A1 |
20060161516 | Clarke et al. | Jul 2006 | A1 |
20060195526 | Lederer et al. | Aug 2006 | A1 |
20060206570 | Heidloff et al. | Sep 2006 | A1 |
20060224679 | Kikuchi et al. | Oct 2006 | A1 |
20060242208 | Goldick | Oct 2006 | A1 |
20060259524 | Horton | Nov 2006 | A1 |
20060282762 | Diamond et al. | Dec 2006 | A1 |
20060294455 | Morris et al. | Dec 2006 | A1 |
20070005717 | Thierry et al. | Jan 2007 | A1 |
20070022166 | Bhogal et al. | Jan 2007 | A1 |
20070118598 | Bedi et al. | May 2007 | A1 |
20070118794 | Hollander et al. | May 2007 | A1 |
20070130259 | Daniell et al. | Jun 2007 | A1 |
20070136814 | Lee et al. | Jun 2007 | A1 |
20070143419 | Plas | Jun 2007 | A1 |
20070143425 | Kieselbach et al. | Jun 2007 | A1 |
20070168459 | Fujita et al. | Jul 2007 | A1 |
20070192490 | Minhas | Aug 2007 | A1 |
20070198913 | Terao et al. | Aug 2007 | A1 |
20070208782 | Carter et al. | Sep 2007 | A1 |
20070233794 | Singh | Oct 2007 | A1 |
20070271344 | Danasekaran et al. | Nov 2007 | A1 |
20070271502 | Bedi et al. | Nov 2007 | A1 |
20070283267 | Jeffrey et al. | Dec 2007 | A1 |
20080005139 | Hysom et al. | Jan 2008 | A1 |
20080028017 | Garbow et al. | Jan 2008 | A1 |
20080059539 | Chin et al. | Mar 2008 | A1 |
20080120382 | Heidloff et al. | May 2008 | A1 |
20080244721 | Barrus | Oct 2008 | A1 |
20080250474 | Bhogal et al. | Oct 2008 | A1 |
20080256458 | Aldred et al. | Oct 2008 | A1 |
20080281924 | Gadwale | Nov 2008 | A1 |
20080282159 | Vanderwende et al. | Nov 2008 | A1 |
20080288862 | Smetters et al. | Nov 2008 | A1 |
20090006948 | Parker et al. | Jan 2009 | A1 |
20090024931 | Bae | Jan 2009 | A1 |
20090030919 | Brezina et al. | Jan 2009 | A1 |
20090030997 | Malik | Jan 2009 | A1 |
20090031245 | Brezina et al. | Jan 2009 | A1 |
20090063520 | Kimura | Mar 2009 | A1 |
20090094514 | Dargahl et al. | Apr 2009 | A1 |
20090100109 | Turski et al. | Apr 2009 | A1 |
20090157831 | Tian et al. | Jun 2009 | A1 |
20090187852 | Tsurata | Jul 2009 | A1 |
20090210721 | Phillips | Aug 2009 | A1 |
20090248808 | Izumi | Oct 2009 | A1 |
20090313256 | Konduri et al. | Dec 2009 | A1 |
20090319618 | Affronti et al. | Dec 2009 | A1 |
20100011032 | Fukuoka | Jan 2010 | A1 |
20100017701 | Bargeron et al. | Jan 2010 | A1 |
20100023492 | Lucas | Jan 2010 | A1 |
20100057765 | Dispensa et al. | Mar 2010 | A1 |
20100057864 | Laird-McConnell | Mar 2010 | A1 |
20100057872 | Koons et al. | Mar 2010 | A1 |
20100070448 | Omoigui | Mar 2010 | A1 |
20100070588 | Sinn et al. | Mar 2010 | A1 |
20100076989 | Jakobson | Mar 2010 | A1 |
20100082713 | Frid-Nielsen et al. | Apr 2010 | A1 |
20100095198 | Bultrowicz et al. | Apr 2010 | A1 |
20100100566 | Hronopoulos | Apr 2010 | A1 |
20100106551 | Koskimies et al. | Apr 2010 | A1 |
20100125640 | Boddington et al. | May 2010 | A1 |
20100169295 | Kanomori | Jul 2010 | A1 |
20100169439 | O'Sullivan et al. | Jul 2010 | A1 |
20100169440 | O'Sullivan et al. | Jul 2010 | A1 |
20100191774 | Mason et al. | Jul 2010 | A1 |
20100198927 | Tonnison et al. | Aug 2010 | A1 |
20100228611 | Shenfield | Sep 2010 | A1 |
20100228989 | Neystadt et al. | Sep 2010 | A1 |
20100235763 | Massand | Sep 2010 | A1 |
20100273456 | Wolovitz et al. | Oct 2010 | A1 |
20100281224 | Ho et al. | Nov 2010 | A1 |
20100306180 | Johnson et al. | Dec 2010 | A1 |
20100306330 | Friedman | Dec 2010 | A1 |
20110055177 | Chakra et al. | Mar 2011 | A1 |
20110065419 | Book | Mar 2011 | A1 |
20110066955 | Olson et al. | Mar 2011 | A1 |
20110113104 | Bhogal et al. | May 2011 | A1 |
20110119593 | Jacobson et al. | May 2011 | A1 |
20110145363 | Ananthanarayanan et al. | Jun 2011 | A1 |
20110161435 | Mancuso | Jun 2011 | A1 |
20110276897 | Crevier et al. | Nov 2011 | A1 |
20110295959 | Martin et al. | Dec 2011 | A1 |
20120095890 | Santarlas | Apr 2012 | A1 |
20120117159 | Chakra et al. | May 2012 | A1 |
20120151379 | Schultz et al. | Jun 2012 | A1 |
20120192064 | Antebi et al. | Jul 2012 | A1 |
20120278281 | Meisels et al. | Nov 2012 | A1 |
20120278401 | Meisels et al. | Nov 2012 | A1 |
20120278402 | Limont et al. | Nov 2012 | A1 |
20120278403 | Costenaro et al. | Nov 2012 | A1 |
20120278404 | Meisels et al. | Nov 2012 | A1 |
20120278405 | Costenaro et al. | Nov 2012 | A1 |
20120278407 | Meisels et al. | Nov 2012 | A1 |
20120284344 | Costenaro et al. | Nov 2012 | A1 |
20140173423 | Meisels et al. | Jun 2014 | A1 |
20160006832 | Costenaro et al. | Jan 2016 | A1 |
20160043976 | Schultz et al. | Feb 2016 | A1 |
Number | Date | Country |
---|---|---|
1449525 | Oct 2003 | CN |
1749998 | Mar 2006 | CN |
1753400 | Mar 2006 | CN |
1795654 | Jun 2006 | CN |
1831827 | Sep 2006 | CN |
1971553 | May 2007 | CN |
101009667 | Aug 2007 | CN |
101079846 | Nov 2007 | CN |
101655845 | Feb 2010 | CN |
101655870 | Feb 2010 | CN |
933712 | Aug 1999 | EP |
H05135056 | Jun 1993 | JP |
08235231 | Sep 1996 | JP |
10269236 | Oct 1998 | JP |
11161584 | Jun 1999 | JP |
11345182 | Dec 1999 | JP |
2001043151 | Feb 2001 | JP |
2001307006 | Nov 2001 | JP |
2002049615 | Feb 2002 | JP |
2002091813 | Mar 2002 | JP |
2005011354 | Jan 2005 | JP |
2005025620 | Jan 2005 | JP |
2005084945 | Mar 2005 | JP |
2005129061 | May 2005 | JP |
2007501969 | Feb 2007 | JP |
2007213511 | Aug 2007 | JP |
2008-500646 | Jan 2008 | JP |
2373653 | Nov 2009 | RU |
2003052622 | Jun 2003 | WO |
2005027404 | Mar 2004 | WO |
2007-133504 | Nov 2007 | WO |
2009023769 | Feb 2009 | WO |
2009158108 | Dec 2009 | WO |
2010041505 | Apr 2010 | WO |
2010104659 | Sep 2010 | WO |
Entry |
---|
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=rep1&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. |
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. |
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. |
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. |
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.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 Jul. 1, 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 Jul. 1, 2011 at http://support.microsoft.com/kb/197651; 4 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. |
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. |
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. |
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. |
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. |
U.S. Appl. No. 12/963,091, entitled Shared Attachments, filed Dec. 8, 2010. |
U.S. Appl. No. 13/096,830 entitled Making Document Changes by Replying to Electronic Messages, filed Apr. 28, 2011. |
U.S. Appl. No. 13/096,854 entitled Presenting Links to Content as Attachments in Electronic Messages, filed Apr. 28, 2011. |
U.S. Appl. No. 13/096,869, entitled Presenting Link Information Near Links Within Electronic Messages, filed Apr. 28, 2011. |
U.S. Appl. No. 13/096,880, entitle Upload of Attachment and Insertion of Link Into Electronic Messages, filed Apr. 28, 2011. |
U.S. Appl. No. 13/096,899, entitled Storing Metadata Inside File to Reference Shared Version of File, filed Apr. 28, 2011. |
U.S. Appl. No. 13/102,431, entitled Changes to Documents are Automatically Summarized in Electronic Messages, filed May 6, 2011. |
U.S. Appl. No. 13/096,936, entitled Automatic Uploading of Attachment to a Shared Location, filed Apr. 28, 2011. |
U.S. Appl. No. 13/096,910, entitled “Uploading Attachment to Shared Location and Replacing with a Link”, filed May 12, 2012. |
Docstoc; “OneClick: Email Large Documents Without Attaching Files”; retrieved Jan. 7, 2011, from http://www.docstoc.com/oneclick/; 4 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. |
MSDN.com; “How to Share Large Files Without Attaching Them”; Aug. 21, 2008; retrieved Jan. 7, 2011, from http://blogs.msdn.com/b/outlook/archive/2008/08/21/how-to-share-large-files-without-attaching-them.aspx; 3 pgs. |
Sendthisfile.com; “Welcome to SendThisFile”; accessed Jan. 7, 2011, from http://www.sendthisfile.com/; 1 pg. |
PCT Search Report in PCT/US2012/035710 dated Sep. 28, 2012. |
Office Action dated Nov. 13, 2012, issued in U.S. Appl. No. 13/096,910. |
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. |
Microsoft Support; “You may receive an ‘Outlook blocked access to the following potentially unsafe attachments’ message in Outlook”; Last Review: May 13, 2010; http://suport.microsoft.com/kb/829982; 7 pgs. |
Office Action dated Jun. 20, 2012, issued in U.S. Appl. No. 13/096,899. |
Office Action dated Sep. 7, 2012, issued in U.S. Appl. No. 12/963,0919. |
Office Action dated Oct. 3, 2012, issued in U.S. Appl. No. 12/096,830. |
Office Action dated Jun. 4, 2013, issued in U.S. Appl. No. 13/096,936. |
Office Action dated Jun. 10, 2013, issued in U.S. Appl. No. 13/102,431. |
Office Action dated Jun. 11, 2013, issued in U.S. Appl. No. 13/096,910. |
Office Action dated Jun. 20, 2013, issued in U.S. Appl. No. 13/096,854. |
Office Action dated Jun. 21, 2013, issued in U.S. Appl. No. 13/096,830. |
Office Action dated Jun. 21, 2013, issued in U.S. Appl. No. 13/096,869. |
Office Action dated Jul. 16, 2013, issued in U.S. Appl. No. 13/096,880. |
Office Action dated Sep. 24, 2013, issued in U.S. Appl. No. 13/096,899. |
Office Action dated Feb. 11, 2013, issued in U.S. Appl. No. 13/096,899. |
PCT Search Report in PCT/US2012/035707 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/035708 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/035709 dated Nov. 26, 2012. |
PCT Search Report in PCT/US2012/036701 dated Nov. 28, 2012. |
PCT Search Report in PCT/US2012/036702 dated Dec. 3, 2012. |
Office Action dated Nov. 21, 2012, issued in U.S. Appl. No. 13/096,936. |
Office Action dated Nov. 26, 2012, issued in U.S. Appl. No. 13/102,431. |
Office Action dated Dec. 11, 2012, issued in U.S. Appl. No. 13/096,854. |
Office Action dated Dec. 14, 2012, issued in U.S. Appl. No. 13/096,869. |
Office Action dated Dec. 26, 2012, issued in U.S. Appl. No. 13/096,880. |
Office Action dated Jan. 9, 2013, issued in U.S. Appl. No. 12/963,091. |
Office Action dated Apr. 9, 2015, issued in U.S. Appl. No. 13/096,936, 23 pgs. |
Office Action dated Apr. 20, 2015, issued in U.S. Appl. No. 13/096,880, 25 pgs. |
Notice of Allowance dated Apr. 28, 2015, issued in U.S. Appl. No. 13/096,910, 23 pgs. |
U.S. Appl. No. 14/188,666 entitled Making Document Changes by Replying to Electronic Messages, filed Feb. 24, 2014. |
Office Action dated Jan. 15, 2014, issued in U.S. Appl. No. 13/096,854. |
Office Action dated Apr. 8, 2014, issued in U.S. Appl. No. 13/102,431, 16 pgs. |
Wikipedia, Message, http://en.wikipedia.org/wikilMessage retrieved Jan. 9, 2014, p. 1-2. |
Office Action dated Jun. 16, 2014, issued in U.S. Appl. No. 12/963,091, 22 pgs. |
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 (cited in Apr. 23, 2015 EP Comm.). |
EP Communication dated Apr. 23, 2015 in Appln No. PCT/US2012/035710, 8 pgs. |
Notice of Allowance dated Jun. 15, 2015, issued in U.S. Appl. No. 12/963,091, 28 pgs. |
Office Action dated Jun. 23, 2015, issued in U.S. Appl. No. 13/096,899, 30 pgs. |
Office Action dated Jun. 26, 2015, issued in U.S. Appl. No. 13/096,854, 50 pgs. |
EP Extended Search Report in PCT/US2012/036702 dated Aug. 12, 2014, 6 pgs. |
Office Action dated Jul. 10, 2014, issued in U.S. Appl. No. 13/096,869, 29 pgs. |
Office Action dated Jul. 16, 2014, issued in U.S. Appl. No. 13/102,431, 20 pgs. |
Office Action dated Aug. 14, 2014, issued in U.S. Appl. No. 13/096,854, 32 pgs. |
EP Extended Search Report in PCT/US2012/035708 dated Aug. 29, 2014, 6 pgs. |
EP Extended Search Report in PCT/US2012/035709 dated Sep. 22, 2014, 6 pgs. |
Office Action dated Sep. 25, 2014, issued in U.S. Appl. No. 12/963,091, 24 pgs. |
Office Action dated Sep. 26, 2014, issued in U.S. Appl. No. 13/096,936, 29 pgs. |
Office Action dated Oct. 6, 2014, issued in U.S. Appl. No. 13/096,880, 31 pgs. |
Office Action dated Oct. 7, 2014, issued in U.S. Appl. No. 13/096,910, 32 pgs. |
Office Action dated Oct. 23, 2014, issued in U.S. Appl. No. 13/096,899, 24 pgs. |
EP Extended Search Report in PCT/US2012/035707 dated Oct. 21, 2014, 6 pgs. |
EP Search Report in PCT/US2012/036701 dated Dec. 4, 2014, 5 pgs. |
Notice of Allowance dated Oct. 14, 2014 issued in U.S. Appl. No. 13/102,431, 51 pgs. |
Troost et al., Internet Engineering Task Force, RFC 2183 dated Aug. 1997, 12 pgs. available at: www.rfc-editor.org/rfc/rfc2183.txt. |
Office Action dated Jan. 31, 2014, issued in U.S. Appl. No. 13/096,869. |
U.S. Appl. No. 14/887,086, entitled Shared Attachments, filed Oct. 19, 2015. |
U.S. Appl. No. 14/853,098, entitled “Uploading Attachment to Shared Location and Replacing with a Link”, filed Sep. 14, 2015. |
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 Patent Application No. 201280021905.6, dated Dec. 2, 2015, 14 pgs. |
Office Action dated Nov. 23, 2015, issued in U.S. Appl. No. 13/096,936, 21 pgs. |
Office Action dated Jan. 5, 2016, issued in U.S. Appl. No. 13/096,899, 19 pgs. |
Chinese Office Action and Search Report Issued in Chinese Patent Application No. 201280020441.7, dated Dec. 15, 2015, 18 Pages. |
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. |
European Office Action Issued in Application No. 12777397.6 , dated Mar. 3, 2016, 6 pgs. |
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 dated Mar. 22, 2016, 5 Pages. |
Japanese Office Action Issued in Patent Application No. 2014-508171, dated Mar. 11, 2016, 6 Pages. |
Taiwan Office Action and Search Report Issued in Taiwan Patent Application No. 101110617, dated Mar. 21, 2016, 6 Pages. |
U.S. Appl. No. 13/096,854, Office Action dated May 2, 2016, 35 pgs. |
U.S. Appl. No. 13/096,880, Office Action dated Feb. 19, 2016, 19 pgs. |
U.S. Appl. No. 13/096,936, Office Action dated Mar. 22, 2016, 20 pgs. |
U.S. Appl. No. 14/188,666, Office Action dated Feb. 26, 2016, 77 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. |
Japanese Office Action Issued in Patent Application No. 2014-510384, dated May 9, 2016, 6 Pages. |
Russian Office Action Issued in Patent Application No. 2013149178, dated May 20, 2016, With English Translation. 9 Pages. |
Australian Office Action Full Examination Report Issued in Patent Application No. 2012253808, dated Jul. 9, 2016, 3 Pages. |
Chinese Office Action Issued in Patent Application No. 201280021905.6, dated Jul. 1, 2016, With English translation. 10 pgs. |
Japanese Notice Of Allowance Issued in Patent Application No. 2014-508169, dated Jul. 12, 2016, 3 Pages. Without English Translation. |
Japanese Office Action Issued in Patent Application No. 2014-510385, dated May 30, 2016, With english translation. 9 Pages. |
Japanese Notice of Allowance Issued in Patent Application No. 2014-508171, dated Aug. 4, 2016, 4 Pages. |
Australian Notice of Allowance in Application 2012253808, dated Nov. 28, 2016, 2 pages. |
Chinese Notice of Allowance in Application 201280021954.X, dated Dec. 22, 2016, 4 pages. |
Chinese Office Action in Application 201280020430.9, dated Feb. 27, 2017, 8 pages. |
Japanese Notice of Allowance in Application 2014-510385, dated Oct. 13, 2016, 4 pages. |
Japanese Office Action in Application 2014-510384, dated Oct. 13, 2016, 6 pages. |
Taiwanese Notice of Allowance in Application 101110617, dated Nov. 16, 2016, 4 pages. |
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,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 Sep. 18, 2015, 3 pages. |
U.S. Appl. No. 13/096,880, Advisory Action dated Oct. 15, 2015, 4 pages. |
U.S. Appl. No. 13/102,431, Notice of Allowance dated Jan. 27, 2015, 2 pages. |
U.S. Appl. No. 14/188,666, Notice of Allowance dated Apr. 20, 2017, 6 pages. |
Japaneses Notice of Allowance in Application 2014-510384, dated Mar. 31, 2017, 3 page. (No English Translation.). |
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. |
Second Office Action and Search Report Issued in Chinese Patent Application No. 201280020430.9, dated Nov. 1, 2016, 11 Pages. |
JP: Office Action Issued in Japanese Patent Application No. 2014-508168, dated Oct. 7, 2016, 8 Pages. |
JP: Notice of Allowance Issued in Japanese Patent Application No. 2014-508171, dated Aug. 4, 2016, 4 Pages. |
AU: Office Action Issued in Australian Patent Application No. 2012253808, dated Sep. 16, 2016, 3 Pages. |
U.S. Appl. No. 14/188,666, Office Action dated Oct. 25, 2016, 24 pgs. |
U.S. Appl. No. 13/096,854, Office Action dated Jan. 11, 2017, 39 pgs. |
U.S. Appl. No. 13/096,880, Office Action dated Oct. 25, 2016, 20 pgs. |
Taiwan Office Action and Search Report Issued in Taiwan Patent Application No. 101110617, dated Jul. 26, 2016, 7 Pages. |
Japanese Notice of Allowance Issued in Patent Application No. 2014-508170, dated Sep. 13, 2016, 3 Pages. |
Third Office Action Issued in Chinese Patent Application No. 201280020441.7, dated Jan. 25, 2017, 10 Pages. |
Chinese Office Action Issued in Patent Application No. 201280020342.9, dated Aug. 1, 2016, With English translation. 10 pages. |
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. |
European Office Action Issued in Application No. 12782951.3 , dated Aug. 17, 2016, 6 pages. |
U.S. Appl. No. 13/096,899, Office Action dated Sep. 26, 2016, 36 pages. |
U.S. Appl. No. 14/887,086, Office Action dated Jan. 26, 2018, 19 pages. |
Canadian Office Action in Application 2835323, dated Jan. 25, 2018, 4 pages. |
Chinese Decision on Reexamination in Application 201280021905.6, dated Jan. 29, 2018, 14 pages. (No English Translation.). |
European Summons in Application 12782951.3, dated Feb. 13, 2018, 7 pages. |
U.S. Appl. No. 14/853,098, Office Action dated Feb. 8, 2018, 11 pages. |
European Office Action in Application 12777397.6, dated Jan. 3, 2018, 6 pages. |
U.S. Appl. No. 13/096,880, Office Action dated Jun. 14, 2017, 13 pages. |
U.S. Appl. No. 14/188,666, Supplemental Notice of Allowance dated Jul. 11, 2017, 2 pages. |
U.S. Appl. No. 13/096,854, Office Action dated Jun. 29, 2017, 29 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, Office Action dated Oct. 6, 2017, 16 pages. |
U.S. Appl. No. 13/096,899, Office Action dated Aug. 15, 2017, 24 pages. |
U.S. Appl. No. 14/853,098, Office Action dated Aug. 4, 2017, 12 pages. |
Chinese Office Action in Application 201280020441.7, dated Jun. 2, 2017, 9 pages. |
Russian Notice of Allowance in Application 2013149178, dated Jun. 15, 2017, 17 pages. |
Chinese Notice of Allowance in Application 201280020430.9, dated Aug. 29, 2017, 4 pages. |
Chinese Office Action in Application 201280021905.6, dated Sep. 19, 2017, 9 pages. |
Korean Office Action in Application 10-2013-7028430, dated Oct. 23, 2017, 11 pages. |
Chinese Office Action in Application 201280020342.9, dated Sep. 29, 2017, 11 pages. |
European Communication in Application 12777074.1, dated Oct. 16, 2017, 7 pages. |
Korean Office Action in Application 10-2013-7028280, dated Oct. 21, 2017, 11 pages. |
Chinese Office Action in Application 201280020368.3, dated Nov. 6, 2017, 10 pages. |
Korean Office Action in Application 10-2013-702827, 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. 27, 2017, 4 pages. |
U.S. Appl. No. 13/096,854, Office Action dated Dec. 28, 2017, 29 pages. |
Re@DNotify, How to forward emails “As Attachments”, Retrieved on Jul. 2, 2009 by the WayBack Machine, 7 pages. |
Chinese Office Action in Application 201280020368.8, dated Apr. 8, 2018, 18 pages. |
Chinese Office Action in Application 201280020441.7, dated May 4, 2018, 8 pages. |
European Extended Search Report in Application 12776501.4, dated Jun. 6, 2018, 7 pages. |
Korean Notice of Allowance in Application 10-2013-7029310, dated May 21, 2018, 4 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-7028430, dated May 14, 2018, 8 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, 8 Pages. |
“Final Office Action Issued in Korean Patent Application No. 10-2013-7029294”, dated May 28, 2018, 05 Pages. |
U.S. Appl. No. 13/096,899, Office Action dated Mar. 19, 2018, 20 pages. |
“Final Office Action Issued in U.S. Appl. No. 13/096,854”, dated Jul. 23, 2018, 25 Pages. |
Chinese Notice of Allowance in Application 201280021905.6, dated Mar. 27, 2018, 4 pages. |
Chinese Decision on Reexamination in Application 201280020342.9, dated Mar. 30, 2018 15 pages. |
U.S. Appl. No. 14/853,098, Notice of Allowance dated May 31, 2018, 14 pages. |
U.S. Appl. No. 14/887,086, Notice of Allowance dated Jun. 6, 2018, 7 pages. |
“Office Action Issued in Canadian Patent Application No. 2,835,323”, dated Sep. 17, 2018, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20120284345 A1 | Nov 2012 | US |