Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/30—Information retrieval; Database structures therefor; File system structures therefor of unstructured textual data
  • G06F16/34—Browsing; Visualisation therefor
  • G06F16/345—Summarisation for human users
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/01—Input arrangements or combined input and output arrangements for interaction between user and computer
  • G06F3/048—Interaction techniques based on graphical user interfaces [GUI]
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F3/00—Input arrangements for transferring data to be processed into a form capable of being handled by the computer; Output arrangements for transferring data from processing unit to output unit, e.g. interface arrangements
  • G06F3/14—Digital output to display device ; Cooperation and interconnection of the display device with other functional units

Definitions

• electronic mail typically serves as the primary source of communication among members of the enterprise as well as among members of the enterprise and persons outside the enterprise.
• electronic mail users receive tens or even hundreds of emails, they may become overwhelmed and have trouble prioritizing which electronic mail messages to read first or to otherwise process.
• users want to quickly find electronic mail conversations associated with tasks, questions, meeting proposals, and the like. Once a given electronic mail conversation or messaging thread is identified as having the desired information, the users want to jump directly to the most important parts of the given electronic mail or messaging item. The quicker users can find and read through appropriate electronic mail or messaging items, the easier it is for them to deal with electronic mail and messaging overload.
• Embodiments of the present invention solve the above and other problems by automatically summarizing electronic communication conversation threads.
• electronic mails, text messages, instant messages, tasks, questions and answers, meeting requests, calendar items, and the like are processed via a combination of natural language processing and heuristics.
• a text summary of the thread is generated to highlight the most important text in the thread.
• the text summary is presented to a user in a visual user interface to allow the user to quickly understand the significance or relevance of the thread.
• Fig. 1A illustrates a screen shot of an electronic user interface showing a conversation thread and showing a conversation summary automatically generated for the conversation thread.
• Fig. IB illustrates a screen shot of an electronic user interface for allowing a user to approved, reject or modify a candidate conversation thread summary.
• FIG. 2 illustrates a system architecture for automatically summarizing an electronic conversation thread.
• FIG. 3 illustrates a process flow for automatically summarizing an electronic conversation thread.
• Fig. 4 illustrates a system architecture for automatically summarizing an electronic conversation thread.
• FIG. 5 is a block diagram of a system including a computing device with which embodiments of the invention may be practiced.
• embodiments of the present invention are directed to automatically summarizing electronic conversation threads and to providing a summary of one or more electronic conversation thread items in a user interface component for review by one or more users associated with the conversation thread items.
• the following description refers to the accompanying drawings. Whenever possible, the same reference numbers are used in the drawings and the following description to refer to the same or similar elements. While embodiments of the invention may be described, modifications, adaptations, and other implementations are possible. For example, substitutions, additions, or modifications may be made to the elements illustrated in the drawings, and the methods described herein may be modified by substituting, reordering, or adding stages to the disclosed methods. Accordingly, the following detailed description does not limit the invention.
• program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types.
• program modules may be located in both local and remote memory storage devices.
• Figure 1A illustrates a screen shot of an electronic user interface showing a conversation thread and showing a conversation summary automatically generated for the conversation thread.
• an electronic mail conversation thread is displayed showing four sequential electronic mail messages comprising a conversation thread associated with some topic or issue.
• the example electronic mail items, illustrated in Figure 1A are for purposes of illustration only and are not limiting of other types of electronic communication items that may be grouped together as a conversation thread.
• the electronic communication items, illustrated in Figure 1A may be illustrative of a conversation thread comprised of various text messages displayed on a handheld computing device
• the communication items may be illustrative of a conversation thread comprised of communication items from a discussion board, for example, an Internet-based chat forum, and the like. That is, embodiments of the present invention may be utilized for providing a conversation summary for any type of electronic communication item, as described below.
• a given user may receive tens or hundreds of electronic mail messages, text messages, discussion forum messages, and the like over any given period of time, and each of the received messages may relate to a variety of different issues.
• electronic communications may include tasks that need to be performed by a user, meetings that need to be attended by a user, questions to a user, answers to a user, general information about some upcoming event, and the like.
• the user may perform a search function to retrieve all messages or mail items related to the given topic, for example, a particular project with which the user is associated.
• the user may still receive a large list of electronic mail items or other similar messages related to the searched topic.
• a conversation summary may be generated for a group of messages, for example, electronic mail items, associated with a given topic, and the conversation summary may be displayed in a user interface component to allow the user to quickly understand the nature and relevance of the conversation thread.
• an example conversation thread is displayed comprised of four electronic mail items.
• a user may have received tens or even hundreds of electronic mail items grouped together in a conversation thread as a result of a search on a given topic, for example, a search on a given project.
• each of the example electronic mail items displayed in the example electronic mail user interface is associated with a common project, "project AB.”
• project AB a common project
• information about each of the communication items contained in the communication thread is extracted, and a conversation summary is generated.
• a conversation summary user interface 130 may then be displayed to the user containing a brief summary of the conversation thread.
• a brief conversation summary of "Project AB schedule and documents" is illustrated in the user interface component 130.
• the conversation summary illustrated in the user interface component 130 may be automatically displayed to give the user a quick understanding of the nature and relevance of the communication thread. For example, the user may have sorted his/her electronic mail items based on a particular sender of the electronic mail items, or based on a particular time period in which electronic mail items are received, and the user may not realize the particular relevance of the resulting thread.
• the conversation summary displayed to the user in the user interface component 130 may be used to provide a conversation summary for the user to allow the user to know the relevance of the conversation thread items at a glance by quickly reviewing the conversation summary displayed to the user in the conversation summary user interface component 130.
• a candidate thread summary may be presented to a user for acceptance, rejection or modification.
• the user interface component 140 includes an example header of "Conversation Thread Summary" to indicate to the user that a candidate conversation thread summary is presented for review.
• a heading 145 such as "The following is a proposed conversation thread summary” may be provided above a text box or field 150 in which an indication candidate thread summary is displayed.
• a candidate summary of "Project AB documents and schedule” is displayed. If the user accepts the candidate summary, it will be used as the summary for the associated communication thread. If the user rejects the candidate summary, an alternate summary may be provided. And, if the user desires a different summary, the user may enter a replacement summary in the text box/field 155, and the user-entered replacement summary will be used as the summary for the associated communication thread.
• Figure 2 illustrates a system architecture of a conversation thread summarizing system 200 for automatically summarizing an electronic conversation thread.
• the conversation threads and metadata 202 component is illustrative of one or more memory storage areas at which conversation threads, messages comprising conversation threads and metadata items associated with conversation threads may be stored and from which information about the conversation threads may be obtained for use in generating summaries for conversation threads.
• the messages illustrated in Figures 1 may be stored in the repository 202, and metadata items, for example, identification of message senders, identification of message receivers, dates/times of message transmission and receipt, subject lines manually entered for any messages comprising the conversation threads, generated and stored topic titles for the conversation threads, relation between a given conversation thread or messages comprising the conversation thread and other messages or other conversation threads, and the like may be obtained.
• metadata items for example, identification of message senders, identification of message receivers, dates/times of message transmission and receipt, subject lines manually entered for any messages comprising the conversation threads, generated and stored topic titles for the conversation threads, relation between a given conversation thread or messages comprising the conversation thread and other messages or other conversation threads, and the like may be obtained.
• the conversation thread analyzer component 204 is illustrative an application or module operative to process received conversation thread items for generation of conversation thread summaries. Received conversation threads and metadata are analyzed and formatted as necessary for text processing described below. According to embodiments, the conversation thread analysis may be performed by a text parser operative to parse text contained in the retrieved conversation threads and associated metadata for processing the text into one or more text components (e.g., sentences and terms comprising the one or more sentences).
• a text parser operative to parse text contained in the retrieved conversation threads and associated metadata for processing the text into one or more text components (e.g., sentences and terms comprising the one or more sentences).
• the conversation thread analysis may include parsing the retrieved conversation threads and associated metadata according to the associated structured data language for processing the text as described herein.
• the conversation threads and associated metadata may be retrieved from an online source such as an Internet-based chat forum where the retrieved text may be formatted according to a formatting such as Hypertext Markup Language (HTML).
• the conversation thread analysis may be include formatting the retrieved conversation threads and associated metadata from such a source so that it may be processed for conversation topics as described herein.
• the text included in the messages comprising the conversation thread next may be processed for use in generating conversation thread summaries.
• a text processing application may be employed whereby the text is broken into one or more text components for determining whether the received/retrieved text may be contain terms that may be formed into a topic title for the conversation thread. Breaking the text into the one or more text components may include breaking the text into individual sentences followed by breaking the individual sentences into individual tokens, for example, words, numeric strings, etc.
• Such text processing is well known to those skilled in the art and may include breaking text portions into individual sentences and individual tokens according to known parameters. For example, punctuation marks and capitalization contained in a text portion may be utilized for determining the beginning and ending of a sentence. Spaces contained between portions of text may be utilized for determining breaks between individual tokens, for example, individual words, contained in individual sentences. Alphanumeric strings following known patterns, for example, five digit numbers associated with zip codes, may be utilized for identifying portions of text.
• initially identified sentences or sentence tokens may be passed to one or more recognizer programs for comparing initially identified sentences or tokens against databases of known sentences or tokens for further determining individual sentences or tokens.
• a word contained in a given sentence may be passed to a database to determine whether the word is a person's name, the name of a city, the name of a company, or whether a particular token is a recognized acronym, trade name, or the like.
• a variety of means may be employed for comparing sentences or tokens of sentences against known, words, or other alphanumeric strings for further identifying those text items.
• text processing may include breaking each of the mail messages into individual words that may be utilized in association with other properties obtained for the example mail items in automatically generating a summary for the thread.
• the feature extraction component 206 is illustrative of a collection of communication item features extracted from each of the communications comprising a given conversation thread with which a conversation thread summary will be generated for presenting to a user via the user interface component 130.
• various features and properties are associated with each item to provide helpful information in summarizing the relevance of the item relative to other items in the conversation thread.
• properties and features that may be extracted from each conversation thread item include identification of communication item sender, identification of communication item recipients, date/time of communication item transmission, date/time of transmission and receipt relative to other communication items, importance level associated with communication items, flags attached to communication items, content items attached to communication items, and the like.
• other features extracted from communication items comprising a conversation thread include substantive content items contained in communication thread items.
• tasks 208 may be embedded in conversation thread items and may have helpful information that may be used for generating a conversation thread summary.
• Meeting information for example, meeting requests 210 likewise may provide valuable information that may be used for generating a conversation thread summary, for example, a subject line associated with a meeting request that may include information that summarizes the reason for the meeting request.
• Questions and answers 212 embedded in text contained in electronic mail items, text messages, or other messaging similarly may be used to extract helpful information that may be used for summarizing a conversation thread comprised of various communication items.
• a variety of other communication item features 214 may also be utilized by the conversation thread summarizing system 200 for obtaining information for generating and presenting a conversation thread summary as illustrated in the user interface component 130.
• a first conversation thread may be comprised of electronic mail items
• information may be obtained by the system 200 from other sources, for example, a source of text messages that may include information useful in generating a summary for a conversation thread comprised of electronic mail items.
• sources of information for example, contacts lists, calendars of users identified in the conversation thread, tasks lists of users identified in the conversation thread, and the like may be utilized for gathering information that may be used for generating a conversation thread summary, as described herein.
• the selection/ranking component 216 is illustrative of a determination made by the system 200 as to the importance, weight, or relevance of the various features and properties extracted from the electronic communication items, as described above. For example, during the selection/ranking operation, duplicate features may be removed, features considered to be irrelevant, for example, an electronic mail item having no text associated with other electronic mail items in the conversation thread may be removed, outdated meeting requests that have been superseded by subsequent meeting requests may be removed, and more recent conversation items in an lengthy conversation thread may be raised to a higher relevance in the conversation thread, and features extract from those items may take on higher relevance in generating the conversation thread summary. For example, the timeline of the conversation thread based on send/receive dates and times may be used for initially aligning the conversation thread items for future extraction and analysis.
• the text summarization component 220 is illustrative of the generation of a conversation thread summary comprised of one or more communication item features, for example, words, phrases, numeric strings, and the like extracted from various communication thread items into a conversation thread summary that may be presented to users associated with the conversation thread.
• the user interface component 225 is illustrative of the presentation of the conversation thread summary to users of the conversation thread to allow the users a quick and easy understanding of the nature and relevance of the conversation thread they are reviewing.
• FIG. 3 illustrates a process flow for automatically summarizing an electronic conversation thread.
• the method 300 begins at start operation 305 and proceeds to operation 310 where conversation threads and associated metadata are obtained from various sources at which conversation thread items may be stored.
• electronic mail items and associated metadata may be stored at an electronic mail server that provides electronic mail storage for a large organization.
• electronic mail items that may be utilized for generating an electronic mail thread summary may be stored at a variety of different electronic mail servers or storage media located in a distributed computing environment where some items are located in one server, some items are located in another server, and so on.
• text messages that may be utilized for generating a conversation thread summary may be distributed across storage servers operated by various communications services providers responsible for providing text messaging services to various users.
• the conversation threads and metadata may be retrieved from Internet-based chat services, where the messages, message content, and message metadata may be stored in one or across numerous storage services systems.
• operation 310 is performed after a user conducts some operation for assembling a given conversation thread for which a conversation thread summary is to be generated. For example, if a user is associated with a project team that has sent and received a variety of electronic mail messages concerning a given aspect of the project, the user may desire to search for all electronic mails associated with that project aspect. Once the user enters some type of search criteria, the user may receive a great number of electronic mail items having some relevance to the desired aspect of the project. For example, the listing of electronic mail messages illustrated in Figure 1 may be displayed to the user as the result of a search on the "project AB" identified in each of the example electronic mail items.
• the user may be forced to read through numerous electronic mail items, some of which may be of little relevance to the user to determine a more particular relevance or nature of the communication thread.
• the communication thread identified by the user's search that results in a collection of communication items comprising the thread is retrieved for analysis and generation of the conversation thread summary, as described below.
• text and metadata retrieved from each of the communication items contained in the conversation thread are analyzed, formatted and processed into individual terms, e.g., words, phrases, numeric strings, etc. as described above with reference to the conversation thread analyzer 204.
• the individual terms extracted from the thread items may be used to construct a conversation summary for the thread.
• features from the communication items comprising the retrieved communication thread are extracted for use in generating a communication thread summary.
• feature extraction at operation 320 includes extracting terms and information from the processed text and metadata for each of the communication items that may be useful in determining the relationship between the communication items and then ultimately generating a communication thread summary.
• extracted features from the communication items and associated metadata may be stored temporarily for selection and ranking.
• the extracted features from the communication items and associated metadata are selected and ranked for use in the generation of the conversation thread summary.
• selection of one or more features may include discarding certain features that are considered duplicative or irrelevant. For example, if the same terminology is used in two consecutive communication items, the terminology from one of the communication items may be discarded. For another example, if a communication item comprising a communication thread includes no terms or metadata in common with other communication items, then the communication item and its extracted features may be discarded. Once a set of features is selected, the selected features may be ranked in order of importance. For example, more recent communication items may be ranked above older communication items. Out-of-date meeting requests and information contained therein may be discarded in lieu of more up-to-date meeting requests and information contained therein.
• a summarization of text features extracted from the various communication items comprising the communication thread is performed. Based on the selection and ranking performed at operation 325, a grouping of key words or other terms extracted from the conversation thread may be generated into a conversation thread summary as illustrated above in Figure 1. For example, referring back to Figure 1 , each of the example electronic mail items includes the terms “project” and "AB.” In addition, the term “documents” appears in close proximity to the terms “project” and "AB.” Finally, a number of the electronic mail items include scheduling features that may be associated with task items and calendar items extracted by the system 200 when the electronic mail thread was assembled. As a result, a text summary of "project AB schedule and documents" is generated for the example conversation thread.
• the extracted and presented conversation thread summary may include the use of a set of sentences or phrases extracted from analyzed electronic mail items, text messages, task items, calendar items and the like as a summary of the associated thread. That is, the presented summary in the user interface component 130 may include one or more sentences extracted from a conversation thread, one or more tasks extracted from a tasks storage, one or more meeting schedule items extracted from a calendar application in association with a conversation thread, answers to questions posed in a conversation thread, or combinations of these items that all occur in or are associated with a given conversation thread.
• a summary presented in the user interface component 130 may include a couple of thread sentences, a task item and a calendar item as a summary of the associated thread.
• the initially generated conversation thread summary may be presented to the user prior to establishment of the initially generated summary as the final conversation thread summary for the example conversation thread.
• the presentation of the candidate conversation thread summary may be presented to the user in a user interface component, as illustrated above in Figure IB. If a user accepts the presented candidate conversation thread, then the candidate conversation thread will be stored and presented as the final conversation thread summary.
• the user may be provided with a field 155, as illustrated above in Figure IB to allow the user to enter a preferred conversation thread summary that may replace the conversation thread summary recommended by the system 200.
• the candidate conversation thread summary generated by the system 200 may be automatically presented to users of the conversation thread in the user interface component 130 illustrated above in Figure 1A without user interaction.
• the conversation summary generated by the system 200, or the conversation summary modified or accepted by the user at operation 330 is displayed to the user in the conversation summary user interface component 130, as illustrated and described above with reference to Figure 1A.
• the conversation thread summary generation method may be performed by the system 200 each time a conversation thread is obtained by a given user, or a previously generated conversation thread summary may be obtained from storage and may be presented to the user.
• the method 300 may be re-accomplished to account for additional conversation item features that may have been added to the conversation thread by the addition of the new conversation item.
• the method ends at operation 340.
• FIG. 4 illustrates a system architecture for providing conversation thread summaries to various client devices after generation as described above.
• an automatic conversation thread summary system 420 may generate thread summaries from conversation threads and metadata retrieved using a variety of communication channels and stores. Information and features helpful to generating conversation thread summaries may also be stored in different communication channels or other storage types. For example, conversation thread communication items, metadata or feature information may be stored using directory services 422, web portals 424, mailbox services 426, instant messaging stores 428 and social networking sites 430.
• the automatic conversation thread summary system 420 may use any of these types of systems or the like to store conversation thread summaries in a thread summary store 416.
• a server 412 may provide conversation thread summaries to clients.
• server 412 may be a web server providing thread summaries over the web.
• Server 412 may provide online thread summaries over the web to clients through a network 407.
• clients that may obtain thread summaries include computing device 401 , which may include any general purpose personal computer, a tablet computing device 403 and/or mobile computing device 405 which may include smart phones. Any of these devices may obtain thread summaries from the thread summary store 416.
• embodiments of the invention may be implemented via local and remote computing and data storage systems, including the systems illustrated and described with reference to Figures 1A, IB, 2, 3 and 4.
• the aforementioned memory storage and processing unit may be implemented in a computing device, such as computing device 500 of Figure 5.
• the computing device may be in the form of a personal computer, server computer, handheld computer, smart phone, tablet or slate device, or any other device capable of containing and operating the computing components and functionality described herein.
• the computing device components described below may operate as a computing system printed on a programmable chip. Any suitable combination of hardware, software, or firmware may be used to implement the memory storage and processing unit.
• the memory storage and processing unit may be implemented with computing device 500 or any other computing devices 518, in combination with computing device 500, wherein functionality may be brought together over a network in a distributed computing environment, for example, an intranet or the Internet, to perform the functions as described herein.
• the aforementioned system, device, and processors are examples and other systems, devices, and processors may comprise the aforementioned memory storage and processing unit, consistent with embodiments of the invention.
• computing device 500 may comprise operating environment 100 as described above.
• a system consistent with embodiments of the invention may include a computing device, such as computing device 500.
• computing device 500 may include at least one processing unit 502 and a system memory 504.
• system memory 504 may comprise, but is not limited to, volatile (e.g. random access memory (RAM)), non-volatile (e.g. read-only memory (ROM)), flash memory, or any combination.
• System memory 504 may include operating system 505, one or more programming modules 506, and may include the conversation topic detection, generation and storage system 200 having sufficient computer-executable instructions, which when executed, performs functionalities as described herein. Operating system 505, for example, may be suitable for controlling computing device 500's operation.
• embodiments of the invention may be practiced in conjunction with a graphics library, other operating systems, or any other application program and is not limited to any particular application or system. This basic configuration is illustrated in Figure 5 by those components within a dashed line 508.
• Computing device 500 may have additional features or functionality.
• computing device 500 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape.
• additional storage is illustrated in Figure 5 by a removable storage 509 and a non-removable storage 510.
• Computing device 500 may also contain a communication connection 516 that may allow device 500 to communicate with other computing devices 518, such as over a network in a distributed computing environment, for example, an intranet or the Internet.
• Communication connection 516 is one example of communication media.
• program modules 506 may include the automatic conversation thread summary generation system 200, 420 which may be program modules containing sufficient computer-executable instructions, which when executed, performs functionalities as described herein.
• processing unit 502 may perform other processes.
• Other programming modules that may be used in accordance with embodiments of the present invention may include electronic mail and contacts applications, word processing applications, spreadsheet applications, database applications, slide presentation applications, drawing or computer-aided application programs, etc.
• program modules may include routines, programs, components, data structures, and other types of structures that may perform particular tasks or that may implement particular abstract data types.
• embodiments of the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor- based or programmable consumer electronics, minicomputers, mainframe computers, and the like.
• Embodiments of the invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network.
• program modules may be located in both local and remote memory storage devices.
• embodiments of the invention may be practiced in an electrical circuit comprising discrete electronic elements, packaged or integrated electronic chips containing logic gates, a circuit utilizing a microprocessor, or on a single chip containing electronic elements or microprocessors.
• Embodiments of the invention may also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies.
• embodiments of the invention may be practiced within a general purpose computer or in any other circuits or systems.
• Embodiments of the invention may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media.
• the computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process.
• the present invention may be embodied in hardware and/or in software (including firmware, resident software, micro-code, etc.).
• embodiments of the present invention may take the form of a computer program product on a computer-usable or computer- readable storage medium having computer-usable or computer-readable program code embodied in the medium for use by or in connection with an instruction execution system.
• a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device.
• Computer readable media may include computer storage media.
• Computer storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information, such as computer readable instructions, data structures, program modules, or other data.
• System memory 504, removable storage 509, and non-removable storage 510 are all computer storage media examples (i.e., memory storage.)
• Computer storage media may include, but is not limited to, RAM, ROM, electrically erasable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store information and which can be accessed by computing device 500. Any such computer storage media may be part of device 500.
• Computing device 500 may also have input device(s) 512 such as a keyboard, a mouse, a pen, a sound input device, a touch input device, etc.
• Output device(s) 514 such as a display, speakers, a printer, etc. may also be included. The aforementioned devices are examples and others may be used.
• Computer readable media may also include communication media.
• Communication media may be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media.
• modulated data signal may describe a signal that has one or more characteristics set or changed in such a manner as to encode information in the signal.
• communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, radio frequency (RF), infrared, and other wireless media.
• RF radio frequency
• Embodiments of the present invention are described above with reference to block diagrams and/or operational illustrations of methods, systems, and computer program products according to embodiments of the invention.
• the functions/acts noted in the blocks may occur out of the order as shown in any flowchart.
• 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/acts involved.

Landscapes

• Engineering & Computer Science (AREA)
• Theoretical Computer Science (AREA)
• General Engineering & Computer Science (AREA)
• Physics & Mathematics (AREA)
• General Physics & Mathematics (AREA)
• Data Mining & Analysis (AREA)
• Databases & Information Systems (AREA)
• Human Computer Interaction (AREA)
• Information Transfer Between Computers (AREA)
• Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
• User Interface Of Digital Computer (AREA)

Priority Applications (9)

Applications Claiming Priority (2)

Publications (2)

Family

ID=47391656

Family Applications (1)

Country Status (11)

Cited By (10)

Families Citing this family (64)

Family Cites Families (51)

• 2011
  • 2011-06-28 US US13/170,787 patent/US9116984B2/en active Active
• 2012
  • 2012-06-22 CN CN201280031889.9A patent/CN103620539B/zh active Active
  • 2012-06-22 JP JP2014518876A patent/JP2014524089A/ja active Pending
  • 2012-06-22 RU RU2013158714A patent/RU2621005C2/ru active
  • 2012-06-22 CN CN201610312461.1A patent/CN106021387B/zh active Active
  • 2012-06-22 WO PCT/US2012/043848 patent/WO2013003240A2/en active Application Filing
  • 2012-06-22 CA CA2840485A patent/CA2840485C/en active Active
  • 2012-06-22 MX MX2013015150A patent/MX2013015150A/es unknown
  • 2012-06-22 EP EP20120805128 patent/EP2727012A4/en not_active Ceased
  • 2012-06-22 KR KR1020137034645A patent/KR101960115B1/ko active IP Right Grant
  • 2012-06-22 AU AU2012275628A patent/AU2012275628B2/en active Active
  • 2012-06-22 BR BR112013032004A patent/BR112013032004A2/pt not_active Application Discontinuation

Non-Patent Citations (4)

Also Published As

Similar Documents

Legal Events