A common method of exchanging personal and/or business contact information from one person to another is through the exchange of physical printed business cards. Often, a given person may give and/or receive tens or even hundreds of printed business cards over the course of a given period of time. Upon receipt of a printed business card, the card recipient often desires to store the data from the card via an electronic contacts application. Unfortunately, storing the data via the electronic contacts application typically requires entry of the data by hand. Similarly, if the recipient already has contact information associated with a received business card, the recipient has no automated means for updating the contact information with new information received on the business card. Electronic card readers have been developed for storing a scanned image of a printed business card, but such readers do not allow for storage of individual typed data fields of a given card, for example, name, telephone number, address, and the like, or metadata that provides information about which of such data fields are included in the card.
In addition, contacts applications users often desire to send contact information to a recipient via an electronic communication method, such as electronic mail, but the contact information must be entered into an electronic mail message by hand or by a copy and paste operation. Such methods are cumbersome and do not provide for a succinct visual presentation of the contact information as is the case with a physical printed business card. According to the vCard standard, electronic business cards may be sent over digital media, but vCards do not carry a graphical visual representation of the contact information as is the case with physical printed business cards. Thus, sending contact information electronically in such a manner does not provide the sender a means for branding himself/herself as is possible with business cards that present unique logos or formatting properties.
It is with respect to these and other considerations that the present invention has been made.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features or essential features of the claimed subject matter, nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Embodiments of the present invention provide for generating electronic business cards from electronic contact information that may be rendered and displayed as single electronic business cards or as a collection of electronic business cards. According to this embodiment, all electronic contact files stored in an electronic mail application contacts data repository have one associated “electronic business card”, which is essentially a graphical presentation of the data in a business card format. Electronic business cards may be automatically generated by the electronic mail application according to one or more default templates, or electronic business cards may be customized manually by a user with unique logos, pictures, or other custom formatting properties. Electronic business cards may be structured according to a data structuring language, such as the Extensible Markup Language, and an associated schema file. Structured and schematized electronic business cards may be consumed by any application functionally capable of consuming data structured according to the data structuring language applied to the electronic business card.
Contact information may be sent over electronic communications media, such as electronic mail, in the form of electronic business cards. According to one embodiment, an electronic business card sent over digital media includes sending an image of the business card as it appears to the user, for example a JPEG, PNG, GIF, TIFF image, with an associated vCard that contains an encapsulated design of the electronic business card with the contact data such as name, phone numbers, addresses and any number of pictures, logos, background color or patterns that the business card may display. Alternatively, an electronic business card sent over digital media includes sending an image of the business card as it appears to the user in JPEG format and the vCard containing contact data such as name, phone numbers, addresses and any pictures, logos, background colors or patterns that the business card may display is embedded into the EXIF metadata of the JPEG image. Alternatively, the electronic business card may be sent as an OLE object with image and associated data.
Electronic business cards may also be shared over electronic communications media such as the Internet or the World Wide Web or through electronic media such as electronic mail systems. The electronic business cards that are exchanged over electronic communications media may be digitally signed for identification of a sender as well as for verifying the integrity of information that is sent from the sender.
Users may publish their business cards on their web sites, or organizations may publish one or more business cards for key contact persons in their web sites. These business cards can then be downloaded and opened by an electronic contacts application and stored locally for future use by the user from a contacts application. According to another embodiment, electronic business cards may be exchanged using shared computer folders, or shared locations identified by Uniform Resource Identifiers to which one or more computers may have access. Electronic business cards may be published to a shared location, such as a shared directory, as vCard files. Electronic contacts applications that have access to the shared directory can then choose to render the business card information in the vCard files when accessing or opening the information from the shared location.
When sending an electronic business card over electronic mail, an electronic mail application may provide the user with one or more business cards that represent the user's own information, such as name and telephone number, as an attachment to an electronic mail message. Alternatively, electronic business cards may be selected from a collection of electronic business cards from the user's electronic contacts repository for attachment to an electronic mail message. According to one embodiment, the first time an electronic business card sender designates contact information for sending to a recipient, an automatically generated electronic business card may be presented to the sender based on information contained about the sender, for example, name, title, address, telephone numbers, and the like maintained for the sender in the sender's electronic contacts repository. Such information about the sender/user may be also be picked by the electronic mail application from a corporate or other institutional directory based on the user's logon credentials into the corporate/institutional computer system. Alternatively, the sender may graphically pick electronic business cards from a collection of business cards for sending in an electronic mail message. In addition, a thumbnail representation of an electronic business card may be added to an electronic signature of an electronic mail message.
When selecting to send electronic business cards, the user may be able to quickly access them according to various lists, for example, a most recently sent business cards list may be presented to the user from the electronic mail form. In addition, electronic business cards may be added to an electronic mail signature in a thumbnail format so that users are able to easily exchange their own contact information in all the emails that they send. Additionally, a smart tag designation may be presented when a user enters information in an electronic mail message that is present in an associated contact file for allowing the user to substitute textual information, such as telephone numbers, with an electronic business card associated with the textual information.
Visual representations of electronic business cards received via electronic mail messages may be viewed in an electronic mail message body. Received electronic business cards may be added to the user's electronic contacts repository from the message body of an electronic mail message or from an attachment. Duplicate electronic business cards may be resolved if the associated contacts information already exists in the recipient's electronic contacts repository. In addition, changes or updates to a contact file associated with a received electronic business card may be previewed before selecting to accept the associated changes.
These and other features and advantages, which characterize the present invention, will be apparent from a reading of the following detailed description and a review of the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are explanatory only and are not restrictive of the invention as claimed.
Embodiments of the present invention are directed to generating electronic business cards and sending and receiving electronic business cards over digital media. According to embodiments of the present invention, electronic business cards are digital visual representations of an electronic contact file that is laid out in a printed business card format, backed by schematized contact data. Electronic business cards may be generated from contact information from one or more default templates followed by user customization, if desired. Electronic business cards may be automatically generated upon rendering of electronic contacts data including sending an automatically generated business card through electronic mail messages. Electronic business cards and associated images may be sent to and received by recipients over various types of digital media.
Recipients of electronic business cards may add received electronic business cards and associated contact information to their own contacts application files. If a received electronic business card provides updated information for an existing contact file, information from the received electronic business card may be used for updating the existing file. If the received electronic business card is a duplicate of an existing electronic business card, a method is presented for either updating the existing contact information or for creating a new copy of the received information.
In the following detailed description, references are made to the accompanying drawings that form a part hereof, and in which are shown by way of illustrations specific embodiments or examples. These embodiments may be combined, other embodiments may be utilized, and structural changes may be made without departing from the spirit or scope of the present invention. The following detailed description is therefore not to be taken in a limiting sense and the scope of the present invention is defined by the appended claims and their equivalents.
Referring now to the drawings, in which like numerals refer to like elements through the several figures, aspects of the present invention and an exemplary computing operating environment will be described.
Generally, program modules include routines, programs, components, data structures, and other types of structures that perform particular tasks or implement particular abstract data types. Moreover, those skilled in the art will appreciate that the invention may be practiced with other computer system configurations, including hand-held devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and the like. The invention may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.
Embodiments of the invention may be implemented as a computer process (method), a computing system, or as an article of manufacture, such as a computer program product or computer readable media. The computer program product may be a computer storage media readable by a computer system and encoding a computer program of instructions for executing a computer process. The computer program product may also be a propagated signal on a carrier readable by a computing system and encoding a computer program of instructions for executing a computer process.
With reference to
In one embodiment, the application 106 may comprise many types of programs, such as a word processing application program, a spreadsheet application, a desktop publishing, and the like. According to an embodiment of the present invention, the application program 106 comprises a multiple-functionality software application for providing a user calendaring functionality, electronic mail functionality, contacts storage and management functionality, electronic notes functionality, electronic journal functionality and the like. Some of the individual program modules comprising such a multiple-functionality program 106 include an electronic mail program, a contacts application 120, a calendaring module, a tasks module, a notes module and a journal module. An example of such a multiple-functionality program 106 is OUTLOOK® manufactured by MICROSOFT CORPORATION.
The computing device 100 may have additional features or functionality. For example, the computing device 100 may also include additional data storage devices (removable and/or non-removable) such as, for example, magnetic disks, optical disks, or tape. Such additional storage is illustrated in
The computing device 100 may also contain communication connections 116 that allow the device to communicate with other computing devices 118, such as over a network in a distributed computing environment, for example, an intranet or the Internet. Communication connection 116 is one example of communication media. Communication media may typically be embodied by computer readable instructions, data structures, program modules, or other data in a modulated data signal, such as a carrier wave or other transport mechanism, and includes any information delivery media. 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. The term computer readable media as used herein includes both storage media and communication media.
Electronic Business Card Creation and Rendering
Referring now to
The user interface illustrated in
According to embodiments of the present invention, and as will be described in detail herein, the view area of the user interface 200 shows a number of electronic business cards that have been previously generated, received or automatically generated by the electronic contacts application and that have been stored by the user in the user's electronic contacts repository. The user can choose different ways of viewing the electronic business cards presented in the user interface 200, as illustrated in
The example electronic business cards 230, 235, illustrated in
Referring now to
As illustrated in
According to embodiments of the present invention, a user may use the electronic business cards auto-generated by the electronic contacts application 120, as described above. Or, individual electronic business cards may be customized using different template styles, discussed above with reference to
According to another embodiment, a company, educational institution, profit or non-profit organization or any other entity may set up default electronic business cards for all employees and associates of the organization or entity. Such default business cards may be formatted according to a standard organization business card format with one or more unique logos or images (e.g., company photographs, artwork, etc.). The default cards may be structured such that individual data, for example, name, title, address, telephone number, etc. is populated for each employee in standard positions. Additionally, other attributes such as unique borders, background colors and font size/style may be applied. Each employee then may automatically generate and send to others an organization/company business card with his/her personal contact information populated into the organization/company business card just as he/she could exchange a paper organization/company business card.
Referring back to
As should be appreciated, the XML data file 340 does not show actual XML data. The XML data file 340 is for purposes of illustration only. Additionally, the XML data file 340 does not show formatting information for the associated electronic business card 320. The following sample XML file shows formatting information that may be applied to an electronic business card 320 for showing the layout and formatting of the electronic business card. It also should be appreciated that the following sample XML file only includes formatting data and does not include actual values of included properties.
Referring still to
The structuring and schematization of each electronic business card, as described above, allows each electronic business card to be consumed and rendered by subsequent consuming applications, for example, electronic mail applications, contacts applications, card reader applications, word processing applications, spreadsheet applications, mail merge and mass mailing applications, instant messaging applications, cell phones, applications on personal digital assistants (PDA), integrated cell phone/personal digital assistants, etc. That is, any application that is capable of consuming the structured data file 340 (e.g., XML capable application) in accordance with the associated schema file 370, may render, display, and otherwise utilize data from the electronic business card. For example, as will be described below, an electronic mail application may render and display an associated electronic business card in the body of an electronic mail message, or a contacts application may extract data, for example, a name and address of a given contact, from an electronic business card based on the structure of the electronic business card for adding the extracted information to a contact file or for updating information contained in an existing contact file.
According to another embodiment, another consumer of electronic business cards includes a printing function or module. According to this embodiment, one or more selected electronic business cards may be printed for generating physical business cards. For example, a selected paper stock may be utilized for generating high quality paper business cards by printing to the paper one or more desired electronic business cards.
Referring still to
Sending and Receiving Electronic Business Cards
According to embodiments of the present invention, electronic business cards may be sent to other users as objects inserted in an electronic mail message. Referring to
According to other embodiments, the user can also take other actions, such as shrinking all the business cards in a view to be able to see more business cards in the view, or increasing the size of the business cards in the view so as to be able to see larger text in the cards for increasing readability. The user may also decide to select a variety of other transformations on the business cards. For example, the user may choose to view only those business cards that have been received by the medium of email, or the user may choose to view only those business cards that have a text only design or only those business cards that have a certain formatting characteristic, such as a particular background color.
According to this embodiment, if the user desires to forward (send) the associated contact information to a destination address as an electronic business card, as illustrated in
Referring now to
Referring now to
In addition, a “send full contact” function 733 is shown in the menu 720. As should be appreciated, a given electronic business card may include only a subset of the contacts data elements contained in a given contact file, which typically matches what is visible in the business card design. Using the “send full contact” function 733, all information in a given contact file may be sent to a recipient. As should be understood, using the “send full contact” function may include sending an electronic business card associated with the selected contact file along with other information contained in the contact file that is not contained in the electronic business card.
Referring now to
Selection of the “other business cards” control may cause the display of a collection of selectable business cards, as illustrated above in
According to other embodiments of the invention, in addition to the primary user electronic business card or “other business cards” category, other business cards may be presented in the pop-up menu 840. For example, a “most recently sent” list of electronic business cards may be created for listing a number of electronic business cards sent within a prescribed period of time. For example, the pop-out menu illustrated in
Referring now to
Referring to
The electronic business card 1010 presented as a preview shows the presently stored electronic business card for the selected contact. If no electronic business card has been generated for the selected contact, an electronic business card is automatically generated, as described above with reference to
According to an embodiment of the invention, electronic business cards may be inserted into an electronic mail message by substituting entered textual contact information with an associated electronic business card. According to this embodiment, the electronic mail application is equipped with a “smart tags” module for detecting textual contact information entered into an electronic mail message and for associating the textual contact information with an electronic business card stored in the sender's electronic contacts repository. According to this embodiment, as textual information is entered into a message entry area of the user interface 810, portions of the entered text, for example, words, sentences, paragraphs, or a prescribed number of entered characters, are sent to a recognizer module. According to this embodiment, the recognizer module is a software module, such as a dynamically-linked library (DLL), having sufficient computer-executable instructions for comparing received text with a list or database of information for matching entries.
When the recognizer module receives a portion of text, the portion of text is broken into individual words, numbers, and number/text combinations (e.g., names, telephone numbers, addresses, etc.). For example, a continuous text string located between two spaces may be recognized as a word. For another example, a five-digit number following a word may be recognized as a zip code. For another example, a 10-digit number string may be recognized as a telephone number. Once the text string passed to the recognizer module is parsed into text units, such as words, numbers, and/or number/word combinations, the text units are compared against the user's electronic contacts repository for matches. If a match is found, for example, a parsed word matches a name in the user's contacts repository, or a parsed number string matches a telephone number in the user's contacts repository, the word or number string being entered into the electronic mail message entry area may be automatically highlighted to the user (e.g., underlining).
If the user selects the highlighted word or number string, a pop-up dialog may be presented to offer the insertion of an electronic business card for the matching contact file. For example, if the user types “the following is the contact information for my friend, John Smith,” the name “John Smith” may be recognized as associated with a contact file for a person named “John Smith.” In accordance with this embodiment, the name “John Smith” will be recognized and highlighted. Upon selection of the highlighted name, the pop-up dialog may offer a selectable action for inserting an electronic business card for “John Smith.” If the user selects the insertion of the electronic business card for John Smith, then the electronic business card will be dynamically inserted into the electronic mail message entry area. Thus, the user does not have to type the contact information manually.
As described above, once an electronic business card is selected, it may be transmitted electronically to a desired recipient. One method of sending electronic business card information over digital media to recipients is via the use of a vCard, which is an Internet standard for sharing virtual business card information over digital media. As understood by those skilled in the art, vCards may be used for transmitting structured data associated with a contact file over digital media, for example, electronic mail. For more information on vCard creation and use, see RFC2425 and RFC2426 promulgated by the Internet Mail Consortium. However, because the vCard standard does not allow for exchanging the auto-generated or custom generated visual presentations of electronic business card designs, as illustrated above in
According to one embodiment of the present invention, electronic business cards are exchanged over digital media by sending a vCard that contains all the information, such as associated data, pictures and formatting information required to render the business cards in the receiving electronic contacts application. A graphical view of the business card is additionally sent as an image, for example, a JPEG image, a PNG image, a GIF image, a TIFF image, and the like. The image allows the receiving user to clearly identify that an electronic business card has been sent and allows a method of quickly receiving the attached vCard from the image itself by using means such as right clicking the received image or by showing a halo 1535 (illustrated in
Referring back to
According to this embodiment, when an electronic business card is sent over digital media, the electronic business card will include a vCard file (.VCF file), which is essentially a text file. The vCard file will also include a display definition of the electronic business card as a vCard schema extension, for example, in the form “X-MS-OL-DESIGN.” According to one embodiment, the display definition is a portion of binary information that contains information about a display of the card. For example, the display definition may contain information about what properties are included in the business card, such as name and telephone number, and what label to use with these properties (such as displaying “home” before the home phone number). The display definition may include information about the order of such properties and what formatting is to be applied to those properties, for example, bold, italics, highlighting, font size and color, etc. Other information may include what picture or image to use, for example, a photograph or logo image with the associated formatting of the image such as alpha blending, transparency, fit to edge and other image transformations. Additional information may include where to place an image in the card, for example, top, bottom, right, left, etc. and what size or area in the card an image should occupy. Other additional information may include attributes such as background color, background pattern, background image, etc. with associated image transformation effects.
The following is an example of vCard data associated with an electronic business card according to this embodiment, where the [image data] portion would include traditional vCard data associated with the business card and where the [display definition or card design data] portion would include the display definition information described above.
According to this embodiment, the image that is sent includes a special tag (e.g., a word processing application bookmark tag) that is wrapped around the image that indicates the vCard attachment name for the electronic business card. According to one embodiment, a destination application will receive data of the following form:
This tag is essentially an HTML “A” tag with a name but no source identifier. When the destination application receives such a tag or bookmark string, it will check to see if a vCard file with the same name as the “A” tag is attached. If the vCard file is attached, then the receiving application may enable functionality for updating or adding the electronic business card to an electronic contacts repository, as described herein. That is, when a user selects the rendered image, a menu or other user interface may be provided to allow data contained in the attached data file to be used for updating contact files, as described herein. If the card data file is not included as an attachment, then the receiving or destination application need not enable such functionality, and any image associated with the received data may be rendered as any received image would be rendered by the receiving application.
According to another embodiment, an electronic business card may be exchanged over digital media in JPEG format, and associated vCard information for the selected electronic business card may be embedded into the EXIF metadata of the JPEG image. As known to those skilled in the art, the Exchangeable Image File Format (EXIF) is a file format for allowing metadata information to be inserted into the headers or application segments of a JPEG file. Embedding vCard information within the JPEG image of the electronic business card allows for associated contact information to be persisted in the image when the image is exchanged through different digital media. According to this embodiment, when a receiving or consuming application receives the card, the receiving application may display the card according to the JPEG image, and the vCard information may be extracted from the EXIF metadata for use by the receiving application for generating an associated contact file or for updating a contact file on the receiving end. This embodiment can also apply to image types other than JPEG that allow including vCard information in the metadata of the image.
According to another embodiment, an electronic business card may be exchanged over digital media as an OLE object. According to this embodiment, card data and an associated image may be packaged together as an OLE object and may be sent to a receiving party for rendering and disposition by a receiving application, for example, an email or contacts application. According to this embodiment, card data such as name, address, telephone number, URL, formatting data, order of fields in the card, locations of images in the card, etc. may be brought together, for example, in an aforementioned vCard (.VCF) file. The card data and an associated image, for example, a JPEG or PNG image, are then packaged together in an OLE object. When the OLE object is received at a receiving application, the OLE object instructs the receiving application as to how to use the data and image. For example, the image may be displayed by the receiving application and the data may cause the receiving application to enable a function described herein for updating contact files or other use of the data. Thus, a receiving electronic contacts application 120 or electronic mail application may render the received electronic business card according to the desired format contained within the OLE object, and data, such as name, address, telephone number, URL, and the like, may be utilized by the receiving system according to the associated vCard data.
Referring to
If sending the selected electronic business card according to a selected alternate format causes a degradation of the electronic business card in any manner, a dialog may be displayed for alerting the sending party that the formatted information in the electronic business card will be reformatted according to the selected formatting property and that some objects in the electronic business card, for example, pictures or images may be lost. As should be appreciated, the sender may desire to send an electronic business card to a recipient who is using a device that is better suited for receiving the information according to an alternate format. For example, if the recipient utilizes a personal digital assistant or other handheld computing device that is not capable of rendering and displaying the electronic business card according to all of its associated formatting properties, the sender may desire to send the information from the electronic business card in some format such as plain text or HTML for the benefit of the recipient.
Referring now to
As illustrated in
Updating Contacts Information From Received Electronic Business Cards
Referring now to
As illustrated in
Because the electronic business card is based on schematized structured data, the electronic contacts application 120 of the recipient may place the electronic business card in an electronic contacts repository. Because each data item in the received electronic business card is structured, the receiving electronic contacts application may parse the received electronic business card and may extract each data item for placement into an appropriate contact file. For example, names, address, telephone numbers, title, and the like associated with a received electronic business card may be extracted from the card and populated into the fields of an electronic contact file. Additionally, if the business card contains an image, such as a logo, photograph, or other art, data structuring associated with the image may be utilized by the receiving application for storing the image in the electronic contact file. Moreover, any formatting properties applied to the received electronic business card, for example, positioning of various data items in the business card, text styles, fonts, text sizes, etc., may be stored in the fields of the electronic contact files so that the receiving electronic contacts application may subsequently render and display the stored electronic business card according to the formatting properties and structure applied to the electronic business card by the sender of the electronic business card.
Referring now to
As illustrated in
As illustrated in
Referring back to
According to one embodiment, if no previous contact file exists for the contact information contained in the electronic business card, the user interface 1600 may be automatically populated from information extracted from the electronic business card, as described above. Alternatively, if a contact file already exists for the associated contact information, then the information displayed in the user interface 1600 may be shown in its updated form after the electronic contacts application 120 has utilized information from the received electronic business card to update fields in the user interface 1600, for example, full name, job title, company, etc. If the user is satisfied with the information populated into the user interface 1600 by the contacts application, the user may save the information to the contact file for subsequent use.
According to another embodiment of the invention, the received electronic business card may be edited by the receiving user. If edits to the received electronic business card are desired, an edit control, such as the example “Edit Card” control 1620, may be selected for launching a card editing user interface 1800, illustrated in
As described above, electronic business cards may be consumed and used by a variety of consuming applications, for example, receiving contacts applications, receiving electronic mail applications, receiving electronic signature modules, and the like. An additional consumer of electronic business cards includes a mail merge function of a word processing application or other application operative to merge contact data automatically with fields of a document. As known to those skilled in the art, a mail merge function allows integration of contacts information with other documents. For example, a letter document may be linked with a contact file in the user's contacts repository so that when the document is rendered, data from the associated contact file may be retrieved for automatically populating fields in the letter, such as name, address, telephone number, etc.
According to embodiments of the present invention, an electronic business card may be sent to a selected document via a mail merge function. That is, using a mail merge function, a portion of a document for which contacts information for a given contact is required may be pointed to an electronic business card for the contact. The receiving document may extract required information from the electronic business card such as name, title and address for populating the associated portion of the document. As should be appreciated, a single document may be pointed to a number of electronic business cards so that the mail merge function may be used for generating a document for each of the number of electronic business cards.
As described herein, graphical visual representations of electronic business cards may be generated and sent and received over digital media. Contacts information associated with received electronic business cards may be used for adding to or updating information contained in a recipient's electronic contact files repository. It will be apparent to those skilled in the art that various modifications or variations may be made in the present invention without departing from the scope or spirit of the invention. Other embodiments of the present invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein.
Number | Name | Date | Kind |
---|---|---|---|
5493105 | Desai | Feb 1996 | A |
5732229 | Dickinson | Mar 1998 | A |
5764629 | Bower et al. | Jun 1998 | A |
5774117 | Kukkal et al. | Jun 1998 | A |
5845261 | McAbian | Dec 1998 | A |
5852807 | Skarbo et al. | Dec 1998 | A |
6137710 | Iwasaki et al. | Oct 2000 | A |
6157954 | Moon et al. | Dec 2000 | A |
6175741 | Alperovich | Jan 2001 | B1 |
6195686 | Moon et al. | Feb 2001 | B1 |
6254001 | Chan | Jul 2001 | B1 |
6397219 | Mills | May 2002 | B2 |
6442263 | Beaton et al. | Aug 2002 | B1 |
6533171 | Porter | Mar 2003 | B1 |
6760728 | Osborn | Jul 2004 | B1 |
6816725 | Lemke et al. | Nov 2004 | B1 |
6857072 | Schuster et al. | Feb 2005 | B1 |
6868426 | Mankoff | Mar 2005 | B1 |
6873861 | Awada et al. | Mar 2005 | B2 |
6883000 | Gropper | Apr 2005 | B1 |
6888927 | Cruickshank et al. | May 2005 | B1 |
6889213 | Douvikas et al. | May 2005 | B1 |
6954934 | Kumar | Oct 2005 | B2 |
6983371 | Hurtado et al. | Jan 2006 | B1 |
7003546 | Cheah | Feb 2006 | B1 |
7007068 | Morkel | Feb 2006 | B2 |
7017109 | Douvikas et al. | Mar 2006 | B1 |
7039869 | Smith | May 2006 | B2 |
7043531 | Seibel et al. | May 2006 | B1 |
7047041 | Vanska et al. | May 2006 | B2 |
7062656 | Richards et al. | Jun 2006 | B2 |
7109985 | Spencer et al. | Sep 2006 | B2 |
7228335 | Caughey | Jun 2007 | B2 |
7246099 | Feldhahn | Jul 2007 | B2 |
7255267 | Chao | Aug 2007 | B2 |
7280975 | Donner | Oct 2007 | B1 |
7289110 | Hansson | Oct 2007 | B2 |
7322007 | Schowtka et al. | Jan 2008 | B2 |
7337127 | Smith et al. | Feb 2008 | B1 |
7387234 | Kanatani et al. | Jun 2008 | B2 |
7451099 | Henkin et al. | Nov 2008 | B2 |
7483179 | Stumbo et al. | Jan 2009 | B2 |
7607084 | Malone et al. | Oct 2009 | B2 |
7753260 | Kanatani et al. | Jul 2010 | B2 |
7814438 | Grossman et al. | Oct 2010 | B2 |
20010021935 | Mills | Sep 2001 | A1 |
20010027472 | Guan | Oct 2001 | A1 |
20010032251 | Rhoads et al. | Oct 2001 | A1 |
20020013815 | Obradovich et al. | Jan 2002 | A1 |
20020035566 | Rugg | Mar 2002 | A1 |
20020055955 | Lloyd-Jones et al. | May 2002 | A1 |
20020095384 | Pestoni et al. | Jul 2002 | A1 |
20020107938 | Moroney et al. | Aug 2002 | A1 |
20020116396 | Somers et al. | Aug 2002 | A1 |
20020130185 | LaForge et al. | Sep 2002 | A1 |
20020133482 | Wen Hung | Sep 2002 | A1 |
20020138633 | Angwin et al. | Sep 2002 | A1 |
20020152086 | Smith et al. | Oct 2002 | A1 |
20020188606 | Sun et al. | Dec 2002 | A1 |
20030020959 | Henry | Jan 2003 | A1 |
20030050920 | Sun | Mar 2003 | A1 |
20030066877 | Howard et al. | Apr 2003 | A1 |
20030110130 | Pelletier | Jun 2003 | A1 |
20030131001 | Matsuo | Jul 2003 | A1 |
20030158860 | Caughey | Aug 2003 | A1 |
20030158893 | Komatsu et al. | Aug 2003 | A1 |
20030163705 | Richards, Jr. et al. | Aug 2003 | A1 |
20030203744 | Otsuka | Oct 2003 | A1 |
20040019521 | Birmingham | Jan 2004 | A1 |
20040076345 | Olszak et al. | Apr 2004 | A1 |
20040153328 | Macholda | Aug 2004 | A1 |
20040181517 | Jung et al. | Sep 2004 | A1 |
20040181540 | Jung et al. | Sep 2004 | A1 |
20040207878 | Ferlitsch | Oct 2004 | A1 |
20040243496 | Kim et al. | Dec 2004 | A1 |
20040243930 | Schowtka et al. | Dec 2004 | A1 |
20050010490 | Liu | Jan 2005 | A1 |
20050091074 | Feidhahn | Apr 2005 | A1 |
20050103838 | Slotkin et al. | May 2005 | A1 |
20050113025 | Akamatsu et al. | May 2005 | A1 |
20050122543 | Walker | Jun 2005 | A1 |
20050165621 | Lapstun et al. | Jul 2005 | A1 |
20050182644 | Douvikas et al. | Aug 2005 | A1 |
20050233697 | Yu | Oct 2005 | A1 |
20050239439 | Manabe | Oct 2005 | A1 |
20050251448 | Gropper | Nov 2005 | A1 |
20050289474 | Master et al. | Dec 2005 | A1 |
20060038447 | Bruelle-Drews | Feb 2006 | A1 |
20060065707 | Kanatani et al. | Mar 2006 | A1 |
20060065708 | Kanatani et al. | Mar 2006 | A1 |
20060075050 | Kanatani et al. | Apr 2006 | A1 |
20060075231 | Yu et al. | Apr 2006 | A1 |
20060088214 | Handley et al. | Apr 2006 | A1 |
20060184574 | Wu et al. | Aug 2006 | A1 |
20060229988 | Oshima et al. | Oct 2006 | A1 |
20060270388 | Veeramachaneni et al. | Nov 2006 | A1 |
20060293904 | Ramanathan et al. | Dec 2006 | A1 |
20060293905 | Ramanathan et al. | Dec 2006 | A1 |
20070156831 | Quine | Jul 2007 | A1 |
20090116687 | Rhoads et al. | May 2009 | A1 |
20090216839 | Yokoyama | Aug 2009 | A1 |
20090217199 | Hara et al. | Aug 2009 | A1 |
Number | Date | Country |
---|---|---|
02-044467 | Feb 1990 | JP |
07-064923 | Oct 1995 | JP |
08-008962 | Jan 1996 | JP |
08-147289 | Jun 1996 | JP |
10-190645 | Jul 1998 | JP |
9929127 | Oct 1999 | JP |
2001-243221 | Sep 2001 | JP |
2001-249863 | Sep 2001 | JP |
2001-282793 | Oct 2001 | JP |
2002-297855 | Oct 2002 | JP |
2002-334046 | Nov 2002 | JP |
2003-006161 | Jan 2003 | JP |
2003-30211 | Jan 2003 | JP |
2003-123035 | Apr 2003 | JP |
2003-309552 | Oct 2003 | JP |
2003-348077 | Dec 2003 | JP |
2004-164166 | Jun 2004 | JP |
2004-192138 | Jul 2004 | JP |
2004-362264 | Dec 2004 | JP |
2005-018746 | Jan 2005 | JP |
4416644 | Dec 2009 | JP |
WO 2007001638 | Jan 2007 | WO |
WO 2007005606 | Jan 2007 | WO |
WO 20070016434 | Jan 2007 | WO |
WO 2007005606 | Jun 2007 | WO |
WO 20070016434 | Oct 2007 | WO |
WO 2007001638 | Nov 2007 | WO |
Number | Date | Country | |
---|---|---|---|
20060293903 A1 | Dec 2006 | US |