Automatic face extraction
Abstract
Faces of speakers in a meeting or conference are automatically detected and facial images corresponding to each speaker are stored in a faces database. A timeline is created to graphically identify when each speaker is speaking during playback of a recording of the meeting. Instead of generically identifying each speaker in the timeline, a facial image is shown to identify each speaker associated with the timeline.

Term
Term ended
Projected expiry passed 18 October 2025, 0.9 years ago.
- Priority
- Filed
- Published
- Projected expiry
- Today
32 claims: 5 independent, 27 dependent
- 1A method, comprising:detecting one or more facial images in a video sample;detecting one or more speakers in an audio sample that corresponds to the video sample;storing a speaker timeline that identifies a speaker by a speaker identifier and a speaker location at each time along a the speaker timeline;storing at least one facial image for each detected speaker in a faces database;and associating a speaker timeline and a facial image with each detected speaker.
- 10A method, comprising:displaying an audio/visual (A/V) sample having one or more speakers included therein;displaying a speaker timeline corresponding to each speaker, the speaker timeline indicating at what points along a temporal continuum the speaker corresponding to the speaker timeline is speaking;associating a speaker facial image with each speaker timeline, the speaker facial image corresponding to the speaker associated with the speaker timeline;and displaying the facial image with the corresponding speaker timeline.
- 13One or more computer-readable media containing executable instructions that, when executed, implement the following method:identifying each speaker in an A/V sample by a speaker identifier;identifying location for each speaker in the A/V sample;extracting at least one facial image for each speaker identified in the A/V sample;creating a speaker timeline for each speaker identified in the A/V sample, each speaker timeline indicating a time, a speaker identifier and a speaker location;and associating the facial image for a speaker with a speaker timeline that corresponds to the same speaker.
- 23One or more computer-readable media, comprising:a speaker timeline database that includes a speaker timeline for each speaker in an A/V sample, each speaker timeline identifying a speaker and a speaker location for multiple times along a time continuum;and a faces database that includes at least one facial image for each speaker identified in a speaker timeline and a speaker identifier that links each facial image with the appropriate speaker timeline in the speaker timeline database.
- 25A system, comprising:an A/V sample;means for identifying each speaker appearing in the A/V sample;means for identifying a facial image for each speaker identified in the A/V sample;means for creating a speaker timeline for each speaker identified in the A/V sample;and means for associating a facial image with an appropriate speaker timeline.
Independent claims5
68 paragraphs in 5 sections, as filed
CROSS-REFERENCE(S) TO RELATED APPLICATION(S)
0001This application is a continuation-in-part of U.S. Patent Application Number 10/177,315, entitled "A System and Method for Distributed Meetings", filed 06/21/2002 by the present inventor and assigned to Microsoft Corp., the assignee of the present application. Applicant claims priority to the filing date of said application, which is hereby incorporated by reference for all that it discloses and teaches.
TECHNICAL FIELD
0002The following description relates generally to video image processing. More particularly, the following description relates to providing an indexed timeline for video playback.
BACKGROUND
0003Playback of recorded video of scenarios that include more than one speaker - such as playback of a recorded meeting - is usually shown contemporaneously with an indexed timeline. Using the timeline, a user can quickly move to a particular time in the meeting by manipulating one or more timeline controls. When the video includes more than one speaker, multiple timelines may be used where one timeline is associated with a particular speaker. Each timeline indicates when a corresponding speaker is speaking. That way, a user can navigate to portions of the meeting where a particular speaker is speaking.
0004Such multiple timelines may be labeled in a generic fashion to identify each speaker as, for example, "Speaker 1," "Speaker 2," etc. Current techniques for automatically labeling timelines with specific speaker names are inaccurate and also may require a database of users and their associated voiceprints and faceprints, which could entail security and privacy issues.
BRIEF DESCRIPTION OF THE DRAWINGS
0005The foregoing aspects and many of the attendant advantages of this invention will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein: <ul id="ul0001" list-style="none" compact="compact"><li>Figure 1 is a block diagram depicting an exemplary general purpose computing/camera device.</li><li>Figure 2 is a block diagram representing an exemplary panoramic camera and client device.</li><li>Figure 3 is a representation of an exemplary playback screen with a panoramic image and a facial image timeline.</li><li>Figure 4 is an exemplary playback screen with a panoramic image and a facial image timeline.</li><li>Figure 5 is an exemplary flow diagram of a methodological implementation for creating a timeline with facial images.</li><li>Figure 6 is an exemplary flow diagram depicting a methodological implementation for creating a faces database.</li></ul>
DETAILED DESCRIPTION
0006The following description relates to various implementations and embodiments for automatically detecting each speaker's face in a multi-speaker environment and associating one or more images of a speaker's face with a portion of a timeline that corresponds to the speaker. This sort of specific labeling has advantages over generic labeling in that a viewer can more readily determine which portion of a timeline corresponds to a particular one of multiple speakers.
0007In the following discussion, an instance of a panoramic camera is described wherein the panoramic camera is used to record a meeting having more than one participant and/or speaker. Although a panoramic camera including multiple cameras is described, the following description also relates to single cameras and multi-camera devices having two or more cameras.
0008A panoramic image is input to a face tracker (FT) which detects and tracks faces in the meeting. A microphone array is input to a sound source localizer (SSL) which detects locations of speakers based on sound. The outputs from the face tracker and from the sound source localizer are input to a virtual cinematographer to detect locations of the speakers.
0009The speakers are post-processed with a speaker clustering module which clusters speakers temporally and spatially to better delineate an aggregate timeline that includes two or more individual timelines. The (aggregate) timeline is stored in a timeline database. A faces database is created to store one or more images for each speaker, at least one of each face to be used in a timeline associated with a speaker.
0010The concepts presented and claimed herein are described in greater detail, below, with regard to one or more appropriate operating environments. Some of the elements described below are also described in parent U.S. Patent Application No. 10/177,315, entitled "A System and Method for Distributed Meetings", filed 06/21/2002 and incorporated by reference above.
Exemplary Operating Environment
0011Fig. 1 is a block diagram depicting a general purpose computing/camera device. The computing system environment 100 is only one example of a suitable computing environment and is not intended to suggest any limitation as to the scope of use or functionality of the claimed subject matter. Neither should the computing environment 100 be interpreted as having any dependency or requirement relating to any one or combination of components illustrated in the exemplary operating environment 100.
0012The described techniques and objects are operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known computing systems, environments, and/or configurations that may be suitable for use include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, distributed computing environments that include any of the above systems or devices, and the like.
0013The following description may be couched in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The described implementations may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
0014With reference to Fig. 1, an exemplary system for implementing the invention includes a general purpose computing device in the form of a computer 110. Components of computer 110 may include, but are not limited to, a processing unit 120, a system memory 130, and a system bus 121 that couples various system components including the system memory to the processing unit 120. The system bus 121 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus.
0015Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of the any of the above should also be included within the scope of computer readable media.
0016The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation, FIG. 1 illustrates operating system 134, application programs 135, other program modules 136, and program data 137.
0017The computer 110 may also include other removable/non-removable, volatile/nonvolatile computer storage media. By way of example only, Fig. 1 illustrates a hard disk drive 141 that reads from or writes to non-removable, nonvolatile magnetic media, a magnetic disk drive 151 that reads from or writes to a removable, nonvolatile magnetic disk 1 52, and an optical disk drive 1 55 that reads from or writes to a removable, nonvolatile optical disk 156 such as a CD ROM or other optical media. Other removable/non-removable, volatile/nonvolatile computer storage media that can be used in the exemplary operating environment include, but are not limited to, magnetic tape cassettes, flash memory cards, digital versatile disks, digital video tape, solid state RAM, solid state ROM, and the like. The hard disk drive 141 is typically connected to the system bus 121 through anon-removable memory interface such as interface 140, and magnetic disk drive 151 and optical disk drive 155 are typically connected to the system bus 121 by a removable memory interface, such as interface 1 50.
0018The drives and their associated computer storage media discussed above and illustrated in Fig. 1, provide storage of computer readable instructions, data structures, program modules and other data for the computer 110. In Fig. 1, for example, hard disk drive 141 is illustrated as storing operating system 144, application programs 145, other program modules 146, and program data 147. Note that these components can either be the same as or different from operating system 134, application programs 135, other program modules 136, and program data 137. Operating system 144, application programs 145, other program modules 146, and program data 147 are given different numbers here to illustrate that, at a minimum, they are different copies. A user may enter commands and information into the computer 110 through input devices such as a keyboard 162 and pointing device 161, commonly referred to as a mouse, trackball or touch pad. Other input devices (not shown) may include a microphone, joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus 121, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195. Of particular significance to the present invention, a camera 163 (such as a digital/electronic still or video camera, or film/photographic scanner) capable of capturing a sequence of images 164 can also be included as an input device to the personal computer 110. Further, while just one camera is depicted, multiple cameras could be included as an input device to the personal computer 110. The images 164 from the one or more cameras are input into the computer 110 via an appropriate camera interface 165. This interface 165 is connected to the system bus 121, thereby allowing the images to be routed to and stored in the RAM 132, or one of the other data storage devices associated with the computer 110. However, it is noted that image data can be input into the computer 110 from any of the aforementioned computer-readable media as well, without requiring the use of the camera 163.
0019The computer 110 may operate in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110, although only a memory storage device 181 has been illustrated in Fig. 1. The logical connections depicted in Fig. 1 include a local area network (LAN) 1 71 and a wide area network (WAN) 173, but may also include other networks. Such networking environments are commonplace in offices, enterprise-wide computer networks, intranets and the Internet.
0020When used in a LAN networking environment, the computer 110 is connected to the LAN 1 71 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation, Fig. 1 illustrates remote application programs 185 as residing on memory device 181. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers may be used.
Exemplary Panoramic Camera and Client Device
0021Fig. 2 is a block diagram representing an exemplary panoramic camera apparatus 200 and an exemplary client device 222. Although it is shown in a particular configuration, it is noted that the panoramic camera apparatus 200 may be any apparatus that includes a panoramic camera or its functional equivalent. More or less components than those shown included with the panoramic camera apparatus 200 may be included in a practical application incorporating one or more of the techniques described herein.
0022The panoramic camera apparatus 200 includes a processor 202 and memory 204. The panoramic camera apparatus 200 creates a panoramic image by stitching together several individual images produced by multiple cameras 206 (designated 206_1 through 206_n). The panoramic image may be a complete 360° panoramic image or it may be only a portion thereof. It is noted that although a panoramic camera apparatus 200 is shown and described herein, the described techniques may also be utilized with a single camera.
0023The panoramic camera apparatus 200 also includes a microphone array 208. As will be described in greater detail below, the microphone array is configured so that sound direction may be localized. In other words, analysis of sound input into the microphone array yields a direction from which a detected sound is produced. A speaker 210 may also be included in the panoramic camera apparatus 200 to enable a speakerphone or to emit notification signals and the like to users.
0024The memory 204 stores several camera settings 212 such as calibration data, exposure settings, stitching tables, etc. An operating system 214 that controls camera functions is also stored in the memory 204 along with one or more other camera software applications 216.
0025The panoramic camera apparatus 200 also includes an input/output (I/O) module 218 for transmitting data from and receiving data to the panoramic camera apparatus 200, and miscellaneous other hardware 220 elements that may be required for camera functionality.
0026The panoramic camera apparatus 200 communicates with at least one client device 222, which includes a processor 224, memory 226, a mass storage device 242 (such as a hard disk drive) and other hardware 230 that may be required to execute the functionality attributed to the client device 222 below.
0027The memory 226 stores a face tracker (FT) module 230 and a sound source localization (SSL) module 232. The face tracker module 230 and the sound source localization module 232 are used in conjunction with a virtual cinematographer 234 to detect a person in a camera scene and determine if and when the person is speaking. Any of several conventional methods of sound source localization may be used. Various face tracker methods (or person detection and tracking systems), including the one described in the parent application hereto, may be used as described herein.
0028The memory 226 also stores a speaker clustering module 236 that is configured to determine a primary speaker when two or more persons are speaking and concentrate a particular timeline portion to the primary speaker. In most meeting situations, there are instances where more than one person talks at the same time. Usually, a primary speaker is speaking when another person interrupts the speaker for a short period or talks over the speaker. The speaker clustering module 236 is configured to cluster speakers temporally and spatially to clean up the timeline.
0029A timeline 238 is created by the virtual cinematographer 234. The timeline 238 is stored in a timeline database 244 on the mass storage device 242. The timeline database 238 includes a plurality of fields including, but not necessarily limited to, time, speaker number, and speaker bounding box within a camera image (x, y, width, height). The timeline database 238 may also include one or more speaker face angles (azimuth and elevation).
0030A face extractor module 240 is also stored in the memory 226 and is configured to extract an image of a speaker's face from a face bounding box (identified by the face tracker 230) of a camera image. The face extractor module 240 stores extracted facial images in a face database 246 on the mass storage device 242.
0031In at least one implementation, multiple facial images may be stored for one or more speakers. Parameters can be specified to determine which facial image is used at which particular times. Or, a user may be able to manually select a particular facial image from the multiple facial images.
0032In at least one alternative implementation, only a single facial image is stored for each speaker. The stored facial image may be a single image extracted by the face extractor module 240, but the face extractor module 240 may also be configured to select a best image of a speaker.
0033Selecting a best image of a speaker can be accomplished by identifying frontal facial angles (on an assumption that an image with a frontal facial image is a better representation than an alternative image), by identifying a facial image that exhibits a minimum of motion or by identifying a facial image that maximizes facial symmetry.
0034The recorded meeting 248 is also stored on the mass storage device 242 so that it can be recalled and played back at a later time.
0035The elements and functionality shown and described with regard to Fig. 2 will be described more fully below, with respect to subsequent figures.
Exemplary Playback Screen
0036Fig. 3 is a line drawing representation of a playback screen 300 that includes a panoramic image 302 and a facial image timeline 304. The panoramic image 302 is shown with a first meeting participant 303 and a second meeting participant 305. The playback screen 300 is also shown having a title bar 306 and an individual image 308. The individual image 308 is an optional feature wherein a particular individual is focused on, typically a primary speaker. In Fig. 3, the individual image 308 displays a facial image of the first meeting participant 303.
0037The exemplary playback screen 300 also includes a controls section 310 that contains controls typically found in a media player, such as a play button, a fast forward button, a rewind button, etc. An information area 312 is included in the playback screen 300 where information regarding the subject matter of the playback screen 300 may be displayed. For example, a meeting title, a meeting room number, a list of meeting attendees, and the like may be displayed in the information area 312.
0038The facial image timeline 304 includes a first sub-timeline 314 that corresponds to the first meeting participant 303 and a second sub-timeline 316 that corresponds to the second meeting participant. Each sub-timeline 314, 316 indicates sections along a temporal continuum where the corresponding meeting participant is speaking. A user may directly access any point on a sub-timeline 314, 316 to immediately access a portion of the meeting wherein a particular meeting participant is speaking.
0039A first facial image 318 of the first meeting participant 303 appears adjacent to the first sub-timeline 314 to indicate that the first sub-timeline 314 is associated with the first meeting participant 318. A facial image 320 of the second meeting participant 305 appears adjacent to the second sub-timeline 316 to indicate that the second sub-timeline 316 is associated with the second meeting participant 305.
0040Fig. 4 shows an exemplary playback screen 400 that includes similar elements as the exemplary playback screen 300 shown and described in Fig. 3. The elements and reference numerals shown and described with respect to Fig. 3 will be used with reference to the exemplary playback screen 400 of Fig. 4.
0041The exemplary playback screen 400 includes a panoramic image 302 and a facial image timeline 304. The panoramic image 302 shows a first meeting participant 303 and a second meeting participant 305. A title bar 306 spans the top of the playback screen 400 and an individual image 408 shows the second meeting participant 303.
0042The exemplary playback screen 400 also includes a whiteboard speaker image 402 that displays a meeting participant (in this case, the second meeting participant 305) that is situated before a whiteboard. The whiteboard speaker image 402 is not included in the playback screen 300 of Fig. 3 and is used here to show how other images may be included in any particular playback screen 300, 400.
0043A controls section 310 includes multimedia controls and an information area 312 displays information regarding the meeting shown on the playback screen 400.
0044The facial image timeline 304 includes a first sub-timeline 314, a second sub-timeline 316 and a third sub-timeline 404. It is noted that while only two sub-timelines are shown in Fig. 3, a timeline may contain any manageable number of sub-timelines. In Fig. 4, for example, there are three sub-timelines.
0045It is noted that while there are only two meeting participants in this example, there are three sub-timelines. This is because a single speaker may be associated with more than a single sub-timeline. In the present example, the second sub-timeline 316 is associated with the second meeting participant 305 while the second meeting participant 305 is at the whiteboard, and the third sub-timeline 404 is associated with the second meeting participant 305 while the second meeting participant 305 is situated at a location other than the whiteboard.
0046This situation can happen when a meeting participant occupies more than one location during a meeting. The virtual cinematographer 234 in this case has detected speakers in three locations. It does not necessarily know that only two speakers are present in those locations. This feature assists a user in cases where the user is interested mainly in a speaker when the speaker is in a certain position. For example, a user may only want to play a portion of a recorded meeting when a speaker is situated at the whiteboard.
0047The exemplary playback screen 400 also includes a first facial image 318 of the first meeting participant 303 and a second facial image 320 of the second meeting participant 305. In addition, a third facial image 406 is included and is associated with the third sub-timeline 404. The third facial image 406 corresponds with a second location of the second meeting participant 305.
0048The techniques used in presenting the exemplary playback screens 300, 400 will be described in greater detail below, with respect to the other figures.
Exemplary Methodological Implementation: Creation of Facial Image Timeline
0049Fig. 5 is an exemplary flow diagram 500 of a methodological implementation for creating a timeline with facial images. In the following discussion of the exemplary flow diagram 500, continuing reference is made to the elements and reference numerals shown in previous figures.
0050At block 502, the panoramic camera apparatus 200 samples one or more video images to create a panoramic image. The panoramic image is input to the face tracker 230 (block 504) which detects and tracks faces in the image. Approximately simultaneously at block 506, the microphone array 208 samples sound corresponding to the panoramic image and inputs the sound into the sound source localizer 232 which detects locations of speakers based on the sampled sound at block 508.
0051The virtual cinematographer 234 processes data from the face tracker 230 and the sound source localizer 232 to create the timeline 238 at block 510. At block 512, the speaker clustering module 236 clusters speakers temporally and spatially to consolidate and clarify portions of the timeline 238 as described previously.
0052The timeline is stored in the timeline database 244 with the following fields: time, speaker number, speaker bounding box in image (x, y, width, height), speaker face angles (azimuth, elevation), etc.
0053Using the panoramic image and face identification coordinates (i.e. face bounding boxes) derived by the face tracker 230, the face extractor 240 extracts a facial image of the speakers at block 514. Extracted facial images are stored in the faces database 246 and are associated with a speaker number.
0054As previously noted, the face extractor 240 may be configured to extract more than one image for each speaker and use what the face extractor 240 determines to be the best image in the timeline 238.
0055An exemplary methodological implementation of selecting a "best" facial image and creating the faces database 246is shown and described below, with respect to Fig. 6.
Exemplary Methodological Implementation: Creating a Faces Database
0056Fig. 6 is an exemplary flow diagram 600 depicting a methodological implementation for creating a faces database. In the following discussion of Fig. 6, continuing reference is made to elements and reference numerals shown in one or more previous figures.
0057At block 602, the face extractor 240 extracts a facial image from the panoramic image as described above. If a facial image for the speaker is not already stored in the faces database 246 ("No" branch, block 604), then the facial image is stored in the faces database 246 at block 610. It is noted that determining if the facial image is stored does not necessarily depend on whether the person who appears in the facial image already has an image of their likeness stored, but whether the identified speaker has an image already stored that corresponds to the speaker. Thus, if a speaker located in a first position has a stored facial image and then the speaker is detected at a second location, a facial image of the speaker in the second location will not be compared with the stored facial image of the speaker in the first position to determine if the speaker already has a facial image stored.
0058If a facial image for the speaker is already stored in the faces database 246 - hereinafter, the "stored facial image" - ("Yes" branch, block 604), then the facial image is compared to the stored facial image at block 606. If the face extractor 240 determines that the facial image is better or more acceptable than the stored facial image ("Yes" branch, block 608), then the facial image is stored in the faces database 246, thus overwriting the previously stored facial image.
0059If the facial image is not better than the stored facial image ("No" branch, block 608), then the facial image is discarded and the stored facial image is retained.
0060The criteria for determining which facial image is a better facial image can be numerous and varied. For instance, the face extractor 234 may be configured to determine that a "best" facial image is one that captures a speaker in a position where the speaker's face is most in a frontal position. Or, if a first facial image shows signs of motion and a second facial image does not, then the face extractor 246 may determine that the second facial image is the best facial image. Or, the face extractor 246 may be configured to determine which of multiple images of a speaker exhibits maximum symmetry and to use that facial image in the timeline. Other criteria not enumerated here may also be used to determine the most appropriate facial image to utilize with the timeline.
0061If there is another speaker ("Yes" branch, block 612), then the process reverts to block 602 and is repeated for each unique speaker. Again, "unique speaker" as used in this context does not necessarily mean a unique person, since a person that appears in different speaking locations may be interpreted as being different speakers. The process terminates when there are no more unique speakers to identify ("No" branch, block 612).
Conclusion
0062While one or more exemplary implementations have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the claims appended hereto.
Contents5
7 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US8645283B2 | Cited by | United States of America | Applicant |
| EP2055088A4 | Cited by | European Patent Office (EPO) | Search report |
| EP2055088A2 | Cited by | European Patent Office (EPO) | Search report |
| WO2008045153A2 | Cited by | World Intellectual Property Organization (WIPO) | Applicant |
| WO2010058064A1 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| GB2395852A | Cites | United Kingdom | Search report |
| WO9960788A1 | Cites | World Intellectual Property Organization (WIPO) | Search report |
59 members in 11 offices
Priority claims2
| Document | Office | Kind | Date |
|---|---|---|---|
| 978172 | United States of America | – | |
| 97817204 | United States of America | A |
Members59
| Document | Office | Kind | |
|---|---|---|---|
| US2003234866A1 | United States of America | A1 | |
| EP1377026A2 | European Patent Office (EPO) | A2 | |
| JP2004054928A | Japan | A | |
| EP1377026A3 | European Patent Office (EPO) | A3 | |
| US2004263611A1 | United States of America | A1 | |
| US2005046703A1 | United States of America | A1 | |
| US2005117015A1 | United States of America | A1 | |
| US2005117034A1 | United States of America | A1 | |
| US2005151837A1 | United States of America | A1 | |
| US2005285943A1 | United States of America | A1 | |
| CA2513760A1 | Canada | A1 | |
| CN1727991A | China | A | |
| MXPA05008090A | Mexico | A | |
| US2006023074A1 | United States of America | A1 | |
| US2006023075A1 | United States of America | A1 | |
| EP1624687A2 | European Patent Office (EPO) | A2 | |
| JP2006039564A | Japan | A | |
| AU2005203094A1 | Australia | A1 | |
| BRPI0503143A | Brazil | A | |
| CA2521670A1 | Canada | A1 | |
| MXPA05010595A | Mexico | A | |
| MXPA05010595A | Mexico | A | |
| AU2005220252A1 | Australia | A1 | |
| JP2006129480A | Japan | A | |
| KR20060049992A | Republic of Korea | A | |
| KR20060051672A | Republic of Korea | A | |
| EP1659518A2This record | European Patent Office (EPO) | A2 | |
| CN1783998A | China | A | |
| BRPI0504224A | Brazil | A | |
| BRPI0504224A | Brazil | A | |
| EP1677534A1 | European Patent Office (EPO) | A1 | |
| KR20060079079A | Republic of Korea | A | |
| JP2006191535A | Japan | A | |
| CN1837952A | China | A | |
| US2006268131A1 | United States of America | A1 | |
| RU2005123981A | Russian Federation | A | |
| RU2005133403A | Russian Federation | A | |
| US7259784B2 | United States of America | B2 | |
| US7298392B2 | United States of America | B2 | |
| US7495694B2 | United States of America | B2 | |
| CN100524017C | China | C | |
| US7593042B2 | United States of America | B2 | |
| US7598975B2 | United States of America | B2 | |
| US7602412B2 | United States of America | B2 | |
| EP1659518A3 | European Patent Office (EPO) | A3 | |
| JP4421843B2 | Japan | B2 | |
| CN1783998B | China | B | |
| US7782357B2 | United States of America | B2 | |
| RU2398277C2 | Russian Federation | C2 | |
| CN1837952B | China | B | |
| US7936374B2 | United States of America | B2 | |
| JP4890005B2 | Japan | B2 | |
| JP5027400B2 | Japan | B2 | |
| KR101201107B1 | Republic of Korea | B1 | |
| KR101238586B1 | Republic of Korea | B1 | |
| CA2521670C | Canada | C | |
| EP1677534B1 | European Patent Office (EPO) | B1 | |
| EP1659518B1 | European Patent Office (EPO) | B1 | |
| ES2645313T3 | Spain | T3 |
80 legal events, as 11 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Announcement of lapse in spainLapsedFD2A | FD2A | ES | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Gb: european patent ceased through non-payment of renewal feeCeasedGBPC | GBPC | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | NL | |
| Application deemed withdrawn, or ip right lapsed, due to non-payment of renewal feeWithdrawnR119 | R119 | DE | |
| Change of representativeR082 | R082 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Invalidated european patentMG4D | MG4D | LT | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Definitive protectionFG2A | FG2A | ES | |
| Translation for ep filed (entry of ep into country)FP | FP | NL | |
| Fee paymentPLFP | PLFP | FR | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Information on inventor provided before grant (corrected)RIN1 | RIN1 | EP | |
| Intention to grant announced (deleted)INTC | INTC | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Information related to disapproval of communication of intention to grant by the applicant or resumption of examination proceedings by the epo deletedORIGINAL CODE: EPIDOSDIGR1GRAJ | GRAJ | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Designation fees paidAKX | AKX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Search report despatchedORIGINAL CODE: 0009013PUAL | PUAL | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 1659518
- Application
- 51096832
Titles3
- German
- Automatische Gesichtextrahierung
- English
- Automatic face extraction
- French
- Extraction de visage automatique
Classification
- CPC, 13
- H04N1/3876
- G06V40/173
- H04N5/93
- H04N1/6027
- H04N7/147
- H04N7/15
- H04N7/155
- H04N17/002
- H04N23/698
- H04N23/90
- H04N23/88
- G06T7/20
- G06T7/40
- IPC, 15
- G06K9 00
- H04N7 14
- G03B37 00
- G06N99 00
- G06T1 00
- G06T3 00
- G06T5 40
- G06T7 00
- H04N1 387
- H04N1 60
- H04N5 225
- H04N5 265
- H04N5 76
- H04N9 73
- H04N17 00
Designated states36
- Contracting states, 31
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
- Netherlands (Kingdom of the)
and 7 moreShow fewer
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye
- Extension states, 5
- Albania
- Bosnia and Herzegovina
- Croatia
- North Macedonia
- Yugoslavia, later Serbia and Montenegro (until 2006)