CA2440291A1 - Method and apparatus for annotating a document with audio comments - Google Patents
Method and apparatus for annotating a document with audio comments Download PDFInfo
- Publication number
- CA2440291A1 CA2440291A1 CA002440291A CA2440291A CA2440291A1 CA 2440291 A1 CA2440291 A1 CA 2440291A1 CA 002440291 A CA002440291 A CA 002440291A CA 2440291 A CA2440291 A CA 2440291A CA 2440291 A1 CA2440291 A1 CA 2440291A1
- Authority
- CA
- Canada
- Prior art keywords
- document
- audio
- user
- file
- comment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/169—Annotation, e.g. comment data or footnotes
-
- 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/16—Sound input; Sound output
- G06F3/165—Management of the audio stream, e.g. setting of volume, audio stream path
-
- G—PHYSICS
- G10—MUSICAL INSTRUMENTS; ACOUSTICS
- G10L—SPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
- G10L13/00—Speech synthesis; Text to speech systems
-
- G—PHYSICS
- G10—MUSICAL INSTRUMENTS; ACOUSTICS
- G10L—SPEECH ANALYSIS OR SYNTHESIS; SPEECH RECOGNITION; SPEECH OR VOICE PROCESSING; SPEECH OR AUDIO CODING OR DECODING
- G10L15/00—Speech recognition
- G10L15/26—Speech to text systems
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
Abstract
Apparatus and methods allowing users to review and add annotations (512,910) to a digital document (305,306). The document is presented to the user via an audio output device (310) and provides the user with the ability to annotate the document by speaking into an audio input device (310). The user may access the document from multiple locations using multiple types of devices.
Description
METHOD AND APPARATUS FOR
ANNOTATING A DOCUMENT
FIELD OF THE INVENTION
This invention relates to the field of computer technology. More specifically, the invention relates to a method and apparatus for performing document annotation.
Portions of the disclosure of this patent document contain material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office file or records, but otherwise reserves all copyrights whatsoever.
BACKGROUND
Writing a screenplay, a book, or any other document is a process that usually requires a significant time investment from the people responsible for producing such a document. The quality and value of the document that is ultimately generated typically increases when multiple people have had the opportunity to review and comment on the document. As a result, the process of reviewing documents is tightly integrated into many aspects of modern business.
The first draft of a document often contains mistakes or other problems that should be corrected. These issues are typically resolved during the review process. Anybody that can provide valuable input about the document may contribute to the review process. During this process, the reviewer may, for example, wish to provide input about the contents of the document by giving comments, feedback, and/or making changes to the text of the document. In
ANNOTATING A DOCUMENT
FIELD OF THE INVENTION
This invention relates to the field of computer technology. More specifically, the invention relates to a method and apparatus for performing document annotation.
Portions of the disclosure of this patent document contain material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure as it appears in the Patent and Trademark Office file or records, but otherwise reserves all copyrights whatsoever.
BACKGROUND
Writing a screenplay, a book, or any other document is a process that usually requires a significant time investment from the people responsible for producing such a document. The quality and value of the document that is ultimately generated typically increases when multiple people have had the opportunity to review and comment on the document. As a result, the process of reviewing documents is tightly integrated into many aspects of modern business.
The first draft of a document often contains mistakes or other problems that should be corrected. These issues are typically resolved during the review process. Anybody that can provide valuable input about the document may contribute to the review process. During this process, the reviewer may, for example, wish to provide input about the contents of the document by giving comments, feedback, and/or making changes to the text of the document. In
2 some instances entire portions of the document are deleted or rewritten. In other instances, portions of the document are simply critiqued. The document that is ultimately produced when the review process is complete may be very different from the document that existed in first draft form. Thus, the review process is a valuable step in the process of finalizing a document.
Since the people who are largely responsible for reviewing documents often have a schedule that keeps them moving from one meeting to another, there is a need for a device that simplifies the review process by allowing a reviewer to interact with the document while on the move. For example, current systems do not allow the reviewer to access and verbally comment on a document from multiple locations. A reviewer cannot use current systems to begin reviewing a document from a Bell phone in the reviewer's car, continue to review the same document from a home PC, and finish reviewing the document from a pay phone.
Current systems also do not provide the reviewer with an intuitive way to verbally interact with the document. Most systems for reviewing documents are text-based and do not have the ability to read the document to the reviewer so that the reviewer can hear the contents of the document. Moreover, these text-based systems do not provide a way to record verbal comments provided by the reviewer while the document is being read. These limitations become particularly evident when the document being reviewed is a movie script or some other kind of document where it is important for the reviewer to hear the words contained in the document.
So that the reader can better understand the advances in the art made by , embodiments of the invention, a brief discussion of several current systems for editing and/or commenting about a document follows. Some text-based
Since the people who are largely responsible for reviewing documents often have a schedule that keeps them moving from one meeting to another, there is a need for a device that simplifies the review process by allowing a reviewer to interact with the document while on the move. For example, current systems do not allow the reviewer to access and verbally comment on a document from multiple locations. A reviewer cannot use current systems to begin reviewing a document from a Bell phone in the reviewer's car, continue to review the same document from a home PC, and finish reviewing the document from a pay phone.
Current systems also do not provide the reviewer with an intuitive way to verbally interact with the document. Most systems for reviewing documents are text-based and do not have the ability to read the document to the reviewer so that the reviewer can hear the contents of the document. Moreover, these text-based systems do not provide a way to record verbal comments provided by the reviewer while the document is being read. These limitations become particularly evident when the document being reviewed is a movie script or some other kind of document where it is important for the reviewer to hear the words contained in the document.
So that the reader can better understand the advances in the art made by , embodiments of the invention, a brief discussion of several current systems for editing and/or commenting about a document follows. Some text-based
3 PCT/US02/07222 systems (e.g., word processors) provide a way for reviewers to comment on a document by manually typing an entry into a comment field. Comments can also be recorded in a sound file and manually associated with the document.
However, this process is laborious and does not provide the reviewer with a way to easily hear and comment upon a document.
Some word processing programs (e.g., Microsoft WordTM) have a built in mechanism for inserting comments into a document. This mechanism does not provide reviewers with a way to listen to audio output associated with the contents of a text document. Nor do such programs allow the reviewer to provide input about the document by speaking to the word processing program. However, such word processing programs do supply reviewers with a way to manually insert typed comments into a text document.
Figure 1 illustrates a word processing program configured to insert comments into a document. Word processing program 100 contains an instance of document 112 containing text about which the user of the program may comment. If the user wishes to comment on sentence 104, the user may insert comments into the document by utilizing a pointing device (e.g., a mouse) to highlight the text that is to be associated with the comment. Once the text is selected the user inputs the comments via an input device such as a computer keyboard. The comments are typically entered in a comment region 102 that consists of a list of one or more comments associated with document 112.
The user who authored the comment is identified in an abbreviated manner in a location related to the comment. User ID 110, for example, indicates that a user having a username (e.g.,userl: jake_smyth) is associated with comment 108. Comment 108 may exist as a textual comment or as an audio file.
If a verbal comment was recorded and associated with document 112, the user
However, this process is laborious and does not provide the reviewer with a way to easily hear and comment upon a document.
Some word processing programs (e.g., Microsoft WordTM) have a built in mechanism for inserting comments into a document. This mechanism does not provide reviewers with a way to listen to audio output associated with the contents of a text document. Nor do such programs allow the reviewer to provide input about the document by speaking to the word processing program. However, such word processing programs do supply reviewers with a way to manually insert typed comments into a text document.
Figure 1 illustrates a word processing program configured to insert comments into a document. Word processing program 100 contains an instance of document 112 containing text about which the user of the program may comment. If the user wishes to comment on sentence 104, the user may insert comments into the document by utilizing a pointing device (e.g., a mouse) to highlight the text that is to be associated with the comment. Once the text is selected the user inputs the comments via an input device such as a computer keyboard. The comments are typically entered in a comment region 102 that consists of a list of one or more comments associated with document 112.
The user who authored the comment is identified in an abbreviated manner in a location related to the comment. User ID 110, for example, indicates that a user having a username (e.g.,userl: jake_smyth) is associated with comment 108. Comment 108 may exist as a textual comment or as an audio file.
If a verbal comment was recorded and associated with document 112, the user
4 may elect to listen to the verbal comment by selecting icon 106. Upon selection of icon 106, audio player 112 plays the audio file containing the stored version of the verbal comment. In some word processing programs, the text that is related to comment 104 is highlighted with a color that indicates a comment was made about that portion of text.
Although word processing programs provide a built-in mechanism for typing comments into a document such programs do not provide a way to insert comments into the document from a place other than the program itself.
For example, a user cannot comment about the document unless the user is utilizing the word processing program and has a copy of the document on-hand.
Thus, there is a need for a method and apparatus that complements existing word processing programs by providing users with alternative avenues for editing or commenting on a document while on the move. Moreover, such word processing program lack an efficient way to store and easily retrieve documents from any location once annotations are made to the document. For example, existing systems do not have a way to that allows the user to continuously access and make comments to the document.
Another example, of an existing system for editing documents can be found in Boys, et al. (U.S. Patent Number 5,875,448). The Boys, et al. patent . describes an audio editor that operates on a file that may contain text and voice data in separate regions. The audio editor described in Bovs et al., provides functions for entering voice data, and also for editing the entered voice data.
Once such voice data is entered and edited that data is passed to an individual for conversion into a text file. Files can be uploaded from the audio editor to a PC
application for converting the file entirely to text, providing a system wherein all variable entry and editing can be done verbally, and conversion to text is left as a final chore.
Figure 2 illustrates a representation of a data file as used in the audio editor described in Boys, et al.. Data file 200 is created by the audio editor or some other digital device and downloaded to the audio editor. The file typically consists of digitally recorded voice data entered via a microphone or some other
Although word processing programs provide a built-in mechanism for typing comments into a document such programs do not provide a way to insert comments into the document from a place other than the program itself.
For example, a user cannot comment about the document unless the user is utilizing the word processing program and has a copy of the document on-hand.
Thus, there is a need for a method and apparatus that complements existing word processing programs by providing users with alternative avenues for editing or commenting on a document while on the move. Moreover, such word processing program lack an efficient way to store and easily retrieve documents from any location once annotations are made to the document. For example, existing systems do not have a way to that allows the user to continuously access and make comments to the document.
Another example, of an existing system for editing documents can be found in Boys, et al. (U.S. Patent Number 5,875,448). The Boys, et al. patent . describes an audio editor that operates on a file that may contain text and voice data in separate regions. The audio editor described in Bovs et al., provides functions for entering voice data, and also for editing the entered voice data.
Once such voice data is entered and edited that data is passed to an individual for conversion into a text file. Files can be uploaded from the audio editor to a PC
application for converting the file entirely to text, providing a system wherein all variable entry and editing can be done verbally, and conversion to text is left as a final chore.
Figure 2 illustrates a representation of a data file as used in the audio editor described in Boys, et al.. Data file 200 is created by the audio editor or some other digital device and downloaded to the audio editor. The file typically consists of digitally recorded voice data entered via a microphone or some other
5 audio input. However, in some instances the data file supplied to the audio editor may have machine operable text code, as in a PC word processor file, and other portions that are digitally recorded voice. The dual nature of the data file is important because the final desirable form of a file is machine-readable code (e.g., a finished word-processor document). Thus, the nature of data file 200 is a formatted word processor file having sections wherein data may be added and edited as digitally recorded voice. This formatted file 200 contains sections such as headers, footers, subheads, (e.g., elements 202, 204, 206, 208, 210, 212, and 213) that cannot be edited by the audio editor because they are machine operable-text code. Bob, et al. does contemplate the use of text-reading software to render elements 202, 204, 206, 208, 210, and 212 as synthetic speech. The text-reading software provides users with a way to review all parts of the file 200, but the user "may only enter, add to, and edit the digitally-recorded audio portions"
(See Bobs, et al., Column 9, lines 4-5). In between elements 202, 204, 206, 208, 210, and 212 file 200 contains portions 59, 61, 63, 65, 67, and 69. These portions are reserved for digitally recorded voice. Thus, file 200 may contain both text portions (referred to as machine-operable text code) and digitally recorded audio portions. When the user selects a play button both the text portion and the audio portion are vocalized. The user may then forward or rewind the file to hear different portions vocalized. Thus, the audio editor provides users a way to create and edit a file before converting the file entirely to machine-operable Bode (e.g., text).
(See Bobs, et al., Column 9, lines 4-5). In between elements 202, 204, 206, 208, 210, and 212 file 200 contains portions 59, 61, 63, 65, 67, and 69. These portions are reserved for digitally recorded voice. Thus, file 200 may contain both text portions (referred to as machine-operable text code) and digitally recorded audio portions. When the user selects a play button both the text portion and the audio portion are vocalized. The user may then forward or rewind the file to hear different portions vocalized. Thus, the audio editor provides users a way to create and edit a file before converting the file entirely to machine-operable Bode (e.g., text).
6 Once the user has finished creating the file it may be uploaded to a host computer such as a PC and converted into text. An operator does the final conversion using a word processing application. The word processing application displays file 200 in a manner that shows the text and vocal portions of the file. The operator may listen to the vocalized portions by selecting such portions with a mouse or other pointing device. The operator may then enter the vocalized data as text as it is recited.
There are multiple problems associated with the approach utilized in the Boars et al. reference. Boys et al.,, for example, does not provide a mechanism for verbally editing all aspects of the file (e.g., elements 200-213) cannot be edited.
Boys et al. discloses a mechanism for editing the audio portions of file 200, but does not provide a way for the user to edit or comment on text elements in the file. bouts et al. is directed to creating and subseejuently editing audio files that are inserted into a template file containing elements that cannot be edited.
Thus, Bo~TS, et al. limits the operations of the user by restricting the elements that can be edited. Moreover, Boys et al. does not distinguish between vocalized input that is intended to be a comment or annotations. Rather Bo~~s, et al. provides a way to add or makes changes to a document, but the user cannot flag certain portions of input as general comments. Another limitation inherent in the design utilized in Boys et al. is that the audio portions of the file must be manually converted into text via an operator. bouts et al. does not have a mechanism in place for automatically converting or aiding the user in the editing process. Boys et al. also lacks a mechanism for selectively listening to comments made by a particular user. In Bob si et al.,, if two people edit the same document, the system does not distinguish between the parties and provide users a way to selectively listen to the comments of one party or another. Rather, the audio editor is intended to aid a single user in the creation and editing of a single file.
There are multiple problems associated with the approach utilized in the Boars et al. reference. Boys et al.,, for example, does not provide a mechanism for verbally editing all aspects of the file (e.g., elements 200-213) cannot be edited.
Boys et al. discloses a mechanism for editing the audio portions of file 200, but does not provide a way for the user to edit or comment on text elements in the file. bouts et al. is directed to creating and subseejuently editing audio files that are inserted into a template file containing elements that cannot be edited.
Thus, Bo~TS, et al. limits the operations of the user by restricting the elements that can be edited. Moreover, Boys et al. does not distinguish between vocalized input that is intended to be a comment or annotations. Rather Bo~~s, et al. provides a way to add or makes changes to a document, but the user cannot flag certain portions of input as general comments. Another limitation inherent in the design utilized in Boys et al. is that the audio portions of the file must be manually converted into text via an operator. bouts et al. does not have a mechanism in place for automatically converting or aiding the user in the editing process. Boys et al. also lacks a mechanism for selectively listening to comments made by a particular user. In Bob si et al.,, if two people edit the same document, the system does not distinguish between the parties and provide users a way to selectively listen to the comments of one party or another. Rather, the audio editor is intended to aid a single user in the creation and editing of a single file.
7 The audio editor is used to generate documents not comment on an existing document without necessarily modifying the contents of the document itself. A
further limitation in current systems is that such system are not directed to providing documents to users in any location. Users of the audio editor described in'Bovs et al. cannot, for example, obtain a document from a remote location without having an instance of the document on-hand.
Thus, there is a need for a system that solve the limitations inherent in the prior art by allowing the user to listen to a document and verbally comment on the contents of the document without necessarily changing the document.
' Moreover users could benefit from a system that aids the user responsible (e.g., the typist or data entry person) for the conversion process. In some instances there is also a need for a system that allows user to selectively listen to comments made by a certain individual without having to review all comments that were made about the document.
In the foregoing discussion about current systems, the problems and limitations set forth as existent in the prior art are provided for exemplarily purposes. It should be clear to one of ordinary skill in the art that these problems also exist in other contexts or professions and that the invention may apply to situations other than the ones described herein.
SUMMARY OF THE INVENTION
An embodiment of the invention describes a system that enables people to add verbal annotations (i.e. add comments) to a digital document such as a movie script, book, or any other type of document. This device provides the reviewer with an improved way to interact and comment upon documents while on the move. For example, the reviewer may utilize an embodiment of the invention to access and verbally comment on a document from multiple locations. Thus, the invention provides a system that enables the reviewer to begin reviewing a document from a Bell phone, continue to review the same document from a home PC, and finish reviewing the document from a pay phone. An embodiment of the invention also provides the reviewer with an intuitive way to verbally interact with documents. The system can read documents (e.g., via a text-to-speech engine) so that the reviewer can hear the contents of the document. The system also provides the reviewer with a way to record verbal comments about the document. When a comment is supplied the comment becomes associated with the location in the document where the comment was provided. If, for example, the reviewer makes a comment about a particular passage of text, the comment becomes associated with the passage of text the comment is related to.
The device that embodies the invention uses an audio output mechanism to play the document to the user. At any time during playback the user may provide a comment by selecting an annotate button and simply speaking to the device. In turn, the device records the user's comment and associates it with the location in the document where the comment was given. If the document is replayed after a user provides comments, the device plays back the document and the comments via the audio output mechanism. This way the user can hear the document and any comments that were made about the document.
Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a regular telephone, a personal computer, or any other computational system. Each of the devices that embody the invention may access the document (e.g., via a data storage medium or computer network) so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish reviewing the document from home using a regular phone line.
One or more embodiments of the invention comprises a method and apparatus that enables users to add any number of annotations (i.e. add comments) to a digital document such as movie scripts, books, etc. from anywhere in the world. Thus, an embodiment of the invention enables users to hear and comment on a document from one or more locations. Any type of computational device may be configured to embody the invention and thereby provide the user with an interface to comment on or review comments about a particular document. Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a regular telephone (e.g., POTS), a personal computer (e.g., a PC or a PDA), or any other system capable of accepting audio input and output. Each of the devices that embody the invention may access the document so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish reviewing the document from home using a regular phone line.
Multiple types of devices can be modified to incorporate aspects of the 5 invention. For example, an annotation device (e.g., an apparatus) having a processor and memory containing a text document may be coupled with a document processing engine that is configured to obtain the text document from memory and convert a portion of the document to an audio file that can be played to a user. If a user indicates a desire to hear the content of a document 10 the annotation device uses an audi~ output mechanism to play the audio file to the user. If the user provides a comment to the annotation device an audio input device configured to obtain such verbalized comments from the user stores the comment as an audio comment file. The annotation device passes the audio comment file to an annotator that is configured to associate the audio comment file with a location in the text document that corresponds to the audio file playing when the first user provided the verbalized comment.
Another embodiment of the invention comprises an apparatus that utilizes a set of components distributed across a network. In this embodiment a server that has a text-to-speech engine obtains a document comprising text from a document source (e.g., memory or another computer) and converts some or all of the text in the document into an audio file. A thin-client (e.g., a user interface device) obtains the audio file from the server via network connection and an audio output device associated with the plays the audio file to the user of the thin-client. If the user desires to make a comment about the document, the user may provide verbalized input (e.g., comments and/or annotations) to an audio input device associated with the thin-client. Once the user provides such input, the input is transmitted to the server computer where the file is stored as an audio comment file (e.g., in the associations data structure). The server computer comprises an annotator that is configured to associate the audio comment file with a location in the document that corresponds to the portion of the audio file playing when the user provided the comment.
The invention also contemplates a method for annotating a document.
Computer software may complement the method by performing some or all aspect of the process described. One embodiment of the invention is a method for annotating a document that comprises: generating authentication information of a user desiring access to a document; allocating an associations file structure for the user; obtaining the document from a memory medium via an interconnection path configured to access the document, the document having text elements; obtaining a first annotation of the text document, the first annotation having a first set of audio elements; converting the text elements to a second set of audio elements; associating the first set of audio elements with the second set of audio elements to generate a playback document; generating an audible playback of the playback document to the user when the user indicates a desire to hear the document; obtaining verbalized comments from the user via an audio input mechanism upon activation of an annotation trigger during the audible playback; associating the verbalized comments with a location in the playback document corresponding with the occurrence of the annotation trigger during the audible playback; and storing the location and the authentication information of the user and the verbalized comments in the associations file structure.
DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates a word processing environment that contains a way for users to manually insert comments into a document.
Figure 2 illustrates a representation of a data file as used in a prior art audio editing device.
Figure 3 provides an example of the command interface associated with an annotation device implementing an embodiment of the invention.
Figure 4 is an illustration of some of the types of apparatus utilized in accordance with one embodiment of the present invention to annotate a document.
Figure 5 illustrates the basic components for annotating a document in accordance with one embodiment of the invention.
Figure 6 provides an example of the process utilized in accordance with one embodiment of the invention to annotate a document.
Figure 7 illustrates the process utilized by an embodiment of the invention to allocate processing responsibilities depending on the processing power of the system utilized to listen to and obtain the document or comment data from a computer network.
Figure 8 is a schematic of a smart client configuration in accordance with an embodiment of the present invention.
Figure 9 illustrates the process utilized in accordance with one embodiment of the invention to annotate a document on a smart device with limited memory such that document data from the server is sent in packets to the smart client.
Figure 10 shows a schematic of the thin client configuration according to one embodiment of the present invention.
Figure 11 is a flow diagram of the processes performed by the document server when interacting with a thin terminal according to one embodiment of the present invention.
Figure 12 shows a file structure for storing the annotations in accordance with an embodiment of the present invention.
Figure 13 is an illustration of the hierarchical tree structure of the file storage system in accordance with an embodiment of the present invention.
Figure 14 shows a general-purpose hardware environment utilized to implement one or more embodiments of the invention.
DETAILED DESCRIPTION
A method and apparatus for annotating documents is described. In the following description numerous specific details are set forth in order to provide a more thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail so as not to obscure the invention.
It is important to note that any type of individual who has a need to review documents may utilize one or .more aspects of the invention Movie producers, directors, actors, and other entertainment industry people as well as doctors, lawyers, teachers, students, businessmen, and many other types of individuals encounter the problems solved by embodiments of the invention.
Thus, it should be clear to one of ordinary skill in the art that there are multiple contexts within which to utilize the method and apparatus for annotating documents described herein.
System Overview:
In one or more embodiments of the invention, the apparatus and methods described herein allows users to review and add any number of annotations (i.e. add comments) to a digital document such as movie scripts, books, etc. from anywhere in the world. For instance, the invention may play the document to the user via an audio output mechanism and provides the user with a way to comment on the document by simply speaking to an audio input mechanism. Any type of computational device may be configured to embody the invention and thereby provide the user with an interface to comment on or review comments about a particular document. Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a land-based telephone, a personal computer (e.g., a PC or a PDA), dictation device, or 5 any other system capable of accepting audio input and output. Each of the devices that embody the invention may access the document so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish 10 reviewing the document from home using a regular phone line.
If a user wishes to review the contents of a document while the user is at a remote location (e.g., in an automobile), the user may utilize a device (see e.g., Figure 3, annotation device 300) implementing one or more embodiments of the invention to obtain and play an instance of the document the user wishes to 15 hear. The user may provide documents to the device via any type of removable media 304 (e.g., flash memory, floppy disk) comprising document data 305. The user may insert such removable media into media slot 302. In accordance with one embodiment of the invention the device can also be configured to obtain document data 305 from server 312 via network 308 (e.g., a wireless network, the Internet, a radio frequency (RF) network, cellular network, etc...). Documents typically originate as text data (e.g., Microsoft WordTM files, HTML files, XML files, or any other type of ACSCII or binary data representing a document) and are converted to audio data prior to playback (e.g., via a text-to-speech operation which may be referred to in one embodiment of the invention as a document processing engine). However, the invention contemplates embodiments configured to interact with multiple types of documents and may be adapted to provide users with the ability to review any type of digital document.
The text-to-speech operation that prepares the document data for audible playback to the user may occur at server 312 or at annotation device 300. In one embodiment of the invention, the user of annotation device 300 may begin reviewing a document by identifying which document to review and selecting play button 312. This causes the device to audibly playback the document to the user via audio output 310. If the document was originally text, the device converts the text into sound files (e.g., via the text-to-speech engine) before it sends the sound data to audio output 310. .Any time during playback of the document, the user may verbally insert comments into the document by selecting annotate button 313. Upon activation of annotate button 313, annotation device 300 begins to collect audible comments provided by the user via audio input 310. Thus, the annotation device comprises a mechanism such as a microphone for collecting audible words (e.g., comments/annotations) from the user.
Each comment the user provides is stored by the system in memory (on the client device or the document server) and associated with a location in the document that is contextually relevant to the comment. If, for instance, the document is a script, the person reviewing the script may insert comments about a particular scene or treatment at a point in the document that correlates to the scene or treatment to which the comment pertains. If the usex makes a comment about scene 1, that comment is associated with scene 1 so that if another individual revisits the document after the first user inserted the comment that individual can review the first user's comments along with the contents of the document.
If the user wishes to forward or rewind to a certain section in the device, the user may utilize forward/rewind button 314 to reach a certain place in the document. Button 314 therefore provides the user with a way to quickly forward to or rewind to relevant portions of the document. In one embodiment of the invention, button 314 comprises a shuttle/jog button such as the type utilized in linear editing. Stop button 315 provides users with a means to stop playback of the document. The invention may also comprise pause button 316 which when depressed causes playback to suspend for a certain interval of time until the user indicates by selection of another button to resume playback of the document. One embodiment of the invention contemplates the use of voice-activated software in order to implement the functions associated with buttons 312-316. In this embodiment, the user may annotate a document by verbally issuing an annotations command while the document is playing.
Once the annotation device obtains comments from the user, the comments are stored in a digital memory medium for later use and/or processing. The stored comments may, for example, be converted from audio data back into text data via a speech recognition engine (SRE). Thus, the comments associated with the document may be stored in text and/or audio form. If the same or another user plays the document back at a different time, the device obtain the originally sampled audio from memory and plays it back when the user is listening to the point in the document where the comment was previously given. In one embodiment of the invention, the user who provided the comment is audibly identified when the comment is played. If, for example, a user named user 1 made comments about a particular portion of a document, the device would identify, at the time the comment way played, that the comment originated from user 1. Thus, the device provides users with a way to identify who each set of comments originated from. The user reviewing the 1~
document may elect to hear comments from certain users while excluding comments from other users. If, for instance, the reviewer wishes to hear user 1's comments, but not user 2's comments, the review may request that the device only playback user 1's comments.
Figure 4 is an illustration of some of the different types of annotation devices that may be utilized to annotate a document. Each type of device provides the user with a means to annotate a document from a different location. The illustration of Figure 4 shows user 400 desiring to comment on document 407 located in document server 402. User 400 may accomplish this by utilizing device 404, 406, or 401. Annotation device 401 comprises a land-based telephone (e.g., a payphone, home phone, business phone, cell phone, etc...).
In the embodiments where mobile client 401 is a wireless device, wireless tower 403 may be used to interconnect between annotation device 401 and communication network 410. Annotation device 401 may comprise a "smart"
device configured with adequate processing power and memory to handle the requirements of the present invention. For example, if annotation device 401 comprises a smart mobile client device 401 should have the computational power to perform the annotating functions described in Figure 5 in addition to the control functions 502 for playback of the original document.
In another embodiment, annotation device 401 is a "thin°' device such as a land telephone or RF device. In the land telephone configuration, annotation device 401 provides the playback control functions 502 of Figure 5 for playback control of the document. For example, the telephone keypad keys or appropriate voice commands may provide the playback control functions. The Figure 5 functions depicting annotating engine 500 and speech recognition engine 510 are performed in one embodiment of the invention in document server 402.
Annotation device 401 may comprise any device with access to different types of communication interconnects. An embodiment of the invention contemplates the use of any type of interconnection fabric that provides one or more suitable communication paths for carrying data between multiple types of computational devices. The iilterconnect fabric may be a type of wireless transport mechanism that may act as a carrier wave for data. For example, an embodiment of the invention may utilize a Cellular Digital Packet Data (CDPD) network, a Global System for Mobile (GSM) network, a Mobitex network, and/or any other type of radio, satellite, or wireless communication channel that can establish a link between multiple devices. Annotation device 401 may, for example, transmit data to or receive data from communication network 410 (e.g., the Internet) to document server 402.
Annotation device 401 provides user 400 with an interface for controlling the output of document server 402. User 400 may, for example, utilize annotation device 401 to connect to a system (e.g., server 402) configured to audibly play documents (e.g., document 40~) to user 400. In this embodiment of the invention document server 402 may utilize one or more components of a voice mail system to play document 407 to the user. The voice mail system is adapted in such a way that it can access and play document files that reside in a predetermined location via network 410. If the files accessed are text data the system may convert them to audio data via a text-to-speech engine. When the user access the system, the user selects a document to hear (e.g., by navigating a hierarchical menu structure) and the system plays that document to the user.
If the user wishes to provide comments about the document the user indicates to i.
the system that a comment is going to be provided (e.g., by pressing a key on the telephone keypad). When the user makes such an indication, the system pauses playback of the document and marks the location of the comment. The user may then provide a comment to the system by making a verbal statement to the system. The system records the user's comments and associates that 5 comment with the location i1z the document identified by the user. If the same or another user plays the document back again, the system plays the previously provided comment when the system reaches the location in the document where the user previously submitted a comment. Thus, users may utilize annotation device 401 as an interface to document server 402 so as to listen to 10 and submit comments about a particular document.
Annotation device 404 and 406 comprises a client device (such as the one illustrated in figure 3) configured to obtain document data from one or more sources. Device 404 comprises a personal computer, PDA, or some other type of client computing device configured to obtain document 407 from document 15 server 402 via network 410. In one or more embodiments, annotation device 404 may be used for the annotating function. Annotation device 404 is connected to document server 402 through communication network 410.
Annotation device 404 is capable of processing data from removable storage media 405, from document server 402, or from any other data source. Data that 20 is stored (e.g., document 407) may comprise the document to be annotated or the annotated document. In the case where the document data is contained in removable storage media 405, client computer 407 may be used to transfer the data to document server 402. For example, removable storage 405 may contain data processed in autonomous client 406.
Autonomous client 406 comprises another type of device that may utilize one or more embodiment of the invention. Users of autonomous client 406 may manually provided document data taken from client computer 407 via removable storage media 405. Autonomous client 406 is capable of processing document file stored in removable storage 405. In one or more embodiments, autonomous client 406 does not have direct connection to communications network 410. In this configuration, autonomous client 406 possesses the full capability to perform the functions described in Figure 5. Thus, autonomous client 406 comprises enough components to act as a stand-alone device for annotating documents.
Autonomous client 406 includes control functions for playback of the document contained in removable storage 405 such as Play, Rewind, Fast-Forward, Pause, Stop, Annotate (i.e. mark), etc. It will be apparent to one of ordinary skill in the art that other playback control functions not described in this disclosure can be added, subtracted, or substituted to provide the capability for optimum playback of the document. For example, it may be desirable to have the ability to enter a user identification, to vary playback speed, to provide jump functions, and find functions. Tllus, autonomous client 406 may be modified to incorporate these and other playback control functions.
Document server 402 maintains the current copy of the annotated document. In one or more embodiments of the invention, document server 402 is on a worldwide communications network so that users may log on (using device 401, annotation device 404, or client computer 404) to comment on a particular document from anywhere in the world. Document server 402 also maintains the capability to perform some or all of the processing functions described in this disclosure. For example, document server 402 has the ability to perform the full processing described in Figure 6 as well as store and maintain the original document and its annotations. Document server 402 may also maintain a security mechanism that prevents unauthorized access to the documents. For example, document server 402 may require a logon ID and password or perform some other type of authentication before access can be granted to the document file contained therein.
Annotating Engine One or more embodiments of the present invention comprise an annotating engine as shown in Figure 5. Annotating engine 500 accepts control inputs from playback controller 502 and comments 512 from a user. For example, when a user desires to comment on a document contained in memory 504, the user performs any necessary authentication to gain access to the document. After access is granted, the document in memory 504 may be played back using controls functions from playback controller 502. Memory 504 comprises any type of memory (e.g., flash memory, removable storage media, static storage, or any other type of computer memory).
Once the user provides comments 512, annotating engine 500 associates comment 512 with the location in the document where the comment was provided. For example, annotating engine 500 preserves the original document in memory 504 and creates the associated files (i.e., Annotations file, Annotations index file, and Annotations names file) as shown in Figure 11.
Playback controller 502 provides playback instructions to the annotating engine. Playback controller 502 provides commands such as play, rewind, fast-forward, pause, stop, and annotate (i.e. annotation start mark 514) to control the playback of the data in memory. Playback control functions are not limited to those listed above, other functions that may enhance playback to the user such as volume control in embodiments that employ audible playback as feedback to the user. Other examples may include variable speed controls, jump and find functions. For example, the user may desire to jump to the beginning of the document or to a known point in the data.
During playback, the document may be converted to speech in text/speech conversion block 506 if the document is text and if audible playback is desired. Text/speech conversion block 506 comprises a text-to-speech conversion engine configured to accept text as input and generate audio as output. Some examples of text-to-speech engines that text/speech block may comprises includes text-to-speech engines such as the ones made by Lernout &
Hauspie, MicrosoftTM, or any other text-to-speech provider. A user desiring to add comments to the document at a particular point during playback generates an annotaion start mark 514 by selecting performing an action such as selecting annotate button 313. However, the invention contemplates other mechanisms that may cause an annotation start mark 514 to occur. For instance, annotation start mark may be voice activated or activated by any other command provided by the user who desires to pr ovide an annotation.
At the occurrence of annotation start mark 514, audio playback of the document pauses and annotator 508 begins recording user comments. A
subsequent annotation mark 514 (e.g., an end annotation mark) may signify the end of user comments for that location in the document. In some instances the passage of a certain period of time causes the annotation end mark 514 to occur.
If, for example, after causiilg an annotation start mark 514 to occur, the user does not speak for some interval of time, the annotation end mark 514 will occur and thereby mark the end of the user's comment.
In one embodiment of the invention, annotator 508 has the capability to transmit sound and text data to the user. For example, audio sound generated in text/speech conversion block 506 may be transmitted to the user via a speaker system. If the system is part of an automobile sound system, for instance, audio data may be generated and sent via the speaker system associated with the automobile's stereo system. If the document contains sound data, the annotator 508 utilizes a media player to play the sound data directly to the user via the speaker system. Annotator 508 has the capability to receive and record sound and text data. For example, user comments 512 may arrive from a sound input source such as a microphone and recorded in memory 504 by annotator 508.
Thus, annotator 508 comprises or is associated with an audio input/output mechanism that can collect audio data from or provide audio data to the user.
Annotator 508 determines the location in the document under review that corresponds to occurrence of the annotation start mark 514. This location signifies the place where the user began making comment 512 (e.g., the start).
Upon receipt of the annotation start mark, annotator 508 determines the current location of the document under review. This location is stored, in one embodiment of the invention, as part of the associations files discussed in Figure 11. Concurrently, annotator 508 starts recording the user's comments 512 until receipt of an end annotation mark 514. During recording of the user's comment, annotating engine 500 suspends playback of the document under review at the point corresponding to the location where the user began making comment 512.
Playback of the document resumes at completion of recording of the user comments. For instance, playback resumes when the user submits an end annotation mark 514.
After playback of the document and recording of user comments are complete, annotator 508 stores the associations information (See Figure 11) into memory 504. The associations information comprises data memory that represents the comments provided by one or more users. Each comment is typically associated with a certain document and/or a certain user. In one embodiment of the invention, the associations information is stored in a data structure comprising an annotations names file, annotations index file, and annotations file. The specifics of this associations data structure are discussed later in this specification. When the aruzotation device utilizes the associations data structure, the integrity of the origizzal document is not compromised during processing.
Annotator 508 converts the recorded data to proper format for storing.
5 In one or more embodiments, the comments are stored as sound data in a WAV
file or any other audio format capable of storing sounds data (e.g., MP3, RealAudioTM, etc...). Comments may also be converted to text for storage or for transmittal as data packets using protocols such as the Wireless Applications Protocol (WAP) in cases where processing is done in a wireless client and where 10 text transmission is desirable over voice transmittal. When conversion of the comments to text is desired, Speech Recognition Engine 510 may be used to convert the comments to text. In one or more embodiments, annotator 508 provides the user the capability to review comments before saving the comments in the data structure.
15 Process Utilized to ObtainlPlayback Annotations:
Figure 6 provides an example of the process utilized in accordance with one embodiment of the invention to annotate a document. The process may be implemented in hardware and/or software form and may, for example, comprises computer readable program code tangibly embodied in a computer 20 readable medium such as a processor, or memory coupled to the processor. In other instances, the invention executes in memory such as a hard disk, floppy disk, and/or any other form of memory capable of storing computer readable program code. The computer program or hardware device is referred to herein as the system. As will be discussed herein, certain executable and non-executable 25 portions of the files that are used by embodiments of the invention may be distributed or obtained via a network (e.g., a wireless network).
When the system enters an execution state at start point 600 the system waits for input from the user. In accordance with one embodiment of the invention input from the user may require authentication. Authentication provides the system with a way to determine which user made a particular set of comments. If multiple users comment on the document, the authentication data enables the system to discern between comments provided by different users. If authentication is required (e.g., at step 602), the system obtains a unique identifier (e.g., at step 604) from the user or the system associated with the user.
If such authentication is not required, the system allocates a portion of memory to the system for one or more data structures) (e.g., at step 606) associated with the annotations to be provided by the user. One of ordinary skill in the art should recognize that the invention also contemplates embodiments where the system allocates memory earlier or later in the execution process.
Once memory is allocated for the data structure, the system obtains the file that is to be reviewed (e.g., at step 60~). This file typically comprises a document contaiizing data such as text and/or other elements. Documents may, for example, originate as text files (e.g., ASCII, EPSIDIC, etc...), audio files, (e.g., MP3, RealAudioTM, WAV, etc...), image files (e.g., GIF, JPG, TIFF, etc..) movie files (e.g., AVI, MPEG, RM, etc...), or any other type of file containing data the user of the system may wish to review and subsequently comment upon.
When the file to be reviewed (or the location of the file) is loaded into memory the system waits for the user to indicate a desire to playback the file with annotations (e.g., at step 610). If the user initiates (e.g., by depressing a play w/annotations button or stating a verbal command) a command to begin playback with annotations, the system responds by obtaining the unique identifier (e.g. ID(s)) associated with the users) whose comments/annotations the user operating the system wishes to hear. If for example, the user of the system wishes to hear comments from one or more certain individuals, the ID(s) associated with those individuals are supplied to the system at step 612. The system may default to a setting that plays back all the comments associated with the document or in other instances the system may prioritize the comments by playing comments from some individuals prior to comments from others.
When the system identifies which set of comments to obtain it obtains one or more annotations files (e.g., at step 614). The annotations file is accessible in one embodiment of the invention via an index or set of pointers. Thus, the appropriate annotations file may be accessed by utilizing the index to determine the location of the comments the operating user wishes to hear. Each annotations file comprises one or more files that point to or contain comments from one or more users. In one embodiment of the invention, the annotations file contains a list of memory locations, network addresses, or hyperlinks that reference or comprise user comments. The annotations file may contain components located within memory or distributed across multiple computers accessible via a network (e.g., a wireless network). In one instance, comments are made accessible via a computer network such as the Internet or some other mechanism for obtaining digital files having user comments.
If the user has not initiated a command to review the document with annotations, the system bypasses steps 612 and 614 and executes step 616. At step 616, the system prepares a document file for playback. In the instances where the user has previously indicated a desire to listen to the annotations, the system prepares the annotations file and the document file for playback by associating the two files with one another in a playback file. If the user does not want to hear any annotations, the system prepares the document file for playback without any annotations. Both the document file and the annotations files may comprise text, sound, and/or any other type of data. In accordance with one embodiment of the invention the document file originates as text and the annotations files) contains audio data that is related to a particular location in a document. However, both the document file and the annotations file may contain other types of data.
In one embodiment of the invention, the system reviews the type data or contents of the playback file to determine what operations to perform on the playback file. At step 618, the system may determine whether the file is a sound file. If the system encounters a sound file, the system converts the file (e.g., at step 620) from audio data to text data by, using a text-to-speech engine. The location of the text-to-speech processing may vary depending upon the processing capacity of the system that is utilized. The text-to-speech conversion may take place on the computer conducting the playback or on a computer separable from the computer performing the playback. After the text-to-speech conversion occurs, the system plays the audio file (e.g., at step 622) via an audio ' output mechanism. If the system reaches the end of the file (EOF), without the user providing any comments, (e.g., step 624) the system may exit at step 625.
However, if the user indicates a desire to provide comments/annotations (e.g., at step 626) by selecting an annotate button, verbalizing a comment, or by some other mechanism for issuing a command, the system executes step 628 where it pauses playback of the audio associated with the text file and inserts a mark at . , , the appropriate location. The mark identifies the location where the user initiated an annotate command. Once the mark is set, the system obtains comments from the user (e.g., at step 630) via an audio input mechanism such as a microphone. The comment may comprise any type of verbalized or non-verbalized input that can be associated with the document about which the user is commenting upon. A comment about a particular segment of text in the document may, for example, contain reference to a Web address that contains information the reviewer wishes to share. Comments may point to other comments so that each comment may be related to or associated with other types of data. The reviewer may therefore reference other URLs or data in a comment and the user listening to the reviewer's comments may access that data.
The system monitors the input to determine when the user finishes providing the comment. When the user finishes the comment, the system saves the comment in the appropriate location. The system may, for example, place the comment into a memory location associated with the data structure allocated at step 606. In some instances, each comment the user provides is saved in the annotations file and stored at any location capable of storing digital data.
Allocation of Processing Responsibilities:
When a device is configured to obtain document data and/or annotation data over a network (e.g., a cell phone network, wireless network, etc...) so that the user can interact with such data, the type of device attempting to obtain access to the data is important. If, for example, the system has sufficient processing capacity, and the network utilized to connect to the system has a low bandwidth or high cost associated with it, the amount of data sent to the device should be minimized and the processing should be performed on the system. If, however, the system does not have any processing resources or has minimal processing capabilities, the processing should be performed on the computer supplying the document or annotation data (e.g., the server computer).
Figure 7 illustrates the process utilized by an embodiment of the invention to allocate processing responsibilities. The process illustrated begins at step 700 where a determination is made as to whether or not the system attempting to obtain text data from a network source for conversion to audio data and then subsequent playback to the user comprises a smart mobile device.
If the system (e.g., the annotation device) comprises a smart mobile device, the network source, typically document server 402, retrieves the text data from memory (e.g., at step X02) and prepares and transmits the text data to the smart 5 mobile device (e.g., at step 704). In one embodiment of the invention, the smart mobile device performs the annotating engine functions described above. For example, the type of processing performed at the smart mobile device typically comprises a text-to-speech operation that converts the text supplied from the network source into audio data that can be played to the user. Each portion of 10 text may, for example, be processed utilizing Digital Signal Processing (DSP) techniques to enhance the quality of the audio data and/or encode the data into an audio format that the smart mobile system is capable of playing. The smart mobile device may for example, convert the text into an optimized Real AudioTM
file (e.g., streaming media file) prior to playing the file to the user via an 15 embedded or software Real AudioTM player. Once the processing is complete, the smart mobile device transmits some data back to the server (e.g., at step 706) for storage or further processing. For instance, if the user made a comment (e.g., at step 705), the smart mobile device may transmit the users comments as well as the location data associated with the comment back to the server for 20 storage and /or processing purposes. The location data identifies where in relation to the text the user made a comment. The comment comprises the data inserted into the annotations file. It is important to note that the smart mobile device may also send other types of data back to the server for security or authentication purpose. The invention also contemplates the transmission of 25 other types of data needed to maintain the link between the data sources and the smart mobile device.
In the instances where the outcome of step 700 indicates that the system connected to the data source is not a smart mobile device, but is rather a device which contains minimal or non processing capacity (e.g., a payphone or land line phone), the processing may be performed on a computer that has a higher capacity for processing data. Such processing may be performed on the data source or on any other computer accessible via a computer network. The computer tasked with performing such processing obtains the data and then converts the text file into an audio file (e.g., at step X08). The processing performed may also contain routiizes for optimizing the quality of the audio file in view of the device the file is going to be transmitted to. Once the text file is processed, the audio data can be transmitted to the device associated with the user (e.g., step X10). If, for example, the user is at a payphone or some other type of telecommunications device that does not have a mechanism for processing data the audio file created by the server is transmitted to the user at the telecommunications device via the telephone network. The system tasked with performing the processing listens while it is playing back the document to the client for some form of command to start receiving comments (e.g. at step 712). If the user wishes to insert a comment into the document the user may generate a tone or some other sound via a telephone keypad or some other mechanism capable of generating a sound. In one embodiment of the invention, the user may depress a key (e.g., a number such as 1) or a simple verbal ,, statement such as "insert comment" to indicate a desire to make a comment.
Once the system receives the audible command, the system stops transmitting audio data and enters a listening mode. When the system is in a listening mode it picks up any verbal input (e.g., comments or annotations) provided by the user (e.g., at step 714). The system marks the location associated with the user comment and associates the comment with the document the user is commenting about. Once the user finishes providing the comment the system stores the comment in the annotations file for later access. The system may determine that the user has finished commenting when the user is silent for a certain threshold period of time (e.g., 30 seconds, 45 second,1 minute, etc...) or when the user indicates the comment is complete by depressing a key or button on the device that cause an audible noise to be generated.
Smart Client Configuration Figure 8 comprises a schematic of a smart client configuration in accordance with an embodiment of the present invention. As used herein, the smart client possesses processing power and control functions adequate to perform the processing required for the present invention. As shown in Figure
further limitation in current systems is that such system are not directed to providing documents to users in any location. Users of the audio editor described in'Bovs et al. cannot, for example, obtain a document from a remote location without having an instance of the document on-hand.
Thus, there is a need for a system that solve the limitations inherent in the prior art by allowing the user to listen to a document and verbally comment on the contents of the document without necessarily changing the document.
' Moreover users could benefit from a system that aids the user responsible (e.g., the typist or data entry person) for the conversion process. In some instances there is also a need for a system that allows user to selectively listen to comments made by a certain individual without having to review all comments that were made about the document.
In the foregoing discussion about current systems, the problems and limitations set forth as existent in the prior art are provided for exemplarily purposes. It should be clear to one of ordinary skill in the art that these problems also exist in other contexts or professions and that the invention may apply to situations other than the ones described herein.
SUMMARY OF THE INVENTION
An embodiment of the invention describes a system that enables people to add verbal annotations (i.e. add comments) to a digital document such as a movie script, book, or any other type of document. This device provides the reviewer with an improved way to interact and comment upon documents while on the move. For example, the reviewer may utilize an embodiment of the invention to access and verbally comment on a document from multiple locations. Thus, the invention provides a system that enables the reviewer to begin reviewing a document from a Bell phone, continue to review the same document from a home PC, and finish reviewing the document from a pay phone. An embodiment of the invention also provides the reviewer with an intuitive way to verbally interact with documents. The system can read documents (e.g., via a text-to-speech engine) so that the reviewer can hear the contents of the document. The system also provides the reviewer with a way to record verbal comments about the document. When a comment is supplied the comment becomes associated with the location in the document where the comment was provided. If, for example, the reviewer makes a comment about a particular passage of text, the comment becomes associated with the passage of text the comment is related to.
The device that embodies the invention uses an audio output mechanism to play the document to the user. At any time during playback the user may provide a comment by selecting an annotate button and simply speaking to the device. In turn, the device records the user's comment and associates it with the location in the document where the comment was given. If the document is replayed after a user provides comments, the device plays back the document and the comments via the audio output mechanism. This way the user can hear the document and any comments that were made about the document.
Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a regular telephone, a personal computer, or any other computational system. Each of the devices that embody the invention may access the document (e.g., via a data storage medium or computer network) so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish reviewing the document from home using a regular phone line.
One or more embodiments of the invention comprises a method and apparatus that enables users to add any number of annotations (i.e. add comments) to a digital document such as movie scripts, books, etc. from anywhere in the world. Thus, an embodiment of the invention enables users to hear and comment on a document from one or more locations. Any type of computational device may be configured to embody the invention and thereby provide the user with an interface to comment on or review comments about a particular document. Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a regular telephone (e.g., POTS), a personal computer (e.g., a PC or a PDA), or any other system capable of accepting audio input and output. Each of the devices that embody the invention may access the document so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish reviewing the document from home using a regular phone line.
Multiple types of devices can be modified to incorporate aspects of the 5 invention. For example, an annotation device (e.g., an apparatus) having a processor and memory containing a text document may be coupled with a document processing engine that is configured to obtain the text document from memory and convert a portion of the document to an audio file that can be played to a user. If a user indicates a desire to hear the content of a document 10 the annotation device uses an audi~ output mechanism to play the audio file to the user. If the user provides a comment to the annotation device an audio input device configured to obtain such verbalized comments from the user stores the comment as an audio comment file. The annotation device passes the audio comment file to an annotator that is configured to associate the audio comment file with a location in the text document that corresponds to the audio file playing when the first user provided the verbalized comment.
Another embodiment of the invention comprises an apparatus that utilizes a set of components distributed across a network. In this embodiment a server that has a text-to-speech engine obtains a document comprising text from a document source (e.g., memory or another computer) and converts some or all of the text in the document into an audio file. A thin-client (e.g., a user interface device) obtains the audio file from the server via network connection and an audio output device associated with the plays the audio file to the user of the thin-client. If the user desires to make a comment about the document, the user may provide verbalized input (e.g., comments and/or annotations) to an audio input device associated with the thin-client. Once the user provides such input, the input is transmitted to the server computer where the file is stored as an audio comment file (e.g., in the associations data structure). The server computer comprises an annotator that is configured to associate the audio comment file with a location in the document that corresponds to the portion of the audio file playing when the user provided the comment.
The invention also contemplates a method for annotating a document.
Computer software may complement the method by performing some or all aspect of the process described. One embodiment of the invention is a method for annotating a document that comprises: generating authentication information of a user desiring access to a document; allocating an associations file structure for the user; obtaining the document from a memory medium via an interconnection path configured to access the document, the document having text elements; obtaining a first annotation of the text document, the first annotation having a first set of audio elements; converting the text elements to a second set of audio elements; associating the first set of audio elements with the second set of audio elements to generate a playback document; generating an audible playback of the playback document to the user when the user indicates a desire to hear the document; obtaining verbalized comments from the user via an audio input mechanism upon activation of an annotation trigger during the audible playback; associating the verbalized comments with a location in the playback document corresponding with the occurrence of the annotation trigger during the audible playback; and storing the location and the authentication information of the user and the verbalized comments in the associations file structure.
DESCRIPTION OF THE DRAWINGS
Figure 1 illustrates a word processing environment that contains a way for users to manually insert comments into a document.
Figure 2 illustrates a representation of a data file as used in a prior art audio editing device.
Figure 3 provides an example of the command interface associated with an annotation device implementing an embodiment of the invention.
Figure 4 is an illustration of some of the types of apparatus utilized in accordance with one embodiment of the present invention to annotate a document.
Figure 5 illustrates the basic components for annotating a document in accordance with one embodiment of the invention.
Figure 6 provides an example of the process utilized in accordance with one embodiment of the invention to annotate a document.
Figure 7 illustrates the process utilized by an embodiment of the invention to allocate processing responsibilities depending on the processing power of the system utilized to listen to and obtain the document or comment data from a computer network.
Figure 8 is a schematic of a smart client configuration in accordance with an embodiment of the present invention.
Figure 9 illustrates the process utilized in accordance with one embodiment of the invention to annotate a document on a smart device with limited memory such that document data from the server is sent in packets to the smart client.
Figure 10 shows a schematic of the thin client configuration according to one embodiment of the present invention.
Figure 11 is a flow diagram of the processes performed by the document server when interacting with a thin terminal according to one embodiment of the present invention.
Figure 12 shows a file structure for storing the annotations in accordance with an embodiment of the present invention.
Figure 13 is an illustration of the hierarchical tree structure of the file storage system in accordance with an embodiment of the present invention.
Figure 14 shows a general-purpose hardware environment utilized to implement one or more embodiments of the invention.
DETAILED DESCRIPTION
A method and apparatus for annotating documents is described. In the following description numerous specific details are set forth in order to provide a more thorough understanding of the present invention. It will be apparent, however, to one skilled in the art, that the present invention may be practiced without these specific details. In other instances, well-known features have not been described in detail so as not to obscure the invention.
It is important to note that any type of individual who has a need to review documents may utilize one or .more aspects of the invention Movie producers, directors, actors, and other entertainment industry people as well as doctors, lawyers, teachers, students, businessmen, and many other types of individuals encounter the problems solved by embodiments of the invention.
Thus, it should be clear to one of ordinary skill in the art that there are multiple contexts within which to utilize the method and apparatus for annotating documents described herein.
System Overview:
In one or more embodiments of the invention, the apparatus and methods described herein allows users to review and add any number of annotations (i.e. add comments) to a digital document such as movie scripts, books, etc. from anywhere in the world. For instance, the invention may play the document to the user via an audio output mechanism and provides the user with a way to comment on the document by simply speaking to an audio input mechanism. Any type of computational device may be configured to embody the invention and thereby provide the user with an interface to comment on or review comments about a particular document. Some examples of the type of devices that can be configured to implement embodiments of the invention include, the components of an automobile sound system, a cell phone, a land-based telephone, a personal computer (e.g., a PC or a PDA), dictation device, or 5 any other system capable of accepting audio input and output. Each of the devices that embody the invention may access the document so as to provide the user with a way to review documents from multiple locations using multiple types of devices. The user may, for example, begin reviewing a document in an automobile, continue to review the document via a cell phone, and finish 10 reviewing the document from home using a regular phone line.
If a user wishes to review the contents of a document while the user is at a remote location (e.g., in an automobile), the user may utilize a device (see e.g., Figure 3, annotation device 300) implementing one or more embodiments of the invention to obtain and play an instance of the document the user wishes to 15 hear. The user may provide documents to the device via any type of removable media 304 (e.g., flash memory, floppy disk) comprising document data 305. The user may insert such removable media into media slot 302. In accordance with one embodiment of the invention the device can also be configured to obtain document data 305 from server 312 via network 308 (e.g., a wireless network, the Internet, a radio frequency (RF) network, cellular network, etc...). Documents typically originate as text data (e.g., Microsoft WordTM files, HTML files, XML files, or any other type of ACSCII or binary data representing a document) and are converted to audio data prior to playback (e.g., via a text-to-speech operation which may be referred to in one embodiment of the invention as a document processing engine). However, the invention contemplates embodiments configured to interact with multiple types of documents and may be adapted to provide users with the ability to review any type of digital document.
The text-to-speech operation that prepares the document data for audible playback to the user may occur at server 312 or at annotation device 300. In one embodiment of the invention, the user of annotation device 300 may begin reviewing a document by identifying which document to review and selecting play button 312. This causes the device to audibly playback the document to the user via audio output 310. If the document was originally text, the device converts the text into sound files (e.g., via the text-to-speech engine) before it sends the sound data to audio output 310. .Any time during playback of the document, the user may verbally insert comments into the document by selecting annotate button 313. Upon activation of annotate button 313, annotation device 300 begins to collect audible comments provided by the user via audio input 310. Thus, the annotation device comprises a mechanism such as a microphone for collecting audible words (e.g., comments/annotations) from the user.
Each comment the user provides is stored by the system in memory (on the client device or the document server) and associated with a location in the document that is contextually relevant to the comment. If, for instance, the document is a script, the person reviewing the script may insert comments about a particular scene or treatment at a point in the document that correlates to the scene or treatment to which the comment pertains. If the usex makes a comment about scene 1, that comment is associated with scene 1 so that if another individual revisits the document after the first user inserted the comment that individual can review the first user's comments along with the contents of the document.
If the user wishes to forward or rewind to a certain section in the device, the user may utilize forward/rewind button 314 to reach a certain place in the document. Button 314 therefore provides the user with a way to quickly forward to or rewind to relevant portions of the document. In one embodiment of the invention, button 314 comprises a shuttle/jog button such as the type utilized in linear editing. Stop button 315 provides users with a means to stop playback of the document. The invention may also comprise pause button 316 which when depressed causes playback to suspend for a certain interval of time until the user indicates by selection of another button to resume playback of the document. One embodiment of the invention contemplates the use of voice-activated software in order to implement the functions associated with buttons 312-316. In this embodiment, the user may annotate a document by verbally issuing an annotations command while the document is playing.
Once the annotation device obtains comments from the user, the comments are stored in a digital memory medium for later use and/or processing. The stored comments may, for example, be converted from audio data back into text data via a speech recognition engine (SRE). Thus, the comments associated with the document may be stored in text and/or audio form. If the same or another user plays the document back at a different time, the device obtain the originally sampled audio from memory and plays it back when the user is listening to the point in the document where the comment was previously given. In one embodiment of the invention, the user who provided the comment is audibly identified when the comment is played. If, for example, a user named user 1 made comments about a particular portion of a document, the device would identify, at the time the comment way played, that the comment originated from user 1. Thus, the device provides users with a way to identify who each set of comments originated from. The user reviewing the 1~
document may elect to hear comments from certain users while excluding comments from other users. If, for instance, the reviewer wishes to hear user 1's comments, but not user 2's comments, the review may request that the device only playback user 1's comments.
Figure 4 is an illustration of some of the different types of annotation devices that may be utilized to annotate a document. Each type of device provides the user with a means to annotate a document from a different location. The illustration of Figure 4 shows user 400 desiring to comment on document 407 located in document server 402. User 400 may accomplish this by utilizing device 404, 406, or 401. Annotation device 401 comprises a land-based telephone (e.g., a payphone, home phone, business phone, cell phone, etc...).
In the embodiments where mobile client 401 is a wireless device, wireless tower 403 may be used to interconnect between annotation device 401 and communication network 410. Annotation device 401 may comprise a "smart"
device configured with adequate processing power and memory to handle the requirements of the present invention. For example, if annotation device 401 comprises a smart mobile client device 401 should have the computational power to perform the annotating functions described in Figure 5 in addition to the control functions 502 for playback of the original document.
In another embodiment, annotation device 401 is a "thin°' device such as a land telephone or RF device. In the land telephone configuration, annotation device 401 provides the playback control functions 502 of Figure 5 for playback control of the document. For example, the telephone keypad keys or appropriate voice commands may provide the playback control functions. The Figure 5 functions depicting annotating engine 500 and speech recognition engine 510 are performed in one embodiment of the invention in document server 402.
Annotation device 401 may comprise any device with access to different types of communication interconnects. An embodiment of the invention contemplates the use of any type of interconnection fabric that provides one or more suitable communication paths for carrying data between multiple types of computational devices. The iilterconnect fabric may be a type of wireless transport mechanism that may act as a carrier wave for data. For example, an embodiment of the invention may utilize a Cellular Digital Packet Data (CDPD) network, a Global System for Mobile (GSM) network, a Mobitex network, and/or any other type of radio, satellite, or wireless communication channel that can establish a link between multiple devices. Annotation device 401 may, for example, transmit data to or receive data from communication network 410 (e.g., the Internet) to document server 402.
Annotation device 401 provides user 400 with an interface for controlling the output of document server 402. User 400 may, for example, utilize annotation device 401 to connect to a system (e.g., server 402) configured to audibly play documents (e.g., document 40~) to user 400. In this embodiment of the invention document server 402 may utilize one or more components of a voice mail system to play document 407 to the user. The voice mail system is adapted in such a way that it can access and play document files that reside in a predetermined location via network 410. If the files accessed are text data the system may convert them to audio data via a text-to-speech engine. When the user access the system, the user selects a document to hear (e.g., by navigating a hierarchical menu structure) and the system plays that document to the user.
If the user wishes to provide comments about the document the user indicates to i.
the system that a comment is going to be provided (e.g., by pressing a key on the telephone keypad). When the user makes such an indication, the system pauses playback of the document and marks the location of the comment. The user may then provide a comment to the system by making a verbal statement to the system. The system records the user's comments and associates that 5 comment with the location i1z the document identified by the user. If the same or another user plays the document back again, the system plays the previously provided comment when the system reaches the location in the document where the user previously submitted a comment. Thus, users may utilize annotation device 401 as an interface to document server 402 so as to listen to 10 and submit comments about a particular document.
Annotation device 404 and 406 comprises a client device (such as the one illustrated in figure 3) configured to obtain document data from one or more sources. Device 404 comprises a personal computer, PDA, or some other type of client computing device configured to obtain document 407 from document 15 server 402 via network 410. In one or more embodiments, annotation device 404 may be used for the annotating function. Annotation device 404 is connected to document server 402 through communication network 410.
Annotation device 404 is capable of processing data from removable storage media 405, from document server 402, or from any other data source. Data that 20 is stored (e.g., document 407) may comprise the document to be annotated or the annotated document. In the case where the document data is contained in removable storage media 405, client computer 407 may be used to transfer the data to document server 402. For example, removable storage 405 may contain data processed in autonomous client 406.
Autonomous client 406 comprises another type of device that may utilize one or more embodiment of the invention. Users of autonomous client 406 may manually provided document data taken from client computer 407 via removable storage media 405. Autonomous client 406 is capable of processing document file stored in removable storage 405. In one or more embodiments, autonomous client 406 does not have direct connection to communications network 410. In this configuration, autonomous client 406 possesses the full capability to perform the functions described in Figure 5. Thus, autonomous client 406 comprises enough components to act as a stand-alone device for annotating documents.
Autonomous client 406 includes control functions for playback of the document contained in removable storage 405 such as Play, Rewind, Fast-Forward, Pause, Stop, Annotate (i.e. mark), etc. It will be apparent to one of ordinary skill in the art that other playback control functions not described in this disclosure can be added, subtracted, or substituted to provide the capability for optimum playback of the document. For example, it may be desirable to have the ability to enter a user identification, to vary playback speed, to provide jump functions, and find functions. Tllus, autonomous client 406 may be modified to incorporate these and other playback control functions.
Document server 402 maintains the current copy of the annotated document. In one or more embodiments of the invention, document server 402 is on a worldwide communications network so that users may log on (using device 401, annotation device 404, or client computer 404) to comment on a particular document from anywhere in the world. Document server 402 also maintains the capability to perform some or all of the processing functions described in this disclosure. For example, document server 402 has the ability to perform the full processing described in Figure 6 as well as store and maintain the original document and its annotations. Document server 402 may also maintain a security mechanism that prevents unauthorized access to the documents. For example, document server 402 may require a logon ID and password or perform some other type of authentication before access can be granted to the document file contained therein.
Annotating Engine One or more embodiments of the present invention comprise an annotating engine as shown in Figure 5. Annotating engine 500 accepts control inputs from playback controller 502 and comments 512 from a user. For example, when a user desires to comment on a document contained in memory 504, the user performs any necessary authentication to gain access to the document. After access is granted, the document in memory 504 may be played back using controls functions from playback controller 502. Memory 504 comprises any type of memory (e.g., flash memory, removable storage media, static storage, or any other type of computer memory).
Once the user provides comments 512, annotating engine 500 associates comment 512 with the location in the document where the comment was provided. For example, annotating engine 500 preserves the original document in memory 504 and creates the associated files (i.e., Annotations file, Annotations index file, and Annotations names file) as shown in Figure 11.
Playback controller 502 provides playback instructions to the annotating engine. Playback controller 502 provides commands such as play, rewind, fast-forward, pause, stop, and annotate (i.e. annotation start mark 514) to control the playback of the data in memory. Playback control functions are not limited to those listed above, other functions that may enhance playback to the user such as volume control in embodiments that employ audible playback as feedback to the user. Other examples may include variable speed controls, jump and find functions. For example, the user may desire to jump to the beginning of the document or to a known point in the data.
During playback, the document may be converted to speech in text/speech conversion block 506 if the document is text and if audible playback is desired. Text/speech conversion block 506 comprises a text-to-speech conversion engine configured to accept text as input and generate audio as output. Some examples of text-to-speech engines that text/speech block may comprises includes text-to-speech engines such as the ones made by Lernout &
Hauspie, MicrosoftTM, or any other text-to-speech provider. A user desiring to add comments to the document at a particular point during playback generates an annotaion start mark 514 by selecting performing an action such as selecting annotate button 313. However, the invention contemplates other mechanisms that may cause an annotation start mark 514 to occur. For instance, annotation start mark may be voice activated or activated by any other command provided by the user who desires to pr ovide an annotation.
At the occurrence of annotation start mark 514, audio playback of the document pauses and annotator 508 begins recording user comments. A
subsequent annotation mark 514 (e.g., an end annotation mark) may signify the end of user comments for that location in the document. In some instances the passage of a certain period of time causes the annotation end mark 514 to occur.
If, for example, after causiilg an annotation start mark 514 to occur, the user does not speak for some interval of time, the annotation end mark 514 will occur and thereby mark the end of the user's comment.
In one embodiment of the invention, annotator 508 has the capability to transmit sound and text data to the user. For example, audio sound generated in text/speech conversion block 506 may be transmitted to the user via a speaker system. If the system is part of an automobile sound system, for instance, audio data may be generated and sent via the speaker system associated with the automobile's stereo system. If the document contains sound data, the annotator 508 utilizes a media player to play the sound data directly to the user via the speaker system. Annotator 508 has the capability to receive and record sound and text data. For example, user comments 512 may arrive from a sound input source such as a microphone and recorded in memory 504 by annotator 508.
Thus, annotator 508 comprises or is associated with an audio input/output mechanism that can collect audio data from or provide audio data to the user.
Annotator 508 determines the location in the document under review that corresponds to occurrence of the annotation start mark 514. This location signifies the place where the user began making comment 512 (e.g., the start).
Upon receipt of the annotation start mark, annotator 508 determines the current location of the document under review. This location is stored, in one embodiment of the invention, as part of the associations files discussed in Figure 11. Concurrently, annotator 508 starts recording the user's comments 512 until receipt of an end annotation mark 514. During recording of the user's comment, annotating engine 500 suspends playback of the document under review at the point corresponding to the location where the user began making comment 512.
Playback of the document resumes at completion of recording of the user comments. For instance, playback resumes when the user submits an end annotation mark 514.
After playback of the document and recording of user comments are complete, annotator 508 stores the associations information (See Figure 11) into memory 504. The associations information comprises data memory that represents the comments provided by one or more users. Each comment is typically associated with a certain document and/or a certain user. In one embodiment of the invention, the associations information is stored in a data structure comprising an annotations names file, annotations index file, and annotations file. The specifics of this associations data structure are discussed later in this specification. When the aruzotation device utilizes the associations data structure, the integrity of the origizzal document is not compromised during processing.
Annotator 508 converts the recorded data to proper format for storing.
5 In one or more embodiments, the comments are stored as sound data in a WAV
file or any other audio format capable of storing sounds data (e.g., MP3, RealAudioTM, etc...). Comments may also be converted to text for storage or for transmittal as data packets using protocols such as the Wireless Applications Protocol (WAP) in cases where processing is done in a wireless client and where 10 text transmission is desirable over voice transmittal. When conversion of the comments to text is desired, Speech Recognition Engine 510 may be used to convert the comments to text. In one or more embodiments, annotator 508 provides the user the capability to review comments before saving the comments in the data structure.
15 Process Utilized to ObtainlPlayback Annotations:
Figure 6 provides an example of the process utilized in accordance with one embodiment of the invention to annotate a document. The process may be implemented in hardware and/or software form and may, for example, comprises computer readable program code tangibly embodied in a computer 20 readable medium such as a processor, or memory coupled to the processor. In other instances, the invention executes in memory such as a hard disk, floppy disk, and/or any other form of memory capable of storing computer readable program code. The computer program or hardware device is referred to herein as the system. As will be discussed herein, certain executable and non-executable 25 portions of the files that are used by embodiments of the invention may be distributed or obtained via a network (e.g., a wireless network).
When the system enters an execution state at start point 600 the system waits for input from the user. In accordance with one embodiment of the invention input from the user may require authentication. Authentication provides the system with a way to determine which user made a particular set of comments. If multiple users comment on the document, the authentication data enables the system to discern between comments provided by different users. If authentication is required (e.g., at step 602), the system obtains a unique identifier (e.g., at step 604) from the user or the system associated with the user.
If such authentication is not required, the system allocates a portion of memory to the system for one or more data structures) (e.g., at step 606) associated with the annotations to be provided by the user. One of ordinary skill in the art should recognize that the invention also contemplates embodiments where the system allocates memory earlier or later in the execution process.
Once memory is allocated for the data structure, the system obtains the file that is to be reviewed (e.g., at step 60~). This file typically comprises a document contaiizing data such as text and/or other elements. Documents may, for example, originate as text files (e.g., ASCII, EPSIDIC, etc...), audio files, (e.g., MP3, RealAudioTM, WAV, etc...), image files (e.g., GIF, JPG, TIFF, etc..) movie files (e.g., AVI, MPEG, RM, etc...), or any other type of file containing data the user of the system may wish to review and subsequently comment upon.
When the file to be reviewed (or the location of the file) is loaded into memory the system waits for the user to indicate a desire to playback the file with annotations (e.g., at step 610). If the user initiates (e.g., by depressing a play w/annotations button or stating a verbal command) a command to begin playback with annotations, the system responds by obtaining the unique identifier (e.g. ID(s)) associated with the users) whose comments/annotations the user operating the system wishes to hear. If for example, the user of the system wishes to hear comments from one or more certain individuals, the ID(s) associated with those individuals are supplied to the system at step 612. The system may default to a setting that plays back all the comments associated with the document or in other instances the system may prioritize the comments by playing comments from some individuals prior to comments from others.
When the system identifies which set of comments to obtain it obtains one or more annotations files (e.g., at step 614). The annotations file is accessible in one embodiment of the invention via an index or set of pointers. Thus, the appropriate annotations file may be accessed by utilizing the index to determine the location of the comments the operating user wishes to hear. Each annotations file comprises one or more files that point to or contain comments from one or more users. In one embodiment of the invention, the annotations file contains a list of memory locations, network addresses, or hyperlinks that reference or comprise user comments. The annotations file may contain components located within memory or distributed across multiple computers accessible via a network (e.g., a wireless network). In one instance, comments are made accessible via a computer network such as the Internet or some other mechanism for obtaining digital files having user comments.
If the user has not initiated a command to review the document with annotations, the system bypasses steps 612 and 614 and executes step 616. At step 616, the system prepares a document file for playback. In the instances where the user has previously indicated a desire to listen to the annotations, the system prepares the annotations file and the document file for playback by associating the two files with one another in a playback file. If the user does not want to hear any annotations, the system prepares the document file for playback without any annotations. Both the document file and the annotations files may comprise text, sound, and/or any other type of data. In accordance with one embodiment of the invention the document file originates as text and the annotations files) contains audio data that is related to a particular location in a document. However, both the document file and the annotations file may contain other types of data.
In one embodiment of the invention, the system reviews the type data or contents of the playback file to determine what operations to perform on the playback file. At step 618, the system may determine whether the file is a sound file. If the system encounters a sound file, the system converts the file (e.g., at step 620) from audio data to text data by, using a text-to-speech engine. The location of the text-to-speech processing may vary depending upon the processing capacity of the system that is utilized. The text-to-speech conversion may take place on the computer conducting the playback or on a computer separable from the computer performing the playback. After the text-to-speech conversion occurs, the system plays the audio file (e.g., at step 622) via an audio ' output mechanism. If the system reaches the end of the file (EOF), without the user providing any comments, (e.g., step 624) the system may exit at step 625.
However, if the user indicates a desire to provide comments/annotations (e.g., at step 626) by selecting an annotate button, verbalizing a comment, or by some other mechanism for issuing a command, the system executes step 628 where it pauses playback of the audio associated with the text file and inserts a mark at . , , the appropriate location. The mark identifies the location where the user initiated an annotate command. Once the mark is set, the system obtains comments from the user (e.g., at step 630) via an audio input mechanism such as a microphone. The comment may comprise any type of verbalized or non-verbalized input that can be associated with the document about which the user is commenting upon. A comment about a particular segment of text in the document may, for example, contain reference to a Web address that contains information the reviewer wishes to share. Comments may point to other comments so that each comment may be related to or associated with other types of data. The reviewer may therefore reference other URLs or data in a comment and the user listening to the reviewer's comments may access that data.
The system monitors the input to determine when the user finishes providing the comment. When the user finishes the comment, the system saves the comment in the appropriate location. The system may, for example, place the comment into a memory location associated with the data structure allocated at step 606. In some instances, each comment the user provides is saved in the annotations file and stored at any location capable of storing digital data.
Allocation of Processing Responsibilities:
When a device is configured to obtain document data and/or annotation data over a network (e.g., a cell phone network, wireless network, etc...) so that the user can interact with such data, the type of device attempting to obtain access to the data is important. If, for example, the system has sufficient processing capacity, and the network utilized to connect to the system has a low bandwidth or high cost associated with it, the amount of data sent to the device should be minimized and the processing should be performed on the system. If, however, the system does not have any processing resources or has minimal processing capabilities, the processing should be performed on the computer supplying the document or annotation data (e.g., the server computer).
Figure 7 illustrates the process utilized by an embodiment of the invention to allocate processing responsibilities. The process illustrated begins at step 700 where a determination is made as to whether or not the system attempting to obtain text data from a network source for conversion to audio data and then subsequent playback to the user comprises a smart mobile device.
If the system (e.g., the annotation device) comprises a smart mobile device, the network source, typically document server 402, retrieves the text data from memory (e.g., at step X02) and prepares and transmits the text data to the smart 5 mobile device (e.g., at step 704). In one embodiment of the invention, the smart mobile device performs the annotating engine functions described above. For example, the type of processing performed at the smart mobile device typically comprises a text-to-speech operation that converts the text supplied from the network source into audio data that can be played to the user. Each portion of 10 text may, for example, be processed utilizing Digital Signal Processing (DSP) techniques to enhance the quality of the audio data and/or encode the data into an audio format that the smart mobile system is capable of playing. The smart mobile device may for example, convert the text into an optimized Real AudioTM
file (e.g., streaming media file) prior to playing the file to the user via an 15 embedded or software Real AudioTM player. Once the processing is complete, the smart mobile device transmits some data back to the server (e.g., at step 706) for storage or further processing. For instance, if the user made a comment (e.g., at step 705), the smart mobile device may transmit the users comments as well as the location data associated with the comment back to the server for 20 storage and /or processing purposes. The location data identifies where in relation to the text the user made a comment. The comment comprises the data inserted into the annotations file. It is important to note that the smart mobile device may also send other types of data back to the server for security or authentication purpose. The invention also contemplates the transmission of 25 other types of data needed to maintain the link between the data sources and the smart mobile device.
In the instances where the outcome of step 700 indicates that the system connected to the data source is not a smart mobile device, but is rather a device which contains minimal or non processing capacity (e.g., a payphone or land line phone), the processing may be performed on a computer that has a higher capacity for processing data. Such processing may be performed on the data source or on any other computer accessible via a computer network. The computer tasked with performing such processing obtains the data and then converts the text file into an audio file (e.g., at step X08). The processing performed may also contain routiizes for optimizing the quality of the audio file in view of the device the file is going to be transmitted to. Once the text file is processed, the audio data can be transmitted to the device associated with the user (e.g., step X10). If, for example, the user is at a payphone or some other type of telecommunications device that does not have a mechanism for processing data the audio file created by the server is transmitted to the user at the telecommunications device via the telephone network. The system tasked with performing the processing listens while it is playing back the document to the client for some form of command to start receiving comments (e.g. at step 712). If the user wishes to insert a comment into the document the user may generate a tone or some other sound via a telephone keypad or some other mechanism capable of generating a sound. In one embodiment of the invention, the user may depress a key (e.g., a number such as 1) or a simple verbal ,, statement such as "insert comment" to indicate a desire to make a comment.
Once the system receives the audible command, the system stops transmitting audio data and enters a listening mode. When the system is in a listening mode it picks up any verbal input (e.g., comments or annotations) provided by the user (e.g., at step 714). The system marks the location associated with the user comment and associates the comment with the document the user is commenting about. Once the user finishes providing the comment the system stores the comment in the annotations file for later access. The system may determine that the user has finished commenting when the user is silent for a certain threshold period of time (e.g., 30 seconds, 45 second,1 minute, etc...) or when the user indicates the comment is complete by depressing a key or button on the device that cause an audible noise to be generated.
Smart Client Configuration Figure 8 comprises a schematic of a smart client configuration in accordance with an embodiment of the present invention. As used herein, the smart client possesses processing power and control functions adequate to perform the processing required for the present invention. As shown in Figure
8, smart client 800 encapsulates playback controls 802, memory 504, text/speech conversion 506, and annotator 508 functions. In one or more embodiments, memory 504 may be a removable storage media. In other embodiments, memory 504 is memory device such as random access memory, flash memory, optical memory, etc. For example, a wireless device such as a cellular phone may employ random access memory for temporary storage of the document transmitted as text messages via the wireless application protocol or any similar protocol.
Playback control function 802 is provided by controls available on the smart device. Block 802 also encompasses a speaker and microphone for audio input/output. W the instance where the smart device is a computer terminal, the keyboard functions may provide the controls required for control of document playback, navigation, and annotation. The smart device may be a device built specifically to provide the control functions (e.g. buttons or by use of voice commands) for practicing the present invention. In instances where a cellular phone is used, the keypad may provide the necessary controls for playback.
In one or more embodiments of the present invention, the text/speech conversion block 506 and annotator 508 may be provided as objects from the server to client 800 in the form of Java applets at log in. Java applets are executable objects in the form of bytecodes that are runtime compiled and executed by a Java Virtual Machine (JVM). In the case of a smart device with small footprint (i.e. limited processilzg power and memory), a "K" Virtual Machine (KVM) compiles and executes the applets. The use of Java applets or other form of machine independent code provides the flexibility to perform the processes of the present invention on any smart device with a Virtual Machine.
The Process Utilized by Smart Mobile Device with Limited Memory:
Figure 9 illustrates the process utilized in accordance with one embodiment of the invention to annotate a document on a smart device with limited memory such that document data from the server is sent in packets to the smart client. For example, a wireless device utilizing the Wireless Application Protocol may receive the document in data packets for processing. Other device that are connected to the Internet may utilize protocols such as TCP/IP, UDP, or any other protocol that can encapsulate the contents of the document that is to be commented upon.
The processing performed by the smart device initiates at step 902 where the system obtains a text document and converts the text to audio data. For instance, at step 902 data packets transmitted to the device are processed and converted to speech for playback at step 904. If at step 906 an indication is received to start annotation, processing proceeds to step 908. Indication to start annotation may take any of the form described above such as a tone generated by a key entry or a voice command. Otherwise, playback continues with the process returning back to step 902 to receive more packets of data and continue until playback is complete or a start annotation indication is received.
If a start annotation mark (e.g., an annotation trigger) is received, playback is suspended. At step 908, the current location (i.e. delta location when referring back to the range of the data sent in the data packet under playback in relationship to the original document file) corresponding to the offset in the data packet being processed is noted and the annotator starts recording the annotation at step 910.
At step 912, a determination is made whether a stop annotation trigger indication is received. Stop annotation trigger may be generated in any of the forms described above such as a keypad input or voice command. If the trigger to stop annotation is received, processing proceeds to step 914. Otherwise, the annotator continues recording the incoming comments. At step 914, the delta location, which in one embodiment of the invention comprises the location in the current data packet under playback where the start annotation trigger was received, and the recorded annotation is transmitted to the document server using any desirable protocol. At the document server, the actual document location is determined by adding the offset (i.e. delta location) to the value of the location corresponding to the beginning of the data packet being processed. In one embodiment of the invention, the document server keeps track of the range of data sent in the data packet being processed. Thus, the document server and the annotation device work in connection with each other to identify the appropriate place in the document to insert comments while still synchronizing playback of the document. Processing continues at step 902 until the entire document has been processed or until the user suspends further processing.
Thin-Client Configuration Figure 10 shows a schematic of the thin-client configuration according to one embodiment of the present invention. A user may access the present invention in the thin-client configuration. The thin-client configuration generally 5 implies that little or no processing is performed at the client terminal.
This is generally the case where a user accesses the system through a device like a land telephone or similar devices without sufficient processing power to handle the requirements of annotating engine 500 of Figure 5.
Any device capable of accessing document server 402 (Figure 4) may be 10 used in the thin-client configuration if the user desires to perform some portion of the processing on the doculnent server. For instance a smart client may be used in the thin-client configuration. Any time the user desires that the bulls of the processing be performed on document server 402, the thin-client configuration can be utilized. For example, network traffic considerations may 15 require that a smart-client use a thin-client configuration and thereby perform processing on the server.
In the thin-client configuration processes represented in block 1000 are performed on document server 402. The thin-client 1002 may perform limited processing sueh as generating of playback commands, transmitting and 20 receiving voice commands, generating the annotation start mark command, etc.
For example, where a telephone is used as a client, the keypad buttons may be used for the necessary playback commands. The telephone keypad provides convenient functions for playback control for example, the "#" key may be used as Fast Forward, the "*" key may be used as Rewind, and the numeric keys may 25 be used for other functions. The thin-client may utilize any set of one or more keys to control the various types of playback functions.
Figure 11 is a flow diagram of the processes performed by the document server when interacting with a thin-client device configured to perform annotating. After authentication of the user by the server and document to be played back is retrieved, playback starts at step 1101. For example, the user may be listening to the document through the earpiece of a telephone set. When the playback reaches a point where the user wants to add a comment, the user presses a button designated as the annotate button. This button generates an annotation mark in the form of a tone. In one embodiment of the invention, the annotation mark is referred to as an annotation start mark or an annotation trigger. Playback continues at step 1101 if the server does not receive an annotation start mark. However, if the server receives the annotation start mark at step 1102, it proceeds to step 1103 to synchronize the mark with the server file being played back. Synchronization may take multiple forms. For example, one embodiment may require synchronization back to the beginning of a sentence. Synchronization may also be at the beginning of a sentence since one can assume that a user does not typically want to insert a comment in the middle of a word. However, in some instances the system may allow the user to insert comment in the middle of a word (e.g., to correct the word or add a new word).
At step 1104, the server recor ds the incoming voice comments from the thin client. Recording continues at step 1104 until another annotation mark (e.g., an end annotation mark) is received to signal the end of user comment at step 1105. If the end annotation mark is received, processing continues at step 1106.
In one embodiment, the end annotation mark is triggered by a certain period of silence. At the end of recordation of the comments, the data is saved at step and playback resumes at step 1101 until end of the document is reached or the user indicates a desire to stop the playback. Stop playback may be indicated by simply hanging-up the handset, or the use of a button designated to stop the playback function.
File Structure In one or more embodiments, there are four basic files associated with the annotation of a document as shown in Figure 12. These files comprise the original document 1200 (i.e., the document to be annotated). The Annotations Names File 1202, the Annotations Index File 1204, and the Annotations File 1206.
Document File 1200 comprises the document to be annotated and is not typically modified during annotation. Document file 1200 can also represent a previous annotation (comment) to another document. For example, a user may want to add comments to another user's comments. By adding comments to previous comments, a hierar chy of files and 1W ks is created. For example, for each document being annotated a trio of associations files (e.g., the annotations names file, annotations index file, and annotations file) are created. The result is a hierarchical tree of files with a root at the original document as shown in Figure 13.
In Figure 13, root node 1300 is the original document. The original document may be a book or a movie script, for example. As comments are added to the original document, the annotations names file represented as nodes 1302A-C, annotations index file node 1306, and annotations file node 1304 are created. In one or more embodiments, the comments contained in annotations file 1304 may be annotated thereby creating the children files represented in nodes 1308A-C,1310, and 1312. Comment 1304 is an annotation by NAME1 1302A on the contents of document 1300 whereas comment 1312 is the annotation by NAME61308C on the comments made by NAME1 1302A on document 1300.
Comments 1304 represent a comment in annotations file 1206 for the first level of annotations of the original document. As structured, a second user may comment on any comment in annotations file 1206 made by a previous user.
Therefore, it is possible to have a series of continent 1304 at the same level serving as intermediate nodes to additional comments.
Following the model discussed above, grandchildren and great-grandchildren nodes may be added to the hierarchical tree of annotations. The use of a hierarchical tree in this form makes it possible to add comments upon comments to any desired level, limited only by the memory capacity of the server, while still maintaining the ability to trace back to the original document.
With this tree structure, it is possible to traverse the hierarchical tree to review selective comments using a sophisticated playback controller and annotating engine as described in tlus specification.
Referring back to Figure 12, the annotations names file 1202 contains the identities of the users annotating the document. As discussed above, this document could be a previous comment (i.e. annotation) by another or the same user. In one or more embodiments, a series of alphanumeric characters may be employed for user identification. It is preferable to have unique identification for each user of the system however unique identification is not required. Using unique identifications make it easy to track sources of comments.
There is an annotations index file 1204 for each user (e.g., NAMED in the annotations names file 1202. For example, if there are "N" names in the annotations names file 1202, there will be "N" corresponding annotations index files 1204. Each location (e.g., LOCl) in the annotations index file 1204 contains the location in document file 1200 where a comment is to be inserted, and the location of the comment in the annotations file 1206. That is, each location in the annotations index file 1204 contains two pieces of information. For each location in the annotations index file 1204, there is a location i11 annotations file comprising the corresponding user comment.
Using the file structure presented in Figure 12 provides a method of infinitely storing and tracking the annotations (i.e. comments) made to an original document. Although the file structure described herein is desirable for ease of growth and traversal, however it would be obvious to those of ordinary skill that other file structures may be employed so long as it is conducive to retrieval of user annotations.
Once the comments are stored in the file structure they may be reconstructed upon request by a user. A user may, for example, provide the annotated document to a secretary or some other person in order to finalize the document. In other instances the document is stored for later processing by another person. A description of a general-purpose computer environment that may be utilized to implement various portions of the invention follows:
Embodiment of General Purpose Computer Environment:
An embodiment of the invention can be implemented as computer software in the form of computer readable program code executed on one or more general-purpose computers such as the computer 1400 illustrated in Figure 5 14. A keyboard 1410 and mouse 1411 are coupled to a bi-directional system bus 1418 (e.g." PCI, ISA or other similar architecture). The keyboard and mouse are for introducing user input to the computer system and communicating that user input to central processing unit (CPU) 1413. Other suitable input devices may be used in addition to, or in place of, the mouse 1411 and keyboard 1410. I/O
10 (input/output) unit 1419 coupled to bi-directional system bus 1418 represents possible output devices such as a printer or an A/V (audio/video) device.
Computer 1400 includes video memory 1414, main memory 1415, mass storage 1412, and communication interface 1420. All these devices are coupled to a bi-directional system bus 1418 along with keyboard 1410, mouse 1411 and CPU
15 1413. The mass storage 1412 may include both fixed and removable media, such as magnetic, optical or magnetic optical storage systems or any other available mass storage technology. The system bus 1418 provides a means for addressing video memory 1414 or main memory 1415. The system bus 1418 also provides a mechanism for the CPU to transferring data between and among the 20 components, such as main memory 1415, video memory 1414 and mass storage 1412.
In one embodiment of the invention, the CPU 1413 is a microprocessor manufactured by Motorola, such as the 680X0 processor, an Intel Pentium III
processor, or an UltraSparc processor from Sun Microsystems. However, any 25 other suitable processor or computer may be utilized. Video memory 1414 is a dual ported video random access memory. One port of the video memory 1414 is coupled to video accelerator 1416. The video accelerator device 1416 is used to drive a CRT (cathode ray tube), and LCD (Liquid Crystal Display), or TFT (Thin-Film Transistor) monitor 1417. The video accelerator 1416 is well known in the art and may be implemented by any suitable apparatus. This circuitry converts pixel data stored in video memory 1414 to a signal suitable for use by monitor 1417. The monitor 1417 is a type of monitor suitable for displaying graphic images.
The computer 1400 may also include a communication interface 1420 coupled to the system bus 1418. The communication interface 1420 provides a two-way data communication coupling via a network link 1421 to a network 1422. For example, if the communication interface 1420 is a modem, the communication interface 1420 provides a data communication connection to a corresponding type of telephone line, which comprises part of a network link 1421. If the communication interface 1420 is a Network Interface Card (NIC), communication interface 1420 provides a data communication connection via a network link 1421 to a compatible network. Physical network links can include Ethernet, wireless, fiber optic, and cable television type links. In any such implementation, communication interface 1420 sends and receives electrical, electromagnetic or optical signals which carry digital data streams representing 20' various types of information.
The network link 1421 typically provides data communication through one or more networks to other data devices. For example, network link 1421 may provide a connection through local network 1422 to a host computer 1423 or to data equipment operated by an Internet Service Provider (ISP) 1424. ISP
1424 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the "Internet" 1425. Local network 1422 and Internet 1425 both use electrical, electromagnetic or optical signals that carry digital data streams to files.
The signals through the various networks and the signals on network link 1421 and through communication interface 1420, which carry the digital data to and from computer 1400, are exemplary forms of carrier waves for transporting the digital information.
The computer 1400 can send messages and receive data, including program code, through the network(s), network link 1421, and communication interface 1420. In the Internet example, server 1426 might transmit a requested code for an application program through Internet 1425, ISP 1424, local network 1422 and communication interface 1420.
In one embodiment of the invention a thin-client device is configured to interface with the computer system described above via a computer network. In other instances (e.g., when a smart mobile device is utilized) some or all of the components discussed above are incorporated into the device. It will be evident to one of ordinary skill in the art that the computer systems described above are for purposes of example only. An embodiment of the invention may be implemented in any type of computer system or programming or processing environment.
Thus, a method and apparatus for annotating a document has been described. Particular embodiments described described herein are illustrative only and should not limit the present invention thereby. The claims and their full scope of equivalents define the iilvention.
Playback control function 802 is provided by controls available on the smart device. Block 802 also encompasses a speaker and microphone for audio input/output. W the instance where the smart device is a computer terminal, the keyboard functions may provide the controls required for control of document playback, navigation, and annotation. The smart device may be a device built specifically to provide the control functions (e.g. buttons or by use of voice commands) for practicing the present invention. In instances where a cellular phone is used, the keypad may provide the necessary controls for playback.
In one or more embodiments of the present invention, the text/speech conversion block 506 and annotator 508 may be provided as objects from the server to client 800 in the form of Java applets at log in. Java applets are executable objects in the form of bytecodes that are runtime compiled and executed by a Java Virtual Machine (JVM). In the case of a smart device with small footprint (i.e. limited processilzg power and memory), a "K" Virtual Machine (KVM) compiles and executes the applets. The use of Java applets or other form of machine independent code provides the flexibility to perform the processes of the present invention on any smart device with a Virtual Machine.
The Process Utilized by Smart Mobile Device with Limited Memory:
Figure 9 illustrates the process utilized in accordance with one embodiment of the invention to annotate a document on a smart device with limited memory such that document data from the server is sent in packets to the smart client. For example, a wireless device utilizing the Wireless Application Protocol may receive the document in data packets for processing. Other device that are connected to the Internet may utilize protocols such as TCP/IP, UDP, or any other protocol that can encapsulate the contents of the document that is to be commented upon.
The processing performed by the smart device initiates at step 902 where the system obtains a text document and converts the text to audio data. For instance, at step 902 data packets transmitted to the device are processed and converted to speech for playback at step 904. If at step 906 an indication is received to start annotation, processing proceeds to step 908. Indication to start annotation may take any of the form described above such as a tone generated by a key entry or a voice command. Otherwise, playback continues with the process returning back to step 902 to receive more packets of data and continue until playback is complete or a start annotation indication is received.
If a start annotation mark (e.g., an annotation trigger) is received, playback is suspended. At step 908, the current location (i.e. delta location when referring back to the range of the data sent in the data packet under playback in relationship to the original document file) corresponding to the offset in the data packet being processed is noted and the annotator starts recording the annotation at step 910.
At step 912, a determination is made whether a stop annotation trigger indication is received. Stop annotation trigger may be generated in any of the forms described above such as a keypad input or voice command. If the trigger to stop annotation is received, processing proceeds to step 914. Otherwise, the annotator continues recording the incoming comments. At step 914, the delta location, which in one embodiment of the invention comprises the location in the current data packet under playback where the start annotation trigger was received, and the recorded annotation is transmitted to the document server using any desirable protocol. At the document server, the actual document location is determined by adding the offset (i.e. delta location) to the value of the location corresponding to the beginning of the data packet being processed. In one embodiment of the invention, the document server keeps track of the range of data sent in the data packet being processed. Thus, the document server and the annotation device work in connection with each other to identify the appropriate place in the document to insert comments while still synchronizing playback of the document. Processing continues at step 902 until the entire document has been processed or until the user suspends further processing.
Thin-Client Configuration Figure 10 shows a schematic of the thin-client configuration according to one embodiment of the present invention. A user may access the present invention in the thin-client configuration. The thin-client configuration generally 5 implies that little or no processing is performed at the client terminal.
This is generally the case where a user accesses the system through a device like a land telephone or similar devices without sufficient processing power to handle the requirements of annotating engine 500 of Figure 5.
Any device capable of accessing document server 402 (Figure 4) may be 10 used in the thin-client configuration if the user desires to perform some portion of the processing on the doculnent server. For instance a smart client may be used in the thin-client configuration. Any time the user desires that the bulls of the processing be performed on document server 402, the thin-client configuration can be utilized. For example, network traffic considerations may 15 require that a smart-client use a thin-client configuration and thereby perform processing on the server.
In the thin-client configuration processes represented in block 1000 are performed on document server 402. The thin-client 1002 may perform limited processing sueh as generating of playback commands, transmitting and 20 receiving voice commands, generating the annotation start mark command, etc.
For example, where a telephone is used as a client, the keypad buttons may be used for the necessary playback commands. The telephone keypad provides convenient functions for playback control for example, the "#" key may be used as Fast Forward, the "*" key may be used as Rewind, and the numeric keys may 25 be used for other functions. The thin-client may utilize any set of one or more keys to control the various types of playback functions.
Figure 11 is a flow diagram of the processes performed by the document server when interacting with a thin-client device configured to perform annotating. After authentication of the user by the server and document to be played back is retrieved, playback starts at step 1101. For example, the user may be listening to the document through the earpiece of a telephone set. When the playback reaches a point where the user wants to add a comment, the user presses a button designated as the annotate button. This button generates an annotation mark in the form of a tone. In one embodiment of the invention, the annotation mark is referred to as an annotation start mark or an annotation trigger. Playback continues at step 1101 if the server does not receive an annotation start mark. However, if the server receives the annotation start mark at step 1102, it proceeds to step 1103 to synchronize the mark with the server file being played back. Synchronization may take multiple forms. For example, one embodiment may require synchronization back to the beginning of a sentence. Synchronization may also be at the beginning of a sentence since one can assume that a user does not typically want to insert a comment in the middle of a word. However, in some instances the system may allow the user to insert comment in the middle of a word (e.g., to correct the word or add a new word).
At step 1104, the server recor ds the incoming voice comments from the thin client. Recording continues at step 1104 until another annotation mark (e.g., an end annotation mark) is received to signal the end of user comment at step 1105. If the end annotation mark is received, processing continues at step 1106.
In one embodiment, the end annotation mark is triggered by a certain period of silence. At the end of recordation of the comments, the data is saved at step and playback resumes at step 1101 until end of the document is reached or the user indicates a desire to stop the playback. Stop playback may be indicated by simply hanging-up the handset, or the use of a button designated to stop the playback function.
File Structure In one or more embodiments, there are four basic files associated with the annotation of a document as shown in Figure 12. These files comprise the original document 1200 (i.e., the document to be annotated). The Annotations Names File 1202, the Annotations Index File 1204, and the Annotations File 1206.
Document File 1200 comprises the document to be annotated and is not typically modified during annotation. Document file 1200 can also represent a previous annotation (comment) to another document. For example, a user may want to add comments to another user's comments. By adding comments to previous comments, a hierar chy of files and 1W ks is created. For example, for each document being annotated a trio of associations files (e.g., the annotations names file, annotations index file, and annotations file) are created. The result is a hierarchical tree of files with a root at the original document as shown in Figure 13.
In Figure 13, root node 1300 is the original document. The original document may be a book or a movie script, for example. As comments are added to the original document, the annotations names file represented as nodes 1302A-C, annotations index file node 1306, and annotations file node 1304 are created. In one or more embodiments, the comments contained in annotations file 1304 may be annotated thereby creating the children files represented in nodes 1308A-C,1310, and 1312. Comment 1304 is an annotation by NAME1 1302A on the contents of document 1300 whereas comment 1312 is the annotation by NAME61308C on the comments made by NAME1 1302A on document 1300.
Comments 1304 represent a comment in annotations file 1206 for the first level of annotations of the original document. As structured, a second user may comment on any comment in annotations file 1206 made by a previous user.
Therefore, it is possible to have a series of continent 1304 at the same level serving as intermediate nodes to additional comments.
Following the model discussed above, grandchildren and great-grandchildren nodes may be added to the hierarchical tree of annotations. The use of a hierarchical tree in this form makes it possible to add comments upon comments to any desired level, limited only by the memory capacity of the server, while still maintaining the ability to trace back to the original document.
With this tree structure, it is possible to traverse the hierarchical tree to review selective comments using a sophisticated playback controller and annotating engine as described in tlus specification.
Referring back to Figure 12, the annotations names file 1202 contains the identities of the users annotating the document. As discussed above, this document could be a previous comment (i.e. annotation) by another or the same user. In one or more embodiments, a series of alphanumeric characters may be employed for user identification. It is preferable to have unique identification for each user of the system however unique identification is not required. Using unique identifications make it easy to track sources of comments.
There is an annotations index file 1204 for each user (e.g., NAMED in the annotations names file 1202. For example, if there are "N" names in the annotations names file 1202, there will be "N" corresponding annotations index files 1204. Each location (e.g., LOCl) in the annotations index file 1204 contains the location in document file 1200 where a comment is to be inserted, and the location of the comment in the annotations file 1206. That is, each location in the annotations index file 1204 contains two pieces of information. For each location in the annotations index file 1204, there is a location i11 annotations file comprising the corresponding user comment.
Using the file structure presented in Figure 12 provides a method of infinitely storing and tracking the annotations (i.e. comments) made to an original document. Although the file structure described herein is desirable for ease of growth and traversal, however it would be obvious to those of ordinary skill that other file structures may be employed so long as it is conducive to retrieval of user annotations.
Once the comments are stored in the file structure they may be reconstructed upon request by a user. A user may, for example, provide the annotated document to a secretary or some other person in order to finalize the document. In other instances the document is stored for later processing by another person. A description of a general-purpose computer environment that may be utilized to implement various portions of the invention follows:
Embodiment of General Purpose Computer Environment:
An embodiment of the invention can be implemented as computer software in the form of computer readable program code executed on one or more general-purpose computers such as the computer 1400 illustrated in Figure 5 14. A keyboard 1410 and mouse 1411 are coupled to a bi-directional system bus 1418 (e.g." PCI, ISA or other similar architecture). The keyboard and mouse are for introducing user input to the computer system and communicating that user input to central processing unit (CPU) 1413. Other suitable input devices may be used in addition to, or in place of, the mouse 1411 and keyboard 1410. I/O
10 (input/output) unit 1419 coupled to bi-directional system bus 1418 represents possible output devices such as a printer or an A/V (audio/video) device.
Computer 1400 includes video memory 1414, main memory 1415, mass storage 1412, and communication interface 1420. All these devices are coupled to a bi-directional system bus 1418 along with keyboard 1410, mouse 1411 and CPU
15 1413. The mass storage 1412 may include both fixed and removable media, such as magnetic, optical or magnetic optical storage systems or any other available mass storage technology. The system bus 1418 provides a means for addressing video memory 1414 or main memory 1415. The system bus 1418 also provides a mechanism for the CPU to transferring data between and among the 20 components, such as main memory 1415, video memory 1414 and mass storage 1412.
In one embodiment of the invention, the CPU 1413 is a microprocessor manufactured by Motorola, such as the 680X0 processor, an Intel Pentium III
processor, or an UltraSparc processor from Sun Microsystems. However, any 25 other suitable processor or computer may be utilized. Video memory 1414 is a dual ported video random access memory. One port of the video memory 1414 is coupled to video accelerator 1416. The video accelerator device 1416 is used to drive a CRT (cathode ray tube), and LCD (Liquid Crystal Display), or TFT (Thin-Film Transistor) monitor 1417. The video accelerator 1416 is well known in the art and may be implemented by any suitable apparatus. This circuitry converts pixel data stored in video memory 1414 to a signal suitable for use by monitor 1417. The monitor 1417 is a type of monitor suitable for displaying graphic images.
The computer 1400 may also include a communication interface 1420 coupled to the system bus 1418. The communication interface 1420 provides a two-way data communication coupling via a network link 1421 to a network 1422. For example, if the communication interface 1420 is a modem, the communication interface 1420 provides a data communication connection to a corresponding type of telephone line, which comprises part of a network link 1421. If the communication interface 1420 is a Network Interface Card (NIC), communication interface 1420 provides a data communication connection via a network link 1421 to a compatible network. Physical network links can include Ethernet, wireless, fiber optic, and cable television type links. In any such implementation, communication interface 1420 sends and receives electrical, electromagnetic or optical signals which carry digital data streams representing 20' various types of information.
The network link 1421 typically provides data communication through one or more networks to other data devices. For example, network link 1421 may provide a connection through local network 1422 to a host computer 1423 or to data equipment operated by an Internet Service Provider (ISP) 1424. ISP
1424 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the "Internet" 1425. Local network 1422 and Internet 1425 both use electrical, electromagnetic or optical signals that carry digital data streams to files.
The signals through the various networks and the signals on network link 1421 and through communication interface 1420, which carry the digital data to and from computer 1400, are exemplary forms of carrier waves for transporting the digital information.
The computer 1400 can send messages and receive data, including program code, through the network(s), network link 1421, and communication interface 1420. In the Internet example, server 1426 might transmit a requested code for an application program through Internet 1425, ISP 1424, local network 1422 and communication interface 1420.
In one embodiment of the invention a thin-client device is configured to interface with the computer system described above via a computer network. In other instances (e.g., when a smart mobile device is utilized) some or all of the components discussed above are incorporated into the device. It will be evident to one of ordinary skill in the art that the computer systems described above are for purposes of example only. An embodiment of the invention may be implemented in any type of computer system or programming or processing environment.
Thus, a method and apparatus for annotating a document has been described. Particular embodiments described described herein are illustrative only and should not limit the present invention thereby. The claims and their full scope of equivalents define the iilvention.
Claims (59)
1. An apparatus for annotating a document comprising:
a processor;
memory coupled to said processor, said memory comprising at least one text document;
a document processing engine configured to obtain said at least one text document from said memory and convert at least a portion of said at least one text document to at least one audio file;
an audio output device configured to play said at least one audio file to a first user;
an audio input device configured to obtain at least one verbalized comment from said user about said at least one audio file wherein said at least one verbalized comment is stored as an audio comment file;
an annotator, said annotator configured to associate said audio comment file with a location in said text document that corresponds to said audio file playing when said first user provided said at least one comment.
a processor;
memory coupled to said processor, said memory comprising at least one text document;
a document processing engine configured to obtain said at least one text document from said memory and convert at least a portion of said at least one text document to at least one audio file;
an audio output device configured to play said at least one audio file to a first user;
an audio input device configured to obtain at least one verbalized comment from said user about said at least one audio file wherein said at least one verbalized comment is stored as an audio comment file;
an annotator, said annotator configured to associate said audio comment file with a location in said text document that corresponds to said audio file playing when said first user provided said at least one comment.
2. The apparatus of claim 1 wherein said memory comprises removable media.
3. The apparatus of claim 2 where said removable media comprises flash memory.
4. The apparatus of claim 1 wherein said audio file comprises a streaming media file.
5. The apparatus of claim 1 wherein annotator obtains a start annotation mark from said first user indicating a beginning of said location.
6. The apparatus of claim 5 wherein said annotator obtains an annotation end mark identifying the end of said location.
7. An apparatus for annotating a document comprising:
a server having a text-to-speech engine configured to obtain at least one text document from memory and convert at least a portion of said at least one text document to at least one audio file;
a thin-client device configured to obtain said at least one audio file from said server;
an audio output device configured to play said at least one audio file to a first user, wherein said audio output device is associated with said thin-client;
said thin-client device having an audio input element configured to obtain at least one verbalized comment from said user about said at least one audio file, wherein said at least one verbalized comment is transmitted to said server and stored as an audio comment file on said server;
said server having an annotator, said annotator configured to associate said audio comment file with a location in said text document that corresponds to said audio file playing when said first user provided said at least one comment.
a server having a text-to-speech engine configured to obtain at least one text document from memory and convert at least a portion of said at least one text document to at least one audio file;
a thin-client device configured to obtain said at least one audio file from said server;
an audio output device configured to play said at least one audio file to a first user, wherein said audio output device is associated with said thin-client;
said thin-client device having an audio input element configured to obtain at least one verbalized comment from said user about said at least one audio file, wherein said at least one verbalized comment is transmitted to said server and stored as an audio comment file on said server;
said server having an annotator, said annotator configured to associate said audio comment file with a location in said text document that corresponds to said audio file playing when said first user provided said at least one comment.
8. The apparatus of claim 7 wherein said thin-client device is connected to said server via an interconnection fabric.
9. The apparatus of claim 8 wherein said interconnection fabric comprises a telephone network.
10. The apparatus of claim 9 wherein said interconnection fabric comprises a computer network.
11. The apparatus of claim 9 wherein said thin-client comprises a telephone.
12. The apparatus of claim 9 wherein said audio comment file is stored in at least one associations file.
13. The apparatus of claim 9 wherein said annotator is associated with a Speech Recognition Engine configured to obtain said audio comment file and convert said verbalized comment back to text.
14. The apparatus of claim 9 wherein said server comprises a voice command interface.
15. The apparatus of claim 9 wherein said server is configured to mark the beginning of said verbalized comment upon receipt of a start annotation mark.
16. The apparatus of claim 15 wherein said server is configured to mark the end of said verbalized comment upon receipt of an end annotation mark.
17. The apparatus of claim 16 wherein said audio comment file comprises data recorded by said server between receipt of said start annotation mark and said end annotation mark.
18. A method for annotating a document comprising:
obtaining a document from a memory medium via an interconnection path configured to access said document;
converting said document to audio elements;
presenting an audible playback of said audio elements to a user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon receipt of an annotation start mark during said audible playback;
associating said verbalized comments with a location in said document corresponding with the occurrence of said annotation start mark during said audible playback.
obtaining a document from a memory medium via an interconnection path configured to access said document;
converting said document to audio elements;
presenting an audible playback of said audio elements to a user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon receipt of an annotation start mark during said audible playback;
associating said verbalized comments with a location in said document corresponding with the occurrence of said annotation start mark during said audible playback.
19. The method of claim 18 wherein said document comprises text data.
20. The method of claim 18 wherein said memory medium comprises removable media.
21. The method of claim 20 wherein said removable media comprises flash memory.
22. The method of claim 20 wherein said interconnection path comprises a network.
23. The method of claim 20 wherein said network comprises a wireless network.
24. The method of claim 20 wherein said network comprises a telephone network.
25. The method of claim 24 wherein said telephone network comprises a cellular network.
26. The method of claim 18 wherein a document processing engine performs said converting step.
27. The method of claim 26 wherein said document processing engine optimizes said audio elements.
28. The method of claim 18 wherein said converting said document to audio elements occurs at a server.
29. The method of claim 28 wherein said server generates an audio file associated with said presenting said audible playback of said audio elements.
30. The method of claim 18 wherein said converting said document to audio elements occurs at a client.
31. The method of claim 29 wherein said client generates an audio file associated with said presenting said audible playback of audio elements.
32. A method for annotating a document comprising:
obtaining a document from a memory medium via an interconnection path configured to access said document, said document having text elements;
obtaining a first annotation of said text document, said first annotation having a first set of audio elements;
converting said text elements to a second set of audio elements;
associating said first set of audio elements with said second set of audio elements to generate a playback document;
generating an audible playback of said playback document to a user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon activation of an annotation trigger during said audible playback;
associating said verbalized comments with a location in said playback document corresponding with the occurrence of said annotation trigger during said audible playback.
obtaining a document from a memory medium via an interconnection path configured to access said document, said document having text elements;
obtaining a first annotation of said text document, said first annotation having a first set of audio elements;
converting said text elements to a second set of audio elements;
associating said first set of audio elements with said second set of audio elements to generate a playback document;
generating an audible playback of said playback document to a user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon activation of an annotation trigger during said audible playback;
associating said verbalized comments with a location in said playback document corresponding with the occurrence of said annotation trigger during said audible playback.
33. The method of claim 32 wherein said document comprises text data.
34. The method of claim 32 wherein said memory medium comprises removable media.
35. The method of claim 34 wherein said removable media comprises flash memory.
36. The method of claim 32 wherein said interconnection path comprises a network.
37. The method of claim 36 wherein said network comprises a wireless network.
38. The method of claim 36 wherein said network comprises a telephone network.
39. The method of claim 38 wherein said telephone network comprises a cellular network.
40. The method of claim 32 wherein a document processing engine performs said converting step.
41. The method of claim 40 wherein said document processing engine optimizes said audio elements.
42. The method of claim 32 wherein said converting said document to audio elements occurs at a server.
43. The method of claim 42 wherein said server generates an audio file associated with said presenting said audible playback of said audio elements.
44. The method of claim 32 wherein said converting said document to audio elements occurs at a client.
45. The method of claim 44 wherein said client generates an audio file associated with said presenting said audible playback of audio elements.
46. A method for annotating a document comprising:
generating authentication information of a user desiring access to a document;
allocating an associations file structure for said user;
obtaining said document from a memory medium via an interconnection path configured to access said document, said document having text elements;
obtaining a first annotation of said text document, said first annotation having a first set of audio elements;
converting said text elements to a second set of audio elements;
associating said first set of audio elements with said second set of audio elements to generate a playback document;
generating an audible playback of said playback document to said user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon activation of an annotation trigger during said audible playback;
associating said verbalized comments with a location in said playback document corresponding with the occurrence of said annotation trigger during said audible playback; and storing said location and said authentication information of said user and said verbalized comments in said associations file structure.
generating authentication information of a user desiring access to a document;
allocating an associations file structure for said user;
obtaining said document from a memory medium via an interconnection path configured to access said document, said document having text elements;
obtaining a first annotation of said text document, said first annotation having a first set of audio elements;
converting said text elements to a second set of audio elements;
associating said first set of audio elements with said second set of audio elements to generate a playback document;
generating an audible playback of said playback document to said user when said user indicates a desire to hear said document;
obtaining verbalized comments from said user via an audio input mechanism upon activation of an annotation trigger during said audible playback;
associating said verbalized comments with a location in said playback document corresponding with the occurrence of said annotation trigger during said audible playback; and storing said location and said authentication information of said user and said verbalized comments in said associations file structure.
47. The method of claim 46 wherein said document comprises text data.
48. The method of claim 46 wherein said memory medium comprises removable media.
49. The method of claim 48 wherein said removable media comprises flash memory.
50. The method of claim 48 wherein said interconnection path comprises a network.
51. The method of claim 50 wherein said network comprises a wireless network.
52. The method of claim 50 wherein said network comprises a telephone network.
53. The method of claim 52 wherein said telephone network comprises a cellular network.
54. The method of claim 46 wherein a document processing engine performs said converting.
55. The method of claim 46 wherein said document processing engine optimizes said audio elements.
56. The method of claim 46 wherein said converting said document to audio elements occurs at a server.
57. The method of claim 56 wherein said server generates an audio file associated with said presenting said audible playback of said audio elements.
58. The method of claim 46 wherein said converting said document to audio elements occurs at a client.
59. The method of claim 58 wherein said client generates an audio file associated with said presenting said audible playback of audio elements.
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US09/802,395 US7366979B2 (en) | 2001-03-09 | 2001-03-09 | Method and apparatus for annotating a document |
US09/802,395 | 2001-03-09 | ||
PCT/US2002/007222 WO2002073353A2 (en) | 2001-03-09 | 2002-03-07 | Method and apparatus for annotating a document with audio comments |
Publications (1)
Publication Number | Publication Date |
---|---|
CA2440291A1 true CA2440291A1 (en) | 2002-09-19 |
Family
ID=25183581
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CA002440291A Abandoned CA2440291A1 (en) | 2001-03-09 | 2002-03-07 | Method and apparatus for annotating a document with audio comments |
Country Status (5)
Country | Link |
---|---|
US (5) | US7366979B2 (en) |
EP (2) | EP2390783B1 (en) |
JP (2) | JP2005506602A (en) |
CA (1) | CA2440291A1 (en) |
WO (1) | WO2002073353A2 (en) |
Families Citing this family (459)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8645137B2 (en) | 2000-03-16 | 2014-02-04 | Apple Inc. | Fast, language-independent method for user authentication by voice |
US7487112B2 (en) | 2000-06-29 | 2009-02-03 | Barnes Jr Melvin L | System, method, and computer program product for providing location based services and mobile e-commerce |
US7366979B2 (en) * | 2001-03-09 | 2008-04-29 | Copernicus Investments, Llc | Method and apparatus for annotating a document |
US7392287B2 (en) * | 2001-03-27 | 2008-06-24 | Hemisphere Ii Investment Lp | Method and apparatus for sharing information using a handheld device |
EP1535392A4 (en) | 2001-07-18 | 2009-09-16 | Wireless Generation Inc | System and method for real-time observation assessment |
US20030018662A1 (en) * | 2001-07-19 | 2003-01-23 | Sheng Li | Synchronizing multimedia data |
US7885987B1 (en) * | 2001-08-28 | 2011-02-08 | Lee Eugene M | Computer-implemented method and system for managing attributes of intellectual property documents, optionally including organization thereof |
US7747943B2 (en) * | 2001-09-07 | 2010-06-29 | Microsoft Corporation | Robust anchoring of annotations to content |
US20090106251A1 (en) * | 2001-10-24 | 2009-04-23 | Harris Scott C | Web based communication of information with reconfigurable format |
US8504652B2 (en) * | 2006-04-10 | 2013-08-06 | Portulim Foundation Llc | Method and system for selectively supplying media content to a user and media storage device for use therein |
US8909729B2 (en) * | 2001-11-20 | 2014-12-09 | Portulim Foundation Llc | System and method for sharing digital media content |
US8122466B2 (en) * | 2001-11-20 | 2012-02-21 | Portulim Foundation Llc | System and method for updating digital media content |
US7711774B1 (en) * | 2001-11-20 | 2010-05-04 | Reagan Inventions Llc | Interactive, multi-user media delivery system |
US7503059B1 (en) * | 2001-12-28 | 2009-03-10 | Rothschild Trust Holdings, Llc | Method of enhancing media content and a media enhancement system |
US20070022465A1 (en) * | 2001-11-20 | 2007-01-25 | Rothschild Trust Holdings, Llc | System and method for marking digital media content |
JP2003157206A (en) | 2001-11-21 | 2003-05-30 | Nec Corp | System and method for distributing information and program |
JP2004153299A (en) * | 2001-12-13 | 2004-05-27 | Ricoh Co Ltd | Program, recording medium, information recording apparatus, and information recording method |
US6996558B2 (en) | 2002-02-26 | 2006-02-07 | International Business Machines Corporation | Application portability and extensibility through database schema and query abstraction |
US20030214528A1 (en) * | 2002-03-15 | 2003-11-20 | Pitney Bowes Incorporated | Method for managing the annotation of documents |
US20030204498A1 (en) * | 2002-04-30 | 2003-10-30 | Lehnert Bernd R. | Customer interaction reporting |
US7219164B2 (en) * | 2002-05-17 | 2007-05-15 | University Of Miami | Multimedia re-editor |
US8611919B2 (en) | 2002-05-23 | 2013-12-17 | Wounder Gmbh., Llc | System, method, and computer program product for providing location based services and mobile e-commerce |
US10489449B2 (en) | 2002-05-23 | 2019-11-26 | Gula Consulting Limited Liability Company | Computer accepting voice input and/or generating audible output |
US7392267B2 (en) * | 2002-12-04 | 2008-06-24 | International Business Machines Corporation | Annotation validity using partial checksums |
US7536713B1 (en) * | 2002-12-11 | 2009-05-19 | Alan Bartholomew | Knowledge broadcasting and classification system |
US20040122843A1 (en) * | 2002-12-19 | 2004-06-24 | Terris John F. | XML browser markup and collaboration |
KR100490734B1 (en) * | 2002-12-21 | 2005-05-24 | 한국전자통신연구원 | Annotation-based automatic document generation apparatus and method |
US7966554B2 (en) * | 2003-03-11 | 2011-06-21 | Thomson Financial Llc | Financial disclosure content synchronizing software |
US7216266B2 (en) * | 2003-03-12 | 2007-05-08 | Thomson Licensing | Change request form annotation |
JP4250983B2 (en) * | 2003-03-13 | 2009-04-08 | 富士ゼロックス株式会社 | Device for associating user data with continuous data |
US7269787B2 (en) * | 2003-04-28 | 2007-09-11 | International Business Machines Coporation | Multi-document context aware annotation system |
US7620648B2 (en) * | 2003-06-20 | 2009-11-17 | International Business Machines Corporation | Universal annotation configuration and deployment |
JP2005027048A (en) * | 2003-07-02 | 2005-01-27 | Minolta Co Ltd | Imaging apparatus and method for providing annotation information to image |
US20050021339A1 (en) * | 2003-07-24 | 2005-01-27 | Siemens Information And Communication Networks, Inc. | Annotations addition to documents rendered via text-to-speech conversion over a voice connection |
US7418656B1 (en) * | 2003-10-03 | 2008-08-26 | Adobe Systems Incorporated | Dynamic annotations for electronics documents |
US20050097451A1 (en) * | 2003-11-03 | 2005-05-05 | Cormack Christopher J. | Annotating media content with user-specified information |
US20050114357A1 (en) * | 2003-11-20 | 2005-05-26 | Rathinavelu Chengalvarayan | Collaborative media indexing system and method |
US7900133B2 (en) | 2003-12-09 | 2011-03-01 | International Business Machines Corporation | Annotation structure type determination |
JP2005190088A (en) * | 2003-12-25 | 2005-07-14 | Matsushita Electric Ind Co Ltd | E-mail processor and e-mail processing system |
US7343552B2 (en) * | 2004-02-12 | 2008-03-11 | Fuji Xerox Co., Ltd. | Systems and methods for freeform annotations |
US7669117B2 (en) * | 2004-03-18 | 2010-02-23 | International Business Machines Corporation | Method and system for creation and retrieval of global annotations |
US20130304453A9 (en) * | 2004-08-20 | 2013-11-14 | Juergen Fritsch | Automated Extraction of Semantic Content and Generation of a Structured Document from Speech |
US7584103B2 (en) * | 2004-08-20 | 2009-09-01 | Multimodal Technologies, Inc. | Automated extraction of semantic content and generation of a structured document from speech |
US7885955B2 (en) | 2005-08-23 | 2011-02-08 | Ricoh Co. Ltd. | Shared document annotation |
US7672543B2 (en) * | 2005-08-23 | 2010-03-02 | Ricoh Co., Ltd. | Triggering applications based on a captured text in a mixed media environment |
US8838591B2 (en) * | 2005-08-23 | 2014-09-16 | Ricoh Co., Ltd. | Embedding hot spots in electronic documents |
US8521737B2 (en) | 2004-10-01 | 2013-08-27 | Ricoh Co., Ltd. | Method and system for multi-tier image matching in a mixed media environment |
US7970171B2 (en) * | 2007-01-18 | 2011-06-28 | Ricoh Co., Ltd. | Synthetic image and video generation from ground truth data |
US8856108B2 (en) * | 2006-07-31 | 2014-10-07 | Ricoh Co., Ltd. | Combining results of image retrieval processes |
US8156427B2 (en) | 2005-08-23 | 2012-04-10 | Ricoh Co. Ltd. | User interface for mixed media reality |
US8332401B2 (en) | 2004-10-01 | 2012-12-11 | Ricoh Co., Ltd | Method and system for position-based image matching in a mixed media environment |
US8005831B2 (en) * | 2005-08-23 | 2011-08-23 | Ricoh Co., Ltd. | System and methods for creation and use of a mixed media environment with geographic location information |
US9405751B2 (en) * | 2005-08-23 | 2016-08-02 | Ricoh Co., Ltd. | Database for mixed media document system |
US8868555B2 (en) * | 2006-07-31 | 2014-10-21 | Ricoh Co., Ltd. | Computation of a recongnizability score (quality predictor) for image retrieval |
US8965145B2 (en) | 2006-07-31 | 2015-02-24 | Ricoh Co., Ltd. | Mixed media reality recognition using multiple specialized indexes |
US8176054B2 (en) | 2007-07-12 | 2012-05-08 | Ricoh Co. Ltd | Retrieving electronic documents by converting them to synthetic text |
US7812986B2 (en) * | 2005-08-23 | 2010-10-12 | Ricoh Co. Ltd. | System and methods for use of voice mail and email in a mixed media environment |
US7991778B2 (en) * | 2005-08-23 | 2011-08-02 | Ricoh Co., Ltd. | Triggering actions with captured input in a mixed media environment |
US9373029B2 (en) * | 2007-07-11 | 2016-06-21 | Ricoh Co., Ltd. | Invisible junction feature recognition for document security or annotation |
US7669148B2 (en) * | 2005-08-23 | 2010-02-23 | Ricoh Co., Ltd. | System and methods for portable device for mixed media system |
US8276088B2 (en) * | 2007-07-11 | 2012-09-25 | Ricoh Co., Ltd. | User interface for three-dimensional navigation |
US8086038B2 (en) * | 2007-07-11 | 2011-12-27 | Ricoh Co., Ltd. | Invisible junction features for patch recognition |
US7551780B2 (en) * | 2005-08-23 | 2009-06-23 | Ricoh Co., Ltd. | System and method for using individualized mixed document |
US9530050B1 (en) | 2007-07-11 | 2016-12-27 | Ricoh Co., Ltd. | Document annotation sharing |
US8144921B2 (en) * | 2007-07-11 | 2012-03-27 | Ricoh Co., Ltd. | Information retrieval using invisible junctions and geometric constraints |
US9384619B2 (en) * | 2006-07-31 | 2016-07-05 | Ricoh Co., Ltd. | Searching media content for objects specified using identifiers |
US8510283B2 (en) * | 2006-07-31 | 2013-08-13 | Ricoh Co., Ltd. | Automatic adaption of an image recognition system to image capture devices |
US8156115B1 (en) | 2007-07-11 | 2012-04-10 | Ricoh Co. Ltd. | Document-based networking with mixed media reality |
US8156116B2 (en) | 2006-07-31 | 2012-04-10 | Ricoh Co., Ltd | Dynamic presentation of targeted information in a mixed media reality recognition system |
US8184155B2 (en) | 2007-07-11 | 2012-05-22 | Ricoh Co. Ltd. | Recognition and tracking using invisible junctions |
US7702673B2 (en) * | 2004-10-01 | 2010-04-20 | Ricoh Co., Ltd. | System and methods for creation and use of a mixed media environment |
US8949287B2 (en) * | 2005-08-23 | 2015-02-03 | Ricoh Co., Ltd. | Embedding hot spots in imaged documents |
US9171202B2 (en) * | 2005-08-23 | 2015-10-27 | Ricoh Co., Ltd. | Data organization and access for mixed media document system |
US7920759B2 (en) * | 2005-08-23 | 2011-04-05 | Ricoh Co. Ltd. | Triggering applications for distributed action execution and use of mixed media recognition as a control input |
US8369655B2 (en) * | 2006-07-31 | 2013-02-05 | Ricoh Co., Ltd. | Mixed media reality recognition using multiple specialized indexes |
US8825682B2 (en) * | 2006-07-31 | 2014-09-02 | Ricoh Co., Ltd. | Architecture for mixed media reality retrieval of locations and registration of images |
US7587412B2 (en) * | 2005-08-23 | 2009-09-08 | Ricoh Company, Ltd. | Mixed media reality brokerage network and methods of use |
US8385589B2 (en) * | 2008-05-15 | 2013-02-26 | Berna Erol | Web-based content detection in images, extraction and recognition |
US8335789B2 (en) | 2004-10-01 | 2012-12-18 | Ricoh Co., Ltd. | Method and system for document fingerprint matching in a mixed media environment |
US8195659B2 (en) | 2005-08-23 | 2012-06-05 | Ricoh Co. Ltd. | Integration and use of mixed media documents |
US8600989B2 (en) | 2004-10-01 | 2013-12-03 | Ricoh Co., Ltd. | Method and system for image matching in a mixed media environment |
US7639387B2 (en) * | 2005-08-23 | 2009-12-29 | Ricoh Co., Ltd. | Authoring tools using a mixed media environment |
US7917554B2 (en) * | 2005-08-23 | 2011-03-29 | Ricoh Co. Ltd. | Visibly-perceptible hot spots in documents |
US8443279B1 (en) * | 2004-10-13 | 2013-05-14 | Stryker Corporation | Voice-responsive annotation of video generated by an endoscopic camera |
US8225335B2 (en) | 2005-01-05 | 2012-07-17 | Microsoft Corporation | Processing files from a mobile device |
US20070236505A1 (en) * | 2005-01-31 | 2007-10-11 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resampling of transformed shared image techniques |
US9910341B2 (en) | 2005-01-31 | 2018-03-06 | The Invention Science Fund I, Llc | Shared image device designation |
US9082456B2 (en) | 2005-01-31 | 2015-07-14 | The Invention Science Fund I Llc | Shared image device designation |
US9489717B2 (en) | 2005-01-31 | 2016-11-08 | Invention Science Fund I, Llc | Shared image device |
US20060285150A1 (en) * | 2005-01-31 | 2006-12-21 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Regional proximity for shared image device(s) |
US20060171603A1 (en) * | 2005-01-31 | 2006-08-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Resampling of transformed shared image techniques |
US20060221197A1 (en) * | 2005-03-30 | 2006-10-05 | Jung Edward K | Image transformation estimator of an imaging device |
US20060187228A1 (en) * | 2005-01-31 | 2006-08-24 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Sharing including peripheral shared image device |
US8606383B2 (en) | 2005-01-31 | 2013-12-10 | The Invention Science Fund I, Llc | Audio sharing |
US8902320B2 (en) | 2005-01-31 | 2014-12-02 | The Invention Science Fund I, Llc | Shared image device synchronization or designation |
US7920169B2 (en) * | 2005-01-31 | 2011-04-05 | Invention Science Fund I, Llc | Proximity of shared image devices |
US20060170956A1 (en) | 2005-01-31 | 2006-08-03 | Jung Edward K | Shared image devices |
US9124729B2 (en) | 2005-01-31 | 2015-09-01 | The Invention Science Fund I, Llc | Shared image device synchronization or designation |
US20060190968A1 (en) * | 2005-01-31 | 2006-08-24 | Searete Llc, A Limited Corporation Of The State Of The State Of Delaware | Sharing between shared audio devices |
US7876357B2 (en) * | 2005-01-31 | 2011-01-25 | The Invention Science Fund I, Llc | Estimating shared image device operational capabilities or resources |
US9325781B2 (en) | 2005-01-31 | 2016-04-26 | Invention Science Fund I, Llc | Audio sharing |
US20060174203A1 (en) | 2005-01-31 | 2006-08-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Viewfinder for shared image device |
US20060187227A1 (en) * | 2005-01-31 | 2006-08-24 | Jung Edward K | Storage aspects for imaging device |
CA2636258A1 (en) * | 2005-02-14 | 2006-08-24 | Teresis Media Management, Inc. | Multipurpose media players |
US8577683B2 (en) | 2008-08-15 | 2013-11-05 | Thomas Majchrowski & Associates, Inc. | Multipurpose media players |
US20070098348A1 (en) * | 2005-10-31 | 2007-05-03 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Degradation/preservation management of captured data |
US8253821B2 (en) * | 2005-10-31 | 2012-08-28 | The Invention Science Fund I, Llc | Degradation/preservation management of captured data |
US9967424B2 (en) | 2005-06-02 | 2018-05-08 | Invention Science Fund I, Llc | Data storage usage protocol |
US9076208B2 (en) * | 2006-02-28 | 2015-07-07 | The Invention Science Fund I, Llc | Imagery processing |
US20070222865A1 (en) | 2006-03-15 | 2007-09-27 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Enhanced video/still image correlation |
US9191611B2 (en) * | 2005-06-02 | 2015-11-17 | Invention Science Fund I, Llc | Conditional alteration of a saved image |
US8233042B2 (en) * | 2005-10-31 | 2012-07-31 | The Invention Science Fund I, Llc | Preservation and/or degradation of a video/audio data stream |
US8072501B2 (en) * | 2005-10-31 | 2011-12-06 | The Invention Science Fund I, Llc | Preservation and/or degradation of a video/audio data stream |
US7872675B2 (en) * | 2005-06-02 | 2011-01-18 | The Invention Science Fund I, Llc | Saved-image management |
US9819490B2 (en) | 2005-05-04 | 2017-11-14 | Invention Science Fund I, Llc | Regional proximity for shared image device(s) |
US7782365B2 (en) | 2005-06-02 | 2010-08-24 | Searete Llc | Enhanced video/still image correlation |
US9451200B2 (en) | 2005-06-02 | 2016-09-20 | Invention Science Fund I, Llc | Storage access technique for captured data |
US8681225B2 (en) * | 2005-06-02 | 2014-03-25 | Royce A. Levien | Storage access technique for captured data |
US9167195B2 (en) * | 2005-10-31 | 2015-10-20 | Invention Science Fund I, Llc | Preservation/degradation of video/audio aspects of a data stream |
US9001215B2 (en) | 2005-06-02 | 2015-04-07 | The Invention Science Fund I, Llc | Estimating shared image device operational capabilities or resources |
US9942511B2 (en) | 2005-10-31 | 2018-04-10 | Invention Science Fund I, Llc | Preservation/degradation of video/audio aspects of a data stream |
US8964054B2 (en) * | 2006-08-18 | 2015-02-24 | The Invention Science Fund I, Llc | Capturing selected image objects |
US10003762B2 (en) | 2005-04-26 | 2018-06-19 | Invention Science Fund I, Llc | Shared image devices |
US9621749B2 (en) | 2005-06-02 | 2017-04-11 | Invention Science Fund I, Llc | Capturing selected image objects |
US8015009B2 (en) * | 2005-05-04 | 2011-09-06 | Joel Jay Harband | Speech derived from text in computer presentation applications |
US20060259930A1 (en) * | 2005-05-10 | 2006-11-16 | Rothschild Leigh M | System and method for obtaining information on digital media content |
US20060274153A1 (en) * | 2005-06-02 | 2006-12-07 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Third party storage of captured data |
US7610545B2 (en) * | 2005-06-06 | 2009-10-27 | Bea Systems, Inc. | Annotations for tracking provenance |
US20060293089A1 (en) * | 2005-06-22 | 2006-12-28 | Magix Ag | System and method for automatic creation of digitally enhanced ringtones for cellphones |
JP2007004896A (en) * | 2005-06-23 | 2007-01-11 | Toshiba Corp | Information storage medium, information transfer method, information reproducing method, and information recording method |
US20070022098A1 (en) * | 2005-07-25 | 2007-01-25 | Dale Malik | Systems and methods for automatically updating annotations and marked content of an information search |
US20070022135A1 (en) * | 2005-07-25 | 2007-01-25 | Dale Malik | Systems and methods for organizing and annotating an information search |
US7769772B2 (en) * | 2005-08-23 | 2010-08-03 | Ricoh Co., Ltd. | Mixed media reality brokerage network with layout-independent recognition |
US7779347B2 (en) * | 2005-09-02 | 2010-08-17 | Fourteen40, Inc. | Systems and methods for collaboratively annotating electronic documents |
US8677377B2 (en) | 2005-09-08 | 2014-03-18 | Apple Inc. | Method and apparatus for building an intelligent automated assistant |
US20070203595A1 (en) * | 2006-02-28 | 2007-08-30 | Searete Llc, A Limited Liability Corporation | Data management of an audio data stream |
US20070120980A1 (en) * | 2005-10-31 | 2007-05-31 | Searete Llc, A Limited Liability Corporation Of The State Of Delaware | Preservation/degradation of video/audio aspects of a data stream |
US20070124142A1 (en) * | 2005-11-25 | 2007-05-31 | Mukherjee Santosh K | Voice enabled knowledge system |
KR100719514B1 (en) * | 2005-12-20 | 2007-05-17 | 엔에이치엔(주) | Method and system for sorting/searching file and record media therefor |
US8036889B2 (en) * | 2006-02-27 | 2011-10-11 | Nuance Communications, Inc. | Systems and methods for filtering dictated and non-dictated sections of documents |
US7823069B1 (en) * | 2006-03-23 | 2010-10-26 | Cisco Technology, Inc. | Method and application tool for dynamically navigating a user customizable representation of a network device configuration |
US7735101B2 (en) * | 2006-03-28 | 2010-06-08 | Cisco Technology, Inc. | System allowing users to embed comments at specific points in time into media presentation |
US20070256008A1 (en) * | 2006-04-26 | 2007-11-01 | Bedingfield James C Sr | Methods, systems, and computer program products for managing audio information |
EP2018618A1 (en) * | 2006-05-09 | 2009-01-28 | Koninklijke Philips Electronics N.V. | A device and a method for annotating content |
GB0610119D0 (en) * | 2006-05-20 | 2006-06-28 | Ibm | Internet browser and method of bookmarking in same |
JP4124243B2 (en) * | 2006-06-05 | 2008-07-23 | セイコーエプソン株式会社 | Storage element manufacturing method, storage element, storage device, electronic device, and transistor manufacturing method |
WO2007150005A2 (en) | 2006-06-22 | 2007-12-27 | Multimodal Technologies, Inc. | Automatic decision support |
US11853374B2 (en) | 2006-06-22 | 2023-12-26 | Rohit Chandra | Directly, automatically embedding a content portion |
US11301532B2 (en) | 2006-06-22 | 2022-04-12 | Rohit Chandra | Searching for user selected portions of content |
US11429685B2 (en) | 2006-06-22 | 2022-08-30 | Rohit Chandra | Sharing only a part of a web page—the part selected by a user |
US8301995B2 (en) * | 2006-06-22 | 2012-10-30 | Csr Technology Inc. | Labeling and sorting items of digital data by use of attached annotations |
JPWO2008001500A1 (en) * | 2006-06-30 | 2009-11-26 | 日本電気株式会社 | Audio content generation system, information exchange system, program, audio content generation method, and information exchange method |
US20080033735A1 (en) * | 2006-07-20 | 2008-02-07 | William Bryan Graham | System and method for recording and distributing audio renditions of scripts |
US8676810B2 (en) * | 2006-07-31 | 2014-03-18 | Ricoh Co., Ltd. | Multiple index mixed media reality recognition using unequal priority indexes |
US8073263B2 (en) * | 2006-07-31 | 2011-12-06 | Ricoh Co., Ltd. | Multi-classifier selection and monitoring for MMR-based image recognition |
US9176984B2 (en) * | 2006-07-31 | 2015-11-03 | Ricoh Co., Ltd | Mixed media reality retrieval of differentially-weighted links |
US8489987B2 (en) * | 2006-07-31 | 2013-07-16 | Ricoh Co., Ltd. | Monitoring and analyzing creation and usage of visual content using image and hotspot interaction |
US9020966B2 (en) * | 2006-07-31 | 2015-04-28 | Ricoh Co., Ltd. | Client device for interacting with a mixed media reality recognition system |
US8201076B2 (en) * | 2006-07-31 | 2012-06-12 | Ricoh Co., Ltd. | Capturing symbolic information from documents upon printing |
US9063952B2 (en) * | 2006-07-31 | 2015-06-23 | Ricoh Co., Ltd. | Mixed media reality recognition with image tracking |
US9318108B2 (en) | 2010-01-18 | 2016-04-19 | Apple Inc. | Intelligent automated assistant |
JP4668875B2 (en) * | 2006-09-20 | 2011-04-13 | 株式会社日立製作所 | Program recording / playback apparatus, program playback position control method, and program information providing apparatus |
US20080091719A1 (en) * | 2006-10-13 | 2008-04-17 | Robert Thomas Arenburg | Audio tags |
US20080147604A1 (en) * | 2006-12-15 | 2008-06-19 | Info Services Llc | Voice Documentation And Analysis Linking |
US8515757B2 (en) * | 2007-03-20 | 2013-08-20 | Nuance Communications, Inc. | Indexing digitized speech with words represented in the digitized speech |
US8977255B2 (en) | 2007-04-03 | 2015-03-10 | Apple Inc. | Method and system for operating a multi-function portable electronic device using voice-activation |
US20080270406A1 (en) * | 2007-04-27 | 2008-10-30 | International Business Machines Corporation | System and method for adding comments to knowledge documents and expediting formal authoring of content |
US20080276159A1 (en) * | 2007-05-01 | 2008-11-06 | International Business Machines Corporation | Creating Annotated Recordings and Transcripts of Presentations Using a Mobile Device |
US8351380B2 (en) * | 2007-05-09 | 2013-01-08 | Samsung Electronics Co., Ltd | Method and apparatus for layer 2 ARQ for packets |
US8504908B2 (en) * | 2007-10-17 | 2013-08-06 | ITI Scotland, Limited | Computer-implemented methods displaying, in a first part, a document and in a second part, a selected index of entities identified in the document |
US8898558B2 (en) * | 2007-12-07 | 2014-11-25 | Hewlett-Packard Development Company, L.P. | Managing multimodal annotations of an image |
US20090164572A1 (en) * | 2007-12-20 | 2009-06-25 | Motorola, Inc. | Apparatus and method for content item annotation |
US10002189B2 (en) | 2007-12-20 | 2018-06-19 | Apple Inc. | Method and apparatus for searching using an active ontology |
US9330720B2 (en) | 2008-01-03 | 2016-05-03 | Apple Inc. | Methods and apparatus for altering audio output signals |
WO2009105735A2 (en) * | 2008-02-21 | 2009-08-27 | Globalenglish Corporation | Web-based tool for collaborative, social learning |
US20090251440A1 (en) * | 2008-04-03 | 2009-10-08 | Livescribe, Inc. | Audio Bookmarking |
US8996376B2 (en) | 2008-04-05 | 2015-03-31 | Apple Inc. | Intelligent text-to-speech conversion |
US7610202B1 (en) * | 2008-04-21 | 2009-10-27 | Nuance Communications, Inc. | Integrated system and method for mobile audio playback and dictation |
JP5455321B2 (en) * | 2008-05-02 | 2014-03-26 | キヤノン株式会社 | Document processing apparatus and document processing method |
US10496753B2 (en) | 2010-01-18 | 2019-12-03 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
US8321784B1 (en) | 2008-05-30 | 2012-11-27 | Adobe Systems Incorporated | Reviewing objects |
US9390169B2 (en) * | 2008-06-28 | 2016-07-12 | Apple Inc. | Annotation of movies |
US20100017694A1 (en) * | 2008-07-18 | 2010-01-21 | Electronic Data Systems Corporation | Apparatus, and associated method, for creating and annotating content |
US10127231B2 (en) | 2008-07-22 | 2018-11-13 | At&T Intellectual Property I, L.P. | System and method for rich media annotation |
US9251281B2 (en) * | 2008-07-29 | 2016-02-02 | International Business Machines Corporation | Web browsing using placemarks and contextual relationships in a data processing system |
US20100030549A1 (en) | 2008-07-31 | 2010-02-04 | Lee Michael M | Mobile device having human language translation capability with positional feedback |
US20100042615A1 (en) * | 2008-08-12 | 2010-02-18 | Peter Rinearson | Systems and methods for aggregating content on a user-content driven website |
US8171411B1 (en) | 2008-08-18 | 2012-05-01 | National CineMedia LLC | System and method for delivering content in a movie trailer |
US8676904B2 (en) | 2008-10-02 | 2014-03-18 | Apple Inc. | Electronic devices with voice command and contextual data processing capabilities |
US8201074B2 (en) * | 2008-10-08 | 2012-06-12 | Microsoft Corporation | Talking paper authoring tools |
JP5385596B2 (en) * | 2008-11-25 | 2014-01-08 | キヤノン株式会社 | EDITING DEVICE, ITS CONTROL METHOD, AND IMAGING DEVICE |
US8532269B2 (en) * | 2009-01-16 | 2013-09-10 | Microsoft Corporation | In-band signaling in interactive communications |
US20130124242A1 (en) | 2009-01-28 | 2013-05-16 | Adobe Systems Incorporated | Video review workflow process |
US9292481B2 (en) * | 2009-02-27 | 2016-03-22 | Adobe Systems Incorporated | Creating and modifying a snapshot of an electronic document with a user comment |
US8930843B2 (en) | 2009-02-27 | 2015-01-06 | Adobe Systems Incorporated | Electronic content workflow review process |
US9274624B2 (en) * | 2009-03-31 | 2016-03-01 | Ricoh Company, Ltd. | Annotating digital files of a host computer using networked tablet computers |
US9134947B2 (en) | 2009-03-31 | 2015-09-15 | Ricoh Company, Ltd. | Annotating digital files of a host computer using a peripheral device |
US9836276B2 (en) * | 2009-05-27 | 2017-12-05 | Hon Hai Precision Industry Co., Ltd. | Voice command processing method and electronic device utilizing the same |
US8943408B2 (en) | 2009-05-27 | 2015-01-27 | Adobe Systems Incorporated | Text image review process |
US8943431B2 (en) | 2009-05-27 | 2015-01-27 | Adobe Systems Incorporated | Text operations in a bitmap-based document |
US10255566B2 (en) | 2011-06-03 | 2019-04-09 | Apple Inc. | Generating and processing task items that represent tasks to perform |
US10241644B2 (en) | 2011-06-03 | 2019-03-26 | Apple Inc. | Actionable reminder entries |
US9858925B2 (en) | 2009-06-05 | 2018-01-02 | Apple Inc. | Using context information to facilitate processing of commands in a virtual assistant |
US10241752B2 (en) | 2011-09-30 | 2019-03-26 | Apple Inc. | Interface for a virtual digital assistant |
US8290777B1 (en) * | 2009-06-12 | 2012-10-16 | Amazon Technologies, Inc. | Synchronizing the playing and displaying of digital content |
KR101236476B1 (en) * | 2009-06-15 | 2013-02-28 | 한국전자통신연구원 | Method and apparatus for displaying search data |
US8385660B2 (en) * | 2009-06-24 | 2013-02-26 | Ricoh Co., Ltd. | Mixed media reality indexing and retrieval for repeated content |
US8510247B1 (en) | 2009-06-30 | 2013-08-13 | Amazon Technologies, Inc. | Recommendation of media content items based on geolocation and venue |
US9153141B1 (en) | 2009-06-30 | 2015-10-06 | Amazon Technologies, Inc. | Recommendations based on progress data |
US9390402B1 (en) | 2009-06-30 | 2016-07-12 | Amazon Technologies, Inc. | Collection of progress data |
US9431006B2 (en) | 2009-07-02 | 2016-08-30 | Apple Inc. | Methods and apparatuses for automatic speech recognition |
US20110035383A1 (en) * | 2009-08-06 | 2011-02-10 | Ghimire Shankar R | Advanced Text to Speech Patent Search Engine |
US8745067B2 (en) * | 2009-08-12 | 2014-06-03 | Google Inc. | Presenting comments from various sources |
US8958685B2 (en) * | 2009-08-17 | 2015-02-17 | Avaya Inc. | Word cloud audio navigation |
US20110087703A1 (en) * | 2009-10-09 | 2011-04-14 | Satyam Computer Services Limited Of Mayfair Center | System and method for deep annotation and semantic indexing of videos |
US20110093263A1 (en) * | 2009-10-20 | 2011-04-21 | Mowzoon Shahin M | Automated Video Captioning |
US8558919B2 (en) | 2009-12-30 | 2013-10-15 | Blackberry Limited | Filing digital images using voice input |
US10705794B2 (en) | 2010-01-18 | 2020-07-07 | Apple Inc. | Automatically adapting user interfaces for hands-free interaction |
US10553209B2 (en) | 2010-01-18 | 2020-02-04 | Apple Inc. | Systems and methods for hands-free notification summaries |
US10679605B2 (en) | 2010-01-18 | 2020-06-09 | Apple Inc. | Hands-free list-reading by intelligent automated assistant |
US10276170B2 (en) | 2010-01-18 | 2019-04-30 | Apple Inc. | Intelligent automated assistant |
DE202011111062U1 (en) | 2010-01-25 | 2019-02-19 | Newvaluexchange Ltd. | Device and system for a digital conversation management platform |
US8406745B1 (en) * | 2010-01-28 | 2013-03-26 | Sprint Communications Company L.P. | Synchronization of voice mail greeting and email auto-reply by a wireless communication device |
CN101799994B (en) * | 2010-02-10 | 2012-12-19 | 惠州Tcl移动通信有限公司 | Voice note recording method of e-book reader |
US8682667B2 (en) | 2010-02-25 | 2014-03-25 | Apple Inc. | User profiling for selecting user specific voice input processing information |
JP5464048B2 (en) * | 2010-05-24 | 2014-04-09 | 株式会社ナカヨ通信機 | Document proofreading support device |
CN102262890A (en) * | 2010-05-31 | 2011-11-30 | 鸿富锦精密工业(深圳)有限公司 | Electronic device and marking method thereof |
WO2011156719A1 (en) * | 2010-06-10 | 2011-12-15 | Logoscope, Llc | System and method for conversion of speech to displayed media data |
JP4924754B2 (en) | 2010-06-21 | 2012-04-25 | 住友金属鉱山株式会社 | Method for removing copper ions from copper-containing nickel chloride solution and method for producing electrolytic nickel |
US8744239B2 (en) | 2010-08-06 | 2014-06-03 | Apple Inc. | Teleprompter tool for voice-over tool |
US8959102B2 (en) | 2010-10-08 | 2015-02-17 | Mmodal Ip Llc | Structured searching of dynamic structured document corpuses |
US20120131131A1 (en) * | 2010-11-18 | 2012-05-24 | Samsung Electronics Co. Ltd. | Sharing of mobile code information |
US20120159351A1 (en) * | 2010-12-21 | 2012-06-21 | International Business Machines Corporation | Multiple reviews of graphical user interfaces |
US9800941B2 (en) * | 2011-01-03 | 2017-10-24 | Curt Evans | Text-synchronized media utilization and manipulation for transcripts |
US20130334300A1 (en) | 2011-01-03 | 2013-12-19 | Curt Evans | Text-synchronized media utilization and manipulation based on an embedded barcode |
US8782513B2 (en) | 2011-01-24 | 2014-07-15 | Apple Inc. | Device, method, and graphical user interface for navigating through an electronic document |
US9262612B2 (en) | 2011-03-21 | 2016-02-16 | Apple Inc. | Device access using voice authentication |
US8326338B1 (en) | 2011-03-29 | 2012-12-04 | OnAir3G Holdings Ltd. | Synthetic radio channel utilizing mobile telephone networks and VOIP |
KR101397562B1 (en) * | 2011-05-30 | 2014-05-30 | 이해성 | Apparatus for processing user annotations and electronic book service system for the same |
TWI488174B (en) * | 2011-06-03 | 2015-06-11 | Apple Inc | Automatically creating a mapping between text data and audio data |
US10672399B2 (en) | 2011-06-03 | 2020-06-02 | Apple Inc. | Switching between text data and audio data based on a mapping |
US10057736B2 (en) | 2011-06-03 | 2018-08-21 | Apple Inc. | Active transport based notifications |
US9058331B2 (en) | 2011-07-27 | 2015-06-16 | Ricoh Co., Ltd. | Generating a conversation in a social network based on visual search results |
US8994660B2 (en) | 2011-08-29 | 2015-03-31 | Apple Inc. | Text correction processing |
US9240180B2 (en) | 2011-12-01 | 2016-01-19 | At&T Intellectual Property I, L.P. | System and method for low-latency web-based text-to-speech without plugins |
JP5710464B2 (en) * | 2011-12-27 | 2015-04-30 | 株式会社東芝 | Electronic device, display method, and program |
CN102541692A (en) * | 2011-12-31 | 2012-07-04 | 中兴通讯股份有限公司 | Method for adding remarks to backup data and terminal with backup function |
US20130178961A1 (en) * | 2012-01-05 | 2013-07-11 | Microsoft Corporation | Facilitating personal audio productions |
US8989495B2 (en) | 2012-02-28 | 2015-03-24 | Sony Corporation | Capturing metadata on set using a smart pen |
US10134385B2 (en) | 2012-03-02 | 2018-11-20 | Apple Inc. | Systems and methods for name pronunciation |
US9483461B2 (en) | 2012-03-06 | 2016-11-01 | Apple Inc. | Handling speech synthesis of content for multiple languages |
US9864482B2 (en) * | 2012-03-13 | 2018-01-09 | Cognilore Inc. | Method of navigating through digital content |
USD726735S1 (en) * | 2012-03-30 | 2015-04-14 | Sony Corporation | Display screen with graphical user interface |
US20140129221A1 (en) * | 2012-03-23 | 2014-05-08 | Dwango Co., Ltd. | Sound recognition device, non-transitory computer readable storage medium stored threreof sound recognition program, and sound recognition method |
JP5820320B2 (en) * | 2012-03-27 | 2015-11-24 | 株式会社東芝 | Information processing terminal and method, and information management apparatus and method |
US9628573B1 (en) | 2012-05-01 | 2017-04-18 | Amazon Technologies, Inc. | Location-based interaction with digital works |
US9412372B2 (en) * | 2012-05-08 | 2016-08-09 | SpeakWrite, LLC | Method and system for audio-video integration |
US9280610B2 (en) | 2012-05-14 | 2016-03-08 | Apple Inc. | Crowd sourcing information to fulfill user requests |
US10417037B2 (en) | 2012-05-15 | 2019-09-17 | Apple Inc. | Systems and methods for integrating third party services with a digital assistant |
WO2013180437A1 (en) * | 2012-05-28 | 2013-12-05 | Samsung Electronics Co., Ltd. | A method and system for enhancing user experience during an ongoing content viewing activity |
US9721563B2 (en) | 2012-06-08 | 2017-08-01 | Apple Inc. | Name recognition system |
US9495129B2 (en) | 2012-06-29 | 2016-11-15 | Apple Inc. | Device, method, and user interface for voice-activated navigation and browsing of a document |
US20140033040A1 (en) * | 2012-07-24 | 2014-01-30 | Apple Inc. | Portable device with capability for note taking while outputting content |
US9264501B1 (en) | 2012-09-17 | 2016-02-16 | Audible, Inc. | Shared group consumption of the same content |
US9378474B1 (en) * | 2012-09-17 | 2016-06-28 | Audible, Inc. | Architecture for shared content consumption interactions |
US9547647B2 (en) | 2012-09-19 | 2017-01-17 | Apple Inc. | Voice-based media searching |
US9384290B1 (en) | 2012-11-02 | 2016-07-05 | Google Inc. | Local mobile memo for non-interrupting link noting |
WO2014121234A2 (en) * | 2013-02-03 | 2014-08-07 | Study Outloud Llc | Method and apparatus for contextual text to speech conversion |
KR20230137475A (en) | 2013-02-07 | 2023-10-04 | 애플 인크. | Voice trigger for a digital assistant |
US9934200B1 (en) * | 2013-02-28 | 2018-04-03 | Ca, Inc. | Method and system for implementing dynamic note formatting and display |
KR101952179B1 (en) | 2013-03-05 | 2019-05-22 | 엘지전자 주식회사 | Mobile terminal and control method for the mobile terminal |
US9766905B2 (en) * | 2013-03-20 | 2017-09-19 | Microsoft Technology Licensing, Llc | Flexible pluralization of localized text |
US9390079B1 (en) | 2013-05-10 | 2016-07-12 | D.R. Systems, Inc. | Voice commands for report editing |
US20140350928A1 (en) * | 2013-05-21 | 2014-11-27 | Microsoft Corporation | Method For Finding Elements In A Webpage Suitable For Use In A Voice User Interface |
WO2014197336A1 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for detecting errors in interactions with a voice-based digital assistant |
WO2014197334A2 (en) | 2013-06-07 | 2014-12-11 | Apple Inc. | System and method for user-specified pronunciation of words for speech synthesis and recognition |
US9582608B2 (en) | 2013-06-07 | 2017-02-28 | Apple Inc. | Unified ranking with entropy-weighted information for phrase-based semantic auto-completion |
WO2014197335A1 (en) | 2013-06-08 | 2014-12-11 | Apple Inc. | Interpreting and acting upon commands that involve sharing information with remote devices |
US10176167B2 (en) | 2013-06-09 | 2019-01-08 | Apple Inc. | System and method for inferring user intent from speech inputs |
EP3937002A1 (en) | 2013-06-09 | 2022-01-12 | Apple Inc. | Device, method, and graphical user interface for enabling conversation persistence across two or more instances of a digital assistant |
US10891428B2 (en) * | 2013-07-25 | 2021-01-12 | Autodesk, Inc. | Adapting video annotations to playback speed |
US10545657B2 (en) | 2013-09-03 | 2020-01-28 | Apple Inc. | User interface for manipulating user interface objects |
WO2015040743A1 (en) * | 2013-09-20 | 2015-03-26 | 株式会社東芝 | Annotation sharing method, annotation sharing device, and annotation sharing program |
US20150100502A1 (en) * | 2013-10-08 | 2015-04-09 | Tunnls LLC | System and method for pitching and evaluating scripts |
US9898451B2 (en) | 2013-11-26 | 2018-02-20 | Adobe Systems Incorporated | Content adaptation based on selected reviewer comment |
US10296160B2 (en) | 2013-12-06 | 2019-05-21 | Apple Inc. | Method for extracting salient dialog usage from live data |
US9792276B2 (en) * | 2013-12-13 | 2017-10-17 | International Business Machines Corporation | Content availability for natural language processing tasks |
US10224056B1 (en) | 2013-12-17 | 2019-03-05 | Amazon Technologies, Inc. | Contingent device actions during loss of network connectivity |
US20150242182A1 (en) * | 2014-02-24 | 2015-08-27 | Honeywell International Inc. | Voice augmentation for industrial operator consoles |
US9442720B2 (en) * | 2014-02-26 | 2016-09-13 | Paypal, Inc. | Adding on-the-fly comments to code |
TWI510940B (en) * | 2014-05-09 | 2015-12-01 | Univ Nan Kai Technology | Image browsing device for establishing note by voice signal and method thereof |
US9785630B2 (en) | 2014-05-30 | 2017-10-10 | Apple Inc. | Text prediction using combined word N-gram and unigram language models |
US10170123B2 (en) | 2014-05-30 | 2019-01-01 | Apple Inc. | Intelligent assistant for home automation |
AU2015266863B2 (en) | 2014-05-30 | 2018-03-15 | Apple Inc. | Multi-command single utterance input method |
US10078631B2 (en) | 2014-05-30 | 2018-09-18 | Apple Inc. | Entropy-guided text prediction using combined word and character n-gram language models |
US9715875B2 (en) | 2014-05-30 | 2017-07-25 | Apple Inc. | Reducing the need for manual start/end-pointing and trigger phrases |
US9633004B2 (en) | 2014-05-30 | 2017-04-25 | Apple Inc. | Better resolution when referencing to concepts |
US9430463B2 (en) | 2014-05-30 | 2016-08-30 | Apple Inc. | Exemplar-based natural language processing |
KR101929372B1 (en) | 2014-05-30 | 2018-12-17 | 애플 인크. | Transition from use of one device to another |
US9760559B2 (en) | 2014-05-30 | 2017-09-12 | Apple Inc. | Predictive text input |
US9842101B2 (en) | 2014-05-30 | 2017-12-12 | Apple Inc. | Predictive conversion of language input |
US9691385B2 (en) * | 2014-06-19 | 2017-06-27 | Nuance Communications, Inc. | Methods and apparatus for associating dictation with an electronic record |
CN105306501A (en) * | 2014-06-26 | 2016-02-03 | 国际商业机器公司 | Method and system for performing interactive update on multimedia data |
US9338493B2 (en) | 2014-06-30 | 2016-05-10 | Apple Inc. | Intelligent automated assistant for TV user interactions |
US10659851B2 (en) | 2014-06-30 | 2020-05-19 | Apple Inc. | Real-time digital assistant knowledge updates |
US10446141B2 (en) | 2014-08-28 | 2019-10-15 | Apple Inc. | Automatic speech recognition based on user feedback |
USD789419S1 (en) | 2014-09-01 | 2017-06-13 | Apple Inc. | Display screen or portion thereof with graphical user interface |
US10073590B2 (en) | 2014-09-02 | 2018-09-11 | Apple Inc. | Reduced size user interface |
US10114521B2 (en) | 2014-09-02 | 2018-10-30 | Apple Inc. | Multi-dimensional object rearrangement |
US9818400B2 (en) | 2014-09-11 | 2017-11-14 | Apple Inc. | Method and apparatus for discovering trending terms in speech requests |
US10789041B2 (en) | 2014-09-12 | 2020-09-29 | Apple Inc. | Dynamic thresholds for always listening speech trigger |
US9646609B2 (en) | 2014-09-30 | 2017-05-09 | Apple Inc. | Caching apparatus for serving phonetic pronunciations |
US10074360B2 (en) | 2014-09-30 | 2018-09-11 | Apple Inc. | Providing an indication of the suitability of speech recognition |
US9886432B2 (en) | 2014-09-30 | 2018-02-06 | Apple Inc. | Parsimonious handling of word inflection via categorical stem + suffix N-gram language models |
US10127911B2 (en) | 2014-09-30 | 2018-11-13 | Apple Inc. | Speaker identification and unsupervised speaker adaptation techniques |
US9668121B2 (en) | 2014-09-30 | 2017-05-30 | Apple Inc. | Social reminders |
US10114810B2 (en) | 2014-12-01 | 2018-10-30 | Workiva Inc. | Methods and a computing device for maintaining comments and graphical annotations for a document |
US9922048B1 (en) | 2014-12-01 | 2018-03-20 | Securus Technologies, Inc. | Automated background check via facial recognition |
US10552013B2 (en) | 2014-12-02 | 2020-02-04 | Apple Inc. | Data detection |
US20160162136A1 (en) * | 2014-12-04 | 2016-06-09 | Kobo Incorporated | Method and system for e-book reading-launch interface |
US9575750B2 (en) * | 2014-12-11 | 2017-02-21 | Successfactors, Inc. | Generic annotation seeker |
US10152299B2 (en) | 2015-03-06 | 2018-12-11 | Apple Inc. | Reducing response latency of intelligent automated assistants |
US9865280B2 (en) | 2015-03-06 | 2018-01-09 | Apple Inc. | Structured dictation using intelligent automated assistants |
US10567477B2 (en) | 2015-03-08 | 2020-02-18 | Apple Inc. | Virtual assistant continuity |
US9886953B2 (en) | 2015-03-08 | 2018-02-06 | Apple Inc. | Virtual assistant activation |
US9721566B2 (en) | 2015-03-08 | 2017-08-01 | Apple Inc. | Competing devices responding to voice triggers |
US9412394B1 (en) | 2015-03-09 | 2016-08-09 | Jigen Labs, LLC | Interactive audio communication system |
US10950329B2 (en) | 2015-03-13 | 2021-03-16 | Mmodal Ip Llc | Hybrid human and computer-assisted coding workflow |
US9899019B2 (en) | 2015-03-18 | 2018-02-20 | Apple Inc. | Systems and methods for structured stem and suffix language models |
EP3073487A1 (en) * | 2015-03-27 | 2016-09-28 | Ricoh Company, Ltd. | Computer-implemented method, device and system for converting text data into speech data |
KR102324074B1 (en) * | 2015-04-08 | 2021-11-09 | 삼성전자주식회사 | Method for controlling sound output and an electronic device thereof |
US9842105B2 (en) | 2015-04-16 | 2017-12-12 | Apple Inc. | Parsimonious continuous-space phrase representations for natural language processing |
US10460227B2 (en) | 2015-05-15 | 2019-10-29 | Apple Inc. | Virtual assistant in a communication session |
US10083688B2 (en) | 2015-05-27 | 2018-09-25 | Apple Inc. | Device voice control for selecting a displayed affordance |
US10127220B2 (en) | 2015-06-04 | 2018-11-13 | Apple Inc. | Language identification from short strings |
USD773510S1 (en) | 2015-06-05 | 2016-12-06 | Apple Inc. | Display screen or portion thereof with graphical user interface |
US10101822B2 (en) | 2015-06-05 | 2018-10-16 | Apple Inc. | Language input correction |
US9578173B2 (en) | 2015-06-05 | 2017-02-21 | Apple Inc. | Virtual assistant aided communication with 3rd party service in a communication session |
US10186254B2 (en) | 2015-06-07 | 2019-01-22 | Apple Inc. | Context-based endpoint detection |
US11025565B2 (en) | 2015-06-07 | 2021-06-01 | Apple Inc. | Personalized prediction of responses for instant messaging |
US10255907B2 (en) | 2015-06-07 | 2019-04-09 | Apple Inc. | Automatic accent detection using acoustic models |
US20160378747A1 (en) | 2015-06-29 | 2016-12-29 | Apple Inc. | Virtual assistant for media playback |
CN106409295B (en) * | 2015-07-31 | 2020-06-16 | 腾讯科技(深圳)有限公司 | Method and device for recognizing time information from natural voice information |
US10671428B2 (en) | 2015-09-08 | 2020-06-02 | Apple Inc. | Distributed personal assistant |
US10747498B2 (en) | 2015-09-08 | 2020-08-18 | Apple Inc. | Zero latency digital assistant |
US9697820B2 (en) | 2015-09-24 | 2017-07-04 | Apple Inc. | Unit-selection text-to-speech synthesis using concatenation-sensitive neural networks |
US11010550B2 (en) | 2015-09-29 | 2021-05-18 | Apple Inc. | Unified language modeling framework for word prediction, auto-completion and auto-correction |
US10366158B2 (en) | 2015-09-29 | 2019-07-30 | Apple Inc. | Efficient word encoding for recurrent neural network language models |
US11587559B2 (en) | 2015-09-30 | 2023-02-21 | Apple Inc. | Intelligent device identification |
US10691473B2 (en) | 2015-11-06 | 2020-06-23 | Apple Inc. | Intelligent automated assistant in a messaging environment |
US11120342B2 (en) | 2015-11-10 | 2021-09-14 | Ricoh Company, Ltd. | Electronic meeting intelligence |
US10049668B2 (en) | 2015-12-02 | 2018-08-14 | Apple Inc. | Applying neural network language models to weighted finite state transducers for automatic speech recognition |
US10223066B2 (en) | 2015-12-23 | 2019-03-05 | Apple Inc. | Proactive assistance based on dialog communication between devices |
US10446143B2 (en) | 2016-03-14 | 2019-10-15 | Apple Inc. | Identification of voice inputs providing credentials |
US10444934B2 (en) | 2016-03-18 | 2019-10-15 | Audioeye, Inc. | Modular systems and methods for selectively enabling cloud-based assistive technologies |
US11727195B2 (en) | 2016-03-18 | 2023-08-15 | Audioeye, Inc. | Modular systems and methods for selectively enabling cloud-based assistive technologies |
US10423709B1 (en) | 2018-08-16 | 2019-09-24 | Audioeye, Inc. | Systems, devices, and methods for automated and programmatic creation and deployment of remediations to non-compliant web pages or user interfaces |
US10867120B1 (en) | 2016-03-18 | 2020-12-15 | Audioeye, Inc. | Modular systems and methods for selectively enabling cloud-based assistive technologies |
US10896286B2 (en) | 2016-03-18 | 2021-01-19 | Audioeye, Inc. | Modular systems and methods for selectively enabling cloud-based assistive technologies |
US20170285930A1 (en) * | 2016-04-01 | 2017-10-05 | Microsoft Technology Licensing, Llc. | Document content replay |
US9934775B2 (en) | 2016-05-26 | 2018-04-03 | Apple Inc. | Unit-selection text-to-speech synthesis based on predicted concatenation parameters |
US20170345410A1 (en) * | 2016-05-26 | 2017-11-30 | Tyler Murray Smith | Text to speech system with real-time amendment capability |
US9972304B2 (en) | 2016-06-03 | 2018-05-15 | Apple Inc. | Privacy preserving distributed evaluation framework for embedded personalized systems |
US11227589B2 (en) | 2016-06-06 | 2022-01-18 | Apple Inc. | Intelligent list reading |
US10249300B2 (en) | 2016-06-06 | 2019-04-02 | Apple Inc. | Intelligent list reading |
US10049663B2 (en) | 2016-06-08 | 2018-08-14 | Apple, Inc. | Intelligent automated assistant for media exploration |
DK179588B1 (en) | 2016-06-09 | 2019-02-22 | Apple Inc. | Intelligent automated assistant in a home environment |
US10192552B2 (en) | 2016-06-10 | 2019-01-29 | Apple Inc. | Digital assistant providing whispered speech |
US10509862B2 (en) | 2016-06-10 | 2019-12-17 | Apple Inc. | Dynamic phrase expansion of language input |
US10586535B2 (en) | 2016-06-10 | 2020-03-10 | Apple Inc. | Intelligent digital assistant in a multi-tasking environment |
US10637986B2 (en) | 2016-06-10 | 2020-04-28 | Apple Inc. | Displaying and updating a set of application views |
US10490187B2 (en) | 2016-06-10 | 2019-11-26 | Apple Inc. | Digital assistant providing automated status report |
US10067938B2 (en) | 2016-06-10 | 2018-09-04 | Apple Inc. | Multilingual word prediction |
DK179049B1 (en) | 2016-06-11 | 2017-09-18 | Apple Inc | Data driven natural language event detection and classification |
DK201670595A1 (en) | 2016-06-11 | 2018-01-22 | Apple Inc | Configuring context-specific user interfaces |
DK179415B1 (en) | 2016-06-11 | 2018-06-14 | Apple Inc | Intelligent device arbitration and control |
DK179343B1 (en) | 2016-06-11 | 2018-05-14 | Apple Inc | Intelligent task discovery |
DK201670540A1 (en) | 2016-06-11 | 2018-01-08 | Apple Inc | Application integration with a digital assistant |
US10474753B2 (en) | 2016-09-07 | 2019-11-12 | Apple Inc. | Language identification using recurrent neural networks |
US10043516B2 (en) | 2016-09-23 | 2018-08-07 | Apple Inc. | Intelligent automated assistant |
US11307735B2 (en) | 2016-10-11 | 2022-04-19 | Ricoh Company, Ltd. | Creating agendas for electronic meetings using artificial intelligence |
US11281993B2 (en) | 2016-12-05 | 2022-03-22 | Apple Inc. | Model and ensemble compression for metric learning |
CN108231058A (en) * | 2016-12-17 | 2018-06-29 | 鸿富锦精密电子(天津)有限公司 | Voice auxiliary testing system and voice auxiliary test methods |
US10593346B2 (en) | 2016-12-22 | 2020-03-17 | Apple Inc. | Rank-reduced token representation for automatic speech recognition |
US11204787B2 (en) | 2017-01-09 | 2021-12-21 | Apple Inc. | Application integration with a digital assistant |
EP3364311A1 (en) * | 2017-02-15 | 2018-08-22 | Televic Education NV | Visualisation system |
US10475438B1 (en) * | 2017-03-02 | 2019-11-12 | Amazon Technologies, Inc. | Contextual text-to-speech processing |
US10754910B2 (en) * | 2017-03-07 | 2020-08-25 | Enemy Tree LLC | Digital multimedia pinpoint bookmark device, method, and system |
US10417266B2 (en) | 2017-05-09 | 2019-09-17 | Apple Inc. | Context-aware ranking of intelligent response suggestions |
DK201770383A1 (en) | 2017-05-09 | 2018-12-14 | Apple Inc. | User interface for correcting recognition errors |
US10692494B2 (en) * | 2017-05-10 | 2020-06-23 | Sattam Dasgupta | Application-independent content translation |
US10395654B2 (en) | 2017-05-11 | 2019-08-27 | Apple Inc. | Text normalization based on a data-driven learning network |
US10726832B2 (en) | 2017-05-11 | 2020-07-28 | Apple Inc. | Maintaining privacy of personal information |
DK201770439A1 (en) | 2017-05-11 | 2018-12-13 | Apple Inc. | Offline personal assistant |
DK179496B1 (en) | 2017-05-12 | 2019-01-15 | Apple Inc. | USER-SPECIFIC Acoustic Models |
DK201770429A1 (en) | 2017-05-12 | 2018-12-14 | Apple Inc. | Low-latency intelligent automated assistant |
US11301477B2 (en) | 2017-05-12 | 2022-04-12 | Apple Inc. | Feedback analysis of a digital assistant |
DK179745B1 (en) | 2017-05-12 | 2019-05-01 | Apple Inc. | SYNCHRONIZATION AND TASK DELEGATION OF A DIGITAL ASSISTANT |
DK201770431A1 (en) | 2017-05-15 | 2018-12-20 | Apple Inc. | Optimizing dialogue policy decisions for digital assistants using implicit feedback |
DK201770432A1 (en) | 2017-05-15 | 2018-12-21 | Apple Inc. | Hierarchical belief states for digital assistants |
DK179560B1 (en) | 2017-05-16 | 2019-02-18 | Apple Inc. | Far-field extension for digital assistant services |
US10311144B2 (en) | 2017-05-16 | 2019-06-04 | Apple Inc. | Emoji word sense disambiguation |
US10303715B2 (en) | 2017-05-16 | 2019-05-28 | Apple Inc. | Intelligent automated assistant for media exploration |
US10403278B2 (en) | 2017-05-16 | 2019-09-03 | Apple Inc. | Methods and systems for phonetic matching in digital assistant services |
US10860786B2 (en) * | 2017-06-01 | 2020-12-08 | Global Tel*Link Corporation | System and method for analyzing and investigating communication data from a controlled environment |
US10657328B2 (en) | 2017-06-02 | 2020-05-19 | Apple Inc. | Multi-task recurrent neural network architecture for efficient morphology handling in neural language modeling |
US10679627B2 (en) | 2017-07-28 | 2020-06-09 | Bank Of America Corporation | Processing system for intelligently linking messages using markers based on language data |
US10490193B2 (en) | 2017-07-28 | 2019-11-26 | Bank Of America Corporation | Processing system using intelligent messaging flow markers based on language data |
US20190065615A1 (en) * | 2017-08-28 | 2019-02-28 | Bridgit, S.P.C. | System for creating and retrieving contextual links between user interface objects |
US10445429B2 (en) | 2017-09-21 | 2019-10-15 | Apple Inc. | Natural language understanding using vocabularies with compressed serialized tries |
US10755051B2 (en) | 2017-09-29 | 2020-08-25 | Apple Inc. | Rule-based natural language processing |
US11030585B2 (en) | 2017-10-09 | 2021-06-08 | Ricoh Company, Ltd. | Person detection, person identification and meeting start for interactive whiteboard appliances |
CN107808007A (en) * | 2017-11-16 | 2018-03-16 | 百度在线网络技术(北京)有限公司 | Information processing method and device |
US10636424B2 (en) | 2017-11-30 | 2020-04-28 | Apple Inc. | Multi-turn canned dialog |
US10733982B2 (en) | 2018-01-08 | 2020-08-04 | Apple Inc. | Multi-directional dialog |
US10733375B2 (en) | 2018-01-31 | 2020-08-04 | Apple Inc. | Knowledge-based framework for improving natural language understanding |
US10789959B2 (en) | 2018-03-02 | 2020-09-29 | Apple Inc. | Training speaker recognition models for digital assistants |
US10592604B2 (en) | 2018-03-12 | 2020-03-17 | Apple Inc. | Inverse text normalization for automatic speech recognition |
US10818288B2 (en) | 2018-03-26 | 2020-10-27 | Apple Inc. | Natural assistant interaction |
US10909331B2 (en) | 2018-03-30 | 2021-02-02 | Apple Inc. | Implicit identification of translation payload with neural machine translation |
US10928918B2 (en) | 2018-05-07 | 2021-02-23 | Apple Inc. | Raise to speak |
US11145294B2 (en) | 2018-05-07 | 2021-10-12 | Apple Inc. | Intelligent automated assistant for delivering content from user experiences |
US10984780B2 (en) | 2018-05-21 | 2021-04-20 | Apple Inc. | Global semantic word embeddings using bi-directional recurrent neural networks |
DK179822B1 (en) | 2018-06-01 | 2019-07-12 | Apple Inc. | Voice interaction at a primary device to access call functionality of a companion device |
US11386266B2 (en) | 2018-06-01 | 2022-07-12 | Apple Inc. | Text correction |
DK201870355A1 (en) | 2018-06-01 | 2019-12-16 | Apple Inc. | Virtual assistant operation in multi-device environments |
DK180639B1 (en) | 2018-06-01 | 2021-11-04 | Apple Inc | DISABILITY OF ATTENTION-ATTENTIVE VIRTUAL ASSISTANT |
US10892996B2 (en) | 2018-06-01 | 2021-01-12 | Apple Inc. | Variable latency device coordination |
US10504518B1 (en) | 2018-06-03 | 2019-12-10 | Apple Inc. | Accelerated task performance |
US10734024B1 (en) * | 2018-09-04 | 2020-08-04 | Adobe, Inc. | Systems and methods of appending metadata to a media file for playing time-lapsed audio |
USD893512S1 (en) | 2018-09-10 | 2020-08-18 | Apple Inc. | Electronic device with graphical user interface |
US11010561B2 (en) | 2018-09-27 | 2021-05-18 | Apple Inc. | Sentiment prediction from textual data |
US11170166B2 (en) | 2018-09-28 | 2021-11-09 | Apple Inc. | Neural typographical error modeling via generative adversarial networks |
US10839159B2 (en) | 2018-09-28 | 2020-11-17 | Apple Inc. | Named entity normalization in a spoken dialog system |
US11462215B2 (en) | 2018-09-28 | 2022-10-04 | Apple Inc. | Multi-modal inputs for voice commands |
US11475898B2 (en) | 2018-10-26 | 2022-10-18 | Apple Inc. | Low-latency multi-speaker speech recognition |
CN110060717A (en) * | 2019-01-02 | 2019-07-26 | 孙剑 | A kind of law enforcement equipment laws for criterion speech French play system |
US11638059B2 (en) | 2019-01-04 | 2023-04-25 | Apple Inc. | Content playback on multiple devices |
US11080466B2 (en) * | 2019-03-15 | 2021-08-03 | Ricoh Company, Ltd. | Updating existing content suggestion to include suggestions from recorded media using artificial intelligence |
US11573993B2 (en) | 2019-03-15 | 2023-02-07 | Ricoh Company, Ltd. | Generating a meeting review document that includes links to the one or more documents reviewed |
US11270060B2 (en) * | 2019-03-15 | 2022-03-08 | Ricoh Company, Ltd. | Generating suggested document edits from recorded media using artificial intelligence |
US11263384B2 (en) | 2019-03-15 | 2022-03-01 | Ricoh Company, Ltd. | Generating document edit requests for electronic documents managed by a third-party document management service using artificial intelligence |
US11720741B2 (en) | 2019-03-15 | 2023-08-08 | Ricoh Company, Ltd. | Artificial intelligence assisted review of electronic documents |
US11392754B2 (en) | 2019-03-15 | 2022-07-19 | Ricoh Company, Ltd. | Artificial intelligence assisted review of physical documents |
US11348573B2 (en) | 2019-03-18 | 2022-05-31 | Apple Inc. | Multimodality in digital assistant systems |
US11423908B2 (en) | 2019-05-06 | 2022-08-23 | Apple Inc. | Interpreting spoken requests |
US11475884B2 (en) | 2019-05-06 | 2022-10-18 | Apple Inc. | Reducing digital assistant latency when a language is incorrectly determined |
DK201970509A1 (en) | 2019-05-06 | 2021-01-15 | Apple Inc | Spoken notifications |
US11307752B2 (en) | 2019-05-06 | 2022-04-19 | Apple Inc. | User configurable task triggers |
US11140099B2 (en) | 2019-05-21 | 2021-10-05 | Apple Inc. | Providing message response suggestions |
US11289073B2 (en) | 2019-05-31 | 2022-03-29 | Apple Inc. | Device text to speech |
DK180129B1 (en) | 2019-05-31 | 2020-06-02 | Apple Inc. | User activity shortcut suggestions |
US11496600B2 (en) | 2019-05-31 | 2022-11-08 | Apple Inc. | Remote execution of machine-learned models |
US11360641B2 (en) | 2019-06-01 | 2022-06-14 | Apple Inc. | Increasing the relevance of new available information |
CN110673838A (en) * | 2019-09-10 | 2020-01-10 | 四川新网银行股份有限公司 | Input checking method |
WO2021056255A1 (en) | 2019-09-25 | 2021-04-01 | Apple Inc. | Text detection using global geometry estimators |
CN111343149B (en) * | 2020-02-05 | 2021-05-14 | 北京字节跳动网络技术有限公司 | Comment method and device, electronic equipment and computer readable medium |
US20220368548A1 (en) | 2021-05-15 | 2022-11-17 | Apple Inc. | Shared-content session user interfaces |
US11907605B2 (en) | 2021-05-15 | 2024-02-20 | Apple Inc. | Shared-content session user interfaces |
Family Cites Families (48)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4430726A (en) * | 1981-06-18 | 1984-02-07 | Bell Telephone Laboratories, Incorporated | Dictation/transcription method and arrangement |
US4627001A (en) | 1982-11-03 | 1986-12-02 | Wang Laboratories, Inc. | Editing voice data |
JPH02110658A (en) * | 1988-10-19 | 1990-04-23 | Hitachi Ltd | Document editing device |
US4996707A (en) * | 1989-02-09 | 1991-02-26 | Berkeley Speech Technologies, Inc. | Text-to-speech converter of a facsimile graphic image |
JPH03289854A (en) * | 1990-04-06 | 1991-12-19 | Nippon Telegr & Teleph Corp <Ntt> | Electronic mail system |
US5404295A (en) * | 1990-08-16 | 1995-04-04 | Katz; Boris | Method and apparatus for utilizing annotations to facilitate computer retrieval of database material |
US5309359A (en) * | 1990-08-16 | 1994-05-03 | Boris Katz | Method and apparatus for generating and utlizing annotations to facilitate computer text retrieval |
US5477451A (en) | 1991-07-25 | 1995-12-19 | International Business Machines Corp. | Method and system for natural language translation |
JPH05119793A (en) * | 1991-10-25 | 1993-05-18 | Nippon Telegr & Teleph Corp <Ntt> | Method and device for speech recognition |
US5737395A (en) | 1991-10-28 | 1998-04-07 | Centigram Communications Corporation | System and method for integrating voice, facsimile and electronic mail data through a personal computer |
JPH05313554A (en) | 1992-05-14 | 1993-11-26 | Sanyo Electric Co Ltd | Word processor |
IT1256823B (en) | 1992-05-14 | 1995-12-21 | Olivetti & Co Spa | PORTABLE CALCULATOR WITH VERBAL NOTES. |
US5500919A (en) | 1992-11-18 | 1996-03-19 | Canon Information Systems, Inc. | Graphics user interface for controlling text-to-speech conversion |
US5787231A (en) | 1995-02-02 | 1998-07-28 | International Business Machines Corporation | Method and system for improving pronunciation in a voice control system |
US5841979A (en) | 1995-05-25 | 1998-11-24 | Information Highway Media Corp. | Enhanced delivery of audio data |
US5661291A (en) | 1995-06-07 | 1997-08-26 | Hand Held Products, Inc. | Audio proof of delivery system and method |
US5826025A (en) * | 1995-09-08 | 1998-10-20 | Sun Microsystems, Inc. | System for annotation overlay proxy configured to retrieve associated overlays associated with a document request from annotation directory created from list of overlay groups |
US5737725A (en) | 1996-01-09 | 1998-04-07 | U S West Marketing Resources Group, Inc. | Method and system for automatically generating new voice files corresponding to new text from a script |
US5884262A (en) | 1996-03-28 | 1999-03-16 | Bell Atlantic Network Services, Inc. | Computer network audio access and conversion system |
US5915238A (en) | 1996-07-16 | 1999-06-22 | Tjaden; Gary S. | Personalized audio information delivery system |
US5850629A (en) | 1996-09-09 | 1998-12-15 | Matsushita Electric Industrial Co., Ltd. | User interface controller for text-to-speech synthesizer |
US5732216A (en) * | 1996-10-02 | 1998-03-24 | Internet Angles, Inc. | Audio message exchange system |
US5721827A (en) | 1996-10-02 | 1998-02-24 | James Logan | System for electrically distributing personalized information |
US5875448A (en) | 1996-10-08 | 1999-02-23 | Boys; Donald R. | Data stream editing system including a hand-held voice-editing apparatus having a position-finding enunciator |
US6616038B1 (en) * | 1996-10-28 | 2003-09-09 | Francis Olschafskie | Selective text retrieval system |
US5915001A (en) | 1996-11-14 | 1999-06-22 | Vois Corporation | System and method for providing and using universally accessible voice and speech data files |
US5924068A (en) | 1997-02-04 | 1999-07-13 | Matsushita Electric Industrial Co. Ltd. | Electronic news reception apparatus that selectively retains sections and searches by keyword or index for text to speech conversion |
US5884266A (en) | 1997-04-02 | 1999-03-16 | Motorola, Inc. | Audio interface for document based information resource navigation and method therefor |
US5899975A (en) | 1997-04-03 | 1999-05-04 | Sun Microsystems, Inc. | Style sheets for speech-based presentation of web pages |
US6279014B1 (en) * | 1997-09-15 | 2001-08-21 | Xerox Corporation | Method and system for organizing documents based upon annotations in context |
JPH11161567A (en) * | 1997-11-28 | 1999-06-18 | Canon Inc | Device, method and system for processing information |
US6181351B1 (en) * | 1998-04-13 | 2001-01-30 | Microsoft Corporation | Synchronizing the moveable mouths of animated characters with recorded speech |
US6956593B1 (en) * | 1998-09-15 | 2005-10-18 | Microsoft Corporation | User interface for creating, viewing and temporally positioning annotations for media content |
WO2000016541A1 (en) * | 1998-09-15 | 2000-03-23 | Microsoft Corporation | Annotation creation and notification via electronic mail |
EP1116217B1 (en) * | 1998-09-30 | 2003-08-13 | Lernout & Hauspie Speech Products N.V. | Voice command navigation of electronic mail reader |
US6167376A (en) | 1998-12-21 | 2000-12-26 | Ditzik; Richard Joseph | Computer system with integrated telephony, handwriting and speech recognition functions |
US6321198B1 (en) | 1999-02-23 | 2001-11-20 | Unisys Corporation | Apparatus for design and simulation of dialogue |
US6687878B1 (en) * | 1999-03-15 | 2004-02-03 | Real Time Image Ltd. | Synchronizing/updating local client notes with annotations previously made by other clients in a notes database |
US6459774B1 (en) * | 1999-05-25 | 2002-10-01 | Lucent Technologies Inc. | Structured voicemail messages |
US6507643B1 (en) * | 2000-03-16 | 2003-01-14 | Breveon Incorporated | Speech recognition system and method for converting voice mail messages to electronic mail messages |
WO2002005119A1 (en) * | 2000-07-07 | 2002-01-17 | Consilient, Inc. | Method and apparatus for providing process-container platforms |
US20020099552A1 (en) * | 2001-01-25 | 2002-07-25 | Darryl Rubin | Annotating electronic information with audio clips |
US7366979B2 (en) * | 2001-03-09 | 2008-04-29 | Copernicus Investments, Llc | Method and apparatus for annotating a document |
US20020010715A1 (en) * | 2001-07-26 | 2002-01-24 | Garry Chinn | System and method for browsing using a limited display device |
GB2380109A (en) * | 2001-09-21 | 2003-03-26 | Hewlett Packard Co | Apparatus for interpreting electronic legal documents |
US6650735B2 (en) * | 2001-09-27 | 2003-11-18 | Microsoft Corporation | Integrated voice access to a variety of personal information services |
US20040186713A1 (en) * | 2003-03-06 | 2004-09-23 | Gomas Steven W. | Content delivery and speech system and apparatus for the blind and print-handicapped |
US20050096909A1 (en) * | 2003-10-29 | 2005-05-05 | Raimo Bakis | Systems and methods for expressive text-to-speech |
-
2001
- 2001-03-09 US US09/802,395 patent/US7366979B2/en not_active Expired - Fee Related
-
2002
- 2002-03-07 WO PCT/US2002/007222 patent/WO2002073353A2/en active Application Filing
- 2002-03-07 JP JP2002572544A patent/JP2005506602A/en not_active Withdrawn
- 2002-03-07 CA CA002440291A patent/CA2440291A1/en not_active Abandoned
- 2002-03-07 EP EP11177378.4A patent/EP2390783B1/en not_active Expired - Lifetime
- 2002-03-07 EP EP02726603A patent/EP1374231A4/en not_active Ceased
-
2005
- 2005-08-18 US US11/207,598 patent/US7500193B2/en not_active Expired - Fee Related
-
2009
- 2009-02-27 US US12/395,265 patent/US8091028B2/en not_active Expired - Fee Related
-
2010
- 2010-02-18 JP JP2010033611A patent/JP2010140506A/en active Pending
-
2011
- 2011-12-07 US US13/314,070 patent/US8762853B2/en not_active Expired - Fee Related
-
2014
- 2014-06-17 US US14/306,647 patent/US20140365860A1/en not_active Abandoned
Also Published As
Publication number | Publication date |
---|---|
WO2002073353A8 (en) | 2009-04-30 |
US20140365860A1 (en) | 2014-12-11 |
US20090228126A1 (en) | 2009-09-10 |
EP2390783A1 (en) | 2011-11-30 |
WO2002073353A2 (en) | 2002-09-19 |
WO2002073353A3 (en) | 2003-05-01 |
US7366979B2 (en) | 2008-04-29 |
EP1374231A4 (en) | 2009-05-13 |
EP2390783B1 (en) | 2014-07-23 |
US20020129057A1 (en) | 2002-09-12 |
US20120173959A1 (en) | 2012-07-05 |
JP2005506602A (en) | 2005-03-03 |
US8091028B2 (en) | 2012-01-03 |
EP1374231A2 (en) | 2004-01-02 |
US8762853B2 (en) | 2014-06-24 |
US20060143559A1 (en) | 2006-06-29 |
JP2010140506A (en) | 2010-06-24 |
US7500193B2 (en) | 2009-03-03 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP2390783B1 (en) | Method and apparatus for annotating a document | |
US9530415B2 (en) | System and method of providing speech processing in user interface | |
US9214154B2 (en) | Personalized text-to-speech services | |
US7233982B2 (en) | Arrangement for accessing an IP-based messaging server by telephone for management of stored messages | |
US7779357B2 (en) | Audio user interface for computing devices | |
US9043691B2 (en) | Method and apparatus for editing media | |
EP2157571A2 (en) | Automatic answering device, automatic answering system, conversation scenario editing device, conversation server, and automatic answering method | |
US20090298529A1 (en) | Audio HTML (aHTML): Audio Access to Web/Data | |
US20030110211A1 (en) | Method and system for communicating, creating and interacting with content between and among computing devices | |
JP2008529345A (en) | System and method for generating and distributing personalized media | |
US8682938B2 (en) | System and method for generating personalized songs | |
CN104038774B (en) | Generate the method and device of ring signal file | |
US6760704B1 (en) | System for generating speech and non-speech audio messages | |
JP2008523759A (en) | Method and system for synthesizing video messages | |
AU2002257025A1 (en) | Method and apparatus for annotating a document with audio comments | |
US20030215063A1 (en) | Method of creating and managing a customized recording of audio data relayed over a phone network | |
KR102427213B1 (en) | Method, system, and computer readable record medium to manage together text conversion record and memo for audio file | |
KR100387102B1 (en) | learning system using voice recorder | |
JP3712967B2 (en) | COMMUNICATION SYSTEM, COMMUNICATION DEVICE, COMMUNICATION METHOD, COMMUNICATION PROGRAM, AND RECORDING MEDIUM CONTAINING COMMUNICATION PROGRAM | |
KR20170088255A (en) | A system and method of an electronic scenario offer for the actor's script reading based on on-line | |
JP2003271496A (en) | Information processing system, information processing method and communication terminal | |
KR20040049224A (en) | Real-time Authoring System and Method for Audio Data Using Internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
EEER | Examination request | ||
FZDE | Discontinued |