JP4294355B2 - Ticket issuance management method and system, and information processing apparatus - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a ticket issue management method and system, and an information processing apparatus.
[0002]
[Prior art]
In the realization of an electronic government, for example, various application procedures from the public to the government are digitized. On the other hand, various certificates and tickets issued by the government have been provided only by means of receiving mail or distribution at the counter in order to prevent tampering and unauthorized use. For this reason, various techniques have been proposed in order to enable validity confirmation of various certificates and tickets in a ubiquitous environment.
For example, the verification of the authenticity and validity of the printed material is performed offline (see Patent Document 1), the printed material printed by the applicant seeking certification is used as an official certificate (refer to Patent Document 2), or an individual A database that associates and manages information that can identify the certificate and certificate data, a technique that searches certificate data based on key information (see Patent Document 3), and the like have been proposed.
[0003]
[Patent Document 1]
JP 2001-134672 A
[0004]
[Patent Document 2]
JP 2001-357154 A
[0005]
[Patent Document 3]
JP 2002-279099 A
[0006]
[Problems to be solved by the invention]
However, this conventional technique has the following problems. First, an electronic sheet incorporating a non-contact electronically readable / writable data carrier mechanism, or non-copyable paper (a special character or pattern that appears as a copy when the copy is taken with a copier) Need to be used as a print recording medium. In other words, the use of special printing devices and papers is of considerable concern for deterioration in operational efficiency and cost and an increase in the burden of hardware installation on the user side.
Therefore, a method for issuing a certificate or the like that can economically and efficiently verify the validity (whether or not tampering has occurred) has not been established.
Therefore, the present invention has been made paying attention to such a problem, and an object thereof is to provide a ticket issuance management method and system, and an information processing apparatus, which can execute validity confirmation economically and efficiently.
[0007]
[Means for Solving the Problems]
  The ticket issuance management method of the present invention that achieves the above object is a method in which ticket issuance management is performed by an information processing apparatus, wherein the first information processing apparatus that generates ticket mount data has a plurality of secrets stored in a storage device. A mount issuer authentication database having a key and storing authentication information of a second information processing apparatus that issues a ticket; and a mount management database storing a usage status of the ticket mount; and the second information Receiving a ticket mount issuance request from a processing device; verifying authentication data included in the mount issuance request against the mount issuance destination authentication database and authenticating the second information processing device; If the second information processing apparatus is authenticated, the information specific to the mount is transferred to the first secret key according to the number of mount issuance requests included in the mount issuance request. A process of generating encrypted first encrypted data, encoding the first encrypted data, and generating first data of a single color dot or pixel coloring pattern corresponding to the code; Is encrypted with a second secret key to create second encrypted data, the second encrypted data is encoded, and a second pattern of a single color dot or pixel corresponding to this code is applied. The process of generating data is repeated until the predetermined area of the mount is filled with the data of the single-color dot or pixel coating pattern, etc., and the mount status is generated for each mount data, and the mount management is performed for each mount data. A step of registering in a database, and a step of transmitting the mount data to the second information processing device, wherein the second information processing device A ticket issuance destination authentication database that stores authentication information of a third information processing apparatus that performs printing, and a ticket management database that stores the use status of a ticket, and a ticket issuance request from the third information processing apparatus , Verifying authentication data included in the ticket issuance request with the ticket issuance destination authentication database, authenticating the third information processing apparatus, and authenticating the third information processing apparatus If generated, the step of generating ticket data according to the number of ticket issuance requests included in the ticket issuance request, the step of registering the issuance status of each ticket data in the ticket management database, and the ticket data The mount comprising data of a single color dot or pixel coating pattern Generating an electronic ticket by combining with the data; executing a request for updating a usage status of the mount data constituting the electronic ticket to the mount management database; and A step of transmitting to the information processing device, wherein the third information processing device receives an electronic ticket from the second information processing device, and coloring of single-color dots or pixels constituting the mount data Encoding the individual information of the electronic ticket indicating the correlation between the pattern data and the print area data overwritten on the pattern, and combining the encoded individual information into the electronic ticket and printing A step of outputting to the apparatus, and a requirement to update the usage status of the electronic ticket with respect to the ticket management database. And a step of executionAnd a fourth information processing device that accepts use of the printed matter of the electronic ticket reads the encoded individual information indicating the correlation between the mount data and the data of the print area on the printed matter; Performing image reading of the printed matter, recognizing individual information indicating a correlation between the mount data and the data of the print area on the printed matter, determining consistency between the individual information, As a result of the determination, if consistency is obtained between the individual information, it is recognized that the falsification has not been performed, and a step of outputting the fact to the output interface is executed.It is characterized by that.
[0008]
  The ticket issuance management system according to the present invention includes a mount issuer authentication database that stores a plurality of secret keys in a storage device and stores authentication information of a second information processing apparatus that issues a ticket, and the usage status of the ticket mount. Means for receiving a request for issuing a ticket mount from the second information processing apparatus, and checking the authentication data included in the mount issue request database against the mount issuer authentication database; And means for authenticating the second information processing apparatus, and if the second information processing apparatus is authenticated, the individual information of the mount is obtained according to the number of mount issuance requests included in the mount issuance request. First encrypted data encrypted with the first secret key is created, the first encrypted data is coded, and single color dots or pixels corresponding to the code are coded. A process for generating the first data of the turn, and encrypting the first encrypted data with a second secret key to create second encrypted data, encoding the second encrypted data, The processing for generating the second data of the corresponding single color dot or pixel coloring pattern is repeated until the predetermined area of the mount is filled with the data of the single color dot or pixel coloring pattern to generate the mount data. A first information processing apparatus comprising: means; means for registering the issuance status of each mount data in the mount management database; and means for transmitting the mount data to the second information processing apparatus; ticket printing; Access to a ticket issuer authentication database that stores authentication information of the third information processing apparatus that performs authentication, and a ticket management database that stores the usage status of tickets. Means for receiving a ticket issuance request from the third information processing apparatus, and checking the authentication data included in the ticket issuance request against the ticket issuance destination authentication database, so that the third information processing apparatus And a means for generating ticket data according to the number of ticket issuance requests included in the ticket issuance request when the third information processing apparatus is authenticated, and for each ticket data Means for registering the situation in the ticket management database; means for synthesizing the ticket data with the mount data composed of data of a single color dot or pixel painting pattern; and the mount management Means for executing a request to update the usage status of the mount data constituting the electronic ticket to the database; A second information processing apparatus comprising: means for transmitting the electronic ticket to the third information processing apparatus; means for receiving the electronic ticket from the second information processing apparatus; and monochrome dots constituting the mount data Alternatively, means for encoding the individual information of the electronic ticket indicating the correlation between the data of the pixel painting pattern and the data of the print area overwritten on the pattern, and the encoded individual information as the electronic ticket A third information processing apparatus comprising: means for combining and outputting to the printing apparatus; and means for executing a request for updating the usage status of the electronic ticket with respect to the ticket management database; Coded,Shows the correlation between the mount data and the print area dataMeans for reading the individual information and reading the image of the printed matter,, Showing the correlation between the mount data and the print area dataA means for recognizing individual information; a means for determining consistency between the individual information; and if the result of the determination indicates that consistency is obtained between the individual information, it recognizes that tampering has not been performed, and And a fourth information processing apparatus including means for outputting to the output interface.
[0009]
  The information processing apparatus according to the present invention also includes a mount issuance destination authentication database that stores a plurality of secret keys in the storage device and stores authentication information of a second information processing apparatus that issues a ticket, and stores the usage status of the ticket mount. A means for receiving a ticket mount issuance request from the second information processing apparatus, and verifying authentication data included in the mount issuance request database against the mount issuance destination authentication database. The means for authenticating the second information processing apparatus, and if the second information processing apparatus is authenticated, the information specific to the mount is changed according to the number of mount issuance requests included in the mount issuance request. First encrypted data encrypted with one secret key is created, the first encrypted data is encoded, and the first pattern of a single color dot or pixel corresponding pattern corresponding to the code is generated. And generating the second encrypted data by encrypting the first encrypted data with the second secret key, encoding the second encrypted data, and the monochrome dot corresponding to the code Alternatively, the processing for generating the second data of the pixel coating pattern is repeated until the predetermined area of the mount is filled with the single color dots or the pixel coating pattern data, and means for generating the mount data; And a means for registering the issue status of each mount data in the mount management database, and a means for transmitting the mount data to the second information processing apparatus. This information processing apparatus corresponds to the first information processing apparatus in claim 1 of the present application.
[0010]
  Further, the information processing apparatus of the present invention is accessible to a ticket issuer authentication database that stores authentication information of a third information processing apparatus that performs ticket printing, and a ticket management database that stores the usage status of tickets. Means for receiving a ticket issuance request from the third information processing apparatus; and means for authenticating the third information processing apparatus by checking authentication data included in the ticket issuance request against the ticket issuance destination authentication database. And, if the third information processing apparatus is authenticated, means for generating ticket data in accordance with the number of ticket issuance requests included in the ticket issuance request, and the ticket management for the issuance status of each ticket data The means for registering in the database and the ticket data include data of a single color dot or pixel pattern. A request for updating the usage status of the mount data constituting the electronic ticket is executed to the mount management database for storing the usage status of the ticket mount and the means for generating the electronic ticket by combining with the mount data composed of Means for transmitting the electronic ticket to the third information processing apparatus;It is characterized by providing.This information processing apparatus corresponds to the second information processing apparatus according to claim 1 of the present application.
[0011]
  The information processing apparatus according to the present invention also includes means for receiving electronic ticket data from the second information processing apparatus, data of a single color dot or pixel pattern constituting the electronic ticket mount data, and the pattern. Means for encoding the individual information of the electronic ticket indicating the correlation with the print area data to be overwritten, means for synthesizing the encoded individual information into the electronic ticket and outputting the same to the printing device; Means for executing a request to update the usage status of the electronic ticket with respect to the ticket management database storing the usage status of the electronic ticket;It is characterized by providing.This information processing apparatus corresponds to the third information processing apparatus in claim 1 of the present application.
[0012]
  Also, the information processing apparatus of the present invention has the electronic ticket individual information indicating the correlation between the data of the single color dot or pixel pattern constituting the mount data and the data of the print area overwritten on the pattern. A means for reading the coded individual information from the printed electronic ticket printed matter, and reading the image of the printed matter on the printed matter., Showing the correlation between the mount data and the print area dataA means for recognizing individual information; a means for determining consistency between the individual information; and if the result of the determination indicates that consistency is obtained between the individual information, it recognizes that tampering has not been performed, and And means for outputting to an output interface. This information processing apparatus corresponds to the fourth information processing apparatus in claim 4 of the present application.
[0014]
Note that the above electronic tickets can be applied to various tickets for which the necessity of issue management is recognized, such as valuable tickets and various certificates, in addition to entrance tickets for various events.
[0015]
In addition, the problems disclosed by the present application and the solutions thereof will be clarified by the embodiments of the present invention and the drawings.
[0016]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the present invention will be described below in detail with reference to the drawings. FIG. 1 is a diagram showing a conceptual model of a ticket issue management method in the present embodiment. In this embodiment, digitized securities such as various certificates and tickets issued by government offices and companies can be printed and distributed in a ubiquitous environment while tampering and unauthorized use are established and effectiveness is established. And Therefore, each of the mounts constituting the certificate, ticket, etc. (hereinafter referred to as “ticket”) is registered and managed with distinctiveness. The ticket can be applied to various certificates for which the necessity of issue management is recognized, such as an entrance ticket for events as well as various certificates.
[0017]
An electronic mount issuance management apparatus (hereinafter referred to as a mount management apparatus 100) as a first information processing apparatus that performs mount issuance management can be regarded as a system of a mount provider that provides mounts to, for example, the government offices and companies. The mount management apparatus 100 authenticates a ticket issue management apparatus (hereinafter referred to as a ticket management apparatus 200) as a second information processing apparatus that issues a ticket, and generates and distributes mount data.
[0018]
Therefore, an issuer authentication database 101 (mounting issuer authentication database) storing authentication information of the ticket management apparatus 200 and an electronic mount management database 102 (mounting management database) for storing and managing the usage status of ticket mounts are provided. I have. Alternatively, it can be accessed via a network. Then, in response to a ticket mount issue request received from the ticket management apparatus 200, an electronic mount issue program 103 that generates and distributes the required number of mount data, and the issue status of each mount data is indicated in the electronic mount management database. And an electronic mount state update program 104 registered in 102.
[0019]
Such a mount management device 100 stores the programs 103 and 104 in an appropriate storage device, and the processing devices issue the mount issuing process by reading them based on an OS (Operating System). In addition, the mount management apparatus 100 is connected to the ticket management apparatus 200, the ticket reception apparatus 400, which will be described later, the ticket verification apparatus 500, etc. via the network 600, and executes various data output. Naturally, the information processing apparatus includes an output interface for receiving information and an input interface for receiving selections and instructions from the operator.
[0020]
In addition, a table (not shown) that defines the attribute of the mount data to be generated for each ticket management device 200 is referred to, and the mount data corresponding to the corresponding ticket management device 200 is referred to when generating the mount data. You can also specify the generated contents.
[0021]
On the other hand, the ticket management apparatus 200 displays an issue destination authentication database 201 (ticket issue destination authentication database) in which authentication information of a user apparatus 300 as a third information processing apparatus that performs ticket printing is stored, and a ticket usage status. And a ticket management database 202 to be stored. Alternatively, it can be accessed via a network. Then, in response to a ticket issuance request received from the user device 300, an issuer confirmation program 203 for making a mount issuance request to the mount management device 100, and a required number corresponding to the ticket issuance request from the user device 300 A ticket issuance program 204 for generating and distributing the electronic ticket 50 and a ticket status updating program 205 for registering the issuance / usage status of the electronic ticket in the ticket management database 202 for each electronic ticket. Such a ticket management apparatus 200 is naturally provided with means and functions that should be provided as an information processing apparatus, like the mount management apparatus 100.
[0022]
On the other hand, the user device 300 is a device that allows a ticket user to actually print an electronic ticket on a print medium and obtain it. The user device 300 makes a ticket issuance request to the ticket management device 200, and receives a user confirmation program 301 responsible for receiving the electronic ticket 50 (the ticket data embedded in the mount data), and the electronic ticket 50. A ticket printing program 302 that outputs to a printer device 303 (printing device) and generates a printed ticket (hereinafter, printed matter 90), and the printer device 303 are provided. Such a user device 300 is naturally provided with means and functions that should be provided as an information processing device, similar to the mount management device 100 and the like.
[0023]
The printed matter 90 is carried to the place of use by the ticket user. Then, the effectiveness of the printed matter 90 is confirmed. The main role of this validity check is the ticket reception device 400 as the fourth information processing device. The ticket reception apparatus 400 recognizes individual information on the printed material by reading an image of the printed material 90, an image scanner device 401 that reads the image of the printed material 90, a capture program 402 that controls the image scanner device 401, and the image of the printed material 90. And an electronic mount validity confirmation program 403 for confirming validity.
[0024]
Further, a verification data transfer program 404 for transferring the result of the validity check to the ticket verification apparatus 500 that collects the validity check processing for each printed matter 90 can be provided. The ticket verification apparatus 500 includes an image scanner apparatus 501, a capture program 502, an electronic mount validity confirmation program 503, and the like, similar to the ticket reception apparatus 400. It is also possible to check the validity again based on the result of the validity check transferred from the ticket receiving apparatus 400 and the printed matter 90 (for example, a stub after the ticket is received). The ticket status update request program 504 requests the ticket management database 202 to update the status where the printed matter 90, that is, the electronic ticket 50 is used.
[0025]
In FIG. 2, a configuration example in which the mount management device 100, the ticket management device 200, the user device 300, the ticket reception device 400, and the ticket verification device 500 are collectively regarded as one system (ticket issue management system) 10. Is shown. The system 10 includes a memory 11 that stores the programs 103, 104, 203, 204, 205, 301, 302, 402, 403, 404, 502, 503, and 504, and an operation that reads and executes the programs. And a CPU 12 as a device.
[0026]
Also, an I / O control unit 13 responsible for data input / output control, a user operation input / output unit 14 as an input / output interface that receives data from a user and outputs data, and communication as a network adapter for data communication control A network connection unit 15 is provided. In addition, the printer device 303 and the image scanner devices 401 and 501 are also provided.
[0027]
Further, the electronic mount management database 102, the ticket management database 202, and the issue destination authentication databases 101 and 201 are provided in a storage device such as the hard disk 16. Such a system 10 can exchange authentication information with, for example, an external certificate authority 150 through the communication network 600.
[0028]
As described above, the first to fourth information processing apparatuses are integrally configured as the system 10. However, as described with reference to FIG. 1, each information processing apparatus is configured independently, and the network (bus wiring Etc.) can be assumed from the standpoint of operational efficiency.
Next, an example of the data structure of each database will be described. FIG. 3 shows an example of the data structure of the issuer authentication database. The issuer authentication databases 101 and 201 store authentication information for the ticket management apparatus 200 when used by the mount management apparatus 100. When the ticket management apparatus 200 uses them, the authentication of the user apparatus 300 is performed. The information for this is stored.
[0029]
In any case, an issue destination authentication record 55 is generated for each “issue destination”. The record 55 uses the issue destination ID 56 as key information, and is associated with an authentication password 57 and a receivable request code 58 describing a content code receivable for a mount or ticket issuance request.
[0030]
FIG. 4 shows an example of the data structure of the electronic mount management database. In the electronic mount management database 102, an electronic mount management record 60 is set for each generated mount. The record 60 includes an electronic mount ID column 1 for storing the ID of the mount data, a mount issue time column 62 for storing the issue time, a mount issue signature data column 63 for storing the electronic signature of the mount management apparatus 100, and the mount data. Valid period data column 64 in which the valid period of the card is stored, usage identification data column 65 in which the usage of the mount is stored, encryption key column 66 in which the encryption key is stored, and electronic mount issue destination in which the issuer ID of the mount is stored It includes an ID column 67 and an electronic mount issue verified flag column 68 that indicates whether or not a ticket is issued using the mount data in the ticket management apparatus 200.
[0031]
FIG. 5 shows an example of the data structure of the ticket management database. In the ticket management database 202, a ticket management record 70 is generated for each issued ticket. The record 70 includes a ticket issue time column 71, a ticket content data column 72, a ticket ID column 73, a ticket issue signature data column 74, a ticket user ID column 75, an electronic mount ID column 76, an electronic mount pattern data column 77, a ticket. It is composed of an issue verified flag column 78, a ticket validity period column 79, and a ticket use verified data column 80.
[0032]
Next, the printed matter 90 that is output when the electronic ticket 50 is printed by the printer device 303 of the user device 300 will be described. The printed matter 90 is based on an appropriate print medium (for example, paper, resin, or other printable material) on which the mount data issued by the mount management device 100 is printed. The mount data becomes information constituting the electronic mount pattern data print area 91. The area 91 includes a ticket content data print area 92, a ticket issue signature data print area 93, a ticket valid period print area 94, and a used check entry area 95.
[0033]
The ticket content data print area 92 and the ticket valid period print area 94 are areas for describing information that can be directly read by humans, such as character information. On the other hand, the ticket issue signature print data area 93 is an area for writing code information. Code information refers to information that can be read using an information processing apparatus having a reader function or the like, such as a bar code or a two-dimensional code.
[0034]
The two-dimensional code is assumed to be a stack type in which barcodes are stacked and a matrix type in which cells of the same size are arranged vertically and horizontally in black and white, but other two-dimensional barcodes and information similar to that are used. It is also possible to apply a method of recording Instead of the area for writing the code information, a storage medium such as an IC chip or a magnetic tape may be provided on the mount and the code information may be stored in this storage medium. Further, the present embodiment includes both a storage medium and an area for writing code information.
[0035]
The areas 92 and 94 for writing the character information and the area 93 for writing the code information are each divided into two areas. In one area, data such as an electronic mount ID for managing the mount, a mount issuance time, and a signature at the time of the mount is written in the mount management apparatus 100. In the other area, the feature amount (individual information) of the (validity) proof content in the printed matter 90, the time when the proof content was overwritten by the printing of the ticket content data, the signature at the time of overwriting, etc. Data is described in the ticket management device 200.
[0036]
FIG. 7 shows the ledger pattern image when the individual information data 700 such as the electronic mount ID, the mount issue time, and the signature data at the time of the mount is encoded and written in the area 91 in the mount management apparatus 100. It is. When a partial area 710 of the area 92 is enlarged, there are a pixel 720 displayed as a black dot and a pixel 730 expressed as a blank. For example, if a character is represented by 32 bits, this data is represented by 16 digits in binary, so it is 1 in 16 dots of black and white (0 represents white in binary and 1 represents black). Can represent characters.
[0037]
Since the data 700 is composed of a plurality of character strings, the area 93 is filled with a pattern (electronic mount pattern) shown in 710 when coded by the above method. Here, an example in which the data 700 is simply encoded has been described. However, from the viewpoint of preventing forgery of data, it is desirable that the data 700 is encoded and then encoded. Also, it is desirable to repeat the data in consideration of reading errors.
[0038]
FIG. 8 is an explanatory diagram of a pattern in consideration of reading by an information processing apparatus such as a reader. In the method of FIG. 7 described above, it is determined that one character is expressed by 16 dots. If the character string is the same, the same pattern is drawn. However, there is a possibility that characters and character breaks cannot be distinguished, and it is considered unsuitable for applications such as reading original data from a pattern.
[0039]
Therefore, in FIG. 8, the filled area is divided into a 5 × 5 matrix 800, and the upper left pixel (810, 830, 840, 850) of the matrix is always filled as a reference point. The 16 dots correspond to a 4 × 4 matrix. In this case, the information on the character string is distributed randomly like the pixels 820, 860, 870, and 880. However, since the pixels 810, 830, 840, and 850 are regularly arranged, Is easily found.
However, the present invention is not limited to the method shown in FIG. 8, as various patterns have been proposed for the two-dimensional code. In addition, it is possible to simply paint at predetermined intervals, and store the relationship between the overwritten character (other data), the point to be painted, and the area including the dot. .
[0040]
On the other hand, FIG. 9 is an explanatory diagram showing a method of filling a region with a coded pattern. When the content of the data 910 is encoded and the area 93 is filled, the same pattern is repeatedly used. For example, if it is found that the pattern 920 and the pattern 930 are the same, even if a part of the pattern 920 is erased by the overwrite character, the overwrite character can be erased using the pattern 930. As a method for preventing this, several kinds of secret keys are prepared for encrypting the contents 910, the encrypted data 1 encrypted with the secret key 1 (950) is created, and the pattern encoded thereby is stored in the area 920. Draw. Further, encrypted data 2 is generated by encrypting the encrypted data 1 with the secret key 2 (960), and a pattern obtained by encoding the encrypted data 2 is drawn in the area 930. By repeating such processing, the region 93 is filled. In this case, the pattern in which the area 920 is filled is different from the pattern in which the area 930 is filled.
[0041]
10 and 11 are flowcharts relating to a method for generating a pattern for filling the region 93, and a pattern different from those in FIGS. 7, 8, and 9 is generated. FIG. 12 shows an example of a pattern created by this processing. FIG. 13 is a processing flow for overwriting individual information on the mount pattern.
[0042]
By the way, a basic pattern generation method will be briefly described before pattern customization by the processing of FIG. For example, as the basic pattern, a pattern in which pixels in an area are separately painted with three colors (color 1, color 2, and color 3) is created. At this time, the pixels adjacent to each other at the top, bottom, left, and right are painted differently. The simplest way of painting is to repeatedly paint color 1, color 2 and color 3 in order, and the top row is painted separately in a horizontal row.
[0043]
Next, with respect to the next lower row, the color 2, color 3, and color 1 are repeatedly painted with color 2 as the leftmost end. Further, the lower row is repeatedly painted in the order of color 3, color 1, and color 2 with color 3 as the leftmost end. If this is repeated up to the bottom row, the region 93 can be filled with three colors. This is called a basic pattern. Note that this color may be a primary color used in the printer device 303. For example, three colors may be selected from cyan, magenta, yellow, and black, or four colors may be used without being limited to three colors.
[0044]
Next, a process of embedding individual information such as an electronic mount ID in the basic pattern is performed. This process is shown in FIG. In step 1300, the mount management apparatus 100 sets an initial value for scanning the area 93. For example, the upper left pixel is set as the initial value. In step 1310, the pixel color is examined for the pixel located to the left of the target pixel and the pixel located directly above. If the colors of the two pixels are the same, the process proceeds to step 1315; otherwise, the process proceeds to step 1350.
[0045]
In step 1315, it is determined whether information is embedded in the pixel. However, the information here is a part of the individual information. For example, the electronic mount ID is “11”, and this mount ID is embedded in the image. By the way, “11” is expressed in decimal notation, but when expressed in binary, it becomes “1011”. Therefore, in order to embed the value “11” in a pixel, at least four pixels are necessary. If “1”, “0”, “1”, and “1” can be embedded in the four pixels, respectively, It can be said that the individual ID is embedded.
[0046]
Here, the process returns to step 1315 to check whether the value to be embedded in the target pixel is “1” or “0”. If it is “1”, the process proceeds to step 1320. If it is “0”, the process proceeds to step 1350. In step 1320, the color of the pixel to the left of the target pixel and the color of the pixel immediately above are checked (of course, since the colors of the two pixels are the same, it is sufficient to check one of them). If it is color 3, the target pixel is painted with color 2 in step 1325.
[0047]
If it is not color 3 but color 1, it is determined in step 1330, and the target pixel is painted in color 3 in step 1335. If it is neither color 3 nor color 1, it is necessarily color 2, so the target pixel is painted with color 1 in step 1340. Note that step 1350 is a process related to the color determination of pixels in which information cannot be embedded, and will be described with reference to FIG.
[0048]
When the color of the target pixel is determined, in step 1360, one pixel to be scanned is moved to the right. However, if it is the rightmost end, in step 1365, the process proceeds to step 1370, and otherwise, the process returns to step 1305. Similarly, in step 1370, the pixel to be scanned is moved to the lower stage by one column, and if it is the lowermost stage in step 1375, the process is terminated. Otherwise, the process returns to step 1305 and the process is continued.
[0049]
FIG. 11 is a flowchart showing details of step 1350. In step 1410, the fill color of the target pixel is set to color 1. In step 1415, the colors are examined for the pixel to the left and directly above the pixel of interest and both are not color 1 (ie, both are color 2, both are color 3, one is color 2, and the other is color 3). ) The target pixel is painted with color 1. If at least one is color 1 in step 1415, the fill color is set to color 2 in step 1425.
[0050]
Then, in step 1430, the color is checked in the same manner as described above. If the pixel on the left and right above the target pixel is not color 2, the target pixel is painted in color 2 in step 1435. If color 2 is included in step 1430, either the left side or the pixel immediately above the target pixel is color 1, and the rest is color 2, so in step 1440, the target pixel is filled with color 3. . By performing such processing, it is possible to embed individual information in the basic pattern while following the rule that adjacent pixels are always painted in different colors.
[0051]
The upper part of FIG. 12 is an example of the mount pattern thus created. The lower row shows an example in which the character “u” is overwritten on the mount, and the digest information of “u” is embedded in the mount.
In the upper part, the pixel 1510 in the area 1500 is painted in color 1, the pixel 1520 is painted in color 2, and the pixel 1530 is painted in color 3, and adjacent pixels are painted in different colors. In the lower diagram, the pixel 1560 is a portion where characters overlap. The lower part is an example in which the digest information of the character “U” is embedded in the portion painted in color 1 in the upper part. A pixel 1570 in which color 1 is left as it is and a fourth color 4 different from the three colors 4 Results in a pixel 1580 filled with.
[0052]
FIG. 13 shows a flow of processing for embedding information in the mount. In step 1600, the mount data is read and the characters of the individual data are overwritten on the mount. At this time, a pixel that overlaps the character such as the pixel 1560 is painted with the color of the character.
[0053]
In step 1620, for example, the upper left pixel of the region is set as an initial value, and in step 1640, it is determined whether or not the target pixel is color 1 (here, color 1 is expressed as blank). If the color is 1, the individual data to be embedded is embedded by the same method as described in the explanation of FIG. That is, in step 1650, if the embedded value is “0”, the painted color is left as it is, and if the embedded value is “1”, the painted color is set to color 4.
[0054]
If the color of the target pixel is determined, in step 1660, only one pixel to be scanned is moved to the right. However, if it is the rightmost end, the process proceeds to Step 1680 in Step 1670, and otherwise returns to Step 1630. Similarly, in step 1680, the pixel to be scanned is moved to the lower stage by one column. If it is the lowermost stage in step 1690, the process ends. If not, the process returns to step 1630 to continue the process.
[0055]
The communication network 600 appropriately connecting the mount management device 100, the ticket issuance management method, the user device 300, the ticket reception device 400, and the ticket verification device 500 is not limited to a dedicated line or the Internet, but is also a WAN (Wide Area). Network), LAN, power line network, wireless network, public line network, mobile phone network, EDI dedicated line, and other various networks can be employed. Further, if a virtual private network technology such as VPN is used, communication with improved security is established when the Internet is adopted.
[0056]
Subsequently, a specific processing procedure of the ticket issue management method of the present embodiment will be described below. FIG. 14 is a diagram showing a flow of the mount issuing procedure in the present embodiment. The ticket management device 200 issues a ticket electronic mount issuance request to the mount management device 100 (s2000). This mount issuance request includes at least the authentication data (ID, password, etc.) of the ticket management apparatus 200 and information on the issuance request number.
[0057]
The issuer confirmation program 203 in the ticket management apparatus 200 generates such an electronic mount issue request and transmits it to the mount management apparatus 100. It is assumed that the trigger of the request is based on a ticket issue request from the user device 300. Alternatively, it is conceivable that a predetermined number of tickets are simply prepared in advance according to events such as events.
[0058]
The mount management apparatus 100 receives the mount issue request (s2001). Then, the authentication data included in the received request is read and collated with the issuer authentication database 101 to authenticate the ticket management apparatus 200.
[0059]
If the ticket management apparatus 200 is authenticated, mount data is generated according to the number of mount issuance requests included in the mount issuance request (s2002). For this reason, the electronic mount issuing program 103 first generates a mount ID. For example, if the board ID is a character string obtained by adding a request for issuing the board, the application identification data, and a 10-digit random number, it becomes difficult to estimate the board ID. Also, the uniqueness of the mount ID can be maintained.
[0060]
If the mount ID is generated, mount data is created next. Further, the ticket content data print area 91, the ticket issue signature data print area 93, the ticket valid period print area 94, the used check entry area 95, etc. described in FIG. 6 are secured. If the electronic mount is generated, it is registered in the electronic mount management database 102 and the mount data is transmitted to the ticket management apparatus 200.
[0061]
In generating the mount data, a table in which the attribute of the mount to be generated is determined for each ticket management apparatus 200 may be referred to, and the generation contents of the mount data may be specified according to the corresponding ticket management apparatus 200.
[0062]
On the other hand, the ticket management apparatus 200 receives the electronic mount data transmitted from the mount management apparatus 100 and temporarily stores it in an appropriate storage device (s2003). The mount issuance may be executed for each ticket request. Hereinafter, a ticket issuing procedure will be described with reference to FIG.
[0063]
As described above, it is assumed that the electronic mount issue request is triggered by reception of the ticket issue request from the user device 300 (s2004). Upon receiving the ticket issue request, the ticket management device 200 compares the authentication data of the user device 300 included therein with the issue destination authentication database 201 to authenticate the user device 300 (s2005).
[0064]
If the user device 300 is authenticated, ticket data is generated according to the number of ticket issuance requests included in the ticket issuance request (s2006). The ticket data is overwritten with the pattern (pattern) in the electronic mount data, that is, print information such as “event name”, “location, date and time” to be synthesized. The generated ticket data, that is, the electronic ticket 50 is registered in the ticket management database 202 in advance.
[0065]
The ticket data is combined with the electronic mount data obtained from the mount management apparatus 100 to form an electronic ticket 50 (s2007). The specific procedure is as already described above with reference to FIGS. On the other hand, a request for updating the usage status of the mount data constituting the electronic ticket 50 is transmitted to the mount management apparatus 100. In response to this, the mount management apparatus 100 searches the electronic mount management database 102 for the corresponding mount ID and updates the use status of the mount (s2009). For example, a flag “used” is set in the electronic mount issuance verified flag column 68 in the electronic mount management record 60.
[0066]
The generated electronic ticket 50 is transmitted to the user device 300. The user device 300 receives this and stores it in a suitable storage device (s2008). Then, the ticket printing program 302 drives the printer device 303 to print the electronic ticket 50 on an appropriate print medium (2011). At this time, as described above, the individual information of the electronic ticket 50 is encoded (s2010). The individual information is pattern data, a two-dimensional barcode, and the like, and is overwritten on the areas 91 to 95.
[0067]
Further, a request for updating the usage status of the electronic ticket 50 is executed to the ticket management database 202 of the ticket management apparatus 200. In response to this, for example, in the ticket management verified flag column 78 in the ticket management record 70, the ticket management apparatus 200 sets a flag indicating that “the electronic ticket has been printed on the print medium and becomes a printed matter” (s2012).
The individual information encoding process may be executed by the user device 300.
[0068]
FIG. 16 is a diagram showing a flow of a ticket offline verification procedure in the present embodiment. Next, how to determine the effectiveness (presence / absence of tampering) in the scene where the printed matter 90 is actually used will be described. Here, an example in an environment where the ticket reception apparatus 400 is offline with the ticket verification apparatus 500 is shown.
[0069]
The ticket reception apparatus 400 receives the presentation of the printed matter 90 from a ticket user or the like, and performs a reading process on the image scanner apparatus 401 controlled by the capture program 402 (s2013). By the reading process, the coded individual information on the printed matter 90 is read.
[0070]
The electronic mount validity confirmation program 403 recognizes electronic mount pattern data (pattern) on the printed matter 90 and ticket content data from the ticket surface (printed paper surface) from the image reading result of the printed matter 90. That is, the individual information is recognized (s2014, s2015). If the individual information is recognized, the consistency between the individual information is determined, and it is clarified whether or not falsification has been made (s2016).
[0071]
Here, for example, there is a correlation between the pattern in the pattern data print area 91 or the pattern pattern area in the areas 92 to 95 recognized from the actual printed matter 90 and the area of the individual information overwritten on the pattern area. If the bar code printed in the ticket issuance signature data print area 93 or the like indicates consistency with the “correlation at the beginning of ticket issuance”, it can be determined that no falsification has been made.
[0072]
For example, if there is a deficiency in the pattern that should have been originally attached to the mount, it can be considered that there is a possibility of falsification. In other words, in order to falsify a ticket, even if you erase the data that was overwritten on the mount and enter another data on it, the pattern that was written on the mount when you erase the overwrite data is erased together. Eventually, tampering is discovered.
[0073]
FIG. 17 is a diagram showing a flow of a ticket online verification procedure in the present embodiment. On the other hand, the authenticity verification of the mount may be performed by the ticket verification apparatus 500 online. Therefore, the ticket reception apparatus 400 transfers the validity check data to the ticket verification apparatus 500 (s2018).
[0074]
While the ticket verification apparatus 500 performs the same validity checking process as described above (s2019), the ticket verification apparatus 500 corresponds to the printed matter 90 that has been recognized that the falsification has not been performed on the ticket management database 202 of the ticket management apparatus 200. A request for updating the usage status of the electronic ticket 50 is executed (s2020). In response to this, the ticket management apparatus 200 updates the ticket use verified data column 80 in the ticket management record 70 (s2021). Here, the ID (user ID) of the user device 300 is associated.
Alternatively, the ticket verification device 500 may be set to play a role of batch processing that collects the results of the validity checks performed by the ticket reception device 400 and transmits the results to the ticket reception device 400.
[0075]
FIG. 18 is a diagram showing an outline of an application example of an once-signature ticket as a second embodiment, and FIG. 19 is a diagram showing a print example of an once-signature ticket. Conventionally, there has been no way to sign a digital document, except that the agent keeps an authentication IC card or the like from the client. In that case, the possibility of unauthorized use of the authentication IC card could not be excluded, and a problem was left in terms of security. Therefore, the present invention has devised a technique for limiting the authority of the signature to be passed to the agent. That is, an exclusive signature ticket.
[0076]
A requester who requests a signature substitution or the like first prints the above-mentioned once-signature ticket (hereinafter simply referred to as a ticket) at the printing terminal 1900 to obtain a ticket as a printed matter 90. As shown in FIG. 19, the printed matter 90 is largely composed of two stub areas 1950 and 1960.
[0077]
One stub area 1950 (attached electronic ticket) has an electronic ticket that requires attachment in various application processes, that is, an electronic signature function. Similar to the configuration of the print medium 90 described above, there is an electronic mount pattern data print area 1951, which includes an “application attached stub” print area 1952, a ticket content data print area 1953, ticket issue signature data. A print area 1954 is included. Further, a ticket usage destination ID / reference number entry area 1955 is also arranged.
[0078]
The other stub area 1960 (returned electronic ticket) has an attribute for returning the processing status of the electronic ticket of the stub area 1950 to the requester side. Similarly, there is an electronic mount pattern data print area 1961, which includes a “ticket verification site sending stub” print area 1962, a ticket content data print area 1963, and a ticket issue signature data print area 1964. It is. Further, a ticket usage destination ID / reference number entry area 1965 is also arranged.
[0079]
Such a printed matter 90 is generated by printing processing in the printer apparatus 1903 by the ticket printing program 1902 after user authentication by the user confirmation program 1901 provided in the printing terminal 1900.
[0080]
The user who is requested to act as a signature by the requester separates the stub area 1950 from the printed matter 90. Then, it is submitted to the ticket reception device 400 together with the application document 95. Alternatively, if it is a digitized ticket reception place (for example, an application agent office), the electronic application input program 404 and an appropriate input / output interface corresponding thereto are provided, and the application document 95 is not required to be carried. In this case, the image of the stub area 1950 is read by the image scanner device 401, and the validity is determined under the electronic mount validity check program 403.
[0081]
If there is no falsification, the ticket verification device 1800 (for example, a government office window) that is the origin of the printed matter 90 deletes the validity of the stub area 1950 as an electronic ticket under the ticket status update program 1801. The ticket status is updated. Also, the electronic application acceptance program 1802 is activated, and normal electronic application processing with the electronic signature of the stub area 1950 is executed.
[0082]
The stub area 1950, that is, the attached electronic ticket, can set an upper limit value for the number of uses. For example, the processing data flag is included in the ticket data, and the flag is set each time reception processing is performed in the ticket verification device 1800 or the ticket reception device 400. If the flag reaches the upper limit value, the attached electronic ticket is validated. It destroys sex.
On the other hand, when the place where the ticket is received is not digitized, the validity of the electronic mount is confirmed by visual inspection or the like, and the detailed authentication is performed by a ticket verification apparatus 1850 having the same function as the ticket reception apparatus 400. It may be performed at.
[0083]
As mentioned above, although embodiment of this invention was described concretely based on the embodiment, it is not limited to this and can be variously changed in the range which does not deviate from the summary.
[0084]
【The invention's effect】
According to the present invention, it is possible to provide a ticket issuance management method and system and an information processing apparatus capable of performing validity confirmation economically and efficiently.
[Brief description of the drawings]
FIG. 1 is a diagram showing a conceptual model of a ticket issuance management method in the present embodiment.
FIG. 2 is a diagram illustrating a configuration example in which first to fourth information processing apparatuses are aggregated and regarded as one system (ticket issue management system).
FIG. 3 is a diagram illustrating an example of a data structure of an issuer authentication database.
FIG. 4 is a diagram illustrating an example of a data structure of an electronic mount management database.
FIG. 5 is a diagram showing an example data structure of a ticket management database.
FIG. 6 is a diagram illustrating a configuration example of a print medium according to the present embodiment.
FIG. 7 is an explanatory diagram conceptually showing processing performed on a region.
8 is an explanatory diagram illustrating an example of a dot pattern in consideration of reading by the information processing apparatus in FIGS. 7 and 9. FIG.
FIG. 9 is an explanatory diagram showing a painting method in consideration of the problem in FIG. 7;
FIG. 10 is a flowchart relating to a method of writing a unique value of a mount on a basic pattern for an area in which individual data is described, and a method for generating a fill pattern for this area.
FIG. 11 is a flowchart showing details of step 1350 in FIG.
12 is an explanatory diagram showing an example of a pattern created by the process shown in FIG.
FIG. 13 is a processing flow for overwriting individual data on a mount pattern.
FIG. 14 is a diagram showing a flow of a mount issuance procedure in the present embodiment.
FIG. 15 is a diagram showing a flow of a ticket issuing procedure in the present embodiment.
FIG. 16 is a diagram showing a flow of a ticket offline verification procedure in the embodiment;
FIG. 17 is a diagram showing a flow of a ticket online verification procedure in the present embodiment.
FIG. 18 is a diagram showing an outline of an application example of an once signature ticket as a second embodiment.
FIG. 19 is a diagram illustrating a print example of an once-signature ticket.
[Explanation of symbols]
10. Ticket issue management system, system
11 memory
12 Arithmetic unit, CPU
13 I / O controller
14 Input / output interface, user operation input / output section
15 Network adapter, communication network connection
16 Hard disks, storage devices
50 electronic tickets
55 Issuer Authentication Record
56 Issuer ID
57 Password for authentication
58 Acceptable request code
60 Electronic mount management record
61 Electronic mount ID column
62 Mount issue time column
63 Signature data column when issuing a mount
64 Valid period data column
65 Application identification data column
66 Encryption key column
67 Electronic mount issuer ID column
68 Electronic mount issue verified flag column
70 Ticket management records
71 Ticket issue time column
72 Ticket content data column
73 Ticket ID column
74 Ticket issue signature data column
75 Ticket User ID column
76 Electronic mount ID column
77 Electronic mount pattern data column
78 Ticket issue verified flag column
79 Ticket Validity Column
80 Ticket use verified data column
90 printed matter
91 Electronic mount pattern data printing area
92 Ticket content data printing area
93 Ticket issue signature data print area
94 Ticket valid period printing area
95 Used check area
100 First information processing apparatus, electronic mount issuance management apparatus, mount management apparatus
101 Issuer authentication database, Mount issuer authentication database
102 Electronic mount management database, mount management database
103 Electronic mount issuing program
104 Electronic mount status update program
150 Certificate Authority
200 Second information processing apparatus, ticket issue management apparatus, ticket management apparatus
201 Issuer authentication database, ticket issuer authentication database
202 Ticket management database
203 Issuer Confirmation Program
204 Ticket issuing program
205 Ticket status update program
300 Third information processing apparatus, user apparatus
301 User confirmation program
302 Ticket printing program
303 Printer, printing device
400 Ticket reception device
401 Image scanner device
402 Capture program
403 Electronic mount validity confirmation program
404 Verification data transfer program
500 ticket verification device
501 Image scanner device
502 Capture program
503 Electronic mount validity check program
504 Ticket status update request program
600 Communication network, network

Claims (9)

A method for performing ticket issue management by an information processing apparatus,
A first information processing device that generates ticket mount data is:
The storage device has a plurality of secret keys,
A mount issuer authentication database storing authentication information of a second information processing apparatus that issues a ticket, and a mount management database storing a use status of the ticket mount, and being accessible;
Receiving a ticket mount issue request from the second information processing apparatus;
Collating the authentication data included in the mount issuance request with the mount issuance destination authentication database and authenticating the second information processing apparatus;
If the second information processing apparatus is authenticated, first encrypted data is created by encrypting individual information of the mount with the first secret key according to the number of mount issuance requests included in the mount issuance request. Then, the first encryption data is encoded, the first data having a single color dot or pixel coloring pattern corresponding to the code is generated, and the first encryption data is converted into a second secret key. The process of generating the second encrypted data by encrypting, encoding the second encrypted data, and generating the second data of the single color dot or pixel coloring pattern corresponding to the code, Alternatively, it repeats until the predetermined area of the mount is filled with data of pixel coating pattern data, and generates the mount data;
Registering the issuance status of each mount data in the mount management database;
Transmitting the mount data to the second information processing apparatus,
The second information processing apparatus is
Access to a ticket issuer authentication database storing authentication information of a third information processing apparatus that performs ticket printing, and a ticket management database storing ticket usage status;
Receiving a ticket issue request from the third information processing apparatus;
Collating authentication data included in the ticket issuance request with the ticket issuance destination authentication database and authenticating the third information processing apparatus;
If the third information processing apparatus is authenticated, generating ticket data according to the number of ticket issuance requests included in the ticket issuance request;
Registering the issuance status for each ticket data in the ticket management database;
Generating the electronic ticket by synthesizing the ticket data with the mount data composed of data of a single color dot or pixel painting pattern;
Executing a request to update the usage status of the mount data constituting the electronic ticket to the mount management database;
Transmitting the electronic ticket to the third information processing apparatus,
The third information processing apparatus is
Receiving an electronic ticket from the second information processing apparatus;
Encoding the individual information of the electronic ticket that indicates the correlation between the data of the single color dot or pixel coating pattern constituting the mount data and the data of the print area overwritten on the pattern;
Combining the coded individual information into an electronic ticket and outputting it to a printing device;
Executing a request to update the usage status of the electronic ticket with respect to the ticket management database;
A fourth information processing apparatus for accepting use of the printed matter of the electronic ticket;
Reading the coded individual information on the printed matter indicating the correlation between the mount data and the data of the print area;
Performing image reading of the printed matter, and recognizing individual information indicating a correlation between the mount data and the data of the printing area on the printed matter;
Determining consistency between the individual information; and
As a result of the determination, if consistency is obtained between the individual information, it is recognized that tampering has not been performed, and a step of outputting the fact to the output interface is executed.
A ticket issuance management method characterized by the above. The first information processing apparatus is
In generating the mount data, a step of referring to a table in which the attribute of the mount to be generated is determined for each second information processing apparatus and specifying the generation contents of the mount data according to the corresponding second information processing apparatus. The ticket issuance management method according to claim 1, wherein the ticket issuance management method is executed.   The ticket issue management method according to claim 1, wherein the encoding of the individual information is executed in the second information processing apparatus. The fourth information processing apparatus is
2. The ticket according to claim 1 , further comprising a step of executing a request for updating a usage status of an electronic ticket corresponding to a printed matter recognized as not being falsified with respect to the ticket management database. Issuance management method. The storage device has a plurality of secret keys,
A mount issuer authentication database storing authentication information of a second information processing apparatus that issues a ticket, and a mount management database storing a use status of the ticket mount, and being accessible;
Means for receiving a ticket mount issue request from the second information processing apparatus;
Means for verifying the second information processing apparatus by collating authentication data included in the mount issuance request with the mount issuance destination authentication database;
If the second information processing apparatus is authenticated, first encrypted data is created by encrypting individual information of the mount with the first secret key according to the number of mount issuance requests included in the mount issuance request. Then, the first encryption data is encoded, the first data having a single color dot or pixel coloring pattern corresponding to the code is generated, and the first encryption data is converted into a second secret key. The process of generating the second encrypted data by encrypting, encoding the second encrypted data, and generating the second data of the single color dot or pixel coloring pattern corresponding to the code, Alternatively, means for generating mount data repeatedly until the predetermined area of the mount is filled with data of pixel coating patterns,
Means for registering the issuance status for each mount data in the mount management database;
A first information processing apparatus comprising: means for transmitting the mount data to the second information processing apparatus;
Access to a ticket issuer authentication database storing authentication information of a third information processing apparatus that performs ticket printing, and a ticket management database storing ticket usage status;
Means for receiving a ticket issue request from the third information processing apparatus;
Means for collating authentication data included in the ticket issue request with the ticket issuer authentication database and authenticating the third information processing apparatus;
Means for generating ticket data according to the number of ticket issuance requests included in the ticket issuance request if the third information processing apparatus is authenticated;
Means for registering the issuance status in the ticket management database for each ticket data;
Means for generating an electronic ticket by synthesizing the ticket data with the mount data composed of data of a single-color dot or pixel painting pattern;
Means for executing a request to update the usage status of the mount data constituting the electronic ticket to the mount management database;
A second information processing apparatus comprising: means for transmitting the electronic ticket to the third information processing apparatus;
Means for receiving an electronic ticket from the second information processing apparatus;
Means for encoding the individual information of the electronic ticket indicating the correlation between the data of the single color dot or pixel coating pattern constituting the mount data and the data of the print area overwritten on the pattern;
Means for synthesizing the coded individual information into an electronic ticket and outputting it to a printing device;
A third information processing apparatus comprising means for executing a request to update the usage status of the electronic ticket with respect to the ticket management database;
Means for reading the individual information indicating the correlation between the encoded data on the printed matter and the data of the print area ;
Means for performing image reading of the printed matter and recognizing individual information indicating a correlation between the mount data and the data of the print area on the printed matter;
Means for determining consistency between the individual information;
As a result of the determination, if consistency is obtained between the individual information, a fourth information processing apparatus including means for recognizing that tampering has not been performed and outputting the fact to the output interface;
A ticket issuance management system comprising: The storage device has a plurality of secret keys,
A mount issuer authentication database storing authentication information of a second information processing apparatus that issues a ticket, and a mount management database storing a use status of the ticket mount, and being accessible;
Means for receiving a ticket mount issue request from the second information processing apparatus;
Means for verifying the second information processing apparatus by collating authentication data included in the mount issuance request with the mount issuance destination authentication database;
If the second information processing apparatus is authenticated, first encrypted data is created by encrypting individual information of the mount with the first secret key according to the number of mount issuance requests included in the mount issuance request. Then, the first encryption data is encoded, the first data having a single color dot or pixel coloring pattern corresponding to the code is generated, and the first encryption data is converted into a second secret key. The process of generating the second encrypted data by encrypting, encoding the second encrypted data, and generating the second data of the single color dot or pixel coloring pattern corresponding to the code, Alternatively, means for generating mount data repeatedly until the predetermined area of the mount is filled with data of pixel coating patterns,
Means for registering the issuance status for each mount data in the mount management database;
Means for transmitting the mount data to the second information processing apparatus;
An information processing apparatus comprising: Access to a ticket issuer authentication database storing authentication information of a third information processing apparatus that performs ticket printing, and a ticket management database storing ticket usage status;
Means for receiving a ticket issue request from the third information processing apparatus;
Means for collating authentication data included in the ticket issue request with the ticket issuer authentication database and authenticating the third information processing apparatus;
Means for generating ticket data according to the number of ticket issuance requests included in the ticket issuance request if the third information processing apparatus is authenticated;
Means for registering the issuance status in the ticket management database for each ticket data;
Means for generating an electronic ticket by synthesizing the ticket data with mount data composed of single-color dot or pixel pattern data;
Means for executing a request for updating the usage status of the mount data constituting the electronic ticket to the mount management database storing the usage status of the ticket mount;
Means for transmitting the electronic ticket to the third information processing apparatus;
An information processing apparatus comprising: Means for receiving electronic ticket data from the second information processing device;
Means for encoding the individual information of the electronic ticket indicating the correlation between the data of the single color dot or pixel coating pattern constituting the mount data of the electronic ticket and the data of the print area overwritten on the pattern;
Means for synthesizing the coded individual information into an electronic ticket and outputting it to a printing device;
Means for executing a request to update the usage status of the electronic ticket with respect to the ticket management database storing the usage status of the ticket;
An information processing apparatus comprising: Printed electronic ticket printed with individual electronic ticket information coded and output indicating the correlation between the data of the single color dot or pixel coating pattern composing the mount data and the print area data overwritten on the pattern A means for reading the coded individual information;
Means for performing image reading of the printed matter and recognizing individual information indicating a correlation between the mount data and the data of the print area on the printed matter;
Means for determining consistency between the individual information;
As a result of the determination, when consistency is obtained between the individual information, the means for recognizing that the falsification has not been performed, and outputting the fact to the output interface;
An information processing apparatus comprising:

Images