Text-to-speech (TTS) systems convert raw text into sound using a process sometimes known as speech synthesis. In a common implementation, a TTS system may comprise a computing device configured to receive text input and provide an audio presentation of the text input. Some TTS systems provide a number different language modules and voice modules. Language modules enable a TTS system to receive and process text in a written language, such as American English, German, or Italian. Voice modules enable a TTS system to output an audio presentation in a specific voice, such as French female, Spanish male, or Portuguese child.
TTS systems first preprocess raw text input by disambiguating homographs, expanding abbreviations and symbols (e.g., numerals) into words, and other such operations. The preprocessed text input can be converted into a sequence of words or subword units, such as phonemes or diphones. The resulting sequence is then associated with acoustic and/or linguistic features of a number small speech recordings, also known as speech segments. The phoneme sequence and corresponding acoustic and/or linguistic features are used to select and concatenate recorded and synthetic speech segments into an audio presentation of the input text.
TTS systems may be configured to generate audio presentations from message text, such as electronic mail (email) and text messages, and play back the audio presentations to a user. Some applications that include TTS functionality facilitate entry of network addresses of content, such as uniform resource locators (URLs). Such applications may be configured to retrieve text content from the location corresponding to the entered URL, generate an audio presentation of the content, and transmit or playback the audio presentation to a user.
Throughout the drawings, reference numbers may be re-used to indicate correspondence between referenced elements. The drawings are provided to illustrate example embodiments described herein and are not intended to limit the scope of the disclosure.
Introduction
Generally described, the present disclosure relates to speech synthesis systems. Specifically, aspects of the disclosure relate to generating text-to-speech (TTS) audio programs from textual content received from multiple sources. A TTS system may assemble an audio program from several individual audio presentations of user-selected content. Users may configure the TTS system to retrieve personal content, such as electronic mail (email) and social network messages, as well as publically accessible content, such as the news, for processing and inclusion in the audio program. The audio program may include segues, introductions, summaries, and the like.
Additional aspects of the disclosure relate to selecting voices from which to generate the individual audio presentations. The selection may be automatic and based on the source of the content, such as using various male and female voices for emails from senders of the corresponding gender. Additional or alternative factors that may be considered when selecting a voice include the subject of the content and user preferences. For example, hard news stories may be presented by alternating male and female voices configured to speak in the informative style of live newscasters, while opinion or entertainment columns may be presented by voices configured to sound more friendly or humorous. Users may also select a voice to be used, such as for a general type of content or for a specific source.
Although aspects of the embodiments described in the disclosure will focus, for the purpose of illustration, on interactions between a client device, an audio program server, and a number of content servers, one skilled in the art will appreciate that the techniques disclosed herein may be applied to any number of hardware or software processes or applications. Further, although various aspects of the disclosure will be described with regard to illustrative examples and embodiments, one skilled in the art will appreciate that the disclosed embodiments and examples should not be construed as limiting. Various aspects of the disclosure will now be described with regard to certain examples and embodiments, which are intended to illustrate but not limit the disclosure.
With reference to an illustrative embodiment, a user may access a user interface provided by or associated with an audio program server. The user may indicate or select network-accessible content from any number of sources for inclusion in the audio program generated for the user. The content may include publically accessible content, such as the content pages and Really Simple Syndication (RSS) feeds provided by news, sports, and entertainment content providers. The content may also be personal, such as email, social network messages, and the like. The audio program server may process the selected content to extract the meaningful portion (e.g.: the text of the article) and exclude portions which are not to be included in the audio presentation (e.g.: advertisements). The content may also include content that already exists in audio format, such as audio books.
The audio program server may include a TTS system for generating audio presentations from text input. A TTS system may include tens or hundreds of different voices and different languages. Users may select which voices to use for each content type or source, or the audio program server may automatically select an appropriate voice. For example, a user's email messages from senders detected as being female based on the sender's name may converted into audio presentation using female voice. Different female voices may be used for messages from different female senders. News-related and other informative content may be converted into audio presentations using neutral sounding voices, while sports and entertainment content may be converted into presentations using more lively sounding voices. The text itself may be analyzed as well. More somber news stories may be converted into presentations using voices which sound serious or hushed, and the speed may be adjusted to reflect the somber mood of the content. The speed and tone of lighter stories may also be adjusted accordingly.
The audio program server may assemble the audio presentations into a single audio program. Segues may be included between audio presentations. The segues may include music from a user's local device, from a network-accessible music storage, or they may be chosen from a group of segues provided by the audio program server. Additionally, summaries may be included. For example, a summary may be inserted at the beginning of the audio program, and may inform the user about which content the program contains (e.g.: 2 emails, 3 news stories, and 4 social network messages).
The generated audio programs may be delivered to the user in any appropriate method. For example, the audio program may be streamed to a user device from the audio program server, transmitted as a single file or group of files, or distributed through a newscast distribution network. A user may use an audio program playback application that includes controls for rewinding, fast-forwarding, skipping audio presentations, repeating audio presentations, or selecting an individual audio presentation to play. In some embodiments, the audio program playback application may accept voice input and perform audio program navigation through the use of speech recognition.
Controls or voice commands may be enabled to allow a user to tag or otherwise select an audio presentation for further action. For example, an audio program may include an email message that a user would like to tag for follow-up. The user may activate a control, speak a voice command, or perform some other user interface action to tag the email. The user's email server may then be updated or notified to add a tag to the email so that the email will be tagged when the user subsequently accesses the email, such as via an email client on a personal computing device. The tagging feature is not limited to emails. Users may tag any content item and receive a subsequent notification regarding the tagged item. For example, an audio program may include an audio presentation of a content item. A user may perform some user interface action to tag the content. An email or notification may be sent to the user with a link to the content or the text of the content on which the audio presentation was based. In some cases, the user's account with the audio program server may be updated to reflect the tagged content. For example, the user may subsequently access an account profile page, and links, notifications, or other information about tagged content items may be presented to the user.
Network Computing Environment
Prior to describing embodiments for generating audio programs based on user selected content in detail, an example network computing environment in which these features can be implemented will be described.
The network 100 may be a publicly accessible network of linked networks, possibly operated by various distinct parties, such as the Internet. In other embodiments, the network 100 may include a private network, personal area network, local area network, wide area network, cable network, satellite network, etc. or some combination thereof, each with access to and/or from the Internet.
The audio program server 102 can include any computing system that is configured to communicate via network 100. For example, the audio program server 102 may include a number of server computing devices, desktop computing devices, mainframe computers, and the like. In some embodiments, the audio program server 102 can include several devices or other components physically or logically grouped together.
The client device 104 may correspond to any of a wide variety of computing devices, including personal computing devices, laptop computing devices, in-car dashboard systems, hand held computing devices, terminal computing devices, mobile devices (e.g., mobile phones, tablet computing devices, etc.), wireless devices, electronic book readers, media players, and various other electronic devices and appliances. A client device 104 generally includes hardware and software components for establishing communications over the communication network 100 and interacting with other network entities to send and receive content and other information.
Various content providers 106-118 may be accessed via the network 110. For example, a music server 106 may be configured to store, sell, stream, or otherwise provide access to music. A user of a client device 104 may obtain an account with the music server 106, and may therefore have access to at least a portion of the music hosted by the music server 106. The audio program server 102 may retrieve music associated with the user to use for segues and introductions in the generated audio programs. A user may also have an account with an email server 108, such as a server configured to provide simple mail transfer protocol (SMTP) access to email messages. The user may authorize the audio program server 102 to retrieve email messages from the email server 108 for inclusion in audio programs generated for the user. In addition, a user may have an account with a social network 110, such as a system configured to facilitate communication and content sharing between groups of users. The user may authorize the audio program server 102 to retrieve messages and other content associated with the user from the social network 110.
Publically accessible content providers, such as a portal server 112, news content provider 114, RSS server 116, search engine 118, and any number of other text content servers 150, audio content servers 160, and the like may also be accessed by the audio program sever 102. The example content providers, servers, and hosts illustrated in
Turning now to
The data aggregator 120, text preprocessor, TTS engine 124, and program assembler 126 may be implemented on one or more application server computing devices. For example, each component may be implemented as separate hardware component or as a combination of hardware and software. In some embodiments, two or more components may be implemented on the same physical device.
The user data store 128 may be implemented on a database server computing device configured to store records, audio files, and other data related to the generation of audio presentations and the assembly of audio programs based on the audio presentations and other content. In some embodiments, the audio program server 102 may include a server computing device configured to operate as a remote database management system (RDBMS). The user data store 128 may include one or more databases hosted by the RDBMS. The user data store 128 may be used to store user selections of content, user passwords for personalized or private content such as email, and other such data. The data aggregator 120, program assembler 126, and other components of the audio program server 102 may access the data in the user data store 128 in order to determine, among other things, which voices to use or the order of the audio presentation within the assembled audio program.
In operation, the data aggregator 120 may access the user data store 128 to determine the content sources 106-118 from which to retrieve data for processing. Once the data aggregator 120 has received a content item, it may process the content in order to extract the text on which an audio presentation will ultimately be based. Extraction of such meaningful textual content from a content page that may include superfluous or other undesirable content (e.g.: advertisements, reader comments) may be performed using web scraping techniques or according to other techniques known to those of skill in the art. The data aggregator 120 may also prepare a summary of all content that is to be included in the audio program. For example, the data aggregator 120 may calculate the number and type of each content item received. A summary may include high level detail such as the number of personal messages, the number of news articles, etc. The summary may be prepared as plain text to facilitate conversion by the text preprocessor 122 and TTS engine 124.
The text preprocessor 122 may be configured to receive the raw text input from the data aggregator and process it into a form more suitable for text-to-speech conversion by the TTS engine 124. The preprocessing may include expansion of abbreviations and acronyms into full words. Such expansion may be particularly useful for certain types of network-accessible content (e.g.: email, social network posts, micro blogs). Other types of network-accessible content may be summarized or otherwise distilled from a full text form. For example, attachments to emails may be summarized according to various natural language understanding (NLU) algorithms so that they may be briefly described in the audio program without consuming more program time and storage space than may be desirable and for the convenience of the listener.
The TTS engine 124 may be configured to process input from the text preprocessor 122 and generate audio files or steams of synthesized speech. For example, when using a unit selection technique, a TTS engine 124 may convert text input into a sequence of subword units, associate acoustic and/or linguistic features with the subword units of the sequence, and finally arrange and concatenate a sequence of recorded or synthetic speech segments corresponding to the acoustic and/or linguistic features and the sequence of subword units. The TTS processing described herein in meant to be illustrative only, and not limiting. Other TTS processes known to those of skill in the art may be utilized (e.g., statistical parametric-based techniques, such as those using hidden Markov models).
The program assembler 126 can obtain user data 128 and the various audio presentations generated by the TTS engine 124. The program assembler 126 may then arrange the audio presentations, as well as segues, introductions, pre-existing audio content, and the like according to user preferences. For example, the program assembler may retrieve music files associated with the user or otherwise accessible by the audio program server 102. The music files may be included between individual audio presentations. The program assembler 126 or some other component of the audio program server may then transmit or stream the audio program to the user or some user-accessible location.
User Configuration of an Audio Program
Turning now to
The process 300 of configuring user data regarding an audio program begins at block 302. The process 300 may be executed by a local browser component or by a program stored on the client device 104 and associated with the audio program server 102. In some embodiments, the process 300 may be embodied in a set of executable program instructions and stored on a computer-readable medium drive associated with the client device 104. When the process 300 is initiated, the executable program instructions can be loaded into memory, such as RAM, and executed by one or more processors of the client device 104.
At block 304, the user may indicate a choice for a content item to be included in the user's audio program. For example, the user may enter a URL, select a content source from a listing of predetermined content sources, or otherwise provide the audio program server 102 with information regarding the location of the selected content. Advantageously, the user need not specify each individual content item to include in the audio program. The user may instead provide an indication of which content portion of the content items (e.g.: a display portion of a content page) the user wishes to include. For example, a content page may include a number of textual components, such as headlines, a main article, and other information. One user may select the main article for inclusion, while another user may choose to have the top headlines read for the audio program. In some embodiments, the user may select an automated content distribution service, such as RSS feed. When the audio program is generated, the audio program server 102 may obtain the most recent content associated with the RSS feed for inclusion in the audio program. Additionally, predefined content queries and searches may be added to the audio program. As with RSS feeds, the audio program server 102 may execute the query at the time of audio program generation and include the most recent and/or relevant results in the audio program.
At block 306, the user may provide login information or provide authorization to the audio program server 102 in cases when the selected content is password protected or otherwise private. Some content servers require additional information for accessing private data, such as personal questions or image recognition. The user may provide additional information, such as the security information that the user has proved to the content provider.
At block 308, the user may determine TTS configuration settings for the current content. The TTS configuration settings may include which voice to utilize when generating an audio presentation of the content or which speed or other effect to apply to the voice. Additional configuration settings may include identifying a position within the audio program sequence to insert the audio presentation of the content or whether to summarize the content or portions thereof (e.g.: email attachments) with automated NLU techniques.
At block 310, the user may identify a segue to precede or follow the content. Segues may be audio clips from music supplied by the audio program server 102, supplied by the user, or supplied by a network-accessible service. For example, a user may have access to a number of music files on the local client device 102. The user may upload a particular music file to the audio program server 102 and indicate which portion or portions of the music file to use as a segue. If a music file is stored in a network-accessible location, such as a music server 106, the user may provide information to access the music file, such as a URL, internet protocol (IP) address, or some other information with which to identify the location of the music file.
At decision block 312 the user may determine whether there is additional content to add to or configure for the audio program. If there are more content items, the process 300 may return to block 304 as many times as necessary to add each desired content item or to configure each previously added content item. Otherwise, the process 300 may proceed to block 314, where execution terminates. In some embodiments, the user may select general configuration properties associated with the audio program. For example, the user may specify a preferred delivery method or location, a delivery schedule, and other such configuration settings.
Assembly of Audio Programs
Turning now to
The process 400 begins at block 402. In some embodiments, the process 400 may be embodied in a set of executable program instructions and stored on a computer-readable medium drive associated with a computing system. When the process 400 is initiated, the executable program instructions can be loaded into memory, such as RAM, and executed by one or more processors of the computing system. In some embodiments, the computing system may encompass multiple computing devices, such as servers, and the process 400 may be executed by multiple servers, serially or in parallel. Initiation of the process 400 may occur in response to an on-demand request from a user, according to a schedule, or in response to some event. For example, an audio program may be generated each morning and transmitted to a user prior to the user's commute to work.
At block 404, the data aggregator 120 may retrieve a content item according to the selections of the user. The data aggregator 120 may load or access data in the user data store 128 associated with the user and with the current audio program. The data may indicate a URL or other address to use in order to retrieve the content. The content items may be retrieved according to the order in which they will be placed in the audio program, or in some other order. Some content items may private, and may therefore require a password in order to retrieve them. For example, email messages, social network messages and posts, and other personalized or sensitive content may require the data aggregator 120 to present a password or some other form of authorization. A password may have been previously supplied by the user and stored within the user data store 128. The data aggregator 120 may retrieve the password from the data store 128 and pass it to the content server. SMTP servers may be configured to accept passwords without user interaction. For other types of content, the data aggregator may generate a Hypertext Transfer Protocol (HTTP) POST request that includes the password, or it may use some other technique.
At block 406, the data aggregator 120 may extract the meaningful portion of the content item. Many content items include meaningful textual content and a number of additional elements (e.g.: advertisements, reader comments, image captions) which are not to be included in the audio presentation of the content. The user may have defined the interesting section when configuring the content item, as described above with respect to
At block 408, the text preprocessor 122 may summarize content with a size exceeding a threshold, content which is a specific type, content that the user has indicated should be summarized, etc. Summaries may be useful for lengthy content, linked content, and attached content. Additionally, if a user selects a large number of content items to include in the audio presentation, one or more of the content items may be summarized in order to conserve storage space, bandwidth, computing capacity, and to ensure that the resulting audio program is not too long.
At block 410, the text preprocessor 122 may further process the text into a format suitable for input to a TTS engine. Preprocessing may include expansion of abbreviations and symbols into their full word representations. This may be useful for certain kinds of text, such as email messages and social network postings, which may include abbreviations or symbols, such as smiley faces. Additional preprocessing actions may include disambiguation of homographs, translation of embedded foreign text, and the like. The preprocessed text may be provided to the TTS engine 124.
At block 412, the TTS engine 124 may generate an audio presentation of preprocessed text input by utilizing voice data corresponding to a selected or desired voice. An audio presentation of each content item may be generated utilizing the same voice. In some embodiments, audio presentations may be generated utilizing two or more different voices. The voice for any particular content item may be selected based on user data retrieved from the user data store 128, determined by the user as described above.
In some cases a voice may be automatically selected by the TTS engine 124 or some other component of the audio program server 102. The selection may be based on characteristics of the content or the content source. For example, email messages from females may be converted to an audio presentation by utilizing a female voice. Messages from different females may be associated with different voices randomly or according to some additional characteristic of the content, such as its subject matter.
Additional characteristics of the content may influence the selection of a voice. For example, the subject matter of the content may be more suited to some voices than others. Individual voices may provide better performance (e.g.: more natural sounding results) for long passages of text, while others provide better performance for specific vocabulary (e.g.: highly technical content). As described above, the tone of the content may also be considered. Audio presentations of somber content, such as certain news articles, may be generated utilizing appropriately somber or neutral adult voices rather than voices based on children's speech patterns.
The speed of the voice or the resulting audio presentation may also be customized. Returning to the news example, audio presentations of certain news stories may be generated with longer pauses, slower speech patterns, and the like. In contrast, audio presentations of entertainment news or sports scores may be generated with shorter pauses and faster speech patterns.
The voices selected for other audio presentations to be included in the audio program may also be considered. For example, block 412 may be executed separately, either sequentially or in parallel, for each individual content item that is to be included in the audio program. If two or more news articles are selected, then different voices may be utilized in order to prevent monotony or enhance the naturalness of the audio program. Live news casts often include two or more individuals reading the news. This characteristic may be mimicked in the audio program by selecting two or more voices with the appropriate tone for news content, such as an adult male voice and an adult female voice each configured to sound neutral and informative. Each news article (or other content item) may be associated with the multiple voices. The voice that is used to generate the audio presentation may also be selected based on which voice was used for the preceding or subsequent audio presentation, among other factors. As shown in
In some embodiments, two or more voices may be used to generate an audio presentation of a single content item. For example, a content item may include dialogue between two individuals, such as an interviewer and an interviewee. A voice may be assigned to each of the individuals, and the audio presentation of the content item may therefore mimic a conversation rather than a narration. The portion of the content that corresponds to the first individual (e.g.: the interviewer) can be processed into the audio presentation by using a first voice, and the portion that corresponds to the second individual (e.g.: the interviewee) can be processed using the second voice. Quotations in content items, such as news articles, may be presented in a similar fashion, with the main article text processed using the voice that is selected for the article, and quotations from one or more individuals processed using voices selected for each of the individuals. The quotations can be detected based on the formatting of the original document or the presence of quotation marks or certain words (e.g.: said) preceding or following a sentence or other grouping of words.
In some embodiments, voices may be selected for some or all of the individuals based on characteristics associated with the individual as determined from the text, such as gender, age, and the like. In additional embodiments, voices may be selected for some or all of the individuals based on NLU or other processing of the text attributed to an individual, such as the meaning of the text, the subject matter of the text, or other characteristics.
At block 414, a segue may be chosen for insertion before or after the audio presentation for the current content item. The segue may be based on a music file or a portion thereof. The must file may be a network accessible music file or a file local to the client device that is uploaded or otherwise proved to the audio program server. As shown in
At block 416, the audio program server 102 may determine whether there are additional content items to process and include in the audio program. If there are, the process may return to block 404 for each additional content item. Otherwise, the process 400 may proceed to block 418.
At block 418, a summary of the audio program may be generated for insertion at the beginning and/or end of the audio program. The summary may include a simple count of each type of content or content source. The summary may also be more descriptive and include brief summaries of certain content, as generated buy NLU algorithms and described above. The summary may be processed by the text preprocessor 122 and the TTS engine 124.
At block 420, the audio presentation of the summary may be assembled with the audio presentations of the content items into an audio program. The audio program may be a single file or stream, or it may include multiple files or streams and data regarding playback (e.g.: a playlist). The assembled audio program may then be provided to user according to the user's preferred delivery method.
Terminology
Depending on the embodiment, certain acts, events, or functions of any of the processes or algorithms described herein can be performed in a different sequence, can be added, merged, or left out all together (e.g., not all described operations or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, operations or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules, routines, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The steps of a method, process, routine, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of a non-transitory computer-readable storage medium. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC. The ASIC can reside in a user terminal. In the alternative, the processor and the storage medium can reside as discrete components in a user terminal.
Conditional language used herein, such as, among others, “can,” “could,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements and/or steps. Thus, such conditional language is not generally intended to imply that features, elements and/or steps are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding, with or without author input or prompting, whether these features, elements and/or steps are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
Conjunctive language such as the phrase “at least one of X, Y and Z,” unless specifically stated otherwise, is to be understood with the context as used in general to convey that an item, term, etc. may be either X, Y, or Z, or a combination thereof. Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y and at least one of Z to each be present.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it can be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As can be recognized, certain embodiments of the inventions described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain inventions disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Number | Date | Country | Kind |
---|---|---|---|
P401346 | Oct 2012 | PL | national |
Number | Name | Date | Kind |
---|---|---|---|
6671617 | Odinak et al. | Dec 2003 | B2 |
7454348 | Kapilow et al. | Nov 2008 | B1 |
8473297 | Jang et al. | Jun 2013 | B2 |
20020087224 | Barile | Jul 2002 | A1 |
20030004711 | Koishida et al. | Jan 2003 | A1 |
20050234958 | Sipusic et al. | Oct 2005 | A1 |
20060095848 | Naik | May 2006 | A1 |
20070124142 | Mukherjee | May 2007 | A1 |
20070156410 | Stohr et al. | Jul 2007 | A1 |
20080140406 | Burazerovic et al. | Jun 2008 | A1 |
20080141180 | Reed et al. | Jun 2008 | A1 |
20090202226 | McKay | Aug 2009 | A1 |
20090254345 | Fleizach et al. | Oct 2009 | A1 |
20090326948 | Agarwal et al. | Dec 2009 | A1 |
20100050064 | Liu et al. | Feb 2010 | A1 |
20100082328 | Rogers et al. | Apr 2010 | A1 |
20100082344 | Naik et al. | Apr 2010 | A1 |
20110106283 | Robinson | May 2011 | A1 |
20110124264 | Garbos | May 2011 | A1 |
20110153330 | Yazdani et al. | Jun 2011 | A1 |
20110161085 | Boda et al. | Jun 2011 | A1 |
20110167390 | Reed et al. | Jul 2011 | A1 |
20110313757 | Hoover et al. | Dec 2011 | A1 |
20120191457 | Minnis et al. | Jul 2012 | A1 |
20130124202 | Chang | May 2013 | A1 |
Number | Date | Country |
---|---|---|
WO 2011088053 | Jul 2011 | WO |
Number | Date | Country | |
---|---|---|---|
20140122079 A1 | May 2014 | US |