The present invention relates generally to the field of network-based communications and, more specifically, to a system and method to facilitate translation of communications between entities over a network, such as the Internet.
The explosive growth of the Internet as a publication and interactive communication platform has created an electronic environment that is changing the way business is transacted. As the Internet becomes increasingly accessible around the world, communications between users that utilize different spoken or written languages increase exponentially.
Several attempts have been made to facilitate such communications and to provide translation software packages residing on a computer and configured to translate text or voice communications from one language to another. Some of these translation software packages, however, can be expensive and can result in a financial burden for a user of such software packages. Furthermore, such software packages require considerable storage capacity to be available on the computer.
Another drawback of the translation software packages relates to their limited applicability. For example, current technology allows for translation of text through common text translation software installed on a computer. The translation may be accomplished in a variety of ways, one of which is direct word for word translation of the communication, which is imperfect and produces grammatically incorrect sentences in the translated language. Current technology also allows for limited translation of voice communications through speech recognition software installed on the computer. However, spoken language translation is mostly available in restricted domains, where the database of recognizable words is limited to a specific set of words.
A system and method to facilitate translation of communications between entities over a network are described. Multiple predetermined language constructs are communicated to a first entity as a first transmission over the network. Responsive to selection by the first entity of a language construct from the predetermined language constructs, a translated language construct corresponding to the selected language construct is identified. Finally, the translated language construct is communicated to a second entity as a second transmission over the network.
Other features and advantages of the present invention will be apparent from the accompanying drawings, and from the detailed description, which follows below.
The present invention is illustrated by way of example and not intended to be limited by the figures of the accompanying drawings in which like references indicate similar elements and in which:
A system and method to facilitate translation of communication between entities over a network are described. In the following detailed description of embodiments of the invention, reference is made to the accompanying drawings in which like references indicate similar elements, and in which are shown by way of illustration specific embodiments in which the invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other embodiments may be utilized and that logical, mechanical, electrical, functional, and other changes may be made without departing from the 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 only by the appended claims.
The auction facility 10 includes one or more of a number of types of front-end servers, namely communications servers in the exemplary form of page servers 12 that deliver web pages to multiple entities (e.g., markup language documents), picture servers 14 that dynamically deliver images to be displayed within the web pages, listing servers 16, processing servers in the exemplary form of Common Gateway Interface (CGI) or Internet Server Application Program Interface (ISAPI) servers 18 that provide an intelligent interface to the back-end of the auction facility 10, and search servers 20 that handle search requests to the auction facility 10. In addition, the auction facility 10 includes e-mail servers 21 that provide, inter alia, automated e-mail communications to/from entities of the facility 10.
The auction facility 10 further includes one or more back-end servers, for example a database engine server 22, a search indexer server 24 and a credit card database server 26, each of which maintains and facilitates access to a respective database 23. The network-based auction facility 10, such as an Internet-based auction facility 10, may be accessed by a client program 30, such as a browser (e.g., the Internet Explorer browser distributed by Microsoft Corporation of Redmond, Wash.) that executes on a client machine 32 and accesses the facility 10 via a network 34, such as, for example, the Internet. Other examples of networks that a client may utilize to access the auction facility 10 includes a wide area network (WAN), a local area network (LAN), a wireless network (e.g., a cellular network), or the Plain Old Telephone Service (POTS) network.
Central to the database 23 shown in
The database 23 further includes a note table 48 populated with note records that may be linked to one or more item records within the items table 42 and/or to one or more user records within the user table 40. Each note record within the note table 48 may include, inter alia, a comment, description, history, or other information pertaining to an item being auctioned via the auction facility 10, or pertaining to a user of the auction facility 10.
A number of other tables are also shown to be linked to the user table 40, such as a user past aliases table 50, a feedback table 52, a bids table 54, an accounts table 56, and an account balances table 58.
The database 23 is also shown to include two tables specifically to enable an exemplary embodiment of the present invention. A stored construct table 60 stores a predetermined number of language constructs, such as sentences, phrases, questions, or any other known types of language constructs. A stored translated construct table 70 contains a number of records, each record storing translated language constructs corresponding to the language constructs stored in table 60. Prior to any communication between client 32 and the network-based auction facility 10, each translated language construct is generated and stored in the stored translated construct table 70, and the correspondence to one or more predetermined language constructs in the stored language constructs table 60 is defined, such that each translated language construct includes a predetermined translation of the corresponding predetermined language construct.
As illustrated in
At block 110, the language construct is communicated from the first user 92 to the website 96 via the network 34 in a message directed to the second user 94, for example an electronic mail (e-mail) message.
At block 115, the website 96 (e.g., the auction facility 10) utilizes the search servers 20 to conduct a search of the user table 40, the stored constructs table 60, and the stored translated constructs table 70 to retrieve a translated language construct, based on the user identifier corresponding to the second user 94. The search of the user table 40 locates the user information pertaining to the second user 94, including a language preference of the second user 94, and the search of the tables 60 and 70 locates the translated language construct corresponding to the selected language construct and the language preference of the second user 94. In one embodiment, the predetermined language constructs and the translated language constructs are generated and stored in respective tables 60 and 70 prior to the language constructs being communicated to the first user 92, so as to define a correspondence between each predetermined language construct and at least one associated translated language construct. Alternatively, the storing is so as to define a correspondence between a set of the translated language constructs, wherein each translated language construct of the set includes a predetermined translation of a common underlying language construct.
At block 120, the website 96 generates a translated message to be transmitted to the second user 94. In one embodiment, the translated message is an e-mail message generated by the e-mail servers 21 and directed to the second user 94, which contains the translated language construct. Alternatively, the translated e-mail message may contain multiple interactive fields to allow the second user 94 to respond to the first user 92.
At block 125, the translated message is communicated to the second user 94. In one embodiment, an e-mail message containing the translated language construct is communicated by the e-mail servers 21 to the second user 94.
At block 130, the second user 94 selects a further language construct and a user identifier of the first user 92 to which the further language construct is to be communicated. The further language construct may be selected, in one embodiment, from the drop-down list containing multiple predetermined language constructs translated in the language preference of the second user 94, the drop-down list being displayed in one interactive field of the multiple fields communicated to the second user 94 from the website 96. For example, the
At block 135, the further language construct is communicated from the second user 94 to the website 96 via the network 34 in a reply message directed to the first user 92, for example an electronic mail (e-mail) message.
Returning to
At block 145, the website 96 generates a translated reply message to be transmitted to the first user 92. In one embodiment, the translated reply message is an e-mail message generated by the e-mail servers 21 and directed to the first user 92, which contains the translated further language construct.
At block 150, the translated reply message is communicated to the first user 92. In one embodiment, an e-mail message containing the translated further language construct is communicated by the e-mail servers 21 to the first user 92.
It should be noted that the sequence 90 may have any one of a number of applications and may be implemented within any number of environments. For example, the sequence 90 may be used to communicate information from any one entity, such as first or second users 92 and 94, to the website 96 in a language preferred by the respective entity. The website 96 may subsequently translate the information and use it in any one of a number of applications, such as in the preparation of item listings, or in the updating of the user information.
Referring to
The message is shown to be communicated to the e-mail servers 21 of the website 96. Specifically, the message containing the language construct may be communicated, in one embodiment, as an e-mail message or by utilizing any other transfer protocol or communication. The e-mail servers 21 receive the message using the transmission functions 217 and proceed to parse the message to extract the language construct and the user identifier for the second user that operates the second client machine 32.
The search servers 20 within the website 96 receive the language construct and the user identifier and search tables within corresponding databases using search functions 205 to provide a translated language construct to be communicated to the second user. Specifically, in one embodiment, the search servers 20 search the user table 40 shown in
The translated language construct is subsequently communicated to the e-mail servers 21. The e-mail servers 21 generate a translated e-mail message containing the translated language construct using message generation functions 215. The translated e-mail message is then communicated to the second client machine via the transmission functions 217.
In one embodiment, the second user selects a further language construct and a user identifier of the first user in an e-mail client or browser 326 that executes in the second client machine 32, the first user being the recipient of a reply e-mail message 328 containing the further language construct to be communicated by the second user. The language construct may be selected, in one embodiment, from a drop-down list containing multiple predetermined language constructs translated in the language preference of the second user, the drop-down list being displayed in one interactive field of multiple interactive fields that may be communicated to the second user from the website 96. Alternatively, the second user may only receive the translated e-mail message and take no further action.
The reply message is shown to be communicated to the e-mail servers 21 of the website 96. Specifically, the reply message containing the further language construct may be communicated, in one embodiment, as an e-mail message or by utilizing any other transfer protocol or communication. The e-mail servers 21 receive the reply message using the transmission functions 217 and proceed to parse the reply message to extract the further language construct and the user identifier for the first user that operates the first client machine 32.
The search servers 20 within the website 96 receive the further language construct and the user identifier and search tables within corresponding databases using search functions 205 to provide a translated further language construct to be communicated to the first user. Specifically, in one embodiment, the search servers 20 search the user table 40 shown in
The translated further language construct is subsequently communicated to the e-mail servers 21. The e-mail servers 21 generate a translated reply message containing the translated further language construct using message generation functions 215. The translated reply message is then communicated to the first client machine via the transmission functions 217.
An alternative application would allow each user of the first or second client machines 32 to communicate selected language constructs to the website 96. In this case, the website 96 may perform search and translation operations and use the translated language construct to update listings via listing servers 16, or to update user information in the user table 40.
As illustrated in
At processing block 620, the user table 40 is searched to locate user information pertaining to the second user, including a language preference of the second user. At processing block 625, the stored constructs table 60 and the stored translated constructs table 70 are searched to retrieve a translated language construct corresponding to the selected language construct.
At processing block 630, a translated message containing the translated language construct and multiple interactive fields is generated. At processing block 635, the translated message is communicated to the second user.
At processing block 640, a further language construct and a user identifier of the first user are received from the second user. At processing block 645, the user table 40 is searched to locate user information pertaining to the first user, including a language preference of the first user. At processing block 650, the stored constructs table 60 and the stored translated constructs table 70 are searched to retrieve a translated further language construct corresponding to the selected further language construct.
At processing block 655, a translated reply message containing the translated further language construct is generated. Finally, at processing block 660, the translated reply message is communicated to the first user.
The computer system 300 includes a processor 302, a main memory 304 and a static memory 306, which communicate with each other via a bus 308. The computer system 300 may further include a video display unit 310 (e.g., a liquid crystal display (LCD) or a cathode ray tube (CRT)). The computer system 300 also includes an alphanumeric input device 312 (e.g., a keyboard), a cursor control device 314 (e.g., a mouse), a disk drive unit 316, a signal generation device 18 (e.g., a speaker), and a network interface device 320.
The disk drive unit 316 includes a machine-readable medium 324 on which is stored a set of instructions (i.e., software) 326 embodying any one, or all, of the methodologies described above. The software 326 is also shown to reside, completely or at least partially, within the main memory 304 and/or within the processor 302. The software 326 may further be transmitted or received via the network interface device 320.
It is to be understood that embodiments of this invention may be used as or to support software programs executed upon some form of processing core (such as the CPU of a computer) or otherwise implemented or realized upon or within a machine or computer readable medium. A machine readable medium includes any mechanism for storing or transmitting information in a form readable by a machine (e.g., a computer). For example, a machine readable medium includes read-only memory (ROM); random access memory (RAM); magnetic disk storage media; optical storage media; flash memory devices; electrical, optical, acoustical or other form of propagated signals (e.g., carrier waves, infrared signals, digital signals, etc.); or any other type of media suitable for storing or transmitting information.
In the foregoing specification, the invention has been described with reference to specific exemplary embodiments thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of the invention as set forth in the appended claims. The specification and drawings are, accordingly, to be regarded in an illustrative sense rather than a restrictive sense.
Number | Name | Date | Kind |
---|---|---|---|
3573747 | Adams et al. | Apr 1971 | A |
3581072 | Nymayer | May 1971 | A |
4412287 | Braddock, III | Oct 1983 | A |
4674044 | Kalmus et al. | Jun 1987 | A |
4677552 | Sibley, Jr. | Jun 1987 | A |
4789928 | Fujisaki | Dec 1988 | A |
4799156 | Shavit et al. | Jan 1989 | A |
4823265 | Nelson | Apr 1989 | A |
4864516 | Gathier et al. | Sep 1989 | A |
4903201 | Wagner | Feb 1990 | A |
5063507 | Lindsey et al. | Nov 1991 | A |
5063523 | Vrenjak | Nov 1991 | A |
5077665 | Silverman et al. | Dec 1991 | A |
5101353 | Lupien et al. | Mar 1992 | A |
5136501 | Silverman et al. | Aug 1992 | A |
5168446 | Wiseman | Dec 1992 | A |
5205200 | Wright | Apr 1993 | A |
5243515 | Lee | Sep 1993 | A |
5258908 | Hartheimer et al. | Nov 1993 | A |
5280422 | Moe et al. | Jan 1994 | A |
5297031 | Gutterman et al. | Mar 1994 | A |
5297032 | Trojan et al. | Mar 1994 | A |
5305200 | Hartheimer et al. | Apr 1994 | A |
5325297 | Bird et al. | Jun 1994 | A |
5329589 | Fraser et al. | Jul 1994 | A |
5375055 | Togher et al. | Dec 1994 | A |
5394324 | Clearwater | Feb 1995 | A |
5418949 | Suzuki | May 1995 | A |
5426281 | Abecassis | Jun 1995 | A |
5442782 | Malatesta et al. | Aug 1995 | A |
5485510 | Colbert | Jan 1996 | A |
5497319 | Chong et al. | Mar 1996 | A |
5535403 | Li et al. | Jul 1996 | A |
5544051 | Senn et al. | Aug 1996 | A |
5553145 | Micali | Sep 1996 | A |
5557728 | Garrett et al. | Sep 1996 | A |
5596994 | Bro | Jan 1997 | A |
5598557 | Doner et al. | Jan 1997 | A |
5600833 | Senn et al. | Feb 1997 | A |
5640569 | Miller et al. | Jun 1997 | A |
5652896 | Yamauchi et al. | Jul 1997 | A |
5657389 | Houvener | Aug 1997 | A |
5664115 | Fraser | Sep 1997 | A |
5689652 | Lupien et al. | Nov 1997 | A |
5694546 | Reisman | Dec 1997 | A |
5706457 | Dwyer et al. | Jan 1998 | A |
5710889 | Clark et al. | Jan 1998 | A |
5715314 | Payne et al. | Feb 1998 | A |
5715402 | Popolo | Feb 1998 | A |
5717989 | Tozzoli et al. | Feb 1998 | A |
5722418 | Bro | Mar 1998 | A |
5724524 | Hunt et al. | Mar 1998 | A |
5724593 | Hargrave, III et al. | Mar 1998 | A |
5727165 | Ordish et al. | Mar 1998 | A |
5758126 | Daniels et al. | May 1998 | A |
5771291 | Newton et al. | Jun 1998 | A |
5771380 | Tanaka et al. | Jun 1998 | A |
5778213 | Shakib et al. | Jul 1998 | A |
5790790 | Smith et al. | Aug 1998 | A |
5794219 | Brown | Aug 1998 | A |
5799285 | Klingman | Aug 1998 | A |
5803500 | Mossberg | Sep 1998 | A |
5818914 | Fujisaki | Oct 1998 | A |
5826244 | Huberman | Oct 1998 | A |
5835896 | Fisher et al. | Nov 1998 | A |
5835911 | Nakagawa et al. | Nov 1998 | A |
5845265 | Woolston | Dec 1998 | A |
5845266 | Lupien et al. | Dec 1998 | A |
5846265 | McGregor et al. | Dec 1998 | A |
5850442 | Muftic | Dec 1998 | A |
5854997 | Sukeda et al. | Dec 1998 | A |
5857188 | Douglas | Jan 1999 | A |
5857201 | Write, Jr. et al. | Jan 1999 | A |
5857203 | Kauffman et al. | Jan 1999 | A |
5872848 | Romney et al. | Feb 1999 | A |
5873069 | Reuhl et al. | Feb 1999 | A |
5884056 | Steele | Mar 1999 | A |
5884247 | Christy | Mar 1999 | A |
5890138 | Godin et al. | Mar 1999 | A |
5905974 | Fraser et al. | May 1999 | A |
5905975 | Aussubel | May 1999 | A |
5909544 | Anderson et al. | Jun 1999 | A |
5922074 | Richard et al. | Jul 1999 | A |
5924072 | Havens | Jul 1999 | A |
5926794 | Fethe | Jul 1999 | A |
5944790 | Levy | Aug 1999 | A |
5874412 | Hazelhurst et al. | Oct 1999 | A |
5966685 | Flanagan et al. | Oct 1999 | A |
5991739 | Cupps et al. | Nov 1999 | A |
6006221 | Liddy et al. | Dec 1999 | A |
6018742 | Herbert, III | Jan 2000 | A |
6035288 | Solomon | Mar 2000 | A |
6035402 | Vaeth et al. | Mar 2000 | A |
6044363 | Mori et al. | Mar 2000 | A |
6047264 | Fisher et al. | Apr 2000 | A |
6055518 | Franklin et al. | Apr 2000 | A |
6058379 | Odom et al. | May 2000 | A |
6058417 | Hess et al. | May 2000 | A |
6061448 | Smith et al. | May 2000 | A |
6073117 | Oyanagi et al. | Jun 2000 | A |
6085169 | Walker et al. | Jul 2000 | A |
6085176 | Woolston | Jul 2000 | A |
6092035 | Kurachi et al. | Jul 2000 | A |
6104815 | Alcorn et al. | Aug 2000 | A |
6119137 | Smith et al. | Sep 2000 | A |
6119229 | Martinez et al. | Sep 2000 | A |
6134533 | Shell | Oct 2000 | A |
6141653 | Conklin et al. | Oct 2000 | A |
6144984 | DeBenedictis et al. | Nov 2000 | A |
6151589 | Aggarwal et al. | Nov 2000 | A |
6161082 | Goldberg et al. | Dec 2000 | A |
6178408 | Copple et al. | Jan 2001 | B1 |
6192407 | Smith et al. | Feb 2001 | B1 |
6202051 | Woolston | Mar 2001 | B1 |
6205418 | Li et al. | Mar 2001 | B1 |
6226412 | Schwab | May 2001 | B1 |
6243691 | Fisher et al. | Jun 2001 | B1 |
6266651 | Woolston | Jul 2001 | B1 |
6266652 | Godin et al. | Jul 2001 | B1 |
6275789 | Moser et al. | Aug 2001 | B1 |
6282507 | Horiguchi et al. | Aug 2001 | B1 |
6292769 | Flanagan et al. | Sep 2001 | B1 |
6301554 | Christy | Oct 2001 | B1 |
6317727 | May | Nov 2001 | B1 |
6326985 | Tazoe et al. | Dec 2001 | B1 |
6336105 | Conklin et al. | Jan 2002 | B1 |
6339755 | Hetherington et al. | Jan 2002 | B1 |
6349275 | Schumacher et al. | Feb 2002 | B1 |
6363337 | Amith | Mar 2002 | B1 |
6389427 | Faulkner | May 2002 | B1 |
6396515 | Hetherington et al. | May 2002 | B1 |
6415270 | Rackson et al. | Jul 2002 | B1 |
6421653 | May | Jul 2002 | B1 |
6446048 | Wells et al. | Sep 2002 | B1 |
6460015 | Hetherington et al. | Oct 2002 | B1 |
6463404 | Appleby | Oct 2002 | B1 |
6473729 | Gastaldo et al. | Oct 2002 | B1 |
6493661 | White et al. | Dec 2002 | B1 |
6507813 | Veditz et al. | Jan 2003 | B2 |
6526426 | Lakritz | Feb 2003 | B1 |
6567821 | Polk | May 2003 | B1 |
6570591 | Crovetto et al. | May 2003 | B1 |
6571241 | Nosohara | May 2003 | B1 |
6574239 | Dowling et al. | Jun 2003 | B1 |
6598026 | Ojha et al. | Jul 2003 | B1 |
6623529 | Lakritz | Sep 2003 | B1 |
6647373 | Carlton-Foss | Nov 2003 | B1 |
6721715 | Nemzow | Apr 2004 | B2 |
6732161 | Hess et al. | May 2004 | B1 |
6771291 | DiStefano | Aug 2004 | B1 |
6799165 | Boesjes | Sep 2004 | B1 |
6857022 | Scanlan | Feb 2005 | B1 |
6901408 | Fachat et al. | May 2005 | B2 |
6999932 | Zhou | Feb 2006 | B1 |
7007026 | Wilkinson et al. | Feb 2006 | B2 |
7013289 | Horn et al. | Mar 2006 | B2 |
7076453 | Jammes et al. | Jul 2006 | B2 |
7133835 | Fusz et al. | Nov 2006 | B1 |
7136863 | Wang | Nov 2006 | B2 |
7165041 | Guheen et al. | Jan 2007 | B1 |
7191393 | Chin et al. | Mar 2007 | B1 |
7234110 | Sumitomo | Jun 2007 | B2 |
7315826 | Guheen et al. | Jan 2008 | B1 |
7340389 | Vargas | Mar 2008 | B2 |
7418390 | Jokipii | Aug 2008 | B1 |
20010011241 | Nemzow | Aug 2001 | A1 |
20010029455 | Chin et al. | Oct 2001 | A1 |
20010039531 | Aoki | Nov 2001 | A1 |
20020029182 | Nakagawa | Mar 2002 | A1 |
20020042835 | Pepin et al. | Apr 2002 | A1 |
20020046137 | Odom et al. | Apr 2002 | A1 |
20020073111 | Heyliger | Jun 2002 | A1 |
20020082953 | Batham et al. | Jun 2002 | A1 |
20020082977 | Hammond et al. | Jun 2002 | A1 |
20020099562 | Bruce et al. | Jul 2002 | A1 |
20020123959 | Mozley et al. | Sep 2002 | A1 |
20030005159 | Kumhyr | Jan 2003 | A1 |
20030018885 | Landsman et al. | Jan 2003 | A1 |
20030055747 | Carr et al. | Mar 2003 | A1 |
20030083952 | Simpson et al. | May 2003 | A1 |
20030110047 | Santosuosso et al. | Jun 2003 | A1 |
20030139975 | Perkowski | Jul 2003 | A1 |
20030154134 | Wang | Aug 2003 | A1 |
20030167213 | Jammes et al. | Sep 2003 | A1 |
20050102151 | Fuwa et al. | May 2005 | A1 |
20050240392 | Munro et al. | Oct 2005 | A1 |
20060200353 | Bennett | Sep 2006 | A1 |
20070112643 | Veres et al. | May 2007 | A1 |
Number | Date | Country |
---|---|---|
2253543 | Mar 1997 | CA |
1139782 | Jan 1997 | CN |
2658635 | Feb 1991 | FR |
02207898 | Jul 2002 | JP |
04-094643 | Mar 2004 | JP |
9300266 | Feb 1993 | NL |
WO 9215174 | Feb 1992 | WO |
WO9517711 | Jun 1995 | WO |
WO 9634356 | Apr 1996 | WO |
WO 9737315 | Mar 1997 | WO |
WO9963461 | Dec 1999 | WO |
WO-0058862 | Oct 2000 | WO |
WO-0157722 | Aug 2001 | WO |
WO-0182115 | Nov 2001 | WO |
WO-03038560 | May 2003 | WO |
WO-03038560 | May 2003 | WO |
Number | Date | Country | |
---|---|---|---|
20030074462 A1 | Apr 2003 | US |