Classifications

• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
  • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/30—Managing network names, e.g. use of aliases or nicknames
  • H04L61/301—Name conversion
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/951—Indexing; Web crawling techniques
• • G—PHYSICS
  • G06—COMPUTING; CALCULATING OR COUNTING
  • G06F—ELECTRIC DIGITAL DATA PROCESSING
  • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
  • G06F16/90—Details of database functions independent of the retrieved data types
  • G06F16/95—Retrieval from the web
  • G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
  • G06F16/9566—URL specific, e.g. using aliases, detecting broken or misspelled links
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L61/00—Network arrangements, protocols or services for addressing or naming
  • H04L61/30—Managing network names, e.g. use of aliases or nicknames
• • H—ELECTRICITY
  • H04—ELECTRIC COMMUNICATION TECHNIQUE
  • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
  • H04L2101/00—Indexing scheme associated with group H04L61/00
  • H04L2101/30—Types of network names
  • H04L2101/32—Types of network names containing non-Latin characters, e.g. Chinese domain names

Definitions

• the present invention relates generally to the field of information transfers over the Internet and the various protocols associated with such information transfers.
• the World Wide Web is the total set of interlinked hypertext documents residing on HTTP (Hypertext Transfer Protocol) servers all around the world.
• Documents on the World Wide Web, called pages or Web pages are written in HTML (Hypertext Markup Language), identified by URLs (Uniform Resource Locators) that specify the particular machine and pathname by which a file can be accessed, and transmitted from node to node to the end user under Hypertext Transfer Protocol.
• Codes, called tags, embedded in an HTML document associate particular words and images in the document with URLs so that a user can access another file, which may be halfway around the world, at the press of a key or the click of a mouse.
• FIG. 11 is a screen shot of a conventional Web browser.
• the World Wide Web can be thought of as a vast, hyperlinked bank of data.
• a user To gain access to the World Wide Web, a user must install on his or her computer the appropriate software and obtain a network connection from an Internet access provider.
• the URL identifier for a resource specifies the protocol to be used in accessing the resource (such as "http:” for a World Wide Web page or "ftp:” for an FTP site), the name of the server on which the resource resides and optionally the path to a resource (such as an HTML document or a file on that server.)
• a resource such as an HTML document or a file on that server.
• http://www.israeliinternet.com/thissubsite/sitecontents.html "http://” identifies the Hyper Text Transfer Protocol ; www.israeliinternet.com is the name of the relevant Web server; "/thissubsite/” identifies the directory of the desired document; and "sitecontents.html” designates the document to view.
• Each server name is associated with the 32 bit IP address that identifies a host machine on the Internet.
• the association is accomplished through the use of other computers known as Domain Name Servers. See Siyan, Karanjit, Inside TCP/IP. 3 r ed.. New Riders Publishing,
• the URL that is recognized on the Internet is referred as the "conventional URL” and the server name that is recognized on the Internet is referred to as the "conventional server name.”
• convention URL the URL that is recognized on the Internet
• server name that is recognized on the Internet
• conventional server name the server name that is recognized on the Internet
• reference to languages, alphabets characters and glyphs are based on the terminology used in the specification for the Unicode standard. See The Unicode Standard Version 2.0, Addison- Wesley, 1998.
• a character is defined as smallest component of written language that has semantic value; a glyph, on the other hand, represents the shape that the character can have when it is rendered or displayed.
• FIG. 12 is a screen shot of a Hebrew language browser.
• a conventional URL must be provided in a specific syntax, which is difficult for many users to understand, and even the minor errors, such as confusing ".” with ",” would result in the user failing to access the desired resource.
• the invention contemplates the transformation of a conventional URL to an identifier that is familiar to the user. (This familiar identifier will be referred to as a "friendly" identifier.) This transformed identifier would be displayed to the user. Internally, the apparatus would continue to use the conventional URL and would use this URL in accessing resources on the Internet. Similarly, all resource identifiers that are returned to the apparatus as a result of its operations would be transformed into identifier that are familiar to the user.
• FIG. 1 is a flowchart illustrating the conversion algorithm
• FIGS. 2-5 are diagrams illustrating the conversion algorithm
• FIG. 6 is a flowchart illustrating the mapping algorithm
• FIG. 7 is a block diagram showing a preferred embodiment of the system.
• FIG. 8 is a block diagram showing one embodiment of the client computer
• FIG. 9 is a block diagram showing one embodiment of the computer server.
• FIG. 10 is a block diagram showing one embodiment of the Web server
• FIG. 11 is a screen shot of a conventional English language Web browser
• FIG. 12 is a screen shot of a conventional Hebrew language Web browser
• FIG. 13 is a screen shot of a Hebrew language Web browser that is a preferred embodiment of the invention
• FIG. 14 is a screen shot of a Hebrew language Web browser that is another preferred embodiment of the invention
• FIG. 15 is a screen shot of a Hebrew language Web browser that is another preferred embodiment of the invention
• FIGS. 16 and 17 is a block diagram of the transformation involved in a preferred embodiment of the invention
• FIGS. 18 and 19 is a block diagram of the transformation involved in another preferred embodiment of the invention.
• the overall objective of the invention is to make using the World Wide Web and e- mail a more natural experience for the majority of the world's population who do not use Latin characters in their written language.
• the invention permits transformation of a conventionally URL to any native language that a Web surfer may use. Users of a preferred embodiment of the invention will be able to view Web site addresses in the user's own written language and use e-mail addresses in their own written language.
• the invention takes several different embodiments each geared to a specific situation. Each embodiment, however, relies on transforming an alternative resource identifier into a conventional resource identifier.
• the hidden conventional resource identifier is then used to access resources on the Internet in a conventional manner.
• the conventional resource identifier may be hidden for cosmetic reasons from the user would be available if the user so desired.
• This strategy is a common approach in software engineering.
• storage devices such as magnetic disk drives can be made to appear to the user to be much larger in capacity than they actually are by compressing the data stored on the disk drive in a lossless manner.
• the data is uncompressed on-the-fly in a manner that is concealed for cosmetic reasons from the user.
• the additional steps result in delay, it is well-known in the art how to reduce the delay to an imperceptible interval of time.
• the present invention contemplates displaying a easily comprehensible resource identifier (that is, a friendly identifier) to the user, while the apparatus uses a conventional resource identifier in accessing resources on the Internet.
• the apparatus achieves this functionality by transforming, on-the-fly, the friendly resource identifier to a conventional resource identifier. This transformation process is referred to in this patent application as a transformation algorithm.
• Conversion Algorithm Referring now to FIG. 1, there is illustrated the "conversion" algorithm for transforming a conventional resource identifier into a friendly resource identifier.
• the set of characters of the non-Latin written language used are the Hebrew characters.
• step 100 standard parts of conventional resource identifiers such as "http://www" "com” and "htm” are identified.
• step 102 the standard parts are converted to well-known Hebrew equivalents such as I 1 I / / * J J for
• step 104 the remaining parts of the conventional resource identifier is analyzed for words that have identifiable meanings. For example, the words “health” and “insurance” would be recognized in the word “healthinsurance”.
• step 106 the Hebrew word J
• step 108 the complete Hebrew resource identifier would be produced.
• mapping Algorithm Referring now to FIG. 2, there is illustrated the "mapping" algorithm for transforming a conventional resource identifier into a friendly resource identifier.
• the set of non-Latin characters used are Hebrew characters.
• the conventional resource identifier is inserted into a database query.
• the database query is executed against a database of friendly resource identifiers. Each friendly identifier record in this database would have a field indicating the conventional resource identifier to which the friendly resource identifier is mapped.
• step 204 the success of the query is evaluated. If the query produced a result then that result in step 206 would be the friendly resource identifier. If the query did not produce a result, then failure to obtain a friendly resource identifier would be indicated.
• the conventional resource identifier http://www.healthinsurance.com would be mapped to the Hebrew characters.
• An important useful feature of the mapping algorithm is that any conventional resource identifier could be mapped to any friendly resource identifier. Accordingly, a resource that is merely one of many web pages on a server could be made to appear from its friendly resource identifier to be the default page (that is, the top page) of the Web server.
• non-English speaking Internet users will not even have to have English characters on their keyboard. They will be able to dial any location on the World Wide Web including e-mail using their own native language keyboard.
• the invention will allow for every Internet user world wide, to use their regular mailing address, in their native language, as their e-mail address.
• the disclosed system will receive and deliver email from that address to any location on the Web.
• a portal based system there will be an option for on screen keyboard in every language.
• a user will be able to use his mouse to click native language addresses, email, search engine, and similar items even if the user is in a location where the user has no access to a native language keyboard.
• the system in each language, will be locked into a site. That site will be a specific home page in that language. Every Internet address in that language will be directed into a sub site. To the users, both Web site owners, as well as surfers, the sub site will appear and function as a home page. For example, when an Israeli individual obtains the Hebrew address , the system will convert that Israeli address into an URL that will appear after the regular address. In this case, surfers who do not use the conversion system will see, and may key in, by using the Internet address: http://www.worldurls.com/healthinsurance. An Israeli individual who uses the Hebrew conversion system will view and dial the address in Hebrew. E-mail in this example may go through healthinsurance@worldurls.com. Obviously, conversion system users will key in and view the e-mail with a Hebrew address. The server part of the system will accept free Web sites and e-mail applications. A person may insert an existing URL if the person only wants the address to link to their existing Web site.
• a users may choose a native language Internet address or e-mail account name. If the Internet address or e-mail user name is taken, the user may enter a different choice.
• the system may will generate a Web page or e- mail account.
• the internal name assignment system will work in a similar fashion to the way the system works in the direct translation portion of the system.
• L_ the two tier transformation system
• the surfer will also be able to key in the address in his native language.
• the system will then reverse the process.
• the system will use both the word to word as well as the letter to letter to construct the address. It will create an anomaly where a Latin letter may have more then one letter translations within the same address. That is because the value of the letters in the words translation system is fluid, while in the letter to letter system, the relationship is constant.
• an embodiment of the invention may assign to every English character, a Japanese word that sounds like the letter or as close to sounding like it as possible so that surfers are able to recognize when a Japanese word is used to identify non-English letters.
• FIGS. 16 and 17 illustrate the conversion process.
• the structure of a preferred embodiment is client computer 1000 which has access to the Internet.
• the computer server 2000 also has access to the Internet Web server 3000 also has access to the Internet.
• client computer 1000 includes a CPU 405, Ram 415, ROM 420, clock 435, video driver 425, video monitor 430, communication port 440, input device 445 and data storage device 460.
• computer server 2000 includes CPU 505, Ram 515, ROM 520, clock 535, video driver 525, video monitor 530, communication port 540, input device 545 and data storage device 560.
• Data storage device 560 contains data bases used in providing the conventional and friendly resource identifiers.
• web server 3000 includes CPU 605, Ram 615, ROM 620, clock 635, Web software 640, and data storage device 650), Video Monitor 670, comments port 660 and Input Device 690.
• One preferred embodiment of the invention would be a browser that incorporates software that uses the two algorithms. If the user types a Hebrew resource identifier, the computer must first convert the Hebrew resource identifier to a conventional resource identifier. The algorithm for this process would be the conversion algorithm or the mapping algorithm.
• the user of the browser would use computer server 2000 as an Internet Service Provider that would automatically download to the browser the mapping database.
• the mapping database in another embodiment would be e-mailed to the browser which would incorporate the new mappings into the existing database.
• the operation of the system commences with the user of client computer 1000 inputting a friendly resource identifier using non-Latin characters.
• the client computer 1000 would formulate a file consisting of the information entered in non-Latin characters.
• the client computer 1000 would process the friendly resource locator using either the conversion algorithm or the mapping algorithm and would contact Web server 3000 for the appropriate HTML page
• FIG. 9 is a screen shot of such a browser.
• client computer 1000 would contact computer server 2000.
• Computer server 2000 would then carry out the transformation algorithm and then transmit the information back to the client computer 1000, which would then use this information to obtain the HTML pages.
• server 2000 would obtain itself the HTML page and then retransmit the HTML page to the user.
• a variation of this preferred embodiment would use a browser that uses voice recognition technology.
• mapping algorithm may be successful for part of the resource identifiers (such as the conventional server name) but not for the HTML document. In that case, the mapping algorithm would be applied to the conventional server name and the conversion algorithm would be applied to the remaining portion of the resource identifiers.
• the computer server 2000 would host HTML page on its system. The user would input the friendly resource identifier for one of these hosted HTML pages.
• the client computer 1000 would transform the friendly resource identifier into the appropriate conventional resource identifier. The client computer 1000 would then retrieve the appropriate HTML page from computer server 2000. In another preferred embodiment the client computer 1000 would automatically contact the computer server 2000 in the event that a non-conventional resource identifier is inputted. The computer server 2000 would then perform the conversion.
• This HTML page would also be available to a client computer 1000 that does not use a preferred embodiment but the resource identifier would be conventional one such as "http://www.worldwideurls.com/bjifh-hjjm. Preferred Embodiment of Invention in Portal System
• a portal is the common term for a directory of Internet resources.
• the invention could also be embodied in a portal system in all resource identifiers are friendly resource identifiers.
• the portal server would use the conversion algorithm or the mapping algorithm to supply the information to client computer 1000 to retrieve the appropriate HTML document.
• Preferred Embodiment of Invention in Search Engine the friendly search term would be converted into various conventional using the transformation algorithms Latin search words and a conventional search would be executed. The results would be returned to the browser using either the conversion algorithm or the mapping algorithm.
• the e-mail address would be mapped from Latin to non-Latin characters or the reverse. Either the conversion algorithm or the mapping algorithm would be used. Accordingly, a user whose written language does not consist of Latin characters would be able to use e-mail using the characters of the written language.

Applications Claiming Priority (3)

Publications (2)

Family

ID=22289317

Family Applications (1)

Country Status (12)

Families Citing this family (5)

Citations (4)

Family Cites Families (13)

• 1999
  • 1999-04-30 IL IL14227599A patent/IL142275A0/xx unknown
  • 1999-04-30 EP EP99920268A patent/EP1123533A4/de not_active Withdrawn
  • 1999-04-30 EA EA200100408A patent/EA004074B1/ru not_active IP Right Cessation
  • 1999-04-30 TR TR2001/01131T patent/TR200101131T2/xx unknown
  • 1999-04-30 JP JP2000572779A patent/JP2002526834A/ja active Pending
  • 1999-04-30 AU AU37808/99A patent/AU769025B2/en not_active Ceased
  • 1999-04-30 KR KR1020017003996A patent/KR20010075446A/ko not_active Application Discontinuation
  • 1999-04-30 CA CA002345970A patent/CA2345970A1/en not_active Abandoned
  • 1999-04-30 CN CN99813555A patent/CN1332876A/zh active Pending
  • 1999-04-30 WO PCT/US1999/009614 patent/WO2000019342A1/en active IP Right Grant
• 2001
  • 2001-04-20 ZA ZA200103224A patent/ZA200103224B/en unknown
• 2002
  • 2002-02-16 HK HK02101139.8A patent/HK1039666A1/zh unknown
  • 2002-07-23 HK HK02105422.5A patent/HK1043849A1/zh unknown

Patent Citations (4)

Non-Patent Citations (3)

Also Published As

Similar Documents

Legal Events