The present invention relates to computer systems and more particularly to a system for handling documents that contain a digital watermark.
The technology for inserting digital watermarks in documents and the technology for detecting and reading digital watermarks that are embedded in documents is well developed. Furthermore, methods and systems for linking to internet sites in response to physical objects that contain watermarks are known. For example see co-pending application Ser. No. 09/571,422 May 15, 2000 entitled “Methods and Systems for Controlling Computers or Linking to Internet Resources from Physical and Electronic Objects” the content of which is hereby incorporated herein by reference.
It is also noted that a system marketed by Digimarc Corporation under the trademark “Media-Bridge” includes a central computer which accepts and registers identification numbers and associated action strings, and software which reads a watermark containing an identification number. When a watermark is read, the data base is interrogated via the Internet to locate a previously registered action string, and a response is returned to the requesting software via the Internet.
In some situations, the turn around time between when a watermark is read and when a desired action occurs is very critical. For example, watermarks on a ticket for an event can be used to carry authentication data. The data carried by the watermark on the ticket can be compared to data registered on a server in order to authenticate the ticket. When a ticket is presented at an entry point for an event, the ticket must be authenticated very quickly. The present invention provides a system which can be used to very quickly authenticate documents such as tickets through a local area or a wide area network. The authentication is done without the use of communication via the Internet. Tickets may be sold at many different locations, hence, identification data is registered at a central site using the Internet. At a specified time, the registration data is downloaded to a computer data base at a local site where the tickets will be presented for entry to an event. At the time of the event, when the tickets are presented for authentication, the identification is done quickly for the local data base via a local area network (LAN). Data for tickets sold after the initial download can be downloaded as increments to the local data base.
In other situations, for security considerations, it is not desirable to store all the registration data in a single local data base. In one embodiment, the present invention provides a number of local computers which exchange data on a peer to peer basis. Thus the data can be compartmentalized for security reasons.
In still other situations, due to security and other considerations, it is desirable that all communication be over a local area or wide area network other than the Internet. The present invention provides a system that can operate on a local area network (LAN) or on a wide area network (WAN).
An overall system diagram of a first embodiment of the invention is illustrated in
Each ticket includes watermark data which is unique to the particular ticket. When a ticket is sold, the data in the watermark of the ticket is registered at server 102. The tickets can be printed at the time of sale and a watermark can be embedded in the ticket at that time, or tickets can be pre-printed and at the time a ticket is sold, the watermark in the ticket can be read and registered at server 102.
The tickets are authenticated when they are presented for entry to the event as follows: The watermark in the presented ticket is read. The data in the watermark is sent to watermark checking server 103 which checks to see if the particular ticket in question has been registered as having been sold.
It is noted that while as described herein the system is used to check tickets for events such as concerts or sporting events, the system can be used to authenticate any ticket, image or document that contains a watermark. Generally tickets are sold at many widely dispersed points, hence, entry of the data via internet is convenient. Furthermore selling tickets is a relatively time consuming operation, hence communication via the internet is acceptable even if it involves some slight delays. However, validating tickets when they are presented for entry to an event is a very time sensitive operation. Any delay is unacceptable and the validation must be made without delay. Due to the necessity for speed, the validation station is connected to the watermark checking server via an Ethernet LAN connection.
The system includes a central watermark registration server 102 that can be located anywhere and a watermark checking server 103 that is located near the place here tickets are presented for validation. The watermark registration server 102 includes a watermark registration program 102A and a database 102B. The watermark registration program 102A receives watermark registration information from an entry station when a ticket is sold. This information is generally (but not necessarily) provided to the watermark registration sever 102 via the internet. Thus, watermark registration server 102 collects and stores in a data base 102B, information which identifies the unique data in the watermarks on each of the tickets which is sold.
Information from the watermark registration server 102 is downloaded to a watermark checking server 103 at a designated time prior to when patrons are expected to present tickets for validation. The system includes a ticket validation station 104 which includes a watermark reading mechanism. When a ticket is presented for entry to an event, the watermark in the ticket is read by a conventional watermark reading program. The data in the watermark is checked against the data in the watermark checking server 103 to determine if the particular ticket is valid. If the data in the watermark of a ticket presented for entry is registered in the watermark checking server 103, an “action string of data” is returned to the watermark checking station. The action string can be command data that would open an entry gate 105. Alternatively it could be merely data that would be flashed on a screen to indicate that a particular ticket is valid.
The system can include an application program 210 which for example scans a ticket and opens a gate if the ticket is validated. The watermark on the ticket is read using conventional watermark reading program 211, and the data base 215 is interrogated to determine if the particular ticket contains a watermark which has been registered indicating that the ticket is valid. If the ticket has been registered as having been sold, a signal is sent to the application program 210 to take the appropriate action such as to open a gate.
It is noted that the user application program 210 and the watermark reader 211 are connected to the watermark checking server 103 via a high speed LAN connection. Thus, the communication involved with checking and authenticating a ticket proceeds at high speed with a minimum of delay.
The system can include a hit recording program 216 which keeps track of the number of tickets that have been presented for verification. This system can record a wide variety of statistics. For example it can analyze where tickets presented for verification have been sold and it can record the number of un-validated tickets presented.
A second embodiment of the invention is shown in
Each Department A to D has a watermark embedding and registration input 301A to 301D. These are conventional devices which embed particular watermark data in an image and which ten register the watermark with a registration server. In the example illustrated the servers are designated 302A to 302D. These servers could be physically separate computers or they could be independent servers operating on a single computer. Separate computers provide added security. Each department A to D also has an associated application program and watermark reader 303A to 303D. The watermark readers 303A to 303D check to see if the information read from the watermark in a particular image is registered on the associated server 302A to 302D.
In some situations, a department may desire to have a particular watermark registered on some other servers in addition to the server associated with the particular department. There is a connection between the servers designated 305 to 307 which allows exchange of registration information between the servers. Each registered watermark includes an indication of the particular servers on which the watermark should be registered. There is communication between the servers. When a particular watermark is registered, the user registering the watermark can indicate the particular servers on which the particular watermark should be registered. For example, in a situation where there are ten registration servers connected on a peer to peer basis, the user registering a watermark, might indicate that it should only be registered on the one server in that department, or he might designate nine servers and indicate that it should be register on only these nine of the ten servers, or he might indicate that it should be registered on all of the servers, etc.
A third embodiment of the invention is illustrated in
The contents of application Ser. No. 09/571,422 May 15, 2000 (now U.S. Pat. No. 6,947,571), entitled “Methods and Systems for Controlling Computers or Linking to Internet Resources from Physical and Electronic Objects” is incorporated herein by reference to provide details of some of the elements shown herein in block diagram form. While the invention has been shown and described with respect to a number of preferred embodiments, it should be understood that various other changes in format and detail can be made without departing from the spirit of the invention. The scope of the invention is limited only by the appended claims.
The present application is a continuation in part of application Ser. No. 9/571,422, filed May 15, 2000 (now U.S. Pat. No. 6,947,571), which is a CIP of each of the following applications; 1) Ser. No. 09/314,648, filed May 19, 1999 (now U.S. Pat. No. 6,681,028) 2) Ser. No. 09/342,688, filed Jun. 29, 1999 (now U.S. Pat. No. 6,650,761) 3) Ser. No. 09/342,689, filed Jun. 29, 1999 (now U.S. Pat. No. 6,311,214) 4) Ser. No. 09/342,971, filed Jun. 29, 1999 now abandoned 5) Ser. No. 09/343,101, filed Jun. 29, 1999 now abandoned 6) Ser. No. 09/343,104, filed Jun. 29, 1999 now abandoned 7) 60/141,468, filed Jun. 29, 1999 8) 60/151,586, filed Aug. 30, 1999 9) 60/158,015, filed Oct. 6, 1999 10) 60/163,332, filed Nov. 3, 1999 11) 60/164,619, filed Nov. 10, 1999 12) Ser. No. 09/531,076, filed Mar. 18, 2000 13) Ser. No. 09/543,125, filed Apr. 5, 2000 14) Ser. No. 09/547,664, filed Apr. 12, 2000, and 15) Ser. No. 09/552,998, filed Apr. 19, 2000, now abandoned
Number | Name | Date | Kind |
---|---|---|---|
4947028 | Gorog | Aug 1990 | A |
5053956 | Donald et al. | Oct 1991 | A |
5262860 | Fitzpatrick et al. | Nov 1993 | A |
5288976 | Citron et al. | Feb 1994 | A |
5385371 | Izawa | Jan 1995 | A |
5463209 | Figh et al. | Oct 1995 | A |
5495581 | Tsai | Feb 1996 | A |
5496071 | Walsh | Mar 1996 | A |
5530852 | Meske, Jr. et al. | Jun 1996 | A |
5613004 | Cooperman et al. | Mar 1997 | A |
5640193 | Wellner | Jun 1997 | A |
5659164 | Schmid et al. | Aug 1997 | A |
5673316 | Auerbach et al. | Sep 1997 | A |
5721788 | Powell et al. | Feb 1998 | A |
5742845 | Wagner | Apr 1998 | A |
5761606 | Wolzien | Jun 1998 | A |
5761686 | Bloomberg | Jun 1998 | A |
5774664 | Hidary et al. | Jun 1998 | A |
5774666 | Portuesi | Jun 1998 | A |
5778102 | Sandford, II et al. | Jul 1998 | A |
5804803 | Cragun et al. | Sep 1998 | A |
5809317 | Kogan et al. | Sep 1998 | A |
5818441 | Throckmorton et al. | Oct 1998 | A |
5822432 | Moskowitz et al. | Oct 1998 | A |
5838458 | Tsai | Nov 1998 | A |
5848413 | Wolff | Dec 1998 | A |
5857038 | Owada et al. | Jan 1999 | A |
5872589 | Morales | Feb 1999 | A |
5892900 | Ginter et al. | Apr 1999 | A |
5900608 | Iida | May 1999 | A |
5903729 | Reber et al. | May 1999 | A |
5905248 | Russell et al. | May 1999 | A |
5905800 | Moskowitz et al. | May 1999 | A |
5913210 | Call | Jun 1999 | A |
5915027 | Cox et al. | Jun 1999 | A |
5918214 | Perkowski | Jun 1999 | A |
5932863 | Rathus et al. | Aug 1999 | A |
5933829 | Durst et al. | Aug 1999 | A |
5938726 | Reber et al. | Aug 1999 | A |
5940595 | Reber et al. | Aug 1999 | A |
5978773 | Hudetz et al. | Nov 1999 | A |
5984366 | Priddy | Nov 1999 | A |
5986651 | Reber et al. | Nov 1999 | A |
6012102 | Shachar | Jan 2000 | A |
6052486 | Knowlton et al. | Apr 2000 | A |
6081827 | Reber et al. | Jun 2000 | A |
6098106 | Philyaw et al. | Aug 2000 | A |
6107932 | Walker et al. | Aug 2000 | A |
6108656 | Durst et al. | Aug 2000 | A |
6148331 | Parry | Nov 2000 | A |
6185312 | Nakamura et al. | Feb 2001 | B1 |
6216227 | Goldstein et al. | Apr 2001 | B1 |
6311214 | Rhoads | Oct 2001 | B1 |
6345104 | Rhoads | Feb 2002 | B1 |
20010018660 | Sehr | Aug 2001 | A1 |
20020078357 | Bruckers et al. | Jun 2002 | A1 |
Number | Date | Country |
---|---|---|
0493091 | Jul 1992 | EP |
WO9514289 | May 1995 | WO |
WO9520291 | Jul 1995 | WO |
WO9627259 | Sep 1996 | WO |
WO9636163 | Nov 1996 | WO |
WO9702522 | Jan 1997 | WO |
WO9743736 | Nov 1997 | WO |
WO9803923 | Jan 1998 | WO |
WO9851036 | Nov 1998 | WO |
WO9957623 | Nov 1999 | WO |
WO 0197175 | Dec 2001 | WO |
WO 0203328 | Jan 2002 | WO |
Number | Date | Country | |
---|---|---|---|
20020112165 A1 | Aug 2002 | US |
Number | Date | Country | |
---|---|---|---|
60164619 | Nov 1999 | US | |
60163332 | Nov 1999 | US | |
60158015 | Oct 1999 | US | |
60151586 | Aug 1999 | US | |
60141468 | Jun 1999 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 09571422 | May 2000 | US |
Child | 10113099 | US | |
Parent | 09552998 | Apr 2000 | US |
Child | 09571422 | US | |
Parent | 09547664 | Apr 2000 | US |
Child | 09552998 | US | |
Parent | 09543125 | Apr 2000 | US |
Child | 09547664 | US | |
Parent | 09531076 | Mar 2000 | US |
Child | 09543125 | US | |
Parent | 09342688 | Jun 1999 | US |
Child | 09531076 | US | |
Parent | 09342689 | Jun 1999 | US |
Child | 09342688 | US | |
Parent | 09342971 | Jun 1999 | US |
Child | 09342689 | US | |
Parent | 09343101 | Jun 1999 | US |
Child | 09342971 | US | |
Parent | 09343104 | Jun 1999 | US |
Child | 09343101 | US | |
Parent | 09314648 | May 1999 | US |
Child | 09343104 | US |