US8631119B2 - Interruptibility awareness service - Google Patents
Interruptibility awareness service Download PDFInfo
- Publication number
- US8631119B2 US8631119B2 US12/730,608 US73060810A US8631119B2 US 8631119 B2 US8631119 B2 US 8631119B2 US 73060810 A US73060810 A US 73060810A US 8631119 B2 US8631119 B2 US 8631119B2
- Authority
- US
- United States
- Prior art keywords
- requestee
- interruptibility
- requestor
- interaction
- interactor
- 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.)
- Expired - Fee Related, expires
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]
- H04L51/043—Real-time or near real-time messaging, e.g. instant messaging [IM] using or handling presence information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
- H04L51/52—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail for supporting social networking services
Definitions
- the present disclosure generally relates to computer systems and communications among users, and more particularly to interruptibility awareness service, which, for instance, may provide whether a user may be interrupted to receive a message or the like.
- Today's information and communication technology provides one with the ability to contact a given person at any time.
- Some of the available tools that can be used are email messaging, texting, and chatting tools.
- email messaging, texting, and chatting tools are used.
- texting, and chatting tools are used.
- Another technique monitors the given user's computer or scheduled activity, automatically resetting the user's status.
- Such technique allows a user to optionally have the user's status automatically switch to “In a meeting” when the user is participating in an online meeting according to the user's scheduled activity saved in the user's computer, and switch back to “I am available” when the online meeting concludes.
- this type of technique may provide automatic status updates, it only covers a subset of needed status updates.
- IP Internet Protocol
- GPS Global Positioning System
- a method and system for enabling a requestor to learn whether a requestee is interruptible are provided.
- the method may include obtaining current social interaction information of a requestee and determining whether the requestee is interruptible based on the requestee's current social interaction information.
- the method further includes returning a response that indicates the requestee's interruptibility.
- a system for enabling a requestor to learn whether a requestee is interruptible may include a storage device operable to store current social interaction information of a requestee.
- a module may be operable to obtain the current social interaction information of the requestee and to determine whether the requestee is interruptible based on the requestee's current social interaction information.
- the module may be further operable to return a response that indicates the requestee's interruptibility.
- a computer readable storage medium storing a program of instructions executable by a machine to perform one or more methods described herein also may be provided.
- FIG. 1 is an overview of a method for interruptibility awareness in one embodiment of the present disclosure.
- FIG. 2 is an architectural diagram illustrating network topology for interruptibility awareness in one embodiment of the present disclosure.
- FIG. 3 is a block diagram illustrating functional components for a system that performs interruptibility awareness in one embodiment of the present disclosure.
- FIG. 4 is a flow diagram illustrating flow control or logic of the interruptibility awareness server or system in one embodiment of the present disclosure.
- FIG. 5 is a flow diagram illustrating flow control of the interruptibility request handler in one embodiment of the present disclosure.
- FIG. 6 shows an example of a visualization of a requestee's social interaction information in one embodiment of the present disclosure.
- FIG. 7 shows an example of a visualization of a requestee's social interaction information in a second embodiment of the present disclosure.
- FIG. 8 illustrates an example of a computer system, in which the systems and methodologies of the present disclosure may be carried out or executed.
- the present disclosure discloses a technique which allows a user to determine whether another user can be interrupted, for instance, in order to contact that another user.
- users may be referred to as a first user, a second user, and so forth, only to denote different users.
- the terminologies, “first” and “second”, and so forth, however, do not impart any special meaning and do not imply any order.
- This disclosure also uses the terminology “requestor” to refer to a person trying to learn or find out whether another person is interruptible, and “requestee” to refer to that another person whom the requestor is learning about.
- the technique presented in the present disclosure may respond with the degree of interruptibility. For example, 0% indicates that the requestee should not be interrupted, 100% indicates that the requestee can be interrupted, 50% indicates that the requestee may be interrupted.
- the degree need not be represented as a percentage value as shown in this example. Rather, other degrees may be utilized, for example, ranking from a lower bound to upper bound (e.g., 1 to 10), a ratio, and others.
- the determination may be made, in one aspect, using an identifier of the user, and may shield private information of the user from one another.
- the determination also may be based on various factors. For instance, the technique of the present disclosure in one aspect, may allow a user (referred to as a first user or requestor) looking to contact another user (referred to herein as a second user or requestee) based on:
- known information may be utilized to determine whether the second user is interruptible or not.
- Algorithms to determine interruptibility may use known information, for example, by exploiting information provided by GPS, cellular phone, relationship between a first and a second user.
- a first user may set, incrementally or otherwise, information about a second user. For example, even if a user is doing exactly the same thing as another user, the interruptibility may be subjective, for example, based on who the user is. Therefore, the interruptibility may depend on both the user and the activity. A first user may be provided with the ability to add this information.
- This graphic may also indicate a level of activity (babble-esk)).
- the graphic may be dynamically updated. For example, the position of representative-dots indicating the associated user's level of activity may be dynamically updated (other babble genre graphics being possible as well).
- FIG. 6 shows an example of a visualization of a requestee's social interaction information in one embodiment of the present disclosure.
- FIG. 6 shows an example of a visualization of a requestee's social interaction information in one embodiment of the present disclosure.
- FIG. 7 shows an example of a visualization of a requestee's social interaction information in a second embodiment of the present disclosure. They are also referred to as a babble-like social proxy. Those figures show different graphics returned as a response, for example, to the requestor.
- the babble-like social proxy may be a lecture, a debate, or a roundtable, or the like.
- Visualization option A the requestee is represented by the small circle in the middle of the large circle, the large circle representing the context of the requestee's interaction.
- the other small circles represent all of the other interactors.
- the value inside each of the other small circles indicates the social importance or weight of the given interactor. In one embodiment of the present disclosure, this value ranges from 0 to 1, with 1 indicating the greatest social weight.
- there are four interactors in the context with the requestee with weight values of 0.2 (not important), 0.6, 0.8 (both somewhat important), and 1 (critically important, e.g., CEO of requestee's company).
- An extension of Visualization Option A is shown in FIG. 7 , Visualization Option B.
- the figure also shows a large circle, representing the context of the interaction, which contains small circles representing the requestee (the empty circle near the middle) and all of the current interactors, the social weight of each indicated by the value is each interactors' associated circle.
- this figure also contains a dot directly in the center of the large circle.
- the distance from the center indicates the level of activity of the associated user.
- the requestee's circle is very close to the center, their level of activity is very high (e.g., they just made a post to a chat site).
- the small circle containing 1 is all the way back at the edge of the large circle, indicating that the associated user has not participated recently.
- the technique of the present disclosure may provide a user, for example, a first user with the ability to set an alert with certainty level.
- a first user may set a profile setting that indicates if a second user's determined interruptibility is 75% or better, the first user should be notified.
- FIG. 1 is an overview of a method for interruptibility awareness in one embodiment of the present disclosure.
- a user wanting to contact another user makes a request for the interruptibility status of said another user.
- a user is a user of a device such as a computer, mobile phone, smartphone, and/or other devices, who desires to contact another user via that another user's device, for instance, by sending electronic mail, text messaging, chat messaging, phone call, and/or other.
- the user making the request is also referred to herein as a requestor.
- That another user whose interruptibility status is being requested is also referred to herein as a requestee.
- the request includes the requestor's and requestee's identifiers (IDs). Identifiers may include user names by which the users access the interruptibility awareness service or system of the present disclosure.
- IDs identifiers
- the requestee's current social interaction information is obtained.
- Such current social interaction information may include, but are not limited to: with whom the requestee is interacting; level of activity of the requestee and each interactor the requestee is interacting with; type of interaction the requestee is engaged in; role of each interactor the requestee is interacting with; location of an interaction the requestee is engaged in; location of each interactor the requestee is interacting with; speed at which the requestee is driving an automobile (e.g., if the requestee is currently driving); time of interaction the requestee is engaged in; date of interaction the requestee is engaged in; whether date of interaction the requestee is engaged in is a holiday, vacation day or another off-day or combinations thereof; or whether each interactor the requestee is interacting with is a work colleague, family member, or community or religious group member; or combinations thereof.
- determination is made as to whether the requestee is currently interruptible given their current social interaction information and the social relationship of the requestor to the requestee. This determination may be based on rules. For example,
- the indication of whether the requestee is currently interruptible or not is returned.
- the indication may be a binary value such as 0 or 1, or yes or no.
- the indication may be provided in terms of degrees, for example, percentage value or probability value indicating the likelihood that the requestee may be interrupted.
- the indication may be a graphic representation of requestee's social interaction data, for example, as shown in FIGS. 6 and 7 . Other measures of indications may be utilized.
- FIG. 2 is an architectural diagram illustrating a network topology for interruptibility awareness in one embodiment of the present disclosure.
- Requestor 1010 may be a user using a device such as a personal computer, laptop, netbook, mobile phone, smartphone or other devices through which the user can run a web browser, and/or send and receive messages, including but not limited to voice and/or text messages.
- Requestee 1020 may be another user using such devices or others that can run a web browser, and/or send and receive messages, including but not limited to voice and/or text messages.
- Requestor 1010 and Requestee 1020 devices communicate over a communications network 1030 such as the Internet and/or a private intranet.
- An interruptibility awareness server or system 1040 may be a computer system including hardware components such as one or more processors, storage devices, device drivers, network interface drivers, and programming logic and software that in conjunction provide the interruptibility awareness service of the present disclosure.
- the interruptibility awareness server or system 1040 may communicate to a plurality of users, e.g., one or more requestors (e.g., 1010 ) and requestees (e.g., 1020 ).
- FIG. 3 is a block diagram illustrating functional components for a system that provides interruptibility awareness in one embodiment of the present disclosure.
- the modules shown in FIG. 3 may be components of a computer system that may include any computing node that is able to load and execute programmatic code, for instance, running the operating system and server application suite.
- the system logic may be embodied as computer executable code that is loaded from a remote source (e.g., from a network file system), local permanent optical (CD-ROM), magnetic storage (such as disk), or storage 2020 into memory 2030 for execution by CPU 2000 .
- a network interface 2010 may be used for communicating to other network accessible services.
- Such an interface 2010 may include, but is not limited to a hardwired device, e.g., Ethernet over coax cable, wireless IP, and telephone to IP (VoIP), or others.
- the memory 2030 may include computer readable instructions, data structures, program modules and application interfaces providing logic or functional components for interruptibility awareness service.
- FIG. 3 illustrates the functional components residing in a computer system
- the system and method of the present disclosure is not limited to only that configuration.
- the components may be distributed over a network on different platforms in a distributed environment, and/or configured in a cloud computing environment.
- FIG. 3 shows a CPU 2000
- the system 1040 may include multiple processors and/or cores.
- the system 1040 also includes a network interface 2010 , including, but not limited to Ethernet or wireless IP (e.g., LEAP, CDMA or WAP); a storage device 2020 , such as a disk or DASD (direct access storage device); and memory 2030 , such as RAM.
- a network interface 2010 including, but not limited to Ethernet or wireless IP (e.g., LEAP, CDMA or WAP)
- a storage device 2020 such as a disk or DASD (direct access storage device)
- memory 2030 such as RAM.
- the network interface 2010 allows the system to communicate with other network connected nodes, such as the requestor 1010 and the requestee 1020 via the network 1030 .
- the Interruptibility Awareness Server's logic 2040 (which will be described in detail with reference to FIG. 4 ) is possibly embodied as computer executable code that is loaded from a remote source (e.g., over the network 1030 ), a local permanent optical CR-ROM, magnetic storage (such as disk), or from the storage device 2020 into memory 2030 for execution by the CPU 2000 .
- the memory 2030 may include:
- the interruptibility awareness server database handler 2100 provides for creation, deletion and modification of persistent data, and is used by the handlers 2045 - 2090 of the interruptibility awareness server 1040 .
- An example of a product providing such function includes IBM DB/2TM database system.
- FIG. 4 is a flow diagram illustrating flow control or logic 2040 for the interruptibility awareness server or system 1040 in one embodiment of the present disclosure.
- the server 1040 awaits input, for example, requests from one or more requestors to determine interruptibility of a user, e.g., a requestee.
- step 3030 checks whether the input is a request to update the interruptibility rules for the requestee. If so, then the interruptibility update handler 2080 is called in step 3040 .
- This interruptibility update handler 2080 allows for the updating of the interruptibility determining rules and/or other data for the requestee. These updates include, but are not limited to:
- the requestor may also customize one or more weightings of the requestee's current social interactions, for example, by requesting a history of their interruptibility requests for a given requestee.
- the system and/or method of the present disclosure may present the requestor with a list of the interruptibility requests that were made and corresponding responses.
- the requestor may suggest changes to the data indicated in the provided one or more responses (e.g., suggest modified weights for one or more of the interactors). Those changes may be stored and used in future interruptibility requests for the requestee from the given requestor.
- a requestee may be enabled to customize the weightings of interactors in their own social interactions.
- the requestee may specify one or more requestors, wherein history of requests from the specified one or more requestors and associated responses are provided to the requestee.
- the requestee may modify the associated responses, wherein the modified responses are used in future interruptibility determinations for one or more requests from the specified one or more requestors.
- the requestee may also specify the role of one or more interactors whom the requestee is interacting with.
- the handler passes the ID of the requestee as well as the requestor when it is invoked. Once all additions and alterations have been completed, the user indicates “save” and the handler stores the updated rules using the interruptibility awareness server database handler 2100 . To alter rules for a different requestee/requestor pair of users, the handler 2080 , is invoked with the new pair.
- the determined interruptibility responses may be saved or stored for future reference or use, as well as being provided to the requestor at the time of the request.
- a user may be able to retrieve a history of responses.
- the interruptibility update handler 2080 allows a user to request this information using the interruptibility history retrieving handler 2090 .
- This handler 2090 takes a given requestee/requestor pair of user ID's and returns a history of the responses for the pair, retrieving the information from the interruptibility awareness server database handler 2100 .
- the information provided includes not only each response (i.e., the 0-1 estimate of the requestee's interruptibility by the requestor) but also indication of the requestee's social interaction information at the time of the response.
- control continues at step 3000 .
- the flow control continues to miscellaneous handler for handling the input appropriately, following which control continues at step 3000 .
- FIG. 5 shows the logic flow of the interruptibility request handler 2045 in one embodiment.
- This handler 2045 which is passed the ID's of both the requestee and requestor determines the interruptibility of the requestee by the requestor, returning an indication of this determination to the requestor.
- the interruptibility request handler 2045 obtains the current social interaction information for the requestee (i.e., what they are doing and with whom) using the social interaction information gathering handler 2050 in step 500 .
- One way for the handler 2050 to obtain this information may be from a chat server, e.g., where the requestee and requestor are active, as well as the ID's of any of interactors (e.g., chat participants).
- Another source of context information may be the GPS information provided by one or more of the requestee's devices (e.g., a cellular phone, like Apple's iPhone). Such information would include not only the requestee location (geographic, e.g., U.S. or another country, as well as “home” or “office”), but also may provide their speed. E.g., (in miles/hour):
- Yet another source of interaction information may be the requestee's calendar which may indicate such data as:
- the requestee's calendar could also provide a list of the attendees of one or more of the event (e.g., attendees of a given meeting, or the speaker at a given lecture, this speaker possibly being the requestee).
- the interruptibility determining handler 2060 stores all of this social interaction data in a new request entry using the interruptibility awareness server database handler 2100 .
- the information retrieval also includes the determination of the social weights for each of the interactors (e.g., searching for and retrieving them from the interruptibility awareness server database handler 2100 ).
- the interactor is on a lower organization level
- the default value e.g., 0.5
- low number level indicates higher status in the organization chart.
- Any and all calculated social weights are stored, including but not limited to adding this data to the new entry for the current request using the interruptibility awareness server database handler 2100 .
- the interruptibility determining handler 2060 is called to determine an estimate of whether the requestor can interrupt the requestee, this handler being passed the id's of the requestee and the requestor as well the requestee's social interaction information just obtained.
- the interruptibility determining handler 2060 then retrieves the interruptibility determining rules for the requestee and, where relevant, the requestor, from the interruptibility awareness server database handler 2100 .
- the handler then calculates the requestee's interruptibility by using the requestee's current social interaction information along with the interruptibility rules for the requestee. Note that the weights for each of the interactors can be dependent of the current context.
- a manager might have a weight of 0.9 during work hours, but only a weight of 0.2 during weekends.
- These alterations can be included with the requestee interruptibility rules (i.e., a given rule can indicate that a manager has a weight of 0.9 during work hours, but only 0.2 during weekends).
- the social interaction information and interruptibility estimate are passed to the interruptibility response creation handler 2070 in step 502 .
- This handler 2070 creates and returns the interruptibility estimate to the requestor.
- this response is an applet returned to the requestor's web client, the applet first simply displaying “yes” of “no” depending on whether the estimate value is greater than 0.5 (e.g., “yes” if the value is greater than or equal to 0.5, “no” if less than 0.5).
- the applet may also provide a button or the like functionality, e.g., labeled “details,” which if selected causes the applet to display the actual numeric value of the interruptibility estimate.
- interaction information which if selected displays a visualization of the requestee's current social interaction information (two embodiments of such visualizations described in detail with reference to FIGS. 6 and 7 ).
- a requestee may control which requestors are able to have such a visualization revealed.
- a graph such as those shown in FIGS. 6 and 7 may have a node representing the requestee in the center of the graph, with one or more other nodes representing one or more interactors with whom the requestee is currently interacting.
- the distance or length between the requestee node and an interactor node may represent the length of time elapsed since the interactor's last activity.
- Each node may provide indication of the associated user's role. For example, by hovering a mouse or another pointing device over the node, a role of the user or interactor associated with or represented by the hovered-over node may be displayed as a pop-up or the like.
- the response is provided as a babble-like social proxy such as those shown in FIG. 6 and FIG. 7 , wherein a large circle represents current interaction context.
- a plurality of smaller circles located in the circle represents a requestee and one or more interactors.
- one of the plurality of smaller circles represents the requestee
- the rest of the plurality of smaller circles represents one or more interactors in the current interaction context, social proxy such as a lecture, roundtable, or others.
- Each of the rest of the plurality of smaller circles representing one or more interactors in the current interaction context is associated with a number indicating importance of associated interactor to the requestee.
- Each of the rest of the plurality of smaller circles representing one or more interactors in the current interaction context is positioned in the circle so that its distance from the center of the circle indicates how recently the associated interactor was active in the current interaction context.
- the system and/or method of the present disclosure may enable the requestor to provide feedback information regarding the response. For instance, the requestor may be prompted to enter such feedback.
- the feedback information may include at least whether or not the requestee was actually interruptible.
- the requestee also may be enabled to provide feedback regarding the returned response, for instance, whether or not the requestee was actually interruptible.
- This feedback information may be also saved or stored, for instance, in the interruptibility awareness server database handler 2100 , and used in future interruptibility determinations for the requestee.
- the interruptibility awareness service of the present disclosure may use this feedback in future interruptibility determinations for the given requestee. For example, even though the service said the requestee was interruptible given a particular set of social interaction data, it turned out that the requestee was not interruptible. Given this information, the requestor (or the requestee) later indicates to the interruptibility awareness service (e.g., via a web interface) that it was the presence of one particular interactor (e.g., 3rd line manager) that was not given sufficient weight or importance.
- the interruptibility awareness service 1040 records this piece of information using the interruptibility awareness server database handler 2100 and uses it in subsequent interruptibility determinations for the given requestee.
- the system 1040 and/or method of the present disclosure may enable the requestor to get alerted when the requestee becomes available.
- the requestor may be enabled to indicate a threshold value of interruptibility for getting alerted.
- the threshold value may be stored.
- the threshold value may be set by the requestor specifying a threshold interruptibility level above which they should be notified, e.g., 70%.
- the system 1040 and/or method of the present disclosure may automatically and periodically recheck the requestee's interruptibility, and return the requestee's interruptibility when the threshold value is met.
- a follow up request may be automatically executed.
- the requestor may indicate that follow up request be made after the initial or previous request(s), for instance, providing the period or time for making the follow up request.
- the system 1040 and/or method of the present disclosure may then automatically recheck requestee's interruptibility according to the follow up request, and return the status to the requestor.
- the follow up request may include the specification of a delay.
- a default time delay may be used, after which a follow up request to determine the interruptibility status of the specified requestee is performed automatically.
- aspects of the present invention may be embodied as a system, method or computer program product. Accordingly, aspects of the present invention may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “circuit,” “module” or “system.” Furthermore, aspects of the present invention may take the form of a computer program product embodied in one or more computer readable medium(s) having computer readable program code embodied thereon.
- the computer readable medium may be a computer readable signal medium or a computer readable storage medium.
- a computer readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing.
- a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
- a computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof.
- a computer readable signal medium may be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
- Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
- Computer program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, Smalltalk, C++ or the like and conventional procedural programming languages, such as the “C” programming language or similar programming languages.
- the program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
- the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
- LAN local area network
- WAN wide area network
- Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
- These computer program instructions may also be stored in a computer readable medium that can direct a computer, other programmable data processing apparatus, or other devices to function in a particular manner, such that the instructions stored in the computer readable medium produce an article of manufacture including instructions which implement the function/act specified in the flowchart and/or block diagram block or blocks.
- the computer program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide processes for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
- each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s).
- the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
- the systems and methodologies of the present disclosure may be carried out or executed in a computer system that includes a processing unit 2 , which houses one or more processors and/or cores, memory and other systems components (not shown expressly in the drawing) that implement a computer processing system, or computer that may execute a computer program product.
- the computer program product may comprise media, for example a hard disk, a compact storage medium such as a compact disc, or other storage devices, which may be read by the processing unit 2 by any techniques known or will be known to the skilled artisan for providing the computer program product to the processing system for execution.
- the computer program product may comprise all the respective features enabling the implementation of the methodology described herein, and which—when loaded in a computer system—is able to carry out the methods.
- Computer program, software program, program, or software in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following: (a) conversion to another language, code or notation; and/or (b) reproduction in a different material form.
- the computer processing system that carries out the system and method of the present disclosure may also include a display device such as a monitor or display screen 4 for presenting output displays and providing a display through which the user may input data and interact with the processing system, for instance, in cooperation with input devices such as the keyboard 6 and mouse device 8 or pointing device.
- the computer processing system may be also connected or coupled to one or more peripheral devices such as the printer 10 , scanner (not shown), speaker, and any other devices, directly or via remote connections.
- the computer processing system may be connected or coupled to one or more other processing systems such as a server 10 , other remote computer processing system 14 , network storage devices 12 , via any one or more of a local Ethernet, WAN connection, Internet, etc.
- aspects of the present disclosure may be embodied as a program, software, or computer instructions embodied in a computer or machine usable or readable medium, which causes the computer or machine to perform the steps of the method when executed on the computer, processor, and/or machine.
- a program storage device readable by a machine, tangibly embodying a program of instructions executable by the machine to perform various functionalities and methods described in the present disclosure is also provided.
- the system and method of the present disclosure may be implemented and run on a general-purpose computer or special-purpose computer system.
- the computer system may be any type of known or will be known systems and may typically include a processor, memory device, a storage device, input/output devices, internal buses, and/or a communications interface for communicating with other computer systems in conjunction with communication hardware and software, etc.
- the terms “computer system” and “computer network” as may be used in the present application may include a variety of combinations of fixed and/or portable computer hardware, software, peripherals, and storage devices.
- the computer system may include a plurality of individual components that are networked or otherwise linked to perform collaboratively, or may include one or more stand-alone components.
- the hardware and software components of the computer system of the present application may include and may be included within fixed and portable devices such as desktop, laptop, server.
- a module may be a component of a device, software, program, or system that implements some “functionality”, which can be embodied as software, hardware, firmware, electronic circuitry, or etc.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computing Systems (AREA)
- Information Transfer Between Computers (AREA)
Abstract
Description
-
- with whom the requestee is physically or spatially;
- with whom the requestee is communicating;
- a weighted social network (as an example, a weighted social network indicates the strength of the relationship between the requestee and each of the other people in the network. The present disclosure also utilizes context sensitive weights, for example, the strength of the weights is also dependent on or may change based on the current context of the second user. For example, for the requestee who is talking to her boss, the relationship strength may have a weight of 0.9 during working hours, but can drop to 0.5 during nonworking hours, weight being measured from 0 to 1, 0 being the lowest level of weight and 1 being the highest level of weight in this example measurement);
- rules based on various factors such as the location, activity, speed of certain activities, for example, but not limited to, “do not interrupt if I am alone with upper management,” “OK to interrupt if I am with lots of others”, “do not interrupt if I am in washroom or upper management office”, and “no calls when driving or if driving speed is faster than 5 miles per hour (MPH)”;
- a social network weighting algorithm based on an organization chart (for example, the strength of the relationships is determined by the hierarchy of relationships in an organizational chart. For example, the relationship strength from boss to subordinate could be 0.4 while the same relationship in the opposite direction could be strength 0.9, strength being measured from 0 to 1, 0 being the lowest level and 1 being the highest level of 1 in this example measurement. The weighting that is used is that which is relative to the requestee. For example, if the requestee is the manager and a subordinate is one of the interactors, the value 0.4 is used. Alternatively, if the requestee is the subordinate and the manager is the one of the interactors, then the weight used would be 0.9. What matters is what matters to the requestee, i.e., the weight factor indicates the requestee's availability for interruption);
- history of the requestee's activities, for example, but not limited to, routine or known meeting times and places, the habitual time the requestee goes home or after work hours of the requestee, dinner time (for instance, during those times the requestee should not be interrupted, so the degree of interruptibility would be low, i.e., likely not interruptible);
- location, for example, interruptible if the requestee is standing on line in cafeteria, not interruptible if the requestee seems to be rushing somewhere;
- relationship structure, for example, that learned from employer organization chart;
- how many people are proximal to the requestee.
-
- Rule 1: If requestee is at home and with their family, then interruptibility=0.1
- Rule 2.1: If requestee is driving and requestor is significant other, the interruptibility=0.5
- Rule 2.2: If requestee is driving, then interruptibility=0.1
- Rule 3.1: If requestee is in lecture, and is lecturer, then interruptibility=0.1
- Rule 3.2 If requestee is in lecture but is not lecturer, the interruptibility=0.6
- Rule 4.1: If requestee is involved with others whose maximum relationship weight>=0.7, then interruptibility=0.1.
- Rule 4.2: If requestee is involved with others whose maximum relationship weight is less than that of requestor, then interruptibility=0.8.
- Rule 4.3: If requestee is involved with others whose maximum relationship weight is greater than that of requestor, then interruptibility=1.
-
- an
interruptibility request handler 2045, described in detail with references toFIGS. 4 and 5 ; - a social interaction
information gathering handler 2050, described in detail with reference toFIG. 5 ; - an
interruptibility determining handler 2060, described in detail with reference toFIG. 5 ; - an interruptibility
response creation handler 2070, described in detail with reference toFIG. 5 ; - an
interruptibility update handler 2080, described in detail with reference toFIG. 4 ; - an interruptibility
history retrieving handler 2090, described in detail with reference toFIG. 4 ; and - an interruptibility awareness
server database handler 2100.
- an
-
- altering the concluding interruptibility measure for a given rule, e.g., changing “interruptibility=0.5” to “interruptibility=0.7” for Rule 2.1;
- copying an existing rule into a new one with a changed context, e.g., creating rule 2.3 which is a copy of 2.2 except that the context is “on vacation” rather than “at home”;
- modifying a relationship specification in a given rule, e.g., modifying rule 4.1 so that “maximum relationship weight=0.9” rather than just “maximum relationship weight=0.7”;
- altering the relationship weight of a given user, e.g., changing the weight of the user given a weight of 1 in
FIG. 6 to 0.8.
-
- 0—not moving,
- 3—walking,
- 50—driving
- 250—flying
-
- work time (e.g., 9 AM-5 PM Monday-Friday),
- personal time (e.g., time during the week other than work time),
- holidays,
- meetings, and
- lectures/presentations
0.5+((3−1)*0.1)=
0.5+(2*0.1)=
0.5+0.2=
0.7
0.5−((5−3)*0.1)=
0.5−(2*0.1)=
0.5−0.2=
0.3
Claims (25)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/730,608 US8631119B2 (en) | 2010-03-24 | 2010-03-24 | Interruptibility awareness service |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/730,608 US8631119B2 (en) | 2010-03-24 | 2010-03-24 | Interruptibility awareness service |
Publications (2)
Publication Number | Publication Date |
---|---|
US20110238815A1 US20110238815A1 (en) | 2011-09-29 |
US8631119B2 true US8631119B2 (en) | 2014-01-14 |
Family
ID=44657608
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/730,608 Expired - Fee Related US8631119B2 (en) | 2010-03-24 | 2010-03-24 | Interruptibility awareness service |
Country Status (1)
Country | Link |
---|---|
US (1) | US8631119B2 (en) |
Cited By (15)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20120159347A1 (en) * | 2010-12-15 | 2012-06-21 | Microsoft Corporation | Meeting-specific state indicators |
US20130145293A1 (en) * | 2011-12-01 | 2013-06-06 | Avaya Inc. | Methods, apparatuses, and computer-readable media for providing availability metaphor(s) representing communications availability in an interactive map |
US20150106724A1 (en) * | 2013-10-11 | 2015-04-16 | Michael T. Donnelly | Method of visually indicating optimal communication times |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US9391947B1 (en) * | 2013-12-04 | 2016-07-12 | Google Inc. | Automatic delivery channel determination for notifications |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US9614920B1 (en) | 2013-12-04 | 2017-04-04 | Google Inc. | Context based group suggestion and creation |
US9628576B1 (en) | 2013-12-04 | 2017-04-18 | Google Inc. | Application and sharer specific recipient suggestions |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10033774B2 (en) | 2011-10-05 | 2018-07-24 | Microsoft Technology Licensing, Llc | Multi-user and multi-device collaboration |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US11010724B2 (en) | 2017-12-22 | 2021-05-18 | International Business Machines Corporation | Analyzing calendar entries |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8811587B2 (en) | 2012-04-11 | 2014-08-19 | International Business Machines Corporation | Selectively filtering incoming communications events in a communications device |
WO2014138010A1 (en) * | 2013-03-04 | 2014-09-12 | Yagi Corporation | Activity interruption management |
US20160026633A1 (en) * | 2014-07-24 | 2016-01-28 | Kelvin Inc. | Devices, systems and methods for rendering, updating and communicating relationship information |
US20180349828A1 (en) * | 2017-06-06 | 2018-12-06 | International Business Machines Corporation | People interruption management system and method based on task detection and physiological measures |
Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6944655B1 (en) | 2000-04-03 | 2005-09-13 | International Business Machines Corporation | User-defined online interaction method and device |
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US20070198696A1 (en) * | 2004-10-06 | 2007-08-23 | Morris Robert P | System and method for utilizing contact information, presence information and device activity |
US7424537B2 (en) | 2003-07-21 | 2008-09-09 | International Business Machines Corporation | Communication capability coupons |
US7664853B2 (en) * | 2004-07-15 | 2010-02-16 | International Business Machines Corporation | Automatically infering and updating an availability status of user |
US20100179998A1 (en) * | 2009-01-09 | 2010-07-15 | mxmd, inc. | Stateful server based social networking using mobile devices |
US8191005B2 (en) * | 2007-09-27 | 2012-05-29 | Rockwell Automation Technologies, Inc. | Dynamically generating visualizations in industrial automation environment as a function of context and state information |
-
2010
- 2010-03-24 US US12/730,608 patent/US8631119B2/en not_active Expired - Fee Related
Patent Citations (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US6944655B1 (en) | 2000-04-03 | 2005-09-13 | International Business Machines Corporation | User-defined online interaction method and device |
US7233933B2 (en) * | 2001-06-28 | 2007-06-19 | Microsoft Corporation | Methods and architecture for cross-device activity monitoring, reasoning, and visualization for providing status and forecasts of a users' presence and availability |
US7424537B2 (en) | 2003-07-21 | 2008-09-09 | International Business Machines Corporation | Communication capability coupons |
US7664853B2 (en) * | 2004-07-15 | 2010-02-16 | International Business Machines Corporation | Automatically infering and updating an availability status of user |
US20070198696A1 (en) * | 2004-10-06 | 2007-08-23 | Morris Robert P | System and method for utilizing contact information, presence information and device activity |
US8191005B2 (en) * | 2007-09-27 | 2012-05-29 | Rockwell Automation Technologies, Inc. | Dynamically generating visualizations in industrial automation environment as a function of context and state information |
US20100179998A1 (en) * | 2009-01-09 | 2010-07-15 | mxmd, inc. | Stateful server based social networking using mobile devices |
Non-Patent Citations (2)
Title |
---|
Erickson, T. et al, Socially Translucent Systems: Social Proxies, Persistent Conversation, and the Design of ‘Babble’, Human Factors in Computing Systems: The Proceedings of CHI '99, ACM Press, May 15-20, 1999. |
Erickson, T. et al, Socially Translucent Systems: Social Proxies, Persistent Conversation, and the Design of 'Babble', Human Factors in Computing Systems: The Proceedings of CHI '99, ACM Press, May 15-20, 1999. |
Cited By (19)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10423301B2 (en) | 2008-08-11 | 2019-09-24 | Microsoft Technology Licensing, Llc | Sections of a presentation having user-definable properties |
US10127524B2 (en) | 2009-05-26 | 2018-11-13 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US10699244B2 (en) | 2009-05-26 | 2020-06-30 | Microsoft Technology Licensing, Llc | Shared collaboration canvas |
US9383888B2 (en) | 2010-12-15 | 2016-07-05 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US11675471B2 (en) | 2010-12-15 | 2023-06-13 | Microsoft Technology Licensing, Llc | Optimized joint document review |
US20120159347A1 (en) * | 2010-12-15 | 2012-06-21 | Microsoft Corporation | Meeting-specific state indicators |
US9118612B2 (en) * | 2010-12-15 | 2015-08-25 | Microsoft Technology Licensing, Llc | Meeting-specific state indicators |
US9864612B2 (en) | 2010-12-23 | 2018-01-09 | Microsoft Technology Licensing, Llc | Techniques to customize a user interface for different displays |
US10033774B2 (en) | 2011-10-05 | 2018-07-24 | Microsoft Technology Licensing, Llc | Multi-user and multi-device collaboration |
US9544158B2 (en) | 2011-10-05 | 2017-01-10 | Microsoft Technology Licensing, Llc | Workspace collaboration via a wall-type computing device |
US9996241B2 (en) | 2011-10-11 | 2018-06-12 | Microsoft Technology Licensing, Llc | Interactive visualization of multiple software functionality content items |
US10198485B2 (en) | 2011-10-13 | 2019-02-05 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US11023482B2 (en) | 2011-10-13 | 2021-06-01 | Microsoft Technology Licensing, Llc | Authoring of data visualizations and maps |
US20130145293A1 (en) * | 2011-12-01 | 2013-06-06 | Avaya Inc. | Methods, apparatuses, and computer-readable media for providing availability metaphor(s) representing communications availability in an interactive map |
US20150106724A1 (en) * | 2013-10-11 | 2015-04-16 | Michael T. Donnelly | Method of visually indicating optimal communication times |
US9628576B1 (en) | 2013-12-04 | 2017-04-18 | Google Inc. | Application and sharer specific recipient suggestions |
US9614920B1 (en) | 2013-12-04 | 2017-04-04 | Google Inc. | Context based group suggestion and creation |
US9391947B1 (en) * | 2013-12-04 | 2016-07-12 | Google Inc. | Automatic delivery channel determination for notifications |
US11010724B2 (en) | 2017-12-22 | 2021-05-18 | International Business Machines Corporation | Analyzing calendar entries |
Also Published As
Publication number | Publication date |
---|---|
US20110238815A1 (en) | 2011-09-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US8631119B2 (en) | Interruptibility awareness service | |
KR102581622B1 (en) | Improve the efficiency of task management applications | |
US7483969B2 (en) | Managing presence based on relationship | |
US9495685B2 (en) | Generating and implementing A-lists to manage user relationships | |
CN110168537B (en) | Context and social distance aware fast active personnel card | |
US20090282104A1 (en) | System and method for indicating availability | |
US20080183814A1 (en) | Representing online presence for groups | |
US20100088140A1 (en) | Automated systems and methods for time management | |
US20230078487A1 (en) | Providing task assistance to a user | |
US20110004503A1 (en) | System and method for managing calendar events while preparing for time out-of-office | |
US8990189B2 (en) | Determining relevant contacts based on expertise and availability | |
US9659089B2 (en) | Prioritizing work and personal items from various data sources using a user profile | |
US8126443B2 (en) | Auxiliary output device | |
US20100179992A1 (en) | Generatiing Context Aware Data And Conversation's Mood Level To Determine The Best Method Of Communication | |
WO2018005204A1 (en) | Providing communication ranking scheme based on relationship graph | |
US20150281144A1 (en) | Cross-client subscription to groups | |
US20120303666A1 (en) | Method for restricting access to data based on current work | |
US20130218993A1 (en) | Contextual presence in collaborative systems | |
JP2009521037A (en) | How to manage tasks | |
US10652196B2 (en) | Relationship change alert | |
US20080052389A1 (en) | Method and apparatus for inferring the busy state of an instant messaging user | |
US20180165583A1 (en) | Controlling systems based on values inferred by a generative model | |
US20140258398A1 (en) | System and Method for Automatic Context Detection, Sharing, and Storage in Real-Time Communication Systems | |
US11379333B2 (en) | Managing notifications across ecosystems |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTERNATIONAL BUSINESS MACHINES CORPORATION, NEW Y Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:MALKIN, PETER K.;MARTINO, JACQUELYN A.;REEL/FRAME:024131/0361 Effective date: 20100318 |
|
FEPP | Fee payment procedure |
Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.) |
|
LAPS | Lapse for failure to pay maintenance fees |
Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.) |
|
STCH | Information on status: patent discontinuation |
Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362 |
|
FP | Lapsed due to failure to pay maintenance fee |
Effective date: 20180114 |