U.S. patent application number 11/621267 was filed with the patent office on 2007-12-13 for automatic conversion system.
This patent application is currently assigned to Netmask (El-Mar) Internet Technologies Ltd.. Invention is credited to Eliyahu Marmor.
Application Number | 20070288660 11/621267 |
Document ID | / |
Family ID | 21917495 |
Filed Date | 2007-12-13 |
United States Patent
Application |
20070288660 |
Kind Code |
A1 |
Marmor; Eliyahu |
December 13, 2007 |
Automatic Conversion System
Abstract
A method for transferring information between a server and a
client, through a converter. The method includes receiving an
Internet hypertext document by the converter from the server,
inserting a plurality of objects into the Internet hypertext
document without substantially changing the outward appearance of
the hypertext document, wherein the inserted objects comprise
programs or program calls and transferring the Internet hypertext
document with the replacement objects to the client.
Inventors: |
Marmor; Eliyahu; (Kfar-Saba,
IL) |
Correspondence
Address: |
WOLF, BLOCK, SCHORR & SOLIS-COHEN LLP
250 PARK AVENUE
NEW YORK
NY
10177
US
|
Assignee: |
Netmask (El-Mar) Internet
Technologies Ltd.
Kfar-Saba
IL
|
Family ID: |
21917495 |
Appl. No.: |
11/621267 |
Filed: |
January 9, 2007 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
09941515 |
Aug 28, 2001 |
7167925 |
|
|
11621267 |
Jan 9, 2007 |
|
|
|
09284272 |
Apr 12, 1999 |
6601108 |
|
|
PCT/IL98/00134 |
Mar 24, 1998 |
|
|
|
09941515 |
Aug 28, 2001 |
|
|
|
60041623 |
Mar 27, 1997 |
|
|
|
Current U.S.
Class: |
709/246 |
Current CPC
Class: |
H04L 67/28 20130101;
G06F 16/957 20190101; G06F 16/258 20190101; G06F 16/252 20190101;
H04L 67/02 20130101; H04L 67/22 20130101; H04L 67/2823
20130101 |
Class at
Publication: |
709/246 |
International
Class: |
G06F 15/16 20060101
G06F015/16 |
Foreign Application Data
Date |
Code |
Application Number |
Jun 12, 1997 |
IL |
121071 |
Claims
1. A method for transferring data between a server and a client,
comprising: receiving an Internet hypertext document by a converter
from said server; replacing an input receiving object included in
the hypertext document by another input object; and transferring
the Internet hypertext document with the replaced object to the
client.
2. A method according to claim 1, wherein replacing an object of
the hypertext document comprises replacing a submit button
associated with the input receiving object.
3. A method according to claim 1, wherein said another input object
is of a type supported by said client.
4. A method according to claim 1, wherein said input receiving
object is of a type not supported by said client.
5. A method according to claim 1, wherein said input receiving
object is of a type supported by said client.
6. A method according to claim 1, wherein replacing said input
receiving object is performed responsive to a known difference in
standards between said client and said server.
7. A method according to claim 1, wherein said another input object
does not refer to a standard tool included in a toolkit portion of
said client.
8. A method according to claim 1, wherein said another input object
is a call to a program.
9. A method according to claim 8, wherein said program is a Java
applet.
10. A method according to claim 8, wherein said program is a
Javascript program.
11. A method according to claim 8, wherein said program is an
activeX or BasicScript program.
12. A method according to claim 8, wherein said program emulates
the operation of the input object.
13. A method according to claim 1, wherein said another input
object is a program.
14. A method according to claim 13, wherein said program is a Java
applet.
15. A method according to claim 13, wherein said program is a
Javascript program.
16. A method according to claim 8, wherein said program emulates
the operation of the input object.
17. A method according to claim 1, comprising replacing a second
input receiving object in the hypertext document with a
program.
18. A method according to claim 1, further comprising: receiving
input by the another input object at the client; and transferring
the input received at the client by the another input object, to
the server.
19. A method according to claim 1, wherein transferring the input
received at the client comprises transferring to the converter data
entered to the another input object, upon its being entered to the
another input object.
20. Apparatus for brokering transmission of information between a
server and a client, comprising: a connection to said client; a
connection to said server; and a converter adapted to receive an
Internet hypertext document from the server through the connection
to the server, to change at least one input receiving object in the
document and to transmit the changed document to the client through
the connection to the client.
21. Apparatus according to claim 20, wherein the converter is also
adapted to add a control operable to allow a user to enter
configuration information for said converter (22) to the
document.
22. Apparatus according to claim 20, wherein the server and the
converter are comprised in a single computer.
23. Apparatus according to claim 20, wherein the converter is also
adapted to change the at least one receiving object, into a call to
a program.
24. A method for transferring information between a server and a
client, through a converter, comprising: receiving an Internet
hypertext document by the converter from the server; inserting a
plurality of objects into the Internet hypertext document without
substantially changing the outward appearance of the hypertext
document, wherein the inserted objects comprise programs or program
calls; and transferring the Internet hypertext document with the
inserted objects to the client.
25. A method according to claim 24, wherein inserting the plurality
of objects comprises replacing a plurality of objects with
replacement objects, having a similar outward appearance as their
respective replaced objects.
26. A method according to claim 25, wherein the replaced objects
comprise textual data.
27. A method according to claim 25, comprising selecting the
objects to be replaced by replacement objects as objects not
compatible with said client.
28. A method according to claim 25, wherein the replaced objects
comprise text objects and wherein the replacement objects comprise
references to data files and wherein said references encode at
least a portion of the content of said objects.
29. A method according to claim 25, wherein said replacement
objects are generated on-the-fly.
30. A method according to claim 24, wherein inserting the plurality
of objects comprises inserting at least one input receiving object.
Description
RELATED APPLICATIONS
[0001] The present application is a continuation of U.S. patent
application Ser. No. 09/941,515, filed on Aug. 28, 2001, which is a
divisional of U.S. patent application Ser. No. 09/284,272 filed on
Apr. 12, 1999, now U.S. Pat. No. 6,601,108 issued on Jul. 29, 2003,
which is a national stage of PCT Application PCT/IL98/00134 filed
on Mar. 24, 1998, which claims the benefit under .sctn. 119(e) of
U.S. Provisional Application No. 60/041,623 filed on Mar. 27, 1997,
the disclosures of which are incorporated herein by reference.
FIELD OF THE INVENTION
[0002] This invention is related to the field of multi-lingual and
multi-standard communication between independent computers and, in
particular, to automatic conversion between different
standards.
BACKGROUND OF THE INVENTION
[0003] One of the fastest growing applications on the Internet is
the world-wide web (WWW). The WWW is a collection of networked
computers which exchange pages of hyper-text using the TCP/IP
protocol. These pages may contain combinations of text, images and
sounds, each of which may be either dynamic or static. Hyper-text
is also called hyper-media or hyper-links. In addition, these pages
may provide various methods of data input, for example, fill-in
forms. In the context of the WWW, the pages are also called
documents. The computers may be roughly divided into two main
classes, clients and servers. The pages are usually downloaded from
the servers by a client, using a specialized program called a
"browser". In some cases, the client enters data onto a page, and
transmit this data to a server. This data is usually used to find
new pages for the client to download. Alternatively to storing
pages on a server, it is becoming a common practice to generate WWW
pages on-the-fly at the server, using special programs.
[0004] There exist several additional classes of computers,
including, search engines, which provide a list of pages on servers
which relate to a particular search; proxy servers, which broker
communications between clients and servers, for example, by locally
storing frequently read pages; and gateways, which connect whole
networks to the Internet. A rapidly growing subset of the "client"
class of computer is the network computer, which is a specialized
computer which is especially designed for connection to the
Internet. Included in this sub-class are also Internet telephones
and Internet TVs, all of which are not general purpose computers
and have their Internet support hard-wired rather than programmed
in software.
[0005] One of the greatest obstacles to the continued expansion of
the WWW is the multi-lingual aspect of the data transmitted, which
is compounded by language limitations of users. Currently, most of
the pages in the WWW are written in English and most of the
browsers and the servers are designed mainly for use with the
English language. This situation is equivalent to having a
telephone system which can only transmit words in English and a TV
system which can only transmit programs in English.
[0006] Multi-lingual computer applications are known, for example
multi-lingual word processors and even multi-lingual operating
systems. However, unlike the Internet, in a computer application
the system developer enforces a single standard of language
representation and handling. In the Internet, there is no single
system developer and it is not possible to enforce a single
standard worldwide. Furthermore, there may be multiple standards in
a single country. For example, in Japan there are three common
character code set encodings for the Japanese language; in Israel,
there are several common character sets and three different
standards for display and input of textual information. There also
exist many variants of the display standards in Israel. It should
be appreciated that for many aspects of multi-lingual language
support there is no common denominator between the different
standards.
[0007] The Internet publication "The Multilingual World Wide Web",
written by Gavin Nicol in November 1994, and currently found at the
URL: "http://www.sil.org:80/sgml/nicol-multwww.html", describes
four main failure modes of multi-lingual computer applications and
discusses their relevance to the WWW. The first failure mode is
related to data representation, i.e., how textual data is
represented and how individual characters are encoded. As noted
above, there are three such encoding standards in Japan and several
in Israel. Further, the same character code may be used for
different glyphs depending on the language and on the character
set.
[0008] The second failure mode is related to data manipulation,
where a given program cannot manipulate multi-lingual data. Some
browsers do not support fonts which require more than 8 bits for
encoding. Unicode, for example, requires 16 bits. None of the
leading browsers are designed to support variable width (in bits)
character codes.
[0009] The third failure mode is data display. It should be noted
that in many languages, such as Arabic, the glyph form of a letter
is dependent on the surrounding letters. This requires various
display algorithms. In addition, the number of languages and fonts
in the world are much greater than the number usually stored in a
client computer, especially if it is a specialized network
computer. Also, when using some browsers it is not possible to
simultaneously display more than one language at a time (in
addition to English).
[0010] The fourth failure mode is related to data input. One issue
is keyboard mapping--assuming that a browser supports the font of
the language used by the server, how should the browser map
keystrokes to the individual glyphs. Many languages, such as
Russian, require more than the standard 26 letters of English.
Another issue is support for bi-directional data input. Some
languages, for example, Hebrew and Arabic, are written from right
to left (RTL) rather than from left to right (LTR), as English is.
Other, oriental, languages are written in a vertical
orientation.
[0011] There are several problems unique to bi-directional
languages. Even when the language is written RTL, numbers are
(usually, but not in all "standards") written LTR. In addition, the
text may be stored in a "logical" manner, where the first stored
letter is usually the rightmost letter. Alternatively, the text may
be stored in a "visual" manner, where the first stored letter is
the leftmost letter, which in a multi-line text is located in the
middle of the text. Thus, visually stored data is displayed LTR
(with an appropriate font), while logically stored data must be
displayed on a letter-by-letter basis--LTR letters displayed one
way and RTL letters displayed in another way. It is a common
practice to mix visual and logical representations in a single WWW
page. This is particularly true for input. The input is most
conveniently made using a logical representation, even though the
data may be stored using a visual representation.
[0012] These above problems are compounded when viewed in the
context of the WWW. One example of such a problem relates to search
engines. Search engines automatically assimilate the contents of
many WWW pages and allow a client to search these pages using
various methods. If a page is stored using a visual representation,
a search using keywords entered using a logical representation will
not find the page. Of course, if the character set encoding is
different, the page will not be found either. Another example, also
relating to search engines arises in languages where there is more
than one legal way to spell a word. This is common in various
dialects of English, but in That, there is a lexical equivalence
between various orderings of certain three-letter groups. Since
search engines are inherently global, enforcing a single standard
is practically impossible.
[0013] Another example of a compound problem is the use of multiple
standards and/or languages in a single WWW page. Another compound
problem is translating between units of measurements and ways of
writing dates and times. For example, "Jan. 6, 1999" represents
Jan. 6, 1999 in the US and Jun. 1, 1999 in Europe.
[0014] To make matters worse, even the standard language of the WWW
pages, HTML (Hyper-Text Meta Language) is not uniform around the
world.
[0015] As a direct result of these problems, the "global village"
has not yet arrived. One pointed example can be seen in Israel. At
the time of this writing, Israel is one of the world industrial
leaders in most Internet applications. However, the penetration of
the Internet into the public sector is substantially retarded as
compared to the US, even though a higher percentage of households
in Israel own a computer with a modem than in the US.
[0016] An obvious solution would be to adapt the clients and
servers in the Internet so that they support multiple languages. In
particular, automatic WWW page generators will also have to be
modified. In addition, such adaptation will probably require
modifications to development environments. The amount of work
required for this type of adaptation is enormous, since every
existing browsing software and/or hardware would have to be
adapted, a single standard would have to be enforced and all new
applications would be limited by having to support a great number
of languages and standards. This would be contrary to the concept
of network computers: providing only the minimal hardware and
software for surfing the WWW. For this reason, among others, most
"multi-lingual" solutions support only one language in addition to
English. In many cases, the languages supported are not the two
which are desired.
[0017] In an attempt to solve the problem of multi-lingual
searching, a web site has been constructed in which a client enters
search terms in one language (Hebrew) and the search engine
translates the words to English and applies the translated words to
one of a limited number of existing search engines. The input is
entered using Latin characters, which the web site maps to Hebrew
characters after the input process is finished.
[0018] In yet another attempt, a web site has been created in which
a JavaScript code segment is included in a WWW page, which displays
a virtual keyboard in the desired language and which allows a user
to click on keys. Each click adds a letter to a text object. The
input from the user is directed only to the web site and for use of
the programs therein and does not allow communication with other
web sites.
[0019] Several solutions for the problem of display of
multi-lingual pages have been suggested and/or tried. The Microsoft
Internet Explorer version 3.01, Hebrew version, uses meta-tags in
the WWW page to indicate whether a text object uses visual encoding
or logical encoding. This information is used to drive display
algorithms for the text object.
[0020] In the above referenced WWW publication and in "Summary of
K12 activities in Japan", by Kunio Goto and Masaya Nakayama, URL
"http://k12jain.ad.jp/inet95.html", a conversion server is
suggested for use in Japan. The server is suggested for use as a
proxy server and it replaces character codes from one standard set
with codes from another set. This replacement is on a letter by
letter basis.
[0021] In one system, "Internet with an Accent", published by
Accent Software Ltd., Israel, multilingual pages are developed
using a special development environment provided with the package.
The pages are then stored in a special format. The client must
either be provided with a special browser or with a plug-in to his
existing browser. This package has the capability of automatically
displaying pages in one of several languages based on the setting
at the client. However, this package only works if both the client
and the developer use the "Accent" package.
[0022] The common denominator to all of the above solutions is that
they require changes to at least one, and usually at least two, of
the client, the server and/or the development environment. As a
direct result, the accessibility of advanced and newly developed
features (for non-multi-lingual applications) is retarded. In
addition, the above solutions are not easily portable to newly
developed systems.
SUMMARY OF THE INVENTION
[0023] It is an object of some embodiments of the present invention
to allow data to be exchanged between substantially any client and
substantially any server in substantially any language or standard,
without requiring any changes to be made in the server, client or
even in a development environment in which the data is generated.
Preferably, the server and the client communicate using a WWW
protocol.
[0024] It is a particular aspect of some embodiments of the present
invention to provide a solution to the input of multi-lingual
information.
[0025] An automatic converter, in accordance with preferred
embodiment of the invention is integrated into a client-server
relationship as a (hidden) proxy. When the client downloads
information from the server, the converter converts the information
to a standard usable by the client. When the client enters input
data to the server, the converter converts the input data to a
standard usable by the server.
[0026] Thus, instead of the multi-lingual support increasing the
complexity of the computer software on the client, the support is
provided by the network itself, i.e., "the network is the
computer".
[0027] In a preferred embodiment of the invention, the converter
automatically determines the standard used by the server for a WWW
page. Preferably, the converter automatically detects the language
of at least a portion of the page.
[0028] Alternatively or additionally, the converter automatically
detects the standard used by the client. Preferably the converter
automatically detects the language used by the client.
Alternatively, the client sends information to the converter
regarding the client's capabilities. In one preferred embodiment of
the invention, the converter queries the client regarding the
client's capabilities. The client may respond automatically, or a
user at the client may respond instead.
[0029] In a preferred embodiment of the invention, the client is
provided with a manual override for the standard used by the server
and/or the client. This feature is especially useful if the
automatic standard detection does not properly detect the standard.
Preferably, even if the automatic converter cannot pinpoint the
precise standard used by the client and/or the server, the
converter does attempt to narrow the possibilities. It should be
appreciated however that automatic detection of standards may be
adversely affected by the existence of mistakes in the WWW page,
such as spelling mistakes.
[0030] It is a particular aspect of some embodiments of the present
invention to provide a seamless connection between a client and a
server, in which all data from the server is converted into data
usable by the client and all data from the client is converted into
data usable by the server.
[0031] In a preferred embodiment of the invention, data from the
server which cannot normally be displayed on the client is
converted, by the automatic converter, into image files for display
on the client. Preferably, text data for which there is no
available font on the client is converted in image data, for
example GIF format data. Preferably, the text data is converted
into a plurality of images. In a preferred embodiment of the
invention, small groups of words are converted into a single GIF
file, such that resizing of an object containing the text data is
facilitated. Preferably, the number of words in a group is
inversely related to the font size. Alternatively each group
consists of a single word, to enhance caching.
[0032] In a preferred embodiment of the invention, information
relating to the content and/or the format of the converted text is
encoded into the name of the image file. Thus, the name of an image
file may include an indication that the word is "the" and that it
is underlined. Encoding the information in this manner increases
the efficiency of cache systems.
[0033] Another aspect of some preferred embodiments of the
invention relates to replacing input objects, which are not
supported by the client, with custom made Java applets. In these
embodiments, the converter replaces the definitions of input
objects, in the pages sent by the server, with calls to Java
applets. Preferably, the automatic converter parses the pages to
determine the input objects and replaces the input objects which
have no support at the client with Java applets. When the page is
displayed by the client, the client is provided with a "new" input
object, which supports the standards and/or language. This is most
convenient for the client and which does not require support by the
client's browser. Preferably, these Java applets are cached at the
client for future pages, so that the applets need not be download
anew with each page. Optionally the new input object is compatible
with the server's standards. Alternatively, the converter converts
the data entered using the input object to a standard supported by
the server.
[0034] In a preferred embodiment of the invention, the Java applets
which are used for input in a particular language render individual
keystrokes as character glyphs even if the particular font required
by the language is not supported by the client. Preferably the
applets also provide other services, such as bi-directional input,
letter fusion and even spell checking.
[0035] Another aspect of the present invention relates to
controlling the viewing of copyrighted information. In a preferred
embodiment of the invention, copyrighted information is provided
through a conversion server, which server encodes the information
so that it is difficult to copy using data manipulation programs,
yet easy to assimilate using human senses, once displayed.
Preferably, the display process is also protected so copying the
displayed information is also difficult.
[0036] Typically, consumers must either pay to view copyrighted
information or they are forced to view advertisement information
along with the copyrighted information. However, once data is
available in a computer readable format, there is a danger that an
infringer will copy the data, remove any advertisements and
redistribute the data himself, for his own enjoyment and/or
profit.
[0037] Thus, in a preferred embodiment of the invention, an
automatic converter brokers information between a client and an
information provider, while providing and presenting the
information to the client in a form which is not easily copied.
[0038] In a preferred embodiment of the invention, the client is
provided with a program, preferably a Java applet, which temporally
modulates the information, so that only small parts of the
information are displayed at any instant. Thus, even though a human
can integrate the displayed information, a snapshot of the
displayed data will contain only partial amounts thereof. Some
examples of temporal modulation include, displaying the data in a
running strip and intermixing advertisements with the copyrighted
information. Thus, after viewing the data, the client will not have
in his possession a file containing only and all the displayed
information.
[0039] In a preferred embodiment of the invention, client programs
are authenticated. Preferably the authentication uses a key-code
system in which the server sends a key to the client and the client
is expected to respond with a code which is a (secret) function of
the key. Preferably, a different key-code combination is used in
each communication by the server. Preferably, the transmitted data
is encrypted, to reduce the possibility of it being intercepted by
a copyright pirate.
[0040] There is therefore provided in accordance with a preferred
embodiment of the invention, a method for transferring information
between a server and a client, through a converter, comprising:
[0041] analyzing at least a portion the information by said
converter, to determine a standard used by said server to encode
the information in the portion; and
[0042] replacing at least a portion of the analyzed information
with other information, which other information uses a second
standard,
[0043] wherein, analyzing comprises parsing the information on a
syntactic level and wherein said information comprises at least one
Internet hypertext document. Preferably, the standard comprises a
language. Alternatively or additionally, the standard comprises a
standard for an RTL language. Alternatively or additionally,
replacing comprises replacing only a portion of the analyzed
information.
[0044] There is also provided in accordance with a preferred
embodiment of the invention, a method for transferring information
between a server and a client, through a converter, which
information includes at least one input object, comprising
receiving said information by said converter from said server;
replacing said input object with another input object; and
transmitting the information after said replacing, wherein said
information comprises at least one Internet hypertext document.
[0045] Preferably, the input object is a text object. Alternatively
or additionally, said another input object is of a type supported
by said client. Alternatively or additionally, said input object is
of a type not supported by said client. Alternatively, said input
object is of a type supported by said client.
[0046] In a preferred embodiment of the invention, replacing
comprises replacing said input object responsive to a known
difference in standards between said client and said server.
Preferably, said another input object is not included in a toolkit
portion of said client. Alternatively or additionally, said another
input object is a call to a program. Preferably, said program is a
Java applet.
[0047] In a preferred embodiment of the invention, the method
comprises replacing a second input object with a Java applet,
wherein said second input object is supported by the client.
[0048] There is also provided in accordance with a preferred
embodiment of the invention, a method for transferring information
between a server and a client, through a converter, comprising
analyzing at least a portion of the information by said converter,
to determine a standard used by said server to encode the
information in the portion; and determining at least one portion of
said information not supported by said client, wherein said
information comprises at least one Internet hypertext document.
[0049] Preferably, the method comprises replacing said at least one
portion with a portion supported by the client. Alternatively or
additionally, said standard comprises a language. Alternatively or
additionally, said standard comprises a standard for an RTL
language.
[0050] There is also provided in accordance with a further
preferred embodiment of the present invention, a method for
transferring information between a server and a client, through a
converter, comprising:
[0051] selecting an output portion of said information, which
information is designated for the client and comprises at least one
Internet hypertext document, which portion has a particular
appearance when displayed by a client compatible with output
portion; and
[0052] replacing the output portion with other data, having a
similar outward appearance as the output portion, when the other
data is displayed by the client for which the information is
designated.
[0053] Preferably, said other data is image data. Alternatively or
additionally, said output portion is textual data. Alternatively or
additionally, selecting an output portion comprises selecting an
output portion not compatible with said client. Alternatively or
additionally, said other data comprises a reference to a data file
and wherein said reference encodes at least a portion of the
content of said output portion. Alternatively or additionally, said
other data is generated on-the-fly. Preferably, said other data is
generated at the converter.
[0054] There is also provided in accordance with a preferred
embodiment of the present invention, a method for transferring
information between a server and a client, through a converter,
each of said client and said server using different standards to
encode said information, comprising:
[0055] receiving data from said client;
[0056] changing said received data from a known standard of the
client to a known standard of the server; and
[0057] transmitting said changed data to said server, wherein said
data and said changed data comprise at least one Internet hypertext
document.
[0058] Preferably, said standards differ in language. Alternatively
or additionally, said standards differ in logical/visual
representation of an RTL language. Alternatively or additionally,
said standards differ in character set encoding. Alternatively or
additionally, said standards differ in character bit width.
[0059] There is also provided in accordance with a preferred
embodiment of the invention a method for transferring information
between a server and a client, through a converter, comprising:
[0060] detecting a text portion of said information by said
converter, which portion comprises ordered characters having a
meaning in a first representation and which information comprises
at least one Internet hypertext document; and
[0061] changing the order of at least some of said characters, such
that the text portion has the same meaning in a second
representation.
[0062] Preferably, changing the order comprises changing the order
characters responsive to a known display method used by said
client.
[0063] There is also provided in accordance with a preferred
embodiment of the invention, apparatus for brokering the
transmission of information between a server and a client,
comprising:
[0064] a connection to said client;
[0065] a connection to said server; and
[0066] a converter which receives an Internet hypertext document
from the server through the connection to the server, adds a
control to the document and transmits the document to the client
through the connection to the client,
[0067] wherein said control is operable to allow a user to enter
configuration information for said converter.
[0068] Preferably, said control is operable to download a data
entry form from said converter.
[0069] There is also provided in accordance with a preferred
embodiment of the invention, apparatus for brokering the
transmission of information between a server and a client,
comprising:
[0070] a connection to said client;
[0071] a connection to said server; and
[0072] a converter which receives an Internet hypertext document
from the server through the connection to the server, changes an
object in the document and transmits the changed document to the
client through the connection to the client.
[0073] Preferably, said converter adds an object to the document.
Alternatively or additionally, said converter removes an object
from the document. Alternatively or additionally, said converter
replaces an object on the page with another object. Alternatively
or additionally, said object comprises an object to be displayed by
said client. Alternatively, said object comprises an object which
accepts input at said client.
[0074] In a preferred embodiment of the present invention, the
apparatus comprises a server. Preferably, the server and the
converter are comprised in a single computer. Alternatively or
additionally, the server and the converter operate as a single
process.
[0075] There is also provided in accordance with a preferred
embodiment of the invention, a method for controlling the viewing
of copyrighted information, transmitted from a data source to a
client, on the Internet, comprising:
[0076] transmitting the information from the data source to a
server, wherein said information is in a format viewable by the
client;
[0077] converting the information, at the server, to an encoded
form;
[0078] transmitting the encoded form of the information to the
client; and
[0079] decoding and displaying, at the client, of the encoded
information, wherein said encoding and decoding makes said
information less available to copying by said client.
[0080] Preferably, the format of said information is a format used
on the Internet. Preferably, said format is a HTML format.
[0081] Alternatively or additionally, displaying comprises
temporally modulating the display of the information.
[0082] Alternatively or additionally, decoding comprises decoding
by a server-provided program. Preferably, the server-provided
program requires a live connection with said server. Alternatively
or additionally, the server-provided program is downloaded from the
server. Alternatively or additionally, the method includes
authenticating the server-provided program to the server.
Alternatively or additionally, converting comprises converting said
information to a form unusable by said client without said
server-provided program.
[0083] In a preferred embodiment of the invention, converting
comprises encrypting. Alternatively or additionally, converting the
information comprises converting only a portion of the
information.
BRIEF DESCRIPTION OF THE FIGURES
[0084] FIGS. 1A-1C are schematic diagrams illustrating preferred
network topologies for integrating an automatic converter, in
accordance with a preferred embodiment of the invention, into a
network;
[0085] FIGS. 2A and 2B show a portion of a HTML page before and
after automatic conversion, in accordance with a preferred
embodiment of the invention;
[0086] FIG. 3 is a flowchart of a process for determining what
standards should be used by a converter, in accordance with a
preferred embodiment of the present invention;
[0087] FIG. 4 shows a phrase using a visual representation and
using a logical representation, for a text mixing an LTR language
and an RTL language;
[0088] FIG. 5 is a flowchart of a process for converting input data
to a standard recognized by a server, in accordance with a
preferred embodiment of the invention;
[0089] FIG. 6 is a flowchart of a process for converting input and
output objects in a HTML page, in accordance with a preferred
embodiment of the invention; and
[0090] FIG. 7 is a flowchart of a Java applet which enables
multi-lingual input on a single language client, in accordance with
a preferred embodiment of the invention.
DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
[0091] FIG. 1A shows a configuration 20 of an interconnection of a
server 24 and an automatic converter 22, connected via an Internet
26 to a client 28, in accordance with a preferred embodiment of the
present invention. As used herein, "Internet" includes also
"Intranet" and "WWW" includes using the WWW tools and protocols on
an Intranet. FIG. 2A shows a portion of an HTML file downloaded by
client 28 from WWW server 24. A reference number 10 indicates a
text output object to be displayed and a reference number 12
indicates an input request object. Displaying the HTML file at
client 28 is usually performed using a browser. In a multi-lingual
situation (where server 24 and client 28 do not support the same
languages), it is entirely possible that client 28 is not capable
of displaying text object 10, for example, for lack of a suitable
font. In addition, it is even more usual that client 28 is not
capable of performing the input request 12, for example, if the
client does not have a keyboard mapping for the language used by
server 24.
[0092] In accordance with a preferred embodiment of the invention,
incompatible portions of the HTML file are automatically converted
by converter 22 such that client 28 is capable of displaying the
information in text object 10 and/or performing input request 12.
Preferably, this process is substantially invisible to client 28
and server 24. When client 28 requests a file from server 24,
server 24 supplies the file to converter 22. Converter 22 modifies
the file, on the fly, so that displaying the information in the
file will be within the capabilities of client 28 and sends the
modified file to client 28. If input is entered at client 28, which
input is not compatible with server 24, converter 22 converts the
input to a form usable by server 24.
[0093] In a preferred embodiment of the invention, converter 22
replaces input objects with Java applets, for example, an applet
16. These Java applets enable a user at client 28 to enter data in
a manner which is more comfortable for him and which manner is not
otherwise supported by client 28. Preferably, the applet supports
keyboard mapping, character combining and/or different types of
display of RTL languages. JavaScript, BasicScript and ActiveX may
be used instead of Java, however, they are less preferred due to
their technical limitations and because they are not as widely used
as Java.
[0094] FIGS. 1A-1C show various configurations for connecting an
automatic converter in an Internet configuration in accordance with
preferred embodiments of the invention. FIG. 1A shows configuration
20, where converter 22 is associated with server 24 and separated
by Internet 26 from client 28. Thus, communication between
converter 22 and server 24 is facilitated. This configuration is
useful if converter 22 comprises a proxy server or a gateway for
the server. However, when high bandwidth communication between
converter 22 and client 28 is required, this configuration is not
optimal. It should be appreciated that converter 22 typically
increases the volume of data which it transfers and usually adds to
the number of files transferred. For example, the file in FIG. 2B
is larger than FIG. 2A, even without including the attached image
files for FIG. 2B. However, this increase in file size is deemed
insignificant, especially when compared to the planned transmission
of audio and video information on the Internet and in view of the
rapid increase in the available communication bandwidth.
[0095] In some preferred embodiment of the invention, the server
and the converter are comprised in a single computer. In one
embodiment of the invention, WWW pages are automatically generated
by an automatic page generator on server 24 and passed to converter
22, which converts them for client 28. Preferably, the page
generator is incorporated into converter 22, such that they operate
as a single (CPU) process. It should be appreciated that server 24
handles the requests from client 28, controls the page generator
and, in this embodiment, converter 22.
[0096] FIG. 1B shows a configuration 30 in which a converter 30 is
separated from server 24 by an Internet 32 and separated from
client 28 by an Internet 34. In this configuration, neither
communication between converter 30 and client 28 nor communication
with server 24 are facilitated. However, this configuration may be
desirable if converter 30 servers as a server or as a
translation-service provider which is not associated with any
particular client or server. In such an application, converter 30
preferably adds promotional information to pages downloaded by
client 28. Converter 30 may add promotional or other information
also in other configurations of connections between converter 30,
server 24 and client 28.
[0097] FIG. 1C shows a configuration 40 in which a converter 38 is
associated with client 28. In this configuration, converter 38 may
serve as a proxy an/or gateway for client 28. In a preferred
embodiment of the invention, converter 38 is connected by LAN
(Local Area Network) to client 28 and possibly to an additional
client 36. Alternatively, converter 38 is run on the same computer
as client 28. It should be appreciated that since the communication
between converter 38 and client 28 is based on TCP/IP, the physical
locations of the server, converter and client are transparent,
except for issues related to the communication of data.
[0098] FIG. 3 is a flowchart showing a page reading and conversion
process in accordance with a preferred embodiment of the invention.
When a page download is requested by client 28, converter 38
receives the desired page from server 24. A parser in converter 38
then parses the page to determine input and output objects. As can
be appreciated, if converter 38 is used for converting elements
other than input and output objects, the parser will analyze those
elements too. The parser can be a very fast parser, because, in a
preferred embodiment of the invention the parser does not need to
perform a complete syntactic analysis of the page. Rather, the
parser can obtain most of the information it needs by identifying
the input and output objects and tags in the page. Further, the
simplicity of the parser provides some protection against
improperly structured WWW pages.
[0099] After parsing the page, the standards used by the server are
determined, preferably automatically. In some cases the WWW page
includes meta-tags which indicate the standard and/or language of
particular objects. However, the use of such meta-tags is neither
common, nor does a single world-wide standard govern their use.
Detecting the standard(s) used by the server or, more usually,
limiting the number of possible standards, is preferably a
heuristic process. One heuristic may be used for detecting the
character set-encoding. In a large amount of text, it may be
expected that most of the characters are letters. By analyzing the
distribution of the character codes, it is usually possible to
determine which character codes represent letters, the number of
letters in the character set and whether there are special letters
at the beginning or at the end of a word. Further, some languages
are characterized by a particular distribution of letters in the
language, for example in English, the most common letters are T, N,
O and E. Further, the distributions at the end of words is
different, in many languages, from at the beginning of words. Also,
some letter pairs or triplets may be common in a particular
language, e.g., "th" and "ing" in English. It is also usually
possible to detect which character codes represent numbers. If
converter 38 is loaded with most (if not all) of the possible
standards, the choice can be limited to those standards which are
reasonable in view of the page downloaded from server 24.
Preferably, each output object is separately analyzed, since
multiple languages and/or standards per page are possible. The set
of possible languages may be guessed based on the server location.
A particular type of standard which may be determined using these
methods is whether an RTL language is stored in a visual or logical
manner. In RTL languages, such as Hebrew, the letters at the end of
a word may use different glyphs than at the beginning of a word. By
detecting an end-letter at a beginning of a word, is can be
determined whether the language is stored visually rather than
logically. If such an end-letter is detected in a middle of a word,
than the language is probably not such an RTL language or the
character set encoding is not as expected. Also, some RTL language
standards use special direction changing control codes, which are
not letters and which are usually located in an output object
between RTL portion (language) and LTR portions (numbers and other
languages). The particular code value of such a control code and
its location may also be used to indicate the standard.
[0100] As can be appreciated, such an automatic detection method
may fail, at times. This failure may be due to a text portion being
too short or ambiguous or it may be due to mistakes in the WWW
page. One common mistake (in Hebrew) is the inadvertent replacement
of a regular letter with a similar-looking end-letter. In addition,
end-letters are sometimes not used in some words. Preferably, such
common mistakes and inconsistencies are registered in converter 38
and are ignored thereby.
[0101] In a preferred embodiment of the invention, converter 38
adds a control, such as a push-button, to the page. When a user
presses the button, a configuration page is downloaded from
converter 38. Alternatively, the control activates a Java applet
which displays a configuration form. The configuration page enables
the user to select the standard of the page. Preferably, data is
entered using a form. Preferably, the user can see the effect of
his selection on at least a sample of the page. Further preferably,
the user can select a different standard for each portion of the
page, using the configuration page. The user may also use the
configuration page to indicate the capabilities of client 28. As
can be appreciated, each downloaded page may use a different
standard.
[0102] In a preferred embodiment of the invention, the user can
configure converter 38 with a user-defined standard. A user-defined
standard is useful for standards which are not yet registered in
converter 38. Also, many standards have small variations, not all
of which can be automatically detected. In a preferred embodiment
of the invention, a user can upload a user-defined standard to
converter 38. An uploaded standard may include definitions of code
ranges, heuristics for determining the standard or even Java
applets for affecting the conversion. Java applets may include
input-object applets as describe below.
[0103] The capabilities of the browser at client 28 may be
registered using a configuration page, as described above.
Alternatively, the capabilities of each type of browser are stored
in converter 38. Further alternatively, converter 38 queries client
28 regarding its browser type and/or its capabilities. If the
amount of text entered by the user is sufficient, it may be
possible to automatically detect the standard used by client
28.
[0104] In a preferred embodiment of the invention, a control on
each downloaded WWW page, enables an override of the conversion. An
override may be required when the client includes a printer having
a different type of multi-lingual support than the browser. Also,
some cut-and-paste mechanism may not support multi-lingual usage.
One example is visual/logical display of RTL languages.
[0105] FIG. 5 is a flowchart of another aspect of automatic
conversion. When client 28 sends data to server 24, it may be
necessary to convert the standard from a standard used by client 28
to a standard which is usable by server 24. In a particular example
where server 24 is a search engine, client 28 may enter data using
a logical representation. Search engines usually store data using a
visual representation, as they are stored using a visual
representation in most WWW pages. Thus, if the data is not
converted from logical to visual, the search will probably fail.
FIG. 4 shows a phrase 70, as it is displayed (visual
representation), including two LTR word 72 and 74 and an RTL word
76. If phrase 70 is stored using a logical representation, shown as
a phrase 78, RTL word 76 is visually meaningless but its letters
are ordered in the same way as in most search databases. In such a
bi-directional search, a user is well advised to enter the search
terms in both visual and logical formats. In a preferred embodiment
of the invention, an input object, as described below, allows a
user to specify if data is to be visual or logical or both.
[0106] In a particular embodiment of the present invention, a
search engine registers multi-lingual pages both before and after
conversion by a converter, such as by downloading the pages both
directly and through the converter. One benefit of such
registration, is that pages written in an RTL language can thus be
registered both in a visual representation and in a logical
representation. As a result, clients can find the pages using the
search engine, even without using a converter during the
search.
[0107] Another problem which can be solved by converter 38 is the
problem of illegal form responses. If text in a foreign language is
appended to a URL (or POSTed) using the CGI.BIN standard, the
characters of the response may interfere with a correct
interpretation of the form response by the server. Converter 38 can
indicate the existence of a problem to client 28 and recommend the
user change his input. In addition, converter 38 may be able to
modify the response in a way which will be understandable by server
24, but will not affect the content of the response.
[0108] An example of such a problem arises when a server sends a
page encoded in Unicode (16 bits) to a 8 bit client. The client
will display something, but it will probably look like gibberish.
If a 16 bit client appends Unicode data to a URL and sends it to a
8-bit server the server will not be able to decipher the
response.
[0109] Another aspect of conversion of data sent from client 28 to
server 24 relates to tags sent in association with the actual data.
One such tag is "accept-charset", in which client 28 requests data
using a particular charset, since it can only display data in that
charset. This indicates the limitations of client 28 to server 24.
Since the use of converter 38, in accordance with preferred
embodiments of the present invention, allows even a limited client
to display substantially any font, converter 38 preferably modifies
this tag (and other such tags) to account for the combined
capabilities of converter 38 and client 28. Alternatively,
converter 38 only changes the "accept-charset" tag if server 24
indicates that it cannot supply the desired information under the
"accept-charset" constraint and then resends the request.
[0110] FIG. 6 is a flowchart of a conversion process of a WWW page
in accordance with a preferred embodiment of the invention. First,
converter 38 reads and parses a page. The conversion process may be
effected in parallel with the parsing or it may be performed after
the parsing. For each object in the WWW page, if it is an output
object, converter 38 determines if the output object is supported
by client 28, including, inter alia, font, character size and
character encoding. If the output object is not supported by client
28, it is converted into a form which is supported by client 28 and
the output object is replaced with the converted object(s). For
example, in FIGS. 2A and 2B, output object 10 is replaced by an
output object 14. Several types of conversion may be used. First,
the output object may be replaced with a different output object
which is supported by client 24. Alternatively, the output object
may be replaced with a call to a Java applet which renders the
output object. Preferably, such an applet is downloaded only once
and different data to be rendered is submitted to the applet for
each output object.
[0111] In a preferred embodiment of the invention, the output
object is replaced by one or more image files, which are generated
on-the-fly by converter 38. When converting text, each image
preferably corresponds to a small number of words, so that if the
output object is resized, the line breaks will look good. In many
browsers, if an image does not fit in a display area, it is either
cropped or not displayed; Text is usually folded over to the
following line. To emulate this behavior, relatively small images
must be used, so images that do not fit on a line will be pushed to
the next line. Preferably, the number of words in each image is
inversely related to the font size. Alternatively, each word is
placed in a separate file. If the font is large, the word is long
and/or the display area of the output object is small, a word may
be broken up between two or more images. Preferably, the image
files have a special file extension, such as ".B64", rather than
".GIF" so that the converter can more easily detect this type of
file. The converter instructs the browser to display B64 files as
GIF files.
[0112] In a preferred embodiment of the invention, the names of the
created image files encode the content and/or the format of the
words they replace. This encoding helps in caching, in garbage
collection and, if the client is capable of rendering using a Java
applet, it replaces the need to actually download the images, since
they can be locally generated. Also, since the client receives the
content of the output object and not only its image, makes it
possible for client 28 to supply a Java applet which searches the
contents for textual information. Another benefit is that the
converter is relived of the necessity to maintain a table of image
files and where they were sent. The following data is preferably
encoded in the name: font size (one of seven), font attributes
(Italic, Bold, Underline), 24 bits of color and the text content.
Preferably, the following encoding scheme is used: three bits for
size, three bits for attributes, 24 bits for color and N.times.8
bits for N 8-bit characters. The encoding may also include flags
indicating the encoding scheme (such as the number of bits per
character). Preferably, the encoding also includes several bits for
the font family and for the language. As the encoding must use
characters which are legal in WWW file names, the preferred
encoding is one in which each six bits are represented by one
character. The following 64 characters are preferably used to
indicate the bit values of between 000000 and 111111:
ABCDEFGHUJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789_@
[0113] In a preferred embodiment of the invention the output object
may be used to display a vertically oriented language. Displaying a
vertically oriented language may require a Java applet, as will
other types of output emulators.
[0114] If the object is an input object, converter 38 determines if
client 28 is capable of displaying the input object. If client 28
is not capable of displaying the input object or if client 28
requested to use a different input method, which is more convenient
than that supplied by his browser, the input object is replaced
with a different and, usually more capable, input object. In a
preferred embodiment of the invention, the replacement input object
is not an input object which is supported by the client's toolkit.
Rather, the input object is a Java applet which embodies the
desired input method. The Java applet preferably stays resident, so
it does not need to be downloaded from converter 38 very often.
[0115] FIG. 7 is a flowchart of a Java applet, used for input
emulation, in accordance with a preferred embodiment of the present
invention. The applet preferably deals with incoming keystrokes on
an individual basis. The handling of the keystrokes is dependent on
the keyboard mapping supplied by the Java applet. If a keystroke is
mapped to a control, the control is executed. Examples of controls
include, inter alia, "backspace", "delete character", "change
language and/or writing direction", "insert file", "help" (which
displays a help for using the Java applet, and in particular, the
keyboard mapping), "connect letters" and "compose letter". In some
cases, a control may display a keyboard mapping (for output only)
or a matrix of characters, which can be directly selected using a
mouse.
[0116] If the keystroke is a letter, if the glyph is supported by
client 28, the Java applet may use the client toolkit to render the
character. Thus, the applet need only be capable of rendering
characters not supported by the client toolkit. Alternatively, or
if the glyph is not supported by the client toolkit, the applet
renders the character glyph in the input area. In some cases,
entering a letter (or a space, which usually indicates the end of a
word) requires that the applet rerender a glyph as an word-end
letter or even combine two letters automatically. In composed
characters, such as Umlauts and Chinese pictograms, each additional
"letter" is an instruction to rerender the glyph.
[0117] There are several methods of uploading the contents of the
input box to the converter. As indicated above, in many cases, the
inputted data should be encoded so as not to interfere with the
regular operations of the client and/or server. As the Java
language is defined at this date, Java applets have no interaction
with any element of the WWW page, except that they can display data
in their accorded display area, get input from the input devices,
obtain a list of applets on the WWW page, communicate to such
applets, open a socket to the applet source and (in most browsers)
can request the downloading of a page. One way of sending the data
to converter 38 is to replace the submit button, of which each form
contains at least one, with a second Java applet which queries the
other Java applets in the form before uploading the form contents.
The standard submit button only queries input objects, not Java
applets. In accordance with an alternative embodiment of the
invention, the Java applet sends its contents to converter 38 when
the data is entered thereto. When the submit button is pressed at
client 28, converter 38 adds the input data it received from the
Java applet to what the submit button sends. If the contents of the
Java applet are over-written, it is the last entered data which is
sent to server 24. In another preferred embodiment of the
invention, a free-standing input object is supplied with an
individual submit button.
[0118] It should be appreciated that several types of elements of
the WWW page may be replaced in accordance with preferred
embodiments of the invention. In particular, dates and weights can
be detected in the text and converted to a format as used at client
28. Preferably, both the old value and the converted values are
displayed. In addition, numeric references to particular characters
can also be converted by converter 38 to new values relevant for
the converted output object.
[0119] A more general aspect of the present invention relates to
conversion input and output objects without relation to language.
For example, converter 38 can be used to emulate input/output
structures, such as tables, on browsers which do not support
tables. In a preferred embodiment of the invention, converter 38
replaces an unsupported input or output structure with an
indication to the user at client 28, of what the unsupported
structure is, and preferably, how it may be obtained. Preferably,
the converter renders the unsupported structures and sends them as
images and/or as Java applets to display the structures.
[0120] In a preferred embodiment of the invention, converter 38 can
be used to download Java applets, by demand, to client 28. Thus,
client 28 can be a simple browser and, when needed, capability
expanders in the form of Java applets are downloaded by converter
38 to client 28. Downloading applets as described above is better
than replacing portions of the browser and/or using plug-ins.
First, the applets are downloaded with the page that requires them
and without any intervention of the client. Second, since the
applet can only display information and/or handle input, they pose
less of a security risk.
[0121] Downloading capability expanders by demand opens up the
possibility that any individual may register a standard or a
capability at converter 38, included with which there should be a
Java applet for supporting the new features. When a client tries to
read a WWW page in that standard, the client will receive a
capability expander from converter 38. These capabilities are
especially useful in Java-based browsers, which can download
applets for supporting input and output objects from a converter
attached to them by a LAN. Alternatively, a browser may download an
updated version of itself or at least an updated version of a
portion thereof from a different computer, usually not a converter.
It should be appreciated that by converting the WWW pages and
appending applets thereto in contrast to modifying the browser
itself, there is a minimum of inference with the development of new
browsers, since the applets have only a bare minimum of interaction
with client 28.
[0122] In another aspect of the present invention, text based
output objects are replaced with audio output objects. This is
especially useful for users who have limited vision. Further, input
objects may be replaced with audio input objects. The voice
recognition may reside at the client or it may reside at the
converter.
[0123] In accordance with another aspect of the present invention,
conversion includes translating from the original language of the
WWW page to a language suitable for the client. In a basic aspect
of translation, translation includes transliteration from one
writing form to another, such as from Japanese characters to Latin
characters. Preferably, translation includes detecting the original
language of the page, translating it and replacing the original
text with the new text. The same process may be performed when
translating input entered at client 28.
[0124] Another aspect of the present invention relates to
converting data so as to reduce readability by client 28. One of
the bothersome problems with the Internet is that once copyrighted
information is transmitted to one computer, it can be retransmitted
to many computers without any control or reimbursement of the
copyright owner. A particular case is where, in a large
organization, one user buys certain information from an information
provider and then distributes copies of the information, by LAN to
many other workers in the organization. In most cases, the
copyright owner would be satisfied if the users of the information
paid for each copy of the information or if they are forced to view
commercial information, such as advertisements, when viewing the
copyrighted information. The copyright owner can then charge money
from the advertiser, for advertising space. One example of
undesirable distribution is database providers, which do not wish
for copies of the contents of their databases to be widely
available, except to paying customers. An example of uncontrolled
distribution is online data, which is freely available, but which a
customer is required to view advertisements with, while viewing.
Once the information is downloaded and copied, the advertisements
may be removed and/or subsequent viewers of the information will
not be required to pay for viewing. Most copyrighted information is
textual information, however, copyrighted information also includes
audio and image information.
[0125] In a preferred embodiment of the invention, copyrighted
information is presented, on a computer, in such a manner that it
is easily accessible to the senses of a consumer, but not easily
accessible to data manipulation tools on the computer. As a result,
the consumer can be forced to view advertisements or,
alternatively, each viewing of the information can be controlled
and/charged.
[0126] When data is transmitted from a server computer for display
on a client computer, it can be easily intercepted at one of
several points. Various aspects of the present invention strive to
increase the difficulty of intercepting the information. A first
interception point is when the data is presented on a display. Once
a screen full of text data is displayed the screen can be
photographed or an image of the screen can be captured and then
printed.
[0127] In a preferred embodiment of the invention, the displayed
data is temporally modulated so that at any given instant only a
small portion of the data is displayed. Thus, an image of the
screen is not useful for a copyright infringer. The data may be
temporally modulated using one of two schemes, the data may exist
on the client computer and be displayed in a temporally modulated
manner or the data may be downloaded, using a live connection, from
the server, so that only a small portion of the data is on the
client computer at any given moment.
[0128] In a preferred embodiment of the invention, data is
temporally modulated by only showing a small amount of data on a
screen at a time, the rest preferably being taken up by
advertisements. Thus, in order to recreate the data, an infringer
would be required to capture many screens and to piece together
many data portions from these screens. Preferably, the location of
the data portion changes between screens to increase the difficulty
of automatically piecing together of the data portions.
Alternatively or additionally, the copyrighted information is
intermixed with the advertisements in such a manner that it can be
easily separated by a human, but not by standard data manipulation
programs. One example of such a display is using a different fonts
or font sizes for the advertisements and for the copyrighted
information.
[0129] Alternatively, the data is temporally modulated at a high
enough frequency that a human can integrate the displayed data, but
a screen image will only capture part of the data. One such example
is flashing two partial images at a frequency higher than 30 Hz.
Another example is highlighting only a few words at a time, while
the rest of the text is on a dark background. Yet another example,
is displaying the data in a moving strip, such that only a portion
of the data is simultaneously displayed.
[0130] It should be noted that some media, such as video and audio
cannot be captured from a screen (or loudspeaker) with perfect
quality, so an infringer will experience some degradation.
[0131] A second interception point is at the data display program
itself. For example, when a WWW page is printed, the data display
program (usually a browser) sends that data files directly to the
printer. In a preferred embodiment of the invention, the data is
not available to the data display program. Preferably, the data is
made unavailable, by encoding it using an encoding scheme not
recognized by the browser, but only by a server-supplied Java
applet. This is an opposite to the usually situation, where the
data is originally encoded in an unrecognizable manner. In most of
the above described embodiment of the invention, the Java-applet
"knows" how to print the data and will do so at the request of the
browser. In this preferred embodiment of the invention, the Java
applet will not print the data, since that would be
counter-productive to the protection of the data. The encoding
scheme can include, changing the character codes, using an
unsupported font and changing the order of characters.
[0132] The Java applet may be downloaded anew each information
transfer or it may be locally resident at the client.
Alternatively, a data provider may supply a data display program,
such as a browser, or even an add-in, which incorporates the
functionality of the Java applet. Preferably, the Java applet
transmits back to the server various information regarding, number
of uses, a user number (for charging fees) and the like. It should
be appreciated, that in the embodiment where the Java applet
requires a live connection to the data provider and/or transmits
the user number to the provider, an encapsulated copy of the
copyrighted information, including both the encoded data and Java
applet may be freely distributed, since, in order to view the data,
some sort of control by the copyright owner will be exercised.
[0133] In a preferred embodiment of the invention, the data is
encoded using a cipher. Preferably, each data packet is sent with a
different key, so that continuous connection with the original
provider of the data is necessary in order to decode the data.
Preferably, the key is time coded so that a live connection to the
data source is required. The encoding may include public-key
encoding, in accordance with a preferred embodiment of the
invention. It should be noted that not all the data need be
encoded, it usually is only necessary to hide enough of the data so
that the remaining information is degraded beyond a point which
makes plain copying feasible. This type of encoding is also useful
for audio-visual data, for example, for controlling viewing of
pay-by-view movies in cable television systems.
[0134] In a preferred embodiment of the invention, a live
connection between the Java applet and the server is preferred to
reduce the chances of a "pirate" program disguising itself as a
client. Preferably, the client is required to identify itself using
a new code each time it runs. The server may maintain a list of all
the used codes. Thus, data can only be displayed once using a
particular code and additional displays required a new code.
Preferably, the server also provides multi-use codes which limit
the display of data to a small number of times. Alternatively or
additionally, only a small portion of the information, such as an
abstract, can be viewed without a proper code. Alternatively or
additionally, the server uses a code to authenticate clients. The
server sends a code to the client and the client is expected to
send back a second code which is a function of the first code. A
"pirate" program will probably not be able to respond with the
correct code, especially if different codes are used each time by
the server. It should be appreciated that only the codes need to be
transmitted, not all the data, so the required bandwidth is very
narrow.
[0135] By encoding the data using a cipher, intercepting the data
along the route between the server and the client is also made
difficult. Preferably, the Java applet is compiled in a manner to
make it difficult to reverse engineer.
[0136] In a preferred embodiment of the invention, the data is
displayed using graphical display functions rather than text based
display functions, so as to limit the ease of eavesdropping on the
data as it is displayed. Alternatively, the text is not displayed
in a serial order, as is common, but in a random fashion, such that
the display commands need to be analyzed in order to reconstruct
the correct order of the displayed text. It should be appreciated
that requiring a would-be infringer to store images rather than
text data increases the cost of infringement to a point where it
will usually not be practiced.
[0137] Alternatively or additionally, data is sent in a format
which is suitable only for display, such as a low resolution
graphical format. Printing such a display results in inferior
quality copies. One example is works of art, which are currently
transmitted at full quality. In a preferred embodiment of the
invention, only an inferior quality of the data will be sent,
suitable only for a particular display, unless a certain fee is
paid or advertisements viewed.
[0138] As might be appreciated, there are many data providers on
the Internet for which it would be desirable to protect their
copyrighted information. However, each data provider would then be
required to convert his data to allow for the new type of
presentation. In addition, many information providers use computer
programs which generate a WWW page in response to a request. A
change over might require the information provider to modify these
programs. In accordance with a preferred embodiment of the
invention, a conversion server, as described above performs the
conversion and/or the communication with the clients, on demand.
Preferably, the converter only encodes the copyrighted information
and not any associated advertisements. Thus, an information
provider sends the copyrighted information from a data source, in
its original form, to the conversion server and the conversion
server converts the data to a form which is accessible to the
(human) client, but not to the (computer) client. The conversion
server can then provide various services in a centralized manner,
including, customer payments and partitioning advertisements for
particular market sectors. In an alternative preferred embodiment
of the invention, the server is added on as a gateway to the data
source.
[0139] It should be appreciated that in many cases, the data which
is transmitted from the data source to the conversion server is
already in a format suitable for the client, such as HTML. The data
is preferably transmitted from the data source using an Internet
protocol, such as a WWW protocol.
[0140] In an exemplary embodiment of the present invention,
converter 38 is a general purpose computer with appropriate
software. Alternatively, converter 38 may be a dedicated computer
based on Java. As described above, converter 38 may also be
embodied as part of a server computer.
[0141] It should be appreciated that the present invention is not
limited by what has thus far been described. Rather, the scope of
the invention is described only by the claims which follow.
* * * * *
References