US20110010424A1 - Unified addressing, sending, and receiving collaboration service - Google Patents
Unified addressing, sending, and receiving collaboration service Download PDFInfo
- Publication number
- US20110010424A1 US20110010424A1 US12/690,038 US69003810A US2011010424A1 US 20110010424 A1 US20110010424 A1 US 20110010424A1 US 69003810 A US69003810 A US 69003810A US 2011010424 A1 US2011010424 A1 US 2011010424A1
- Authority
- US
- United States
- Prior art keywords
- communication modality
- collaboration
- computer
- sending
- unified
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/40—Information retrieval; Database structures therefor; File system structures therefor of multimedia data, e.g. slideshows comprising image and additional audio data
- G06F16/48—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually
- G06F16/489—Retrieval characterised by using metadata, e.g. metadata not derived from the content or metadata generated manually using time information
Definitions
- the disclosed technology pertains to multi-user collaboration environments, and more particularly to facilitating the transmission of content between collaboration users.
- Embodiments of the disclosed technology include a unified address or common addressing arrangement that allows for the sharing, posting, and notification of collaboration content independent of any particular communication mechanism being selected as a common communication modality for the collaboration team.
- Collaboration team members are thus no longer interrupted and burdened with needing to know, let alone specify, which communication mechanism should be applied every time he or she wishes to communicate with other collaboration team members.
- Embodiments of the disclosed technology may allow for the mapping of a unified “send” action on the unified address to be mapped to a specific communication modality such as sending an e-mail message, posting a blog entry, or sending an SMS message, for example.
- a specific communication modality such as sending an e-mail message, posting a blog entry, or sending an SMS message, for example.
- each collaboration team member may use a unified address technique for posting, sending, publishing, sharing, commenting, responding, editing, or performing some other type of information interaction event in connection with another team member regardless of whatever communication modality is actually being used.
- embodiments of the disclosed technology essentially move collaborations from a “First Personalized Mechanism then Share” paradigm to a “First Share then Personalized Mechanism” paradigm. Unlike current systems, implementations of the disclosed technology do not require that each member of a given collaboration team have the same technology installed or available as all of the other members of the team.
- FIG. 1 is a block diagram that illustrates an example of a collaboration system using current collaboration tools.
- FIG. 2 is a block diagram that illustrates an example of a unified addressing collaboration system in accordance with embodiments of the disclosed technology.
- FIG. 3 is a block diagram that illustrates an example of a unified addressing configuration specification in accordance with embodiments of the disclosed technology.
- FIG. 4 illustrates an example of a system in which embodiments of the disclosed technology may be implemented.
- FIG. 5 is a flowchart that illustrates an example of a machine-controlled method of sending a contribution to a collaboration team in accordance with embodiments of the disclosed technology.
- FIG. 6 is a flowchart that illustrates an example of a machine-controlled method of receiving a contribution from a collaboration team member in accordance with embodiments of the disclosed technology.
- Embodiments of the disclosed technology may include a common or unified addressing mechanism that may be used in connection with any of a number of different communication modalities.
- a common addressing and sending/receiving mechanism may be mapped to one of several communication modalities that may be used by a particular collaboration team member.
- a team member that desires to share certain information with other team members is thus not burdened with needing to know, let alone select, the particular information sharing mechanism selected by the team or by each individual recipient; rather, each member of the team may select his or her own communication preference without needing to inform the sender of the selected modality.
- a unified address and sending/receiving mechanism in accordance with the disclosed technology may be accessed from technology-specific communication tools such as e-mail messages, twitter posts, or blog entries.
- the unified address and sending/receiving mechanism may be incorporated directly into applications or accessed indirectly through special addresses or tags such as embedded comments or embedded fields.
- a team member may tweet, i.e., enter a twitter post that may have a special hash tag to enable the backend server to recognize and send the tweet through a unified communications server to other team members that may be using other communication modalities.
- the team member may send an e-mail message with special comments in the subject line or post blog entries with embedded tags.
- Particular addresses may be preconfigured to have associated therewith certain carbon copies.
- a backend communications server may recognize the carbon copies and then translate between the sending communication modality and other receiving modalities that are unique to other members of the team. For example, if another team member specifies text messaging as his or her preferred communication modality, the system may send collaboration contributions to that user via text messages, regardless of whatever communication modality was used to send the information by the posting user.
- FIG. 1 is a block diagram that illustrates an example of a collaboration system 100 using current collaboration tools.
- a collaboration team consists of four team members—Amy 102 , Bill 104 , Charlie 106 , and David 108 —that communicate with each other using four different types of communication modalities: Internet 110 , e.g., blog postings, e-mail 112 , file sharing 114 , and voice/text messaging 116 .
- Internet 110 e.g., blog postings, e-mail 112 , file sharing 114 , and voice/text messaging 116 .
- user Amy 102 has made all four communication modalities 110 - 116 available to herself, the other users have only selected, e.g., installed and/or activated, one or two different modalities for communication in the collaboration.
- Amy 102 wishes to communicate with user Charlie 106 , for example, Amy 102 must have available, installed, and ready to use clients for the same technology that Charlie 106 has selected as his preferred communication modality, i.e., file sharing 114 . Similarly, if Amy 102 wishes to communicate with user David 108 , Amy 102 must have accessible to her the same communication modality, i.e., voice/text 116 , that David 108 has selected.
- Amy may have all of the communication modalities 110 - 116 available to her and may thus communicate with each of the other team members 104 - 108 , not all of the other team members 104 - 108 have all of the communication modalities 110 - 116 installed and available to them. Thus, communication between all of the team members 102 - 108 is simply not achievable using the illustrated system 100 .
- FIG. 2 is a block diagram that illustrates an example of a unified addressing collaboration system 200 .
- each of the users Amy 102 , Bill 104 , Charlie 106 , and David 108 have a unified addressing inbox/outbox 202 - 208 , respectively.
- Each unified addressing inbox/outbox 202 - 208 is configured to select a particular communication modality for the corresponding user based on a preference indicated by the corresponding user, for example.
- Each unified addressing inbox/outbox 202 - 208 is also configured to provide an identification of the selected communication modality to the other unified addressing inbox/outboxes 202 - 208 to facilitate the passing of information between the users 102 - 108 .
- Charlie 106 drafts a technical specification for a particular aspect of a new software application. Charlie 106 then sends the technical specification to the rest of his team using his unified addressing inbox/outbox 206 .
- Charlie's unified addressing inbox/outbox 206 is essentially acting as a universal outbox.
- Charlie's unified addressing inbox/outbox 206 may communicate with David's unified addressing inbox/outbox 208 , for example, to determine David's preferred communication modality, i.e., voice/text 116 .
- Charlie's unified addressing inbox/outbox 206 may thus send the technical specification as a text message to David's unified addressing inbox/outbox 208 .
- Charlie's unified addressing inbox/outbox 206 may also communicate with Amy's and Bill's unified addressing inbox/outboxes 202 and 204 , respectively, to determine Amy's and Bill's preferred communication modalities and send the technical specification to both Amy 102 and Bill 104 in accordance with the communication modality for each corresponding user.
- FIG. 3 is a block diagram that illustrates an example of a unified addressing configuration specification 300 that includes a listing of communication modality preferences for a particular user.
- the user can essentially establish particular carbon copies for certain collaboration contributions and specify the circumstances under which they are to occur.
- each collaboration team member can configure his or her account so that, whenever another team member posts a pertinent contribution, the system will be able to determine how to distribute the contribution to the other collaboration team members. That is, the user can essentially configure rules that specify how he or she wants his or her content shared to other group members as the content is posted.
- the user has expressed a preference for sending and receiving information in connection with two different collaboration groups: “Tech 1 ” and “Tech 2 .”
- the user has expressed a preference for all of his or her contributions to be sent via a particular e-mail messaging service using a specified email address.
- the user has also expressed a preference for receivable content to be delivered via a text messaging service to the phone number provided in the unified addressing configuration specification 300 .
- the user has expressed a preference for sending information via postings to a specified blog.
- the user has not, however, indicated in the unified addressing configuration specification 300 a particular communication modality for receiving content in connection with the “Tech 2 ” collaboration.
- Embodiments using the illustrated unified addressing configuration specification 300 may assign a default communication modality for receiving content pertaining to the “Tech 2 ” collaboration, for example.
- a user may use his or her personal unified addressing configuration specification 300 to also provide information that may be pertinent to the selected communication modalities. For example, a user may provide his or her current phone number and/or e-mail address. Additionally, the user may wish to use different phone numbers and/or different e-mail addresses for different collaborations. Thus, if a user were to be assigned a new phone number, he or she would only need to update his or her unified addressing configuration specification 300 —there would be no need to proactively alert the other team members to the updated information because the other users' unified addressing inbox/outboxes would automatically retrieve the information as part of the information transmission process.
- FIG. 4 illustrates an example of a system 400 in which embodiments of the disclosed technology may be implemented.
- the system 400 includes a network 402 , such as the Internet or a company's intranet, that may facilitate interaction between multiple devices such as desktop computers 404 and 406 and laptop computers 406 .
- Other devices such as a personal digital assistant (PDA) 410 and mobile devices 412 and 414 , e.g., cellular or smart phones, may also be used as part of the system 400 .
- PDA personal digital assistant
- a remote database 416 may be used to store information pertaining to users' unified addressing inbox/outboxes such as each user's unified addressing configuration specification 300 . Alternatively, such information may be stored locally on a particular user's device.
- Amy 102 is using the first desktop computer 404 , where her personal unified addressing inbox/outbox 202 resides.
- Bill 104 is using the second desktop computer 406 , on which his personal unified addressing inbox/outbox 204 resides.
- Amy's unified addressing inbox/outbox 202 retrieves the comment in accordance with the particular communication modality that she has specified in her unified addressing configuration specification 300 , e.g., via e-mail 112 .
- FIG. 5 is a flowchart that illustrates an example of a machine-controlled method 500 of sending a contribution to a collaboration team.
- a user contributes to a collaboration by posting content to be sent to the rest of his or her team using his or her unified addressing inbox/outbox, as shown at 502 .
- the user may decide to send content such as a certain technical specification that he or she has recently updated, for example.
- the user's unified addressing inbox/outbox may then determine a particular communication modality for the team member, as shown at 504 .
- the user's unified addressing inbox/outbox may consult a unified addressing configuration specification 300 that is either stored locally on the user's device or resides at a remote location. Once the user's unified addressing inbox/outbox has determined what type of communication modality to use for the team member, the unified addressing inbox/outbox may then send the content out to a central portion of the collaboration system using the user's particular communication modality, as shown at 506 .
- the unified addressing collaboration system may facilitate the transmission of the posted content, i.e., the technical specification, to another team member in accordance with his or her preferred communication modality, as shown at 508 . If the other team member has expressed e-mail, for example, and the system is able to obtain an e-mail address for the other team member, the unified addressing collaboration system may then send the technical specification to the other team member's e-mail address.
- the system may repeat this process for each team member. For example, after sending the content to the other team member at 508 , the system may determine whether there are any other members of the collaboration team, as shown at 510 . If so, the process returns to 508 . Otherwise, the system halts the transmission process for the particular contribution, as shown at 512 . Because the system may thus deliver copies of a single contribution to multiple users that may each use different communication modalities, the user's unified addressing inbox/outbox may be referred to in certain embodiments as a universal outbox.
- FIG. 6 is a flowchart that illustrates an example of a machine-controlled method 600 of receiving a contribution from a collaboration team member.
- a collaboration team member sends a contribution to the team by posting a new comment to a blog entry, for example.
- a user's unified addressing inbox/outbox becomes aware of the posting user's contribution, as shown at 604 .
- the posting team member's unified addressing inbox/outbox or the collaboration system itself may send a notification message to the other team members' unified addressing inbox/outboxes in connection with or in addition to the posted comment.
- each user's unified addressing inbox/outbox may monitor identified information sources within the collaboration system continuously or at certain scheduled times or intervals.
- the user's unified addressing inbox/outbox may retrieve the contribution from the posted location, as shown at 606 .
- the user's unified addressing inbox/outbox may proactively retrieve the contribution.
- the user's unified addressing inbox/outbox may passively receive the contribution directly from the sender's universal outbox or from a component within the collaboration system.
- the user's unified addressing inbox/outbox may also determine the user's preferred communication modality for the corresponding collaboration team, as shown at 608 .
- the user's unified addressing inbox/outbox may consult a unified addressing configuration specification for the user.
- the user's unified addressing inbox/outbox may use a default communication modality.
- the user's unified addressing inbox/outbox may now send the information to the user in accordance with the user's preferred communication modality, as shown at 610 .
- the user may indicate a preference for text messaging in connection with the pertinent collaboration team, his or her unified addressing inbox/outbox may send the new information to him or her as a text message.
- the user's unified addressing inbox/outbox thus sends the information to him or her regardless of whatever communication modality the posting user used to post the new information at 602 .
- Jim a member of a small technical documentation team consisting of five people, creates a first draft of a user's guide. Jim would like to share his progress with and solicit feedback and comments from the other team members using a current collaboration system. Accordingly, Jim edits the document using a particular word processor and then saves the file to his local hard drive. Jim then uses a particular e-mail program to send an e-mail messages to all of his team members with the document as an attachment.
- Jim may ask his team members to review the document and reply with comments and suggested improvements. Unless all of the other team members have both a compatible e-mail system and word processor, however, they may not receive the document and, even if they do, they may not be able to contribute to the collaboration effort by marking up the document with their feedback, for example.
- Jim writes his document using an implementation of the disclosed technology.
- Jim uses a rich editor, e.g., a smart editor that has been integrated with unified addressing capability.
- Jim may select “To:” from the application menu bar and enter “myteam.”
- the system may then send the document out to the rest of the team using a unified addressing mechanism. That is, the system may send the document to each team member included in Jim's “myteam” unified address in accordance with whatever communication modality he or she has specified.
- Jim may not know and, more importantly, does not need to know whether each team member has specified e-mail as the preferred receiving modality.
- each user may have selected, unbeknownst to Jim, an entirely different communication modality for receiving the information from Jim.
- the system is able to recognize which modality to use for each user based on the unified addressing mechanism.
- Sue is a researcher in a team of people that is currently working on gene splicing. Sue regularly posts to her blog about her experiments and their results. Sue keeps most of her research in a database but uses a browser-based blog editor to post her blog entries. She constantly monitors her blog to see if other team members write any comments in connection any of her posts.
- Sue seeks more than mere acknowledgment of her work, though—she is also seeking feedback from and interaction with the other team members in connection with the information that she posts.
- the other team members e.g., interact with the information posted on her blog, they would each need to not only access Sue's blog but also have access to and actively use a tool that would enable them to post information such as comments to Sue's blog.
- Sue writes her blog entry using an implementation of the disclosed technology.
- Sue types a document using a rich editor, e.g., a smart editor that has been integrated with unified addressing capability. Sue may then select “To:” from the application menu bar and enter “myteam.” The system may then post the document on the blog server and also send it to the other team members using whatever communication modality each team member has specified.
- the system may send the comment(s) and/or additional information to Sue using whatever receiving modality Sue has specified. For example, Sue may desire to have the system send any comments to her document sent straight to her mobile device so that she no longer needs to actively monitor her blog directly for any such comments.
- each of the other team members must update their address books or else any communications to and/or from that particular team member may get lost. For example, until the other users are apprised of the new phone number, any text messages they send to the old phone number may not get transferred to the new phone number and, even if they do, the extra time needed for forwarding could be detrimental.
- Sharon may write her status or new information as a microblog entry using a rich editor in a mobile device application, e.g., a smart editor that has been integrated with unified addressing capability.
- Sharon may select “To:” from the application menu bar and enter “myteam.” The system may then send Sharon's information as a text message to all of her team members without requiring her to maintain a list of her own contacts or groups with constant updates to those lists.
- Sharon may not know and does not even need to know whether her information is being sent to the other team members as text messages, let alone what phone numbers the system is using. Also, some team members may have specified that the system is to send Sharon's information to them not as text messages but as entries on a personal chat client, for example. As users post replies to Sharon's messages, the system may send the replies to Sharon as text messages based on Sharon's selection of a preferred communication modality. They system may also enable Sharon to respond to the replies via a text message-type application on her mobile device.
- machine is intended to broadly encompass a single machine or a system of communicatively coupled machines or devices operating together.
- Exemplary machines can include computing devices such as personal computers, workstations, servers, portable computers, handheld devices, tablet devices, and the like.
- a machine typically includes a system bus to which processors, memory (e.g., random access memory (RAM), read-only memory (ROM), and other state-preserving medium), storage devices, a video interface, and input/output interface ports can be attached.
- the machine can also include embedded controllers such as programmable or non-programmable logic devices or arrays, Application Specific Integrated Circuits, embedded computers, smart cards, and the like.
- the machine can be controlled, at least in part, by input from conventional input devices (e.g., keyboards and mice), as well as by directives received from another machine, interaction with a virtual reality (VR) environment, biometric feedback, or other input signal.
- VR virtual reality
- the machine can utilize one or more connections to one or more remote machines, such as through a network interface, modem, or other communicative coupling.
- Machines can be interconnected by way of a physical and/or logical network, such as an intranet, the Internet, local area networks, wide area networks, etc.
- network communication can utilize various wired and/or wireless short range or long range carriers and protocols, including radio frequency (RF), satellite, microwave, Institute of Electrical and Electronics Engineers (IEEE) 545.11, Bluetooth, optical, infrared, cable, laser, etc.
- RF radio frequency
- IEEE Institute of Electrical and Electronics Engineers
- Embodiments of the disclosed technology can be described by reference to or in conjunction with associated data including functions, procedures, data structures, application programs, instructions, etc. that, when accessed by a machine, can result in the machine performing tasks or defining abstract data types or low-level hardware contexts.
- Associated data can be stored in, for example, volatile and/or non-volatile memory (e.g., RAM and ROM) or in other storage devices and their associated storage media, which can include hard-drives, floppy-disks, optical storage, tapes, flash memory, memory sticks, digital video disks, biological storage, and other tangible, physical storage media.
- Associated data can be delivered over transmission environments, including the physical and/or logical network, in the form of packets, serial data, parallel data, propagated signals, etc., and can be used in a compressed or encrypted format. Associated data can be used in a distributed environment, and stored locally and/or remotely for machine access.
Abstract
Description
- This application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/224,778, titled “COLLABORATION TOOLS” and filed on Jul. 10, 2009, and U.S. Provisional Patent Application Ser. No. 61/236,005, titled “PRESENCE-ENABLED INBOX” and filed on Aug. 21, 2009, both of which are hereby fully incorporated by reference herein.
- This application is related to U.S. patent application Ser. No. ______, titled “COLLABORATION SWARMING” and filed on October —, 2009, U.S. patent application Ser. No. ______ titled “INTELLIGENT CO-BROWSING AND CO-EDITING” and filed on October —, 2009, U.S. patent application Ser. No. ______ titled “AUTO GENERATED AND INFERRED GROUP CHAT PRESENCE” and filed on October —, 2009, U.S. patent application Ser. No. ______ titled “UNIFIED EDITABLE INBOX” and filed on October —, 2009, and U.S. patent application Ser. No. ______ titled “PRESENCE-ENABLED INBOX” and filed on October —, 2009, all of which are commonly assigned with this application and are hereby fully incorporated by reference herein.
- The disclosed technology pertains to multi-user collaboration environments, and more particularly to facilitating the transmission of content between collaboration users.
- Current collaboration systems require that teams of various sizes and in varying degrees of formation or cohesiveness work together to generate, process, review, revise, and coordinate information from a number of different sources. Collaboration teams must choose a single communication modality, such as e-mail groups or shared addresses, blogs with comments, text messaging, voicemail, micro blogs, shared folders in a shared file system, or shared logins, for example. While this may be sufficient for a given small team that requires each team member use a certain tool, such an arrangement does not work well when used in situations where there are multiple teams that overlap and may be using different tools or communication modalities.
- Among the various deficiencies with current systems is the problem that, because each team in a given collaboration must decide on a single common communication modality, each member of the team must have access to that same technology with software or hardware that supports the selected communication modality. For example, if a user Alex wants to collaborate with a team that has selected Twitter as the common communication modality, Alex must first obtain a personal Twitter account. Consider another example where a user Rachel wants to collaborate with a team that has selected HTML-based e-mail as the common communication modality. In order to participate in the collaboration, Rachel must first secure a client that is capable of both sending and receiving HTML-based e-mails. If Alex does not wish to obtain a Twitter account and Rachel does not wish to install an HTML-based e-mail client, then both users will be effectively shut out of their respective collaboration teams.
- Thus, there remains a need for improved tools and mechanisms for team-based collaborations.
- Embodiments of the disclosed technology include a unified address or common addressing arrangement that allows for the sharing, posting, and notification of collaboration content independent of any particular communication mechanism being selected as a common communication modality for the collaboration team. Collaboration team members are thus no longer interrupted and burdened with needing to know, let alone specify, which communication mechanism should be applied every time he or she wishes to communicate with other collaboration team members.
- Embodiments of the disclosed technology may allow for the mapping of a unified “send” action on the unified address to be mapped to a specific communication modality such as sending an e-mail message, posting a blog entry, or sending an SMS message, for example. Thus, each collaboration team member may use a unified address technique for posting, sending, publishing, sharing, commenting, responding, editing, or performing some other type of information interaction event in connection with another team member regardless of whatever communication modality is actually being used.
- By allowing for a custom mapping from a common unified address to specific communication modalities for each member of a collaboration team, embodiments of the disclosed technology essentially move collaborations from a “First Personalized Mechanism then Share” paradigm to a “First Share then Personalized Mechanism” paradigm. Unlike current systems, implementations of the disclosed technology do not require that each member of a given collaboration team have the same technology installed or available as all of the other members of the team.
- The foregoing and other features, objects, and advantages of the invention will become more readily apparent from the following detailed description, which proceeds with reference to the accompanying drawings.
-
FIG. 1 is a block diagram that illustrates an example of a collaboration system using current collaboration tools. -
FIG. 2 is a block diagram that illustrates an example of a unified addressing collaboration system in accordance with embodiments of the disclosed technology. -
FIG. 3 is a block diagram that illustrates an example of a unified addressing configuration specification in accordance with embodiments of the disclosed technology. -
FIG. 4 illustrates an example of a system in which embodiments of the disclosed technology may be implemented. -
FIG. 5 is a flowchart that illustrates an example of a machine-controlled method of sending a contribution to a collaboration team in accordance with embodiments of the disclosed technology. -
FIG. 6 is a flowchart that illustrates an example of a machine-controlled method of receiving a contribution from a collaboration team member in accordance with embodiments of the disclosed technology. - Embodiments of the disclosed technology may include a common or unified addressing mechanism that may be used in connection with any of a number of different communication modalities. For example, a common addressing and sending/receiving mechanism may be mapped to one of several communication modalities that may be used by a particular collaboration team member. A team member that desires to share certain information with other team members is thus not burdened with needing to know, let alone select, the particular information sharing mechanism selected by the team or by each individual recipient; rather, each member of the team may select his or her own communication preference without needing to inform the sender of the selected modality.
- A unified address and sending/receiving mechanism in accordance with the disclosed technology may be accessed from technology-specific communication tools such as e-mail messages, twitter posts, or blog entries. The unified address and sending/receiving mechanism may be incorporated directly into applications or accessed indirectly through special addresses or tags such as embedded comments or embedded fields. For example, a team member may tweet, i.e., enter a twitter post that may have a special hash tag to enable the backend server to recognize and send the tweet through a unified communications server to other team members that may be using other communication modalities. Alternatively, the team member may send an e-mail message with special comments in the subject line or post blog entries with embedded tags.
- Particular addresses may be preconfigured to have associated therewith certain carbon copies. A backend communications server may recognize the carbon copies and then translate between the sending communication modality and other receiving modalities that are unique to other members of the team. For example, if another team member specifies text messaging as his or her preferred communication modality, the system may send collaboration contributions to that user via text messages, regardless of whatever communication modality was used to send the information by the posting user.
-
FIG. 1 is a block diagram that illustrates an example of acollaboration system 100 using current collaboration tools. In the example, a collaboration team consists of four team members—Amy 102, Bill 104, Charlie 106, and David 108—that communicate with each other using four different types of communication modalities: Internet 110, e.g., blog postings,e-mail 112,file sharing 114, and voice/text messaging 116. While user Amy 102 has made all four communication modalities 110-116 available to herself, the other users have only selected, e.g., installed and/or activated, one or two different modalities for communication in the collaboration. - If user Amy 102 wishes to communicate with user Charlie 106, for example, Amy 102 must have available, installed, and ready to use clients for the same technology that Charlie 106 has selected as his preferred communication modality, i.e.,
file sharing 114. Similarly, if Amy 102 wishes to communicate with user David 108, Amy 102 must have accessible to her the same communication modality, i.e., voice/text 116, that David 108 has selected. - While Amy may have all of the communication modalities 110-116 available to her and may thus communicate with each of the other team members 104-108, not all of the other team members 104-108 have all of the communication modalities 110-116 installed and available to them. Thus, communication between all of the team members 102-108 is simply not achievable using the illustrated
system 100. - For example, while
user Bill 104 has selected two different communication modalities, i.e., Internet 110 and e-mail 112, neither Charlie 106 nor David 108 has selected either of the Internet 110 ande-mail 112 modalities. Charlie 106 and David 108 may not be configured to connect to the Internet 110, may not have appropriate accounts created, or may not even have access to a computer, for example. Thus, there is currently no communication available betweenBill 104 and either Charlie 106 or David 108 using the illustratedsystem 100. That is, neither Charlie 106 nor David 108 will receive any contribution thatBill 104 sends to the collaboration team. - In contrast,
FIG. 2 is a block diagram that illustrates an example of a unified addressingcollaboration system 200. In the example, each of the users Amy 102, Bill 104, Charlie 106, and David 108 have a unified addressing inbox/outbox 202-208, respectively. Each unified addressing inbox/outbox 202-208 is configured to select a particular communication modality for the corresponding user based on a preference indicated by the corresponding user, for example. Each unified addressing inbox/outbox 202-208 is also configured to provide an identification of the selected communication modality to the other unified addressing inbox/outboxes 202-208 to facilitate the passing of information between the users 102-108. - Consider a first example in which Charlie 106 drafts a technical specification for a particular aspect of a new software application. Charlie 106 then sends the technical specification to the rest of his team using his unified addressing inbox/
outbox 206. Here, Charlie's unified addressing inbox/outbox 206 is essentially acting as a universal outbox. For example, Charlie's unified addressing inbox/outbox 206 may communicate with David's unified addressing inbox/outbox 208, for example, to determine David's preferred communication modality, i.e., voice/text 116. Charlie's unified addressing inbox/outbox 206 may thus send the technical specification as a text message to David's unified addressing inbox/outbox 208. - Charlie's unified addressing inbox/
outbox 206 may also communicate with Amy's and Bill's unified addressing inbox/outboxes Amy 102 andBill 104 in accordance with the communication modality for each corresponding user. -
FIG. 3 is a block diagram that illustrates an example of a unified addressingconfiguration specification 300 that includes a listing of communication modality preferences for a particular user. In other words, the user can essentially establish particular carbon copies for certain collaboration contributions and specify the circumstances under which they are to occur. For example, each collaboration team member can configure his or her account so that, whenever another team member posts a pertinent contribution, the system will be able to determine how to distribute the contribution to the other collaboration team members. That is, the user can essentially configure rules that specify how he or she wants his or her content shared to other group members as the content is posted. - In the example, the user has expressed a preference for sending and receiving information in connection with two different collaboration groups: “
Tech 1” and “Tech 2.” Regarding the first collaboration, i.e., “Tech 1,” the user has expressed a preference for all of his or her contributions to be sent via a particular e-mail messaging service using a specified email address. The user has also expressed a preference for receivable content to be delivered via a text messaging service to the phone number provided in the unified addressingconfiguration specification 300. - Regarding the second collaboration, i.e., “
Tech 2,” the user has expressed a preference for sending information via postings to a specified blog. The user has not, however, indicated in the unified addressing configuration specification 300 a particular communication modality for receiving content in connection with the “Tech 2” collaboration. Embodiments using the illustrated unified addressingconfiguration specification 300 may assign a default communication modality for receiving content pertaining to the “Tech 2” collaboration, for example. - One having ordinary skill in the art will recognize that implementations involving a unified addressing
configuration specification 300 are not merely passing information along; rather, such systems are essentially creating a construct for each collaboration team member's involvement with his or her particular collaboration groups. - A user may use his or her personal unified addressing
configuration specification 300 to also provide information that may be pertinent to the selected communication modalities. For example, a user may provide his or her current phone number and/or e-mail address. Additionally, the user may wish to use different phone numbers and/or different e-mail addresses for different collaborations. Thus, if a user were to be assigned a new phone number, he or she would only need to update his or her unified addressingconfiguration specification 300—there would be no need to proactively alert the other team members to the updated information because the other users' unified addressing inbox/outboxes would automatically retrieve the information as part of the information transmission process. -
FIG. 4 illustrates an example of asystem 400 in which embodiments of the disclosed technology may be implemented. Thesystem 400 includes anetwork 402, such as the Internet or a company's intranet, that may facilitate interaction between multiple devices such asdesktop computers laptop computers 406. Other devices such as a personal digital assistant (PDA) 410 andmobile devices system 400. Aremote database 416 may be used to store information pertaining to users' unified addressing inbox/outboxes such as each user's unified addressingconfiguration specification 300. Alternatively, such information may be stored locally on a particular user's device. - In the example,
Amy 102 is using thefirst desktop computer 404, where her personal unified addressing inbox/outbox 202 resides.Bill 104 is using thesecond desktop computer 406, on which his personal unified addressing inbox/outbox 204 resides. Consider an example in whichBill 104 decides to comment on a particular blog posting thatAmy 102 has authored on theInternet 110. OnceBill 104 has sent his comment via his unified addressing inbox/outbox 204, Amy's unified addressing inbox/outbox 202 retrieves the comment in accordance with the particular communication modality that she has specified in her unified addressingconfiguration specification 300, e.g., viae-mail 112. -
FIG. 5 is a flowchart that illustrates an example of a machine-controlledmethod 500 of sending a contribution to a collaboration team. In the example, a user contributes to a collaboration by posting content to be sent to the rest of his or her team using his or her unified addressing inbox/outbox, as shown at 502. The user may decide to send content such as a certain technical specification that he or she has recently updated, for example. - The user's unified addressing inbox/outbox may then determine a particular communication modality for the team member, as shown at 504. For example, the user's unified addressing inbox/outbox may consult a unified addressing
configuration specification 300 that is either stored locally on the user's device or resides at a remote location. Once the user's unified addressing inbox/outbox has determined what type of communication modality to use for the team member, the unified addressing inbox/outbox may then send the content out to a central portion of the collaboration system using the user's particular communication modality, as shown at 506. - At this point, the unified addressing collaboration system may facilitate the transmission of the posted content, i.e., the technical specification, to another team member in accordance with his or her preferred communication modality, as shown at 508. If the other team member has expressed e-mail, for example, and the system is able to obtain an e-mail address for the other team member, the unified addressing collaboration system may then send the technical specification to the other team member's e-mail address.
- The system may repeat this process for each team member. For example, after sending the content to the other team member at 508, the system may determine whether there are any other members of the collaboration team, as shown at 510. If so, the process returns to 508. Otherwise, the system halts the transmission process for the particular contribution, as shown at 512. Because the system may thus deliver copies of a single contribution to multiple users that may each use different communication modalities, the user's unified addressing inbox/outbox may be referred to in certain embodiments as a universal outbox.
-
FIG. 6 is a flowchart that illustrates an example of a machine-controlledmethod 600 of receiving a contribution from a collaboration team member. At 602, a collaboration team member sends a contribution to the team by posting a new comment to a blog entry, for example. - A user's unified addressing inbox/outbox becomes aware of the posting user's contribution, as shown at 604. For example, the posting team member's unified addressing inbox/outbox or the collaboration system itself may send a notification message to the other team members' unified addressing inbox/outboxes in connection with or in addition to the posted comment. Alternatively, each user's unified addressing inbox/outbox may monitor identified information sources within the collaboration system continuously or at certain scheduled times or intervals.
- As soon as the user's unified addressing inbox/outbox becomes aware of the newly posted contribution, the user's unified addressing inbox/outbox may retrieve the contribution from the posted location, as shown at 606. In certain embodiments, the user's unified addressing inbox/outbox may proactively retrieve the contribution. Alternatively, the user's unified addressing inbox/outbox may passively receive the contribution directly from the sender's universal outbox or from a component within the collaboration system.
- The user's unified addressing inbox/outbox may also determine the user's preferred communication modality for the corresponding collaboration team, as shown at 608. For example, the user's unified addressing inbox/outbox may consult a unified addressing configuration specification for the user. Alternatively, the user's unified addressing inbox/outbox may use a default communication modality.
- Once the user's unified addressing inbox/outbox has retrieved the new contribution at 606 and identified the user's preferred communication modality at 608, the user's unified addressing inbox/outbox may now send the information to the user in accordance with the user's preferred communication modality, as shown at 610. For example, if the user has indicated a preference for text messaging in connection with the pertinent collaboration team, his or her unified addressing inbox/outbox may send the new information to him or her as a text message. The user's unified addressing inbox/outbox thus sends the information to him or her regardless of whatever communication modality the posting user used to post the new information at 602.
- Described below are several different user scenarios that serve to illustrate a variety of implementations in accordance with the disclosed technology. One having ordinary skill in the art will recognize that these examples are provided for purposes of demonstrating various different configurations of the disclosed technology and should not be construed as limiting the scope of the invention.
- Consider a first example in which Jim, a member of a small technical documentation team consisting of five people, creates a first draft of a user's guide. Jim would like to share his progress with and solicit feedback and comments from the other team members using a current collaboration system. Accordingly, Jim edits the document using a particular word processor and then saves the file to his local hard drive. Jim then uses a particular e-mail program to send an e-mail messages to all of his team members with the document as an attachment.
- In the e-mail message, Jim may ask his team members to review the document and reply with comments and suggested improvements. Unless all of the other team members have both a compatible e-mail system and word processor, however, they may not receive the document and, even if they do, they may not be able to contribute to the collaboration effort by marking up the document with their feedback, for example.
- In contrast, consider an alternate version of the first example in which Jim writes his document using an implementation of the disclosed technology. For example, rather than using a stand-alone word processor and e-mail client, Jim uses a rich editor, e.g., a smart editor that has been integrated with unified addressing capability. Once Jim has finished revising the document, he may select “To:” from the application menu bar and enter “myteam.” The system may then send the document out to the rest of the team using a unified addressing mechanism. That is, the system may send the document to each team member included in Jim's “myteam” unified address in accordance with whatever communication modality he or she has specified.
- In the example, Jim may not know and, more importantly, does not need to know whether each team member has specified e-mail as the preferred receiving modality. In fact, each user may have selected, unbeknownst to Jim, an entirely different communication modality for receiving the information from Jim. The system is able to recognize which modality to use for each user based on the unified addressing mechanism.
- Consider a second example in which Sue is a researcher in a team of people that is currently working on gene splicing. Sue regularly posts to her blog about her experiments and their results. Sue keeps most of her research in a database but uses a browser-based blog editor to post her blog entries. She constantly monitors her blog to see if other team members write any comments in connection any of her posts.
- Sue seeks more than mere acknowledgment of her work, though—she is also seeking feedback from and interaction with the other team members in connection with the information that she posts. However, in order for the other team members to collaborate with Sue, e.g., interact with the information posted on her blog, they would each need to not only access Sue's blog but also have access to and actively use a tool that would enable them to post information such as comments to Sue's blog.
- In contrast, consider an alternate version of the second example in which Sue writes her blog entry using an implementation of the disclosed technology. For example, rather than using a browser-based interface to a blog server, Sue types a document using a rich editor, e.g., a smart editor that has been integrated with unified addressing capability. Sue may then select “To:” from the application menu bar and enter “myteam.” The system may then post the document on the blog server and also send it to the other team members using whatever communication modality each team member has specified.
- Once a team member decides to comment on the document or post other pertinent information, the system may send the comment(s) and/or additional information to Sue using whatever receiving modality Sue has specified. For example, Sue may desire to have the system send any comments to her document sent straight to her mobile device so that she no longer needs to actively monitor her blog directly for any such comments.
- Consider a third example in which Sharon is a staff reporter who is working with two new partners on a breaking story. It is crucial that each member of this small collaboration team share his or her notes and newly-gathered information as quickly as possible with the rest of the team. The team members all use mobile devices with text messaging and they e-mail each other regularly. They also have a shared calendar so that they can see who is where and what each person is doing.
- If one of the team members in the example gets a new phone number, however, each of the other team members must update their address books or else any communications to and/or from that particular team member may get lost. For example, until the other users are apprised of the new phone number, any text messages they send to the old phone number may not get transferred to the new phone number and, even if they do, the extra time needed for forwarding could be detrimental.
- In contrast, consider an alternate version of the third example in which Sharon contributes to the collaboration using an implementation of the disclosed technology. For example, Sharon may write her status or new information as a microblog entry using a rich editor in a mobile device application, e.g., a smart editor that has been integrated with unified addressing capability. Sharon may select “To:” from the application menu bar and enter “myteam.” The system may then send Sharon's information as a text message to all of her team members without requiring her to maintain a list of her own contacts or groups with constant updates to those lists.
- In the example, Sharon may not know and does not even need to know whether her information is being sent to the other team members as text messages, let alone what phone numbers the system is using. Also, some team members may have specified that the system is to send Sharon's information to them not as text messages but as entries on a personal chat client, for example. As users post replies to Sharon's messages, the system may send the replies to Sharon as text messages based on Sharon's selection of a preferred communication modality. They system may also enable Sharon to respond to the replies via a text message-type application on her mobile device.
- General Description of a Suitable Machine in which Embodiments of the Disclosed Technology can be Implemented
- The following discussion is intended to provide a brief, general description of a suitable machine in which embodiments of the disclosed technology can be implemented. As used herein, the term “machine” is intended to broadly encompass a single machine or a system of communicatively coupled machines or devices operating together. Exemplary machines can include computing devices such as personal computers, workstations, servers, portable computers, handheld devices, tablet devices, and the like.
- Typically, a machine includes a system bus to which processors, memory (e.g., random access memory (RAM), read-only memory (ROM), and other state-preserving medium), storage devices, a video interface, and input/output interface ports can be attached. The machine can also include embedded controllers such as programmable or non-programmable logic devices or arrays, Application Specific Integrated Circuits, embedded computers, smart cards, and the like. The machine can be controlled, at least in part, by input from conventional input devices (e.g., keyboards and mice), as well as by directives received from another machine, interaction with a virtual reality (VR) environment, biometric feedback, or other input signal.
- The machine can utilize one or more connections to one or more remote machines, such as through a network interface, modem, or other communicative coupling. Machines can be interconnected by way of a physical and/or logical network, such as an intranet, the Internet, local area networks, wide area networks, etc. One having ordinary skill in the art will appreciate that network communication can utilize various wired and/or wireless short range or long range carriers and protocols, including radio frequency (RF), satellite, microwave, Institute of Electrical and Electronics Engineers (IEEE) 545.11, Bluetooth, optical, infrared, cable, laser, etc.
- Embodiments of the disclosed technology can be described by reference to or in conjunction with associated data including functions, procedures, data structures, application programs, instructions, etc. that, when accessed by a machine, can result in the machine performing tasks or defining abstract data types or low-level hardware contexts. Associated data can be stored in, for example, volatile and/or non-volatile memory (e.g., RAM and ROM) or in other storage devices and their associated storage media, which can include hard-drives, floppy-disks, optical storage, tapes, flash memory, memory sticks, digital video disks, biological storage, and other tangible, physical storage media.
- Associated data can be delivered over transmission environments, including the physical and/or logical network, in the form of packets, serial data, parallel data, propagated signals, etc., and can be used in a compressed or encrypted format. Associated data can be used in a distributed environment, and stored locally and/or remotely for machine access.
- Having described and illustrated the principles of the invention with reference to illustrated embodiments, it will be recognized that the illustrated embodiments may be modified in arrangement and detail without departing from such principles, and may be combined in any desired manner. And although the foregoing discussion has focused on particular embodiments, other configurations are contemplated. In particular, even though expressions such as “according to an embodiment of the invention” or the like are used herein, these phrases are meant to generally reference embodiment possibilities, and are not intended to limit the invention to particular embodiment configurations. As used herein, these terms may reference the same or different embodiments that are combinable into other embodiments.
- Consequently, in view of the wide variety of permutations to the embodiments described herein, this detailed description and accompanying material is intended to be illustrative only, and should not be taken as limiting the scope of the invention. What is claimed as the invention, therefore, is all such modifications as may come within the scope and spirit of the following claims and equivalents thereto.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/690,038 US20110010424A1 (en) | 2009-07-10 | 2010-01-19 | Unified addressing, sending, and receiving collaboration service |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US22477809P | 2009-07-10 | 2009-07-10 | |
US23600509P | 2009-08-21 | 2009-08-21 | |
US12/690,038 US20110010424A1 (en) | 2009-07-10 | 2010-01-19 | Unified addressing, sending, and receiving collaboration service |
Publications (1)
Publication Number | Publication Date |
---|---|
US20110010424A1 true US20110010424A1 (en) | 2011-01-13 |
Family
ID=43428259
Family Applications (7)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/690,056 Abandoned US20110010635A1 (en) | 2009-07-10 | 2010-01-19 | Unified editable inbox |
US12/690,038 Abandoned US20110010424A1 (en) | 2009-07-10 | 2010-01-19 | Unified addressing, sending, and receiving collaboration service |
US12/690,075 Abandoned US20110010638A1 (en) | 2009-07-10 | 2010-01-19 | Presence-enabled inbox |
US12/690,028 Expired - Fee Related US8898282B2 (en) | 2009-07-10 | 2010-01-19 | Auto generated and inferred group chat presence |
US12/690,066 Expired - Fee Related US8280846B2 (en) | 2009-07-10 | 2010-01-19 | Collaboration swarming |
US12/690,071 Abandoned US20110010640A1 (en) | 2009-07-10 | 2010-01-19 | Intelligent co-browsing and co-editing |
US13/619,543 Active 2030-03-07 US9595022B2 (en) | 2009-07-10 | 2012-09-14 | Collaboration swarming |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/690,056 Abandoned US20110010635A1 (en) | 2009-07-10 | 2010-01-19 | Unified editable inbox |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/690,075 Abandoned US20110010638A1 (en) | 2009-07-10 | 2010-01-19 | Presence-enabled inbox |
US12/690,028 Expired - Fee Related US8898282B2 (en) | 2009-07-10 | 2010-01-19 | Auto generated and inferred group chat presence |
US12/690,066 Expired - Fee Related US8280846B2 (en) | 2009-07-10 | 2010-01-19 | Collaboration swarming |
US12/690,071 Abandoned US20110010640A1 (en) | 2009-07-10 | 2010-01-19 | Intelligent co-browsing and co-editing |
US13/619,543 Active 2030-03-07 US9595022B2 (en) | 2009-07-10 | 2012-09-14 | Collaboration swarming |
Country Status (1)
Country | Link |
---|---|
US (7) | US20110010635A1 (en) |
Cited By (13)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130024419A1 (en) * | 2009-07-10 | 2013-01-24 | Andrew Fox | Collaboration swarming |
US9367490B2 (en) | 2014-06-13 | 2016-06-14 | Microsoft Technology Licensing, Llc | Reversible connector for accessory devices |
US9384334B2 (en) | 2014-05-12 | 2016-07-05 | Microsoft Technology Licensing, Llc | Content discovery in managed wireless distribution networks |
US9384335B2 (en) | 2014-05-12 | 2016-07-05 | Microsoft Technology Licensing, Llc | Content delivery prioritization in managed wireless distribution networks |
US9430667B2 (en) | 2014-05-12 | 2016-08-30 | Microsoft Technology Licensing, Llc | Managed wireless distribution network |
US20160350398A1 (en) * | 2010-12-17 | 2016-12-01 | Microsoft Technology Licensing, Llc | Hash tag management in a microblogging infrastructure |
US9614724B2 (en) | 2014-04-21 | 2017-04-04 | Microsoft Technology Licensing, Llc | Session-based device configuration |
US9717006B2 (en) | 2014-06-23 | 2017-07-25 | Microsoft Technology Licensing, Llc | Device quarantine in a wireless network |
US9874914B2 (en) | 2014-05-19 | 2018-01-23 | Microsoft Technology Licensing, Llc | Power management contracts for accessory devices |
US10111099B2 (en) | 2014-05-12 | 2018-10-23 | Microsoft Technology Licensing, Llc | Distributing content in managed wireless distribution networks |
US10691445B2 (en) | 2014-06-03 | 2020-06-23 | Microsoft Technology Licensing, Llc | Isolating a portion of an online computing service for testing |
US20230077024A1 (en) * | 2011-12-29 | 2023-03-09 | Intel Corporation | Management of collaborative teams |
US20230247137A1 (en) * | 2022-01-31 | 2023-08-03 | Zoom Video Communications, Inc. | Collaborative Virtual Waiting Room |
Families Citing this family (40)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8700776B2 (en) * | 2009-03-23 | 2014-04-15 | Google Inc. | System and method for editing a conversation in a hosted conversation system |
US8527602B1 (en) | 2009-05-28 | 2013-09-03 | Google Inc. | Content upload system with preview and user demand based upload prioritization |
US9602444B2 (en) | 2009-05-28 | 2017-03-21 | Google Inc. | Participant suggestion system |
US9021386B1 (en) | 2009-05-28 | 2015-04-28 | Google Inc. | Enhanced user interface scrolling system |
US20110119337A1 (en) * | 2009-11-19 | 2011-05-19 | At&T Intellectual Property I, L.P. | System and Method for Electronic Messaging and Voicemail Management |
US8166121B2 (en) * | 2009-12-31 | 2012-04-24 | International Business Machines Corporation | Situation based presence notification leveraging |
US8510399B1 (en) | 2010-05-18 | 2013-08-13 | Google Inc. | Automated participants for hosted conversations |
US9380011B2 (en) | 2010-05-28 | 2016-06-28 | Google Inc. | Participant-specific markup |
US9026935B1 (en) | 2010-05-28 | 2015-05-05 | Google Inc. | Application user interface with an interactive overlay |
US20120047449A1 (en) * | 2010-08-17 | 2012-02-23 | International Business Machines Corporation | Integrating a user browsing feed into a co-browsing session |
US20120110064A1 (en) | 2010-11-01 | 2012-05-03 | Google Inc. | Content sharing interface for sharing content in social networks |
US8880603B2 (en) | 2011-06-07 | 2014-11-04 | Interdigital Patent Holdings, Inc. | Peer to peer (P2P) operation by integrating with content delivery networks (CDN) |
CN103064829A (en) * | 2011-10-19 | 2013-04-24 | 王国臣 | Copy and paste method based on internet and copy and paste system |
US10482638B2 (en) | 2011-11-11 | 2019-11-19 | Microsoft Technology Licensing, Llc | Collaborative commenting in a drawing tool |
US9021031B1 (en) | 2011-12-08 | 2015-04-28 | Google Inc. | Providing for selective availability on a messaging service |
US9628296B2 (en) * | 2011-12-28 | 2017-04-18 | Evernote Corporation | Fast mobile mail with context indicators |
US9497152B2 (en) | 2012-01-19 | 2016-11-15 | Microsoft Technology Licensing, Llc | Managing team mailbox integrating email repository and content management store services |
GB2505022B (en) * | 2012-08-16 | 2015-01-14 | Jaguar Land Rover Ltd | Speed control system and method for operating the same |
US20140095603A1 (en) * | 2012-09-29 | 2014-04-03 | Deepti Bhardwaj | One stop for multiple perspectives on somebody's personality from qualified associations |
US20140101571A1 (en) * | 2012-10-04 | 2014-04-10 | Lucid Dream Software, Inc. | Shared collaborative environment |
US9313282B2 (en) | 2013-02-18 | 2016-04-12 | International Business Machines Corporation | Intelligently detecting the leader of a co-browsing session |
US9674260B2 (en) * | 2013-07-09 | 2017-06-06 | John Henry Page | System and method for exchanging and displaying resource viewing position and related information |
US9407596B2 (en) * | 2013-11-20 | 2016-08-02 | International Business Machines Corporation | Interactive splitting of entries in social collaboration environments |
CN105874486B (en) * | 2013-11-28 | 2020-10-27 | 帕特里克·弗尔韦特 | Platform device for providing qualitative cluster knowledge |
US9576261B2 (en) | 2014-04-17 | 2017-02-21 | Microsoft Technology Licensing, Llc | Quick drafts of items in a primary work queue |
EP3193764B1 (en) * | 2014-08-28 | 2021-05-05 | Waldemar Link GmbH & Co. KG | Handheld surgical tool with autonomous navigation |
WO2016049186A1 (en) * | 2014-09-25 | 2016-03-31 | Osix Corporation | Computer-implemented methods, computer readable media, and systems for co-editing content |
JP6434640B2 (en) * | 2014-11-04 | 2018-12-05 | 華為技術有限公司Huawei Technologies Co.,Ltd. | Message display method, message display device, and message display device |
US10191890B2 (en) * | 2014-12-17 | 2019-01-29 | Microsoft Technology Licensing, Llc | Persistent viewports |
US20170129870A1 (en) * | 2015-11-11 | 2017-05-11 | Mohan Murali Alapati | Compositions and methods for the treatment of neurological diseases |
US9798742B2 (en) | 2015-12-21 | 2017-10-24 | International Business Machines Corporation | System and method for the identification of personal presence and for enrichment of metadata in image media |
US11036712B2 (en) | 2016-01-12 | 2021-06-15 | Microsoft Technology Licensing, Llc. | Latency-reduced document change discovery |
US10303420B2 (en) * | 2017-05-02 | 2019-05-28 | Microsoft Technology Licensing, Llc | Proactive staged distribution of document activity indicators |
US11330029B2 (en) * | 2018-03-27 | 2022-05-10 | Lenovo (Singapore) Pte. Ltd. | Sharing content with a detected device |
KR20200086856A (en) * | 2019-01-10 | 2020-07-20 | 최재호 | Apparatus and method of file sharing based on chat room |
US11418551B2 (en) | 2019-10-18 | 2022-08-16 | Samsung Sds Co., Ltd. | Method and system for providing virtual whiteboard based collaboration service |
WO2021218946A1 (en) * | 2020-04-30 | 2021-11-04 | 北京字节跳动网络技术有限公司 | Method and device for information exchange, electronic device, and storage medium |
EP4135271A4 (en) * | 2020-04-30 | 2023-09-13 | Beijing Bytedance Network Technology Co., Ltd. | Information interaction method and apparatus, device, and medium |
CN111953502A (en) | 2020-07-28 | 2020-11-17 | 北京字节跳动网络技术有限公司 | Information announcement method and device and electronic equipment |
US11863525B2 (en) * | 2021-01-29 | 2024-01-02 | Salesforce, Inc. | Contact passlisting across digital channels |
Citations (24)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6778642B1 (en) * | 1999-03-23 | 2004-08-17 | Verizon Laboratories Inc. | Unified messaging system |
US20060173784A1 (en) * | 2005-01-26 | 2006-08-03 | Marples David J | Payment system for the distribution of digital content using an intelligent services control point |
US20070071187A1 (en) * | 2005-07-26 | 2007-03-29 | Microsoft Corporation | Providing contextual information automatically |
US20070113201A1 (en) * | 2005-11-17 | 2007-05-17 | Bales Christopher E | System and method for providing active menus in a communities framework |
US20070143415A1 (en) * | 2005-12-15 | 2007-06-21 | Daigle Brian K | Customizable presence icons for instant messaging |
US20070226357A1 (en) * | 2006-03-22 | 2007-09-27 | Mcmurry Kathleen A | Providing an Aggregate Reachability Status |
US20070226125A1 (en) * | 2006-03-10 | 2007-09-27 | Temte John D | Interactive system and method for transacting business |
US20070282887A1 (en) * | 2006-05-31 | 2007-12-06 | Red. Hat, Inc. | Link swarming in an open overlay for social networks and online services |
US20080114776A1 (en) * | 2005-07-22 | 2008-05-15 | Huawei Technologies Co., Ltd. | Method and system for providing presence information, the presence server thereof |
US20080125157A1 (en) * | 2005-12-30 | 2008-05-29 | Huawei Technologies Co., Ltd. | Method, system and apparatuses for sharing presence information |
US20080133698A1 (en) * | 2006-12-05 | 2008-06-05 | Chavez Timothy R | File Fragment Trading Based on Rarity Values in a Segmented File Sharing System |
US20080153459A1 (en) * | 2006-09-08 | 2008-06-26 | Palm, Inc. | Apparatus and methods for providing directional commands for a mobile computing device |
US20090061825A1 (en) * | 2007-08-31 | 2009-03-05 | Palm, Inc. | Techniques for group messaging on a mobile computing device |
US20090092124A1 (en) * | 2007-10-03 | 2009-04-09 | Microsoft Corporation | Network routing of endpoints to content based on content swarms |
US20090100128A1 (en) * | 2007-10-15 | 2009-04-16 | General Electric Company | Accelerating peer-to-peer content distribution |
US7533153B1 (en) * | 2008-05-15 | 2009-05-12 | International Business Machines Corporation | Method for managing instant messaging presence by group |
US20090125413A1 (en) * | 2007-10-09 | 2009-05-14 | Firstpaper Llc | Systems, methods and apparatus for content distribution |
US20090182815A1 (en) * | 2007-10-15 | 2009-07-16 | General Electric Company | Accelerating peer-to-peer content distribution |
US20100023615A1 (en) * | 2008-07-23 | 2010-01-28 | Grigsby Travis M | Redirecting web downloads |
US7702315B2 (en) * | 2002-10-15 | 2010-04-20 | Varia Holdings Llc | Unified communication thread for wireless mobile communication devices |
US7831928B1 (en) * | 2006-06-22 | 2010-11-09 | Digg, Inc. | Content visualization |
US20110153452A1 (en) * | 2004-05-20 | 2011-06-23 | Manyworlds, Inc. | Contextual Commerce Systems and Methods |
US20110293079A1 (en) * | 2006-04-20 | 2011-12-01 | Cisco Technology, Inc. | Techniques for Marking and Manipulating Voice Message Segments Through a Telephone User Interface |
US8140621B2 (en) * | 2009-03-27 | 2012-03-20 | T-Mobile, Usa, Inc. | Providing event data to a group of contacts |
Family Cites Families (142)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5107443A (en) * | 1988-09-07 | 1992-04-21 | Xerox Corporation | Private regions within a shared workspace |
US5671428A (en) * | 1991-08-28 | 1997-09-23 | Kabushiki Kaisha Toshiba | Collaborative document processing system with version and comment management |
US6148328A (en) * | 1998-01-29 | 2000-11-14 | International Business Machines Corp. | Method and system for signaling presence of users in a networked environment |
US6601087B1 (en) * | 1998-11-18 | 2003-07-29 | Webex Communications, Inc. | Instant document sharing |
US6360272B1 (en) * | 1999-05-28 | 2002-03-19 | Palm, Inc. | Method and apparatus for maintaining a unified view of multiple mailboxes |
JP3572571B2 (en) * | 1999-06-30 | 2004-10-06 | 富士通株式会社 | Multi-tier management system and local monitoring device |
US6678698B2 (en) * | 2000-02-15 | 2004-01-13 | Intralinks, Inc. | Computerized method and system for communicating and managing information used in task-oriented projects |
JP3549097B2 (en) * | 2000-04-26 | 2004-08-04 | インターナショナル・ビジネス・マシーンズ・コーポレーション | Method for identifying owner of collaborative work object, computer system, and computer-readable recording medium |
US6684212B1 (en) * | 2000-08-14 | 2004-01-27 | Ford Motor Company | System and method for data sharing between members of diverse organizations |
WO2002021413A2 (en) * | 2000-09-05 | 2002-03-14 | Zaplet, Inc. | Methods and apparatus providing electronic messages that are linked and aggregated |
US6661877B1 (en) * | 2000-09-29 | 2003-12-09 | Oracle International Corporation | System and method for providing access to a unified message store logically storing computer telephony messages |
US8707185B2 (en) * | 2000-10-10 | 2014-04-22 | Addnclick, Inc. | Dynamic information management system and method for content delivery and sharing in content-, metadata- and viewer-based, live social networking among users concurrently engaged in the same and/or similar content |
US6725228B1 (en) * | 2000-10-31 | 2004-04-20 | David Morley Clark | System for managing and organizing stored electronic messages |
US7082457B1 (en) * | 2000-11-01 | 2006-07-25 | Microsoft Corporation | System and method for delegation in a project management context |
US20020075303A1 (en) * | 2000-12-18 | 2002-06-20 | Nortel Networks Limited And Bell Canada | Method and system for creating a virtual team environment |
US20020083134A1 (en) * | 2000-12-22 | 2002-06-27 | Bauer Kirk Wayne | Method and system of collaborative browsing |
CA2368404C (en) * | 2001-01-18 | 2005-08-09 | Research In Motion Limited | Unified messaging system and method |
US6981223B2 (en) * | 2001-03-19 | 2005-12-27 | Ecrio, Inc. | Method, apparatus and computer readable medium for multiple messaging session management with a graphical user interface |
US7603379B2 (en) * | 2001-04-11 | 2009-10-13 | Lg Electronics Inc. | Unified management method of various types of messages of a personal information terminal |
US7325193B2 (en) * | 2001-06-01 | 2008-01-29 | International Business Machines Corporation | Automated management of internet and/or web site content |
US6976028B2 (en) * | 2001-06-15 | 2005-12-13 | Sony Corporation | Media content creating and publishing system and process |
US20030020749A1 (en) * | 2001-07-10 | 2003-01-30 | Suhayya Abu-Hakima | Concept-based message/document viewer for electronic communications and internet searching |
US7370269B1 (en) * | 2001-08-31 | 2008-05-06 | Oracle International Corporation | System and method for real-time annotation of a co-browsed document |
US6954737B2 (en) * | 2001-11-05 | 2005-10-11 | Johnsondiversey, Inc. | Method and apparatus for work management for facility maintenance |
NL1019286C2 (en) * | 2001-11-05 | 2003-05-07 | Koninkl Kpn Nv | Information storage system. |
US7496841B2 (en) * | 2001-12-17 | 2009-02-24 | Workshare Technology, Ltd. | Method and system for document collaboration |
US20030112273A1 (en) * | 2001-12-17 | 2003-06-19 | Workshare Technology, Ltd. | Document collaboration suite using a common database |
US6769013B2 (en) * | 2002-02-02 | 2004-07-27 | E-Wings, Inc. | Distributed system for interactive collaboration |
US7299193B2 (en) * | 2002-02-06 | 2007-11-20 | International Business Machines Corporation | Method and meeting scheduler for automated meeting scheduling using delegates, representatives, quorums and teams |
US7698230B1 (en) * | 2002-02-15 | 2010-04-13 | ContractPal, Inc. | Transaction architecture utilizing transaction policy statements |
US20030231207A1 (en) * | 2002-03-25 | 2003-12-18 | Baohua Huang | Personal e-mail system and method |
US20040015556A1 (en) * | 2002-05-10 | 2004-01-22 | Renu Chopra | Software-based process/issue management system |
US7263535B2 (en) * | 2002-05-21 | 2007-08-28 | Bellsouth Intellectual Property Corporation | Resource list management system |
US7111044B2 (en) * | 2002-07-17 | 2006-09-19 | Fastmobile, Inc. | Method and system for displaying group chat sessions on wireless mobile terminals |
US7401158B2 (en) * | 2002-09-16 | 2008-07-15 | Oracle International Corporation | Apparatus and method for instant messaging collaboration |
US7818678B2 (en) * | 2002-10-31 | 2010-10-19 | Litera Technology Llc | Collaborative document development and review system |
US20080027781A1 (en) * | 2002-11-20 | 2008-01-31 | Vom Scheidt Gregor A | Method for monitoring and controlling workflow of a project, applications program and computer product embodying same and related computer systems |
US7139761B2 (en) * | 2002-12-11 | 2006-11-21 | Leader Technologies, Inc. | Dynamic association of electronically stored information with iterative workflow changes |
EP1576447A1 (en) * | 2002-12-17 | 2005-09-21 | Koninklijke Philips Electronics N.V. | System to allow content sharing |
US20040201668A1 (en) * | 2003-04-11 | 2004-10-14 | Hitachi, Ltd. | Method and apparatus for presence indication |
US9256753B2 (en) * | 2003-06-11 | 2016-02-09 | Microsoft Technology Licensing, Llc | Method and apparatus for protecting regions of an electronic document |
US7904323B2 (en) * | 2003-06-23 | 2011-03-08 | Intel Corporation | Multi-team immersive integrated collaboration workspace |
AU2003903994A0 (en) * | 2003-07-31 | 2003-08-14 | Canon Kabushiki Kaisha | Collaborative editing with automatic layout |
US20050033811A1 (en) * | 2003-08-07 | 2005-02-10 | International Business Machines Corporation | Collaborative email |
US7433920B2 (en) * | 2003-10-10 | 2008-10-07 | Microsoft Corporation | Contact sidebar tile |
US20050089023A1 (en) * | 2003-10-23 | 2005-04-28 | Microsoft Corporation | Architecture for an extensible real-time collaboration system |
US20050203851A1 (en) * | 2003-10-25 | 2005-09-15 | Macrovision Corporation | Corruption and its deterrence in swarm downloads of protected files in a file sharing network |
US20050114475A1 (en) * | 2003-11-24 | 2005-05-26 | Hung-Yang Chang | System and method for collaborative development environments |
US7451190B2 (en) * | 2003-11-26 | 2008-11-11 | Yahoo! Inc. | Associating multiple visibility profiles with a user of a real-time communication system |
US20050138540A1 (en) * | 2003-12-22 | 2005-06-23 | Xerox Corporation | Systems and methods for user-specific document change highlighting |
US9224131B2 (en) * | 2003-12-29 | 2015-12-29 | International Business Machines Corporation | System and method for facilitating collaboration in a shared email repository |
US7296023B2 (en) * | 2004-01-15 | 2007-11-13 | International Business Machines Corporation | Method and apparatus for persistent real-time collaboration |
US20050198124A1 (en) * | 2004-03-03 | 2005-09-08 | Mccarthy Shawn J. | System and method for embedded instant messaging collaboration |
KR101254209B1 (en) * | 2004-03-22 | 2013-04-23 | 삼성전자주식회사 | Apparatus and method for moving and copying right objects between device and portable storage device |
JP4352959B2 (en) * | 2004-03-25 | 2009-10-28 | 日本電気株式会社 | Group communication system based on presence information and client device |
US7734802B1 (en) * | 2004-05-28 | 2010-06-08 | Adobe Systems Incorporated | Dynamically adaptable collaborative electronic meeting space |
US7933958B2 (en) * | 2004-06-08 | 2011-04-26 | International Business Machines Corporation | Real-time blog interaction |
US20060026502A1 (en) * | 2004-07-28 | 2006-02-02 | Koushik Dutta | Document collaboration system |
US7730030B1 (en) * | 2004-08-15 | 2010-06-01 | Yongyong Xu | Resource based virtual communities |
US7707249B2 (en) * | 2004-09-03 | 2010-04-27 | Open Text Corporation | Systems and methods for collaboration |
US7867094B1 (en) * | 2004-11-18 | 2011-01-11 | Turbo Squid, Inc. | Methods for promoting the development and sharing of content and a dynamically modified computer game |
US8347088B2 (en) * | 2005-02-01 | 2013-01-01 | Newsilike Media Group, Inc | Security systems and methods for use with structured and unstructured data |
US7783980B1 (en) * | 2005-04-07 | 2010-08-24 | Aol Inc. | Sharing digital items |
US10510043B2 (en) * | 2005-06-13 | 2019-12-17 | Skyword Inc. | Computer method and apparatus for targeting advertising |
US7991916B2 (en) * | 2005-09-01 | 2011-08-02 | Microsoft Corporation | Per-user application rendering in the presence of application sharing |
WO2007037018A1 (en) * | 2005-09-29 | 2007-04-05 | Fujitsu Limited | Presence communication system |
US8566109B2 (en) * | 2005-11-29 | 2013-10-22 | Alcatel Lucent | Common interest community service via presence messaging |
US20080228738A1 (en) * | 2005-12-13 | 2008-09-18 | Wisteme, Llc | Web based open knowledge system with user-editable attributes |
US7913162B2 (en) * | 2005-12-20 | 2011-03-22 | Pitney Bowes Inc. | System and method for collaborative annotation using a digital pen |
US20070150299A1 (en) * | 2005-12-22 | 2007-06-28 | Flory Clive F | Method, system, and apparatus for the management of the electronic files |
US20070218900A1 (en) * | 2006-03-17 | 2007-09-20 | Raj Vasant Abhyanker | Map based neighborhood search and community contribution |
US20070150491A1 (en) * | 2005-12-28 | 2007-06-28 | Marko Torvinen | Server middleware for enterprise work group presence solution |
US20070157105A1 (en) * | 2006-01-04 | 2007-07-05 | Stephen Owens | Network user database for a sidebar |
US7933956B2 (en) * | 2006-01-24 | 2011-04-26 | Simulat, Inc. | System and method to create a collaborative web-based multimedia layered platform |
US8464164B2 (en) * | 2006-01-24 | 2013-06-11 | Simulat, Inc. | System and method to create a collaborative web-based multimedia contextual dialogue |
US7764701B1 (en) * | 2006-02-22 | 2010-07-27 | Qurio Holdings, Inc. | Methods, systems, and products for classifying peer systems |
US20090198622A1 (en) * | 2006-03-10 | 2009-08-06 | Temte John D | Interactive System And Method For Transacting Business Over A Network |
US8560946B2 (en) * | 2006-03-22 | 2013-10-15 | Vistracks, Inc. | Timeline visualizations linked with other visualizations of data in a thin client |
US8744885B2 (en) * | 2006-03-28 | 2014-06-03 | Snowflake Itm, Inc. | Task based organizational management system and method |
US20070260683A1 (en) * | 2006-05-04 | 2007-11-08 | International Business Machines Corporation | Computer program product for providing parallel presentations |
CA2652507C (en) * | 2006-05-16 | 2013-05-07 | Research In Motion Limited | System and method for home screen interface integrating application and system status |
US20070282947A1 (en) * | 2006-05-31 | 2007-12-06 | Susanne Hupfer | Method and system for providing simultaneous awareness across multiple team spaces in real time |
US9009607B2 (en) * | 2006-06-22 | 2015-04-14 | Linkedin Corporation | Evaluating content |
US20130066822A1 (en) * | 2006-06-22 | 2013-03-14 | Digg, Inc. | Promoting content |
US8020172B2 (en) * | 2006-06-30 | 2011-09-13 | Sap Ag | Using status models having status derivations in a computer system |
US8200715B1 (en) * | 2006-06-30 | 2012-06-12 | Sap Ag | Using status models with adaptable process steps in a computer system |
US7966647B1 (en) * | 2006-08-16 | 2011-06-21 | Resource Consortium Limited | Sending personal information to a personal information aggregator |
US7634540B2 (en) * | 2006-10-12 | 2009-12-15 | Seiko Epson Corporation | Presenter view control system and method |
WO2008054750A2 (en) * | 2006-10-30 | 2008-05-08 | Credit Suisse Securities (Usa) Llc | Generating documentation and approvals for entities and transactions |
US7693736B1 (en) * | 2006-10-30 | 2010-04-06 | Avaya Inc. | Recurring meeting schedule wizard |
US20080177708A1 (en) * | 2006-11-01 | 2008-07-24 | Koollage, Inc. | System and method for providing persistent, dynamic, navigable and collaborative multi-media information packages |
US7552127B2 (en) * | 2006-12-19 | 2009-06-23 | International Business Machines Corporation | System and method for providing platform-independent content services for users for content from content applications leveraging Atom, XLink, XML Query content management systems |
US7900142B2 (en) * | 2007-01-15 | 2011-03-01 | Microsoft Corporation | Selective undo of editing operations performed on data objects |
US8683342B2 (en) * | 2007-02-28 | 2014-03-25 | Red Hat, Inc. | Automatic selection of online content for sharing |
US8762327B2 (en) * | 2007-02-28 | 2014-06-24 | Red Hat, Inc. | Synchronizing disributed online collaboration content |
US20080244740A1 (en) * | 2007-03-06 | 2008-10-02 | Wetpaint.Com, Inc. | Browser-independent editing of content |
US20080243852A1 (en) * | 2007-03-26 | 2008-10-02 | International Business Machines Corporation | System and Methods for Enabling Collaboration in Online Enterprise Applications |
US7765266B2 (en) * | 2007-03-30 | 2010-07-27 | Uranus International Limited | Method, apparatus, system, medium, and signals for publishing content created during a communication |
US8095873B2 (en) * | 2007-04-02 | 2012-01-10 | International Business Machines Corporation | Promoting content from one content management system to another content management system |
US20080290987A1 (en) * | 2007-04-22 | 2008-11-27 | Lehmann Li | Methods and apparatus related to content sharing between devices |
US8224897B2 (en) * | 2007-06-13 | 2012-07-17 | Microsoft Corporation | Automatically sharing a user's personal message |
US20080320087A1 (en) * | 2007-06-22 | 2008-12-25 | Microsoft Corporation | Swarm sensing and actuating |
US20090049135A1 (en) * | 2007-08-16 | 2009-02-19 | O'sullivan Patrick J | System and method for managing an instant messaging community |
US8555200B2 (en) * | 2007-08-21 | 2013-10-08 | Wetpaint.Com, Inc. | Representing editable attributes of embedded content |
US8433999B2 (en) * | 2007-08-21 | 2013-04-30 | Wetpaint.Com, Inc. | Method and apparatus for retrieving and editing dynamically generated content for editable web pages |
US8631015B2 (en) * | 2007-09-06 | 2014-01-14 | Linkedin Corporation | Detecting associates |
US20090083132A1 (en) * | 2007-09-20 | 2009-03-26 | General Electric Company | Method and system for statistical tracking of digital asset infringements and infringers on peer-to-peer networks |
US20090222743A1 (en) * | 2007-09-27 | 2009-09-03 | Hadfield Marc C | Meme-Based Graphical User Interface And Team Collaboration System |
US7945594B2 (en) * | 2007-09-27 | 2011-05-17 | Sap Ag | Using status models with inhibiting status values in a computer system |
US20090163183A1 (en) * | 2007-10-04 | 2009-06-25 | O'donoghue Hugh | Recommendation generation systems, apparatus and methods |
US20090113311A1 (en) * | 2007-10-25 | 2009-04-30 | Eric Philip Fried | Personal status display system |
US8381169B2 (en) * | 2007-10-30 | 2013-02-19 | International Business Machines Corporation | Extending unified process and method content to include dynamic and collaborative content |
US8145600B1 (en) * | 2007-11-02 | 2012-03-27 | Adobe Systems Incorporated | Version preview and selection |
US8620708B2 (en) * | 2007-11-09 | 2013-12-31 | Hitachi-Ge Nuclear Energy, Ltd. | Progress status management method, program, and progress status management device |
US7941399B2 (en) * | 2007-11-09 | 2011-05-10 | Microsoft Corporation | Collaborative authoring |
WO2009070927A1 (en) * | 2007-12-03 | 2009-06-11 | Ebay Inc. | Live search chat room |
US7954058B2 (en) * | 2007-12-14 | 2011-05-31 | Yahoo! Inc. | Sharing of content and hop distance over a social network |
US20090192869A1 (en) * | 2008-01-25 | 2009-07-30 | Irvine Steven R | Marketing Control Center |
US20130215116A1 (en) * | 2008-03-21 | 2013-08-22 | Dressbot, Inc. | System and Method for Collaborative Shopping, Business and Entertainment |
US8429176B2 (en) * | 2008-03-28 | 2013-04-23 | Yahoo! Inc. | Extending media annotations using collective knowledge |
US9172751B2 (en) * | 2008-04-09 | 2015-10-27 | Nokia Technologies Oy | Content distribution |
US8352870B2 (en) * | 2008-04-28 | 2013-01-08 | Microsoft Corporation | Conflict resolution |
US9418054B2 (en) * | 2008-05-12 | 2016-08-16 | Adobe Systems Incorporated | Document comment management |
US8417666B2 (en) * | 2008-06-25 | 2013-04-09 | Microsoft Corporation | Structured coauthoring |
US20090327904A1 (en) * | 2008-06-27 | 2009-12-31 | Microsoft Corporation | Presenting dynamic folders |
US20100169364A1 (en) * | 2008-06-30 | 2010-07-01 | Blame Canada Holdings Inc. | Metadata Enhanced Browser |
US20100004944A1 (en) * | 2008-07-07 | 2010-01-07 | Murugan Palaniappan | Book Creation In An Online Collaborative Environment |
US9569406B2 (en) * | 2008-10-08 | 2017-02-14 | Adobe Systems Incorporated | Electronic content change tracking |
US9386089B2 (en) * | 2008-11-11 | 2016-07-05 | Nbcuniversal Media, Llc | Early detection of high volume peer-to-peer swarms |
US8108779B1 (en) * | 2008-12-16 | 2012-01-31 | Adobe Systems Incorporated | Collaborative editing operations |
US8327278B2 (en) * | 2009-02-17 | 2012-12-04 | Microsoft Corporation | Synchronizing metadata describes user content updates and an indication of user gestures being performed within the document, and across client systems using different communication channels |
US20100257457A1 (en) * | 2009-04-07 | 2010-10-07 | De Goes John A | Real-time content collaboration |
US9046995B2 (en) * | 2009-04-09 | 2015-06-02 | On24, Inc. | Editing of two dimensional software consumables within a complex three dimensional spatial application and method |
US8209603B2 (en) * | 2009-04-29 | 2012-06-26 | Microsoft Corporation | Maintaining undo and redo capability across metadata merges |
US8161019B2 (en) * | 2009-05-01 | 2012-04-17 | Microsoft Corporation | Cross-channel coauthoring consistency |
US20100287023A1 (en) * | 2009-05-05 | 2010-11-11 | Microsoft Corporation | Collaborative view for a group participation plan |
WO2010135724A1 (en) * | 2009-05-21 | 2010-11-25 | Shared Performance, Llc | Methods and systems for resource and organization achievement |
US20100299385A1 (en) * | 2009-05-22 | 2010-11-25 | Timothy Root | Method & apparatus for displaying the presence of a shared client communication device |
US8156050B2 (en) * | 2009-05-26 | 2012-04-10 | The United States Of America As Represented By The Secretary Of The Navy | Project management system and method |
US20100318571A1 (en) * | 2009-06-16 | 2010-12-16 | Leah Pearlman | Selective Content Accessibility in a Social Network |
US20110010635A1 (en) * | 2009-07-10 | 2011-01-13 | Novell, Inc. | Unified editable inbox |
US8280958B2 (en) * | 2009-07-13 | 2012-10-02 | International Business Machines Corporation | List passing in a background file sharing network |
-
2010
- 2010-01-19 US US12/690,056 patent/US20110010635A1/en not_active Abandoned
- 2010-01-19 US US12/690,038 patent/US20110010424A1/en not_active Abandoned
- 2010-01-19 US US12/690,075 patent/US20110010638A1/en not_active Abandoned
- 2010-01-19 US US12/690,028 patent/US8898282B2/en not_active Expired - Fee Related
- 2010-01-19 US US12/690,066 patent/US8280846B2/en not_active Expired - Fee Related
- 2010-01-19 US US12/690,071 patent/US20110010640A1/en not_active Abandoned
-
2012
- 2012-09-14 US US13/619,543 patent/US9595022B2/en active Active
Patent Citations (25)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7349528B2 (en) * | 1999-03-23 | 2008-03-25 | Verizon Laboratories Inc. | Unified messaging system |
US6778642B1 (en) * | 1999-03-23 | 2004-08-17 | Verizon Laboratories Inc. | Unified messaging system |
US7702315B2 (en) * | 2002-10-15 | 2010-04-20 | Varia Holdings Llc | Unified communication thread for wireless mobile communication devices |
US20110153452A1 (en) * | 2004-05-20 | 2011-06-23 | Manyworlds, Inc. | Contextual Commerce Systems and Methods |
US20060173784A1 (en) * | 2005-01-26 | 2006-08-03 | Marples David J | Payment system for the distribution of digital content using an intelligent services control point |
US20080114776A1 (en) * | 2005-07-22 | 2008-05-15 | Huawei Technologies Co., Ltd. | Method and system for providing presence information, the presence server thereof |
US20070071187A1 (en) * | 2005-07-26 | 2007-03-29 | Microsoft Corporation | Providing contextual information automatically |
US20070113201A1 (en) * | 2005-11-17 | 2007-05-17 | Bales Christopher E | System and method for providing active menus in a communities framework |
US20070143415A1 (en) * | 2005-12-15 | 2007-06-21 | Daigle Brian K | Customizable presence icons for instant messaging |
US20080125157A1 (en) * | 2005-12-30 | 2008-05-29 | Huawei Technologies Co., Ltd. | Method, system and apparatuses for sharing presence information |
US20070226125A1 (en) * | 2006-03-10 | 2007-09-27 | Temte John D | Interactive system and method for transacting business |
US20070226357A1 (en) * | 2006-03-22 | 2007-09-27 | Mcmurry Kathleen A | Providing an Aggregate Reachability Status |
US20110293079A1 (en) * | 2006-04-20 | 2011-12-01 | Cisco Technology, Inc. | Techniques for Marking and Manipulating Voice Message Segments Through a Telephone User Interface |
US20070282887A1 (en) * | 2006-05-31 | 2007-12-06 | Red. Hat, Inc. | Link swarming in an open overlay for social networks and online services |
US7831928B1 (en) * | 2006-06-22 | 2010-11-09 | Digg, Inc. | Content visualization |
US20080153459A1 (en) * | 2006-09-08 | 2008-06-26 | Palm, Inc. | Apparatus and methods for providing directional commands for a mobile computing device |
US20080133698A1 (en) * | 2006-12-05 | 2008-06-05 | Chavez Timothy R | File Fragment Trading Based on Rarity Values in a Segmented File Sharing System |
US20090061825A1 (en) * | 2007-08-31 | 2009-03-05 | Palm, Inc. | Techniques for group messaging on a mobile computing device |
US20090092124A1 (en) * | 2007-10-03 | 2009-04-09 | Microsoft Corporation | Network routing of endpoints to content based on content swarms |
US20090125413A1 (en) * | 2007-10-09 | 2009-05-14 | Firstpaper Llc | Systems, methods and apparatus for content distribution |
US20090182815A1 (en) * | 2007-10-15 | 2009-07-16 | General Electric Company | Accelerating peer-to-peer content distribution |
US20090100128A1 (en) * | 2007-10-15 | 2009-04-16 | General Electric Company | Accelerating peer-to-peer content distribution |
US7533153B1 (en) * | 2008-05-15 | 2009-05-12 | International Business Machines Corporation | Method for managing instant messaging presence by group |
US20100023615A1 (en) * | 2008-07-23 | 2010-01-28 | Grigsby Travis M | Redirecting web downloads |
US8140621B2 (en) * | 2009-03-27 | 2012-03-20 | T-Mobile, Usa, Inc. | Providing event data to a group of contacts |
Cited By (17)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20130024419A1 (en) * | 2009-07-10 | 2013-01-24 | Andrew Fox | Collaboration swarming |
US9595022B2 (en) * | 2009-07-10 | 2017-03-14 | Micro Focus Software Inc. | Collaboration swarming |
US20160350398A1 (en) * | 2010-12-17 | 2016-12-01 | Microsoft Technology Licensing, Llc | Hash tag management in a microblogging infrastructure |
US10417260B2 (en) * | 2010-12-17 | 2019-09-17 | Microsoft Technology Licensing, Llc | Hash tag management in a microblogging infrastructure |
US20230077024A1 (en) * | 2011-12-29 | 2023-03-09 | Intel Corporation | Management of collaborative teams |
US9614724B2 (en) | 2014-04-21 | 2017-04-04 | Microsoft Technology Licensing, Llc | Session-based device configuration |
US9430667B2 (en) | 2014-05-12 | 2016-08-30 | Microsoft Technology Licensing, Llc | Managed wireless distribution network |
US9384335B2 (en) | 2014-05-12 | 2016-07-05 | Microsoft Technology Licensing, Llc | Content delivery prioritization in managed wireless distribution networks |
US10111099B2 (en) | 2014-05-12 | 2018-10-23 | Microsoft Technology Licensing, Llc | Distributing content in managed wireless distribution networks |
US9384334B2 (en) | 2014-05-12 | 2016-07-05 | Microsoft Technology Licensing, Llc | Content discovery in managed wireless distribution networks |
US9874914B2 (en) | 2014-05-19 | 2018-01-23 | Microsoft Technology Licensing, Llc | Power management contracts for accessory devices |
US10691445B2 (en) | 2014-06-03 | 2020-06-23 | Microsoft Technology Licensing, Llc | Isolating a portion of an online computing service for testing |
US9477625B2 (en) | 2014-06-13 | 2016-10-25 | Microsoft Technology Licensing, Llc | Reversible connector for accessory devices |
US9367490B2 (en) | 2014-06-13 | 2016-06-14 | Microsoft Technology Licensing, Llc | Reversible connector for accessory devices |
US9717006B2 (en) | 2014-06-23 | 2017-07-25 | Microsoft Technology Licensing, Llc | Device quarantine in a wireless network |
US20230247137A1 (en) * | 2022-01-31 | 2023-08-03 | Zoom Video Communications, Inc. | Collaborative Virtual Waiting Room |
US11936813B2 (en) * | 2022-01-31 | 2024-03-19 | Zoom Video Communications, Inc. | Collaborative virtual waiting room with connection modes |
Also Published As
Publication number | Publication date |
---|---|
US20110010640A1 (en) | 2011-01-13 |
US8280846B2 (en) | 2012-10-02 |
US8898282B2 (en) | 2014-11-25 |
US20110010335A1 (en) | 2011-01-13 |
US9595022B2 (en) | 2017-03-14 |
US20110010635A1 (en) | 2011-01-13 |
US20130024419A1 (en) | 2013-01-24 |
US20110010638A1 (en) | 2011-01-13 |
US20110010447A1 (en) | 2011-01-13 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20110010424A1 (en) | Unified addressing, sending, and receiving collaboration service | |
Müller | The digital nomad: Buzzword or research category? | |
US8082308B1 (en) | Online collaboration and planning system transparently integrated with e-mail | |
US8738720B2 (en) | Systems and methods for enabling anonymous collaboration among members along value chains | |
JP6254950B2 (en) | Existence-based synchronization | |
US10389663B2 (en) | Automatic uploading of attachments to group cloud storage at send time | |
CN110945841B (en) | Method and system for implementing multiple social media aliases | |
US20130031486A1 (en) | Pushed content notification and display | |
US20060105753A1 (en) | Method, wireless handheld electronic device and system of remotely controlling e-mail settings from the device | |
JP4992854B2 (en) | Community management system and community management method | |
US10764233B1 (en) | Centralized communication platform with email which organizes communication as a plurality of information streams and which generates a second message based on and a first message and formatting rules associated with a communication setting | |
US9954807B2 (en) | Endorsement indications in communication environments | |
US9235815B2 (en) | Name resolution | |
US10069780B2 (en) | Methods and systems for structuring information of email messages | |
CN111684442A (en) | System, method and software for implementing note taking services | |
JP6166390B2 (en) | Social network server, screen display method and program | |
US20180374056A1 (en) | Smart reminders for responding to emails | |
US20180374055A1 (en) | Smart reminders for responding to emails | |
US20170169393A1 (en) | Method of managing user contacts and associations between the user contacts | |
EP2405633A1 (en) | Pushed content notification and display | |
US9722959B2 (en) | Associating private annotations with public profiles | |
US20240121124A1 (en) | Scheduled synchronous multimedia collaboration sessions | |
JP6589846B2 (en) | E-mail management apparatus and e-mail management program | |
JP2024022684A (en) | Chat management program, chat processing program, chat management device, chat system, and chat processing method | |
Staines | Making connections in a disconnected world: Heather Staines discusses strategies for networking, mentoring and career advancement in the world of scholarly communications. |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: NOVELL, INC., UTAH Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:FOX, ANDREW;LAPALOMENTO, DAVID MARSHALL;ROUGHLEY, IAN EDWARD;SIGNING DATES FROM 20100127 TO 20100204;REEL/FRAME:023979/0508 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NEW YORK Free format text: GRANT OF PATENT SECURITY INTEREST;ASSIGNOR:NOVELL, INC.;REEL/FRAME:026270/0001 Effective date: 20110427 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, CAYMAN ISLANDS BRANCH, NEW YORK Free format text: GRANT OF PATENT SECURITY INTEREST (SECOND LIEN);ASSIGNOR:NOVELL, INC.;REEL/FRAME:026275/0018 Effective date: 20110427 |
|
AS | Assignment |
Owner name: NOVELL, INC., UTAH Free format text: RELEASE OF SECURITY INTEREST IN PATENTS FIRST LIEN (RELEASES RF 026270/0001 AND 027289/0727);ASSIGNOR:CREDIT SUISSE AG, AS COLLATERAL AGENT;REEL/FRAME:028252/0077 Effective date: 20120522 Owner name: NOVELL, INC., UTAH Free format text: RELEASE OF SECURITY IN PATENTS SECOND LIEN (RELEASES RF 026275/0018 AND 027290/0983);ASSIGNOR:CREDIT SUISSE AG, AS COLLATERAL AGENT;REEL/FRAME:028252/0154 Effective date: 20120522 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, AS COLLATERAL AGENT, NEW YORK Free format text: GRANT OF PATENT SECURITY INTEREST FIRST LIEN;ASSIGNOR:NOVELL, INC.;REEL/FRAME:028252/0216 Effective date: 20120522 Owner name: CREDIT SUISSE AG, AS COLLATERAL AGENT, NEW YORK Free format text: GRANT OF PATENT SECURITY INTEREST SECOND LIEN;ASSIGNOR:NOVELL, INC.;REEL/FRAME:028252/0316 Effective date: 20120522 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |
|
AS | Assignment |
Owner name: NOVELL, INC., UTAH Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0316;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:034469/0057 Effective date: 20141120 Owner name: NOVELL, INC., UTAH Free format text: RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 028252/0216;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:034470/0680 Effective date: 20141120 |
|
AS | Assignment |
Owner name: BANK OF AMERICA, N.A., CALIFORNIA Free format text: SECURITY INTEREST;ASSIGNORS:MICRO FOCUS (US), INC.;BORLAND SOFTWARE CORPORATION;ATTACHMATE CORPORATION;AND OTHERS;REEL/FRAME:035656/0251 Effective date: 20141120 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT, NEW Free format text: NOTICE OF SUCCESSION OF AGENCY;ASSIGNOR:BANK OF AMERICA, N.A., AS PRIOR AGENT;REEL/FRAME:042388/0386 Effective date: 20170501 |
|
AS | Assignment |
Owner name: JPMORGAN CHASE BANK, N.A., AS SUCCESSOR AGENT, NEW Free format text: CORRECTIVE ASSIGNMENT TO CORRECT THE TO CORRECT TYPO IN APPLICATION NUMBER 10708121 WHICH SHOULD BE 10708021 PREVIOUSLY RECORDED ON REEL 042388 FRAME 0386. ASSIGNOR(S) HEREBY CONFIRMS THE NOTICE OF SUCCESSION OF AGENCY;ASSIGNOR:BANK OF AMERICA, N.A., AS PRIOR AGENT;REEL/FRAME:048793/0832 Effective date: 20170501 |
|
AS | Assignment |
Owner name: MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.), WASHINGTON Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062623/0009 Effective date: 20230131 Owner name: MICRO FOCUS (US), INC., MARYLAND Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062623/0009 Effective date: 20230131 Owner name: NETIQ CORPORATION, WASHINGTON Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062623/0009 Effective date: 20230131 Owner name: ATTACHMATE CORPORATION, WASHINGTON Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062623/0009 Effective date: 20230131 Owner name: BORLAND SOFTWARE CORPORATION, MARYLAND Free format text: RELEASE OF SECURITY INTEREST REEL/FRAME 035656/0251;ASSIGNOR:JPMORGAN CHASE BANK, N.A.;REEL/FRAME:062623/0009 Effective date: 20230131 |