Many users consume media on a plurality of devices, such as, for example, personal computers and handheld devices. For example, the media may include television shows, movies, music, pictures, and/or any other type of media. A plurality of broadcast sources may transmit the media and the user may consume the received media by purchasing the media, renting the media, watching the media, playing the media, and/or consume the media in any other manner.
Many aspects of the present disclosure can be better understood with reference to the following drawings. The components in the drawings are not necessarily to scale, emphasis instead being placed upon clearly illustrating the principles of the disclosure. Moreover, in the drawings, like reference numerals designate corresponding parts throughout the several views.
Disclosed are various embodiments for generating personalized streaming media based on streaming media received from a broadcast source. In one embodiment, a media service application determines the content of the streaming media and identifies files in a file system of a user that include content related to the streaming media. Upon identifying the related files, the media service application embeds the content of the related files in a relevant portion of the streaming media to generate the personalized streaming media. In the following discussion, a general description of the system and its components is provided, followed by a discussion of the operation of the same.
With reference to
The computing device 103 may comprise, for example, a server computer or any other system providing computing capability. Alternatively, a plurality of computing devices 103 may be employed that are arranged, for example, in one or more server banks or computer banks or other arrangements. For example, a plurality of computing devices 103 together may comprise a cloud computing resource, a grid computing resource, and/or any other distributed computing arrangement. Such computing devices 103 may be located in a single installation or may be distributed among many different geographical locations. For purposes of convenience, the computing device 103 is referred to herein in the singular. Even though the computing device is referred to in the singular, it is understood that a plurality of computing devices 103 may be employed in the various arrangements as described above.
Various applications and/or other functionality may be executed in the computing device 103 according to various embodiments. Also, various data is stored in a data store 116 that is accessible to the computing device 103. The data store 116 may be representative of a plurality of data stores as can be appreciated. The data stored in the data store 116, for example, is associated with the operation of the various applications and/or functional entities described below.
The components executed on the computing device 103, for example, include a file service 119, a media service 123, and other applications 126, services, processes, systems, engines, or functionality not discussed in detail herein. The file service 119 is executed to maintain a file organization of files and folders in file systems associated with service accounts. To this end, the file service 119 may support various file-related operations such as, for example, creating files, deleting files, modifying files, setting permissions for files, downloading data files, and/or other operations. The media service 123 is executed to identify content of streaming media and embed content of files of a user's file system in relevant portions of the streaming media. To this end, the media service 123 may support various media-related operations such as, for example, determining media content, identifying files related to the content, editing the media, and/or other operations.
The applications 126 correspond to hosted applications that may access the data stored in the file system. Various applications 126 may, for example, have a web-based interface that may serve up network pages, such as web pages or other forms of network content, to facilitate user interaction. Other applications 126 may include internal applications that may not have a web-based interface. For example, the applications 126 may include media organizing tools, media consuming tools, word processors, email applications, and/or other applications 126.
The data stored in the data store 116 includes, for example, account data 129, file systems 133, files 136, media data 139, and potentially other data. The account data 129 includes various data associated with file service accounts including data regarding authorized user(s) 143 of the computing device 103. In addition, account data 129 may also include usernames, passwords, security credentials, file management permissions, storage quotas and limitations, authorized applications, purchasing information, payment instrument information, billing information, and/or other data.
The file systems 133 correspond to logical file organizations that are maintained within the computing device 103 on behalf of one or more authorized users associated with a file service account. In various embodiments, the logical file organizations embodied in the file systems 133 are abstractions that do not directly correspond to any particular physical storage arrangements such as disk drives, portable storage media, etc. A file service account may be associated with one or more file systems 133. Each account-level user may have its own file system 133, or the file systems 133 may be shared by multiple account-level users.
Each file system 133 may include one or more files 136. A file 136 may include a file name 149, a unique identifier 153, a data object reference 156, a parent object reference 159, one or more permissions 163, a file creation date, a file modification date, and/or other data. The file name 149 may correspond to a human-readable character string that identifies the contents of the file 136. In one embodiment, the file name 149 may be limited in character length and may be limited in terms of allowed characters. In some cases, such limitations may be enforced for compatibility reasons. In addition, the file name 149 may be restricted to being unique to a folder and/or a file system 133 in various embodiments.
The unique identifier 153 corresponds to a number, character string, or other identifier that uniquely identifies the file 136 across the file system 133 and/or all of the file systems 133. In one embodiment, the unique identifier 153 of a file 136 coupled with an identifier of a file system 133 may correspond to an identifier that is unique across all of the file systems 133. In another embodiment, the unique identifier 153 of a file 136 may itself be unique across all of the file systems 133.
The data object reference 156 corresponds to a reference that may identify a data object associated with the file 136 that is stored in a data store such as the data store 116. In one embodiment, the data object reference 156 may include a key value for obtaining the data object. The data stored from which to obtain the data object may be determined implicitly or explicitly, for example, from a definition in the data object reference 156. The parent object reference 159 corresponds to a reference that may identify a folder or file 136 that is considered to be the parent of the file 136. In this way, the folders are associated with files 136. In some situations, the parent object reference 159 may include a special identifier, such as, for example, NULL and/or 0, that identifies the root of the file system 133.
The permissions 163 may correspond to access permissions and security policies associated with the file 136. For example, a user may be designated as a file owner, and a group of users may be designated as a file group. In such an example, read or write access may be enabled or disabled as it applies to the user, the group of users, and/or all users. Similarly, access to a file 136 may be enabled or disabled as it applies to a file service account, a group of file service accounts, and/or all file service accounts. In another embodiment, each file 136 may also have an associated metadata that describes the content of the file 136. For example, the metadata may comprise text that includes keywords describing the content and/or type of file 136.
The media data 139 corresponds to information that is associated with streaming media received from a variety of sources. The media data 139 includes information for a plurality of different media and may include a media name 169, a media content information 173, a frame identifier 176, and a listing of related files 146. For example, the media name 169 may be a sequence of characters that uniquely identifies the media. The media content information 173 may be a description of the media being consumed. In one embodiment, the media content information 173 may include a listing of keywords that describe the media. For example, the media may be a video clip and the media content information 173 may describe the contents of the video for each frame having a unique frame identifier 176. In addition, the related files 146 may be a listing of file names 149 that relate to the media content information 173.
The client 106 is representative of a plurality of client devices that may be coupled to the network 109. The client 106 may comprise, for example, a processor-based system such as a computer system. Such a computer system may be embodied in the form of a desktop computer, a laptop computer, a personal digital assistant, a cellular telephone, set-top box, music players, web pads, tablet computer systems, game consoles, or other devices with like capability.
The client 106 may be configured to execute various applications such as a client side application 179, a receiver application 183, and/or other applications. The client side application 179 may be executed in a client 106, for example, to access and render network pages 186, such as web pages, or other network content served up by the computing device 103 and/or other servers. To this end, the client side application 179 may comprise, for example, a browser application or a similar application. When executed in the client, the client side application 179 renders network pages 186 on the display 113. Network pages 186 indicating content (e.g. files 136) of a file system 133 can include media. In one embodiment, the client side application 179 is integrated with an operating system of the client 106 to provide access to a file system 133 similarly to a mounted file system of the client 106. The client 106 may be configured to execute applications beyond client side application 179 such as, for example, email applications, instant message applications, and/or other applications.
The receiver application 183 may be configured to process streaming media 189 from a source such as a cable system, a broadcast source, an/or another media transmission medium that is rendered, for example, on a display 113. Additionally, the receiver application 183 makes the processed streaming media 189 available to the computing device 103 which is then used by the computing device 103 for generating personalized streaming media 193, as will be described. For example, the client side application 179 renders the personalized streaming media 193 on a screen 196 associated with the display 113.
Next, a general description of the operation of the various components of the networked environment 100 is provided. To begin, a user may establish a file service account through the client side application 179, or another application 126 to create one or more file systems 133. The file service 119 and/or one or more applications 126 of the computing device 103 may provide a user interface to allow the user to create the file service account by generating one or more network page(s) 186 in response to user actions. The user may specify various parameters, such as, for example, a maximum storage requirement, performance requirements, a rate plan, access permissions, security credentials, and so on. Accordingly, the account data 129 corresponding to the established file service account is populated and a file system 133 may be created. The file service 119 and/or another application(s) 126 may also provide a user interface to allow the user to access and/or manipulate the content of the file system(s) 133 associated with the established account, such as, for example, adding, deleting, copying, viewing, and/or any other type of consumption of the files 136.
In one embodiment, the user may wish to consume streaming media 189 on a display 113 associated with the client 106. In addition, the user may sometimes wish to view content from personal files 136 of the established file system 133 as part of the streaming media 189. For instance, the user may wish to view a personalized streaming media 193 that includes relevant content from the user's files 136 embedded within the streaming media 189. In one embodiment, the media service 123 identifies the content of the streaming media 189 and embeds the content of files 136 related to the content of the streaming media 189 to create personalized streaming media 193. As an example, the streaming media 189 may be a film including a scene of a man examining a portrait on a wall. In this scene, the portrait may be irrelevant. The media service 123 may substitute the portrait with an image from the user's files 136 that is displayed on the wall. As such, the media service 123 generates a personalized streaming media 193 by including content from a user's personal files 136 that are related to the streaming media 189.
In one embodiment, the receiver application 183 receives the streaming media 189 from a broadcast source such as, for instance a broadcast center via a plurality of satellites. The receiver application 183 processes the streaming media 189 and communicates the streaming media 189 to the display 113 to be rendered on the screen 196. The streaming media 189 may comprise television shows, commercials, infomercials, movies, documentaries, videos on demand, music, holograms, three-dimensional video, and/or any other type of media. Upon an indication by the user to include content from the user's files 136 in the streaming media, the client side application 179 generates and transmits a request to the media service 123 to generate the personalized streaming media 193. For instance, the user may request personalized streaming media 193 by activating a button on a remote control device associated with the display 113.
Upon receiving the request, the media service 123 determines the content of the streaming media 189 being received by the receiver application 183. In one embodiment, the media service 123 determines the media content information 173 from a metadata associated with the broadcast of the streaming media 189. For instance, the media content information 173 may comprise lyrics of a song, a transcript for the audio component of a movie, text summarizing the subject matter of the media, text summarizing the media on a per frame basis, and/or any other description of the media. In another embodiment, the media content information 173 may comprise a closed-caption of the media if closed-captioning is provided with the streaming media 189 and/or any other type of audio transcription of the streaming media 189.
Having determined the media content information 173, the media service 123 may store the data in the data store 116. For instance, the media service 123 may determine the media name 169 by parsing the metadata associated with the broadcast of the streaming media 189. As example, the media service 123 may store the name of the streaming media 189 as the media name 169, the content of the metadata as the media content information 173, and any frame identification information as the frame identifier 176 if the media content information 173 is specific to specific video frames of the streaming media 189. In one embodiment, the frame identifier 176 may correspond to specific portion of the streaming media 189 described by the media content information 173.
Next, the media service 123 identifies the files 136 in the user's file system 133 that relate to the content of the streaming media 189. In one embodiment, the media service 123 may search the user's file system 133 for files 136 having file names 149 that match the media name 169 associated with the streaming media 189. The media service 123 may determine that that files 136 with a file name 149 that match the media name 169 of the streaming media 189 may be related. In another embodiment, the media service 123 may search the user's file system 133 for files 136 matching the media content information 173. For example, the media service 123 may search for file names 149 of the files 136 in the file system 133 that match the media content information 173. The media service 123 may determine that any files 136 with file names 149 that match the media content information 173 relate to the content of the streaming media 189. For instance, using the above example, the user may have an image file 136 of a famous painting prepared by the user having a file name 149 that matches the media name 169 of a streaming media 189 and/or the media content information 173 of the streaming media 189. The media service 123 determines that the image file 136 is related to the streaming media 189 by finding a match between the file name 149 of the image 136 and the media name 169 and/or the media content information 173 of the streaming media 189.
In another embodiment, the media service 123 may also search metadata associated with files 136 to identify the files that are related to the streaming media 189. For example, the metadata may include a description of the subject matter of the files, such as for instance, lyrics of a music file, transcript of a video file, a description of a picture file, and/or other description. The media service 123 may compare the content of the metadata associated with each of the files 136 with the media content information 173 to identify files 136 that are related to the streaming media 189. Having identified the files 136 related to the streaming media 189, the media service 123 stores a listing of the identified files 136 in the data store 116 as related files 146. For instance, the media service 123 associates the listing of related files 146 with the media data 139 for each streaming media 189.
Next, the media service 123 gathers the content of the related files 146 to generate the personalized streaming media 193. For instance, the related files 146 may include a listing of file names 149 identifying the related files, as described above. In one embodiment, the media service 123 determines the content from the data object reference 156 associated with each of the file names 149 in the listing of related files 146. For example, the data object reference 156 includes a key value that identifies the data object associated with the file name 149. In one embodiment, the media server 123 determines that the data object associated with the file name 149 is the content of the file 136.
Once the content of each of the related files 146 is determined, the media service 123 embeds the content of the related files 146 in relevant portion of the streaming media 189 to generate the personalized streaming media 193. As an example, the content of a related file 146 may be an image and/or any other type of media. The media service 123 includes the image in a relevant portion of the streaming media 189 to generate the personalized streaming media 193. In addition, the content of the related file 146 may be music, a video clip, a three-dimensional video, and/or any other type of media. The media service 123 may include the media found in the related files 146 in a relevant portion of the streaming media 189.
In one embodiment, the media service 123 identifies the relevant portion of the streaming media 189 to include the content of the related files 146 from frame identifier 176. For instance, the relevant frame for the media content information 173 is stored as the frame identifier 176 in the media data 139, as described above. Using the above example, the media service 123 includes the image and/or any other type of media in the frame identified by the frame identifier 176. In one embodiment, the media service embeds the image into the video frame to generate the personalized streaming media 193. Similarly, the media service may embed any other type of media file, such as, for instance, overlaying a music file as the audio portion of a video clip, embed a video file as video playing in the background of the video clip, and/or any other approach to embed a media file into a video clip. Upon generating the personalized streaming media 193, the media service 123 transmits the personalized streaming media 193 to the requesting service, such as, for instance, the client side application 179 and/or any other application 126.
In one embodiment, the streaming media 189 may include identifiers within the media that can be used for embedding the content of the related files 146. For instance, using the above example where the streaming media 189 is a video, the streaming media 189 may include one or more header frames that include frame data that can be used for embedding the content of related files 146. As an example, the media service 123 may use the frame data to identify relevant portions of the streaming media 189 for embedding the content of the related files 146. In this embodiment, the frame data may indicate a type of media file 136 that may be embedded within the frame associated with the frame data. For instance, the frame data may indicate that the frame may be compatible for an image file 136, an audio file 136, a video file 136, and/or any other type of media file 136 to be embedded within a particular frame. As such, the media service 123 may only embed relevant files 146 that include content compatible with the types of media files 136 indicated by the frame data.
Referring next to
Referring next to
Moving on to
According to one embodiment, the media service 123 generates personalized streaming media 193 (
Beginning with box 403, the media service 123 determines the content of the streaming media 189 received from a broadcast source. In one embodiment, the media service 123 determines the content of the streaming media 189 from a metadata associated with the streaming media 189. For example, the metadata may include a summary of the streaming media 189a, closed captioning of the streaming media 189a, a frame-by-frame description of the streaming media 189a, a transcript of the streaming media 189a, and/or any other type of description of the streaming media 189. The media service 123 may parse the metadata of the streaming media 189 to search for keywords that describe the content of the streaming media 189.
Then, in box 406, the media service 123 stores the keywords and any other information from the metadata in a data store 116 (
Next, in box 409, the media service 123 identifies files 136 (
Then, in box 413, the media service 123 generates personalized streaming media 193 (
Referring next to
According to one embodiment, the client side application 179 generates a request for personalized streaming media 193 (
Beginning with box 503, the client side application 179 generates and transmits a request for personalized streaming media 193 that includes content from a user's file system 133 (
Then, in box 506, the client side application 179 receives the personalized streaming media 193 including related content from the user's file system 133. In one embodiment, related content from the user's file system 133 is determined from metadata associated with the streaming media 189. For instance, the meta data may include a summary of the streaming media 189, closed captioning of the streaming media 189, a frame-by-frame description of the streaming media 189, and/or any other type of description of the streaming media 189. Related files 146 (
With reference to
Stored in the memory 606 are both data and several components that are executable by the processor 603. In particular, stored in the memory 606 and executable by the processor 603 are the file service 119, the media service 123, and potentially other applications 126. Also stored in the memory 606 may be a data store 113 and other data. In addition, an operating system may be stored in the memory 606 and executable by the processor 603.
It is understood that there may be other applications that are stored in the memory 606 and are executable by the processors 603 as can be appreciated. Where any component discussed herein is implemented in the form of software, any one of a number of programming languages may be employed such as, for example, C, C++, C#, Objective C, Java, Javascript, Perl, PHP, Visual Basic, Python, Ruby, Delphi, Flash, or other programming languages.
A number of software components are stored in the memory 606 and are executable by the processor 603. In this respect, the term “executable” means a program file that is in a form that can ultimately be run by the processor 603. Examples of executable programs may be, for example, a compiled program that can be translated into machine code in a format that can be loaded into a random access portion of the memory 606 and run by the processor 603, source code that may be expressed in proper format such as object code that is capable of being loaded into a random access portion of the memory 606 and executed by the processor 603, or source code that may be interpreted by another executable program to generate instructions in a random access portion of the memory 606 to be executed by the processor 603, etc. An executable program may be stored in any portion or component of the memory 606 including, for example, random access memory (RAM), read-only memory (ROM), hard drive, solid-state drive, USB flash drive, memory card, optical disc such as compact disc (CD) or digital versatile disc (DVD), floppy disk, magnetic tape, or other memory components.
The memory 606 is defined herein as including both volatile and nonvolatile memory and data storage components. Volatile components are those that do not retain data values upon loss of power. Nonvolatile components are those that retain data upon a loss of power. Thus, the memory 606 may comprise, for example, random access memory (RAM), read-only memory (ROM), hard disk drives, solid-state drives, USB flash drives, memory cards accessed via a memory card reader, floppy disks accessed via an associated floppy disk drive, optical discs accessed via an optical disc drive, magnetic tapes accessed via an appropriate tape drive, and/or other memory components, or a combination of any two or more of these memory components. In addition, the RAM may comprise, for example, static random access memory (SRAM), dynamic random access memory (DRAM), or magnetic random access memory (MRAM) and other such devices. The ROM may comprise, for example, a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other like memory device.
Also, the processor 603 may represent multiple processors 603 and the memory 606 may represent multiple memories 606 that operate in parallel processing circuits, respectively. In such a case, the local interface 609 may be an appropriate network 109 (
Although the file service 119, the media service 123, the application(s) 126, and other various systems described herein may be embodied in software or code executed by general purpose hardware as discussed above, as an alternative the same may also be embodied in dedicated hardware or a combination of software/general purpose hardware and dedicated hardware. If embodied in dedicated hardware, each can be implemented as a circuit or state machine that employs any one of or a combination of a number of technologies. These technologies may include, but are not limited to, discrete logic circuits having logic gates for implementing various logic functions upon an application of one or more data signals, application specific integrated circuits having appropriate logic gates, or other components, etc. Such technologies are generally well known by those skilled in the art and, consequently, are not described in detail herein.
The flowcharts of
Although the flowcharts of
Also, any logic or application described herein, including the file service 119, the media service 123, and application(s) 126, that comprises software or code can be embodied in any non-transitory computer-readable medium for use by or in connection with an instruction execution system such as, for example, a processor 603 in a computer system or other system. In this sense, the logic may comprise, for example, statements including instructions and declarations that can be fetched from the computer-readable medium and executed by the instruction execution system. In the context of the present disclosure, a “computer-readable medium” can be any medium that can contain, store, or maintain the logic or application described herein for use by or in connection with the instruction execution system. The computer-readable medium can comprise any one of many physical media such as, for example, magnetic, optical, or semiconductor media. More specific examples of a suitable computer-readable medium would include, but are not limited to, magnetic tapes, magnetic floppy diskettes, magnetic hard drives, memory cards, solid-state drives, USB flash drives, or optical discs. Also, the computer-readable medium may be a random access memory (RAM) including, for example, static random access memory (SRAM) and dynamic random access memory (DRAM), or magnetic random access memory (MRAM). In addition, the computer-readable medium may be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or other type of memory device.
It should be emphasized that the above-described embodiments of the present disclosure are merely possible examples of implementations set forth for a clear understanding of the principles of the disclosure. Many variations and modifications may be made to the above-described embodiment(s) without departing substantially from the spirit and principles of the disclosure. All such modifications and variations are intended to be included herein within the scope of this disclosure and protected by the following claims.
Number | Name | Date | Kind |
---|---|---|---|
5416529 | Lake | May 1995 | A |
5422674 | Hooper et al. | Jun 1995 | A |
5715018 | Fasciano et al. | Feb 1998 | A |
6029045 | Picco et al. | Feb 2000 | A |
6323861 | Carraro et al. | Nov 2001 | B1 |
6680739 | Robertus et al. | Jan 2004 | B1 |
6757027 | Edwards et al. | Jun 2004 | B1 |
6944585 | Pawson | Sep 2005 | B1 |
7015979 | Lord et al. | Mar 2006 | B1 |
7312803 | Wilkins | Dec 2007 | B2 |
7460731 | Senftner et al. | Dec 2008 | B2 |
7484103 | Woo et al. | Jan 2009 | B2 |
7610597 | Johnson et al. | Oct 2009 | B1 |
7613691 | Finch | Nov 2009 | B2 |
7624416 | Vandermolen et al. | Nov 2009 | B1 |
7873982 | Smith et al. | Jan 2011 | B2 |
7912217 | Baugher et al. | Mar 2011 | B2 |
7974493 | Senftner et al. | Jul 2011 | B2 |
8005973 | Collet et al. | Aug 2011 | B2 |
8074248 | Sigmon et al. | Dec 2011 | B2 |
8156435 | Wohlert | Apr 2012 | B2 |
8219536 | Wohlert | Jul 2012 | B2 |
8245252 | Gee et al. | Aug 2012 | B2 |
8266246 | Cho et al. | Sep 2012 | B1 |
8340498 | Gill et al. | Dec 2012 | B1 |
8356324 | Rajakarunanayake | Jan 2013 | B2 |
8397253 | McDonough et al. | Mar 2013 | B2 |
8495674 | Johnson et al. | Jul 2013 | B1 |
8495675 | Philpott et al. | Jul 2013 | B1 |
8510771 | Casagrande et al. | Aug 2013 | B2 |
8527877 | Wohlert | Sep 2013 | B2 |
8539523 | Philpott et al. | Sep 2013 | B2 |
8542743 | Van Den Berghe | Sep 2013 | B2 |
8589992 | Babic | Nov 2013 | B2 |
8843957 | Lemire et al. | Sep 2014 | B2 |
9031127 | Hannuksela | May 2015 | B2 |
9042454 | Gordon et al. | May 2015 | B2 |
9077860 | Sigmon et al. | Jul 2015 | B2 |
20020059604 | Papagan et al. | May 2002 | A1 |
20020083184 | Elliott | Jun 2002 | A1 |
20020092019 | Marcus | Jul 2002 | A1 |
20020156842 | Signes et al. | Oct 2002 | A1 |
20020171670 | Clernock et al. | Nov 2002 | A1 |
20030135553 | Pendakur | Jul 2003 | A1 |
20030177063 | Currans et al. | Sep 2003 | A1 |
20030191850 | Thornton | Oct 2003 | A1 |
20030212811 | Thornton | Nov 2003 | A1 |
20040049780 | Gee | Mar 2004 | A1 |
20050278565 | Frattura et al. | Dec 2005 | A1 |
20060015904 | Marcus | Jan 2006 | A1 |
20060074744 | Bodlaender et al. | Apr 2006 | A1 |
20060090010 | Qin | Apr 2006 | A1 |
20070005795 | Gonzalez | Jan 2007 | A1 |
20070022215 | Singer et al. | Jan 2007 | A1 |
20070061364 | Klein, Jr. | Mar 2007 | A1 |
20070061759 | Klein, Jr. | Mar 2007 | A1 |
20070088844 | Seims | Apr 2007 | A1 |
20070244983 | Berger | Oct 2007 | A1 |
20070300249 | Smith et al. | Dec 2007 | A1 |
20070300250 | Smith et al. | Dec 2007 | A1 |
20080019576 | Senftner et al. | Jan 2008 | A1 |
20080120364 | Chari et al. | May 2008 | A1 |
20080126109 | Cragun et al. | May 2008 | A1 |
20080127272 | Cragun et al. | May 2008 | A1 |
20080134278 | Al-Karmi | Jun 2008 | A1 |
20080168489 | Schraga | Jul 2008 | A1 |
20080170622 | Gordon et al. | Jul 2008 | A1 |
20080235722 | Baugher et al. | Sep 2008 | A1 |
20080263098 | Kindig | Oct 2008 | A1 |
20090080855 | Senftner et al. | Mar 2009 | A1 |
20090089354 | Kim et al. | Apr 2009 | A1 |
20090122873 | Van Den Berghe | May 2009 | A1 |
20090244289 | Raake et al. | Oct 2009 | A1 |
20090257730 | Chen et al. | Oct 2009 | A1 |
20090307732 | Cohen et al. | Dec 2009 | A1 |
20100036808 | Lee | Feb 2010 | A1 |
20100049862 | Dixon | Feb 2010 | A1 |
20100057926 | Cao et al. | Mar 2010 | A1 |
20100131527 | Wohlert | May 2010 | A1 |
20100131844 | Wohlert | May 2010 | A1 |
20100131895 | Wohlert | May 2010 | A1 |
20100145938 | Boetje et al. | Jun 2010 | A1 |
20100162291 | Casagrande et al. | Jun 2010 | A1 |
20100202750 | Senftner et al. | Aug 2010 | A1 |
20100299191 | Fernandez Gutierrez | Nov 2010 | A1 |
20100313131 | Yuen | Dec 2010 | A1 |
20100332329 | Roberts et al. | Dec 2010 | A1 |
20110023063 | McDonough et al. | Jan 2011 | A1 |
20110145370 | Nieuwenhuys | Jun 2011 | A1 |
20110145858 | Philpott et al. | Jun 2011 | A1 |
20110302308 | Prodan et al. | Dec 2011 | A1 |
20110314493 | Lemire et al. | Dec 2011 | A1 |
20110321086 | Buchheit et al. | Dec 2011 | A1 |
20120047542 | Lewis et al. | Feb 2012 | A1 |
20120137337 | Sigmon et al. | May 2012 | A1 |
20120143996 | Liebald et al. | Jun 2012 | A1 |
20120180083 | Marcus | Jul 2012 | A1 |
20120192221 | McDonough et al. | Jul 2012 | A1 |
20120192226 | Zimmerman et al. | Jul 2012 | A1 |
20120227077 | Spivack et al. | Sep 2012 | A1 |
20120246279 | Zang et al. | Sep 2012 | A1 |
20120254755 | Wohlert | Oct 2012 | A1 |
20120297417 | Philpott et al. | Nov 2012 | A1 |
20130046781 | Frankel et al. | Feb 2013 | A1 |
20130073684 | Fernandez Gutierrez | Mar 2013 | A1 |
20130097642 | Cragun et al. | Apr 2013 | A1 |
20130173709 | Yerli | Jul 2013 | A1 |
20130202150 | Sinha et al. | Aug 2013 | A1 |
20130204889 | Sinha et al. | Aug 2013 | A1 |
20130205212 | Sinha et al. | Aug 2013 | A1 |
20130205315 | Sinha et al. | Aug 2013 | A1 |
20130205316 | Sinha et al. | Aug 2013 | A1 |
20130205317 | Sinha et al. | Aug 2013 | A1 |
20130205318 | Sinha et al. | Aug 2013 | A1 |
20130205319 | Sinha et al. | Aug 2013 | A1 |
20130205321 | Sinha et al. | Aug 2013 | A1 |
20130205322 | Sinha et al. | Aug 2013 | A1 |
20130205323 | Sinha et al. | Aug 2013 | A1 |
20130205324 | Sinha et al. | Aug 2013 | A1 |
20130205325 | Sinha et al. | Aug 2013 | A1 |
20130205326 | Sinha et al. | Aug 2013 | A1 |
20130205330 | Sinha et al. | Aug 2013 | A1 |
20130205335 | Sinha et al. | Aug 2013 | A1 |
20130205338 | Sinha et al. | Aug 2013 | A1 |
20130212609 | Sinha et al. | Aug 2013 | A1 |
20130238757 | Cho et al. | Sep 2013 | A1 |
20130275611 | Somekh et al. | Oct 2013 | A1 |
20130290307 | Boetje et al. | Oct 2013 | A1 |
20140086338 | Lu et al. | Mar 2014 | A1 |
20140099066 | Jang et al. | Apr 2014 | A1 |
20140363143 | Dharssi et al. | Dec 2014 | A1 |